<?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 Lock Disk Requirments in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-requirments/m-p/2832899#M711301</link>
    <description>I have a two node cluster with the latest MCSG software on 11.0.&lt;BR /&gt;&lt;BR /&gt;My cmquerycl returns nothing for possible lock volume:&lt;BR /&gt;&lt;BR /&gt;Possible Cluster Lock Devices:&lt;BR /&gt;&lt;BR /&gt;LVM volume groups:&lt;BR /&gt;&lt;BR /&gt;/dev/vg_ops1   Node1&lt;BR /&gt;               Node2&lt;BR /&gt;&lt;BR /&gt;and the rest of my shared disk in the same fasion.&lt;BR /&gt;&lt;BR /&gt;What is the requirment of the lock vg?  I edited my config file to plave it on what I'm calling vg_ops4 here is the current vgdisplay:&lt;BR /&gt;&lt;BR /&gt;VG Name                     /dev/vg_ops4&lt;BR /&gt;VG Write Access             read/write     &lt;BR /&gt;VG Status                   available, shared, server &lt;BR /&gt;Max LV                      255    &lt;BR /&gt;Cur LV                      3      &lt;BR /&gt;Open LV                     3      &lt;BR /&gt;Max PV                      16     &lt;BR /&gt;Cur PV                      2      &lt;BR /&gt;Act PV                      2      &lt;BR /&gt;Max PE per PV               18432        &lt;BR /&gt;VGDA                        4   &lt;BR /&gt;PE Size (Mbytes)            4               &lt;BR /&gt;Total PE                    17362   &lt;BR /&gt;Alloc PE                    1344    &lt;BR /&gt;Free PE                     16018   &lt;BR /&gt;Total PVG                   2        &lt;BR /&gt;Total Spare PVs             0              &lt;BR /&gt;Total Spare PVs in use      0                     &lt;BR /&gt;&lt;BR /&gt;I've tried recreating the cluster from scratch, but the problem is cmquerycl doesn't see a possibility for a lock vg.  &lt;BR /&gt;&lt;BR /&gt;Anyone?</description>
    <pubDate>Thu, 24 Oct 2002 17:19:46 GMT</pubDate>
    <dc:creator>Gene Kornacki_2</dc:creator>
    <dc:date>2002-10-24T17:19:46Z</dc:date>
    <item>
      <title>Lock Disk Requirments</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-requirments/m-p/2832899#M711301</link>
      <description>I have a two node cluster with the latest MCSG software on 11.0.&lt;BR /&gt;&lt;BR /&gt;My cmquerycl returns nothing for possible lock volume:&lt;BR /&gt;&lt;BR /&gt;Possible Cluster Lock Devices:&lt;BR /&gt;&lt;BR /&gt;LVM volume groups:&lt;BR /&gt;&lt;BR /&gt;/dev/vg_ops1   Node1&lt;BR /&gt;               Node2&lt;BR /&gt;&lt;BR /&gt;and the rest of my shared disk in the same fasion.&lt;BR /&gt;&lt;BR /&gt;What is the requirment of the lock vg?  I edited my config file to plave it on what I'm calling vg_ops4 here is the current vgdisplay:&lt;BR /&gt;&lt;BR /&gt;VG Name                     /dev/vg_ops4&lt;BR /&gt;VG Write Access             read/write     &lt;BR /&gt;VG Status                   available, shared, server &lt;BR /&gt;Max LV                      255    &lt;BR /&gt;Cur LV                      3      &lt;BR /&gt;Open LV                     3      &lt;BR /&gt;Max PV                      16     &lt;BR /&gt;Cur PV                      2      &lt;BR /&gt;Act PV                      2      &lt;BR /&gt;Max PE per PV               18432        &lt;BR /&gt;VGDA                        4   &lt;BR /&gt;PE Size (Mbytes)            4               &lt;BR /&gt;Total PE                    17362   &lt;BR /&gt;Alloc PE                    1344    &lt;BR /&gt;Free PE                     16018   &lt;BR /&gt;Total PVG                   2        &lt;BR /&gt;Total Spare PVs             0              &lt;BR /&gt;Total Spare PVs in use      0                     &lt;BR /&gt;&lt;BR /&gt;I've tried recreating the cluster from scratch, but the problem is cmquerycl doesn't see a possibility for a lock vg.  &lt;BR /&gt;&lt;BR /&gt;Anyone?</description>
      <pubDate>Thu, 24 Oct 2002 17:19:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-requirments/m-p/2832899#M711301</guid>
      <dc:creator>Gene Kornacki_2</dc:creator>
      <dc:date>2002-10-24T17:19:46Z</dc:date>
    </item>
    <item>
      <title>Re: Lock Disk Requirments</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-requirments/m-p/2832900#M711302</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;This is an existing cluster and you lost the cluster lock disk?  If so, check this link:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000062686621" target="_blank"&gt;http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000062686621&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Did the syslog show any errors?  What were the errors?  Did you include both nodes in your cmquerycl?  &lt;BR /&gt;&lt;BR /&gt;Hope this helps&lt;BR /&gt;&lt;BR /&gt;Chris</description>
      <pubDate>Thu, 24 Oct 2002 17:33:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-requirments/m-p/2832900#M711302</guid>
      <dc:creator>Christopher McCray_1</dc:creator>
      <dc:date>2002-10-24T17:33:29Z</dc:date>
    </item>
    <item>
      <title>Re: Lock Disk Requirments</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-requirments/m-p/2832901#M711303</link>
      <description>Usually the shared disk with the least seek time i.e the disk that can be searched/looked up or queried in the least possible time is selected as the lock disk because time is crucial in obtaining the lock in case of a cluster tie up . This disk is usually suggested by the cmquerycl command itself .&lt;BR /&gt;&lt;BR /&gt;The disk can be a data disk or for that matter any other disk as long as it is seen by both the nodes . &lt;BR /&gt;&lt;BR /&gt;So you can just choose any disk that you deem fit and put that in your config files and apply them to all the nodes and it still will work . THere shouldn't be any issues .</description>
      <pubDate>Thu, 24 Oct 2002 17:36:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-requirments/m-p/2832901#M711303</guid>
      <dc:creator>Ashwani Kashyap</dc:creator>
      <dc:date>2002-10-24T17:36:21Z</dc:date>
    </item>
    <item>
      <title>Re: Lock Disk Requirments</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-requirments/m-p/2832902#M711304</link>
      <description>Also try this link:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000062686663" target="_blank"&gt;http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000062686663&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Chris</description>
      <pubDate>Thu, 24 Oct 2002 17:39:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-requirments/m-p/2832902#M711304</guid>
      <dc:creator>Christopher McCray_1</dc:creator>
      <dc:date>2002-10-24T17:39:34Z</dc:date>
    </item>
    <item>
      <title>Re: Lock Disk Requirments</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-requirments/m-p/2832903#M711305</link>
      <description>NODE_NAME               piggy&lt;BR /&gt;  NETWORK_INTERFACE     lan0&lt;BR /&gt;    STATIONARY_IP       xxx.xxx.xxx.xxx&lt;BR /&gt;  NETWORK_INTERFACE     lan1&lt;BR /&gt;    HEARTBEAT_IP                111.111.111.111 &lt;BR /&gt;&lt;BR /&gt;FIRST_CLUSTER_LOCK_PV /dev/dsk/c5t14d0&lt;BR /&gt;&lt;BR /&gt;NODE_NAME               smelly&lt;BR /&gt;  NETWORK_INTERFACE     lan0&lt;BR /&gt;    STATIONARY_IP       xxx.xxx.xxx.xxx&lt;BR /&gt;  NETWORK_INTERFACE     lan2&lt;BR /&gt;  NETWORK_INTERFACE     lan1&lt;BR /&gt;    HEARTBEAT_IP                111.111.111.112&lt;BR /&gt;  FIRST_CLUSTER_LOCK_PV /dev/dsk/c4t14d0&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;This is what is in my config file and the error in my syslog.log are &lt;BR /&gt;&lt;BR /&gt;ARNING: Cluster lock on disk /dev/dsk/c4t14d0&lt;BR /&gt; is missing!&lt;BR /&gt;</description>
      <pubDate>Thu, 24 Oct 2002 17:41:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-requirments/m-p/2832903#M711305</guid>
      <dc:creator>Gene Kornacki_2</dc:creator>
      <dc:date>2002-10-24T17:41:17Z</dc:date>
    </item>
    <item>
      <title>Re: Lock Disk Requirments</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-requirments/m-p/2832904#M711306</link>
      <description>Given the error you provided, you should look into the first doc I posted.&lt;BR /&gt;&lt;BR /&gt;Chris</description>
      <pubDate>Thu, 24 Oct 2002 17:51:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-requirments/m-p/2832904#M711306</guid>
      <dc:creator>Christopher McCray_1</dc:creator>
      <dc:date>2002-10-24T17:51:04Z</dc:date>
    </item>
    <item>
      <title>Re: Lock Disk Requirments</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-requirments/m-p/2832905#M711307</link>
      <description>Chris,&lt;BR /&gt;&lt;BR /&gt;The cminilockcl is great. &lt;BR /&gt;&lt;BR /&gt;Thanks, I've created it but I suppose it will be about an hour before I find out if it worked.  I can't see why it wouldn't.&lt;BR /&gt;&lt;BR /&gt;And thanks to others who replied.  It's tough getting this and Real Application Cluster going wihtout HP or Oracle support, but it's going and this appears to be the only error. What a great combo!</description>
      <pubDate>Thu, 24 Oct 2002 17:58:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-requirments/m-p/2832905#M711307</guid>
      <dc:creator>Gene Kornacki_2</dc:creator>
      <dc:date>2002-10-24T17:58:11Z</dc:date>
    </item>
    <item>
      <title>Re: Lock Disk Requirments</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-requirments/m-p/2832906#M711308</link>
      <description>Hi Gene,&lt;BR /&gt;&lt;BR /&gt;If the cmquerycl is performed on a node that already has a cluster applied, then it is likely that there are no non-shared, non-clustered VGs left to choose from.  If the present cluster is no longer needed, perform a 'cmdeleteconf' to purge the cluster and remove the cluster references from the disks.&lt;BR /&gt;&lt;BR /&gt;If this is a new cluster, cmquerycl will succeed in finding a cluster lock disk (or any shared disk) ONLY when each node has /etc/lvmtab set up to see the shared VGs.&lt;BR /&gt;&lt;BR /&gt;This requires the Admin to build the VGs on one node and vgimport them on the other nodes.&lt;BR /&gt;When each node can "see" the shared VGs, then cmquerycl can "see" them and identify the common VGs for selection of a cluster lock VG/disk.&lt;BR /&gt;&lt;BR /&gt;-s.</description>
      <pubDate>Fri, 25 Oct 2002 14:43:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-requirments/m-p/2832906#M711308</guid>
      <dc:creator>Stephen Doud</dc:creator>
      <dc:date>2002-10-25T14:43:52Z</dc:date>
    </item>
  </channel>
</rss>

