跳转到主内容

CRC错误未在EMS中触发警报

Views:
5
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core<a>2009899752</a>
Last Updated:

适用场景

ONTAP 9

问题描述

  • ifstat输出显示大量CRC错误。

Cluster::> node run -node Node-01 ifstat e4a

-- interface  e4a  (21 days, 20 hours, 30 minutes, 17 seconds) --

RECEIVE
Total frames:    1163m | Frames/second:    616  | Total bytes:    2013g
Bytes/second:    1066k | Total errors:   28738  | Errors/minute:     1
 Total discards:    0  | Discards/minute:    0  | Multi/broadcast:  5035k
Non-primary u/c:    0  | Errored frames:    0  | Unsupported Op:    0
 CRC errors:    28646 | Runt frames:      0  | Fragment:       0
 Long frames:      0  | Jabber:        92  | Length errors:     0
 Alignment errors:   0  | No buffer:       0  | Pause:         0
 Jumbo:        230m | Error symbol:     0  | Bus overruns:     0
 Queue drops:      0  | LRO segments:    947m | LRO bytes:     1993g
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

  • 但是、EMS中不会针对这些错误生成任何警报。
 

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.