Skip to main content
NetApp Knowledge Base

Intercluster LIF port flapping makes cluster peer health DATA/ICMP unreachable

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

Applies to

  • FAS8200
  • ONTAP 9

Issue

  • One of the network ports in intercluster LIF repeats link up and down.

     EMS log reports the following information:

Mon Mar 08 00:32:09 JST [cluster-01-06: intr: netif.linkDown:info]: Ethernet e0h: Link down, check cable.

Mon Mar 08 00:32:10 JST [cluster-01-06: intr: netif.linkUp:info]: Ethernet e0h: Link up.

Mon Mar 08 00:34:11 JST [cluster-01-06: intr: netif.linkDown:info]: Ethernet e0h: Link down, check cable.

Mon Mar 08 00:34:12 JST [cluster-01-06: intr: netif.linkUp:info]: Ethernet e0h: Link up.

Mon Mar 08 00:36:19 JST [cluster-01-06: intr: netif.linkDown:info]: Ethernet e0h: Link down, check cable.

Mon Mar 08 00:36:20 JST [cluster-01-06: intr: netif.linkUp:info]: Ethernet e0h: Link up.

  • Availability of the Remote Cluster shows as Partial status in CLUSTERPEER-ATABLE:

Cluster UUID xxxxxxxxxxxxxx
Availability of the Remote Cluster    Partial
Unreachable Local Nodes    
Num of Node Pairs Healthy    195
Num of Node Pairs Unhealthy    5

  • Ping-Status shows DATA and ICMP as unreachable in cluster peer health show on SnapMirror destination side:

cluster-05::> cluster peer health show

Node       Cluster-Name                 Node-Name

             Ping-Status         RDB-Health Cluster-Health Availability

---------- --------------------------- --------- --------------- ------------

cluster-05-01

           cluster-01                   cluster-01-06

 

             Data: unreachable

             ICMP: unreachable         true      true            false

cluster-05-03

           cluster-01                  cluster-01-06

             Data: unreachable

             ICMP: unreachable         true      true false

 

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.