AMDS won't start on a VAX V7.3

[Zia_Ahmad]

I am having problems with one of the nodes in a four node VAXcluster {Sigh}
A set verify and invocation yields ...
.....
NOTE that this works on the other nodes in the Cluster.

$ !
$ RUN AMDS$SYSTEM:AMDS$RMCP

Copyright (c) 1995 Digital Equipment 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-E-RMUNSUCCESS, Data Provider startup unsuccessful
%SYSTEM-F-DEVOFFLINE, device is not in configuration or not available

[Arch_Muthiah]

Zia,

As per HP doc, AMDS does not recognize some LAN adapters. When AMDS starts, if it does not recognize the LAN adapter in your system, you will receive "%SYSTEM-F-DEVOFFLINE, device is not in configuration or not available"

You can try this using this commands...
@SYS$STARTUP:AMDS$STARTUP START and
@SYS$STARTUP:AMDS$STARTUP STOP

So please check your name of LAN adaptor and make sure it has been assigned to the logical name AMDS$DEVICE in the AMDS$SYSTEM:AMDS$LOGICALS.COM file.

Edith this file and make sure you have correct value assigned for few of logicals, ex:
AMDS$DEVICE should be assigned the correct lan_adaptor.
It can be EIA0, EIBO, EWA0 or whatever you have, depends on you VAX OpenVMS Version

Please go thru this link under "2.2 Logical LAN Support"

And other logical is MDS$COMM_READS, this controls the number of requests for data (read operations) queued to the data link, HP recommends this be 2 or more.


Archunan

[Zia_Ahmad]

I had tried this before.
Here's the anamoly that I notice in the cluster....
Amds$device points to fxb0 [on all the other nodes in the cluster]. When I look at ncp all the lines are mfa-1[fddi]
except the node [i am having problems] which
is mfa-0
I tried defining fxa0 as the amds$device without any success.
the amds$read* is at 15

[Arch_Muthiah]

Zia,

Yes, it is definitely because of this LAN device problem.

can you go thru this link under "2.2 Logical LAN Support", it tells about LAN device failover.

http://h71000.www7.hp.com/openvms/products/availman/5929rel_notes_v73-2a.txt

btw, have you tried this cmd
@SYS$STARTUP:AMDS$STARTUP START,
was it successfull? or you got the same error?

Archunan

[Volker Halle]

Zia,

welcome to the ITRC OpenVMS forum.

The easiest way to check, which LAN devices are available in your OpenVMS system is via SDA:

$ ANAL/SYS
SDA> SHOW LAN

This will give you a list of all LAN devices and the protocols (Clients) running on those devices. AMDS will show up as ... 802E 08-00-2B-80-48 ...

Please check the value of the logical AMDS$DEVICE in the running system, after you've tried to start DECamds, to make sure it's correctly defined. FXA0 (DEMFA) is in the list of devices accepted by AMDS (see AMDS$LOGICALS.COM)

I seem to vaguely remember a problem with multiple AMDS$LOGICALS.COM files in different directories...


Archunan,

Logical LAN support (LLx devices) is not available on OpenVMS VAX, so no need to worry about it.

Volker.

[Ian Miller.]

you are correct in noticing mfa-1 is fxb0 and mfa-0 is fxa0. This suggests a hardware or configuration difference with this node. AMDS$DEVICE should be defined as fxa0 (note no : used in the device name).

Volker has given the command already to determine what protcols are running on which lan interfaces. Can you report the results.

[Zia_Ahmad]

On the working node:
-- FXB Unit Summary 5-DEC-2005 12:23:17 --

UCB UCB Addr Fmt Value Client State
--- -------- --- ----- ------ -----------
FXB0 D7BE5DC0
FXB3 D7C81A80 Eth 60-04 LAT 0015 Strtn,Uniq,Strtd
FXB4 D82A5240 Eth 60-03 DECNET 0017 Strtn,Len,Uniq,Strtd
FXB384 D7C86000 802E 08-00-2B-80-48 AMDS 0015 Strtn,Uniq,Strtd

Press RETURN for more.
SDA> spa
_SYSTEM> show log amds$device
"AMDS$DEVICE" = "FXB0" (LNM$SYSTEM_TABLE)_SYSTEM>
NCP>show known line

Known Line Volatile Summary as of 5-DEC-2005 12:25:28

Line State

MFA-1 on

On the NON-WORKING node:
AN Data Structures
-------------------
LSB address = D7BE0C80
Device state = 4013 Inited,Run,Timer

-- FXA Unit Summary 5-DEC-2005 12:27:02 --

UCB UCB Addr Fmt Value Client State
--- -------- --- ----- ------ -----------
FXA0 D7BE0980
FXA3 D8266C80 Eth 60-03 DECNET 0017 Strtn,Len,Uniq,Strtd
FXA5 D8267440 Eth 08-00 IP 0015 Strtn,Uniq,Strtd
FXA7 D82687C0 Eth 08-06 ARP 0015 Strtn,Uniq,Strtd

Press RETURN for more.
SDA> spa

_SYSTEM> mcr ncp show known line

Known Line Volatile Summary as of 5-DEC-2005 12:27:48

Line State

MFA-0 on
_SYSTEM> !*** and here's something strange **
show log amds$device
"AMDS$DEVICE" = "FXA0" (LNM$SYSTEM_TABLE)

@sys$startup:amds$startup start

This procedure has given up trying to start/stop a port
to the datalink. Please ensure your datalink device is
in working order.
%AMDS-E-RMUNSUCCESS, Data Provider startup unsuccessful
%SYSTEM-F-DEVOFFLINE, device is not in configuration or not available

show log *amds$device*
"AMDS$DEVICE" = "FXB0" <----- ??
in the file amds$logicals amds$device is defined as FXA0

A confused soul :)

[Arch_Muthiah]

Zia,

Volker post says...
< I seem to vaguely remember a problem with < multiple AMDS$LOGICALS.COM files in
< different directories...

Make sure you don't have multiple AMDS$LOGICALS.COM files.... Also, before excuting @sys$startup:amds$startup start, try run @AMDS$LOGICALS.COM procedure.

Archunan

[Arch_Muthiah]

Zia,

have looked into sys$startup:amds$startup ?

Archunan

[Zia_Ahmad]

Found the problem {Duh} amd$system:amds$logicals kept changing amds$device to fxa0! This file is does not equate to Sys$startup:amds$logicals.com !

Thanks for all the suggestions and help.
Happy Holidays - Zia

[Ian Miller.]

previous versions of AMDS had files in different place to current. This may explain.

[Jan van den Ende]

Zia,

to thank those who helped you:

http://forums1.itrc.hp.com/service/forums/helptips.do?#33

Proost.

Have one on me.

jpe