<?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/2533786#M717142</link>
    <description>1) Why do I HAVE to use dual cluster lock? &lt;BR /&gt;To try to avoid the "Split Brain Syndrome" &lt;BR /&gt;&lt;BR /&gt;=&amp;gt; I understand that dual CL conf increases the possibility of having the Syndrome. Could you explain to me this situation? I visited yesterday both links you sent, but I still have doubts.&lt;BR /&gt;&lt;BR /&gt;2) How to configure it: &lt;BR /&gt;a) On both node the same parameters for FIRST_CLUSTER_LOCK_PV=disk1 and SECOND_CLUSTER_LOCK_PV=disk2 ?? &lt;BR /&gt;&lt;BR /&gt;b) On each node different value for FIRST_CLUSTER_LOCK_PV=diskn ?? &lt;BR /&gt;The CL PVs will possibly be the same on the nodes, but not necessarily. The important thing is they are on vg's seen by ALL nodes in the cluster. &lt;BR /&gt;&lt;BR /&gt;=&amp;gt; Which configuration do you suggest? I think the "a" item reduces the possibility of having the Syndrome...&lt;BR /&gt;&lt;BR /&gt;3) May I use any VG for CL, regardless which is its primary node? Getting the lock disk doesn?t mean mounting the vglock, correct ? &lt;BR /&gt;Correct. &lt;BR /&gt;&lt;BR /&gt;=&amp;gt; Does it make sense having a mirror copy of the VGlock? I don?t think so ...&lt;BR /&gt;&lt;BR /&gt;To avoid using cluster lock discs, you may prefer to use an Arbitration node. &lt;BR /&gt;&lt;BR /&gt;=&amp;gt; I have to study this possibility. Thanks.</description>
    <pubDate>Tue, 29 May 2001 12:36:10 GMT</pubDate>
    <dc:creator>Leila Maria Rebel</dc:creator>
    <dc:date>2001-05-29T12:36:10Z</dc:date>
    <item>
      <title>Cluster Lock</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/2533784#M717140</link>
      <description>Hi!&lt;BR /&gt;I?ve a two-node local cluster, and I?m migrating to a Campus Cluster. My questions are:&lt;BR /&gt;&lt;BR /&gt;1) Why do I HAVE to use dual cluster lock?&lt;BR /&gt;&lt;BR /&gt;2) How to configure it:&lt;BR /&gt;   a) On both node the same parameters for FIRST_CLUSTER_LOCK_PV=disk1 and SECOND_CLUSTER_LOCK_PV=disk2  ??&lt;BR /&gt;&lt;BR /&gt;   b) On each node different value for FIRST_CLUSTER_LOCK_PV=diskn   ??&lt;BR /&gt;&lt;BR /&gt;3) May I use any VG for CL, regardless which is its primary node? Getting the lock disk doesn?t mean mounting the vglock, correct ?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Leila</description>
      <pubDate>Tue, 29 May 2001 11:59:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/2533784#M717140</guid>
      <dc:creator>Leila Maria Rebel</dc:creator>
      <dc:date>2001-05-29T11:59:41Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Lock</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/2533785#M717141</link>
      <description>1) Why do I HAVE to use dual cluster lock? &lt;BR /&gt;To try to avoid the "Split Brain Syndrome"&lt;BR /&gt;&lt;BR /&gt;2) How to configure it: &lt;BR /&gt;a) On both node the same parameters for FIRST_CLUSTER_LOCK_PV=disk1 and SECOND_CLUSTER_LOCK_PV=disk2 ?? &lt;BR /&gt;&lt;BR /&gt;b) On each node different value for FIRST_CLUSTER_LOCK_PV=diskn ?? &lt;BR /&gt;The CL PVs will possibly be the same on the nodes, but not necessarily. The important thing is they are on vg's seen by ALL nodes in the cluster.&lt;BR /&gt;&lt;BR /&gt;3) May I use any VG for CL, regardless which is its primary node? Getting the lock disk doesn?t mean mounting the vglock, correct ? &lt;BR /&gt;Correct.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;To avoid using cluster lock discs, you may prefer to use an Arbitration node.&lt;BR /&gt;&lt;BR /&gt;I suggest you take a look at:&lt;BR /&gt;&lt;A href="http://docs.hp.com/hpux/onlinedocs/ha/hpworl98.pdf" target="_blank"&gt;http://docs.hp.com/hpux/onlinedocs/ha/hpworl98.pdf&lt;/A&gt;&lt;BR /&gt;and also:&lt;BR /&gt;&lt;A href="http://docs.hp.com/hpux/onlinedocs/B3936-90045/B3936-90045.html" target="_blank"&gt;http://docs.hp.com/hpux/onlinedocs/B3936-90045/B3936-90045.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 29 May 2001 12:19:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/2533785#M717141</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2001-05-29T12:19:19Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Lock</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/2533786#M717142</link>
      <description>1) Why do I HAVE to use dual cluster lock? &lt;BR /&gt;To try to avoid the "Split Brain Syndrome" &lt;BR /&gt;&lt;BR /&gt;=&amp;gt; I understand that dual CL conf increases the possibility of having the Syndrome. Could you explain to me this situation? I visited yesterday both links you sent, but I still have doubts.&lt;BR /&gt;&lt;BR /&gt;2) How to configure it: &lt;BR /&gt;a) On both node the same parameters for FIRST_CLUSTER_LOCK_PV=disk1 and SECOND_CLUSTER_LOCK_PV=disk2 ?? &lt;BR /&gt;&lt;BR /&gt;b) On each node different value for FIRST_CLUSTER_LOCK_PV=diskn ?? &lt;BR /&gt;The CL PVs will possibly be the same on the nodes, but not necessarily. The important thing is they are on vg's seen by ALL nodes in the cluster. &lt;BR /&gt;&lt;BR /&gt;=&amp;gt; Which configuration do you suggest? I think the "a" item reduces the possibility of having the Syndrome...&lt;BR /&gt;&lt;BR /&gt;3) May I use any VG for CL, regardless which is its primary node? Getting the lock disk doesn?t mean mounting the vglock, correct ? &lt;BR /&gt;Correct. &lt;BR /&gt;&lt;BR /&gt;=&amp;gt; Does it make sense having a mirror copy of the VGlock? I don?t think so ...&lt;BR /&gt;&lt;BR /&gt;To avoid using cluster lock discs, you may prefer to use an Arbitration node. &lt;BR /&gt;&lt;BR /&gt;=&amp;gt; I have to study this possibility. Thanks.</description>
      <pubDate>Tue, 29 May 2001 12:36:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/2533786#M717142</guid>
      <dc:creator>Leila Maria Rebel</dc:creator>
      <dc:date>2001-05-29T12:36:10Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Lock</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/2533787#M717143</link>
      <description>aha, got my fingers twisted there.&lt;BR /&gt;Sorry, the dual cluster lock is needed in case one entire side of the campus cluster, namely a data centre, goes down. The other site must be able to get a cluster lock disc. This INCREASES the chance of Split Brain Syndrome ( imust have had "Brain Asleep " earlier :-}&lt;BR /&gt;&lt;BR /&gt;The physical disc device naming will differ or be the same DEPENDANT upon how you have.&lt;BR /&gt;configured your hardware. If you create the shared vg's, cmquerycl will attempt to check for a shared vg and list the PV's in the ascii file.&lt;BR /&gt;As for mirroring the CL info, this is not and cannot be done. The CL info gets written into an area that is Never mirrored, even thoough all Lvol's in the VG may be mirrored.&lt;BR /&gt;&lt;BR /&gt;This is usually explained quite well in the ServiceGuard class.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;</description>
      <pubDate>Tue, 29 May 2001 13:15:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/2533787#M717143</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2001-05-29T13:15:08Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Lock</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/2533788#M717144</link>
      <description>Ok, it seems perfect to me. Thanks a lot!&lt;BR /&gt;&lt;BR /&gt;Leila&lt;BR /&gt;</description>
      <pubDate>Tue, 29 May 2001 14:11:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock/m-p/2533788#M717144</guid>
      <dc:creator>Leila Maria Rebel</dc:creator>
      <dc:date>2001-05-29T14:11:22Z</dc:date>
    </item>
  </channel>
</rss>

