How to show iDRAC SNMP Trap on Nagios XI Interface

[timlee]

Lets try changing the EVENT line to:

Code: Select all

EVENT alertTestTrapEvent SNMPv2-SMI::enterprises.674.10892.5.3.2.5.0.10395 "Status Events" INFORMATIONAL

Save and restart

Code: Select all

service snmptt restart

Now send the test trap again. Does this work?

Sorry bro, this one doesn't fix the problem either.

[ssax]

I'm not seeing the trap for that in your snmptt.conf file that you attached, where are you making those changes?

[Box293]

OK this is what I'm seeing:

Code: Select all

Trap received from 192.168.168.221: TST001
0:		hostname
1:		ip address
2:		uptime
3:		trapname / OID
4:		ip address from trap agent
5:		trap community string
6:		enterprise
7:		securityEngineID        (snmptthandler-embedded required)
8:		securityName            (snmptthandler-embedded required)
9:		contextEngineID         (snmptthandler-embedded required)
10:		contextName             (snmptthandler-embedded required)
0+:		passed variables

Value 0: 192.168.168.221

Value 1: 192.168.168.221

Value 2: SNMPv2-SMI::enterprises.674.10892.5.3.2.5.0.10395

Value 3: TST001

Value 3 is supposed to be the OID that the EVENT line matches but for some reason it's coming though in the Value 2. Hence it's trying to match TST001. I've not come across this before.

[timlee]

I'm not seeing the trap for that in your snmptt.conf file that you attached, where are you making those changes?

Hi ssax, the attached is a snmptt.debug file.

[timlee]

OK this is what I'm seeing:

Code: Select all

Trap received from 192.168.168.221: TST001
0:		hostname
1:		ip address
2:		uptime
3:		trapname / OID
4:		ip address from trap agent
5:		trap community string
6:		enterprise
7:		securityEngineID        (snmptthandler-embedded required)
8:		securityName            (snmptthandler-embedded required)
9:		contextEngineID         (snmptthandler-embedded required)
10:		contextName             (snmptthandler-embedded required)
0+:		passed variables

Value 0: 192.168.168.221

Value 1: 192.168.168.221

Value 2: SNMPv2-SMI::enterprises.674.10892.5.3.2.5.0.10395

Value 3: TST001

Value 3 is supposed to be the OID that the EVENT line matches but for some reason it's coming though in the Value 2. Hence it's trying to match TST001. I've not come across this before.

In this case are we able to tweak the position of value 2 and value 3? Say under EXEC?

[Box293]

The EXEC line is what has to match the incoming OID before anything else.

I don't know of a way to tell SNMPTT to look at Value 2 instead of Value 3. Maybe one of the other Nagios techs will know.

[timlee]

The EXEC line is what has to match the incoming OID before anything else.

I don't know of a way to tell SNMPTT to look at Value 2 instead of Value 3. Maybe one of the other Nagios techs will know.

Hi mate, I did a check on the Dell Test Notification Reference

DellTestEventNotificationMessageReference_20121214.pdf

and realised that TST001 is not a valid Test event. I wonder why DEll even went to create an eventID that is not even valid....

I tried on Web GUI Test event with a valid code e.g. BAT0007 and the Trap Receiver Host actually receives it!

webGuiTestEvent.JPG

However, the trap is received under the SNMP Trap row, which is the last column and every other trap just falls into there.
Is there any way to separate it out like the above according to different components?

trapReceiver.JPG

[ssax]

You would want to edit your /etc/snmp/snmptt.conf

Changing the EXEC line for the OID's you want to have different service names, you would change:

Code: Select all

"SNMP Traps"

To:

Code: Select all

"SNMP Traps - Your Service Name"

You can add a MATCH to those to fire on specific information contained in the trap if you need duplicate OIDs that fire on different text.
http://snmptt.sourceforge.net/docs/snmp ... CONF-MATCH

[abrist]

and realised that TST001 is not a valid Test event. I wonder why DEll even went to create an eventID that is not even valid....

Yeah, manufactures have an issue with there mibs not even supporting their own events (especially their test traps oids) . . .

[timlee]

You would want to edit your /etc/snmp/snmptt.conf

Changing the EXEC line for the OID's you want to have different service names, you would change:

Code: Select all

"SNMP Traps"

To:

Code: Select all

"SNMP Traps - Your Service Name"

You can add a MATCH to those to fire on specific information contained in the trap if you need duplicate OIDs that fire on different text.
http://snmptt.sourceforge.net/docs/snmp ... CONF-MATCH

Thanks ssax, Troy, and everyone's help. It is working now.

Just another question. How do I remove the MIBs, or rather the link, that I have uploaded as processed traps?
I have already removed it from the web GUI under Admin > Manage MIBs and under the folder /usr/share/snmp/mibs/processed_mibs/, however when I restart snmptt service, I still get this prompt.

Code: Select all

[root@Cent6-TrapReceiver ~]# service snmptt restart
Stopping snmptt:                                           [  OK  ]
Starting snmptt: PID file: /var/run/snmptt.pid
Could not open configuration file: /usr/share/snmp/mibs/processed_mibs/iDRAC-MIB.txt (No such file or directory) at /usr/sbin/snmptt line 2723.
                                                           [  OK  ]