Unable to add a second node in Cluster - Windows 2012

Question

_{Tuesday, March 19, 2013 5:16 PM}

Hi,

I have a lot of trouble, trying to create a cluster in a lab environment using Windows Server 2012. I can create the cluster only with one node. As soon as I try with 2 nodes, it failed due to timeout. When I try to add a second node to the created cluster same result. The network configuration is ok, no firewall, no antivirus.

I got the following error message (when adding second node). Also when creating the cluster with 2 nodes, event id 1572 (timeout)

Node: LAB-HYPV02.testlab.dom Started 15.03.2013 21:37:10 Completed 15.03.2013 21:43:28 Adding LAB-HYPV02.testlab.dom to the cluster. Validating cluster state on node LAB-HYPV02. Getting current node membership of cluster CLUSTER01. Adding node LAB-HYPV02 to Cluster configuration data. Validating installation of the Network FT Driver on node LAB-HYPV02. Validating installation of the Cluster Disk Driver on node LAB-HYPV02. Configuring Cluster Service on node LAB-HYPV02. Waiting for notification that Cluster service on node LAB-HYPV02.testlab.dom has started. Waiting for notification that node LAB-HYPV02 is a fully functional member of the cluster. Unable to successfully cleanup. The server 'LAB-HYPV02.testlab.dom' could not be added to the cluster. An error occurred while adding node 'LAB-HYPV02.testlab.dom' to cluster 'CLUSTER01'. This operation returned because the timeout period expired

I did check a lot a posts regarding this error but no success till now. Any idea ????

Thanks a lot

All replies (5)

_{Tuesday, March 19, 2013 5:24 PM ✅Answered | 1 vote}

Try pinging each cluster node from each side and review carefully the replies to ensure identical (aside from ip address) behaviour. Secondly perform an nslookup on each node (for both nodes).

Finally and most importantly, ensure that your network configuration *is* correct. I know you say it is, but I have seen these kind of issues displayed when:

network bindings are different across nodes
wrong ips/ subnets assigned to the wrong NICs
IPv6 and IPv4 configurations different across nodes
DNS misconfiguration for nodes
and various other network issues

..you can also try specifying the fully qualified node name when adding the second name.

Regards,
Mark Broadbent.

Contact me through (twitter|blog|SQLCloud)
Please click "Propose As Answer" if a post solves your problem
or "Vote As Helpful" if a post has been useful to you
Watch my sessions at the PASS Summit 2012 and SQLBits

_{Friday, June 7, 2013 10:26 PM ✅Answered}

Hi,

Finally I figure it out. It seems the iSCSI interface setup on a DC was registered into the DNS. Therefore my DNS was probably unable to resolve properly DNS request when forming the cluster. My cluster is now fully working as it should be.

_{Tuesday, March 19, 2013 6:07 PM}

Did you get any warning messages from the cluster validation wizard? Since you do not yet have a working cluster, make sure you run the validation wizard before creating a cluster. It saves a lot of time in trying to troubleshoot things because it makes dozens of checks against the environment and will report anything that is even slightly out of whack. Just because you get a warning does not mean that you can't build a cluster, but it will tell you exactly where to check for things.

.:|:.:|:. tim

_{Wednesday, May 1, 2013 7:27 PM}

Thanks for your help and sorry for the late answer.

I did check again every points you mentionned. I can ping both hosts, with or without FQDN, IP is also fine. No validation errors.....

Could it be related to Active Directory? I'm logged in with the Domain Admin account so I assume it's enough...

Any other idea, I'm losing my head!