<?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 Re: 4 node cluster in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/4-node-cluster/m-p/5415855#M658064</link>
    <description>&lt;P&gt;1. Why and how long are you taking down the 2 nodes for?&lt;/P&gt;&lt;P&gt;2.&amp;nbsp;Do you want the packages to remain up and running while the 2 nodes are down? If so, make sure package are enabled to run on the remaining nodes. (cmmodpkg -e)&lt;/P&gt;&lt;P&gt;3. Have you tested the package failover before, and do the other nodes have sufficient system capacity for the additional packages to run there? of course it also depends on when (busy time)&amp;nbsp;and how long they will remain up and running there.&lt;/P&gt;&lt;P&gt;4. The cluster will actually not "reform" because the other 2 nodes will remain up and running and still be part of the cluster. You will simply halt the 2 nodes you're taking down, and when you're done, you will bring them up and have them re-join the cluster.&lt;/P&gt;</description>
    <pubDate>Mon, 12 Dec 2011 23:19:33 GMT</pubDate>
    <dc:creator>Henry Fauni</dc:creator>
    <dc:date>2011-12-12T23:19:33Z</dc:date>
    <item>
      <title>4 node cluster</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/4-node-cluster/m-p/5415685#M658063</link>
      <description>&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have 4 node cluster . We are planning to bring down the 2 node.&amp;nbsp; As per my understanding the cluster will reform and it will run . Could you please let us know the ur thougts and which are the complication will occures .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!!!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Dec 2011 19:26:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/4-node-cluster/m-p/5415685#M658063</guid>
      <dc:creator>prashanth</dc:creator>
      <dc:date>2011-12-12T19:26:21Z</dc:date>
    </item>
    <item>
      <title>Re: 4 node cluster</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/4-node-cluster/m-p/5415855#M658064</link>
      <description>&lt;P&gt;1. Why and how long are you taking down the 2 nodes for?&lt;/P&gt;&lt;P&gt;2.&amp;nbsp;Do you want the packages to remain up and running while the 2 nodes are down? If so, make sure package are enabled to run on the remaining nodes. (cmmodpkg -e)&lt;/P&gt;&lt;P&gt;3. Have you tested the package failover before, and do the other nodes have sufficient system capacity for the additional packages to run there? of course it also depends on when (busy time)&amp;nbsp;and how long they will remain up and running there.&lt;/P&gt;&lt;P&gt;4. The cluster will actually not "reform" because the other 2 nodes will remain up and running and still be part of the cluster. You will simply halt the 2 nodes you're taking down, and when you're done, you will bring them up and have them re-join the cluster.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Dec 2011 23:19:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/4-node-cluster/m-p/5415855#M658064</guid>
      <dc:creator>Henry Fauni</dc:creator>
      <dc:date>2011-12-12T23:19:33Z</dc:date>
    </item>
    <item>
      <title>Re: 4 node cluster</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/4-node-cluster/m-p/5419433#M658065</link>
      <description>&lt;P&gt;Hi Henry,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are taking for memory upgrade.&lt;/P&gt;&lt;P&gt;1. Why and how long are you taking down the 2 nodes for?&lt;/P&gt;&lt;P&gt;Will take it out for 1 day.&lt;/P&gt;&lt;P&gt;2.&amp;nbsp;Do you want the packages to remain up and running while the 2 nodes are down? If so, make sure package are enabled to run on the remaining nodes. (cmmodpkg -e)&lt;/P&gt;&lt;P&gt;Yes that is there&lt;/P&gt;&lt;P&gt;4. The cluster will actually not "reform" because the other 2 nodes will remain up and running and still be part of the cluster. You will simply halt the 2 nodes you're taking down, and when you're done, you will bring them up and have them re-join the cluster.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I understood .we can halt two node during that time my cluster will run with two active node. After replacing the memory&amp;nbsp; we can join the cluster.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!!!!&lt;/P&gt;</description>
      <pubDate>Thu, 15 Dec 2011 17:37:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/4-node-cluster/m-p/5419433#M658065</guid>
      <dc:creator>prashanth</dc:creator>
      <dc:date>2011-12-15T17:37:25Z</dc:date>
    </item>
    <item>
      <title>Re: 4 node cluster</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/4-node-cluster/m-p/5428023#M658066</link>
      <description>&lt;P&gt;Yes,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;An automatic cluster startup occurs any time a node reboots and joins the cluster. This can follow the reboot of an individual node, or it may be when all nodes in a cluster have failed, as when there has been an extended power failure and all SPUs went down. Automatic cluster startup will take place if the flag AUTOSTART_CMCLD is set to 1 in /etc/rc.config.d/cmcluster. When any node reboots with this parameter set to 1, it will rejoin an existing cluster.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rgds...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 26 Dec 2011 07:03:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/4-node-cluster/m-p/5428023#M658066</guid>
      <dc:creator>P Arumugavel</dc:creator>
      <dc:date>2011-12-26T07:03:30Z</dc:date>
    </item>
  </channel>
</rss>

