Table of Contents
Advertisement
3.
4.
Table B-1
exchange is successful.
Table B-1.
Message
hostname:/etc> request from IP
addr 192.16.24.12
found 192.16.24.12 AN.Boston
bootfile2 /$HOME/.builder_dir/
rel1200/an krnl_an.exe
couldn't access /$HOME/
.builder_dir/rel1200/an
krnl_an.exe.AN.Boston
vendor magic field is
99.130.83.99
sending RFC1048-style reply
308614-14.20 Rev 00
Compare the bootptab file with the sample bootptab file in Chapter 2
(see Figure 2-1 on page 2-8) and correct any inconsistency.
If you cannot find an inconsistency, boot the router and view the bootpd
debugger messages to determine the cause of the error.
provides an example of the sequence of messages when a BootP
BootP Messages
Troubleshooting Network Boot Problems
Explanation
The UNIX host name, the path ( /etc ) of the
bootptab file, and the IP address of the
AN
The IP address (192.16.24.12) mapped to
the host name, AN.Boston, in the bootptab
file
The path name of the kernel file, as
specified in the bootptab file
Disregard this message. The BootP server
tries to access the host by both its name
and IP address. The "couldn't access"
message means that the server tried to
access a host named AN.Boston, but failed
because the AN is not named. The attempt
to access the AN by its IP address
succeeds, as you can infer from the last
message.
Disregard this message.
The BootP server is sending a BootP
response in compliance with RFC 1048.
B-13
Advertisement
Table of Contents
