Ask a Question

Netbotz version 3.x OID data returned by SNMP GET or WALK arrives in a different order than in previous versions of Botzware.

Issue:

Netbotz version 3.x OID data returned by SNMP GET or WALK arrives in a different order than in previous versions of Botzware.

Product Line:

NetBotz

Environment:

NetBotz version 3 SNMP

Cause:

This Affects customers who use custom SNMP clients that sort OID data by predetermined index values.

Prior to Botzware 3.1, the device's SNMP agent maintained OID data in a way that caused some OID data to be skipped prior to sending data back to the client. So even though an OID's element existed and was active on the target device, its data may never be captured by an SNMP GET or WALK query, because the OID data would be simply overlooked.

Resolution:

Botzware starting with 3.1 uses a different scheme to internally track OID data. While this resolves the problem seen in previous versions, the order in which multiple OID data is returned for an SNMP WALK query now differs from previous Botzware versions. For anyone using a fixed-indexed scheme to associate the assumed arrival order of OID data to an index value at the client, incorrect sorting at the client may occur.

Custom SNMP clients using predetermined index values to sort OID data will need to be reworked to be aware of the returned OID index value and its variable's instance for each OID.