![]() ![]() For more information, see Configuring Network Prioritization on a Failover Cluster. Make sure the cluster network isn't configured and that Allow cluster network communication on this network is selected. Open Windows PowerShell with Run as administrator and run the following cmdlet: Get-ClusterNetwork (0x000013AB).Ī cluster network isn't available for this operation. (0x000013AB)įailed to get the network address for the destination node "Host2": A cluster Network isn't available for this operation. Failed to get the network address for the destination node "Host2": A cluster Network isn't available for this operation. Make sure the VM has the same virtual switch on all nodes. Do the same for " Virtual Machine Configuration VM1. On the bottom tab, select Resource, right-click Virtual MachineVM1, select the Advanced Policies tab. The owner node must have all cluster nodes.Īlternatively, open the Failover Cluster Manager (FCM) under roles, select the virtual machine like shown in the following screenshot. Get-clusterResource -name "Virtual Machine Configuration VM1" | Get-clusterOwnerNode.Get-clusterResource -name "Virtual Machine VM1" | Get-clusterOwnerNode.Open Windows PowerShell with Run as administrator, and run the following cmdlets: The operation failed because either the specified cluster node isn't the owner of the group, or the node isn't a possible owner of the group.Ġx1398 5016 ERROR_HOST_NODE_NOT_GROUP_OWNER If a virtual machine is connected to a virtual switch that doesn't exist on the destination node, then live migration fails at Information details > Show details. The virtual switch must have the same name on all nodes. VM failed to live migrate because a virtual switch used by the VM doesn't exist on the destination node "Host2". Event ID 21502 Information regarding Event ID 21502 Live migration failed because a virtual switch used by the VM doesn't exist on the destination node "Host2" ![]() Next, find the event IDs that you encounter during live migration issue from the following sections. The file must start with the PReg signature.Ĭompare permissions on the folders containing the virtual machines files with a working host with the same operating system level. Run notepad and open C:\Windows\System32\GroupPolicy\Machine\Registry.pol. For more information, see Recommended antivirus exclusions for Hyper-V hosts.Ĭheck the corruption of the Registry.pol file: Open Create symbolic links and check whether the following user accounts are listed:Ĭheck for the antivirus exclusions. ![]() Open GPEDIT.MSC and navigate to Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment.Verify that the following policy have at least the default settings. For example: Compare-VM -Name -DestinationHost Ĭheck whether any group policy object is preventing the migration from occurring. Provide the name of the VM and the destination host. Update the BIOS, firmware and third party drivers.Ĭheck whether the virtual machines have the latest matching integration services.Ĭheck whether the migration is authorized on each side.Ĭheck whether the protocol used is identical on each side.Ĭheck whether the TCP Port 66 (for clustering) are listening on both sides.Ĭheck compatibilities issues by running a Compare-VM command. This article provides information on solving the issues when live migrating virtual machines.Īpplies to: Windows Server Original KB number: 4558514 Basic troubleshooting checklistĬheck the hosts are at the same level of patching and whether they can update to the latest rollup. ![]()
0 Comments
Leave a Reply. |