<?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: cluster lock in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/2920668#M709663</link>
    <description>So what you are saying is htat when you start only ONE of hte two nodes, i.e. hte ohter node is down/unavailable, then hte cluster does not start automatically??&lt;BR /&gt;If so, hten YES this is the default and expected behaviour.&lt;BR /&gt;ALL (100%) of the cluster nodes need to be available and attempting to join the cluster within the AUTO_START_TIMEOUT time, default of 10 minutes.&lt;BR /&gt;</description>
    <pubDate>Thu, 06 Mar 2003 11:07:06 GMT</pubDate>
    <dc:creator>melvyn burnard</dc:creator>
    <dc:date>2003-03-06T11:07:06Z</dc:date>
    <item>
      <title>cluster lock</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/2920665#M709660</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;I have one doubts.&lt;BR /&gt;I have two nodes in cluster, the cluster-lock is ok. But, when I power off the two Machines and I power on only one of them, this one don't run cluster service, is necessary force it. Is this the normaly operation? &lt;BR /&gt;&lt;BR /&gt;Tnks in advance.</description>
      <pubDate>Thu, 06 Mar 2003 09:56:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/2920665#M709660</guid>
      <dc:creator>Jose Juan</dc:creator>
      <dc:date>2003-03-06T09:56:45Z</dc:date>
    </item>
    <item>
      <title>Re: cluster lock</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/2920666#M709661</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Check /etc/rc.config.d/cmcluster for the following &lt;BR /&gt;&lt;BR /&gt;AUTOSTART_CMCLD=1&lt;BR /&gt;&lt;BR /&gt;With autostart set to 1 the node will attempt to join/form it's cluster.  However you do need 100% node attendance to form the cluster in the first place.&lt;BR /&gt;&lt;BR /&gt;Regard,&lt;BR /&gt;&lt;BR /&gt;Hilary&lt;BR /&gt;</description>
      <pubDate>Thu, 06 Mar 2003 10:53:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/2920666#M709661</guid>
      <dc:creator>BFA6</dc:creator>
      <dc:date>2003-03-06T10:53:08Z</dc:date>
    </item>
    <item>
      <title>Re: cluster lock</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/2920667#M709662</link>
      <description>hi,&lt;BR /&gt;check your /etc/rc.config.d/cmcluster file. &lt;BR /&gt;&lt;BR /&gt;if you want the cluster to start automatically. set the AUTOSTART_CMCLD to 1 in that file. &lt;BR /&gt;-balaji</description>
      <pubDate>Thu, 06 Mar 2003 11:02:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/2920667#M709662</guid>
      <dc:creator>Balaji N</dc:creator>
      <dc:date>2003-03-06T11:02:04Z</dc:date>
    </item>
    <item>
      <title>Re: cluster lock</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/2920668#M709663</link>
      <description>So what you are saying is htat when you start only ONE of hte two nodes, i.e. hte ohter node is down/unavailable, then hte cluster does not start automatically??&lt;BR /&gt;If so, hten YES this is the default and expected behaviour.&lt;BR /&gt;ALL (100%) of the cluster nodes need to be available and attempting to join the cluster within the AUTO_START_TIMEOUT time, default of 10 minutes.&lt;BR /&gt;</description>
      <pubDate>Thu, 06 Mar 2003 11:07:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/2920668#M709663</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2003-03-06T11:07:06Z</dc:date>
    </item>
  </channel>
</rss>

