<?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 help in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-help/m-p/2736012#M713625</link>
    <description>Hello Leeji,&lt;BR /&gt;The clusterlock disk issue can be resolved using this document: UXSGKBAN00000022  &lt;BR /&gt;TITLE: "Cluster Lock On Disk {dsk} Is Missing"&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I have seen the problem with vg00 when a boot disk of one node in the cluster was created from a "dd" of vg00 from another node in the cluster.  The problem is that the VGID (volume group ID) is the SAME on both server's vg00 disks.  When a modification is made to vg00 on one node, but not the other, and subsequently, a cmquerycl, cmcheckconf or cmapplyconf are performed, SG inspects all VG's in each /etc/lvmtab to see if they have the same VGID between nodes.  If so, SG believes them to be one VG common to both nodes.  After this, if it notices that the LVM structures of vg00 don't match between the nodes, though the VGID is the same - hence the errors you see.&lt;BR /&gt;&lt;BR /&gt;If you used the 'dd' command to create the second server's boot disk, the ONLY resolution is to reinstall that disk.  I have seen some customers do this quickly by using a make_recovery tape created from one server, and restore it to the other server... then customize it's hostname and IP etc.&lt;BR /&gt;&lt;BR /&gt;This document discusses the issue:&lt;BR /&gt;UXSGKBRC00007573  &lt;BR /&gt;TITLE: "Cloned VG00s and ServiceGuard configuration failures"  &lt;BR /&gt;&lt;BR /&gt;-s.</description>
    <pubDate>Wed, 05 Jun 2002 11:56:46 GMT</pubDate>
    <dc:creator>Stephen Doud</dc:creator>
    <dc:date>2002-06-05T11:56:46Z</dc:date>
    <item>
      <title>cluster help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-help/m-p/2736007#M713620</link>
      <description>Hi.all&lt;BR /&gt;I found following message in syslog.log&lt;BR /&gt;WARNING: Cluster lock on disk /dev/dsk/c1t5d0 is missing!&lt;BR /&gt; Until it is fixed, a single failure could&lt;BR /&gt;cause all nodes in the cluster to crash&lt;BR /&gt; and &lt;BR /&gt;when I use cmapply command following appeared&lt;BR /&gt;Error: Volume group /dev/vg00 is configured differently on node dnappc2 than on node dnappc1&lt;BR /&gt;Error: Volume group /dev/vg00 on node dnappc1 does not appear to have a physical volume &lt;BR /&gt;&lt;BR /&gt;corresponding to /dev/dsk/c0t5d0 on node dn.&lt;BR /&gt;Error: Volume group /dev/vg00 on node dnappc1 does not appear to have a physical volume &lt;BR /&gt;&lt;BR /&gt;corresponding to /dev/dsk/c0t8d0 on node dn.&lt;BR /&gt;Do you ahve any idea?&lt;BR /&gt;model :D390 -2-&lt;BR /&gt;array:autoraid -1-&lt;BR /&gt;with inline scsi cable -4-&lt;BR /&gt;external scsi card -4-&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 03 Jun 2002 01:43:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-help/m-p/2736007#M713620</guid>
      <dc:creator>leeji</dc:creator>
      <dc:date>2002-06-03T01:43:31Z</dc:date>
    </item>
    <item>
      <title>Re: cluster help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-help/m-p/2736008#M713621</link>
      <description>Take a look at this document, it may be applicable to your problem.&lt;BR /&gt;DocID=KBRC00001982&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://support2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=500000000092231" target="_blank"&gt;http://support2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=500000000092231&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hope it helps..</description>
      <pubDate>Mon, 03 Jun 2002 02:19:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-help/m-p/2736008#M713621</guid>
      <dc:creator>S.K. Chan</dc:creator>
      <dc:date>2002-06-03T02:19:15Z</dc:date>
    </item>
    <item>
      <title>Re: cluster help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-help/m-p/2736009#M713622</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;It seams that you tried to share the vg00. It is not possible.&lt;BR /&gt;Check the cluster ascii file to see if there is the vg00 (VOLUME_GROUP /dev/vg00).&lt;BR /&gt;In that case try cmapplyconf after deleting this line.&lt;BR /&gt;&lt;BR /&gt;Fr??d??ric</description>
      <pubDate>Mon, 03 Jun 2002 08:46:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-help/m-p/2736009#M713622</guid>
      <dc:creator>Frederic Sevestre</dc:creator>
      <dc:date>2002-06-03T08:46:51Z</dc:date>
    </item>
    <item>
      <title>Re: cluster help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-help/m-p/2736010#M713623</link>
      <description>No , thereis no VG00 in ascii file&lt;BR /&gt;Um, So I try to recompile cluster file using cmapply .&lt;BR /&gt;But same error appears!!&lt;BR /&gt;Does it need to reinstall OS?&lt;BR /&gt;Is there any solution or idea?&lt;BR /&gt;very interesting thing!!!</description>
      <pubDate>Tue, 04 Jun 2002 00:39:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-help/m-p/2736010#M713623</guid>
      <dc:creator>leeji</dc:creator>
      <dc:date>2002-06-04T00:39:38Z</dc:date>
    </item>
    <item>
      <title>Re: cluster help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-help/m-p/2736011#M713624</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;What is the output of the vgdisplay for vg00 on server dnappc1.&lt;BR /&gt;&lt;BR /&gt;vgdisplay -v /dev/vg00 &lt;BR /&gt;&lt;BR /&gt;Can you post the output of this vgdisplay for us to have a look. Also post the output (/tmp/cmclconf_chk) of this command.&lt;BR /&gt;&lt;BR /&gt;cmcheckconf -v -C /etc/cmcluster/cmclconf.ascii &amp;gt;/tmp/cmchkconf.txt&lt;BR /&gt;&lt;BR /&gt;Here cmclconf.ascii is your cluster conf file. If possible post the outpur of the cmquerycl command too,&lt;BR /&gt;&lt;BR /&gt;cmquerycl -v -n node1 -n node2 &amp;gt;/tmp/cmqerycl.txt&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;regds&lt;BR /&gt;</description>
      <pubDate>Tue, 04 Jun 2002 01:26:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-help/m-p/2736011#M713624</guid>
      <dc:creator>Sanjay_6</dc:creator>
      <dc:date>2002-06-04T01:26:57Z</dc:date>
    </item>
    <item>
      <title>Re: cluster help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-help/m-p/2736012#M713625</link>
      <description>Hello Leeji,&lt;BR /&gt;The clusterlock disk issue can be resolved using this document: UXSGKBAN00000022  &lt;BR /&gt;TITLE: "Cluster Lock On Disk {dsk} Is Missing"&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I have seen the problem with vg00 when a boot disk of one node in the cluster was created from a "dd" of vg00 from another node in the cluster.  The problem is that the VGID (volume group ID) is the SAME on both server's vg00 disks.  When a modification is made to vg00 on one node, but not the other, and subsequently, a cmquerycl, cmcheckconf or cmapplyconf are performed, SG inspects all VG's in each /etc/lvmtab to see if they have the same VGID between nodes.  If so, SG believes them to be one VG common to both nodes.  After this, if it notices that the LVM structures of vg00 don't match between the nodes, though the VGID is the same - hence the errors you see.&lt;BR /&gt;&lt;BR /&gt;If you used the 'dd' command to create the second server's boot disk, the ONLY resolution is to reinstall that disk.  I have seen some customers do this quickly by using a make_recovery tape created from one server, and restore it to the other server... then customize it's hostname and IP etc.&lt;BR /&gt;&lt;BR /&gt;This document discusses the issue:&lt;BR /&gt;UXSGKBRC00007573  &lt;BR /&gt;TITLE: "Cloned VG00s and ServiceGuard configuration failures"  &lt;BR /&gt;&lt;BR /&gt;-s.</description>
      <pubDate>Wed, 05 Jun 2002 11:56:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-help/m-p/2736012#M713625</guid>
      <dc:creator>Stephen Doud</dc:creator>
      <dc:date>2002-06-05T11:56:46Z</dc:date>
    </item>
    <item>
      <title>Re: cluster help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-help/m-p/2736013#M713626</link>
      <description>Hi:&lt;BR /&gt;&lt;BR /&gt;  Try this..&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;1.halt the cluster&lt;BR /&gt;&lt;BR /&gt;2. vgchange -a y /dev/vglock (activate the cluster lock on the node)&lt;BR /&gt;&lt;BR /&gt;3. cmapplyconf -C /etc/cmcluster/cmclconf&lt;BR /&gt; &lt;BR /&gt; -P /etc/cmcluster/pkgdir/pkgconf&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;4.   vgchange -a n /dev/vglock(deactivate)&lt;BR /&gt;&lt;BR /&gt;5. start the cluster.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 05 Jun 2002 12:29:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-help/m-p/2736013#M713626</guid>
      <dc:creator>Giri Sekar.</dc:creator>
      <dc:date>2002-06-05T12:29:59Z</dc:date>
    </item>
  </channel>
</rss>

