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

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

book

Article ID: 34356

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

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
 

 

Environment

Release: CNMSPP99000-8.4-Unified Infrastructure Mgmt-Server Pack-- On Prem
Component:

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