<?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: Help on cluster hang in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650266#M99201</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt; i have a cluster of two node ES47 with fiber interconnect.&lt;BR /&gt;Your configuration seems to have only two nodes in the cluster and there is no&lt;BR /&gt;quorum disk.&lt;BR /&gt;&lt;BR /&gt;Looks like in your case, as one node is down, the cluster does not have&lt;BR /&gt;quorum to continue and hence other cluster node is in a Hang state.&lt;BR /&gt;In such case, only once the cluster quorum is met, the other node gets out&lt;BR /&gt;of the hang state&lt;BR /&gt;&lt;BR /&gt;Example:&lt;BR /&gt;Node A - Votes=1&lt;BR /&gt;Node B - Votes=1&lt;BR /&gt;&lt;BR /&gt;In this case Quorum = 2.&lt;BR /&gt;* when both Node A &amp;amp; Node B is up, Votes = 1 + 1 = 2. Quorum (=2) is met.&lt;BR /&gt;&lt;BR /&gt;* If node A goes down (for whatever reason).&lt;BR /&gt;  Only Node B is up, its votes=1. Since Quorum is 2, Node B will now be in a&lt;BR /&gt;  Hang state as the Quorum is not met.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt; The boot hang just after the message: %SYSINIT-I- waiting to form or join an&lt;BR /&gt;&amp;gt;&amp;gt; OpenVMS Cluster&lt;BR /&gt;&lt;BR /&gt;You need to give more information about you cluster, such as&lt;BR /&gt;what is the value of &lt;BR /&gt;VOTES ?&lt;BR /&gt;EXPECTED_VOTES ?&lt;BR /&gt;&lt;BR /&gt;Based on this the Quorum of the cluster would get decided.&lt;BR /&gt;&lt;BR /&gt;The most likely cause of the Node in hang state looks like because the cluster&lt;BR /&gt;quorum is not met. However you need to give the values of the above&lt;BR /&gt;parameters in order for us to confirm it.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;For more details about OpenVMS Cluster configuration, refer -&lt;BR /&gt;&lt;A href="http://labs.hoffmanlabs.com/node/153" target="_blank"&gt;http://labs.hoffmanlabs.com/node/153&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Murali</description>
    <pubDate>Mon, 21 Jun 2010 02:39:50 GMT</pubDate>
    <dc:creator>P Muralidhar Kini</dc:creator>
    <dc:date>2010-06-21T02:39:50Z</dc:date>
    <item>
      <title>Help on cluster hang</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650264#M99199</link>
      <description>Hi i have a cluster of two node ES47 with fiber interconnect. Yesterday I lost one of the ES47 because of a cpu problem. During the wait of the replacement, I try to boot one of my DS25 in the cluster using the same root of my ES47. The boot hang just after the message: %SYSINIT-I- waiting to form or join an OpenVMS Cluster&lt;BR /&gt;&lt;BR /&gt;Any Idea</description>
      <pubDate>Mon, 21 Jun 2010 00:31:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650264#M99199</guid>
      <dc:creator>BLANQUART</dc:creator>
      <dc:date>2010-06-21T00:31:01Z</dc:date>
    </item>
    <item>
      <title>Re: Help on cluster hang</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650265#M99200</link>
      <description>Do you use a Quorum disk ?&lt;BR /&gt;Do you use something like AMDS ?&lt;BR /&gt;&lt;BR /&gt;You can from the console prompt boot min and adjust quorum using sysgen parameters. &lt;BR /&gt;&lt;BR /&gt;If think you may need to revise your cluster config.</description>
      <pubDate>Mon, 21 Jun 2010 01:10:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650265#M99200</guid>
      <dc:creator>Thomas Ritter</dc:creator>
      <dc:date>2010-06-21T01:10:31Z</dc:date>
    </item>
    <item>
      <title>Re: Help on cluster hang</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650266#M99201</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt; i have a cluster of two node ES47 with fiber interconnect.&lt;BR /&gt;Your configuration seems to have only two nodes in the cluster and there is no&lt;BR /&gt;quorum disk.&lt;BR /&gt;&lt;BR /&gt;Looks like in your case, as one node is down, the cluster does not have&lt;BR /&gt;quorum to continue and hence other cluster node is in a Hang state.&lt;BR /&gt;In such case, only once the cluster quorum is met, the other node gets out&lt;BR /&gt;of the hang state&lt;BR /&gt;&lt;BR /&gt;Example:&lt;BR /&gt;Node A - Votes=1&lt;BR /&gt;Node B - Votes=1&lt;BR /&gt;&lt;BR /&gt;In this case Quorum = 2.&lt;BR /&gt;* when both Node A &amp;amp; Node B is up, Votes = 1 + 1 = 2. Quorum (=2) is met.&lt;BR /&gt;&lt;BR /&gt;* If node A goes down (for whatever reason).&lt;BR /&gt;  Only Node B is up, its votes=1. Since Quorum is 2, Node B will now be in a&lt;BR /&gt;  Hang state as the Quorum is not met.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt; The boot hang just after the message: %SYSINIT-I- waiting to form or join an&lt;BR /&gt;&amp;gt;&amp;gt; OpenVMS Cluster&lt;BR /&gt;&lt;BR /&gt;You need to give more information about you cluster, such as&lt;BR /&gt;what is the value of &lt;BR /&gt;VOTES ?&lt;BR /&gt;EXPECTED_VOTES ?&lt;BR /&gt;&lt;BR /&gt;Based on this the Quorum of the cluster would get decided.&lt;BR /&gt;&lt;BR /&gt;The most likely cause of the Node in hang state looks like because the cluster&lt;BR /&gt;quorum is not met. However you need to give the values of the above&lt;BR /&gt;parameters in order for us to confirm it.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;For more details about OpenVMS Cluster configuration, refer -&lt;BR /&gt;&lt;A href="http://labs.hoffmanlabs.com/node/153" target="_blank"&gt;http://labs.hoffmanlabs.com/node/153&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Murali</description>
      <pubDate>Mon, 21 Jun 2010 02:39:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650266#M99201</guid>
      <dc:creator>P Muralidhar Kini</dc:creator>
      <dc:date>2010-06-21T02:39:50Z</dc:date>
    </item>
    <item>
      <title>Re: Help on cluster hang</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650267#M99202</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;To get the cluster wide details, you need to provide the values of CL_VOTES,&lt;BR /&gt;CL_EXP and CL_QUORUM parameters.&lt;BR /&gt;&lt;BR /&gt;Command -&lt;BR /&gt;&lt;BR /&gt;$SHOW CLUSTER/CONT&lt;BR /&gt;Command &amp;gt; add CL_VOTES,CL_EXP,CL_QUORUM&lt;BR /&gt;&lt;BR /&gt;Provide the output of the above command.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Murali</description>
      <pubDate>Mon, 21 Jun 2010 03:04:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650267#M99202</guid>
      <dc:creator>P Muralidhar Kini</dc:creator>
      <dc:date>2010-06-21T03:04:29Z</dc:date>
    </item>
    <item>
      <title>Re: Help on cluster hang</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650268#M99203</link>
      <description>Blanquart, is your cluster still running with the one ES47 or have you rebooted things back to "normal" after the CPU was replaced?  If you're still running with one node and trying to add the DS25 and it's stopping at "form or join" you might try halting the DS25 and rebooting it with flags to enable tracking the activities of the system during the boot.  To wit you're putting the primary bootstrap into verbose mode.  This setting is variable depending on your CURRENT root.  If my system boots from SYS5 then I'd use the command boot -fl 5,30000 to make this happen and watch for the system to hang and the last function should be what caused the hang.&lt;BR /&gt;&lt;BR /&gt;However if you've already gotten the cluster back into full operation we can't reach into the ozone and find out the cause of what hung your DS25.  There could be a hardware configuration conflict between the DS25 and ES47 that caused the hang.  The only way to identify that would be the verbose boot and that still might not be totally clear.&lt;BR /&gt;&lt;BR /&gt;bob</description>
      <pubDate>Mon, 21 Jun 2010 03:26:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650268#M99203</guid>
      <dc:creator>Bob Blunt</dc:creator>
      <dc:date>2010-06-21T03:26:33Z</dc:date>
    </item>
    <item>
      <title>Re: Help on cluster hang</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650269#M99204</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;A number of things can be the cause for this problem.&lt;BR /&gt;The system parameters, VOTES, EXPECTED_VOTES, DISK_QUORUM etc. To form a VMS cluster, you need to adjust VOTES and EXPECTED_VOTES. These two define whether a system will actually boot &lt;BR /&gt;or wait until sufficient quorum is available. &lt;BR /&gt;&lt;BR /&gt;Below is the link where similar problem was discussed earlier. &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1277094513523+28353475&amp;amp;threadId=1282524" target="_blank"&gt;http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1277094513523+28353475&amp;amp;threadId=1282524&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Refer below link for some other details. &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.itec.suny.edu/scsys/vms/vmsdoc/72final/6534/6534pro_009.html" target="_blank"&gt;http://www.itec.suny.edu/scsys/vms/vmsdoc/72final/6534/6534pro_009.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Ketan&lt;BR /&gt;</description>
      <pubDate>Mon, 21 Jun 2010 03:49:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650269#M99204</guid>
      <dc:creator>Shriniketan Bhagwat</dc:creator>
      <dc:date>2010-06-21T03:49:13Z</dc:date>
    </item>
    <item>
      <title>Re: Help on cluster hang</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650270#M99205</link>
      <description>Try to boot with &lt;BR /&gt;&lt;BR /&gt;b -fl 0,20000&lt;BR /&gt;&lt;BR /&gt;This will add a lot of debugging, and then, post the last lines displayed here.</description>
      <pubDate>Mon, 21 Jun 2010 05:51:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650270#M99205</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2010-06-21T05:51:13Z</dc:date>
    </item>
    <item>
      <title>Re: Help on cluster hang</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650271#M99206</link>
      <description>It doesn't seem like a voting issue here, it seems more like a communication issue.   &lt;BR /&gt;&lt;BR /&gt;What do you mean when you say you have a "Fiber Interconnect" ?&lt;BR /&gt;&lt;BR /&gt;There is no FC interconnect that I am aware of.   I assume that it is ethernet over Fibre.   Is the interconnect Point-to-Point?   I guess the question really is whether the DS25 can talk to the ES47.   (Layer 2 comms ??)&lt;BR /&gt;&lt;BR /&gt;Dave</description>
      <pubDate>Mon, 21 Jun 2010 12:44:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650271#M99206</guid>
      <dc:creator>The Brit</dc:creator>
      <dc:date>2010-06-21T12:44:23Z</dc:date>
    </item>
    <item>
      <title>Re: Help on cluster hang</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650272#M99207</link>
      <description>Sorry for the typo, I meant&lt;BR /&gt;&lt;BR /&gt;b -fl 5,20000&lt;BR /&gt;&lt;BR /&gt;If you have enabled the log of the startup, see if you have a file in sys$sysdevice:[SYS5.sysexe]startup.log</description>
      <pubDate>Mon, 21 Jun 2010 13:39:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650272#M99207</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2010-06-21T13:39:23Z</dc:date>
    </item>
    <item>
      <title>Re: Help on cluster hang</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650273#M99208</link>
      <description>Rather than being a voting issue, I would think this is either a communication issue (is the DS25 connected to the same network as the ES47?) or else the DS25 is booting from the wrong root directory.&lt;BR /&gt;&lt;BR /&gt;You can test this by the following:&lt;BR /&gt;&lt;BR /&gt;- put a crossover network cable between the ES47 and the DS25;&lt;BR /&gt;- login to the surviving ES47 (assuming it's booted and running) and type in SHOW LOGICAL SYS$SYSROOT&lt;BR /&gt;&lt;BR /&gt;If SYS$SYSROOT ends in SYS0. then you'll need to boot the DS25 off a different root (e.g. SYS1) or the lock manager will step in during boot and prevent the second system from booting.&lt;BR /&gt;&lt;BR /&gt;Steve</description>
      <pubDate>Tue, 22 Jun 2010 06:13:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650273#M99208</guid>
      <dc:creator>Steve Reece_3</dc:creator>
      <dc:date>2010-06-22T06:13:58Z</dc:date>
    </item>
    <item>
      <title>Re: Help on cluster hang</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650274#M99209</link>
      <description>Thanks for all your answers.&lt;BR /&gt;&lt;BR /&gt;I have resolve the issue in booting another DS25 with other fiber cable in the cluster. It appears to be some faulting fiber wich prevent the host to correctly access the quorum disk on the SAN. &lt;BR /&gt;&lt;BR /&gt;Now my ES47 is back and all is OK&lt;BR /&gt;&lt;BR /&gt;Rgs</description>
      <pubDate>Wed, 23 Jun 2010 07:14:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650274#M99209</guid>
      <dc:creator>BLANQUART</dc:creator>
      <dc:date>2010-06-23T07:14:03Z</dc:date>
    </item>
    <item>
      <title>Re: Help on cluster hang</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650275#M99210</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Good that you have posted the solution to the problem.&lt;BR /&gt;It was infact more of a communication issue rather than a voting problem.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt; It appears to be some faulting fiber wich prevent the host to correctly&lt;BR /&gt;&amp;gt;&amp;gt; access the quorum disk on the SAN. &lt;BR /&gt;Did not know that you had a quorum disk also in your setup.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt; Thanks for all your answers.&lt;BR /&gt;Refer the following link which says how you can thank the forum-&lt;BR /&gt;&lt;A href="http://forums11.itrc.hp.com/service/forums/helptips.do?#28" target="_blank"&gt;http://forums11.itrc.hp.com/service/forums/helptips.do?#28&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Murali</description>
      <pubDate>Wed, 23 Jun 2010 07:21:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650275#M99210</guid>
      <dc:creator>P Muralidhar Kini</dc:creator>
      <dc:date>2010-06-23T07:21:08Z</dc:date>
    </item>
    <item>
      <title>Re: Help on cluster hang</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650276#M99211</link>
      <description>BLANQUART,&lt;BR /&gt;&lt;BR /&gt;"It appears to be some faulting fiber wich prevent the host to correctly access the quorum disk on the SAN."&lt;BR /&gt;&lt;BR /&gt;But wasn't the "root" you were booting from also on the SAN?  My guess is that it is more likely that he quorum disk was not presented (by the unspecified SAN disk controller) to the FC HBA in the non-working DS25.&lt;BR /&gt;&lt;BR /&gt;It is worth figuring out the cause, so you will know how to get things working if something similar happens in the future.&lt;BR /&gt;&lt;BR /&gt;Jon</description>
      <pubDate>Thu, 24 Jun 2010 18:39:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/help-on-cluster-hang/m-p/4650276#M99211</guid>
      <dc:creator>Jon Pinkley</dc:creator>
      <dc:date>2010-06-24T18:39:34Z</dc:date>
    </item>
  </channel>
</rss>

