<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic The cluster Node is not reachable in Operating System - Microsoft</title>
    <link>https://community.hpe.com/t5/operating-system-microsoft/the-cluster-node-is-not-reachable/m-p/5294581#M12476</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am building an two node cluster using the following:&lt;/P&gt;&lt;P&gt;1. Nodes Hardware HP BL620c,&lt;/P&gt;&lt;P&gt;2.&amp;nbsp;Cluster Disk:&amp;nbsp; EVA 4400, 5 Luns Presented&lt;/P&gt;&lt;P&gt;3.&amp;nbsp; OS:&amp;nbsp; Windows Server 2008 R2, SP1.&lt;/P&gt;&lt;P&gt;4.&amp;nbsp; One Public NIC and one Heartbeat NIC.&amp;nbsp; The rest of the NIC were disabled.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;Scenario Tested: Live Network&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;1.&amp;nbsp; From the Live Network, Cluster Validation (All Parameters) Tested successfully (all green).&lt;/P&gt;&lt;P&gt;2.&amp;nbsp; When forming the cluster (two nodes simultaneously), the error is: &lt;STRONG&gt;&lt;SPAN&gt;The operation is taking longer than expected. and it's failed.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;3.&amp;nbsp; Second attempt, Create the cluster using one node only.&amp;nbsp; (other node was shutdown).&amp;nbsp; One node cluster, successful including SAN Disk resource.&lt;/P&gt;&lt;P&gt;4.&amp;nbsp; Adding Second node:&amp;nbsp; the result is "&lt;STRONG&gt;&lt;SPAN&gt;The cluster Node is not reachable." after clicking&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;Second Scenario:&amp;nbsp; Isolate ClusterNodes and connect one of the Domain Controller Directly in an Isolated Network.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;1.&amp;nbsp; From HP6120 Virtual Connect (VC) of the blade, I configure the Switch with another VLAN&amp;nbsp;to connect the Phyical Domain Controller and the "uplink" of VC to an isolated switch.&amp;nbsp; Three are reachable to each other.&amp;nbsp; Also, DNS resolution working fine.&lt;/P&gt;&lt;P&gt;2.&amp;nbsp; I've performed above scenario in the isolated&amp;nbsp;and same result achieve.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Same Scenario experiencing in a cluster node for BL460C G7.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone have experiencing this?&lt;/P&gt;</description>
    <pubDate>Mon, 08 Aug 2011 19:27:13 GMT</pubDate>
    <dc:creator>Ruel Alojado</dc:creator>
    <dc:date>2011-08-08T19:27:13Z</dc:date>
    <item>
      <title>The cluster Node is not reachable</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/the-cluster-node-is-not-reachable/m-p/5294581#M12476</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am building an two node cluster using the following:&lt;/P&gt;&lt;P&gt;1. Nodes Hardware HP BL620c,&lt;/P&gt;&lt;P&gt;2.&amp;nbsp;Cluster Disk:&amp;nbsp; EVA 4400, 5 Luns Presented&lt;/P&gt;&lt;P&gt;3.&amp;nbsp; OS:&amp;nbsp; Windows Server 2008 R2, SP1.&lt;/P&gt;&lt;P&gt;4.&amp;nbsp; One Public NIC and one Heartbeat NIC.&amp;nbsp; The rest of the NIC were disabled.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;Scenario Tested: Live Network&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;1.&amp;nbsp; From the Live Network, Cluster Validation (All Parameters) Tested successfully (all green).&lt;/P&gt;&lt;P&gt;2.&amp;nbsp; When forming the cluster (two nodes simultaneously), the error is: &lt;STRONG&gt;&lt;SPAN&gt;The operation is taking longer than expected. and it's failed.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;3.&amp;nbsp; Second attempt, Create the cluster using one node only.&amp;nbsp; (other node was shutdown).&amp;nbsp; One node cluster, successful including SAN Disk resource.&lt;/P&gt;&lt;P&gt;4.&amp;nbsp; Adding Second node:&amp;nbsp; the result is "&lt;STRONG&gt;&lt;SPAN&gt;The cluster Node is not reachable." after clicking&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;Second Scenario:&amp;nbsp; Isolate ClusterNodes and connect one of the Domain Controller Directly in an Isolated Network.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;1.&amp;nbsp; From HP6120 Virtual Connect (VC) of the blade, I configure the Switch with another VLAN&amp;nbsp;to connect the Phyical Domain Controller and the "uplink" of VC to an isolated switch.&amp;nbsp; Three are reachable to each other.&amp;nbsp; Also, DNS resolution working fine.&lt;/P&gt;&lt;P&gt;2.&amp;nbsp; I've performed above scenario in the isolated&amp;nbsp;and same result achieve.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Same Scenario experiencing in a cluster node for BL460C G7.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone have experiencing this?&lt;/P&gt;</description>
      <pubDate>Mon, 08 Aug 2011 19:27:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/the-cluster-node-is-not-reachable/m-p/5294581#M12476</guid>
      <dc:creator>Ruel Alojado</dc:creator>
      <dc:date>2011-08-08T19:27:13Z</dc:date>
    </item>
    <item>
      <title>Re: The cluster Node is not reachable</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/the-cluster-node-is-not-reachable/m-p/5296393#M12477</link>
      <description>&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Aug 2011 11:59:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/the-cluster-node-is-not-reachable/m-p/5296393#M12477</guid>
      <dc:creator>Ruel Alojado</dc:creator>
      <dc:date>2011-08-10T11:59:01Z</dc:date>
    </item>
  </channel>
</rss>

