Send documentation comments to mdsfeedback-doc@cisco.com
4-13
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 4 Troubleshooting Hardware
Troubleshooting Other Hardware Issues
Typically, clock module A is the active clock. On a failure of clock module A, clock module B becomes
the active clock. Refer to the hardware installation guide for your platform at the following website to
replace a clock module.
http://www.cisco.com/en/US/products/hw/ps4159/ps4358/prod_installation_guides_list.html
Troubleshooting Other Hardware Issues
Note To issue commands with the internal keyword, you must have an account that is a member of the
network-admin group.
To identify a hardware issue with a module using the CLI, follow these steps:
Step 1 Use the show module internal exceptionlog command.
The exception log is a wraparound log of all errors and exceptional conditions on each module. Some
exceptions are catastrophic, some partially affect certain ports in a module, and others are for warning
purposes. Each log entry includes the following fields:
• device id—The device that logged the exception. This is interpreted by your customer support
representative.
• device errorcode—The error code that occurred on the device. This is interpreted by your customer
support representative.
• error type—The severity level of the error. Software errors are typically minor or warning. All other
errors may be hardware problems.
• Number Ports that failed—The number of ports on the module that are no longer operational.
• system time— The timestamp when the problem occurred.
The exception log is stored in the NVRAM on the supervisor module.
Most hardware errors are logged in this command output. If the error type field indicates anything other
than minor or warning error, then it is most likely a hardware failure. (See Example 4-5.)
Example 4-5 Output of show module internal exceptionlog Command
switch# show module internal exceptionlog
********* Exception info for module 6 ********
exception information --- exception instance 1 ----
device id: 85
device errorcode: 0xc550120c
system time: (1127748710 ticks) Mon Sep 26 15:31:50 2005
error type: Minor error
Number Ports went bad: none
********* Exception info for module 8 ******** <---Possible failed module
exception information --- exception instance 1 ----
device id: 12
device errorcode: 0x80000080
system time: (1127843531 ticks) Tue Sep 27 17:52:11 2005
error type: FATAL error <------------------- Error Type field
To Next Page
Loading...
Need help?
General