Hyper-V VM hang during cluster port e0a down
Applies to
- AFF-A300
- ONTAP 9.13.1P9
- Hyper-V
- SMB3
Issue
- Some virtual machines(VM) experienced a hang (IO freeze) around an unexpected down event on cluster port e0a of node-3
- The affected VMs were indirectly connected to node-4 through node-3's data LIF and cluster networks
- Partial packet loss between cluster nodes:
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 lock state mismatch
Fri Oct 17 19:38:40 [node-3:kernel:Nblade.cifsLockStateMismatch:debug]: params:{'pMessage':'Leaked share lock?'}- Cluster port e0a down on node 3:
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.- Windows Hyper-V event logs showing IO delays (but SRB_STATUS_SUCCESS):
Warning 2025-10-17 19:38:40'...CA-OP-xxxxxx-N_C.vhdx' I/O request completed in 25406ms, status=SRB_STATUS_SUCCESS.- VMs required forced termination and host reboot to recover