<?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: OpenVMS cluster - expected_votes in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/openvms-cluster-expected-votes/m-p/5187627#M95551</link>
    <description>Closing the thread.</description>
    <pubDate>Thu, 16 Jul 2009 14:56:04 GMT</pubDate>
    <dc:creator>Peter Zeiszler</dc:creator>
    <dc:date>2009-07-16T14:56:04Z</dc:date>
    <item>
      <title>OpenVMS cluster - expected_votes</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-cluster-expected-votes/m-p/5187624#M95548</link>
      <description>I have a 4 node cluster with 3 of them being voting nodes (vote=1).  On one node the value for expected_votes had a typo so the expected votes was calculated.  Of this I would have expected to see expected_votes calculated to 3 however its coming back as 4.  This is openvms 7.3-2.&lt;BR /&gt;&lt;BR /&gt;I hardcoded the expected votes in modparams.&lt;BR /&gt;Except from SYS$SYSROOT:[SYSEXE]AGEN$PARAMS.REPORT&lt;BR /&gt;EXPECTED_VOTES parameter information:- AUTOGEN parameter calculation has been overridden.   The calculated value was 4.  The value 3 will be used in accordance with the following requirements:EXPECTED_VOTES has been specified by a hard-coded value of 3.&lt;BR /&gt;&lt;BR /&gt;I checked the systems and qdskvotes=0 on all and votes are 1 where they are suppose to be.  When I had a node reboot is when I found out the expected_votes was wrong - had to do a set cluster/expected=3.&lt;BR /&gt;&lt;BR /&gt;Is my understanding how expected_votes is calculated wrong?&lt;BR /&gt;</description>
      <pubDate>Wed, 15 Jul 2009 22:40:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-cluster-expected-votes/m-p/5187624#M95548</guid>
      <dc:creator>Peter Zeiszler</dc:creator>
      <dc:date>2009-07-15T22:40:28Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS cluster - expected_votes</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-cluster-expected-votes/m-p/5187625#M95549</link>
      <description>Here, just establish the VOTES and EXPECTED_VOTES values as appropriate; this is VOTES=1 (for each of three cluster hosts) and EXPECTED_VOTES=3, based on your comments. &lt;BR /&gt;&lt;BR /&gt;At its core, this looks to be an AUTOGEN question more than anything else, and particularly around how AUTOGEN picks a default value for this parameter when you don't establish one.   &lt;BR /&gt;&lt;BR /&gt;This calculation of the default is not related to the operational processing of VOTES and EXPECTED_VOTES and the downstream calculation of quorum within a cluster.&lt;BR /&gt;&lt;BR /&gt;See the AUTOGEN.COM DCL below for the logic used:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;$temp = 1&lt;BR /&gt;$IF cluster THEN GOTO genparams55&lt;BR /&gt;$mscp_device = (F$GETDVI(F$TRNLNM("sys$sysdevice"),"devchar2") .AND. 32) / 32&lt;BR /&gt;$IF .NOT. mscp_device THEN GOTO genparams55&lt;BR /&gt;$temp = 0&lt;BR /&gt;$genparams55:&lt;BR /&gt;$GOSUB Check_overrides&lt;BR /&gt;$IF temp .NE. vaxcluster THEN GOSUB output_overrides&lt;BR /&gt;$temp = F$GETSYI("CLUSTER_EVOTES")&lt;BR /&gt;$temp1= F$GETSYI("EXPECTED_VOTES")&lt;BR /&gt;$IF temp .LT. temp1 THEN temp = temp1&lt;BR /&gt;$param_name = "EXPECTED_VOTES"&lt;BR /&gt;$GOSUB Check_overrides&lt;BR /&gt;$IF temp .NE. expected_votes THEN GOSUB output_overrides&lt;BR /&gt;$temp = agen$d_votes&lt;BR /&gt;$IF satellite THEN temp = 0&lt;BR /&gt;$param_name = "VOTES"&lt;BR /&gt;$GOSUB Check_overrides&lt;BR /&gt;$IF temp .NE. votes THEN GOSUB output_overrides&lt;BR /&gt;$temp = agen$d_mvtimeout&lt;BR /&gt;$param_name = "MVTIMEOUT"&lt;BR /&gt;$GOSUB Check_overrides&lt;BR /&gt;$IF temp .NE. mvtimeout THEN GOSUB output_overrides&lt;BR /&gt;</description>
      <pubDate>Thu, 16 Jul 2009 00:50:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-cluster-expected-votes/m-p/5187625#M95549</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2009-07-16T00:50:39Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS cluster - expected_votes</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-cluster-expected-votes/m-p/5187626#M95550</link>
      <description>You know I should have thought about drilling into autogen.&lt;BR /&gt;Apparently when it first joined the cluster it thought it was a voting member.  I changed the votes but didn't set expected_votes at that time.  So it still remembered its old one and didn't do any calculation but just kept recalling its old value.&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
      <pubDate>Thu, 16 Jul 2009 14:33:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-cluster-expected-votes/m-p/5187626#M95550</guid>
      <dc:creator>Peter Zeiszler</dc:creator>
      <dc:date>2009-07-16T14:33:56Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS cluster - expected_votes</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-cluster-expected-votes/m-p/5187627#M95551</link>
      <description>Closing the thread.</description>
      <pubDate>Thu, 16 Jul 2009 14:56:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-cluster-expected-votes/m-p/5187627#M95551</guid>
      <dc:creator>Peter Zeiszler</dc:creator>
      <dc:date>2009-07-16T14:56:04Z</dc:date>
    </item>
  </channel>
</rss>

