19.14 Configuring NNMi to preserve a previously supported varbind order

All SNMPv2 traps contain the two OIDs sysUpTime.0 and snmpTrapOID.0 as the first and seconds varbinds. The varbind position in a varbind list means an OID is positioned in the list according to the SNMPv2 specification. If an OID is used as a trap parameter, it means that the OID is listed in a specific MIB. If an SNMPv2 trap definition contains sysUpTime.0 or snmpTrapOID.0 as trap parameters, they might appear as additional varbinds in positions other than first and second in the varbind list.

Prior to NNMi 10-10, NNMi removed all instances of the sysUpTime.0 and snmpTrapOID.0 OIDs from the varbind list. Starting with NNMi 10-10, NNMi retains these OIDs when they are part of the trap definition, but they might appear in positions other than first and second in the varbind list of received trap. This change in positioning might alter the varbind order for those traps that have either sysUpTime.0 or snmpTrapOID.0 as trap parameters.

For example, suppose NNMi receives a trap with the varbinds positioned as follows:

Varbind 1: .1.3.6.1.2.1.1.3.0 (sysUpTime)
Varbind 2: .1.3.6.1.6.3.1.1.4.1.0 (snmpTrapOID)
Varbind 3: .1.3.6.1.2.1.2.2.1.1.92
Varbind 4: .1.3.6.1.4.1.11.2.17.20.20.1
Varbind 5: .1.3.6.1.4.1.11.2.17.20.20.2
Varbind 6: .1.3.6.1.4.1.11.2.17.20.20.3
Varbind 7: .1.3.6.1.4.1.11.2.17.20.20.4
Varbind 8: .1.3.6.1.2.1.1.3.0 (sysUpTime)
Varbind 9: .1.3.6.1.6.3.1.1.4.1.0 (snmpTrapOID)
Varbind 10: .1.3.6.1.4.1.11.2.17.20.20.3
Varbind 11: .1.3.6.1.4.1.11.2.17.20.20.4

Prior to NNMi 10-10, NNMi would remove all of the sysUpTime and snmpTrapOID varbinds (underlined) in both trap 1 and trap 2, as shown below:

Varbind 1: .1.3.6.1.2.1.1.3.0 (sysUpTime)
Varbind 2: .1.3.6.1.6.3.1.1.4.1.0 (snmpTrapOID)
Varbind 3: .1.3.6.1.2.1.2.2.1.1.92
Varbind 4: .1.3.6.1.4.1.11.2.17.20.20.1
Varbind 5: .1.3.6.1.4.1.11.2.17.20.20.2
Varbind 6: .1.3.6.1.4.1.11.2.17.20.20.3
Varbind 7: .1.3.6.1.4.1.11.2.17.20.20.4
Varbind 8: .1.3.6.1.2.1.1.3.0 (sysUpTime)
Varbind 9: .1.3.6.1.6.3.1.1.4.1.0 (snmpTrapOID)
Varbind 10: .1.3.6.1.4.1.11.2.17.20.20.3
Varbind 11: .1.3.6.1.4.1.11.2.17.20.20.4

Beginning with NNMi 10-10, NNMi retains the sysUpTime and snmpTrapOID varbinds that do not reside in the first and second varbind positions (underlined) as shown below:

Varbind 1: .1.3.6.1.2.1.1.3.0 (sysUpTime)
Varbind 2: .1.3.6.1.6.3.1.1.4.1.0 (snmpTrapOID)
Varbind 3: .1.3.6.1.2.1.2.2.1.1.92
Varbind 4: .1.3.6.1.4.1.11.2.17.20.20.1
Varbind 5: .1.3.6.1.4.1.11.2.17.20.20.2
Varbind 6: .1.3.6.1.4.1.11.2.17.20.20.3
Varbind 7: .1.3.6.1.4.1.11.2.17.20.20.4
Varbind 8: .1.3.6.1.2.1.1.3.0 (sysUpTime)
Varbind 9: .1.3.6.1.6.3.1.1.4.1.0 (snmpTrapOID)
Varbind 10: .1.3.6.1.4.1.11.2.17.20.20.3
Varbind 11: .1.3.6.1.4.1.11.2.17.20.20.4

Set the com.hp.nnm.events.preserveOldVarbindListOrder property to true only if you need to retain the NNMi behavior that existed prior to installing NNMi 10-10.

To retain the NNMi behavior that existed prior to installing NNMi 10-10, do the following:

Edit the following file:
- Windows: %NNM_PROPS%\nms-jboss.properties
- UNIX: $NNM_PROPS/nms-jboss.properties
Search for the text block containing the following line:
```
#!com.hp.nnm.events.preserveOldvarbindListOrder=false
```

Uncomment and edit this line to read as follows:

com.hp.nnm.events.preserveOldvarbindListOrder=true

Save your changes.
Restart NNMi:

a. Run the ovstop command on the NNMi management server.

b. Run the ovstart command on the NNMi management server.

To Page Top