Trailing .0 on the End of the Var Binds in SNMP Traps in 1.21 and 1.22 snmpgtw

Document ID : KB000034356
Last Modified Date : 14/02/2018
Show Technical Document Details

Symptoms:

Traps are not recognized and there is an unexpected trailing .0 on the End of the OID in version 1.07 to 1.31 of the snmpgtw probe.

 

Environment: 

Any environment that is using the probe snmpgtw version from 1.07 to 1.31.

 

Cause:

Traps is not recognized

Looking at the Nimsoft published mib definition there appears to be a .0 append to the end of every trap varbind that is sent from either version 1.21 or 1.22 of this probe.

The MIB states:

nimsoft OBJECT IDENTIFIER ::= { enterprises 4055 }
sysadm OBJECT IDENTIFIER ::= { nimsoft 1 }
alarm OBJECT IDENTIFIER ::= { sysadm 1

and for example the alarm desc:

alarmDescr OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The alarmDescr object type is used to give a
textual description of a NimBUS alarm."
::= { alarm 3

This means that the oid should be enterprises.4055.1.1.3 yet it comes through as - enterprises.4055.1.1.3.0

Example trap (repost this is my message text) :

Dec 29 2011 10:27:00 * [default] 10.129.177.147:57586/0.0.0.0 public 'enterprises.4055.1.1.1.0' = '0' 'enterprises.4055.1.1.10.0' = '1325175071' 'enterprises.4055.1.1.11.0' = '21600' 'enterprises.4055.1.1.12.0' = 'XP72562497-32730' 'enterprises.4055.1.1.13.0' = 'co-ps-nms-a06' 'enterprises.4055.1.1.14.0' = 'CPS' 'enterprises.4055.1.1.3.0' = 'repost this6' 'enterprises.4055.1.1.4.0' = '' 'enterprises.4055.1.1.5.0' = 'nas' 'enterprises.4055.1.1.8.0' = 'CPS_PrimaryHub' 'enterprises.4055.1.1.9.0' = 'ChrisisnotaRookie' 'snmpTrapOID.0' = 'enterprises.4055.1.1.0.2' 'sysDescr.0' = 'NimBUS/SNMP gateway' 'sysUpTime.0' = '0'

From tcpdump - so you know this is coming from Nimsoft:

10:29:49.415616 h-CPSco-ps-nms-a06.57587 > 10.129.177.130.snmptrap: [udp sum ok] |30|82|01|61|02|01{ SNMPv1 |04|06|a4|82|01|52{ Trap(338) |06|09E:4055.1.1 |40|040.0.0.0|02|01 enterpriseSpecific|02|01[specific-trap(2)!=0] |43|010|30|82|01|34 |30|1f|06|08system.sysDescr.0=|04|13"NimBUS/SNMP gateway" |30|10|06|0bE:4055.1.1.1.0=|02|010 |30|1b|06|0bE:4055.1.1.3.0=|04|0c"repost this7" |30|0f|06|0bE:4055.1.1.4.0=|04|00"" |30|12|06|0bE:4055.1.1.5.0=|04|03"nas" |30|1d|06|0bE:4055.1.1.8.0=|04|0e"CPS_PrimaryHub" |30|20|06|0bE:4055.1.1.9.0=|04|11"ChrisisnotaRookie" |30|13|06|0bE:4055.1.1.10.0=|02|041325175071 |30|14|06|0bE:4055.1.1.11.0=|04|05"21600" |30|1f|06|0bE:4055.1.1.12.0=|04|10"XP72562497-32730" |30|1c|06|0bE:4055.1.1.13.0=|04|0d"co-ps-nms-a06" |30|12|06|0bE:4055.1.1.14.0=|04|03"CPS"} } (ttl 128, id 19769, len 385

TCP dump command

tcpdump -vvv -s 0 -i any 'host 10.129.177.147 and port 162'

 

Resolution:

Upgrade to snmpgtw version 1.32 or above.

 

Fixed the issue of trailing .0 at the end of the Variable Binds in SNMP Traps generated by the probe