How to add a new or rebuilt cluster node to SCVMM 2008

re: How to add a new or rebuilt cluster node to SCVMM 2008

Steve TH - MSFT — Fri, 16 Sep 2011 22:17:11 GMT

This method ensures there is quick synchronicity between the configuration state in both Hyper-v and Failover clustering and the VMM datastore (which is is where the console pulls from initially and updates based upon state changes in the environment.

re: How to add a new or rebuilt cluster node to SCVMM 2008

Larry — Mon, 05 Sep 2011 13:37:22 GMT

@Kare you say all of the VM's go into the Unsupported Cluster Configuration?

Are you adding a new node? Or are you re-adding a node that has VM's on it.

I would assume that before you added it to either SCVMM or to the cluster you would have to have everything exactly the same as the other nodes, networks etc.

I just want to know which way is recomended or if it does not matter are there any things NOT to do.

re: How to add a new or rebuilt cluster node to SCVMM 2008

Kåre Overgård — Wed, 15 Jun 2011 17:18:05 GMT

Actually, when we use the steps you outline here, all the VMs go into the "Unsupported Cluster Configuration" status when the second node is added. While in this status, no management of the VMs are possible.

This is due to the fact that the networks defined on the first Hyper-V Host are not configured yet on the second Hyper-V Host.

We have found it preferably to:

1. Add the new host to VMM

2. Define all networks on the new host the same as the other hosts in the cluster.

3. Add the new host to the cluster using Failover Cluster Manager

VMM automatically moves the host from a standalone host as now being part of the cluster, and the VMs doesn't end up with the "Unsupported Cluster Configuration" status.