Load Server Host Not Responding - Bay Networks 5393 Hardware Installation Manual

Chapter 4 Troubleshooting Procedures
4-12 Remote Annex 5393/PRI Hardware Installation Guide
The IP encapsulation type. Many systems have hardware
Ethernet interfaces that are IEEE 802.3 compliant, but very
few actually do 802.3 IP packet encapsulation. Use the
default, Ethernet, unless you know absolutely that your
LAN does 802.2/802.3 IP packet encapsulation.
You can use the defaults for the name of the image file containing the
Remote Annex's software and the address of the preferred load server
host. If the value for the image name is incorrect, the Remote Annex
cannot boot. Correct the name using the image command. If the
address for the preferred load server host is incorrect, the boot takes
longer, since the Remote Annex has to broadcast for a host. Correct
the load host's address using the addr command.
Confirm that the Remote Annex's boot parameters are correct by
using the appropriate ROM Monitor commands. Modify any boot
parameters that are incorrect or missing. Boot the Remote Annex
either by entering the boot command at the service port terminal, or
by resetting the module.

Load Server Host Not Responding

The Remote Annex can boot from one of the following hosts acting
as a load server host:
A UNIX host on the local area network.
Another Remote Annex.
Any host (UNIX or non-UNIX) using tftp.
A Windows NT host.
The following subsections discuss troubleshooting for some of these
load server hosts.