Skip to main content
NetApp Knowledge Base

MetroCluster IP - CLUSTER NETWORK DEGRADED: CRC Errors Detected

  1. Last updated
  2. Save as PDF
Views:
119
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • MetroCluster IP
  • ONTAP 9
  • NVidia SN2100 MetroCluster switches

Issue

Error messages observed in EMS
 
Example:
 
Tue Sep 19 21:25:18 +0200 [ClusterA-02: vifmgr: vifmgr.cluscheck.hwerrors:alert]: Port eXx on node ClusterA-02 is reporting a high number (at least 1 per 1000 packets) of observed hardware errors (CRC, length, alignment, dropped).
 
Tue Sep 19 21:25:18 +0200 [ClusterA-02: vifmgr: callhome.clus.net.degraded:alert]: Call home for CLUSTER NETWORK DEGRADED: CRC Errors Detected - High CRC errors detected on port eXx node ClusterA-02
 
Tue Sep 19 21:25:18 +0200 [ClusterA-02: nphmd: hm.alert.raised:alert]: Alert Id = NodeIfInErrorsWarnAlert , Alerting Resource = ClusterA-02/eXx raised by monitor controller

 

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.