Skip to main content
NetApp Knowledge Base

Cluster interconnect link down in a two-node switchless cluster

  1. Last updated
  2. Save as PDF
Views:
1,487
Visibility:
Public
Votes:
2
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • FAS systems
  • AFF systems
  • Two-node switchless cluster

Issue

  • The cluster ports are connected to each other in a two-node switchless cluster, as shown in the below example:
    • Node-1 e0a  <-> Node-2 e0a
    • Node-1 e0b  <-> Node-2 e0b
  • In this scenario, if one of the cluster ports goes down on one node, then that cluster interconnect link goes down on both the nodes at the same time.

For Example:

Tue Jul 27 02:24:18 IST [Node-1: kernel: netif.linkDown:info]: Ethernet e0a: Link down, check cable.
Tue Jul 27 02:24:21 IST [Node-1: vifmgr: vifmgr.portdown:notice]: A link down event was received on node Node-1, port e0a.
Tue Jul 27 02:24:24 IST [Node-1: vifmgr: vifmgr.clus.linkdown:EMERGENCY]: The cluster port e0a on node Node-1 has gone down unexpectedly
                         
Tue Jul 27 02:24:18 IST [Node-2: kernel: netif.linkDown:info]: Ethernet e0a: Link down, check cable.
Tue Jul 27 02:24:21 IST [Node-2: vifmgr: vifmgr.portdown:notice]: A link down event was received on node Node-2, port e0a.
Tue Jul 27 02:24:25 IST [Node-2: vifmgr: vifmgr.clus.linkdown:EMERGENCY]: The cluster port e0a on node Node-2 has gone down unexpectedly.

  • The cluster LIFs hosted on the down cluster ports will be moved to the redundant cluster ports on both nodes.

For Example:

Tue Jul 27 02:24:24 IST [Node-1: vifmgr: vifmgr.lifsuccessfullymoved:notice]: LIF Node-1_clus1 (on virtual server 5432198765), IP address 169.X.X.X, is now hosted on node Node-1, port e0b.
Tue Jul 27 02:24:25 IST [Node-2: vifmgr: vifmgr.lifsuccessfullymoved:notice]: LIF Node-2_clus1 (on virtual server 5432198765), IP address 169.X.X.X, is now hosted on node Node-2, port e0b.                 

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.