Installation
Loading Server Software
Once the self-tests have completed, the communications server automatically
begins the boot sequence to load the software. Software is downline loaded to the
communications server from a VMS, ULTRIX, or MS–DOS™ load host using the
MOP or BOOTP protocol.
If a device is attached to the console port, status messages can be displayed while
the boot sequence is running. Status messages indicate the Ethernet address of
the communications server, the name of the load image it is looking for, and the
stage of the boot process it is in.
During the boot sequence the communications server searches for a load host.
The communications server tries both MOP and BOOTP protocols in a factory-
defined order. Once the communications server finds a load host, it records the
protocol and load host in its permanent database. Once a load host is found,
status messages indicate the address of the load host and the protocol used.
If a valid load host cannot be found, the communications server remains in the
boot sequence indefinitely, while continually searching for a load host. If this
occurs, it may be indicating that the communications server software has not
been properly installed on a load host. The boot sequence includes a wait period
after each pass through all the boot protocols.
Upon startup of the boot process, the Network OK LED blinks continuously
and the System OK LED remains lit indicating that communications server is
attempting to load the software. Port Activity LEDs six, seven, or eight light to
indicate which protocol is being tried by the communications server to downline
load the software. Port activity LED five lights to indicate that all attempts to
find a load host have failed and that the communications server will remain in a
wait state for a designated period of time before trying again (refer to Table 2–1).
Installation 2–9
