跳转到主内容

ONTAP 如何监控CRC?

Views:
13
Visibility:
Public
Votes:
0
Category:
not set
Specialty:
not set
Last Updated:

适用场景

  • 以太网协议。IEEE 802.3
  • CRC或帧检查序列

问题解答

  • 收到损坏的帧后、ONTAP 会报告CRC错误。

  • ifstat 输出和AutoSupport 部分:

::> system node run -node node-name ifstat e0c 
-- interface  e0c  (7 days, 18 hours, 10 minutes, 41 seconds) -- 
RECEIVE 
 Total frames:    508k | Frames/second:     1  | Total bytes:   37009k 
 Bytes/second:     55  | Total errors:   12117 | Errors/minute:     0 
 Total discards:    0  | Discards/minute:   0  | Multi/broadcast: 1280k 
 Non-primary u/c:   0  | CRC errors:     12117 | Runt frames:       0 
 Long frames:       0  | Length errors:     0  | Alignment errors:  0 
 No buffer:         0  | Pause:             0  | Jumbo:             0 
 ...

  • 事件消息和EMS AutoSupport 消息: 

Wed Jun 30 02:38:27 CEST [node-name: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e0c on node node-name is reporting a high number of observed hardware errors, possibly CRC errors.

  • 如果1000个帧中的帧数超过1个、则ONTAP 会在事件消息和EMS AutoSupport 消息中报告CRC错误。 

追加信息

  • CRC错误通常是由硬件故障或硬件不兼容引起的 
  • 网络交换机可能愿意转发错误的CRC帧
  • 数据包跟踪不有用 

 

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.

 

  • 这篇文章对您有帮助吗?