SNMP Trap Viewer - OID GUI drill down vs Add Rule creating different snmpTrapOID

mlan

Hey all,

I ran into a confusing issue with the SNMP Trap Viewer/Alert Rules.  I am running NPM 10.2.2.  We were troubleshooting why an existing alert rule for APC "upsOnBattery" (1.3.6.1.4.1.318.5) was not functioning correctly (not matching the rule and failing to send a notification email).  We were not sure when this started happening, but we have recently upgraded from 10.1.1 to 10.2.1, along with a server migration, and another upgrade to 10.2.2.

We are seeing the traps come in to the Trap Viewer with the displayed snmpTrapOID of:

snmpTrapOID=PowerNet-MIB:apc.0.5

However, the existing rule was set to match on this snmpTrapOID:

snmpTrapOID=PowerNet-MIB:upsOnBattery

We found that if you create the match condition using the GUI (drilling down to 1.3.6.1.4.1.318.5), then the match rule is created with the snmpTrapOID of "PowerNet-MIB:upsOnBattery".  However, if you right-click the received trap and "create rule" it uses the correct snmpTrapOID of "PowerNet-MIB:apc.0.5", which matches correctly.

Is this a bug, or am I missing something (regarding my MIB database)?

Thanks.

mdriskell

I would start by updating the MIB database (perhaps when you upgraded it was packaged with an older DB) if that doens't work then a support case would be needed to identify.

From my understanding utilizing the RAW OID will always work whereas the named format only works if it can be decoded properly in the MIB table.