Cisco MDS-9124 Troubleshooting Guide - Page 111

Chapter 4 Troubleshooting Hardware Troubleshooting Supervisor Issues Send documentation comments to [email protected] Active Supervisor Reboots Symptom Active supervisor reboots. Table 4-7 Active Supervisor Reboots Symptom Active supervisor reboots. Possible Cause Solution Supervisor process crashed, resulting in a supervisor reload. 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 4-7.) Use the show process log CLI command to view a list of process restarts. Runtime diagnostics failure detected. Use the show module internal exceptionlog CLI command on the standby supervisor to view the cause of the reset after the supervisor reboots. (See Example 4-8.) 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 2-13. Example 4-6 displays the reason for the recent when a supervisor module reboots after a process crash. Example 4-6 Reset Reason for Supervisor Reboot Caused by Failed Process switch# show system reset-reason ----- reset reason for module 6 ----1) At 94009 usecs after Tue Sep 27 18:52:13 2005 Reason: Reset triggered due to HA policy of Reset Service: Service "xbar Process that caused the reboot Version: 2.1(2) Example 4-7 displays the system messages on the standby supervisor when a supervisor reboots after a process crash. Example 4-7 System Messages for Supervisor Reboot Caused by Failed Process 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 Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x 4-15