Conference 7.286::fddi

443.0. "FDDI can prevent VMS install from Infoserver" by KYOA::WALKER (Clarke Walker, NJ CS, DTN:323-4040) Mon Jan 13 1992 10:08

       FDDI interface can prevent VMS installation from Infoserver

I just finished tracking down a problem installing VMS V5.5 on a VAX
6000 model 620 which needs to be shared with others because of its
impact.

This customer's VAX 6000 model 620 had the KFMSA DSSI controller,
DEMNA Ethernet controller, and DEMFA FDDI controller.  The load device
is an Infoserver 150.  I followed the installation instructions in the
"VMS V5.5 Upgrade and Installation Manual" and the "VMS Upgrade and
Installation Supplement: VAX 6000 Series" where appropriate (this
manual is out of date).

The backup of the VMS055.B saveset from the Infoserver to DSSI disk
went correctly (only takes a few minutes).  I then booted the DSSI disk
using:

	>>>BOOT /XMI:D /PORT:1 /DSSI:1 DI0

The STARTUP.INS file was invoked and the dialoque began.  The command
procedure prompted for the distribution device and I entered DAD1
(there is a typo in the manual, always use DAD1 when the Infoserver
is being used).  The procedure then prompted for the service name,
VMS055, and the work group number, 0.  The system would then hang.  No
error message or further text was printed.

After stepping through the installation procedure I discovered that
the ESS (LADCP) software was creating the DAD device on the FDDI
interface and NOT the Ethernet device.  There is nothing connected to
the customer's FDDI interface and thus the system hung.

Our only remedy is to remove the FDDI interface from the computer.

I assume this problem will occur for any VAX system having an FDDI
interface.  Also, if your Infoserver is accessible via FDDI then you
should not have any problems.

This problem has been reported to the Telephone Support Center in
Colorado and cross posted in the Infoserver and VMSNOTES note files.


Clarke Walker
NJ EIS/Consulting Services