OPERATIONAL DEFECT DATABASE
...
...
An IOS-XE based router running 3.13.6S-15.4(3)S6-, 3.16.2S-15.5(3)S2, or 3.17.1S-15.6(1)S1 may experience high CPU under the "SNMP" process when doing get-next to consistently get the value of "entStateStandby".
IOS-XE based routers running 3.13.6S-15.4(3)S6-, 3.16.2S-15.5(3)S2, or 3.17.1S-15.6(1)S1 Customers should upgrade to either: - 3.13.7S - 3.16.3S - 3.17.2S Or later. Affects devices configured with either SNMPv1, SNMPv2 or SNMPv3. This can occur on ASR1k or ISR4k
create a view to block the OID will not hep. Thus, there is no specific workaround to reduce the high cpu caused by snmp process. however, the recovery process is tricky so please read this carefully. Recovery Procedure : Perform warm restart (removing and re-adding SNMP server config) to reduce the CPU usage. you can use either command in below: 1. reload warm 2. Router(config)# warm-reboot count 10 uptime 10 note: the router will accept the "reload" command but it won't execute the "reload" right away due to snmp caused 100% CPU so IOS put the "reload" in pending and warning "reload in progress". the router will auto reload after removing snmp from running-config because CPU utils will drop immediately. If the device console is accessible, administrators can remove the SNMP configuration to allow the CPU to recover and allow for a device upgrade to a fixed release of the software. If the device console is not accessible, administrators can power cycle the device and either remove the SNMP configuration or prevent SNMP polling on the device to allow for a device upgrade to a fixed release of the software.
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
