メインコンテンツへスキップ

MTUの不一致が原因でvifmgr.cluscheck.crcerrorsアラートとifstatが長いフレームを受信

Views:
305
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

環境

  • ONTAP 9
  • ネットワーク
  • 最大伝送ユニット(MTU)

問題

  • ifstat ポートが長いフレームを受信していることを示します。

::>system node run -node Node1 -command ifstat e1d
-- interface  e1d  (5 days, 13 hours, 44 minutes, 30 seconds) --
RECEIVE
 Total frames:    438k | Frames/second:     1  | Total bytes:    32232k
 Bytes/second:     67  | Total errors:   32047 | Errors/minute:     4 
 Total discards:    0  | Discards/minute:    0  | Multi/broadcast:   561k
 Non-primary u/c:    0  | CRC errors:      0  | Runt frames:      0 
 Long frames:    32047 | Length errors:     0  | Alignment errors:   0 
 No buffer:       0  | Pause:         0  | Jumbo:         0 
 Noproto:        0  | Bus overruns:     0  | LRO segments:     0 
 ...

  • ONTAPのバージョンに応じて、次のいずれかのイベントが繰り返しEMSに記録されます。
    • [Node1: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e1d on node Node1 is reporting a high number of observed CRC errors.
    • [Node1: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e1d on node Node1 is reporting a high number of observed hardware errors, possibly CRC errors.
    • [Node1: vifmgr: vifmgr.cluscheck.hwerrors:alert]: Port e1d on node Node1 is reporting a high number (at least 1 per 1000 packets) of observed hardware errors (CRC, length, alignment, dropped).
    • [Node-01: vifmgr: callhome.clus.net.degraded:alert]: Call home for CLUSTER NETWORK DEGRADED: Large MTU Packet Loss - Ping failures detected between lif_clus1 ( 169.254.231.150 ) on Node-01 and Lif_clus1 ( 169.254.30.145 ) on Node-01
  • スイッチポートが長いフレームを送信しています

switch# show interface eth0/10
Ethernet0/10 is up
  RX
   0 jumbo packets  0 storm suppression bytes
 TX
  32047 jumbo packets

  • MTUがジャンボフレームサイズより小さい値に設定されている

::> net port show -fields mtu,broadcast-domain  -node Node1 -port e1d
  (network port show)
node      port mtu broadcast-domain
------------ ---- ---- ----------------
Node1     e1d  1500 Default

 

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.