<?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: Quorum fix in DECamds works? in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/quorum-fix-in-decamds-works/m-p/3653830#M72005</link>
    <description>Jan,&lt;BR /&gt;&lt;BR /&gt;I'm sure I've demonstrated this once or twice over the years...&lt;BR /&gt;&lt;BR /&gt;- do you have write access to the target node from your data analyzer node ?&lt;BR /&gt;Test it with trying to force an image exit or modify quotas for a process on that node. Use REPLY/ENABLE on the target node to check the RMDRIVER message.&lt;BR /&gt;&lt;BR /&gt;- what state is the cluster in ? Note that you cannot 'fix quorum' if the node has never joined an existing cluster (i.e. boot one single node with VOTES=1 and  EXPECTED_VOTES=2)&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
    <pubDate>Thu, 20 Oct 2005 09:08:34 GMT</pubDate>
    <dc:creator>Volker Halle</dc:creator>
    <dc:date>2005-10-20T09:08:34Z</dc:date>
    <item>
      <title>Quorum fix in DECamds works?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/quorum-fix-in-decamds-works/m-p/3653829#M72004</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;Has anyone used the quorum fix option in DECamds successfully? I couldnt get it working in a test-cluster, so am I overlooking something?&lt;BR /&gt;&lt;BR /&gt;I tried it using DECamds data analyzer on a node outside the cluster AND on a node within the cluster.&lt;BR /&gt;&lt;BR /&gt;Greets,&lt;BR /&gt;Jan</description>
      <pubDate>Thu, 20 Oct 2005 08:54:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/quorum-fix-in-decamds-works/m-p/3653829#M72004</guid>
      <dc:creator>Jan van den Boogaard</dc:creator>
      <dc:date>2005-10-20T08:54:22Z</dc:date>
    </item>
    <item>
      <title>Re: Quorum fix in DECamds works?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/quorum-fix-in-decamds-works/m-p/3653830#M72005</link>
      <description>Jan,&lt;BR /&gt;&lt;BR /&gt;I'm sure I've demonstrated this once or twice over the years...&lt;BR /&gt;&lt;BR /&gt;- do you have write access to the target node from your data analyzer node ?&lt;BR /&gt;Test it with trying to force an image exit or modify quotas for a process on that node. Use REPLY/ENABLE on the target node to check the RMDRIVER message.&lt;BR /&gt;&lt;BR /&gt;- what state is the cluster in ? Note that you cannot 'fix quorum' if the node has never joined an existing cluster (i.e. boot one single node with VOTES=1 and  EXPECTED_VOTES=2)&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Thu, 20 Oct 2005 09:08:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/quorum-fix-in-decamds-works/m-p/3653830#M72005</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-10-20T09:08:34Z</dc:date>
    </item>
    <item>
      <title>Re: Quorum fix in DECamds works?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/quorum-fix-in-decamds-works/m-p/3653831#M72006</link>
      <description>I use the Availablity Manager running on a non VMS box to help manager systems.  The adjust quorum works very well.  I believe you need "Control" access to adjust quorum and crash a node.  See SYS$MANAGER:AMDS$DRIVER_ACCESS.DAT for the configuration.  You'll need to restart AMDS to load a configuration change.&lt;BR /&gt;&lt;BR /&gt;If your cluster doesn't have quorum, you won't be able to adjust quorum from any node in the cluster, the trigger needs to come from outside the cluster.  &lt;BR /&gt;&lt;BR /&gt;Andy &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 20 Oct 2005 22:35:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/quorum-fix-in-decamds-works/m-p/3653831#M72006</guid>
      <dc:creator>Andy Bustamante</dc:creator>
      <dc:date>2005-10-20T22:35:42Z</dc:date>
    </item>
    <item>
      <title>Re: Quorum fix in DECamds works?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/quorum-fix-in-decamds-works/m-p/3653832#M72007</link>
      <description>Thanks Andy and Volker&lt;BR /&gt;&lt;BR /&gt;I tried the quorum fix in Availability manager from a OpenVMS node outside the cluster and it worked ok, after I set the access to W (write) in AMDS$DRIVER_ACCESS.DAT (something like *\password\W ).&lt;BR /&gt;&lt;BR /&gt;I'll try AMDS later on. &lt;BR /&gt;&lt;BR /&gt;By the way, am I right in that the Quorum fix can ONLY be one from a node outside the cluster?&lt;BR /&gt;&lt;BR /&gt;Greetings , Jan</description>
      <pubDate>Fri, 21 Oct 2005 02:27:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/quorum-fix-in-decamds-works/m-p/3653832#M72007</guid>
      <dc:creator>Jan van den Boogaard</dc:creator>
      <dc:date>2005-10-21T02:27:56Z</dc:date>
    </item>
    <item>
      <title>Re: Quorum fix in DECamds works?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/quorum-fix-in-decamds-works/m-p/3653833#M72008</link>
      <description>Jan,&lt;BR /&gt;&lt;BR /&gt;if the cluster has lost quorum and your AMDS/Availability Manager data analyzer node would be part of that cluster, it will also hang (waiting for quorum to be regained) and you can't use it...&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Fri, 21 Oct 2005 02:31:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/quorum-fix-in-decamds-works/m-p/3653833#M72008</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-10-21T02:31:13Z</dc:date>
    </item>
    <item>
      <title>Re: Quorum fix in DECamds works?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/quorum-fix-in-decamds-works/m-p/3653834#M72009</link>
      <description>Jan,&lt;BR /&gt;&lt;BR /&gt;&lt;QUOTE&gt;&lt;BR /&gt;AMDS$DRIVER_ACCESS.DAT (something like *\password\W ).&lt;BR /&gt;&lt;/QUOTE&gt;&lt;BR /&gt;&lt;BR /&gt;Please consider to make your AMDS security a little less generic by adding an ethernet or DECnet address (of each of your possible data analyzer nodes) instead of the wildcard '*'.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Fri, 21 Oct 2005 02:35:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/quorum-fix-in-decamds-works/m-p/3653834#M72009</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-10-21T02:35:50Z</dc:date>
    </item>
  </channel>
</rss>

