Quantcast
Channel: High Availability (Clustering) forum
Viewing all articles
Browse latest Browse all 6672

The Cluster node is not Reachable.

$
0
0

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/

Viewing all articles
Browse latest Browse all 6672

Trending Articles