Skip to main content
NetApp Knowledge Base

Only the port of one node is shown as degraded in a switchless cluster system

  1. Last updated
  2. Save as PDF
Views:
356
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
HW
Last Updated:

Applies to

  • ONTAP 9
  • 2-node Switchless Cluster (TNSC)

Issue

  • Autosupport Alert
    HA Group Notification (CLUSTER NETWORK DEGRADED) ALERT
  • The EMS log shows that the one of cluster port is in the degraded state.

[vifmgr.reach.skipped:notice]: Network port e0d on node Node-01 was not scanned for reachability because it was administratively or operationally down at the time of the scan.
[vifmgr.port.monitor.failed:error]: The "link_flapping" health check for port e0d (node node-01) has failed. The port is operating in a degraded state.
[vifmgr.portDeg.lifMoved:notice]: LIF node-01_clus2 (on virtual server ****), IP address *****, is being moved to node node-01, port e0c from node node-01, 
port e0d because the port's health status is in a degraded state.

  • The network port show command output indicate that only the port of one node is in a degraded state.
    The two Cluster ports of the partner node are both in healthy status.

::> network port show
Node: Node-01
                                                  Speed(Mbps) Health
Port    IPspace      Broadcast Domain Link MTU  Admin/Oper  Status
--------- ------------ ---------------- ---- ---- ----------- --------
e0M       Default      Default          up   1500  auto/1000  healthy
e0a       Default      -                up   1500 auto/1000  healthy
e0b       Default      -                down 1500  auto/-     -
e0c       Cluster      Cluster          up   9000  auto/25000 healthy
e0d       Cluster      Cluster          up   9000  auto/25000 degraded
e2a       Default      -     down 1500  auto/-     -

Node: Node-02
                              Speed(Mbps) Health
Port      IPspace      Broadcast Domain Link MTU  Admin/Oper  Status
--------- ------------ ---------------- ---- ---- ----------- --------
e0M       Default      Default          up   1500  auto/1000 healthy
e0a       Default      -                up   1500  auto/1000  healthy
e0b       Default      -                down 1500 auto/-     -
e0c       Cluster      Cluster          up   9000  auto/25000 healthy
e0d       Cluster      Cluster          up   9000  auto/25000 healthy
e2a       Default      -                down 1500  auto/-     -
e2b       Default      - down 1500  auto/-     -
14 entries were displayed.

  • Resetting the direct attach cable does not improve the situation.

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.