Skip to main content
NetApp Knowledge Base

CONTAP-53314: Tx total errors count of an interface group port in "ifstat" output might not correlate with respective counts of member ports

Views:
54
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Issue

  • Output of ifstat in section TRANSMIT indicates increasing Total Errors for interface group, but not for its underlying physical member ports.
Example:

RECEIVE Total frames: 72688k | Frames/second: 266 | Total bytes: 207g Bytes/second: 760k | Total errors: 0 | Errors/minute: 0 [...] TRANSMIT Total frames: 397m | Frames/second: 55169 | Total bytes: 512g Bytes/second: 71122k | Total errors: 2720 | Errors/minute: 23

Note: Total errors on TRANSMIT increased
  • EMS finds ifgrp interface generate alert vifmgr.cluscheck.crcerrors.

nodename::*> event log show -message-name vifmgr.cluscheck.crcerrors Time Node Severity Event ------------------- ---------------- ------------- --------------------------- 4/22/2021 00:42:39 nodename ALERT vifmgr.cluscheck.crcerrors: Port a0a on nodename is reporting a high number of observed hardware errors, possibly CRC errors.

or

ALERT vifmgr.cluscheck.hwerrors: Port a1a on node ***** is reporting a high number (at least 1 per 1000 packets) of observed hardware errors (CRC, length, alignment, dropped).

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.