Managing External Changes to Host Clusters

Applies To: Virtual Machine Manager 2008, Virtual Machine Manager 2008 R2, Virtual Machine Manager 2008 R2 SP1

When you add or remove nodes from a host cluster outside Virtual Machine Manager, VMM detects the change and in most cases indicates through status changes the action that is required in VMM.

When a Cluster Node Is Added

When a node is added to a host cluster outside VMM, VMM discovers the new node and adds the node to the cluster, with Pending Management status, in Hosts view. Until you add the host, if any highly available virtual machine on any other node in the host cluster fails over to the new node, the virtual machine has Missing status until the new node is added to VMM. Use the Add to host cluster action to add the host to VMM. For more information, see How to Add a Pending Host to VMM.

Note

After you add a node to an existing Hyper-V host cluster and then add the host to VMM, you must set the default remote connection port on the new host to port 2179, the remote connection port that Hyper-V uses. The property is on the Remote tab of the Host Properties dialog box.

When a Cluster Node Is Removed

VMM also detects when a node is removed from a host cluster outside VMM. In that case, VMM sets the Clustered property of the node to False and begins managing the host as a stand-alone host in the parent host group for the host cluster. Use the Remove host cluster action to remove the host from VMM. For more information, see How to Remove a Host.

Note

If you evict a node from a host cluster that has Performance and Resource Optimization (PRO) enabled and you want to continue to use PRO on the host, you must manually configure at least one default virtual machine path on the host for use during virtual machine placement. To specify default virtual machine paths, use the Placement tab in the Host Properties dialog box. For more information, see How to Set Placement Options for a Host.

See Also

Concepts

Managing Host Clusters