%SYS-3-CPUHOG: Task is running for ([dec])msecs, more than ([dec])msecs ([dec]/[dec]),process = [chars].[chars]
The indicated process ran too long without relinquishing the processor. Each process should run for a small amount of time and then relinquish the CPU so other processes can run. This problem can be caused by many things like traffic or system load, hardware or operational configuration, a configuration change, initialization (of many interfaces, cards or ports for example), a high momentary error rate, a sustained abnormal condition or many other conditions.
And when i decode i got for following information:-
%SYS-3-CPUHOG: Task ran for [dec] msec ([dec]/[dec]), process = [chars], PC
Explanation: Every process that runs must relinquish the processor after a certain
period so that other processes can run. 'CPUHOG' is an informational message that
occurs when a certain process holds the CPU for 2000 msec or longer. This problem
can occur due to one or more of these conditions:
Improper operational configuration
Initialization of many interfaces
High momentary error rate
Sustained abnormal condition
Software bug in the IOS during normal operation.
Recommended Action: If communication is fine, and no other messages are displayed
before this message, you can ignore the CPUHOG message. If another error message
appears along with this message, decode the other error message using the Error
Message Decoder tool. If the CPU usage is high because of IP input process, then
the router is process-switching a lot of IP traffic. Enable CEF to lower the CPU
usage by this process. Review the Bug Toolkit for potential issues related to
STACK DECODE NOTIFICATIONS (if any)
Note: Understanding the 'Fixed In Version' field - Sometimes the fixed-in version
specified may not be available for download from the IOS Upgrade Planner. This
is because, bug fixes are incorporated into software versions which have not been
regression tested. These builds are called interim images and will have a "."
in the build number found between the parenthesis, for example 12.3(8.1). The bug
fix will be in the next available image, and all later images. So if a bug is fixed
in 12.3(8.1), the bug fix is present in 12.3(9), 12.3(10), and so on.
REFERENCE: For more information on how IOS images are named, see Cisco IOS Reference
The failure was caused by a software defect.
Also you see there is huge peak on the cpu status. anyways As suggested by amit you could probably think of upgrading IOS on the device.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...