Cisco Catalyst 4000 series Hardware Troubleshoot page 16

♦
Messages and Recovery Procedures
♦
Common CatOS Error Messages on Catalyst 4000 Series Switches
Supervisor Crashes and Steps to Resolve Them
Supervisor crashes occur when the switch has reset, continually resets, or is down completely.
These commands are supported by the Output Interpreter and can be used to assist in troubleshooting
supervisor crashes: show version or show system.
If you have the output of the supported commands from your Cisco device, you can use Output Interpreter
(registered customers only) in order to display potential issues and fixes. In order to use Output Interpreter
(registered customers only) , you must be a registered user, be logged in, and have JavaScript enabled.
Getting system error messages
System error messages can be useful if you experience a switch reset. See the Getting system error messages
section for more information.
Switch has reset or is continually resetting
If the switch has reset or crashed due to a reason related to hardware or software, it is important to capture the
output of certain show commands as quickly as possible.
1. Capture the show log, show version, show test 0,and show logging buffer 1023 command output.
The show log command output has a number of important indications of problems that can be related
to a crash.
♦
It keeps track of the last ten system resets with timestamps that show when the reboot
occurred. This is a snapshot of the Reboot History output:
The Reboot History only indicates that the switch was reset. It can have been reset manually
by the user or due to a crash. But, the most recent manual reset of the switch is recorded
further down in the output.
Notice that the timestamp of the last manual reset, 1/23/2002,11:13:13, matches the most
recent entry in the Reboot History.
♦
It shows if there have been any exceptions. Exceptions are CPU dumps that occur
immediately after a crash. For example:
In this case, there were no exceptions recorded. If there were an exception, it includes a
timestamp that can be matched with the Reboot History, and also includes a HEX dump or
stack, which can be decoded by a TAC engineer in order to determine whether this was a
software forced exception or due to hardware.
Reboot History: Jan 23 2002 11:14:16 0, Jan 22 2002 14:57:21 0
Last software reset by user: Jan 23 2002 11:14:16 0
MCP Exceptions/Hang:
DEC 24 2001 13:56:38 0, DEC 24 2001 13:52:30 0
DEC 11 2001 12:31:59 0, DEC 07 2001 13:26:48 0
DEC 07 2001 10:42:19 0, DEC 07 2001 10:36:16 0
Nov 28 2001 11:03:10 0, Oct 26 2001 16:04:26 0
0