Active Supervisor Reboots - Cisco 9134 - MDS Multilayer Fabric Switch Troubleshooting Manual

Chapter 4 Troubleshooting Hardware
S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m

Active Supervisor Reboots

Symptom
Table 4-7 Active Supervisor Reboots
Symptom Possible Cause
Active supervisor Supervisor process crashed, resulting in a
reboots. supervisor reload.
Runtime diagnostics failure detected.
Example 4-6
Example 4-6
switch# show system reset-reason
----- reset reason for module 6 -----
1) At 94009 usecs after Tue Sep 27 18:52:13 2005
Example 4-7
process crash.
Example 4-7
Switch# show logging
2005 Sep 27 18:58:05 172.20.150.204 %SYSMGR-3-SERVICE_CRASHED: Service "xbar" (PID 1225)
hasn't caught signal 9 (no core).
2005 Sep 27 18:58:06 172.20.150.204 %SYSMGR-3-SERVICE_CRASHED: Service "xbar" (PID 2349)
hasn't caught signal 9 (no core).
2005 Sep 27 18:58:06 172.20.150.204 %SYSMGR-3-SERVICE_CRASHED: Service "xbar" (PID 2352)
hasn't caught signal 9 (no core).
OL-9285-05
Active supervisor reboots.
displays the reason for the recent when a supervisor module reboots after a process crash.
Reset Reason for Supervisor Reboot Caused by Failed Process
Reason: Reset triggered due to HA policy of Reset
Service: Service "xbar" <------------------ Process that caused the reboot
Version: 2.1(2)
displays the system messages on the standby supervisor when a supervisor reboots after a
System Messages for Supervisor Reboot Caused by Failed Process
Solution
Use the show system reset-reason CLI command to
view the cause of the reset after the supervisor reboots.
(See Example 4-6.) If you have a standby supervisor, the
standby is now the active supervisor. Display the system
message log on the standby supervisor to see the same
information. (See Example
Use the show process log CLI command to view a list of
process restarts.
Use the show module internal exceptionlog CLI
command on the standby supervisor to view the cause of
the reset after the supervisor reboots. (See
If you have a standby supervisor, the standby is now the
active supervisor. Display the system message log on the
standby supervisor to see the same information. See
(Example 4-9.) Optionally, when the supervisor reboots,
use the show system reset-reason CLI command to view
this same information.
See also the "Troubleshooting Cisco SAN-OS Software
System Reboots" section on page
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
Troubleshooting Supervisor Issues
4-7.)
Example 4-8.)
2-13.
4-15