<?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 Regarding lockLUN in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/regarding-locklun/m-p/4006410#M57503</link>
    <description>Hello, &lt;BR /&gt;&lt;BR /&gt;I would like to know regarding lockLUN&lt;BR /&gt;&lt;BR /&gt;[ENVIRONMENT] &lt;BR /&gt;RHEL AS 4 up4 &lt;BR /&gt;Serviceguard 11.16.10&lt;BR /&gt;&lt;BR /&gt;[QUESTION] &lt;BR /&gt;There are two cluster member as Serviceguard for Linux.&lt;BR /&gt;When a package failover from host-A to host-B, is there possibility to appear like following&lt;BR /&gt;by using cmviewcl command ? &lt;BR /&gt;&lt;BR /&gt;Host-A -----&amp;gt; "unknown"&lt;BR /&gt;Host-B -----&amp;gt; "UP"&lt;BR /&gt;&lt;BR /&gt;Thank you for advice.&lt;BR /&gt;Best Regards.&lt;BR /&gt;/Minoru.Asano</description>
    <pubDate>Thu, 24 May 2007 06:26:28 GMT</pubDate>
    <dc:creator>Minoru Asano</dc:creator>
    <dc:date>2007-05-24T06:26:28Z</dc:date>
    <item>
      <title>Regarding lockLUN</title>
      <link>https://community.hpe.com/t5/operating-system-linux/regarding-locklun/m-p/4006410#M57503</link>
      <description>Hello, &lt;BR /&gt;&lt;BR /&gt;I would like to know regarding lockLUN&lt;BR /&gt;&lt;BR /&gt;[ENVIRONMENT] &lt;BR /&gt;RHEL AS 4 up4 &lt;BR /&gt;Serviceguard 11.16.10&lt;BR /&gt;&lt;BR /&gt;[QUESTION] &lt;BR /&gt;There are two cluster member as Serviceguard for Linux.&lt;BR /&gt;When a package failover from host-A to host-B, is there possibility to appear like following&lt;BR /&gt;by using cmviewcl command ? &lt;BR /&gt;&lt;BR /&gt;Host-A -----&amp;gt; "unknown"&lt;BR /&gt;Host-B -----&amp;gt; "UP"&lt;BR /&gt;&lt;BR /&gt;Thank you for advice.&lt;BR /&gt;Best Regards.&lt;BR /&gt;/Minoru.Asano</description>
      <pubDate>Thu, 24 May 2007 06:26:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/regarding-locklun/m-p/4006410#M57503</guid>
      <dc:creator>Minoru Asano</dc:creator>
      <dc:date>2007-05-24T06:26:28Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding lockLUN</title>
      <link>https://community.hpe.com/t5/operating-system-linux/regarding-locklun/m-p/4006411#M57504</link>
      <description>Yes, it's possible.&lt;BR /&gt;&lt;BR /&gt;It means Host-A does not respond at all, so Host-B does not know if Host-A is crashed or just lost all the ways to communicate with Host-B.&lt;BR /&gt;&lt;BR /&gt;You'll have to inspect Host-A to see what's going on. &lt;BR /&gt;&lt;BR /&gt;If it's running, check "uptime": it should have rebooted itself right after losing network connections to Host-B. Obviously Host-B managed to access the lockLUN first, and Host-A rebooted to avoid the split-brain situation. As cmviewcl (on host-B I think) is reporting host-A as unknown, there may be a network problem preventing host-B from getting information about host-A.&lt;BR /&gt;&lt;BR /&gt;After the network problem is fixed, cmviewcl on host-B should be able to say with confidence that host-A is "down". To make it re-join the cluster, run "cmrunnode host-A"&lt;BR /&gt;or reboot host-A.&lt;BR /&gt;&lt;BR /&gt;If host-A is not running, find out why and fix it (Overheating? Loss of power? Hardware failure?). If there are no network problems and /usr/local/cmcluster/cmcluster.rc has the default value, it should automatically re-join the cluster when it reboots. If not, "cmrunnode host-A" is the command to make it re-join the cluster manually.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Thu, 24 May 2007 13:34:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/regarding-locklun/m-p/4006411#M57504</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2007-05-24T13:34:31Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding lockLUN</title>
      <link>https://community.hpe.com/t5/operating-system-linux/regarding-locklun/m-p/4006412#M57505</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;If you wish, explain the subject of the post versus the question.&lt;BR /&gt;&lt;BR /&gt;Host A is not accessible. Common cause is inconsistent /etc/hosts networking. If you are not using that (see /etc/nsswitch.conf) then it could be DNS.&lt;BR /&gt;&lt;BR /&gt;Start with ping and make sure the nodes recognize each other.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 24 May 2007 13:47:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/regarding-locklun/m-p/4006412#M57505</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2007-05-24T13:47:59Z</dc:date>
    </item>
  </channel>
</rss>

