Verifying The Problem And Cause - Cisco IE-3000-8TC Software Configuration Manual

Chapter 39 Troubleshooting
•
•

Verifying the Problem and Cause

To determine if high CPU utilization is a problem, enter the show processes cpu sorted privileged
EXEC command. Note the underlined information in the first line of the output example.
This example shows normal CPU utilization. The output shows that utilization for the last 5 seconds is
8%/0%, which has this meaning:
•
•
\
Table 39-3 Troubleshooting CPU Utilization Problems
Type of Problem
Interrupt percentage value is almost
as high as total CPU utilization value.
Total CPU utilization is greater than
50% with minimal time spent on
interrupts.
For complete information about CPU utilization and how to troubleshoot utilization problems, see the
Troubleshooting High CPU Utilization
OL-13018-03
BGP or OSPF routing topology changes
HSRP flapping
Switch# show processes cpu sorted
CPU utilization for five seconds: 8%/0%; one minute: 7%; five minutes: 8%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
309 42289103 752750 56180 1.75% 1.20% 1.22% 0 RIP Timers
140 8820183 4942081 1784 0.63% 0.37% 0.30% 0 HRPC qos request
100 3427318 16150534 212 0.47% 0.14% 0.11% 0 HRPC pm-counters
192 3093252 14081112 219 0.31% 0.14% 0.11% 0 Spanning Tree
143 8 37 216 0.15% 0.01% 0.00% 0 Exec
...
<output truncated>
The total CPU utilization is 8 percent, including both time running Cisco IOS processes and time
spent handling interrupts
The time spent handling interrupts is zero percent.
Cause
The CPU is receiving too many packets
from the network.
One or more Cisco IOS process is
consuming too much CPU time. This is
usually triggered by an event that activated
the process.
Corrective Action
Determine the source of the network
packet. Stop the flow, or change the
switch configuration. See the section on
"Analyzing Network Traffic."
Identify the unusual event, and
troubleshoot the root cause. See the
section on
Processes."
document on Cisco.com.
Cisco IE 3000 Switch Software Configuration Guide
Troubleshooting Tables
"Debugging Active
39-19