Loading...
Loading...
When SNMP creates a packet to notify of a Dying Gasp event high CPU triggers which results into a CPUHOG message.
This symptom is observed when SNMP is configured in a Customer Premise Equipment (CPE) and a power loss or a low power event occurs.
Disable SNMP
TAC assistance is required in order to identify if the device is affected by this bug. The device throws CPUHOG logs which need to be decoded in order to match the bug: %SYS-3-CPUHOG: Task is running for (2832)msecs, more than (2000)msecs (43/43),process = DHCPD Receive. -Traceback= 1#cf0e82598cc863255666812cb8b054d6 :10000000+12CE138 %SYS-3-CPUHOG: Task is running for (3824)msecs, more than (2000)msecs (43/43),process = DHCPD Receive. -Traceback= 1#cf0e82598cc863255666812cb8b054d6 :10000000+4AE7780 :10000000+4AE776C :10000000+4AE7CC0 :10000000+4AE87F4 :10000000+80E3AC :10000000+811F5C :10000000+1715E3C :10000000+11463A8 :10000000+114888C :10000000+1148C7C :10000000+1149B0C :10000000+1149EC0 :10000000+114AA48 :10000000+2EB7740 Dying Gasp documentation for IOS-XE: https://www.cisco.com/c/en/us/td/docs/routers/access/4400/software/configuration/xe-16-11/isr4400swcfg-xe-16-11-book/m-dying_gasp.html
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.