Skip to main content
NetApp Knowledge Base

Switched Cluster : Received PANIC packet from partner

Views:
172
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • ONTAP 9
  • Cluster Switch

Issue

  • Cluster ports go down on a node

[Node-01: kernel: netif.linkDown:debug]: Ethernet e0c: Link down, check cable.
[Node-01: kernel:netif.linkDown:debug]: Ethernet e0c: Link down, check cable.
[Node-01: kernel:netif.linkDown:debug]: Ethernet e0d: Link down, check cable.
[Node-01: vifmgr:vifmgr.portdown:debug]: A link down event was received on node XXXXX,   port  e0d.
[Node-01: vifmgr:vifmgr.clus.linkdown:debug]: The cluster port e0d on node XXXXX has   gone down unexpectedly.

  • This triggers a CLAM Panic and the partner performs takeover

[Node-01: mcc_ic_kill_pkt_handler: sk.panic:debug]: Panic String:Received PANIC packet from partner, receiving message is (Coredump and takeoverinitiated because Connectivity, Liveliness and Availability Monitor (CLAM) hasdetermined this node is out of quorum.) in SK process mcc_ic_kill_pkt_handler onrelease 9.11.1P9 (C)

  • network port show -role cluster displays all cluster ports as down

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.