<?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: Availabillity manager on a two node cluster problem in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327160#M63473</link>
    <description>What do you have on each node in amds$system:amds*console*.dat and amds$system:amds*driver*.dat ?&lt;BR /&gt;&lt;BR /&gt;On which network interface is started amds ?&lt;BR /&gt;&lt;BR /&gt;$ ana/sys&lt;BR /&gt;sh lan&lt;BR /&gt;do you see amds on a network device on each node ?</description>
    <pubDate>Fri, 09 Jul 2004 03:11:50 GMT</pubDate>
    <dc:creator>labadie_1</dc:creator>
    <dc:date>2004-07-09T03:11:50Z</dc:date>
    <item>
      <title>Availabillity manager on a two node cluster problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327159#M63472</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I have availabillity manager running on a two-node cluster with a common system disk, but only one node appears in my view window. &lt;BR /&gt;&lt;BR /&gt;Any ideas??&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Piet</description>
      <pubDate>Fri, 09 Jul 2004 03:06:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327159#M63472</guid>
      <dc:creator>Piet Timmers</dc:creator>
      <dc:date>2004-07-09T03:06:15Z</dc:date>
    </item>
    <item>
      <title>Re: Availabillity manager on a two node cluster problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327160#M63473</link>
      <description>What do you have on each node in amds$system:amds*console*.dat and amds$system:amds*driver*.dat ?&lt;BR /&gt;&lt;BR /&gt;On which network interface is started amds ?&lt;BR /&gt;&lt;BR /&gt;$ ana/sys&lt;BR /&gt;sh lan&lt;BR /&gt;do you see amds on a network device on each node ?</description>
      <pubDate>Fri, 09 Jul 2004 03:11:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327160#M63473</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2004-07-09T03:11:50Z</dc:date>
    </item>
    <item>
      <title>Re: Availabillity manager on a two node cluster problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327161#M63474</link>
      <description>On the node, device rma0 must exist or amds is not active (f$getd("rma0","exists").&lt;BR /&gt;&lt;BR /&gt;Or it might be your settings :&lt;BR /&gt;&lt;BR /&gt;Default files are in AMDS$SYSTEM. A node can be in 1 group only. The node is&lt;BR /&gt;setup in the logical AMDS$GROUP_NAME in the file AMDS$LOGICALS.COM. Default is&lt;BR /&gt;that all nodes are in 1 group.&lt;BR /&gt;&lt;BR /&gt;The client security key is in AMDS$CONSOLE_ACCESS.DAT.&lt;BR /&gt;The server security key is in AMDS$DRIVER_ACCESS.DAT&lt;BR /&gt;A match must occur to give access.&lt;BR /&gt;&lt;BR /&gt;It contains 3 fields : an address, a password and R|W.&lt;BR /&gt;E.g. 2.1\wimpass\W gives write access to node 2.1 giving password wimpass.&lt;BR /&gt;Wildcard addresses can be used.</description>
      <pubDate>Fri, 09 Jul 2004 03:15:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327161#M63474</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-07-09T03:15:38Z</dc:date>
    </item>
    <item>
      <title>Re: Availabillity manager on a two node cluster problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327162#M63475</link>
      <description>Labadie &amp;amp; Wim,&lt;BR /&gt;&lt;BR /&gt;All the configuration files for AMDS are in the common directories (I have checked this) so the settings are the same for both nodes.&lt;BR /&gt;&lt;BR /&gt;Using $ ana/sys&lt;BR /&gt;        show lan&lt;BR /&gt;&lt;BR /&gt;On node-1: &lt;BR /&gt;EIA16    81CCC1C0  802E  08-00-2B-80-48  AMDS    0017 STRTN,LEN,UNIQ,STRTD&lt;BR /&gt;&lt;BR /&gt;and on node-2:&lt;BR /&gt;EIA13    81CBD540  802E  08-00-2B-80-48  AMDS    0017 STRTN,LEN,UNIQ,STRTD&lt;BR /&gt;&lt;BR /&gt;On both nodes the device rma0: exists.&lt;BR /&gt;&lt;BR /&gt;Greetings,&lt;BR /&gt;&lt;BR /&gt;Piet</description>
      <pubDate>Fri, 09 Jul 2004 03:47:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327162#M63475</guid>
      <dc:creator>Piet Timmers</dc:creator>
      <dc:date>2004-07-09T03:47:52Z</dc:date>
    </item>
    <item>
      <title>Re: Availabillity manager on a two node cluster problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327163#M63476</link>
      <description>both node have the eia card on same network ?&lt;BR /&gt;&lt;BR /&gt;seen node with 2 network cards and amds started on the "bad" adapter.</description>
      <pubDate>Fri, 09 Jul 2004 03:49:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327163#M63476</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2004-07-09T03:49:34Z</dc:date>
    </item>
    <item>
      <title>Re: Availabillity manager on a two node cluster problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327164#M63477</link>
      <description>On my nodes, amds sits on all cards.&lt;BR /&gt;&lt;BR /&gt;Did you specify * in the access files ?&lt;BR /&gt;&lt;BR /&gt;How is the hello  interval set ? Maybe you have to wait 5 minutes.&lt;BR /&gt;&lt;BR /&gt;Do you use the gui on one of the cluster nodes ?&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Fri, 09 Jul 2004 04:11:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327164#M63477</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-07-09T04:11:07Z</dc:date>
    </item>
    <item>
      <title>Re: Availabillity manager on a two node cluster problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327165#M63478</link>
      <description>Wim,&lt;BR /&gt;&lt;BR /&gt;I have specified a * in the access files, I use the PC Availability manager program, and I am waiting for at over 3 hours now to see both nodes.&lt;BR /&gt;&lt;BR /&gt;Greetings,&lt;BR /&gt;&lt;BR /&gt;Piet</description>
      <pubDate>Fri, 09 Jul 2004 04:19:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327165#M63478</guid>
      <dc:creator>Piet Timmers</dc:creator>
      <dc:date>2004-07-09T04:19:38Z</dc:date>
    </item>
    <item>
      <title>Re: Availabillity manager on a two node cluster problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327166#M63479</link>
      <description>Oeps, I checked and they are on 1 card only.&lt;BR /&gt;&lt;BR /&gt;On node2 :&lt;BR /&gt;ana/sys&lt;BR /&gt;show lan/dev=eia13&lt;BR /&gt;&lt;BR /&gt;and check the counters. Is it working ?&lt;BR /&gt;&lt;BR /&gt;Try restarting :&lt;BR /&gt;@sys$startup:amds$startup stop&lt;BR /&gt;@sys$startup:amds$startup&lt;BR /&gt;&lt;BR /&gt;The eia device hasn't got the same number. Or the protocols are not started in the same way or something went wrong during startup (wild guess).&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Fri, 09 Jul 2004 04:38:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327166#M63479</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-07-09T04:38:16Z</dc:date>
    </item>
    <item>
      <title>Re: Availabillity manager on a two node cluster problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327167#M63480</link>
      <description>Wim,&lt;BR /&gt;&lt;BR /&gt;I see a few differences:&lt;BR /&gt;On the "working" node:&lt;BR /&gt;Last receive          9-JUL 11:42:57&lt;BR /&gt;MCA match enabled                 01&lt;BR /&gt;&lt;BR /&gt;on the "not working" node:&lt;BR /&gt;Last receive                    None&lt;BR /&gt;MCA match enabled                 00&lt;BR /&gt;&lt;BR /&gt;The last receive None is as expected in this situation, but what about "MCA match enabled"?&lt;BR /&gt;&lt;BR /&gt;A restart did not solve my problem.&lt;BR /&gt;&lt;BR /&gt;Greetings</description>
      <pubDate>Fri, 09 Jul 2004 04:50:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327167#M63480</guid>
      <dc:creator>Piet Timmers</dc:creator>
      <dc:date>2004-07-09T04:50:39Z</dc:date>
    </item>
    <item>
      <title>Re: Availabillity manager on a two node cluster problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327168#M63481</link>
      <description>Piet&lt;BR /&gt;&lt;BR /&gt;If the node has multiple network interfaces : check with show lan if AMDS is on the same EI* card as the other protocols. Maybe it is on the wrong card (use counters to checks).&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Fri, 09 Jul 2004 05:36:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327168#M63481</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-07-09T05:36:24Z</dc:date>
    </item>
    <item>
      <title>Re: Availabillity manager on a two node cluster problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327169#M63482</link>
      <description>Availability Manager uses a multicast protocol on the LAN. This is not an IP protocol and must be bridged, not routed. Could it be that the multicasts coming from the 2nd node aren't getting to the PC running Availability Manager through the LAN?</description>
      <pubDate>Mon, 12 Jul 2004 13:02:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327169#M63482</guid>
      <dc:creator>Keith Parris</dc:creator>
      <dc:date>2004-07-12T13:02:32Z</dc:date>
    </item>
    <item>
      <title>Re: Availabillity manager on a two node cluster problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327170#M63483</link>
      <description>Keith,&lt;BR /&gt;&lt;BR /&gt;Your answer is problably the correct one.&lt;BR /&gt;We use in our OpenVMS servers two netwerk devices, each on its on own sub-net.&lt;BR /&gt;When I trace AMDS using $ ana/sys, show lan&lt;BR /&gt;I see that the node I cannot reach with availabillity manager on my PC uses the netwerk interface on the other sub-net, separated by a router.&lt;BR /&gt;&lt;BR /&gt;Is there a way to force AMDS to use a specific netwerk interface?&lt;BR /&gt;&lt;BR /&gt;Greetings,&lt;BR /&gt;&lt;BR /&gt;Piet</description>
      <pubDate>Wed, 14 Jul 2004 01:38:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327170#M63483</guid>
      <dc:creator>Piet Timmers</dc:creator>
      <dc:date>2004-07-14T01:38:49Z</dc:date>
    </item>
    <item>
      <title>Re: Availabillity manager on a two node cluster problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327171#M63484</link>
      <description>Piet,&lt;BR /&gt;&lt;BR /&gt;In sys$startup:amds$def_device.com you can modify the line defining the amds$device.&lt;BR /&gt;&lt;BR /&gt;$ def/sys/exec amds$device "EIA0".&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Wed, 14 Jul 2004 01:44:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/availabillity-manager-on-a-two-node-cluster-problem/m-p/3327171#M63484</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-07-14T01:44:24Z</dc:date>
    </item>
  </channel>
</rss>

