<?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: Availability Manager v2.4 Data Collector on VAX in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/availability-manager-v2-4-data-collector-on-vax/m-p/3445149#M65938</link>
    <description>Art,&lt;BR /&gt;&lt;BR /&gt;you can check, whether RMDRIVER is sending/receiving any packets via the LAN:&lt;BR /&gt;&lt;BR /&gt;UCB     UCB Addr  Fmt   Value           Client     State&lt;BR /&gt;---     --------  ---   -----           ------  -----------&lt;BR /&gt;ESA0    81C51B00&lt;BR /&gt;...&lt;BR /&gt;ESA2    81F44E80  802E  08-00-2B-80-48          0017 Strtn,Len,Uniq,Strtd&lt;BR /&gt;...&lt;BR /&gt;&lt;BR /&gt;SDA&amp;gt; SHOW LAN/DEV=ESA2/COUNT&lt;BR /&gt;&lt;BR /&gt;(08-00-2B-80-48 is the Protocol ID for AMDS).&lt;BR /&gt;&lt;BR /&gt;Does AMDS$GROUP_NAME match between the VAX and the GUI on the PC ?&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
    <pubDate>Thu, 16 Dec 2004 13:41:52 GMT</pubDate>
    <dc:creator>Volker Halle</dc:creator>
    <dc:date>2004-12-16T13:41:52Z</dc:date>
    <item>
      <title>Availability Manager v2.4 Data Collector on VAX</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/availability-manager-v2-4-data-collector-on-vax/m-p/3445147#M65936</link>
      <description>Testing what AM can do for our environment.  I installed Data Collector on one Alpha, and the Analyzer on my Win2K pc.  Alpha is discovered and I can look at various things.  Good stuff...(I have questions about event notifications as well, but not right now).  I then tried to install the collector (HP-VMS-AVAIL_MAN_COL-V0204--1.PCSI-DCX_VAXEXE;1) on a test VAX and get this when starting:&lt;BR /&gt;&lt;BR /&gt;$ @AMDS$STARTUP.COM start&lt;BR /&gt;&lt;BR /&gt;%AMDS-I-EXLOGFILE, Executing AMDS$AM_AMDS_SYSTEM:AMDS$LOGICALS.COM&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt; Copyright © 2003 HP Computer Corporation. All rights reserved. &lt;BR /&gt;%AMDS-I-RMSTART, starting Data Provider processing for this node&lt;BR /&gt;%AMDS-I-LOADSECDB, loading security database&lt;BR /&gt;&lt;BR /&gt; This procedure has given up trying to start/stop a port&lt;BR /&gt; to the datalink.  Please ensure your datalink device is&lt;BR /&gt; in working order.&lt;BR /&gt;%AMDS-S-RMSUCCESS, Data Provider startup successful&lt;BR /&gt;&lt;BR /&gt;Went into AMDS$LOGICALS.COM and "hardcoded" (as suggested in the command procedure):&lt;BR /&gt;&lt;BR /&gt;$ AMDS$DEF AMDS$DEVICE "EZA0"&lt;BR /&gt;&lt;BR /&gt;AM then "seems" to start (no error messages) but the node doesn't show up in AM Analyzer.&lt;BR /&gt;&lt;BR /&gt;I believe there was an older version of DECamds on this system previously and is possibly interfering with this new AM install.&lt;BR /&gt;&lt;BR /&gt;Any suggestions?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance,&lt;BR /&gt;Ar</description>
      <pubDate>Thu, 16 Dec 2004 11:37:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/availability-manager-v2-4-data-collector-on-vax/m-p/3445147#M65936</guid>
      <dc:creator>Art Wiens</dc:creator>
      <dc:date>2004-12-16T11:37:38Z</dc:date>
    </item>
    <item>
      <title>Re: Availability Manager v2.4 Data Collector on VAX</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/availability-manager-v2-4-data-collector-on-vax/m-p/3445148#M65937</link>
      <description>VAX/VMS v6.2 on a VAXstation 4000/96</description>
      <pubDate>Thu, 16 Dec 2004 11:46:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/availability-manager-v2-4-data-collector-on-vax/m-p/3445148#M65937</guid>
      <dc:creator>Art Wiens</dc:creator>
      <dc:date>2004-12-16T11:46:42Z</dc:date>
    </item>
    <item>
      <title>Re: Availability Manager v2.4 Data Collector on VAX</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/availability-manager-v2-4-data-collector-on-vax/m-p/3445149#M65938</link>
      <description>Art,&lt;BR /&gt;&lt;BR /&gt;you can check, whether RMDRIVER is sending/receiving any packets via the LAN:&lt;BR /&gt;&lt;BR /&gt;UCB     UCB Addr  Fmt   Value           Client     State&lt;BR /&gt;---     --------  ---   -----           ------  -----------&lt;BR /&gt;ESA0    81C51B00&lt;BR /&gt;...&lt;BR /&gt;ESA2    81F44E80  802E  08-00-2B-80-48          0017 Strtn,Len,Uniq,Strtd&lt;BR /&gt;...&lt;BR /&gt;&lt;BR /&gt;SDA&amp;gt; SHOW LAN/DEV=ESA2/COUNT&lt;BR /&gt;&lt;BR /&gt;(08-00-2B-80-48 is the Protocol ID for AMDS).&lt;BR /&gt;&lt;BR /&gt;Does AMDS$GROUP_NAME match between the VAX and the GUI on the PC ?&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Thu, 16 Dec 2004 13:41:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/availability-manager-v2-4-data-collector-on-vax/m-p/3445149#M65938</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2004-12-16T13:41:52Z</dc:date>
    </item>
    <item>
      <title>Re: Availability Manager v2.4 Data Collector on VAX</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/availability-manager-v2-4-data-collector-on-vax/m-p/3445150#M65939</link>
      <description>Volker:&lt;BR /&gt;&lt;BR /&gt;The device is created:&lt;BR /&gt;&lt;BR /&gt;EZA13   87DA0A00  802E  08-00-2B-80-48          0017 Strtn,Len,Uniq,Strtd&lt;BR /&gt;&lt;BR /&gt;And you may be on to something with the counts:&lt;BR /&gt;&lt;BR /&gt;SDA&amp;gt; show lan/count/device=eza13 &lt;BR /&gt;&lt;BR /&gt;         -- EZA13 80-48 Counters Information 16-DEC-2004 13:37:27 --&lt;BR /&gt;&lt;BR /&gt;Last receive                    None    Last transmit        16-DEC 13:37:08&lt;BR /&gt;Octets received                    0    Octets sent                    61752&lt;BR /&gt;PDUs received                      0    PDUs sent                        332&lt;BR /&gt;Mcast octets received              0    Mcast octets sent              61752&lt;BR /&gt;Mcast PDUs received                0    Mcast PDUs sent                  332&lt;BR /&gt;Unavail user buffer                0    Last start attempt              None&lt;BR /&gt;Last start done      16-DEC 10:49:08    Last start failed               None&lt;BR /&gt;&lt;BR /&gt;That may be a mess to look at...basically shows nothing received, but multicasts are being sent.&lt;BR /&gt;&lt;BR /&gt;I didn't change any passwords or group names...the Alpha was discovered right after I brought it up, the VAX not.</description>
      <pubDate>Thu, 16 Dec 2004 14:50:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/availability-manager-v2-4-data-collector-on-vax/m-p/3445150#M65939</guid>
      <dc:creator>Art Wiens</dc:creator>
      <dc:date>2004-12-16T14:50:23Z</dc:date>
    </item>
    <item>
      <title>Re: Availability Manager v2.4 Data Collector on VAX</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/availability-manager-v2-4-data-collector-on-vax/m-p/3445151#M65940</link>
      <description>Art,&lt;BR /&gt;&lt;BR /&gt;What version of VMS is on the Alpha?&lt;BR /&gt;I had a problem where I was unable to see info&lt;BR /&gt;from a VAX and I believe it may be a version&lt;BR /&gt;difference between the collector and the data&lt;BR /&gt;provider on the VAX.  I had the "latest" versions&lt;BR /&gt;running when I had the problem and never got it&lt;BR /&gt;to work and have not bothered trying to get it&lt;BR /&gt;working.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Dave&lt;BR /&gt;</description>
      <pubDate>Thu, 16 Dec 2004 23:25:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/availability-manager-v2-4-data-collector-on-vax/m-p/3445151#M65940</guid>
      <dc:creator>David B Sneddon</dc:creator>
      <dc:date>2004-12-16T23:25:45Z</dc:date>
    </item>
    <item>
      <title>Re: Availability Manager v2.4 Data Collector on VAX</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/availability-manager-v2-4-data-collector-on-vax/m-p/3445152#M65941</link>
      <description>Art,&lt;BR /&gt;&lt;BR /&gt;are the VAX, Alpha and PC on the same LAN segment ? When looking at our VAX AMDS LAN counters, it looks like it's sending one AMDS multicast msg every 30 seconds. It's also receiving 2 MC messages about every 30 seconds, as we have 2 other VMS systems running RMDRIVER on the same LAN.&lt;BR /&gt;&lt;BR /&gt;Once you would be running the AM GUI (and the system gets discovered), the system would also send/receive non-multicast AMDS messages.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Fri, 17 Dec 2004 01:49:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/availability-manager-v2-4-data-collector-on-vax/m-p/3445152#M65941</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2004-12-17T01:49:13Z</dc:date>
    </item>
    <item>
      <title>Re: Availability Manager v2.4 Data Collector on VAX</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/availability-manager-v2-4-data-collector-on-vax/m-p/3445153#M65942</link>
      <description>David:&lt;BR /&gt;&lt;BR /&gt;The Alpha 800 is VMS v7.3-2 (also testing our apps on that as well)&lt;BR /&gt;The VAXstation is VMS v6.2&lt;BR /&gt;The PC is Win2K SP4&lt;BR /&gt;&lt;BR /&gt;Volker:&lt;BR /&gt;&lt;BR /&gt;Of course! The test VAX is in our datacenter, my pc and the test Alpha are outside of the datacenter. Not sure why I didn't give you 10 points for that...reply and I'll give you one more ;-)&lt;BR /&gt;&lt;BR /&gt;I'll see what the Network boys can do for me.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Art</description>
      <pubDate>Fri, 17 Dec 2004 09:34:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/availability-manager-v2-4-data-collector-on-vax/m-p/3445153#M65942</guid>
      <dc:creator>Art Wiens</dc:creator>
      <dc:date>2004-12-17T09:34:43Z</dc:date>
    </item>
  </channel>
</rss>

