Skip to main content
NetApp Stage KB

Received PANIC packet from partner with initial single cluster flapping port

  1. Last updated
  2. Save as PDF

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

Applies to

Issue

  • Initial single flapping cluster port: 
[node_name: kernel: netif.linkDown:info]: Ethernet e0a: Link down, check cable.
[node_name: kernel: netif.linkUp:info]: Ethernet e0a: Link up.
[node_name: kernel: netif.linkDown:info]: Ethernet e0a: Link down, check cable.
[node_name: kernel: netif.linkUp:info]: Ethernet e0a: Link up.
...
 
  • Both cluster ports go down, triggering a PANIC:
[node_name:vifmgr.clus.linkdown:EMERGENCY]: The cluster port e0b on node node_name has gone down unexpectedly.
[node_name:vifmgr.clus.linkdown:EMERGENCY]: The cluster port e0a on node node_name 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.)
  • Loop back test connecting e0a to e0a and e0b to e0b, on each node, shows just one node with active link LED.

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.