Last Modified: Oct 17, 2023
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2
Fixed In:
12.0.0, 11.6.0 HF5
Opened: Jul 29, 2014 Severity: 4-Minor Related Article:
K16207
The following message when querying SNMP ipCidrRouteTable: 'Error: OID not increasing: IP-FORWARD-MIB::ipCidrRouteDest.172.27.96.0.255.255.255.0.0.0.0.0.0 >= IP-FORWARD-MIB::ipCidrRouteDest.172.27.96.0.255.255.255.0.0.0.0.0.0'. Also, querying specifically for ipCidrRouteAge OID under ipCidrRouteTable, can cause snmpd to core.
snmpwalk error and/or snmpd core.
This occurs when there are dual management routes in the default routing table, main. For example: # ip route show table main / ip route show ... 172.27.96.0/24 dev eth0 proto kernel scope link src 172.27.96.18 172.27.96.0/24 dev eth0 scope link src 172.27.96.18 metric 9 ...
Delete the duplicate route with metric 9: ip route del 172.27.96.0/24 dev eth0 scope link src 172.27.96.18 metric 9
snmpwalk now finishes successfully without 'OID not increasing' error, so snmpd no longer core.