Skip to main content
NetApp Knowledge Base

CRC errors received on a single NIC port

Views:
4,054
Visibility:
Public
Votes:
1
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • ONTAP 9
  • FAS / AFF Systems
  • CRC errors reporting on a single port

Issue

  • EMS messages reporting CRC errors on one physical port and/or ifgroup that the port belongs to:

4/16/2021 13:07:49  node_name ALERT vifmgr.cluscheck.crcerrors: Port a0b on node node_name is reporting a high number of observed hardware errors, possibly CRC errors.
4/16/2021 13:07:49  node_name ALERT vifmgr.cluscheck.crcerrors: Port e0d on node node_name is reporting a high number of observed hardware errors, possibly CRC errors.

  • ifstat output. Example:

RECEIVE
 Total frames:   36418m  | Frames/second:   23646  | Total bytes:       179t
 Bytes/second:      116m | Total errors:      170k | Errors/minute:    7
 Total discards:      0  | Discards/minute:     0  | Multi/broadcast:  1686k
 Non-primary u/c:     0  | CRC errors:        159k | Long frames:      0
 Jabber:          10471  | Length errors:       0  | No buffer:           0
 Pause:               0  | Jumbo: 24075m           | Error symbol:        0
 Bus overruns:        0  | LRO segments:    18749m | LRO bytes:         178t
 LRO6 segments:       0  | LRO6 bytes:          0  | Bad UDP cksum:       0
 Bad UDP6 cksum:      0  | Bad TCP cksum:       0  | Bad TCP6 cksum:      0
 Mcast v6 solicit:    0

  • Issue remains after cable/SFP re-seat and ifstat clear in the node side.

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support