<?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: What is the best practice for cluster lock disk? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981297#M698359</link>
    <description>I suspect that best practice is not to use them but instead use a Quorum Server. A little PC running Linux makes a dandy qs.</description>
    <pubDate>Mon, 29 May 2006 23:14:41 GMT</pubDate>
    <dc:creator>A. Clay Stephenson</dc:creator>
    <dc:date>2006-05-29T23:14:41Z</dc:date>
    <item>
      <title>What is the best practice for cluster lock disk?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981291#M698353</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Can cluster lock disk be part of any activated VG? can be part of cluster package VG? or should it be seperate shared disk?&lt;BR /&gt;&lt;BR /&gt;what is the best practice to create cluster lock VG and cluster lock disks?&lt;BR /&gt;like should require seperate VG?.. &lt;BR /&gt;&lt;BR /&gt;Many thanks in advance..</description>
      <pubDate>Mon, 29 May 2006 01:51:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981291#M698353</guid>
      <dc:creator>Ganesan R</dc:creator>
      <dc:date>2006-05-29T01:51:13Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best practice for cluster lock disk?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981292#M698354</link>
      <description>Use a disk which is part of VG in the cluster.&lt;BR /&gt;&lt;BR /&gt;Specify a SECOND_CLUSTER_LOCK disk to obtain a higher availability</description>
      <pubDate>Mon, 29 May 2006 02:05:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981292#M698354</guid>
      <dc:creator>Luk Vandenbussche</dc:creator>
      <dc:date>2006-05-29T02:05:06Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best practice for cluster lock disk?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981293#M698355</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;A lock disk may be used for clusters up to and including four nodes in size. The cluster lock disk is a special area on an LVM disk located in a volume group that is shareable by all nodes in the cluster. When a node obtains the cluster lock, this area is marked so that other nodes will recognize the lock as "taken." &lt;BR /&gt;&lt;BR /&gt;The lock disk is not dedicated for use as the cluster lock; the disk can be employed as part of a normal volume group with user data on it. &lt;BR /&gt;&lt;BR /&gt;Please refer the section in the manual Managing SG pointed by the following url for more info on cluster lock disk.&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/B3936-90079/ch03s02.html#d0e2149" target="_blank"&gt;http://docs.hp.com/en/B3936-90079/ch03s02.html#d0e2149&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Ninad</description>
      <pubDate>Mon, 29 May 2006 05:24:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981293#M698355</guid>
      <dc:creator>Ninad_1</dc:creator>
      <dc:date>2006-05-29T05:24:15Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best practice for cluster lock disk?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981294#M698356</link>
      <description>The cluster lock can be part of any shared disk.&lt;BR /&gt;&lt;BR /&gt;It can be part of a shared vg.&lt;BR /&gt;&lt;BR /&gt;You don't need a separate vg for cluster lock.&lt;BR /&gt;&lt;BR /&gt;See the docs on &lt;A href="http://docs.hp.com/en/ha.html" target="_blank"&gt;http://docs.hp.com/en/ha.html&lt;/A&gt; for more info...&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff</description>
      <pubDate>Mon, 29 May 2006 10:20:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981294#M698356</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2006-05-29T10:20:40Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best practice for cluster lock disk?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981295#M698357</link>
      <description>Cluster Lock Disk: This is a shared disk that both nodes can see and that is controlled by LVM. &lt;BR /&gt;In a cluster of more than four nodes, a cluster lock disk is not supported or allowed. A quorum server is. &lt;BR /&gt;&lt;BR /&gt;Quorum Server: This is a separate node, not part of the cluster but contactable over a network interface (preferably on the same subnet to avoid delays over routers, and so on). This machine could be something as simple as a workstation running HP-UX 11.0 or 11i (either PA-RISC or IPF), or it could even be a machine running Linux. The Quorum Server listens to connection requests from the Serviceguard nodes on port #1238. The server maintains a special area in memory for each cluster, and when a node obtains the cluster lock, this area is marked so that other nodes will recognize the lock as "taken." It may provide quorum services for more than one cluster. &lt;BR /&gt;&lt;BR /&gt;-Amit&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 29 May 2006 23:04:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981295#M698357</guid>
      <dc:creator>Chauhan Amit</dc:creator>
      <dc:date>2006-05-29T23:04:50Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best practice for cluster lock disk?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981296#M698358</link>
      <description>Another important point is :&lt;BR /&gt;&lt;BR /&gt;ServiceGuard does not provide a way to specify alternate links to a cluster lock disk. &lt;BR /&gt;&lt;BR /&gt;When you use a virtual disk (VDisk) as your lock disk in an HP 9000 clustering environment, the HP-UX node cannot access the lock disk when both of the following situations apply:&lt;BR /&gt;The path that is defined for the FIRST_CLUSTER_LOCK_PV variable is unavailable. &lt;BR /&gt;A 50-50 split in the quorum occurs. &lt;BR /&gt;To resolve this issue and to maintain redundancy, specify a different path to the lock disk for each HP-UX node in your cluster using the FIRST_CLUSTER_LOCK_PV variable in the cluster configuration ASCII file. For example, if you are configuring a two-node HP-UX cluster, set the path of FIRST_CLUSTER_LOCK_PV on HP-UX server A to the first SAN Volume Controller node (through one fibre-channel switch) and set the FIRST_CLUSTER_LOCK_PV for HP server B to the second node (through another fibre-channel switch).&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;-Amit&lt;BR /&gt;</description>
      <pubDate>Mon, 29 May 2006 23:06:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981296#M698358</guid>
      <dc:creator>Chauhan Amit</dc:creator>
      <dc:date>2006-05-29T23:06:23Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best practice for cluster lock disk?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981297#M698359</link>
      <description>I suspect that best practice is not to use them but instead use a Quorum Server. A little PC running Linux makes a dandy qs.</description>
      <pubDate>Mon, 29 May 2006 23:14:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981297#M698359</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-05-29T23:14:41Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best practice for cluster lock disk?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981298#M698360</link>
      <description>&lt;BR /&gt;Thanks for your replies..&lt;BR /&gt;&lt;BR /&gt;can i use a disk from cluster VG(using for cluster package) for cluster lock? or should it be in non-cluster VG?&lt;BR /&gt;&lt;BR /&gt;Many thanks in advance</description>
      <pubDate>Mon, 29 May 2006 23:20:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981298#M698360</guid>
      <dc:creator>Ganesan R</dc:creator>
      <dc:date>2006-05-29T23:20:18Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best practice for cluster lock disk?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981299#M698361</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;can i use a disk from cluster VG(using for cluster package) for cluster lock? or should it be in non-cluster VG?&lt;BR /&gt;&lt;BR /&gt;Disk has to be from Cluster VG for cluster lock , so that it is visible from both the nodes.&lt;BR /&gt;&lt;BR /&gt;-Amit</description>
      <pubDate>Mon, 29 May 2006 23:28:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981299#M698361</guid>
      <dc:creator>Chauhan Amit</dc:creator>
      <dc:date>2006-05-29T23:28:23Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best practice for cluster lock disk?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981300#M698362</link>
      <description>Another important point regarding power circuit:&lt;BR /&gt;&lt;BR /&gt;It is recommended that you use a single lock disk. A single lock disk should be configured on a power circuit separate from that of any node in the cluster. For example, it is highly recommended to use three power circuits for a two-node cluster, with a single, separately powered disk for the cluster lock. For two-node clusters, this single lock disk may not share a power circuit with either node, and it must be an external disk. For three or four node clusters, the disk should not share a power circuit with 50% or more of the nodes. &lt;BR /&gt;&lt;BR /&gt;-Amit</description>
      <pubDate>Mon, 29 May 2006 23:29:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981300#M698362</guid>
      <dc:creator>Chauhan Amit</dc:creator>
      <dc:date>2006-05-29T23:29:43Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best practice for cluster lock disk?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981301#M698363</link>
      <description>The lock disk is not dedicated for use as the cluster lock; thus, it can be employed as part of a normal volume group with user data on it. The usable space on the disk is not impacted; the lock disk takes no space away from the disk's volume group. Further, the activation of the volume group on one node does not affect the ability of another node to acquire the cluster lock.&lt;BR /&gt;&lt;BR /&gt;I hope it clarifies ur query.&lt;BR /&gt;&lt;BR /&gt;-Amit</description>
      <pubDate>Mon, 29 May 2006 23:31:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981301#M698363</guid>
      <dc:creator>Chauhan Amit</dc:creator>
      <dc:date>2006-05-29T23:31:44Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best practice for cluster lock disk?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981302#M698364</link>
      <description>Hi Amit,&lt;BR /&gt;&lt;BR /&gt;Thanks for your response.&lt;BR /&gt;&lt;BR /&gt;My Question is, &lt;BR /&gt;&lt;BR /&gt;It has to be from cluster package VG? or it can be?&lt;BR /&gt;&lt;BR /&gt;For examaple, I have a VG on shared storage and it is not being used for any cluster applications.It is activated on one node and being used for some other purpose. but the disks on the vg's are visiable from all the nodes.&lt;BR /&gt;&lt;BR /&gt;can i use a disk from this VG?&lt;BR /&gt;&lt;BR /&gt;Many thanks in advance..</description>
      <pubDate>Mon, 29 May 2006 23:45:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981302#M698364</guid>
      <dc:creator>Ganesan R</dc:creator>
      <dc:date>2006-05-29T23:45:38Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best practice for cluster lock disk?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981303#M698365</link>
      <description>HI Ganesan,&lt;BR /&gt;&lt;BR /&gt;You can use Disk from this VG.&lt;BR /&gt;&lt;BR /&gt;-Amit</description>
      <pubDate>Mon, 29 May 2006 23:47:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981303#M698365</guid>
      <dc:creator>Chauhan Amit</dc:creator>
      <dc:date>2006-05-29T23:47:33Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best practice for cluster lock disk?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981304#M698366</link>
      <description>Hi Ganesan,&lt;BR /&gt;&lt;BR /&gt;You can use any pv from any VG.But that PV should be in shared Storage &amp;amp; it should be visible from both nodes..Even if you don't have Cluster lock your cluster will run.But once in 45 mts it will generate error msg in syslog.But if any Cluster tie breaker happens that time ur Entire cluster will down&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;With Cheers&lt;BR /&gt;Arunkumar.B</description>
      <pubDate>Tue, 30 May 2006 01:04:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981304#M698366</guid>
      <dc:creator>Arunkumar.B</dc:creator>
      <dc:date>2006-05-30T01:04:03Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best practice for cluster lock disk?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981305#M698367</link>
      <description>&lt;BR /&gt;Hi Gurus,&lt;BR /&gt;&lt;BR /&gt;Thanks for all your responses</description>
      <pubDate>Tue, 30 May 2006 01:49:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981305#M698367</guid>
      <dc:creator>Ganesan R</dc:creator>
      <dc:date>2006-05-30T01:49:27Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best practice for cluster lock disk?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981306#M698368</link>
      <description>Many thanks to all cleared my queries..</description>
      <pubDate>Tue, 30 May 2006 01:51:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/what-is-the-best-practice-for-cluster-lock-disk/m-p/4981306#M698368</guid>
      <dc:creator>Ganesan R</dc:creator>
      <dc:date>2006-05-30T01:51:54Z</dc:date>
    </item>
  </channel>
</rss>

