Technical Tip: How to solve SNMP 'Error OID not increasing'

[aneshcheret]

Description
This  article describes how to solve SNMPwalk errors as the one below:

Error: OID not increasing

This error is caused by interface snmp-index duplicates. This occurs when SNMP indexes in the configuration are not auto-corrected (duplicate indexes). This can only occur when the configuration file was manually modified with a text editor, which is not a supported method for modifying the configuration.
Solution
Using SNMP walk tools some times can show the error:

#snmpwalk -v2c -cC -c infoAMT 10.7.19.132

.

.

.

.

.

iso.3.6.1.2.1.2.2.1.1.1 = INTEGER: 1

iso.3.6.1.2.1.2.2.1.1.4 = INTEGER: 4

iso.3.6.1.2.1.2.2.1.1.7 = INTEGER: 7

iso.3.6.1.2.1.2.2.1.1.8 = INTEGER: 8 ------------- Value X

iso.3.6.1.2.1.2.2.1.1.8 = INTEGER: 8 ------------- Value X

Error: OID not increasing: iso.3.6.1.2.1.2.2.1.1.8

>= iso.3.6.1.2.1.2.2.1.1.8

This error means the SNMP index is not increasing. The last value represents the SNMP-Index Interface. These loops occur when SNMP indexes in the configuration are not auto-corrected (duplicate indexes). 

Example:

#config system interface

#edit "port1"

#set snmp-index 1 ---- INDEX

#edit "port2"

#set snmp-index 8 ---- INDEX

#Port1 and port2 has the same index

Solution:

Edit the interfaces and change SNMP-Index value. In this case the administrator needs to edit these interfaces and configure different Indexes:

#config system interface

#edit port2

#set snmp-index 2 ---- New Index value 2

#end

#config system interface

#edit port7

#set snmp-index 3 ---- New Index value 3

#end