GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: snmpd.conf error
Operating System - HP-UX
1847583
Members
3051
Online
110265
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2007 05:02 AM
01-31-2007 05:02 AM
snmpd.conf error
hate to have to ask this here, but I know there are some solaris users here. I support HPUX x 35. I have 1 Solaris system giving me a fit.
Security asked me to
comment out the fields which
were open to public and when we do that we are having a problem at reboot. Get the following errors :
/usr/lib/snmp/snmpdx: community_check() : bad community from localhost
Jan 30 10:48:09 s0b1296 /usr/lib/snmp/snmpdx: session_open() failed for a pdu received from localhost.32781
Jan 30 10:48:09 s0b1296 /usr/lib/snmp/snmpdx: community_check() : bad community from localhost
ANyone have this issue before. Its a security mandate, but I cant seem to get around the error.
Security asked me to
comment out the fields which
were open to public and when we do that we are having a problem at reboot. Get the following errors :
/usr/lib/snmp/snmpdx: community_check() : bad community from localhost
Jan 30 10:48:09 s0b1296 /usr/lib/snmp/snmpdx: session_open() failed for a pdu received from localhost.32781
Jan 30 10:48:09 s0b1296 /usr/lib/snmp/snmpdx: community_check() : bad community from localhost
ANyone have this issue before. Its a security mandate, but I cant seem to get around the error.
UNIX IS GOOD
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2007 07:07 AM
01-31-2007 07:07 AM
Re: snmpd.conf error
Shalom,
I remember vaguely something about certain community strings being no good because they are reserved words.
Security may not know what they are doing. Usually we change the string names and limit what the public can see or do.
In addition, snmp can be shielded with firewalls and tcp wrappers configuration to keep the public from exploiting snmp or even knowing the system has it running.
I'd tell security to please go back to the drawing board on this, or pull a configuration string from a working system.
It might be nice to see the conf file if permitted.
SEP
I remember vaguely something about certain community strings being no good because they are reserved words.
Security may not know what they are doing. Usually we change the string names and limit what the public can see or do.
In addition, snmp can be shielded with firewalls and tcp wrappers configuration to keep the public from exploiting snmp or even knowing the system has it running.
I'd tell security to please go back to the drawing board on this, or pull a configuration string from a working system.
It might be nice to see the conf file if permitted.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-02-2007 12:42 AM
02-02-2007 12:42 AM
Re: snmpd.conf error
Firstly, you don't need SNMP to survive, or do you have some network management like OpenView NNM?
Then, apart from setting/changing SNMP community strings, you can define views on Solaris AFAIK. The other question is if someone changed your SNMP port (usually UDP/161).
Then, apart from setting/changing SNMP community strings, you can define views on Solaris AFAIK. The other question is if someone changed your SNMP port (usually UDP/161).
http://www.tresselt.eu
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP