Skip to main content
NetApp Knowledge Base

CRC errors increment on node due to faulty onboard port

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

Applies to

  • FAS/AFF
  • ONTAP 9

Issue

  • CRC errors are incrementing on an onboard port:

::> system node run -node Node-02 -command ifstat e0e

-- interface  e0e  (6 days, 12 hours, 36 minutes, 51 seconds) --
RECEIVE
Total frames:     1653k | Frames/second:       3  | Total bytes:       357m
Bytes/second:      635  | Total errors:      625  | Errors/minute:       0
Total discards:      0  | Discards/minute:     0  | Multi/broadcast:  2537k
Non-primary u/c:     0  | CRC errors:        625  | Runt frames:         0

  • The following errors are reported in event logs:

[Node-02: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e0e on node Node-02 is reporting a high number of observed CRC errors.

  • Replacement of SFP and cable on the node and switch end does not stop the errors.
  • The errors on the port increment even after changing the switch side port.

 

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.