Brocade switch was reporting persistent hardware faults
Applies to
- MetroCluster FC
- Brocade Switch
- ONTAP 9
Issue
- A Brocade switch was reporting persistent hardware faults, eventually entering a “faulty” state.
- The following errors can be seen on the supportshow:
FCN000001:admin> switchshowswitchName: FCN000001switchType: 162.5switchState: FaultyswitchMode: NativeswitchRole: FaultyswitchDomain: 5switchId: fffc05switchWwn: 10:00:88:94:71:c1:d3:78zoning: ON (CFG_G620_FAB_1_RCF_9_2b)switchBeacon: OFFFC Router: OFFHIF Mode: OFFerrdump -a:2026/03/27-19:13:45 (CEST), [C4-1045], 8144, CHASSIS, INFO, BrocadeG620,Single parity error detected in ftb statistics memory, slot 0 index 0
2026/03/27-19:13:45 (CEST), [C4-1010], 8145, CHASSIS, CRITICAL, BrocadeG620, S0,C0: Above normal hardware errors were observed: fault1:0xa, fault2:0xa thresh2:0xb000000a.
2026/03/27-19:13:45 (CEST), [C4-1056], 8146, CHASSIS, CRITICAL, BrocadeG620, Chip in Slot 0, Chip 0 getting faulted with reason 52.
2026/03/27-19:13:45 (CEST), [EM-1134], 8147, FFDC | CHASSIS, ERROR, BrocadeG620, Switch set to faulty, rc=20015.
2026/03/27-19:13:45 (CEST), [RAS-1001], 8148, CHASSIS, INFO, BrocadeG620, First failure data capture (FFDC) event occurred.- Event logs:
ERROR fcvi.qlgc.ioErr: FC-VI adapter: FCVI driver on port 5a/5c received IO error. Status=FW detected response error (status code=0x121), FCVI opcode=WriteRequest (0x1), QPname=WAFL, QPindex=4/10, Remote node's systemid=