Skip to main content
NetApp Knowledge Base

Cluster port down in a Switchless configuration

Views:
1,535
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
hw
Last Updated:
5/29/2024, 8:14:26 PM

Applies to

  • ONTAP 9
  • AFF/FAS systems
  • Switchless configuration cluster

Issue

  • One cluster port down:

::> network port show

Node: A
                                                  Speed(Mbps) Health
Port      IPspace      Broadcast Domain Link MTU  Admin/Oper  Status
--------- ------------ ---------------- ---- ---- ----------- --------
e0a       Cluster      Cluster          up   9000  auto/10000 healthy
e0b       Cluster      Cluster          down 9000  auto/-     -
...

Node: B
                                                  Speed(Mbps) Health
Port      IPspace      Broadcast Domain Link MTU  Admin/Oper  Status
--------- ------------ ---------------- ---- ---- ----------- --------
e0a       Cluster      Cluster          up   9000  auto/10000 healthy
e0b       Cluster      Cluster          down 9000  1000/-     -
...
28 entries were displayed.

  • EMS log shows port link down or flapping frequently:

<LR d="11Mar2023 16:54:11" n="A" t="1234567890" id="1543945678/1234012" p="6" s="Ok" o="mgmt_port_link_status_poll" vf="" type="0" seq="1234567" >
<netif_linkDown_1
        lanType="Ethernet"
        ifName="e0b"
        status="down, check cable"/>
</LR>

<LR d="11Mar2023 16:54:14" n="A" t="1234567897" id="1543945679/1234017" p="5" s="Ok" o="vifmgr" vf="" type="1" seq="1235678" >
<vifmgr_portdown_1
        nodename="A"
        portname="e0b"/>
</LR>

or

Wed Nov 15 18:20:39 +0900 [Node01: kernel: netif.linkDown:debug]: Ethernet e0b: Link down, check cable.
Wed Nov 15 18:20:39 +0900 [Node01: vifmgr: vifmgr.portdown:debug]: A link down event was received on node Node01, port e0b.
Wed Nov 15 18:20:39 +0900 [Node01: vifmgr: vifmgr.clus.linkdown:debug]: The cluster port e0b on node Node01 has gone down unexpectedly.
Wed Nov 15 18:20:39 +0900 [Node01: vifmgr: vifmgr.lifmoved.linkdown:debug]: LIF Node01_clus2 (on virtual server 4294967293), IP address 169.xx.xx.xxx, is being moved to node Node01, port e0a.
Wed Nov 15 18:20:39 +0900 [Node01: vifmgr: vifmgr.lifsuccessfullymoved:debug]: LIF Node01_clus2 (on virtual server 4294967293), IP address 169.xx.xx.xxx, is now hosted on node Node01, port e0a.
Wed Nov 15 18:20:41 +0900 [Node01: kernel: netif.linkUp:debug]: Ethernet e0b: Link up.
Wed Nov 15 18:20:41 +0900 [Node01: vifmgr: vifmgr.portup:debug]: A link up event was received on node Node01, port e0b.
Wed Nov 15 18:20:44 +0900 [Node01: vifmgr: vifmgr.port.monitor.failed:debug]: The "link_flapping" health check for port e0b (node Node01) has failed. The port is operating in a degraded state.
...
Wed Nov 15 18:25:34 +0900 [Node01: kernel: netif.linkDown:debug]: Ethernet e0b: Link down, check cable.
Wed Nov 15 18:25:34 +0900 [Node01: vifmgr: vifmgr.portdown:debug]: A link down event was received on node Node01, port e0b.

  • One cluster port e0b shows  auto-unknown-fd-down status. :

::> system node run -node * -command sysconfig -a

e0b MAC Address:    00:aa:11:22:33:66 (auto-unknown-fd-down)
            SFP Vendor:         AAAA          
            SFP Part Number:    BBBBBBBB-BBB
            SFP Serial Number:  CCCCCC 

 

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.