Bay Networks Remote Annex 4000, Hardware Installation Manual, Page: 66 / 162

Remote Annex 4000 Hardware Installation Guide
Chapter 2 Installing the Remote Annex 4000
2-28
You can rename Remote Annex operational images, but they must
remain in MOM$LOAD. If you do change the operational image name
from OPER_46_ENET.SYS to some other name, the new file name plus
the extension can be no longer than 16 characters total. This is due to
a MOP restriction of 16 characters in passing the load file name field.
Auto-initializing the ROMs
The Remote Annex 4000 is distributed without an IP address or
preferred load host (UNIX/IP, IPX, or MOP) defined in ROM. When
the device is booted, the Remote Annex 4000 attempts to auto-
initialize its ROMs using BOOTP (bootstrap protocol) and RARP
(Reverse Address Resolution Protocol).
The Remote Annex 4000 supports the BOOTP and RARP protocols.
Use these protocols to automatically obtain boot information from a
UNIX host without requiring any manual set-up on the Remote
Annex 4000.
❑
BOOTP allows a diskless client to determine its IP address,
the IP address of the server, and the name of the file to be
loaded into memory.
❑
RARP maps a hardware address into an IP address.
The ROMs invoke this system of acquiring boot information when a
boot is initiated and the Remote Annex 4000 is not initialized. Under
this condition, the Remote Annex 4000 first tries to get boot
information via BOOTP or RARP.
If BOOTP and RARP fail, the Remote Annex 4000 attempts to load an
image by transmitting an IPX advertisement request for service and
a MOP multicast boot request.