Avanti presents its first three network devices as EWA0, EWB0, and EWC0. A migrated OpenVMS system configured for different controllers may therefore need its DECnet and TCP/IP products reconfigured for EW devices.

The sequence below is retained historical service guidance for DECnet Phase IV and older UCX/TCP/IP Services installations. It has not been executed across the Avanti 5.1.0 guest matrix and is not a substitute for the configuration and startup instructions supplied with the exact OpenVMS, DECnet, and TCP/IP product versions. Back up SYSTARTUP_VMS.COM and the product configuration before changing them, and arrange a console recovery path.

1)Disable the DECnet (STARTNET.COM) and TCP/IP (UCX$STARTUP.COM) startups in SYSTARTUP_VMS.COM.  Comment out commands similar to these:

$ IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN @SYS$MANAGER:STARTNET

$ @SYS$MANAGER:UCX$STARTUP.COM

$ @SYS$MANAGER:TCPIP$STARTUP.COM

2)Reboot VMS.

3)Run NETCONFIG.COM and reset the DECnet parameters.

4)Enable DECnet startup in SYSTARTUP_VMS.COM (STARTNET.COM).

Note: Historical service guidance ran DECnet before TCP/IP and invoked both startup procedures directly from SYSTARTUP_VMS.COM. That order and the blanket prohibition on batch submission have not been revalidated as universal requirements. Preserve the supported startup mechanism for the installed product versions unless their documentation or a reproduced migration problem requires explicit serialization.

5)Reboot, then verify the configured DECnet and LAT devices and inspect their startup messages before proceeding.

6)Run UCX$CONFIG.COM or TCPIP$CONFIG.COM and reset the TCP/IP configuration.

7)Enable TCP/IP in SYSTARTUP_VMS.COM (UCX$STARTUP or TCPIP$STARTUP).

8)Reboot, then verify the configured TCP/IP interface, address, route, and required services. If validation fails, preserve the console and startup output and restore the saved configuration before trying a different release-matched procedure.