An authenticationFailure trap signifies that the SNMP /

[jbennett]

I cannot figure out how to resolve this as it relates to Nagios. When I search online, it seems that all I get is something for Cisco.

Since I have set up SNMP Traps months ago to work with our Nagios installation, I've forgotten everything it seems.

I have checked the snmpd.conf file as well as the snmptt.conf file and verified the the user and community (or so I think) but I'm still getting this warning message as a Trap for localhost.

I cannot see the entire warning as it is cut off at the slash:

An authenticationFailure trap signifies that the SNMP /

Any guidance on where to start would be greatly appreciated.

[sreinhardt]

So this is a trap purely internal to the machine? Have you taken a look at the snmp logs or /var/log/messages?

[jbennett]

Code: Select all

 snmptt]# tail snmptt.debug
Agent IP address (10.250.2.55) resolved to: xxx.yyy.local

Agent IP address was blank, so setting to the same as the host IP address of 127.0.0.1

Agent IP address (127.0.0.1) is the same as the host IP, so copying the host name: localhost.localdomain

Agent IP address was blank, so setting to the same as the host IP address of 127.0.0.1

Code: Select all

snmptt]# tail snmptt.log
Mon Aug 12 16:26:35 2013 .1.3.6.1.6.3.1.1.5.5 Warning "Status Events" xxx - An authenticationFailure trap signifies that the SNMP
Mon Aug 12 16:26:35 2013 .1.3.6.1.6.3.1.1.5.5 Warning "Status Events" localhost - An authenticationFailure trap signifies that the SNMP
Mon Aug 12 16:26:35 2013 .1.3.6.1.6.3.1.1.5.5 Warning "Status Events" localhost - An authenticationFailure trap signifies that the SNMP

snmpttunknown.log only shows items that I'm already aware of (can't get MIBs for those PDus that are correct it seems).

[abrist]

AuthFailure traps are *almost always* due to community issues or snmp v3 auth problems. Some device (possibly nagios) is trying to check (through snmpget or a walk) an OID on one of your devices and is failing the auth. This trap is in turn sent to nagios where it is failing lookup and reporting it as a localhost trap failure. At least that is my conjecture.

Do you know which trap/check is causing this?