I copied this output from the output interpreter on Cisco'c website:
==========================================================================
SHOW PROCESS CPU NOTIFICATIONS (if any)
==========================================================================
INFO: Total CPU Utilization is comprised of process and interrupt percentages.
Total CPU Utilization: 94%
Process Utilization: 94%
Interrupt Utilization: 0%
These values are found on the first line of the output:
CPU utilization for five seconds: x%/y%; one minute: a%; five minutes: b%
Total CPU Utilization: x%
Process Utilization: (x - y)%
Interrupt Utilization: y%
Process Utilization is the difference between the Total and Interrupt (x and y).
The one and five minute utilizations are exponentially decayed averages (rather
than an arithmetic average), therefore recent values have more influence on the
calculated average.
ERROR: Total CPU Utilization is at 94% for the past 5 seconds, which is very high (>90%).
This can cause the following symptoms:
- Input queue drops
- Slow performance
- Slow response in Telnet or unable to Telnet to the router
- Slow response on the console
- Slow or no response to ping
- Router doesn't send routing updates
The following processes are causing excessive CPU usage:
PID CPU Time Process
19 47.87% EMANATE SUBAGENT
37 10.15% Virtual Exec
INFO: The virtual EXEC process handles virtual type terminal (vty) lines,
such as Telnet sessions on the router. Issuing commands that generate long
output (such as 'show tech-support'), or if the debug output has been redirected
to the vty (using the terminal monitor or the no logging console command), the
amount of CPU resources used by the virtual EXEC process increases.
TRY THIS: If there is no indication of any problem in logged messages, then the
problem could possibly be caused by a bug in the IOS. Using the Bug Navigator,
run a search for the specified process to see if any bugs have been reported.
If this is not caused by a bug, this device may be overloaded. Investigate
upgrading this device or moving some CPU intensive tasks to a second device.
INFO: If you need help from a Customer Support Engineer in the Cisco TAC,
capture the 'show tech-support' command output (from enable mode) before
contacting Cisco TAC. Also, if the high CPU utilization is caused by a process,
please capture the 'show stacks {pid}' command output (where pid is the process
ID of the process causing the high CPU utilization). If the problem is caused by
a bug in IOS, please relay the bug ID to the Cisco Customer Support Engineer
handling the case.
REFERENCE: For troubleshooting information, please visit Troubleshooting High CPU Utilization on Cisco Routers
WARNING: 77.04% of CPU Utilization is from process switching.
Process switching is the most basic way of handling a packet.
TRY THIS: Consider another form of switching:
- Fast switching, using the 'ip route-cache' command
- Same-interface switching, using the 'ip route-cache same-interface' command
- Autonomous switching (7000 platforms only), using the 'ip route-cache cbus'
command
- Silicon switching (7000 platforms with an SSP installed only), using the
'ip route-cache sse' command
- Distributed switching (VIP-capable platforms only), using the 'ip route-cache
distributed' command
- Optimum switching (high-end routers only), using the 'ip route-cache optimum'
command
- Netflow switching, using the 'ip route-cache flow' command
- Cisco Express Forwarding (CEF), using the 'ip cef' command
- Distributed CEF, using the 'ip cef distributed' command
NOTE: When TCP Intercept is enabled process switching is required for all
packets during session set-up.
REFERENCE: For more information see Performance Tuning Basics
You have to be registered on their website to use it, please let me know whether this helps?
