Availability Manager v2.4 Data Collector on VAX

[Art Wiens]

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:

$ @AMDS$STARTUP.COM start

%AMDS-I-EXLOGFILE, Executing AMDS$AM_AMDS_SYSTEM:AMDS$LOGICALS.COM


Copyright © 2003 HP Computer Corporation. All rights reserved.
%AMDS-I-RMSTART, starting Data Provider processing for this node
%AMDS-I-LOADSECDB, loading security database

This procedure has given up trying to start/stop a port
to the datalink. Please ensure your datalink device is
in working order.
%AMDS-S-RMSUCCESS, Data Provider startup successful

Went into AMDS$LOGICALS.COM and "hardcoded" (as suggested in the command procedure):

$ AMDS$DEF AMDS$DEVICE "EZA0"

AM then "seems" to start (no error messages) but the node doesn't show up in AM Analyzer.

I believe there was an older version of DECamds on this system previously and is possibly interfering with this new AM install.

Any suggestions?

Thanks in advance,
Ar

[Art Wiens]

VAX/VMS v6.2 on a VAXstation 4000/96

[Volker Halle]

Art,

you can check, whether RMDRIVER is sending/receiving any packets via the LAN:

UCB UCB Addr Fmt Value Client State
--- -------- --- ----- ------ -----------
ESA0 81C51B00
...
ESA2 81F44E80 802E 08-00-2B-80-48 0017 Strtn,Len,Uniq,Strtd
...

SDA> SHOW LAN/DEV=ESA2/COUNT

(08-00-2B-80-48 is the Protocol ID for AMDS).

Does AMDS$GROUP_NAME match between the VAX and the GUI on the PC ?

Volker.

[Art Wiens]

Volker:

The device is created:

EZA13 87DA0A00 802E 08-00-2B-80-48 0017 Strtn,Len,Uniq,Strtd

And you may be on to something with the counts:

SDA> show lan/count/device=eza13

-- EZA13 80-48 Counters Information 16-DEC-2004 13:37:27 --

Last receive None Last transmit 16-DEC 13:37:08
Octets received 0 Octets sent 61752
PDUs received 0 PDUs sent 332
Mcast octets received 0 Mcast octets sent 61752
Mcast PDUs received 0 Mcast PDUs sent 332
Unavail user buffer 0 Last start attempt None
Last start done 16-DEC 10:49:08 Last start failed None

That may be a mess to look at...basically shows nothing received, but multicasts are being sent.

I didn't change any passwords or group names...the Alpha was discovered right after I brought it up, the VAX not.

[David B Sneddon]

Art,

What version of VMS is on the Alpha?
I had a problem where I was unable to see info
from a VAX and I believe it may be a version
difference between the collector and the data
provider on the VAX. I had the "latest" versions
running when I had the problem and never got it
to work and have not bothered trying to get it
working.

Regards
Dave

[Volker Halle · Accepted solution]

Art,

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.

Once you would be running the AM GUI (and the system gets discovered), the system would also send/receive non-multicast AMDS messages.

Volker.

[Art Wiens]

David:

The Alpha 800 is VMS v7.3-2 (also testing our apps on that as well)
The VAXstation is VMS v6.2
The PC is Win2K SP4

Volker:

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 ;-)

I'll see what the Network boys can do for me.

Thanks,
Art