Skip to main content
NetApp Knowledge Base

Temporary vifmgr.port.monitor.failed error. Failed "l2_reachability" health check

  1. Last updated
  2. Save as PDF
Views:
2,147
Visibility:
Public
Votes:
1
Category:
fabric-interconnect-and-management-switches
Specialty:
MetroCluster
Last Updated:

Applies to

  • FAS/AFF
  • ONTAP 9
  • Cluster network switch (CNS) Cisco Nexus N3K-C3132Q-V
  • MetroCluster-IP (MCC-IP)

Issue

  • Several random temporary L2 reachability EMS messages in different nodes and ports. Example:

Thu Dec 03 15:57:33 +0100 [node_name: ctran_clam_0: ems.engine.suppressed:debug]: Event 'csm.connCookieNotFound' suppressed 19 times in last 702 seconds.
Thu Dec 03 15:57:33 +0100 [node_name: ctran_clam_0: csm.connCookieNotFound:debug]: Session (req=cc51A:dblade, rsp=node_name:dblade, uniquifier=0b05b2e186d65fb2): connection cookie 1011 is invalid.
Thu Dec 03 15:57:38 +0100 [node_name: vifmgr: vifmgr.bcastDomainPartition:error]: Broadcast domain Cluster is partitioned into 2 groups on node node_name. The different groups are: {e0a}, {e0b}. LIFs hosted on the ports in this broadcast domain may be at the risk of seeing connectivity issues.
Thu Dec 03 15:57:44 +0100 [node_name: vifmgr: vifmgr.port.monitor.failed:error]: The "l2_reachability" health check for port e0a (node node_name) has failed. The port is operating in a degraded state.
Thu Dec 03 15:57:44 +0100 [node_name: vifmgr: callhome.clus.net.degraded:alert]: Call home for CLUSTER NETWORK DEGRADED: Insufficient L2 Reachability - Insufficient L2 Reachability detected from cluster port e0a on node node_name.
Thu Dec 03 15:57:44 +0100 [node_name: vifmgr: vifmgr.portDeg.lifMoved:notice]: LIF node_name-clus1 (on virtual server 4294967293), IP address 169.254.114.29, is being moved to node node_name, port e0b from node node_name, port e0a because the port's health status is in a degraded state.
Thu Dec 03 15:57:46 +0100 [node_name: vifmgr: vifmgr.lifsuccessfullymoved:notice]: LIF node_name-clus1 (on virtual server 4294967293), IP address 169.254.114.29, is now hosted on node node_name, port e0b.
Thu Dec 03 15:57:46 +0100 [node_name: vifmgr: vifmgr.port.monitor.passed:notice]: The "l2_reachability" health check for port e0a (node node_name) has passed.
Thu Dec 03 15:57:46 +0100 [node_name: vifmgr: vifmgr.portHealthy:notice]: The health status of port e0a (node node_name) has changed from degraded to healthy. This port can now be used for hosting LIFs.

  • The cluster ports reporting issues are connected to different MCC-IP cluster network switches (CNS).
  • The MCC-IP cluster network switches are running a compatible firmware and RCF files.
  • No issues reported in the switch logs "# show tech-support".
  • No issues reported in the ifstat outputs for the ports and VLANs.

 

 
 

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.