Skip to main content
NetApp Knowledge Base

CRC errors received on a single NIC port solved with cable replacement

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

​ ​

Applies to

  • ONTAP 9
  • FAS / AFF Systems
  • CRC errors reporting on a single data port
  • Data port using SFP and optical cable

Issue

  • Event logs report hardware errors on a physical and/or logical port.

[node-01: vifmgr: vifmgr.cluscheck.crcerrors]: Port a0b on node node-01 is reporting a high number of observed hardware errors, possibly CRC errors
[node-02: vifmgr: vifmgr.cluscheck.crcerrors]: Port e0d on node node-02 is reporting a high number of observed hardware errors, possibly CRC errors
[node-02: vifmgr: vifmgr.cluscheck.hwerrors:alert]: Port e0d on node node-02 is reporting a high number (at least 1 per 1000 packets) of observed hardware errors (CRC, length, alignment, dropped)

  • ifstat output show CRC errors if ONTAP is receiving the errors.
  • Issue resolved after cable/SFP swap

 

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.