<?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 - Service Guard in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-service-guard/m-p/3026630#M707802</link>
    <description>Hi Vasikaran,&lt;BR /&gt;&lt;BR /&gt;Halt the cluster.&lt;BR /&gt;&lt;BR /&gt;Leave it activated with "vgchange -a y".  cmapplyconf will take care of making it cluster aware. But make sure it is activated on the node from which you are applying the configuration.&lt;BR /&gt;&lt;BR /&gt;-Sri</description>
    <pubDate>Thu, 17 Jul 2003 22:30:46 GMT</pubDate>
    <dc:creator>Sridhar Bhaskarla</dc:creator>
    <dc:date>2003-07-17T22:30:46Z</dc:date>
    <item>
      <title>Cluster Lock - Service Guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-service-guard/m-p/3026626#M707798</link>
      <description>I need to move the cluster Lock VG / PV from one storage to another. Since i am planning to use a data VG for the cluster lock VG, how do i go about it. This is a new data VG.&lt;BR /&gt;steps i am thinking of: &lt;BR /&gt;Edit the ascii.file for new LOCK VG/PV info.;&lt;BR /&gt;check ; vgchange -a y &lt;DATA_CUM_LOCK_VG&gt; ; apply.&lt;BR /&gt;Since i am doing -a y on the VG, and have the details of VOLUME GROUP in the tail of the ascii file, will it be enough to make the VG cluster aware ?. Is there anything that i am missing ?.&lt;BR /&gt;&lt;BR /&gt;Thanks, &lt;BR /&gt;&lt;BR /&gt;Vasikaran&lt;/DATA_CUM_LOCK_VG&gt;</description>
      <pubDate>Thu, 17 Jul 2003 15:24:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-service-guard/m-p/3026626#M707798</guid>
      <dc:creator>Vasikaran Venkatesan</dc:creator>
      <dc:date>2003-07-17T15:24:20Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Lock - Service Guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-service-guard/m-p/3026627#M707799</link>
      <description>Yes&lt;BR /&gt;&lt;BR /&gt;You ned to re-apply the service-guard binaries&lt;BR /&gt;cmapplyconf -v -C /etc/cmcluster/ -p /etc/cmcluster/&lt;PKG&gt;/&lt;PKG.CONF&gt; ....&lt;BR /&gt;&lt;BR /&gt;This process will write the relavent information into the lock disk.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Tim&lt;/PKG.CONF&gt;&lt;/PKG&gt;</description>
      <pubDate>Thu, 17 Jul 2003 17:23:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-service-guard/m-p/3026627#M707799</guid>
      <dc:creator>Tim D Fulford</dc:creator>
      <dc:date>2003-07-17T17:23:12Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Lock - Service Guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-service-guard/m-p/3026628#M707800</link>
      <description>ofcourse i am doing the cmapply.&lt;BR /&gt;But my question is, since i do "vgchange -a n"&lt;BR /&gt;on the VG, will it be still cluster aware after the cmapply ?.&lt;BR /&gt;&lt;BR /&gt;Since this LockVG is a data VG also, this will be enabled all the time when the package is up, not like the normal VGLOCK, whose main purpose is to handle only Lock mechanism and stay deactivated.</description>
      <pubDate>Thu, 17 Jul 2003 18:02:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-service-guard/m-p/3026628#M707800</guid>
      <dc:creator>Vasikaran Venkatesan</dc:creator>
      <dc:date>2003-07-17T18:02:58Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Lock - Service Guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-service-guard/m-p/3026629#M707801</link>
      <description>You need to edit cluster ascii file at two places, FIRST_CLUSTER_LOCK_VG   /dev/vgname&lt;BR /&gt;and at the end for VOLUME_GROUP  /dev/vgname&lt;BR /&gt;&lt;BR /&gt;If you have a spare disk, create a seperate VG as /dev/vglock rather than naming data VG as &lt;BR /&gt;cluster lock disk, edit cluster ascii file as above and recompile cluster binary file with cmapplyconf.&lt;BR /&gt;&lt;BR /&gt;Srini</description>
      <pubDate>Thu, 17 Jul 2003 20:19:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-service-guard/m-p/3026629#M707801</guid>
      <dc:creator>Srinivas Thokala_1</dc:creator>
      <dc:date>2003-07-17T20:19:52Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Lock - Service Guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-service-guard/m-p/3026630#M707802</link>
      <description>Hi Vasikaran,&lt;BR /&gt;&lt;BR /&gt;Halt the cluster.&lt;BR /&gt;&lt;BR /&gt;Leave it activated with "vgchange -a y".  cmapplyconf will take care of making it cluster aware. But make sure it is activated on the node from which you are applying the configuration.&lt;BR /&gt;&lt;BR /&gt;-Sri</description>
      <pubDate>Thu, 17 Jul 2003 22:30:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-service-guard/m-p/3026630#M707802</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2003-07-17T22:30:46Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Lock - Service Guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-service-guard/m-p/3026631#M707803</link>
      <description>Hi,&lt;BR /&gt;a little addition to Shridar (i hope to wrote it well).&lt;BR /&gt;&lt;BR /&gt;You must activate the vg with&lt;BR /&gt;&lt;BR /&gt;vgchange -a e&lt;BR /&gt;&lt;BR /&gt;since it's already marked as cluster aware.&lt;BR /&gt;&lt;BR /&gt;After the cmapply, close it&lt;BR /&gt;vgchange -a n &lt;BR /&gt;&lt;BR /&gt;and start newly the cluster.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt; Massimo&lt;BR /&gt;</description>
      <pubDate>Fri, 18 Jul 2003 07:14:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-service-guard/m-p/3026631#M707803</guid>
      <dc:creator>Massimo Bianchi</dc:creator>
      <dc:date>2003-07-18T07:14:39Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Lock - Service Guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-service-guard/m-p/3026632#M707804</link>
      <description>Most important you should be aware that for this change you must stop the entire cluster with all its packages(cmhaltcl).&lt;BR /&gt;&lt;BR /&gt;A vgchange -a n does not change the "cluster aware" status of a vg.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Bernhard&lt;BR /&gt;</description>
      <pubDate>Fri, 18 Jul 2003 07:19:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-service-guard/m-p/3026632#M707804</guid>
      <dc:creator>Bernhard Mueller</dc:creator>
      <dc:date>2003-07-18T07:19:43Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Lock - Service Guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-service-guard/m-p/3026633#M707805</link>
      <description>Im sorry my reply offended you.&lt;BR /&gt;&lt;BR /&gt;Here is a manual&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B5158-90044/B5158-90044_top.html&amp;amp;con=/hpux/onlinedocs/B5158-90044/00/00/48-con.html&amp;amp;toc=/hpux/onlinedocs/B5158-90044/00/00/48-toc.html&amp;amp;searchterms=cmapplyconf&amp;amp;queryid=20030718-031139" target="_blank"&gt;http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B5158-90044/B5158-90044_top.html&amp;amp;con=/hpux/onlinedocs/B5158-90044/00/00/48-con.html&amp;amp;toc=/hpux/onlinedocs/B5158-90044/00/00/48-toc.html&amp;amp;searchterms=cmapplyconf&amp;amp;queryid=20030718-031139&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Tim</description>
      <pubDate>Fri, 18 Jul 2003 08:12:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-service-guard/m-p/3026633#M707805</guid>
      <dc:creator>Tim D Fulford</dc:creator>
      <dc:date>2003-07-18T08:12:53Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Lock - Service Guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-service-guard/m-p/3026634#M707806</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;#cmhaltcl&lt;BR /&gt;&lt;BR /&gt;#cp -p /etc/cmcluster/&lt;CLUSTER&gt;.ascii /etc/cmcluster/&lt;CLUSTER&gt;.ascii.old&lt;BR /&gt;&lt;BR /&gt;modify the &lt;CLUSTER&gt;.ascii file&lt;BR /&gt;&lt;BR /&gt;#vgchange -c n /dev/NEW_VG_LOCK (if it is a old vg already in cluster)                        &lt;BR /&gt;&lt;BR /&gt;#vgchange -a y /dev/NEW_VG_LOCK (if it is a new vg)                        &lt;BR /&gt;&lt;BR /&gt;#cmcheckconf -v -C /etc/cmcluster/&lt;CLUSTER&gt;.ascii &lt;BR /&gt;&lt;BR /&gt;#cmapplyconf -v -C /etc/cmcluster/&lt;CLUSTER&gt;.ascii &lt;BR /&gt;&lt;BR /&gt;#cmruncl&lt;BR /&gt;&lt;BR /&gt;Enrico&lt;BR /&gt;&lt;/CLUSTER&gt;&lt;/CLUSTER&gt;&lt;/CLUSTER&gt;&lt;/CLUSTER&gt;&lt;/CLUSTER&gt;</description>
      <pubDate>Fri, 18 Jul 2003 08:41:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-service-guard/m-p/3026634#M707806</guid>
      <dc:creator>Enrico P.</dc:creator>
      <dc:date>2003-07-18T08:41:16Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Lock - Service Guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-service-guard/m-p/3026635#M707807</link>
      <description>Thanks to all of you for the excellent information.</description>
      <pubDate>Fri, 18 Jul 2003 13:18:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-service-guard/m-p/3026635#M707807</guid>
      <dc:creator>Vasikaran Venkatesan</dc:creator>
      <dc:date>2003-07-18T13:18:17Z</dc:date>
    </item>
  </channel>
</rss>

