Skip to main content
NetApp Knowledge Base

NIC port seeing CRC errors in ifstat

Views:
1,972
Visibility:
Public
Votes:
2
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • FAS / AFF Systems
  • Networking Adapters

Issue

  • The output of the ifstat command shows high CRC errors on the affected port

::> system node run -node <NODE_NAME> -command ifstat <PORT>

-- interface  e4a  (7 hours, 33 minutes, 13 seconds) --

RECEIVE
 Total frames:    10739k | Frames/second:     395  | Total bytes:     14537m
 Bytes/second:      534k | Total errors:     4921  | Errors/minute:      11 
 Total discards:      0  | Discards/minute:     0  | Multi/broadcast:   334k
 Non-primary u/c:     0  | CRC errors:       4921  | Runt frames:         0 
 Fragment:            0  | Long frames:         0  | Jabber:              0  

  • Following errors are reported in event logs:

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

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device