The Cluster node is not Reachable.

Question

_{Monday, August 8, 2011 6:58 PM}

Hi,

I am building an two node cluster using the following:

1. Nodes Hardware HP BL620c,

2. Cluster Disk:  EVA 4400, 5 Luns Presented

3.  OS:  Windows Server 2008 R2, SP1.

4.  One Public NIC and one Heartbeat NIC.  The rest of the NIC were disabled.

Scenario Tested: Live Network

1.  From the Live Network, Cluster Validation Tested successfully (all green).

2.  When forming the cluster (two nodes simultaneously), the error is: The operation is taking longer than expected. and it's failed.

3.  Second attempt, Create the cluster using one node only.  (other node was shutdown).  One node cluster, successful including SAN Disk resource.

4.  Adding Second node:  the result is "The cluster Node is not reachable."

Second Scenario:  Isolate ClusterNodes and connect one of the Domain Controller Directly in an Isolated Network.

1.  From HP6120 Virtual Connect (VC) of the blade, I configure the Switch with another VLAN to connect the Phyical Domain Controller and the "uplink" of VC to an isolated switch.  Three are reachable to each other.  Also, DNS resolution working fine.

2.  I've performed above scenario in the isolated and same result achieve.

Note: I check the work around from the forum and didn't work for me.  Also, In our Development environment, I am running a DL580, 64GB, 1TB,  two two-node clusters of Windows Server 2008 R2/SQL Server 2008 R2 with Starwind ISCSI as a shared storage. Both are running fine in our ESX Server.

We are trying to Get HP Involved recheck Blade Configuration specially from the Virtual Connect side.

Appreciate those suggestion that can help me. I've been struggling for three days to make it work.

http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2highavailability/thread/dd1c0345-9710-43eb-ba30-20e763e1c92a/

All replies (5)

_{Wednesday, August 10, 2011 11:54 AM ✅Answered | 1 vote}

Believe it or not the problem is:  the cluster node name have the same username in AD.

It never come to my mind about checking the existence of both computername and username but after renaming the NODE Cluster, the cluster was successfully created.

_{Tuesday, August 9, 2011 3:58 PM}

Check your Windows Firewall settings.  Make sure the Domain firewall is OFF.

Geoff N. Hiten Principal Consultant Microsoft SQL Server MVP

_{Tuesday, August 9, 2011 8:00 PM}

Hi Ruel,

in addition to Geoff his right "pointer" I would like to add here .... ;-)

The windows firewall exceptions are normally automatically added during failover cluster setup. for testing purposes you can disable the FW temporary to verify the root cause but finally I would not "recommended" it for production or permanent scenarios. more detailed informations around required network communication in failover cluster environments can be found in following references:

Cluster Service

<script type="text/javascript">// <![CDATA[ loadTOCNode(3, 'summary'); ]]></script> The Cluster service controls server cluster operations and manages the cluster database. A cluster is a collection of independent computers that act as a single computer. Managers, programmers, and users see the cluster as a single system. The software distributes data among the nodes of the cluster. If a node fails, other nodes provide the services and data that was formerly provided by the missing node. When a node is added or repaired, the cluster software migrates some data to that node.

System service name: ClusSvc

¹ For more information about how to customize this port, see the "Remote Procedure Calls and DCOM" section in the "References" section.
² This is the range in Windows Server 2008 and in Windows Vista

=> http://support.microsoft.com/?kbid=832017

PS: Do you have any further security software installed (a.e. Symantec)?

Hope that helps.

Regards

Ramazan

Ramazan Can [MVP Cluster] http://ramazancan.wordpress.com/ ##This posting is provided "AS IS" with no warranties, and confers no rights##

_{Tuesday, August 9, 2011 8:20 PM}

Thanks for the reply.

@SQLCraftsman, I will double check that as validation results Pass on this part.  I've set the firewall to allow all traffic for the Domain Part.

@Ramazan, in order to isolate the firewall issue, I've made it all allow for Domain.  I've isolated also the Network Connectivity stated in second scenario.  For the Symantec End Point security, i've disabled it temporarily as i have seen this issue in some of the forums. 

Tomorrow, I will try different scenario and let you know.

_{Monday, January 21, 2013 4:16 PM}

Thank You RuelAlojado

very nice worked for me.