Last Modified: Jul 18, 2026
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.5.1, 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, 11.5.2 hf1, 11.5.3, 11.5.3 hf1, 11.5.3 hf2, 11.5.4, 11.5.4 hf1, 11.5.4 hf2, 11.5.4 hf3, 11.5.4 hf4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3
Fixed In:
12.0.0
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.