<?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 disk issues in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk-issues/m-p/2657939#M712274</link>
    <description>Hi Jithu,&lt;BR /&gt;&lt;BR /&gt;I think Melvyn has explained really well on the concepts. I think you might be confused because of the terms being used.&lt;BR /&gt;&lt;BR /&gt;Your post earlier reads :&lt;BR /&gt;1. according to the class notes/manual. &lt;BR /&gt;"without a cluster lock disk, the cluster would not be able to reform should one node fail, causing the entire cluster to go down"&lt;BR /&gt;&lt;BR /&gt;and this is perfectly correct. The difference in terms might be causing the confusion. Here above it says the cluster will not be able to *REFORM*, and what it means is that if there is no cluster lock disk, and one of the nodes goes down ( leaving only the other running, and hence 50% of the cluster ) then the remaining node will TOC as well when it fails to get the cluster lock disk.&lt;BR /&gt;&lt;BR /&gt;On the other hand, if you don't have a cluster lock disk - and you try to start a one node cluster, it will still *FORM* with or without the cluster lock disk.&lt;BR /&gt;&lt;BR /&gt;Hope this helps.</description>
    <pubDate>Fri, 08 Feb 2002 01:34:39 GMT</pubDate>
    <dc:creator>Kim Leong</dc:creator>
    <dc:date>2002-02-08T01:34:39Z</dc:date>
    <item>
      <title>cluster lock disk issues</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk-issues/m-p/2657932#M712267</link>
      <description>Hello folks,&lt;BR /&gt;&lt;BR /&gt;sorry if these have been answered before in this forum, I did some searching but couldn't really find the answers I was looking for.&lt;BR /&gt;&lt;BR /&gt;am new to the MC/SG and hence these questions, please bear with me. thanx&lt;BR /&gt;&lt;BR /&gt;1. it's a 2 node cluster, with one cluster lock vg/pv defined. active and passive node config.&lt;BR /&gt;&lt;BR /&gt;2. if the active node has been up and running(pkgs) and cluster lock pv failed due to&lt;BR /&gt;harware failure(disk/path failure), would the cluster halt or panic, or we just see error mesg's in the log saying that cluster lock disk failed(I saw errors to this tune in this forum)..so am assuming as long as that active node is not shut/halted, the cluster/pkgs will keep running on active node.? lock disk is only used during cluster formation?&lt;BR /&gt;&lt;BR /&gt;2. currently the single cluster lock pv is say /dev/dsk/c1t1d0 on both the active and passive nodes. &lt;BR /&gt;that is a cause of concern, as the access to that PV is via the same switch and FA(EMC). even though the PV has pvlink devices say for example c2t1d0 via a different switch(SAN) and FA(EMC) on both the nodes..so for best practice, in the cluster config file, for node1 use the lock disk to be /dev/dsk/c1t1d0 and for the node2 use /dev/dsk/c2t1d0. both point to the same physical lock disk via diff paths in the SAN.&lt;BR /&gt;&lt;BR /&gt;3. Can we change the cluster lock PV device file on the node2 to /dev/dsk/c2t1d0..am assuming this requires shutting the cluster and then changing the config file and pusing the new changes??&lt;BR /&gt;&lt;BR /&gt;please advise.&lt;BR /&gt;thanx in advance.&lt;BR /&gt;jithu&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 04 Feb 2002 03:18:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk-issues/m-p/2657932#M712267</guid>
      <dc:creator>jithu_1</dc:creator>
      <dc:date>2002-02-04T03:18:01Z</dc:date>
    </item>
    <item>
      <title>Re: cluster lock disk issues</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk-issues/m-p/2657933#M712268</link>
      <description>&lt;BR /&gt;If you have a cluster that is running, and the cluster lock disc fails, the cluster will continue to run, but will log Warning messages to syslog every 60 minutes (polling interval for cluster lock disc).&lt;BR /&gt;If, however, one node now dies/halts/fails, the surviving node HAS to be able to get the lock, and if this is not possible then theis node will TOC, as per design.&lt;BR /&gt;&lt;BR /&gt;If the cluster lock disc is unavailable at cluster formation time, the cluster will still form, but with the same issue.&lt;BR /&gt;&lt;BR /&gt;The ONLY time the cluster lock disc is NEEDED is to break an exact 50% quorum issue, i.e. EXACTLY 50% of the nodes die, leaving EXACTLY 50% surviving.&lt;BR /&gt;&lt;BR /&gt;If you do wish to make the change you have mentioned, ensure that the new hardware path/device you are configuring is the primary path and not the Alternate Link, as this will appear to work, but will in fact not work under a failure condition.&lt;BR /&gt;&lt;BR /&gt;HTH</description>
      <pubDate>Mon, 04 Feb 2002 08:18:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk-issues/m-p/2657933#M712268</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2002-02-04T08:18:29Z</dc:date>
    </item>
    <item>
      <title>Re: cluster lock disk issues</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk-issues/m-p/2657934#M712269</link>
      <description>have another follow-up question for this statement&lt;BR /&gt;&lt;BR /&gt;"If the cluster lock disc is unavailable at cluster formation time, the cluster will still form, but with the same issue."&lt;BR /&gt;&lt;BR /&gt;Does that mean, say if the cluster lock disk failed, the&lt;BR /&gt;node1 was shut/halted for&lt;BR /&gt;some reason, if I try bringing up node2(standby), it would still form cluster and bring up the packages etc even though the lock disk is un-available??&lt;BR /&gt;&lt;BR /&gt;TIA&lt;BR /&gt;jithu</description>
      <pubDate>Mon, 04 Feb 2002 16:10:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk-issues/m-p/2657934#M712269</guid>
      <dc:creator>jithu_1</dc:creator>
      <dc:date>2002-02-04T16:10:07Z</dc:date>
    </item>
    <item>
      <title>Re: cluster lock disk issues</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk-issues/m-p/2657935#M712270</link>
      <description>In a word, yes&lt;BR /&gt;</description>
      <pubDate>Mon, 04 Feb 2002 17:31:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk-issues/m-p/2657935#M712270</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2002-02-04T17:31:15Z</dc:date>
    </item>
    <item>
      <title>Re: cluster lock disk issues</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk-issues/m-p/2657936#M712271</link>
      <description>Hello Melvin,&lt;BR /&gt;&lt;BR /&gt;now am more confused:-)&lt;BR /&gt;&lt;BR /&gt;1. according to the class notes/manual.&lt;BR /&gt;"without a cluster lock disk, the cluster would not be able to reform should one node fail, causing the entire cluster to go down"&lt;BR /&gt;&lt;BR /&gt;in my case, the lock disk&lt;BR /&gt;was un-available, active node1&lt;BR /&gt;was shut/halted. tried to bring up the node2, it couldn't form the cluster and ceased cluster activities.&lt;BR /&gt;&lt;BR /&gt;doesn't that mean, node2 needs&lt;BR /&gt;access to lock disk to bring up the packages etc..&lt;BR /&gt;&lt;BR /&gt;TIA&lt;BR /&gt;jithu&lt;BR /&gt;</description>
      <pubDate>Mon, 04 Feb 2002 19:08:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk-issues/m-p/2657936#M712271</guid>
      <dc:creator>jithu_1</dc:creator>
      <dc:date>2002-02-04T19:08:47Z</dc:date>
    </item>
    <item>
      <title>Re: cluster lock disk issues</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk-issues/m-p/2657937#M712272</link>
      <description>It is required that you have a cluster lock disk for a two node cluster.  This must be one of your shared drives accessible by both nodes.  If this isn't possible, then cluster formation isn't possible.   I would save your old cluster.ascii file by copying it to another file or cmgetconf command, and then do another cmquerycl to see what it gives you as to output.&lt;BR /&gt;&lt;BR /&gt;Hope this helps&lt;BR /&gt;&lt;BR /&gt;Chris</description>
      <pubDate>Mon, 04 Feb 2002 19:14:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk-issues/m-p/2657937#M712272</guid>
      <dc:creator>Christopher McCray_1</dc:creator>
      <dc:date>2002-02-04T19:14:25Z</dc:date>
    </item>
    <item>
      <title>Re: cluster lock disk issues</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk-issues/m-p/2657938#M712273</link>
      <description>If the cluster has been configured and the binary generated, then if the cluster lock disc ismissing at initial cluster formation, then the cluster will form.&lt;BR /&gt;The case you mention is where the cluster was already runing, but when a node went down, then the other node needed to get the cluster lock disc, and failed, resulting in the remaining node going down.&lt;BR /&gt;&lt;BR /&gt;Again I refer you to the fact that to create a new cluster, you must configure a cluster lock disc which must be available at the time of doing cmapplyconf. Once this is done, the cluster lock disc is ONLY used for decision making in the event of a tie, i.e. EXACTLY 50% of a cluster quorum remains.&lt;BR /&gt;Hence, if the cluster goes to start and the cluster lock disc is unavailable, the cluster will still form, itis only upon a failure that the cluster lock disc is actually needed.&lt;BR /&gt;</description>
      <pubDate>Mon, 04 Feb 2002 19:42:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk-issues/m-p/2657938#M712273</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2002-02-04T19:42:37Z</dc:date>
    </item>
    <item>
      <title>Re: cluster lock disk issues</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk-issues/m-p/2657939#M712274</link>
      <description>Hi Jithu,&lt;BR /&gt;&lt;BR /&gt;I think Melvyn has explained really well on the concepts. I think you might be confused because of the terms being used.&lt;BR /&gt;&lt;BR /&gt;Your post earlier reads :&lt;BR /&gt;1. according to the class notes/manual. &lt;BR /&gt;"without a cluster lock disk, the cluster would not be able to reform should one node fail, causing the entire cluster to go down"&lt;BR /&gt;&lt;BR /&gt;and this is perfectly correct. The difference in terms might be causing the confusion. Here above it says the cluster will not be able to *REFORM*, and what it means is that if there is no cluster lock disk, and one of the nodes goes down ( leaving only the other running, and hence 50% of the cluster ) then the remaining node will TOC as well when it fails to get the cluster lock disk.&lt;BR /&gt;&lt;BR /&gt;On the other hand, if you don't have a cluster lock disk - and you try to start a one node cluster, it will still *FORM* with or without the cluster lock disk.&lt;BR /&gt;&lt;BR /&gt;Hope this helps.</description>
      <pubDate>Fri, 08 Feb 2002 01:34:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk-issues/m-p/2657939#M712274</guid>
      <dc:creator>Kim Leong</dc:creator>
      <dc:date>2002-02-08T01:34:39Z</dc:date>
    </item>
  </channel>
</rss>

