Substitute your desired community name in place of public but obviously since this is must be exactly the same everywhere stay away from reserved characters like backslashes. The IP address is wherever you intend to monitor the traps and can be replaced with a hostname.
The smuxpeer line grants access to the SNMP OID section for Dell hardware events being transmitted over the SNMP service and is added automatically during the installation of Server Administrator assuming the service is installed and running before you begin. You can easily add it later as long as you restart the snmpd service. If you ever need the smuxpeer line which is kind of long I usually check the Server Administrator User's Guide section on Configuring SNMP on Systems Running RedHat Enterprise Linux.
<ADMIN NOTE: Broken link has been removed from this post by Dell>
Message Edited by divot2001 on 06-17-2008 12:23 PM
I was wondering if anyone know how to turn off snmp authentication errors on a Linux box? I am just not sure which option within snmpd.conf controls this...
In that case there are most likely two issues happening.
Connected using the Get Community Names - dell
Connected using the Set Community Names - dell
Connected to the agent software(s) - [mib2, NA]
First, because of the response you received through IT Assistant, you are using a different SNMP community on the Windows system running IT Assistant. So if you haven't already modified the community name in the snmpd.conf I posted you'll need to do so. If you have already done this skip ahead.
I did however install OpenManage Assistant first, then snmp.
Second, because you installed OpenManage before SNMP the installation did not have the ability to add a very critical line (smuxpeer .1.3.6.1.4.1.674.10892.1) that grants the necessary privileges to the OpenManage/Dell section of the SNMP service. Short answer is install SNMP and start the service first or reinstall it if you want to save time.
Alternately, you can simply append the line yourself and restart snmpd.
Please try using the following config and posting the output of the included commands.
**** begin text to be added to snmpd.conf **** replace X.X.X.X with the IP address of the RHEL 5 server
rocommunity dell
trapsink X.X.X.X dell
smuxpeer .1.3.6.1.4.1.674.10892.1
****end text to be added to snmpd.conf
rm /etc/snmp/snmpd.conf
vi /etc/snmp/snmpd.conf
service snmpd restart
That's all. Don't include any other settings until after you discover the server.
Then in IT Assistant run the same test only using the X.X.X.X IP address. If it still fails include the output. Also tell me if you have any Linux servers actually being discovered or if they all run Windows. It is possible that you SNMP problems on the IT Assistant side if WMI is being used to discover only Windows systems. They can sometimes deceive you when they use the client discovery protocols instead of SNMP.
Message Edited by divot2001 on 08-22-2008 02:18 AM
// Disable authentication failure traps (or delete the line entirely)
authtrapenable 2
// Enable authentication failure traps
authtrapenable 1
I would suggest removing the line entirely due to certain versions of net-snmp not accepting the authtrapenable parameter. https://bugzilla.redhat.com/show_bug.cgi?id=426497 Always best not to add something you don't need.
divot2001
52 Posts
0
June 17th, 2008 16:00
cd /etc/snmp (/etc for SLES 9 only)
mv snmpd.conf snmpd.old
vi snmpd.conf
service snmpd restart
rocommunity public
trapsink 192.168.0.10 public
smuxpeer .1.3.6.1.4.1.674.10892.1
Substitute your desired community name in place of public but obviously since this is must be exactly the same everywhere stay away from reserved characters like backslashes. The IP address is wherever you intend to monitor the traps and can be replaced with a hostname.
The smuxpeer line grants access to the SNMP OID section for Dell hardware events being transmitted over the SNMP service and is added automatically during the installation of Server Administrator assuming the service is installed and running before you begin. You can easily add it later as long as you restart the snmpd service. If you ever need the smuxpeer line which is kind of long I usually check the Server Administrator User's Guide section on Configuring SNMP on Systems Running RedHat Enterprise Linux.
<ADMIN NOTE: Broken link has been removed from this post by Dell>
Message Edited by divot2001 on 06-17-2008 12:23 PM
davekkkk
3 Posts
0
June 17th, 2008 20:00
I did see this in the guide, but I thought it said it was for SUSE only, so I wasnt sure.
I added it, and still no luck. Going through ITA on another server shows that it can connect fine.
Connected using the Get Community Names - dell
Connected using the Set Community Names - dell
Connected to the agent software(s) - [mib2, NA]
I did however install OpenManage Assistant first, then snmp.
Thanks for the help.
Stooartbaby
2 Intern
•
132 Posts
0
July 30th, 2008 02:00
I was wondering if anyone know how to turn off snmp authentication errors on a Linux box? I am just not sure which option within snmpd.conf controls this...
Thanks,
Stuart.
divot2001
52 Posts
0
August 16th, 2008 01:00
In that case there are most likely two issues happening.
Connected using the Get Community Names - dell
Connected using the Set Community Names - dell
Connected to the agent software(s) - [mib2, NA]
First, because of the response you received through IT Assistant, you are using a different SNMP community on the Windows system running IT Assistant. So if you haven't already modified the community name in the snmpd.conf I posted you'll need to do so. If you have already done this skip ahead.
I did however install OpenManage Assistant first, then snmp.
Second, because you installed OpenManage before SNMP the installation did not have the ability to add a very critical line (smuxpeer .1.3.6.1.4.1.674.10892.1) that grants the necessary privileges to the OpenManage/Dell section of the SNMP service. Short answer is install SNMP and start the service first or reinstall it if you want to save time.
Alternately, you can simply append the line yourself and restart snmpd.
Please try using the following config and posting the output of the included commands.
**** begin text to be added to snmpd.conf
**** replace X.X.X.X with the IP address of the RHEL 5 server
rocommunity dell
trapsink X.X.X.X dell
smuxpeer .1.3.6.1.4.1.674.10892.1
****end text to be added to snmpd.conf
rm /etc/snmp/snmpd.conf
vi /etc/snmp/snmpd.conf
service snmpd restart
That's all. Don't include any other settings until after you discover the server.
Then in IT Assistant run the same test only using the X.X.X.X IP address. If it still fails include the output. Also tell me if you have any Linux servers actually being discovered or if they all run Windows. It is possible that you SNMP problems on the IT Assistant side if WMI is being used to discover only Windows systems. They can sometimes deceive you when they use the client discovery protocols instead of SNMP.
divot2001
52 Posts
0
August 16th, 2008 01:00
// Disable authentication failure traps (or delete the line entirely)
authtrapenable 2
// Enable authentication failure traps
authtrapenable 1
I would suggest removing the line entirely due to certain versions of net-snmp not accepting the authtrapenable parameter. https://bugzilla.redhat.com/show_bug.cgi?id=426497 Always best not to add something you don't need.
davekkkk
3 Posts
0
August 21st, 2008 13:00