forward-itdept
asked on
Add rebuild cluster node back to the Windows cluster
Hi
We had a problem with one of servers in our 2 node Windows 2008 R2 Core cluster Hyper-V setup.
The cluster runs on a iSCSI SAN. The node ended up not being able to start the cluster service and appears as down in the cluster.
As the node was having other issues we have done a fresh install and rebuild of the server.
The server is configured the same with same name and IP address.
How do I add it back into the cluster, the node is still showing in the cluster manager as down.
Do I evict and re-add. First time we have had to do this so want to know correct procedure as we have all our VMs running on one node at the moment.
Thanks for your help
We had a problem with one of servers in our 2 node Windows 2008 R2 Core cluster Hyper-V setup.
The cluster runs on a iSCSI SAN. The node ended up not being able to start the cluster service and appears as down in the cluster.
As the node was having other issues we have done a fresh install and rebuild of the server.
The server is configured the same with same name and IP address.
How do I add it back into the cluster, the node is still showing in the cluster manager as down.
Do I evict and re-add. First time we have had to do this so want to know correct procedure as we have all our VMs running on one node at the moment.
Thanks for your help
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi
I have tried that. Evicted it successfully and then have tried several times to add it with this error:
Configuring node HOST2
--------------------------
12% Validating cluster state on node HOST2.
25% Getting current node membership of cluster cluster01.
37% Adding node HOST2 to Cluster configuration data.
50% Validating installation of the Microsoft Failover Cluster Virtual Adapter o
n node HOST2.This phase has failed for Cluster object 'HOST2' with an error stat
us of 1062 (0x00000426).
Cleaning up HOST2.
System error 1062 has occurred (0x00000426).
The service has not been started.
I have tried that. Evicted it successfully and then have tried several times to add it with this error:
Configuring node HOST2
--------------------------
12% Validating cluster state on node HOST2.
25% Getting current node membership of cluster cluster01.
37% Adding node HOST2 to Cluster configuration data.
50% Validating installation of the Microsoft Failover Cluster Virtual Adapter o
n node HOST2.This phase has failed for Cluster object 'HOST2' with an error stat
us of 1062 (0x00000426).
Cleaning up HOST2.
System error 1062 has occurred (0x00000426).
The service has not been started.
Can you please confirm that the Failover adapter is installed on the failing node?
Open up device manager, Expand Device Manager, and look for 'Microsoft Failover cluster virtual Adapter"
http://blogs.technet.com/b/askcore/archive/2009/02/13/what-is-a-microsoft-failover-cluster-virtual-adapter-anyway.aspx
Open up device manager, Expand Device Manager, and look for 'Microsoft Failover cluster virtual Adapter"
http://blogs.technet.com/b/askcore/archive/2009/02/13/what-is-a-microsoft-failover-cluster-virtual-adapter-anyway.aspx
ASKER
I have just checked and it is installed on the live node (host1) but the node I am trying to add (host2) doesnt have it, how do I enable it?
Thanks for your help
Craig
Thanks for your help
Craig
Hyper-V is currently installed on your second node correct?
I forgot to mention that the entry may be hidden, and you may need to 'Show hidden devices' to see it.
An IPCONFIG /ALL would confirm if its installed or not.
How was this OS reinstalled? From a backup? Just a clean OS? Not Sysprep'd?
Lets also give this a shot - it may be that there is a naming conflict here.
1. Open Registry Editor.
2. Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\
3. Under this subkey, find the subkey that holds a DriverDesc string value entry whose value is "Microsoft Failover Cluster Virtual Adapter."
4. Under the subkey that you found in step 3, add the following string value registry entry:
Name: DatalinkAddress
Value data: 02-AA-BB-CC-DD-01
5. Restart the computer.
6. Repeat step 1 through step 5 on other computers on which you experience this problem. When you do this on other computers, replace the value data of the registry with different values in order to set a unique value for each node. For example, set the value on the second node to 02-AA-BB-CC-DD-02, and set value on the third node to 02-AA-BB-CC-DD-03. If you notice this behavior on distinct clusters, make sure that you use an address for each node that is unique across all clusters.
I forgot to mention that the entry may be hidden, and you may need to 'Show hidden devices' to see it.
An IPCONFIG /ALL would confirm if its installed or not.
How was this OS reinstalled? From a backup? Just a clean OS? Not Sysprep'd?
Lets also give this a shot - it may be that there is a naming conflict here.
1. Open Registry Editor.
2. Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\
3. Under this subkey, find the subkey that holds a DriverDesc string value entry whose value is "Microsoft Failover Cluster Virtual Adapter."
4. Under the subkey that you found in step 3, add the following string value registry entry:
Name: DatalinkAddress
Value data: 02-AA-BB-CC-DD-01
5. Restart the computer.
6. Repeat step 1 through step 5 on other computers on which you experience this problem. When you do this on other computers, replace the value data of the registry with different values in order to set a unique value for each node. For example, set the value on the second node to 02-AA-BB-CC-DD-02, and set value on the third node to 02-AA-BB-CC-DD-03. If you notice this behavior on distinct clusters, make sure that you use an address for each node that is unique across all clusters.
If taking an outage for a 'test' idea isn't easy for you to do either, a sure fire fix would be to schedule a short outage for systems, and remove Failover-Clustering from both nodes, then reinstall Failover clustering on both nodes.
ASKER
Hi
Thanks for your help, actually sorted it now and got it joined back to the cluster this morning.
The failover adapter wasnt installed at all on the failing node and the registry key didn't even exist. It was a clean install following the same instal procedure when we originally setup the cluster. Unistalling and re-installing cluster service didnt help either. After more searching I found the below post which was the same issue I was having. It seemed the HP driver pack for our servers caused an issue with the adapter being created if it was installed before clustering is enabled. I reinstalled again from scratch and enabled Hyper-V and clustering and installed drivers last and everything worked fine.
http://social.technet.microsoft.com/Forums/en-US/winserverClustering/thread/c8166e14-f1c0-4797-bc58-5f0742069d1d/
Thanks for your help, actually sorted it now and got it joined back to the cluster this morning.
The failover adapter wasnt installed at all on the failing node and the registry key didn't even exist. It was a clean install following the same instal procedure when we originally setup the cluster. Unistalling and re-installing cluster service didnt help either. After more searching I found the below post which was the same issue I was having. It seemed the HP driver pack for our servers caused an issue with the adapter being created if it was installed before clustering is enabled. I reinstalled again from scratch and enabled Hyper-V and clustering and installed drivers last and everything worked fine.
http://social.technet.microsoft.com/Forums/en-US/winserverClustering/thread/c8166e14-f1c0-4797-bc58-5f0742069d1d/
ASKER