Skip to main content
NetApp Knowledge Base

Node Panic During Cluster Switch Firmware Upgrade

Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

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).

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.