Boot failure on V6.2-1H2

The order DECnet and TCP/IP services start is important. DECnet needs to start first. If TCP/IP (UCX) gets ahead of it, DECnet can't configure the NIC properly and fails to start.

Try this:

- As Volker suggested, disable the DECnet (STARTNET) and TCP/IP (UCX$STARTUP) start ups in SYSTARTUP_VMS.COM. Comment out commands similar to these:

< class='quote' style='width:400px;white-space:nowrap;overflow:auto'><code style='white-space:nowrap'>$ IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" -
THEN @SYS$MANAGER:STARTNET

$ @SYS$MANAGER:UCX$STARTUP.COM<br><br><br></code>

- Reboot VMS.

- Run NETCONFIG.COM and reset your DECnet parameters.

- Enable DECnet start up in SYSTARTUP_VMS.COM (STARTNET).

- Reboot. This ought to fix DECnet and LAT.

- Run UCX$CONFIG.COM and reset your TCP/IP configuration.

- Enable TCP/IP in SYSTARTUP_VMS.COM (UCX$STARTUP).

- Reboot. This should fix TCP/IP.<hr>

The main problem is that EWA0 is not recognized by VMS.

SDA&gt; CLUE CONFIG shows:
< class='quote' style='width:400px;white-space:nowrap;overflow:auto'><code style='white-space:nowrap'>Adapter Configuration:

---

TR Adapter Name (Address) Hose Bus Node Device Name HW-Id/SW
--

---

----

---

----

---

---

1 KA0D02 (80DC9500) 0 BUSLESS_SYS
2 PCI (80DC9700) 0 PCI






PKA: 6 NCR53C810A 00051000
7 SATURN 04848086



11 DIGITAL_PCI_VEND 00191011




Press RETURN for more.
<br><br><br></code>

I tried installing patch ALPCPU0907_062 according to this thread

forums13.itrc.hp.com/service/forums/ques...3475&threadId=942384

but the interface is still not recognized.

What is the best way to resolve this issue?

Thanks.

Kinsa.<hr>

Kinsa,

the ITRC thread mentioned contains a lot of information regarding DE500 support on OpenVMS Alpha V6.2*

Did you also install ALPLAN05_062 ?
What's the link date of SYS$LOADABLE_IMAGES:SYS$EWDRIVER_DE500BA.EXE ? (Use $ ANAL/IMA/INT ...)

Volker.

Volker,

I created a fresh install of V6.2-1H3, with ALPLAN05_062 and ALPCPU0907_062 patch installed.

< class='quote' style='width:400px;white-space:nowrap;overflow:auto'><code style='white-space:nowrap'> Image Identification Information

image name: "SYS$DE500BADRIVER"
image file identification: "X-3"
image file build identification: "X61Q-SSB-OA00"
link date/time: 4-MAR-1998 17:03:17.42
linker identification: "A11-12"<br><br><br></code>

I also tried installing patch ALPLAN06_062,

< class='quote' style='width:400px;white-space:nowrap;overflow:auto'><code style='white-space:nowrap'> Image Identification Information
image name: "SYS$DE500BADRIVER"
image file identification: "X-3"
image file build identification: "X61Q-SSB-OH00"
link date/time: 27-SEP-2000 22:52:06.68
linker identification: "A11-12"<br><br><br></code>

and the result is still the same.

Kinsa.

Kinsa,

the LAN interface in FreeAXP .271 presents itself as a

DE500-BA - PCI-ID 00191011 (NDT$_DC21143)

The Hardware Version is reported (SDA&gt; SHOW LAN/FULL under V7.3-2) as 02000041 ( TU_C_DC21143_PD ).

According to the [LAN]EWDRIVER_DE500BA sources, support for DC21143_PD was added in OCT-1998.

There seem to exist different variants of the DE500-BA, which can only be detected in the CFRV (Configuration Revision Register) and 0041 may just be 'too new' for the older VMS versions.

The OpenVMS FAQ says:

< class='quote'>
14.23 Which DE500 variant works with which OpenVMS version?

DE500-BA
auto-detection, auto-negotiation,
OpenVMS V6.2-1H3 and CLUSIO, ALPBOOT, ALPLAN and ALPCPU ECOs, or V7.1-1H1 or later and ECO.
Device hardware id 02000030 (check connector, vs DE500-FA) (other values on old Alpha SRM firmware)


I booted OpenVMS V6.2-1H3 (no patches installed) and EWA0 is also not being configured ! It works fine with V7.3-2 though.

This makes me believe, that the LAN adapter choosen to be configured in FreeAXP, may not be supported on the 'older' OpenVMS versions.

Also note that the real AlphaServer 400 only supports a DE500-AA with OpenVMS V6.2-1H3 + ALPBOOT07_062 and ALPLAN04_062 according to the HP supported options list. No support for DE500-BA listed !

< class='quote'>
Problems addressed in the ALPLAN05_062 kit:

o Add support for the DE500-BA adapter and the Gigabit Ethernet
adapter.



PersonalAlpha presents an ESA0 (LANCE) LAN interface (HW version 00000000) and the Stromasys CHARON-AXP emulators by default present a DE435 (HW version 02000020).

Volker.<hr>

I have installed all CLUSIO, ALPBOOT, ALPLAN, and ALPCPU kits. Interface EWA0 was recognized but I got the following error when trying to start TCPIP:

< class='quote' style='width:400px;white-space:nowrap;overflow:auto'><code style='white-space:nowrap'>%%%%%%%%%%% OPCOM 23-APR-2010 16:33:00.05 %%%%%%%%%%%
Message from user INTERnet on TEST
INTERnet Loaded

%RUN-S-PROC_ID, identification of created process is 0000010E
The Internet driver and ACP were successfully loaded.
%UCX-I-SETLOCAL, Setting domain and/or local host
%UCX-I-SETPROTP, Setting protocol parameters
%UCX-I-STARTCOMM, Starting communication
%%%%%%%%%%% OPCOM 23-APR-2010 16:33:00.46 %%%%%%%%%%%
Message from user INTERnet on TEST
INTERnet Started

%UCX-I-DEFINTE, Defining interfaces
%UCX-E-INVINTER, Error defining interface: WE0
-UCX-I-ACPQIO, Failure on Internet ACP QIO
-SYSTEM-F-DEVOFFLINE, device is not in configuration or not available
-SYSTEM-F-DEVOFFLINE, device is not in configuration or not available
%UCX-E-INVINTERNAM, Invalid interface name
-UCX-I-DRIVERQIO, Failure on Internet driver QIO
-UCX-E-INVNETMASK, Invalid network mask
%UCX-E-DELINTER, Error deleting interface: WE0
-UCX-I-ACPQIO, Failure on Internet ACP QIO
-UCX-E-INVINTERNAM, Invalid interface name
%UCX-I-ENABSERV, Enabling services
%UCX-E-CONFIGERROR, Error processing CONFIGURATION request
-RMS-E-RNF, record not found
%UCX-I-STARTNAME, Starting name_service
%UCX-I-LOADSERV, Loading UCX Server proxy information
%UCX-I-SERVLOADED, UCX Aux. Server loaded with 0 proxy records
-UCX-I-SERVSKIP, Skipped 0 communication proxy records
-UCX-I-SERVTOTAL, Total of 0 proxy records read
Startup request completed.
<br><br><br></code>