How to show iDRAC SNMP Trap on Nagios XI Interface

[timlee]

Hi,

I have managed to upload the MIB from from dell with trap processed. but how do you manage to show the traps on Naigos XI interface? Currently I am only able to receive the traps in /var/log/snmptt/snmpttunknow.log instead of snmptt.log

Attached is the MIB file, and below is the capture from snmpttunknown.log captured from the SNMPTT Trap sent from iDRAC.

Code: Select all

Wed Apr 22 17:07:34 2015: Unknown trap (TST001) received from 192.168.168.221 at:
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 4: 192.168.168.221
Value 5:
Value 6:
Value 7:
Value 8:
Value 9:
Value 10:
Ent Value 0: .1.3.6.1.4.1.674.10892.5.3.1.2.0=The iDRAC generated a test trap event in response to a user request. (Trap generated using SNMPv2 format.)
Ent Value 1: .1.3.6.1.4.1.674.10892.5.3.1.3.0=3
Ent Value 2: .1.3.6.1.4.1.674.10892.5.3.1.4.0=3XWVYY1
Ent Value 3: .1.3.6.1.4.1.674.10892.5.3.1.5.0=nxl-esxi02.systex.com.sg
Ent Value 4: .1.3.6.1.4.1.674.10892.5.3.1.6.0=
Ent Value 5: .1.3.6.1.4.1.674.10892.5.3.1.7.0=
Ent Value 6: .1.3.6.1.4.1.674.10892.5.3.1.8.0=
Ent Value 7: .1.3.6.1.4.1.674.10892.5.3.1.9.0=

[abrist]

If the trap appears in snmpttunknown.log, it is not matching any snmptt rule. Just to make sure that snmptt rules have been created for the mib, can you run:

Code: Select all

addmib /usr/share/snmp/mibs/<file name of mib>

[timlee]

If the trap appears in snmpttunknown.log, it is not matching any snmptt rule. Just to make sure that snmptt rules have been created for the mib, can you run:

Code: Select all

addmib /usr/share/snmp/mibs/<file name of mib>

Hi, thanks for your advice, but I have already done that and it doesn't work.

[Box293]

Please post the processed mib file that was generated after adding the mib:

/usr/share/snmp/mibs/processed_mibs/<file name of mib>

[timlee]

Please post the processed mib file that was generated after adding the mib:

/usr/share/snmp/mibs/processed_mibs/<file name of mib>

Hi Troy,
The processed mib file is in first post. Thank you.

[Box293]

Sorry I missed that. For the test trap you supplied, this is the EVENT for that trap:

Code: Select all

EVENT alertTestTrapEvent .1.3.6.1.4.1.674.10892.5.3.2.5.0.10395 "Status Events" INFORMATIONAL
FORMAT Configuration: iDRAC Test Trap Event: Message ID: $1, Device Display Name: $7, Message: $2,Device Status: $3, Device FQDD: $6,System Service Tag: $4, System Name: $5,Chassis Service Tag: $9
SDESC
The iDRAC generated a test trap event in response to a user request.
Variables:
  1: alertMessageID
  2: alertMessage
  3: alertCurrentStatus
  4: alertSystemServiceTag
  5: alertSystemFQDN
  6: alertFQDD
  7: alertDeviceDisplayName
  8: alertMessageArguments
  9: alertChassisServiceTag
EDESC

Let's add the missing EXEC line:

Code: Select all

EVENT alertTestTrapEvent .1.3.6.1.4.1.674.10892.5.3.2.5.0.10395 "Status Events" INFORMATIONAL
FORMAT Configuration: iDRAC Test Trap Event: Message ID: $1, Device Display Name: $7, Message: $2,Device Status: $3, Device FQDD: $6,System Service Tag: $4, System Name: $5,Chassis Service Tag: $9
EXEC /usr/local/bin/snmptraphandling.py "$r" "SNMP Traps" "$s" "$@" "$-*" "Configuration: iDRAC Test Trap Event: Message ID: $1, Device Display Name: $7, Message: $2,Device Status: $3, Device FQDD: $6,System Service Tag: $4, System Name: $5,Chassis Service Tag: $9"

Then

Code: Select all

service snmptt restart

This will sent a passive check result to Nagios for the service "SNMP Traps" for a host object with the address 192.168.168.221.
IF a host object with the address 192.168.168.221 does NOT exist, then it will appear under Admin > Monitoring Config > Unconfigured Objects.

[timlee]

Sorry I missed that. For the test trap you supplied, this is the EVENT for that trap:

Code: Select all

EVENT alertTestTrapEvent .1.3.6.1.4.1.674.10892.5.3.2.5.0.10395 "Status Events" INFORMATIONAL
FORMAT Configuration: iDRAC Test Trap Event: Message ID: $1, Device Display Name: $7, Message: $2,Device Status: $3, Device FQDD: $6,System Service Tag: $4, System Name: $5,Chassis Service Tag: $9
SDESC
The iDRAC generated a test trap event in response to a user request.
Variables:
  1: alertMessageID
  2: alertMessage
  3: alertCurrentStatus
  4: alertSystemServiceTag
  5: alertSystemFQDN
  6: alertFQDD
  7: alertDeviceDisplayName
  8: alertMessageArguments
  9: alertChassisServiceTag
EDESC

Let's add the missing EXEC line:

Code: Select all

EVENT alertTestTrapEvent .1.3.6.1.4.1.674.10892.5.3.2.5.0.10395 "Status Events" INFORMATIONAL
FORMAT Configuration: iDRAC Test Trap Event: Message ID: $1, Device Display Name: $7, Message: $2,Device Status: $3, Device FQDD: $6,System Service Tag: $4, System Name: $5,Chassis Service Tag: $9
EXEC /usr/local/bin/snmptraphandling.py "$r" "SNMP Traps" "$s" "$@" "$-*" "Configuration: iDRAC Test Trap Event: Message ID: $1, Device Display Name: $7, Message: $2,Device Status: $3, Device FQDD: $6,System Service Tag: $4, System Name: $5,Chassis Service Tag: $9"

Then

Code: Select all

service snmptt restart

This will sent a passive check result to Nagios for the service "SNMP Traps" for a host object with the address 192.168.168.221.
IF a host object with the address 192.168.168.221 does NOT exist, then it will appear under Admin > Monitoring Config > Unconfigured Objects.

Hi I've just tried that but it is still showing at snmpttumknow.log

[Box293]

If it is showing in unknown log then it is not being matched.

Edit the file:

Code: Select all

/etc/snmp/snmptt.ini 

Define the following settings:

Code: Select all

DEBUGGING = 2 
DEBUGGING_FILE = /var/log/snmptt/snmptt.debug 

Save the file and restart snmptt

Code: Select all

service snmptt restart

Send the test trap again.

Post the debug log: /var/log/snmptt/snmptt.debug here.

[timlee]

If it is showing in unknown log then it is not being matched.

Edit the file:

Code: Select all

/etc/snmp/snmptt.ini 

Define the following settings:

Code: Select all

DEBUGGING = 2 
DEBUGGING_FILE = /var/log/snmptt/snmptt.debug 

Save the file and restart snmptt

Code: Select all

service snmptt restart

Send the test trap again.

Post the debug log: /var/log/snmptt/snmptt.debug here.

Debug file attached.

[Box293]

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?