[Cluster] Cluster Hyper-V Manager cannot remotely manage other nodes vm/migration exception

Environment

4 nodes of the Hyper-V cluster

Failure phenomena

1. Hyper -V Manager cannot remotely manage all

2. VM Unable to successfully migrate

Cause of failure

Cluster node Time inconsistency

Detailed description and troubleshooting procedures

Hyper - V Manager cannot remotely administer all of the clusters in the cluster Hyper-V,

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M00/78/35/wKioL1Z35YPRooJ-AAF1pV8iTcM478.png "title=" Hyper-V Manager cannot manage Hyper-v.png "alt=" Wkiol1z35yprooj-aaf1pv8itcm478.png "/> on a node in the cluster

Create a test VMS When an alert appears

650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M02/78/35/wKioL1Z35ZjBt_WPAAB2K2_f1Ec739.png "title=" An alert appears when you create a test VM. png "alt=" Wkiol1z35zjbt_wpaab2k2_f1ec739.png "/>

View Reports

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M01/78/35/wKioL1Z35ayj-e2zAACL0J7dbD0013.png "title=" View the report. png "alt=" Wkiol1z35ayj-e2zaacl0j7dbd0013.png "/>

VMS is created normally, but when you try to migrate VMS time.

migrating between different nodes in the same cluster VMS occurs when the start VMS migration error. "View Details" cannot Connect to the node host through WMI. This can be caused by a network problem or a specific security package error in the firewall configuration on the node host. (Exception from hresult:0x80070721) "

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M02/78/37/wKiom1Z35cyySVjVAABEEMwJvSE238.png "title=" Error initiating VM migration. png "alt=" Wkiom1z35cyysvjvaabeemwjvse238.png "/>

The other nodes will have created the VMS after attempting to migrate to (04 hosts), after attempting to fetch, found unable to fetch successfully, in testing more VMS migration Yes, discover Geneva the node cannot migrate any VMS to the other 3 nodes.

View Hyper-V log, log path microsoft-windows-hyper-v-high-availability/admin

 650) this.width=650, "src=" Http://s3.51cto.com/wyfs02/M02/78/36/wKioL1Z35e_j6e2sAACFGIg_9D8172.png "title=" The clocks on the client and server computers are inconsistent. png "alt=" Wkiol1z35e_j6e2saacfgig_9d8172.png "/>

Journal name: Microsoft-windows-hyper-v-high-availability-admin Source: Microsoft-windows-hyper-v-vmms Date:           2015/12/17 17:07:27 Event id:22012 task Category: No level: Error keyword: User: System computer: Description: Unable to authenticate the remote node: The clocks on the client and server computers are inconsistent. (0x80090324)

View 4 the time of a node

650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M02/78/37/wKiom1Z35fSxyipmAABwNgEYoT8573.png "title=" View the time of 4 nodes. png "alt=" Wkiom1z35fsxyipmaabwngeyot8573.png "/>

W32tm/query/source

Check the time synchronization source, incredibly empty

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M00/78/37/wKiom1Z35gXTdQCAAAAbZb-rRQo530.png "title=" Check the time synchronization source. png "alt=" Wkiom1z35gxtdqcaaaabzb-rrqo530.png "/>

NET time \\ip/set

Manually specifying a time source server

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M00/78/36/wKioL1Z35iPQD_qJAAAfFNlbqO4914.png "title=" Manually specify the time source server. png "alt=" Wkiol1z35ipqd_qjaaaffnlbqo4914.png "/>

after the setup is successful, VMS can be migrated successfully.

attached: Microsoft Official Hyper-V Cluster Operations Manual (partial)

To configure high availability for a virtual machine

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

4. if the cluster that you want to configure does not appear in the Failover Cluster Manager snap-in, right-click in the console tree Failover Cluster Manager ", click" managing clusters , and then select or specify the cluster that you want.

6. If the console tree is collapsed, expand the tree below the cluster you want to configure.

8. Click "Services and Applications" .

9. 2. ' action ' pane, click ' virtual machine ' , point to           &NBSP
                  The virtual machine is initially created on that node and then added to the cluster so that it can root It is necessary to move it to one or more nodes.

   4. If the new Virtual Machine Wizard is displayed "Before you Begin" page, click "Next" .

   6. specify a name for the virtual machine, and then select "Store the virtual machine in a different location" and specify a disk in the shared storage, or if the cluster shared volume is enabled, specify a cluster shared volume (which should be located on the system drive of the node \ClusterStorage the volume under the folder).

   8. Follow the instructions in the wizard. You can now specify details such as memory size, network and virtual hard disk files, or you can add or change configuration details at a later time.

   10. Click "Done" , the wizard creates the virtual machine and configures it for high availability. Skip the remaining steps of this procedure.

10. If you have created a virtual machine and only need to configure it for high availability, 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:

    2. in the "Action" pane, click "Configure services or applications" .

    4. If the High Availability Wizard is displayed "Before you Begin" page, click "Next" .

    6. in the "Select a service or application" page, click "Virtual machine" , and then click "Next" .

    8. Select the virtual machine for which you want to configure high availability, and then complete the wizard.

    10. run in the High Availability Wizard and display "Summary" page, if you want to view a report about the tasks that the wizard is performing, click "View Report" .
        

To test failover of a clustered virtual machine

2. if the cluster that you want to configure does not appear in the Failover Cluster Manager snap-in, right-click in the console tree Failover Cluster Manager ", click" managing clusters , and then select or specify the cluster that you want.

4. If the console tree is collapsed, expand the tree below the cluster you want to configure.

6. Expand "Virtual machine" , and then click the virtual machine that you want to test for failover.

8. in the "Action" (on the right), click "move a virtual machine to another node" .
   As the virtual machine moves, the status is displayed in the Results pane (the center pane).

10. (optional) Repeat step 4 to move the virtual machine to another node or back to the original node.

This article from "Heart" blog, reproduced please contact the author!

[Cluster] Cluster Hyper-V Manager cannot remotely manage other nodes vm/migration exception