The Hyper-V manager in the cluster cannot remotely manage VMS on other nodes/migration exceptions.

The Hyper-V manager in the cluster cannot remotely manage VMS on other nodes/migration exceptions.

In the production environment, due to various factors, there may be potential unknown risks of "planting trees and filling traps for future generations. When an inexplicable fault occurs, you cannot find the root cause after trying various troubleshooting methods. The error is in the lower right corner. Soga. The so-called "thousands of queries, all because of time ".

Environment

Hyper-V cluster with four nodes

Fault symptom

Hyper-V manager cannot remotely manage all Hyper-V

Some VMS in the cluster cannot be migrated successfully.

Fault Cause

Inconsistent cluster node time

Detailed description and troubleshooting Process

 

Hyper-V manager cannot remotely manage all Hyper-V instances in the cluster.

1. Operation on the computer failed.

   Unable to connect to the computer RPC service. Make sure that the RPC service runs properly.

   When you create a test VM, an alarm is displayed, "the node cannot be verified because the valid host for this application/service is"

   View reports

   The VM can be created normally, but when trying to migrate the VM.

   During VM migration between different nodes in the same group, an error occurred while starting VM migration ." View the details "You cannot connect to the node host Through WMI. The cause may be a network problem or a specific security package error occurs in the firewall configuration on the node host. (Exception from HRESULT: 0x80070721 )"

   After another node tries to migrate the created VM to the (04 host), it tries to migrate the VM and finds that the Migration fails. In the test, if more VMS are migrated, 04 nodes cannot be migrated to any VM to the other three nodes.

    

   View Hyper-V logs. The Log Path is Microsoft-Windows-Hyper-V-High-Availability/Admin.

   Log name: Microsoft-Windows-Hyper-V-High-Availability-Admin Source: Microsoft-Windows-Hyper-V-VMMS Date: 2015/12/1717: 07: 27 event ID: 22012 task category: NO level: Error Keyword: User: SYSTEM Computer: Description: Unable to authenticate remote nodes: the clock on the client and server computer is inconsistent. (0x80090324)

   View the time of four nodes

   w32tm/query/source

   Check the time synchronization source. It is empty.

   nettime\\IP/set

   Manually specify the time source server

   After the setting is successful, the VM can be migrated successfully.

   Appendix: Microsoft Hyper-V cluster Operation Manual (Part)

   Procedure for configuring High Availability of virtual machines

   • Make sure that the Hyper-V role is installed.

     If the "failover Cluster Manager" management unit does not display the cluster to be configured, right-click "failover Cluster Manager" in the console tree and click "manage cluster ", select or specify the required cluster.

     If the console tree is collapsed, expand the tree under the cluster to be configured.

     Click services and applications ".

     If you have created a virtual machine, skip to Step 6. Otherwise, use the new Virtual Machine Wizard to create a virtual machine and configure high availability for it:

     1. In the operations pane, click virtual machines, point to virtual machines, and click a node. A virtual machine will be created on the node and added to the cluster so that it can be moved to one or more nodes as needed.

        If the "before start" page of The New VM wizard is displayed, click "Next ".

        Specify the name of the VM, select "store the VM in another location", specify a disk in the shared storage, or if the cluster shared volume is enabled, specify a cluster shared volume (the volume should be located in the \ ClusterStorage folder on the node's system drive ).

        Follow the instructions in the Wizard. You can specify details (such as memory size, network, and virtual hard disk files) or add or modify configuration details later.

        Click Finish. The Wizard creates a virtual machine and configures high availability for it. Skip the remaining steps.

        If you have created a virtual machine and only need to configure high availability for it, first make sure that the virtual machine is not running. Then, use the high availability Wizard to configure the high availability of the virtual machine:

        1. In the actions pane, click Configure service or application ".

           If the "before start" page of the high availability wizard is displayed, click "Next ".

           On the "Select Service or application" page, click "Virtual Machine" and then click "Next ".

           Select the Virtual Machine for which you want to configure high availability, and then complete the wizard.

           When running in the high availability wizard and displaying the "summary" page, click "View Report" if you want to view the report of the tasks executed by the wizard ".

           Procedure for testing the Failover of a cluster Virtual Machine

           1. If the "failover Cluster Manager" management unit does not display the cluster to be configured, right-click "failover Cluster Manager" in the console tree and click "manage cluster ", select or specify the required cluster.

              If the console tree is collapsed, expand the tree under the cluster to be configured.

              Expand virtual machine, and click the virtual machine to test failover.

              Under "operation" (on the right), click "move virtual machine to another node ". When the VM moves, the status is displayed in the result pane (center pane.

              (Optional) Repeat Step 4 to move the VM to another node or to the original node.