Server 2008 R2 Cluster Creation issues
Hello all,
I have been running a 3-node Server 2008 R1 Hyper-V Failover Cluster without issue for about as long as Server 2008 has been availible. With the release of R2, I removed one of the nodes and have been trying to get a new cluster setup to replace the production cluster. My setup is as follows:
Nodes:
Dell PowerEdge 2950
2 Quad Core Intel Xenon CPUs, 2.00 GHz
16-20 GB of RAM (2 at 16, on has 20)
2 mirrord SAS drives, 300 GB each
2 Onboard Broadcom BCM5708C NetXtreme II GigE NICs
2 Intel PRO/1000 PT Dual Port Server NICs, PCI-X
SAN:
Dell PowerVault MD3000i
The network configuration is tricky, to say the least. In brief, the Intel cards (total of 4 connections per node) are used for fully redundant iSCSI communications and each is setup on its own private network. The 2 onboard Broadcom NICs are used for public communications. Here is where I think my problem comes in, on my current production cluster I have these two NICs setup as a team with one as the primary and one as the secondary so it is purely a failover team, no load balancing. Hyper-V is then setup on top of this team. This has worked flawlessly for me for over a year now. Server 2008 R2, though, is giving me troubles.As I mentioned before, I removed one of my nodes from the production cluster and have been trying to setup a new cluster with R2. Everything installs just fine and I have even been able to setup and use the same network configurations as the production cluster, NIC teaming and all. However, when I go to create the one-node cluster, it always fails during creation. Here are the steps generated by the report (I have removed all name references):
· Beginning to configure the cluster <Cluster-Name>.
· Initializing Cluster <Cluster-Name>.
· Validating cluster state on node <Node 1>.
· Searching the domain for computer object ‘<Cluster-Name>’.
· Verifying computer object ‘<Cluster-Name>’in the domain.
· Configuring computer object ‘<Cluster-Name>’ as cluster name object.
· Validating installation of the Network FT Driver on node <Node 1>.
· Unable to successfully cleanup.
· To troubleshoot cluster creation problems, run the Validate a Configuration wizard on the servers you want to cluster.
An error occurred while creating the cluster.
An error occurred creating cluster 'SCS-Cluster'.
The service has not been started
As you can see, it is failing at the point ‘Validating installation of the Network FT Driver’. When I first tried this, I was setup with my NIC Team and everything so I wiped the node and reset it this time leaving out the NIC team but still installing the Broadcom driver from their website (I have also installed the Intel Driver for the PCI-X cards though nothing special is done with their configurations). In both cases, with or without the team, the cluster creation fails at the same place.
My question is, has anyone else been seeing these issues with Broadcom (or Intel) NIC drivers? I honestly don’t even know what it means by ‘Network FT Driver’ so would it be possible for someone to explain that a bit? Any and all help is greatly appreciated, I have been banging my head against the wall for quite some time trying to figure this out and have been scouring the internet for information on it but have yet to find what I am looking for.
Thanks,
Ryan Lenkersdorfer
‘Lenker'
Answers
I was able to get it to work with what I can only call a hack. I formatted the node and reinstalled R2. Then, before anything else except getting it joined to my domain and iSCSI setup, I created the cluster using the default MS drivers for all NICs. The cluster creation completed without any errors. Then after it was all up and running, I installed all the drivers and setup my NIC team then configured the cluster to use the new team, that all worked as well. I have it running now with the team in place and am running tests on it to see if it is stable, I am also worrying about when I add another node to the cluster and if I am going to have the same problems then.
Will continue to report what I find, again, if anyone has some deeper insight it would be much appreciated!- Marked As Answer byTim Quan - MSFTMSFT, ModeratorThursday, October 15, 2009 10:20 AM
Hello all,
I have been running a 3-node Server 2008 R1 Hyper-V Failover Cluster without issue for about as long as Server 2008 has been availible. With the release of R2, I removed one of the nodes and have been trying to get a new cluster setup to replace the production cluster. My setup is as follows:
Nodes:
Dell PowerEdge 2950
2 Quad Core Intel Xenon CPUs, 2.00 GHz
16-20 GB of RAM (2 at 16, on has 20)
2 mirrord SAS drives, 300 GB each
2 Onboard Broadcom BCM5708C NetXtreme II GigE NICs
2 Intel PRO/1000 PT Dual Port Server NICs, PCI-X
SAN:
Dell PowerVault MD3000i
The network configuration is tricky, to say the least. In brief, the Intel cards (total of 4 connections per node) are used for fully redundant iSCSI communications and each is setup on its own private network. The 2 onboard Broadcom NICs are used for public communications. Here is where I think my problem comes in, on my current production cluster I have these two NICs setup as a team with one as the primary and one as the secondary so it is purely a failover team, no load balancing. Hyper-V is then setup on top of this team. This has worked flawlessly for me for over a year now. Server 2008 R2, though, is giving me troubles.As I mentioned before, I removed one of my nodes from the production cluster and have been trying to setup a new cluster with R2. Everything installs just fine and I have even been able to setup and use the same network configurations as the production cluster, NIC teaming and all. However, when I go to create the one-node cluster, it always fails during creation. Here are the steps generated by the report (I have removed all name references):
· Beginning to configure the cluster <Cluster-Name>.
· Initializing Cluster <Cluster-Name>.
· Validating cluster state on node <Node 1>.
· Searching the domain for computer object ‘<Cluster-Name>’.
· Verifying computer object ‘<Cluster-Name>’in the domain.
· Configuring computer object ‘<Cluster-Name>’ as cluster name object.
· Validating installation of the Network FT Driver on node <Node 1>.
· Unable to successfully cleanup.
· To troubleshoot cluster creation problems, run the Validate a Configuration wizard on the servers you want to cluster.
An error occurred while creating the cluster.
An error occurred creating cluster 'SCS-Cluster'.
The service has not been started
As you can see, it is failing at the point ‘Validating installation of the Network FT Driver’. When I first tried this, I was setup with my NIC Team and everything so I wiped the node and reset it this time leaving out the NIC team but still installing the Broadcom driver from their website (I have also installed the Intel Driver for the PCI-X cards though nothing special is done with their configurations). In both cases, with or without the team, the cluster creation fails at the same place.
My question is, has anyone else been seeing these issues with Broadcom (or Intel) NIC drivers? I honestly don’t even know what it means by ‘Network FT Driver’ so would it be possible for someone to explain that a bit? Any and all help is greatly appreciated, I have been banging my head against the wall for quite some time trying to figure this out and have been scouring the internet for information on it but have yet to find what I am looking for.
Thanks,
Ryan Lenkersdorfer
‘Lenker'
Hi,
Please read this:
http://eniackb.blogspot.com/2009/10/windows-2008-r2-problems-with-hp.html
Although is related with HP server, the same may happen in DELL servers.
I hope that the information above helps you. This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.- Marked As Answer byTim Quan - MSFTMSFT, ModeratorThursday, October 15, 2009 10:20 AM
- Proposed As Answer bynrdfeeling Thursday, October 15, 2009 10:07 AM
All Replies
- I have exactly the same problem, except that I'm using HP servers and FC. In my setup I already tried with Team on, Team Off, I also updated the Drivers for the Broadcom NICs. I also have Intel NIC and tried on those NICs and the error is the same!!!!
I'm not using SCSI, I'm using FC. I already reinstalled the system, performed enumerous tests but with no success. Before r2 I also had 2008 without issues.
Anyone... I was able to get it to work with what I can only call a hack. I formatted the node and reinstalled R2. Then, before anything else except getting it joined to my domain and iSCSI setup, I created the cluster using the default MS drivers for all NICs. The cluster creation completed without any errors. Then after it was all up and running, I installed all the drivers and setup my NIC team then configured the cluster to use the new team, that all worked as well. I have it running now with the team in place and am running tests on it to see if it is stable, I am also worrying about when I add another node to the cluster and if I am going to have the same problems then.
Will continue to report what I find, again, if anyone has some deeper insight it would be much appreciated!- Marked As Answer byTim Quan - MSFTMSFT, ModeratorThursday, October 15, 2009 10:20 AM
Hello all,
I have been running a 3-node Server 2008 R1 Hyper-V Failover Cluster without issue for about as long as Server 2008 has been availible. With the release of R2, I removed one of the nodes and have been trying to get a new cluster setup to replace the production cluster. My setup is as follows:
Nodes:
Dell PowerEdge 2950
2 Quad Core Intel Xenon CPUs, 2.00 GHz
16-20 GB of RAM (2 at 16, on has 20)
2 mirrord SAS drives, 300 GB each
2 Onboard Broadcom BCM5708C NetXtreme II GigE NICs
2 Intel PRO/1000 PT Dual Port Server NICs, PCI-X
SAN:
Dell PowerVault MD3000i
The network configuration is tricky, to say the least. In brief, the Intel cards (total of 4 connections per node) are used for fully redundant iSCSI communications and each is setup on its own private network. The 2 onboard Broadcom NICs are used for public communications. Here is where I think my problem comes in, on my current production cluster I have these two NICs setup as a team with one as the primary and one as the secondary so it is purely a failover team, no load balancing. Hyper-V is then setup on top of this team. This has worked flawlessly for me for over a year now. Server 2008 R2, though, is giving me troubles.As I mentioned before, I removed one of my nodes from the production cluster and have been trying to setup a new cluster with R2. Everything installs just fine and I have even been able to setup and use the same network configurations as the production cluster, NIC teaming and all. However, when I go to create the one-node cluster, it always fails during creation. Here are the steps generated by the report (I have removed all name references):
· Beginning to configure the cluster <Cluster-Name>.
· Initializing Cluster <Cluster-Name>.
· Validating cluster state on node <Node 1>.
· Searching the domain for computer object ‘<Cluster-Name>’.
· Verifying computer object ‘<Cluster-Name>’in the domain.
· Configuring computer object ‘<Cluster-Name>’ as cluster name object.
· Validating installation of the Network FT Driver on node <Node 1>.
· Unable to successfully cleanup.
· To troubleshoot cluster creation problems, run the Validate a Configuration wizard on the servers you want to cluster.
An error occurred while creating the cluster.
An error occurred creating cluster 'SCS-Cluster'.
The service has not been started
As you can see, it is failing at the point ‘Validating installation of the Network FT Driver’. When I first tried this, I was setup with my NIC Team and everything so I wiped the node and reset it this time leaving out the NIC team but still installing the Broadcom driver from their website (I have also installed the Intel Driver for the PCI-X cards though nothing special is done with their configurations). In both cases, with or without the team, the cluster creation fails at the same place.
My question is, has anyone else been seeing these issues with Broadcom (or Intel) NIC drivers? I honestly don’t even know what it means by ‘Network FT Driver’ so would it be possible for someone to explain that a bit? Any and all help is greatly appreciated, I have been banging my head against the wall for quite some time trying to figure this out and have been scouring the internet for information on it but have yet to find what I am looking for.
Thanks,
Ryan Lenkersdorfer
‘Lenker'
Hi,
Please read this:
http://eniackb.blogspot.com/2009/10/windows-2008-r2-problems-with-hp.html
Although is related with HP server, the same may happen in DELL servers.
I hope that the information above helps you. This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.- Marked As Answer byTim Quan - MSFTMSFT, ModeratorThursday, October 15, 2009 10:20 AM
- Proposed As Answer bynrdfeeling Thursday, October 15, 2009 10:07 AM
Hello all,
I have been running a 3-node Server 2008 R1 Hyper-V Failover Cluster without issue for about as long as Server 2008 has been availible. With the release of R2, I removed one of the nodes and have been trying to get a new cluster setup to replace the production cluster. My setup is as follows:
Nodes:
Dell PowerEdge 2950
2 Quad Core Intel Xenon CPUs, 2.00 GHz
16-20 GB of RAM (2 at 16, on has 20)
2 mirrord SAS drives, 300 GB each
2 Onboard Broadcom BCM5708C NetXtreme II GigE NICs
2 Intel PRO/1000 PT Dual Port Server NICs, PCI-X
SAN:
Dell PowerVault MD3000i
The network configuration is tricky, to say the least. In brief, the Intel cards (total of 4 connections per node) are used for fully redundant iSCSI communications and each is setup on its own private network. The 2 onboard Broadcom NICs are used for public communications. Here is where I think my problem comes in, on my current production cluster I have these two NICs setup as a team with one as the primary and one as the secondary so it is purely a failover team, no load balancing. Hyper-V is then setup on top of this team. This has worked flawlessly for me for over a year now. Server 2008 R2, though, is giving me troubles.As I mentioned before, I removed one of my nodes from the production cluster and have been trying to setup a new cluster with R2. Everything installs just fine and I have even been able to setup and use the same network configurations as the production cluster, NIC teaming and all. However, when I go to create the one-node cluster, it always fails during creation. Here are the steps generated by the report (I have removed all name references):
· Beginning to configure the cluster <Cluster-Name>.
· Initializing Cluster <Cluster-Name>.
· Validating cluster state on node <Node 1>.
· Searching the domain for computer object ‘<Cluster-Name>’.
· Verifying computer object ‘<Cluster-Name>’in the domain.
· Configuring computer object ‘<Cluster-Name>’ as cluster name object.
· Validating installation of the Network FT Driver on node <Node 1>.
· Unable to successfully cleanup.
· To troubleshoot cluster creation problems, run the Validate a Configuration wizard on the servers you want to cluster.
An error occurred while creating the cluster.
An error occurred creating cluster 'SCS-Cluster'.
The service has not been started
As you can see, it is failing at the point ‘Validating installation of the Network FT Driver’. When I first tried this, I was setup with my NIC Team and everything so I wiped the node and reset it this time leaving out the NIC team but still installing the Broadcom driver from their website (I have also installed the Intel Driver for the PCI-X cards though nothing special is done with their configurations). In both cases, with or without the team, the cluster creation fails at the same place.
My question is, has anyone else been seeing these issues with Broadcom (or Intel) NIC drivers? I honestly don’t even know what it means by ‘Network FT Driver’ so would it be possible for someone to explain that a bit? Any and all help is greatly appreciated, I have been banging my head against the wall for quite some time trying to figure this out and have been scouring the internet for information on it but have yet to find what I am looking for.
Thanks,
Ryan Lenkersdorfer
‘Lenker'
Hi,
Please read this:
http://eniackb.blogspot.com/2009/10/windows-2008-r2-problems-with-hp.html
Although is related with HP server, the same may happen in DELL servers.
I hope that the information above helps you. This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.
Worked like a charm for me.
