
Configuring BayStack Remote Access
2-6
117341-B Rev. 00
The sample bootptab file shown in Figure 2-1 enables two ANs (named
AN.Boston and AN.Chicago) to boot over the network. Use the basic format
shown in Figure 2-1 to set up your own bootptab file.
Verifying Consistent BootP Service
You may want to configure a second workstation as a BootP server for backup
purposes. If you do so, make sure that the two bootptab files are identical. Also,
make sure that the kernel, application, and string files are from the same BayRS
version.
Table 2-2. BootPD Tags for a Kernel File Name
Tag
Required
or Optional Value Example
hd Required Home directory -- the directory on
the workstation containing the
kernel files. By default, the Image
Builder writes its files to the
directory specified in the example.
The
rel< number >
directory
contains the current BayRS
release. If you change the default
or move the files to another
directory, specify that directory.
hd=/$HOME/.builder_dir/
rel120/an
bf Required Boot file -- the name of the kernel
file.
bf=krnl_an.exe
bs Required Boot size
-- the size of the kernel
file in 512-byte blocks. If you
specify
auto
as the size, the BootP
server calculates the size of the
file for each BootP request.
bs=auto
vm Required Vendor magic cookie selector
--
the BootP server should always
reply in a manner compliant with
RFC 1048. You must specify
rfc1048
for this tag in order for the
BayStack router to understand the
BootP responses it receives.
vm=rfc1048
Kommentare zu diesen Handbüchern