SNMP Trap from specific host not working

[r.jaynes]

Greetings all. We have one host that is successfully sending in SNMP traps, and we get alerts when they come in. I've added a new host (different manufacturer/product/etc), and setup SNMP traps, but all we seem to see is "Waiting for traps...". I have added the MIB's from the manufacturer into /usr/share/snmp/mibs, and used the 'addmib /usr/share/snmp/mibs/FILENAME-MIB.txt' to add them. If I double check inside /etc/snmp/snmptt.conf, I see reference to the MIB's in the path, and there is a section where it imported the MIB's directly. I turned on logging in /etc/snmp/snmptt.ini, and output the logs to /var/log/snmptt/snmptt.log.

When I open the log file, I see where our device's trap is coming in:

Code: Select all

Thu Mar 10 10:33:17 2011 .1.3.6.1.4.1.664.1.198.0.44686 MAJOR "Status Events" 204.80.201.21 - Status - Alarm: MX2800 44686 T1/E1 LOS Condition ActiveDSX Index: 28, Line ID: OFC Backroom Data, Alarm Status, 13System Name, AMX8A

When I grep for that OID in /etc/snmp/snmptt.conf, I get:

Code: Select all

snmptt.conf:EVENT adMX2800xSetT1E1LOS .1.3.6.1.4.1.664.1.198.0.44686 "Status Events" MAJOR

It appears that the OID is in place and matches the trap, yet we don't get any response. I've tried to look as much into this as possible without contacting you guys first, but i'm hitting some walls now. Any help is appreciated!

[r.jaynes]

Sorry, I didn't include relevant system info:

VMWare Image install, very few back end changes
Installed Version: 2009R1.3F

[r.jaynes]

If it helps, here is the full entry for this particular trap in /etc/snmp/snmptt.conf:

Code: Select all

EVENT adMX2800xSetT1E1LOS .1.3.6.1.4.1.664.1.198.0.44686 "Status Events" MAJOR
FORMAT Status - Alarm: MX2800 44686 T1/E1 LOS Condition ActiveDSX Index: $1, Line ID: $2, Alarm Status, $3System Name, $4
EXEC /usr/local/bin/snmptraphandling.py "$r" "SNMP Traps" "$s" "$@" "$-*" "Status - Alarm: MX2800 44686 T1/E1 LOS Condition ActiveDSX Index: $1, Line ID: $2, Alarm Status, $3System Name, $4"
SDESC
This indicates that MX2800 enters T1/E1 LOS mode.
Variables:
  1: adMX2800StatusDSXIndex
  2: adMX2800DSXCfgLineID
  3: adMX2800SystemAlarmStatus
  4: sysName
EDESC

[tonyyarusso]

Try changing

Code: Select all

EVENT adMX2800xSetT1E1LOS .1.3.6.1.4.1.664.1.198.0.44686 "Status Events" MAJOR

to

Code: Select all

EVENT adMX2800xSetT1E1LOS .1.3.6.1.4.1.664.1.198.0.44686 "Status Events" Critical

in /etc/snmp/snmptt.conf and restart the snmptt daemon.

[r.jaynes]

THANK YOU!

I guess all it took was another pair of eyes. I swear I've been pouring over the documentation on all of this now for two days, and that never hit me. I changed MAJOR to Critical, and NORMAL to Normal, and now we're receiving both types of traps from our test system. Onward to victory.

[rdedon]

Just feel free to post any issues you have in the future and we will be glad to help