<?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 LUN Changing in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-lun-changing/m-p/5035463#M695384</link>
    <description>I have a two node cluster that is using an LVM VG: /dev/vglock There are no LV's or File Systems under this VG, it's only used for the lock disk. The issue is that our SAN group here is making some changes with the SAN configuration and the LUN device for this lock disk is changing, i.e: Device c4t2d0 will be changing to c6t2d0&lt;BR /&gt;&lt;BR /&gt;What steps do I need to do for this Lock VG to ensure that when the SAN work is completed my two servers in the Cluster will still be able to access this lock device ?</description>
    <pubDate>Wed, 21 Mar 2007 14:07:29 GMT</pubDate>
    <dc:creator>MikeL_4</dc:creator>
    <dc:date>2007-03-21T14:07:29Z</dc:date>
    <item>
      <title>Lock Disk LUN Changing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-lun-changing/m-p/5035463#M695384</link>
      <description>I have a two node cluster that is using an LVM VG: /dev/vglock There are no LV's or File Systems under this VG, it's only used for the lock disk. The issue is that our SAN group here is making some changes with the SAN configuration and the LUN device for this lock disk is changing, i.e: Device c4t2d0 will be changing to c6t2d0&lt;BR /&gt;&lt;BR /&gt;What steps do I need to do for this Lock VG to ensure that when the SAN work is completed my two servers in the Cluster will still be able to access this lock device ?</description>
      <pubDate>Wed, 21 Mar 2007 14:07:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-lun-changing/m-p/5035463#M695384</guid>
      <dc:creator>MikeL_4</dc:creator>
      <dc:date>2007-03-21T14:07:29Z</dc:date>
    </item>
    <item>
      <title>Re: Lock Disk LUN Changing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-lun-changing/m-p/5035464#M695385</link>
      <description>Mike,&lt;BR /&gt;&lt;BR /&gt;   You will need to modify the cluster config and redistribute the binary to all the nodes&lt;BR /&gt;&lt;BR /&gt;  # cd /etc/cmcluster&lt;BR /&gt;  # cmgetconf cluster.conf&lt;BR /&gt;  # vi cluster.conf&lt;BR /&gt;&lt;BR /&gt;  Modify the cluster lock disk&lt;BR /&gt; &lt;BR /&gt;  # cmcheckconf -C cluster.conf&lt;BR /&gt;  # cmapplyconf -C cluster.conf&lt;BR /&gt;&lt;BR /&gt;Sundar.</description>
      <pubDate>Wed, 21 Mar 2007 14:12:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-lun-changing/m-p/5035464#M695385</guid>
      <dc:creator>Sundar_7</dc:creator>
      <dc:date>2007-03-21T14:12:17Z</dc:date>
    </item>
    <item>
      <title>Re: Lock Disk LUN Changing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-lun-changing/m-p/5035465#M695386</link>
      <description>This might be an ideal time to convert to a Quorum Server rather than using a lock disk. The software is free and a little Linux box makes a dandy QS and you never have to worry about changes like this again. You will find that a QS is a better answer in all respects.</description>
      <pubDate>Wed, 21 Mar 2007 14:22:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-lun-changing/m-p/5035465#M695386</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2007-03-21T14:22:00Z</dc:date>
    </item>
    <item>
      <title>Re: Lock Disk LUN Changing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-lun-changing/m-p/5035466#M695387</link>
      <description>Thanks Sundar&lt;BR /&gt;&lt;BR /&gt;Clay thats for the suggestion but that isn't an option at this time within this environment.</description>
      <pubDate>Wed, 21 Mar 2007 15:12:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-lun-changing/m-p/5035466#M695387</guid>
      <dc:creator>MikeL_4</dc:creator>
      <dc:date>2007-03-21T15:12:29Z</dc:date>
    </item>
    <item>
      <title>Re: Lock Disk LUN Changing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-lun-changing/m-p/5035467#M695388</link>
      <description>Note that changing the cluster lock disk has to be done with the cluster halted.&lt;BR /&gt;&lt;BR /&gt;And a QS does not really solve this particular problem anyway since it too would require the cluster to be halted if the QS needed to be moved to a different IP address.&lt;BR /&gt;&lt;BR /&gt;The QS does have some advantages, but this is not one of them!</description>
      <pubDate>Thu, 22 Mar 2007 03:20:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lock-disk-lun-changing/m-p/5035467#M695388</guid>
      <dc:creator>John Bigg</dc:creator>
      <dc:date>2007-03-22T03:20:03Z</dc:date>
    </item>
  </channel>
</rss>

