OpenVMS v8.2-1 IA64 and Availability Manager v2.5

[Andrew Rycroft1]

Hi,

I have installed Availability Manager v2.5 on my HP Integrity server with OpenVMS v8.2-1.

It starts up correctly with no errors.

When I start up the client on my PC, it picks up the Alpha system, but not the Integrity. Is there anywhere I can look to see if it is actually polling the Integrity and why the Integrity is not responding?

Thanks
Andrew

[Volker Halle]

Andrew,

first you can check, on which LAN device the AMDS protocol has been started:

$ ANAL/SYS
SDA> SHOW LAN

Look for 'AMDS' in the Client column.

If that device is not connected to your LAN, you will have to edit AMDS$LOGICALS.COM and define an appropriate LAN device for AMDS$DEVICE

Volker.

[Andrew Rycroft1]

Hi,

Yes, the AMDS protocol has been started:-

LAN Data Structures
-------------------

-- EWA Device Summary 10-MAR-2006 10:11:03 --

LSB address = 92780000
Device state = 00001103 RUN,INITED,RING_AVAIL,FP_CPUAFF

UCB UCB Addr Fmt Value Client State
--- -------- --- ----- ------ -----------
EWA0 89196040
EWA3 89601300 Eth 08-00 IP 0015 STRTN,UNIQ,STRTD
EWA4 89757840 Eth 08-06 ARP 0015 STRTN,UNIQ,STRTD
EWA5 89758300 Eth 86-DD IPV6 0015 STRTN,UNIQ,STRTD
EWA6 894A1700 Eth 00-00 0000
EWA7 897F6AC0 Eth 00-00 0000
EWA410 894C0CC0 Eth 00-00 0000
EWA1416 894C1900 802E 08-00-2B-80-48 AMDS 0017 STRTN,LEN,UNIQ,STRTD

Regards
Andrew

[Volker Halle]

Andrew,

and this LAN device (EWA0) is connected to the SAME LAN as your PC ? You can check the counters of the AMDS protocol device EWA1416 with SDA> SHOW LAN/COUNT/DEV=EWA1416

AMDS (SYS$RMDRIVER) sends multicast messages out on the LAN. The Availability Manager GUI listens to those multicast messages and - if it discovers a new system - starts sending AMDS messages to that system to obtain config information.

Are the systems in the same group (logical AMDS$GROUP_NAME) ?

Sometimes it takes a while for Avalability Manager to detect and configure a system, how long did you wait ?

Volker.

[Ian Miller.]

are there any operator messages on the Integrity system from RMDRIVER - sometimes these can indicate the problem e.g group or password mismatch etc.

[Andrew Rycroft1]

Hi,

Thank you for your responses thus far.

We enabled the operator messages, but there were none.

We looked at the counters with

SDA> SHOW
LAN/COUNT/DEV=EWA1416

The server is connected to the same LAN.

The counters of the device showed plety sent but nothing received.

Regards
Andrew

[Volker Halle]

Andrew,

the AMDS LAN device 'Mcast PDUs received' counter should increase. The node should see the AMDS multicast messages sent by the Alpha. If it doesn't, there is probably some problem with multicast messages on your network.

Volker.

[Petr Spisek]

Hi,
did you managed your password in the new AMDS$CONSOLE(DRIVER)_ACCESS.DAT ?

Petr

[Andrew Rycroft1]

Hi,

I have now been informed that the HP Integrity server is on a VLAN. The PC Clients and Alpha are on a standard network.

The network people say that a multicast will not work from the VLAN to the standard network.

My understanding is that a VLAN is just a virtual network and should transport any traffic.

I would appreciate any input in clarfying this.

Thanks
Andrew

[Volker Halle · Accepted solution]

Andrew,

this is a specific network configuration issue at your site.

If your VLAN is configured in such a way, that multicast-messages may not reach your 'standard network', you can't use AMDS communications between your Itanium Server and your PC.

AMDS/Availability Manager is a layer 2 (datalink layer) protocol and requires the participating systems to be on the same logical LAN. AMDS cannot be routed, although this is planned for a future release.

Volker.