Send documentation comments to mdsfeedback-doc@cisco.com
4-14
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 4 Troubleshooting Hardware
Troubleshooting Supervisor Issues
Number Ports went bad:
1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16
Step 2 View the error statistics from the show hardware internal errors command output.
Some error statistics reported under FC-MAC are not necessarily errors, but those counters normally
do not increment for a port that is in an operational state.
Step 3 View the interrupt counts in the show hardware internal errors command output.
Note the following:
• Some interrupts are not necessarily error interrupts.
• Some interrupts have a threshold before the corresponding ports are declared as faulty. Do not
conclude that the hardware is faulty because of some interrupt counts. However, these commands
are useful for your customer support representative when debugging the problems.
• Some interrupt counts may show up under UP-XBAR and DOWN-XBAR ASICs, when one of
Supervisors is pulled out or restarted.
Troubleshooting Supervisor Issues
Supervisor initiation varies depending on whether or not you have a redundant supervisor present. When
two supervisors are present in the system at poweredup, one of the supervisors will become active and
the other standby. The active supervisor initialization differs from the standby supervisor.
If there is no active supervisor in the system, the supervisor that boots up first will default to the active
supervisor. If there is an active supervisor in the system, the supervisor that is booting up will default to
the standby supervisor state. The standby supervisor needs to mirror the state of the active supervisor.
After all components on the standby are synchronized with those of the active supervisor, the standby
supervisor is up.
Cisco SAN-OS maintains debug information during runtime. When a supervisor reboots, much of the
debug information is lost. However, all critical information is stored in NVRAM and can be used to
reconstruct the failure. When an active supervisor reboots, the information that is stored in its NVRAM
cannot be obtained until it comes back up again. Once the supervisor reboots, use the following CLI
commands to view the persistent log:
• show logging nvram
• show system reset-reason
• show module internal exception-log
This section describes how to diagnose when an active or standby supervisor fails to initialize properly.
This section includes the following topics:
• Active Supervisor Reboots, page 4-15
• Standby Supervisor Not Recognized by Active Supervisor, page 4-17
• Standby Supervisor Stays in Powered-Up State, page 4-19
To Next Page
Loading...
Need help?
General