Nagios Support Forum

Ok, the next step in the chain is checking in the /etc/snmp/snmptt.conf to find the proper response for .1.3.6.1.6.3.1.1.5.1, is there an entry for .1.3.6.1.6.3.1.1.5.1 or whatever .1.3.6.1.6.3.1.1.5.1 resolves to?

This is what is inside the snmptt.conf when I searched for the: .1.3.6.1.6.3.1.1.5.1

#
EVENT coldStart .1.3.6.1.6.3.1.1.5.1 "Status Events" Normal
FORMAT A coldStart trap signifies that the SNMP entity, $*
EXEC /usr/local/bin/snmptraphandling.py "$r" "SNMP Traps" "$s" "$@" "$-*" "A coldStart trap signifies that the SNMP entity, $*"
SDESC
A coldStart trap signifies that the SNMP entity,
supporting a notification originator application, is
reinitializing itself and that its configuration may
have been altered.
Variables:
EDESC
#

Ok, so it is in there, and we can verify that you are actually receiving the traps. And, actually, Nagios XI was getting the traps before (as indicated that they showed up in the Unconfigured Objects). Lets just do a quick test to make sure that pipe is working. In this example replace <HOST> with the host name.

/usr/local/bin/snmptraphandling.py "<HOST>" "SNMP Traps" "Normal" `date +%s` ' ' 'Hi ecarrasq'

Please note the quotes around date +%s are backticks (which is the quote located directly above tab.) Now 'Hi ecarasssq' should show up under the SNMP Traps service of <HOST> with Normal/OK status.

THAT WORKED!!!!

now what?

Should the traps be sent a certain way? Is there any configuration changes I need to do to the snmptt.conf?

Thanks!

I just sent a SNMP trap via the siteminder server and its working!!!!!!!!!!!!!!!!!!!!1

THANK YOU NAGIOS SUPPORT TEAM!

Thank YOU for participating with that troubleshooting, I'll be updating the doc with what we went through.