Why are NetBotz traps showing variables out of order?

Issue:

Incorrect OID and order for varbind in SNMP trap

Product Line:

NetBotz

Environment:

Botzware 4.4.0, 4.4.1

Cause:

Due to a change in the SNMP code, an unexpected issue has occurred where variable bindings for certain traps may be out of order.
This should read:
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 =

Instead, as is the case with the spot leak sensor tested here, the varbinds are returned as follows:
VarBinding 4: 1.3.6.1.4.1.5528.100.11.4 = nbAlinkEnc_0_3_SPLK
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 7: 1.3.6.1.4.1.5528.100.11.7 = Spot leak (Test)
VarBinding 8: 1.3.6.1.4.1.5528.100.11.8 =

Note that there is no varbind 5 which should be:
netBotzTrapParms.netBotzTrapSensorLabel
.1.3.6.1.4.1.5528.100.11.5

Instead, the trap puts them out of order as shown in the example above as well as sending them with an invalid OID as .100.11.7 is sent twice with different variables.

Resolution:

Botzware 4.5 has addressed this issue and is due out in the May-June 2015 timeframe. Please note that Botzware release dates are subject to change.