Cisco IE-3000-8TC

39-18
Cisco IE 3000 Switch Software Configuration Guide
OL-13018-03
Chapter 39 Troubleshooting
Troubleshooting Tables
You can display the most recent basic crashinfo file (that is, the file with the highest sequence number
at the end of its filename) by entering the show tech-support privileged EXEC command. You also can
access the file by using any command that can copy or display files, such as the more or the copy
privileged EXEC command.
Extended crashinfo Files
The switch creates the extended crashinfo file when the system is failing. The information in the
extended file includes additional information that can help determine the cause of the switch failure. You
provide this information to the Cisco technical support representative by manually accessing the file and
using the more or the copy privileged EXEC command.
Extended crashinfo files are kept in this directory on the flash file system:
flash:/crashinfo_ext/.
The filenames are crashinfo_ext_n where n is a sequence number.
You can configure the switch to not create the extended creashinfo file by using the no exception
crashinfo global configuration command.
Troubleshooting Tables
These tables are a condensed version of troubleshooting documents on Cisco.com.
• “Troubleshooting CPU Utilization” on page -18
Troubleshooting CPU Utilization
This section lists some possible symptoms that could be caused by the CPU being too busy and shows
how to verify a CPU utilization problem.
Table 39-3 lists the primary types of CPU utilization problems
that you can identify. It gives possible causes and corrective action with links to the Troubleshooting
High CPU Utilization document on Cisco.com.
Possible Symptoms of High CPU Utilization
Note that excessive CPU utilization might result in these symptoms, but the symptoms could also result
from other causes.
• Spanning tree topology changes
• EtherChannel links brought down due to loss of communication
• Failure to respond to management requests (ICMP ping, SNMP timeouts, slow Telnet or SSH
sessions)
• UDLD flapping
• IP SLAs failures because of SLAs responses beyond an acceptable threshold
• DHCP or IEEE 802.1x failures if the switch does not forward or respond to requests
Layer 3 switches:
• Dropped packets or increased latency for packets routed in software