Technical FAQs

Ask a Question

What type of information can I see in a NetBotz SNMP trap?

Issue:

Information found in a NetBotz SNMP trap

Product Line:

StruxureWare Data Center Expert
NetBotz

Environment:

StruxureWare Data Center Expert trap alarm action.
NetBotz SNMP trap

Cause:

SNMP traps from a NetBotz device are a nested trap. This is the same when configuring traps for StruxureWare Data Center Expert (DCE) using the alarm action configuration for a trap. The NMS integration feature is a similar trap configuration but it is based on APC OIDS rather than the NetBotz OIDs. This information is available in document ID FA231439. 



Resolution:

‚ÄčThere are multiple bindings or arguments within the trap. This article is designed to provide some information about what you may see in the trap output.
In this example, we have created an SNMP alert and associated it with a spot leak sensor. The following is the output you will see when there is a leak detected by that sensor:

Trap start: 
Trap Type: V1, V1TRAP
security level: No authenticaion and No Privacy
trap address: 10.218.45.53
community: public
VarBinding 1: 1.3.6.1.4.1.5528.100.11.1 = nbErrorCond_69F2B308
VarBinding 2: 1.3.6.1.4.1.5528.100.11.2 = nbErrorType_errorstate
VarBinding 3: 1.3.6.1.4.1.5528.100.11.3 = Value Error
VarBinding 4: 1.3.6.1.4.1.5528.100.11.4 = nbAlinkEnc_0_3_SPLK
VarBinding 7: 1.3.6.1.4.1.5528.100.11.5 = Spot leak  (Test)
VarBinding 5: 1.3.6.1.4.1.5528.100.11.6 = nbAlinkEnc_0
VarBinding 6: 1.3.6.1.4.1.5528.100.11.7 = Sensor Pod
VarBinding 8: 1.3.6.1.4.1.5528.100.11.8 = 
VarBinding 9: 1.3.6.1.4.1.5528.100.11.9 = 
VarBinding 10: 1.3.6.1.4.1.5528.100.11.10 = 1416430265
VarBinding 11: 1.3.6.1.4.1.5528.100.11.11 = 1416430265
VarBinding 12: 1.3.6.1.4.1.5528.100.11.12 = 0
VarBinding 13: 1.3.6.1.4.1.5528.100.11.13 = 2
VarBinding 14: 1.3.6.1.4.1.5528.100.11.14 = Leak Detected
VarBinding 15: 1.3.6.1.4.1.5528.100.11.15 = 1
VarBinding 16: 1.3.6.1.4.1.5528.100.11.16 = 0
Trap end: 

When you look at the NetBotz MIB, you will also find that the trap parameters are listed under:
iso.org.dod.internet.private.enterprises.netBotzAPC.NetBotz.netBotzTrapParms
or 
.1.3.6.1.4.1.5528.100.11

The information listed above directly correlates to the information in the MIB.
netBotzTrapParms.netBotzTrapErrorID
.1.3.6.1.4.1.5528.100.11.1

netBotzTrapParms.netBotzTrapErrorType
.1.3.6.1.4.1.5528.100.11.2

netBotzTrapParms.netBotzTrapErrorTypeLabel
.1.3.6.1.4.1.5528.100.11.3

netBotzTrapParms.netBotzTrapSensorID
.1.3.6.1.4.1.5528.100.11.4

netBotzTrapParms.netBotzTrapSensorLabel
.1.3.6.1.4.1.5528.100.11.5

netBotzTrapParms.netBotzTrapPodID
.1.3.6.1.4.1.5528.100.11.6

netBotzTrapParms.netBotzTrapPodLabel
.1.3.6.1.4.1.5528.100.11.7

netBotzTrapParms.netBotzTrapPortID
.1.3.6.1.4.1.5528.100.11.8

netBotzTrapParms.netBotzTrapPortLabel
.1.3.6.1.4.1.5528.100.11.9

netBotzTrapParms.netBotzTrapStartTime
.1.3.6.1.4.1.5528.100.11.10

netBotzTrapParms.netBotzTrapNotifyTime
.1.3.6.1.4.1.5528.100.11.11

netBotzTrapParms.netBotzTrapResolveTime
.1.3.6.1.4.1.5528.100.11.12

netBotzTrapParms.netBotzTrapSeverity
.1.3.6.1.4.1.5528.100.11.13

netBotzTrapParms.netBotzTrapSensorValue
.1.3.6.1.4.1.5528.100.11.14

netBotzTrapParms.netBotzTrapSensorValueInt
.1.3.6.1.4.1.5528.100.11.15

netBotzTrapParms.netBotzTrapSensorValueFraction
.1.3.6.1.4.1.5528.100.11.16

Please note that you NMS or trap receiver must support this type of nested trap in order to get this information from the NetBotz appliance. 
 
Was this helpful?
What can we do to improve the information ?