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

クラスターポートe0aダウン時のHyper-V VMハング

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

環境

  • AFF-A300
  • ONTAP 9.13.1P9
  • Hyper-V
  • SMB3

問題

  • 一部の仮想マシン(VM)で、node-3のクラスタ ポートe0aでの予期しない停止イベントが原因でハング(IOのフリーズ)が発生しました
  • 影響を受けたVMは、node-3のデータLIFとクラスタ ネットワークを介してnode-4に間接的に接続されていました
  • クラスタノード間の部分的なパケット損失:
Fri Oct 17 19:38:21 [node-3: vifmgr: vifmgr.cluscheck.droppedlarge:alert]: Partial packet loss when pinging from cluster lif node-3_clus1 (node node-3) to cluster lif node-4_clus4 (node cluster-4).
  • CIFSロック状態の不一致
Fri Oct 17 19:38:40 [node-3:kernel:Nblade.cifsLockStateMismatch:debug]: params:{'pMessage':'Leaked share lock?'}
  • ノード3のクラスタ ポートe0aが停止しています:
Fri Oct 17 19:39:22 [node-3:kernel:netif.linkDown:info]: Ethernet e0a: Link down, check cable.
Fri Oct 17 19:39:22 [node-3:vifmgr:vifmgr.portdown:notice]: A link down event was received on node node-3, port e0a.
Fri Oct 17 19:39:22 [node-3:vifmgr:vifmgr.clus.linkdown:EMERGENCY]: The cluster port e0a on node node-3 has gone down unexpectedly.
  • IOの遅延(ただしSRB_STATUS_SUCCESS)を示すWindows Hyper-Vイベントログ:
Warning 2025-10-17 19:38:40
'...CA-OP-xxxxxx-N_C.vhdx' I/O request completed in 25406ms, status=SRB_STATUS_SUCCESS.
  • VMのリカバリには強制終了とホストの再起動が必要でした

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.