Skip to main content
NetApp Knowledge Base

vifmgr.cluscheck.crcerrors:alert in multiple ports and nodes

Views:
733
Visibility:
Public
Votes:
0
Category:
aff-series
Specialty:
hw
Last Updated:

Applies to

  • All FAS / AFF
  • Data network ports

Issue

  • Multiple CRC errors in different ports for multiple nodes. Example:
[node_name-01: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e8e on node node_name-01 is reporting a high number of observed hardware errors, possibly CRC errors.
[node_name-02: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e10e on node node_name-02 is reporting a high number of observed hardware errors, possibly CRC errors.
[node_name-01: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e1a on node node_name-01 is reporting a high number of observed hardware errors, possibly CRC errors.
[node_name-02: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e1a on node node_name-02 is reporting a high number of observed hardware errors, possibly CRC errors.
[node_name-02: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e8e on node node_name-02 is reporting a high number of observed hardware errors, possibly CRC errors.
  • Increasing CRC errors for those ports. Example

Node node_name-01:

-- interface  e1a  (1 day, 9 hours, 27 minutes, 0 seconds) --
RECEIVE
Total frames:      142k | Frames/second:       1  | Total bytes:     23646k
Bytes/second:      196  | Total errors:        7  | Errors/minute:       0
Non-primary u/c:     0  | CRC errors:          7  | Runt frames:         0

-- interface  e8e  (1 day, 9 hours, 27 minutes, 9 seconds) --
RECEIVE
Total frames:      133k | Frames/second:       1  | Total bytes:     19800k
Bytes/second:      164  | Total errors:        4  | Errors/minute:       0
Non-primary u/c:     0  | CRC errors:          4  | Runt frames:         0

Node node_name-02

-- interface  e1a  (557 days, 2 hours, 57 minutes, 54 seconds) --
RECEIVE
Total frames:    64746k | Frames/second:       1  | Total bytes:     10702m
Bytes/second:      222  | Total errors:       91  | Errors/minute:       0
Non-primary u/c:     0  | CRC errors:         91  | Runt frames:         0

-- interface  e8e  (25 days, 19 hours, 0 minutes, 1 second) --
RECEIVE
Total frames:     5835k | Frames/second:       3  | Total bytes:      1150m
Bytes/second:      516  | Total errors:       44  | Errors/minute:       0
Non-primary u/c:     0  | CRC errors:         44  | Runt frames:         0

-- interface  e10e  (15 days, 18 hours, 10 minutes, 56 seconds) --
RECEIVE
Total frames:     1451k | Frames/second:       1  | Total bytes:       207m
Bytes/second:      152  | Total errors:       50  | Errors/minute:       0
Non-primary u/c:     0  | CRC errors:         50  | Runt frames:         0

  • The interfaces where the previous ports are connected to, in the frontend data switches, report output errors AND not input errors. Example:
data_switch-1# show interface Ethernet1/48
Ethernet1/48 is up
admin state is up, Dedicated Interface
...
RX
7724 unicast packets  59832 multicast packets  0 broadcast packets
67556 input packets  8562626 bytes
0 jumbo packets  0 storm suppression bytes
0 runts  0 giants  0 CRC  0 Stomped CRC  0 no buffer
0 input error  0 short frame  0 overrun   0 underrun  0 ignored
0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
0 input with dribble  0 input discard
0 input buffer drop  0 input total drop
0 Rx pause
TX
87462 unicast packets  471164 multicast packets  1207793 broadcast packets
1766442 output packets  257533918 bytes
18 jumbo packets
23 output error  0 collision  0 deferred  0 late collision
0 lost carrier  0 no carrier  0 babble  0 output discard
0 output buffer drops  0 output total drops
0 Tx pause

data_switch-2# show interface Ethernet1/31
Ethernet1/31 is up
admin state is up, Dedicated Interface
...
RX
273949 unicast packets  2121655 multicast packets  298 broadcast packets
2395902 input packets  292674535 bytes
682 jumbo packets  0 storm suppression bytes
0 runts  0 giants  0 CRC  0 Stomped CRC  0 no buffer
0 input error  0 short frame  0 overrun   0 underrun  0 ignored
0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
0 input with dribble  0 input discard
0 input buffer drop  0 input total drop
0 Rx pause
TX
602784 unicast packets  10301779 multicast packets  29858428 broadcast packets
40763146 output packets  5398888609 bytes
111 jumbo packets
155 output error  0 collision  0 deferred  0 late collision
0 lost carrier  0 no carrier  0 babble  0 output discard
0 output buffer drops  0 output total drops
0 Tx paus

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.