Node Panic During Cluster Switch Firmware Upgrade
Applies to
- NetApp AFF-A250
- ONTAP 9
- BES-53248 Switches (Broadcom)
Issue
During a planned firmware upgrade and reboot of BES-53248 cluster switches in a two-node NetApp AFF-A250 cluster with following FPVR running ONTAP 9.15.1
- Two-node clusters with FPVR-approved non-standard cluster/HA cabling (e.g., e0c/e2a as cluster ports connected with cluster switch, e0d as HA interconnect directly without switch/back-to-back)
The following symptoms occurred:
- Node panic and automatic takeover during switch reboot.
- Cluster port (e2a) experienced repeated link down/up (flapping) events.
- CLAM (Connectivity, Liveliness and Availability Monitor) reported out-of-quorum and triggered a node panic/takeover.
- Event logs showed:
[vifmgr.clus.linkdown:EMERGENCY]: The cluster port e2a on node node-01 has gone down unexpectedly.PANIC: Received PANIC packet from partner, receiving message is (Coredump and takeover initiated because Connectivity, Liveliness and Availability Monitor (CLAM) has determined this node is out of quorum.)
- The issue was reproducible: occurred on both switch reboots, but only on this cluster (other clusters with similar upgrades did not experience the issue).
