Hi,
To troubleshoot the live migration issue, you can follow these steps:
1. Check Virtual Switch Configuration: Ensure that the virtual switch used by the VM exists on all nodes and has the same name and settings. Open the Hyper-V Manager console, select Virtual Switch Manager, and verify the virtual switch configuration.
2. Verify Cluster Network Configuration: Ensure that the cluster network is configured correctly and that Allow cluster network communication on this network is selected. Run the following PowerShell cmdlet to check the cluster network:
Get-ClusterNetwork
Make sure the network is available for the operation.
3. Check Cluster Node Ownership: Verify that the specified cluster node is the owner of the group or a possible owner. Use the following PowerShell cmdlets to check the owner node:
Get-clusterResource -name "Virtual Machine VM1" | Get-clusterOwnerNode
Get-clusterResource -name "Virtual Machine Configuration VM1" | Get-clusterOwnerNode
Alternatively, use the Failover Cluster Manager to check the advanced policies and ensure all nodes are selected.
4. Firewall and Antivirus Settings: Ensure that the necessary TCP ports (6600 and 3343) are open and listening on both sides. Check the firewall settings and antivirus exclusions. Run the following cmdlet to check the ports:
netstat -ano | findstr /I /C:"6600"
5. Network Management: Ensure that the network management settings are correctly configured for migration. If using a stretched VLAN, ensure it includes all nodes of the cluster.