Bay Networks Remote Annex 4000, Hardware Installation Manual

Page: 68 / 162

Remote Annex 4000 Hardware Installation Guide
Chapter 2 Installing the Remote Annex 4000
2-30
When the Remote Annex 4000 receives a
BOOTP
response with the sm,
gw, 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 4000 in this case) with whatever format the
client requests; the Remote Annex 4000 (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 4000’s
preferred load host.
RARP
If the Remote Annex 4000 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 4000, and the host’s ARP table must
be initialized with the Remote Annex 4000’s Internet and Ethernet
addresses (see the arp man page, arp –s
)
.
The only boot information that RARP provides is the Remote Annex
4000’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.
The host serving the Remote Annex 4000 its boot information must
be running on the same network as the Remote Annex 4000 because
the Remote Annex 4000 only broadcasts BOOTP and RARP queries.