Standby CP went into faulty state on Brocade X7 switch
Applies to
- Brocade X7 switch
- FOS v9.2.1a
Issue
- Standby CP rebooted on Brocade X7 switch.
- Standby CP went into faulty state and come back to deasserted state.
2025/04/28-02:03:56 (IST), [HAMK-1004], 2352808, SLOT 1 | CHASSIS, INFO, sw13, Resetting standby CP (double reset may occur).
2025/04/28-02:03:56 (IST), [FSSM-1003], 2352809, SLOT 1 | CHASSIS, WARNING, sw13, HA State out of sync.
2025/04/28-02:03:56 (IST), [EM-1033], 2352810, SLOT 1 | CHASSIS, ERROR, sw13, CP in Slot 2 set to faulty because CP ERROR asserted.
2025/04/28-02:03:59 (IST), [EM-1047], 2352811, SLOT 1 | CHASSIS, INFO, sw13, CP in slot 2 not faulty, CP ERROR deasserted.
2025/04/28-02:04:22 (IST), [MAPS-1021], 2352812, SLOT 1 | FID 128, WARNING, sw1, RuleName=defCHASSISHA_SYNC_0, Condition=CHASSIS(HA_SYNC/NONE==0), Obj:Chassis [HA_SYNC,0] has contributed to switch status MARGINAL.
2025/04/28-02:04:22 (IST), [MAPS-1020], 2352813, SLOT 1 | FID 128, WARNING, sw1, Switch wide status has changed from HEALTHY to MARGINAL.
- Secondary partition on standby package is showing as Vpackage.
firmwareshow -v:
Slot Name Appl Primary/Secondary Versions Status
--------------------------------------------------------------------------
1 CP0 FOS v9.2.1a ACTIVE
v9.2.1a
2 CP1 FOS v9.2.1a STANDBY *
vpackage