Rarp - Bay Networks 5393 Hardware Installation Manual

When the Remote Annex receives a
and ip set, it sets the respective parameters: subnet_mask,
load_dump_gateway, and inet_addr. The Vendor Magic Cookie
must be set to auto. This indicates that bootpd should respond to the
client (Remote Annex 5393/PRI in this case) with whatever format
the client requests; the Remote Annex 5393/PRI (client) always makes
requests in the decimal dot notation format (e.g., 99.130.83.99).
The bootpd adds the address of the host on which it is running as the
Server Address in the bootp response message. The ROMs use the
Server Address as the preferred load host and store it in the
pref_load_addr parameter.
The bootpd must be running on the Remote Annex's preferred
load host.

RARP

If the Remote Annex does not receive a successful BOOTP response,
it uses RARP to get the boot information. For a successful RARP
retrieval, TCP/IP must be running on a host that is on the same
network as the Remote Annex, and the host's ARP table must be
initialized with the Remote Annex's Internet and Ethernet addresses
(see the arp man page, arp –s
The only boot information that RARP provides is the Remote Annex's
Internet address. The ROMs save this information in the inet_addr
parameter. The ROMs use default information for the subnet mask
and preferred load host. This means the ROMs will broadcast their
requests.
Remote Annex 5393/PRI Hardware Installation Guide
Chapter 2 Installing the Remote Annex 5393/PRI
response with the sm, gw,
BOOTP
.
)
2-23