Cisco Systems IE 2000 How to Troubleshoot

46-7
Cisco IE 2000 Switch Software Configuration Guide
OL-25866-01
Chapter 46 Troubleshooting
How to Troubleshoot
• For complete information about CPU utilization and how to troubleshoot utilization problems, see
the Troubleshooting High CPU Utilization document on Cisco.com.
How to Troubleshoot
Recovering from Software Failures
Switch software can be corrupted during an upgrade, by downloading the w rong file to the switch, and
by deleting the image file. In all of these cases, the switch does not pass the power-on self-test (POST),
and there is no connectivity.
This procedure uses the Xmodem Protocol to recover from a co rrupt or wrong image file. There are many
software packages that support the Xmodem Protocol, and this procedure is largely dependent on the
emulation software that you are using.
This recovery procedure requires that you have physical access to the switch.
Step 1 From your PC, download the software image tar file (image_filename.tar) from Cisco.com.
The Cisco IOS image is stored as a bin file in a directory in the tar file. For information about locating
the software image files on Cisco.com, see the release notes.
Step 2 Extract the bin file from the tar file.
• If you are using Windows, use a zip program that can read a tar file. Use the zip program to navigate
to and extract the bin file.
• If you are using UNIX, follow these steps:
1. Display the contents of the tar file by using the tar -tvf <image_filename.tar> UNIX command.
switch% tar -tvf image_filename.tar
2. Locate the bin file, and extract it by using the tar -xvf <image_filename.tar>
<image_filename.bin> UNIX command.
switch% tar -xvf image_filename.tar image_filename.binx
x image_name.bin, 3970586 bytes, 7756 tape blocks
3. Verify that the bin file was extracted by using the ls -l <image_filename.bin> UNIX command.
Tab l e 46-1 Troubleshooting CPU Utilization Problems
Type of Problem Cause Corrective Action
Interrupt percentage value is almost
as high as total CPU utilization value.
The CPU is receiving too many packets
from the network.
Determine the source of the network
packet. Stop the flow, or change the
switch configuration. See the section on
“Analyzing Network Traffic.”
Total CPU utilization is greater than
50% with minimal time spent on
interrupts.
One or more Cisco IOS process is
consuming too much CPU time. This is
usually triggered by an event that activated
the process.
Identify the unusual event, and
troubleshoot the root cause. See the
section on “Debugging Active
Processes.”