<?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: MCSG Issue in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/mcsg-issue/m-p/3660009#M241920</link>
    <description>Ops - ignore my previous post - a 2 node cluster will reform - from Managing Serviceguard:&lt;BR /&gt;&lt;BR /&gt;"Although a cluster quorum of more than 50% is generally required, exactly 50% of the previously running nodes may re-form as a new cluster provided that the other 50% of the previously running nodes do not also re-form. This is guaranteed by the use of a tie-breaker to choose between the two equal-sized node groups, allowing one group to form the cluster and forcing the other group to shut down. This tie-breaker is known as a cluster lock. The cluster lock is implemented either by means of a lock disk or a quorum server. &lt;BR /&gt;&lt;BR /&gt;The cluster lock is used as a tie-breaker only for situations in which a running cluster fails and, as Serviceguard attempts to form a new cluster, the cluster is split into two sub-clusters of equal size. Each sub-cluster will attempt to acquire the cluster lock. The sub-cluster which gets the cluster lock will form the new cluster, preventing the possibility of two sub-clusters running at the same time. If the two sub-clusters are of unequal size, the sub-cluster with greater than 50% of the nodes will form the new cluster, and the cluster lock is not used.&lt;BR /&gt;&lt;BR /&gt;If you have a two-node cluster, you are required to configure a cluster lock. If communications are lost between these two nodes, the node that obtains the cluster lock will take over the cluster and the other node will halt or perform a TOC. Without a cluster lock, a failure of either node in the cluster will cause the other node, and therefore the cluster, to halt. Note also that if the cluster lock fails during an attempt to acquire it, the cluster will halt. "&lt;BR /&gt;&lt;BR /&gt;Basically - as long as there are 50% of the nodes up - it will reform.&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff&lt;BR /&gt;</description>
    <pubDate>Fri, 28 Oct 2005 08:14:14 GMT</pubDate>
    <dc:creator>Geoff Wild</dc:creator>
    <dc:date>2005-10-28T08:14:14Z</dc:date>
    <item>
      <title>MCSG Issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mcsg-issue/m-p/3660005#M241916</link>
      <description>Hi folks,&lt;BR /&gt; Can any body tell whether Cluster will form properly when i am running cmruncl and cluster lock disk was not visible for both nodes. &lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;Ramkumar.G</description>
      <pubDate>Fri, 28 Oct 2005 08:01:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mcsg-issue/m-p/3660005#M241916</guid>
      <dc:creator>ramkumar</dc:creator>
      <dc:date>2005-10-28T08:01:56Z</dc:date>
    </item>
    <item>
      <title>Re: MCSG Issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mcsg-issue/m-p/3660006#M241917</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I don't think this will work.&lt;BR /&gt;You will receive several errors in the syslog.log file</description>
      <pubDate>Fri, 28 Oct 2005 08:03:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mcsg-issue/m-p/3660006#M241917</guid>
      <dc:creator>Luk Vandenbussche</dc:creator>
      <dc:date>2005-10-28T08:03:35Z</dc:date>
    </item>
    <item>
      <title>Re: MCSG Issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mcsg-issue/m-p/3660007#M241918</link>
      <description>The cluster will form, but if the cl;uster lock disc is missing, then you will see errors logged in the syslog.log every hour (polling interval to check the disc), and if oner node were to crash, the other would TOC.</description>
      <pubDate>Fri, 28 Oct 2005 08:05:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mcsg-issue/m-p/3660007#M241918</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2005-10-28T08:05:29Z</dc:date>
    </item>
    <item>
      <title>Re: MCSG Issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mcsg-issue/m-p/3660008#M241919</link>
      <description>No - only time cluster will function without a lock disk (or quorum server) is when it is already running.  Reformations will not work - cluster startup will fail.&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff</description>
      <pubDate>Fri, 28 Oct 2005 08:06:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mcsg-issue/m-p/3660008#M241919</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2005-10-28T08:06:30Z</dc:date>
    </item>
    <item>
      <title>Re: MCSG Issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mcsg-issue/m-p/3660009#M241920</link>
      <description>Ops - ignore my previous post - a 2 node cluster will reform - from Managing Serviceguard:&lt;BR /&gt;&lt;BR /&gt;"Although a cluster quorum of more than 50% is generally required, exactly 50% of the previously running nodes may re-form as a new cluster provided that the other 50% of the previously running nodes do not also re-form. This is guaranteed by the use of a tie-breaker to choose between the two equal-sized node groups, allowing one group to form the cluster and forcing the other group to shut down. This tie-breaker is known as a cluster lock. The cluster lock is implemented either by means of a lock disk or a quorum server. &lt;BR /&gt;&lt;BR /&gt;The cluster lock is used as a tie-breaker only for situations in which a running cluster fails and, as Serviceguard attempts to form a new cluster, the cluster is split into two sub-clusters of equal size. Each sub-cluster will attempt to acquire the cluster lock. The sub-cluster which gets the cluster lock will form the new cluster, preventing the possibility of two sub-clusters running at the same time. If the two sub-clusters are of unequal size, the sub-cluster with greater than 50% of the nodes will form the new cluster, and the cluster lock is not used.&lt;BR /&gt;&lt;BR /&gt;If you have a two-node cluster, you are required to configure a cluster lock. If communications are lost between these two nodes, the node that obtains the cluster lock will take over the cluster and the other node will halt or perform a TOC. Without a cluster lock, a failure of either node in the cluster will cause the other node, and therefore the cluster, to halt. Note also that if the cluster lock fails during an attempt to acquire it, the cluster will halt. "&lt;BR /&gt;&lt;BR /&gt;Basically - as long as there are 50% of the nodes up - it will reform.&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff&lt;BR /&gt;</description>
      <pubDate>Fri, 28 Oct 2005 08:14:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mcsg-issue/m-p/3660009#M241920</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2005-10-28T08:14:14Z</dc:date>
    </item>
    <item>
      <title>Re: MCSG Issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mcsg-issue/m-p/3660010#M241921</link>
      <description>Hey Ram,&lt;BR /&gt;&lt;BR /&gt;  cmruncl should work,provided both the nodes are up. cmcld periodically checks to make sure cluster lock is accessible. If not, error messages will be logged in syslog.log.&lt;BR /&gt;&lt;BR /&gt;   If you want to form a cluster only with specific node(s), then -n option can be used with cmruncl.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Sundar.</description>
      <pubDate>Fri, 28 Oct 2005 10:27:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mcsg-issue/m-p/3660010#M241921</guid>
      <dc:creator>Sundar_7</dc:creator>
      <dc:date>2005-10-28T10:27:02Z</dc:date>
    </item>
    <item>
      <title>Re: MCSG Issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mcsg-issue/m-p/3660011#M241922</link>
      <description>Ram,&lt;BR /&gt;&lt;BR /&gt;As long as there is a heartbeat between the 2 nodes, you should be able to bring up your cluster.  Be advised though, if you reboot one of your nodes without doing a cmhaltnode 1st, there is a good chance that you will cause the other node to TOC.  This happened in our workplace (until we got the lock disk issue resolved).&lt;BR /&gt;&lt;BR /&gt;Andy</description>
      <pubDate>Fri, 28 Oct 2005 11:32:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mcsg-issue/m-p/3660011#M241922</guid>
      <dc:creator>Sheriff Andy</dc:creator>
      <dc:date>2005-10-28T11:32:55Z</dc:date>
    </item>
    <item>
      <title>Re: MCSG Issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mcsg-issue/m-p/3660012#M241923</link>
      <description>Hi Ramkumar,&lt;BR /&gt;&lt;BR /&gt;This is exactly called as split brain scenario. If the cluster lock disk is not available then both the node will form a cluster and also if you are trying to run same package from both the node, the risk of data corruption is there.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 28 Oct 2005 15:08:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mcsg-issue/m-p/3660012#M241923</guid>
      <dc:creator>Bharat Katkar</dc:creator>
      <dc:date>2005-10-28T15:08:55Z</dc:date>
    </item>
  </channel>
</rss>

