Skip to main content
NetApp Knowledge Base

vifmgr reporting CRC errors on multiple interfaces

Views:
5,318
Visibility:
Public
Votes:
2
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • ONTAP 9
  • FAS / AFF Systems
  • CRC errors reporting on multiple ports

Issue

  • Multiple interfaces report CRC errors.

Cluster::> event log show -message-type *crc*
Mon May 25 09:05:14 CEST [node01: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e0e on node node01 is reporting a high number of observed hardware errors, possibly CRC errors.
Mon May 25 09:05:14 CEST [node01: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e0f on node node01 is reporting a high number of observed hardware errors, possibly CRC errors.
Mon May 25 09:55:14 CEST [node01: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e0h on node node01 is reporting a high number of observed hardware errors, possibly CRC errors.

  • ifstat increases the CRC errors counter.

Cluster::> node run node01 ifstat e0h

-- interface  e0h  (5 days, 12 hours, 52 minutes, 9 seconds) --

RECEIVE
Total frames:     1534m | Frames/second:    3208  | Total bytes:      2236g
Bytes/second:     4674k | Total errors:      845  | Errors/minute:       0
Total discards:      0  | Discards/minute:     0  | Multi/broadcast: 31966k
Non-primary u/c:     0  | CRC errors:        843  | Runt frames:         0
Long frames:         2  | Length errors:     101  | Alignment errors:    0
No buffer:           0  | Pause:               0  | Jumbo:             179m
Noproto:             0  | Bus overruns:        0  | LRO segments:    14947m
LRO bytes:        2012g | 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  | Lagg errors:         0
Lacp errors:         0  | Lacp PDU errors:     0

  • There may be link flapping on the affected ports:

Wed Jan 24 12:46:43  0100 [node01: mgmt_port_link_status_poll: netif.linkDown:info]: Ethernet e0e: Link down, check cable.
Wed Jan 24 12:46:43  0100 [node01: intr: net.ifgrp.lacp.link.inactive:error]: ifgrp a0a, port e0e has transitioned to an inactive state. The interface group is in a degraded state.
Wed Jan 24 12:46:43  0100 [node01: vifmgr: vifmgr.portdown:notice]: A link down event was received on node node01, port e0e.
Wed Jan 24 12:46:44  0100 [node01: mgmt_port_link_status_poll: netif.linkUp:info]: Ethernet e0e: Link up.
Wed Jan 24 12:46:44  0100 [node01: vifmgr: vifmgr.portup:notice]: A link up event was received on node node01, port e0e.

 

 

 

 

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.