Brocade X6-8 director does not come online after a power outage

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 280

Visibility:: Public

Votes:: 0

Category:: fabric-interconnect-and-management-switches

Specialty:: brocade

Last Updated:

Applies to

FC
SAN
Brocade X6-8
Brocade Fabric Operating System (FOS)

Issue

The switch is offline/disabled:

switchshow : switchName: switch switchType: 166.0 switchState: Offline switchMode: Native switchRole: Disabled

Both core blades are booting or showing as faulty, other blades may also be down:

slotshow -m :

Slot Blade Type ID Model Name Status

--------------------------------------------------

1 CP BLADE 175 CPX6 ENABLED

2 CP BLADE 175 CPX6 ENABLED

3 UNKNOWN VACANT

4 SW BLADE 178 FC32-48 INSERTED, NOT POWERED ON

5 SW BLADE 178 FC32-48 INSERTED, NOT POWERED ON

6 SW BLADE 178 FC32-48 ENABLED

7 CORE BLADE 177 CR32-8 FAULTY (21)

8 CORE BLADE 177 CR32-8 DIAG RUNNING POST2

9 SW BLADE 178 FC32-48 ENABLED

10 SW BLADE 178 FC32-48 ENABLED

11 UNKNOWN VACANT

12 UNKNOWN VACANT

Reseating individual blades, or both core blades at once, does not bring the blades back up.
Power cycling blades with slotPowerOff and slotPowerOn does not bring the blades back up.
Rebooting the switch does not bring the blades back up.
errdump shows both core blades in slot 7 and 8 failing to boot:

2023/11/02-11:15:32, [BL-1017], 1157, SLOT 2 | CHASSIS, INFO, X6-8, Slot 7 Initializing...

2023/11/02-11:15:52, [BL-1019], 1158, SLOT 2 | CHASSIS, INFO, X6-8, Slot 7, retry 1, internal port retry initialization, ports: 220 .

2023/11/02-11:16:02, [BL-1019], 1159, SLOT 2 | CHASSIS, INFO, X6-8, Slot 7, retry 2, internal port retry initialization, ports: 217 220 .

2023/11/02-11:16:12, [BL-1002], 1160, SLOT 2 | FFDC | CHASSIS, CRITICAL, X6-8, Init Failed: slot 7 DISABLED because internal ports were not ONLINE, ports: 217 220 .

2023/11/02-11:16:12, [RAS-1002], 1161, SLOT 2 | CHASSIS, WARNING, X6-8, First failure data capture (FFDC) reached maximum storage size (15 MB).

2023/11/02-11:16:13, [EM-1134], 1162, SLOT 2 | FFDC | CHASSIS, ERROR, X6-8, Slot 7 set to faulty, rc=20015.

2023/11/02-11:21:54, [EM-2003], 1165, SLOT 2 | CHASSIS, ERROR, X6-8, Slot 8 has failed the POST tests. FRU is being faulted.

2023/11/02-11:21:54, [EM-1072], 1166, SLOT 2 | FFDC | CHASSIS, CRITICAL, X6-8, Chassis cannot become ready since no Core Blades are available.

errdump shows switch auto-reboots and reports it is not ready:

2023/11/02-11:29:37, [SWCH-1001], 1187, SLOT 2 | FID 128, ERROR, switch, Switch is not in ready state - Switch enable failed, switch status= 0x4, c_flags = 0x10400.

2023/11/02-11:35:39, [HAM-1007], 1188, SLOT 2 | FFDC | CHASSIS, CRITICAL, X6-8, Need to reboot the system for recovery, reason: Software Bootup Failure:Bringup timed out.

2023/11/02-11:36:09, [HAM-1008], 1189, SLOT 2 | FFDC | CHASSIS, CRITICAL, X6-8, Rebooting the system for recovery - auto-reboot is enabled.

hadump shows CP blades are not in sync:

Local CP (Slot 2, CP1): Active, Cold Recovered

Remote CP (Slot 1, CP0): Standby, Healthy

HA enabled, Heartbeat Up, HA State not in sync