HP Cisco Nexus 5000 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS R - Page 38

Director Switches, Fabric Switch and Blade Switches, show logging log, show system reset-reason

Page 38 highlights

Caveats Send documentation comments to [email protected] Director Switches The output of the show logging log command will have events like those shown below on director switches. In the following output, module 7 is the supervisor and module 12 is the module that reloaded. 2008 Jul 15 19:39:30 fcd95c41 %MODULE-4-MOD_WARNING: Module 7 (serial: JXXXXXXXXX) reported warnings on ports 7/1-7/3 (Unknown) due to BE2 Arbiter experienced an error in device 65 (device error 0xc410d613) 2008 Jul 15 19:39:30 fcd95c41 %MODULE-4-MOD_WARNING: Module 8 (serial: JXXXXXXXXX) reported warnings on ports 8/1-8/3 (Unknown) due to BE2 Arbiter experienced an error in device 65 (device error 0xc410d613) 2008 Jul 15 19:39:35 fcd95c41 %XBAR-5-XBAR_STATUS_REPORT: Module 12 reported status for component 88 code 0x40240015. 2008 Jul 15 19:39:35 fcd95c41 %MODULE-2-MOD_DIAG_FAIL: Module 12 (serial: JXXXXXXXXX) reported failure on ports 12/1-12/24 (Fibre Channel) due to Fatal runtime Arb error. (DevErr is bitmap of failed modules) in device 88 (device error 0x800) The output of the show logging onboard command will have a log similar to the one shown below for the reloaded module. To identify the issue in the log, look for one of the following signatures: MCSR: 20000000 MCSR: 10000000 Logging time: Tue Jul 15 19:39:28 2008 machine check: process swapper (0), jiffies 0x744af3a4 Free pages in zone[0]:0x4a70,zone[1]:0x0,zone[2]:0x0 Stack: c000dd58 c001eefc c000b2c4 c000ae98 d2060e10 c003d7a4 c00f869c c0045cdc d196c584 d196d100 c000c31c c000c3e4 c000ae90 c000c910 c000c924 c0008948 c01ca610 c0000394 MCSR: 20000000 MCAR Fabric Switch and Blade Switches On affected fabric switch and blades switches, the output of the show system reset-reason command will show the following: ----- reset reason for Supervisor-module 1 (from Supervisor in slot 1) --1) At 867189 usecs after Tue Aug 12 09:06:25 2008 Reason: Kernel Panic Service: Version: 3.2(1a) The output of the show system exception-info command will have logs like those shown below on the fabric switch and blade switches. To identify the issue in the log, look for one of the following signatures: MCSR: 40000000 MCSR: 20000000 MCSR: 10000000 MCSR: 00000010 Time of exception: Tue Aug 12 09:06:24 2008 (second=1218503184) CPU register dump: 1218503184:00960000 machine check: process swapper (0), jiffies 0x6df3d484 Free pages in zone[0]:0xa5c1,zone[1]:0x0,zone[2]:0x0 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(3) 38 OL-14116-11

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44

Send documentation comments to [email protected]
38
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(3)
OL-14116-11
Caveats
Director Switches
The output of the
show logging log
command will have events like those shown below on director
switches. In the following output, module 7 is the supervisor and module 12 is the module that
reloaded.
2008 Jul 15 19:39:30 fcd95c41 %MODULE-4-MOD_WARNING: Module 7 (serial: JXXXXXXXXX)
reported warnings on ports 7/1-7/3 (Unknown) due to BE2 Arbiter experienced an error
in device 65 (device error 0xc410d613)
2008 Jul 15 19:39:30 fcd95c41 %MODULE-4-MOD_WARNING: Module 8 (serial: JXXXXXXXXX)
reported warnings on ports 8/1-8/3 (Unknown) due to BE2 Arbiter experienced an error
in device 65 (device error 0xc410d613)
2008 Jul 15 19:39:35 fcd95c41 %XBAR-5-XBAR_STATUS_REPORT: Module 12 reported status
for component
88 code 0x40240015.
2008 Jul 15 19:39:35 fcd95c41 %MODULE-2-MOD_DIAG_FAIL: Module 12 (serial: JXXXXXXXXX)
reported failure on ports 12/1-12/24 (Fibre Channel) due to Fatal runtime Arb error.
(DevErr is bitmap of failed modules) in device 88 (device error 0x800)
The output of the
show logging onboard
command will have a log similar to the one shown below
for the reloaded module. To identify the issue in the log, look for one of the following signatures:
MCSR: 20000000
MCSR: 10000000
Logging time: Tue Jul 15 19:39:28 2008
machine check: process swapper (0), jiffies 0x744af3a4
Free pages in zone[0]:0x4a70,zone[1]:0x0,zone[2]:0x0
Stack: c000dd58 c001eefc c000b2c4 c000ae98 d2060e10 c003d7a4 c00f869c c0045cdc
d196c584 d196d100 c000c31c c000c3e4 c000ae90 c000c910 c000c924 c0008948 c01ca610
c0000394
...................
..................
MCSR: 20000000 MCAR:
...................................
..................
..................
Fabric Switch and Blade Switches
On affected fabric switch and blades switches, the output of the
show system reset-reason
command will show the following:
----- reset reason for Supervisor-module 1 (from Supervisor in slot 1)
---
1) At 867189 usecs after Tue Aug 12 09:06:25 2008
Reason: Kernel Panic
Service:
Version: 3.2(1a)
The output of the
show system exception-info
command will have logs like those shown below on
the fabric switch and blade switches. To identify the issue in the log, look for one of the following
signatures:
MCSR: 40000000
MCSR: 20000000
MCSR: 10000000
MCSR: 00000010
Time of exception: Tue Aug 12 09:06:24 2008
(second=1218503184)
CPU register dump:
1218503184:00960000 machine check: process swapper (0), jiffies
0x6df3d484 Free pages in zone[0]:0xa5c1,zone[1]:0x0,zone[2]:0x0