Skip to main content
NetApp Knowledge Base

L2 Reachability issues on cluster ports with ONTAP 9.13.1 or later

Views:
7,452
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
hw
Last Updated:

 

Applies to

Issue

  • Errors similar to the following are reported for one of the cluster ports:

Tue Jan 23 18:06:43 +0900 [Node-01: vifmgr: vifmgr.reach.noreach:notice]: Network port e4e on node Node-01 cannot reach its expected broadcast domain Cluster:Cluster. No other broadcast domains appear to be reachable from this port.
Tue Jan 23 18:06:44 +0900 [Node-01: vifmgr: vifmgr.port.monitor.failed:error]: The "l2_reachability" health check for port e4e (node Node-01) has failed. The port is operating in a degraded state.

  • The following call home alert is seen:

Tue Jan 23 18:06:44 +0900 [Node-01: vifmgr: callhome.clus.net.degraded:alert]: Call home for CLUSTER NETWORK DEGRADED: Insufficient L2 Reachability - Insufficient L2 Reachability detected from cluster port e4e on node Node-01.

  • After some time the reachability will be restored:
Tue Jan 23 18:06:57 +0900 [Node-01: vifmgr: vifmgr.reach.ok:notice]: Network port e4e on node Node-01 can reach its expected broadcast domain Cluster:Cluster. No other broadcast domains appear to be reachable from this port.
Tue Jan 23 18:07:14 +0900 [Node-01: vifmgr: vifmgr.port.monitor.passed:notice]: The "l2_reachability" health check for port e4e (node Node-01) has passed.
Tue Jan 23 18:07:14 +0900 [Node-01: vifmgr: vifmgr.portHealthy:notice]: The health status of port e4e (node Node-01) has changed from degraded to healthy. This port can now be used for hosting LIFs.

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.