<?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 concern in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-concern/m-p/4756341#M660557</link>
    <description>Thanks a ton Ismail!&lt;BR /&gt;&lt;BR /&gt;I got a clear picture on that ... :) keeps rocking</description>
    <pubDate>Tue, 22 Feb 2011 13:46:35 GMT</pubDate>
    <dc:creator>gany59</dc:creator>
    <dc:date>2011-02-22T13:46:35Z</dc:date>
    <item>
      <title>cluster concern</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-concern/m-p/4756338#M660554</link>
      <description>Hello techies,&lt;BR /&gt;&lt;BR /&gt;I have the output on the cluster configuration file like below :&lt;BR /&gt;&lt;BR /&gt;FIRST_CLUSTER_LOCK_VG /dev/vgsyb&lt;BR /&gt;for node 1:&lt;BR /&gt;FIRST_CLUSTER_LOCK_PV /dev/dsk/c2t0d0&lt;BR /&gt;for node 2:&lt;BR /&gt;FIRST_CLUSTER_LOCK_PV /dev/dsk/c6t0d0&lt;BR /&gt;&lt;BR /&gt;I got confused that, in the cluster concept we are exporting the same disk to the adoptive node. then how the disk device file is differ.&lt;BR /&gt;&lt;BR /&gt;Please clarrify this. Lock disk in the one what we shared to all the nodes right ?</description>
      <pubDate>Tue, 22 Feb 2011 12:08:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-concern/m-p/4756338#M660554</guid>
      <dc:creator>gany59</dc:creator>
      <dc:date>2011-02-22T12:08:08Z</dc:date>
    </item>
    <item>
      <title>Re: cluster concern</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-concern/m-p/4756339#M660555</link>
      <description>The cluster lock disk has to be the same disk, but for node1 it is named c2t0d0, the name on node2 is c6t0d0 - still the same disk.&lt;BR /&gt;&lt;BR /&gt;Check vgdisplay of vgsyb to confirm.</description>
      <pubDate>Tue, 22 Feb 2011 12:13:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-concern/m-p/4756339#M660555</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2011-02-22T12:13:48Z</dc:date>
    </item>
    <item>
      <title>Re: cluster concern</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-concern/m-p/4756340#M660556</link>
      <description>Hi gany,&lt;BR /&gt;&lt;BR /&gt;The kernel of node1 gives the disk an instance number and by default the number after c on Legacy DSF's default to the instance of the bus connected to that disk. Node2 has a different kernel and it generates a different instance number and hence a different device file for the same disk on different nodes. So relating to your question would speak in terms of "the kernel in node1" and the "kernel in node2" and hence as instance numbers are given by the kernel... will generate different DSFs.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Ismail Azad</description>
      <pubDate>Tue, 22 Feb 2011 13:41:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-concern/m-p/4756340#M660556</guid>
      <dc:creator>Ismail Azad</dc:creator>
      <dc:date>2011-02-22T13:41:38Z</dc:date>
    </item>
    <item>
      <title>Re: cluster concern</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-concern/m-p/4756341#M660557</link>
      <description>Thanks a ton Ismail!&lt;BR /&gt;&lt;BR /&gt;I got a clear picture on that ... :) keeps rocking</description>
      <pubDate>Tue, 22 Feb 2011 13:46:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-concern/m-p/4756341#M660557</guid>
      <dc:creator>gany59</dc:creator>
      <dc:date>2011-02-22T13:46:35Z</dc:date>
    </item>
  </channel>
</rss>

