
Troubleshooting Network Boot Problems
114084 Rev. A A-13
3.
Compare the inconsistency in the bootptab file to the sample bootptab file
in Chapter 3 (refer to Figure 3-1) and correct the error.
4. If you cannot find an inconsistency, boot the router and view the bootpd
debugger messages to determine the cause of the error.
The sample messages in T
able A-1 show the sequence of messages when a
BOOTP exchange is successful.
Verifying the BOOTP Server Setup
Refer to these instructions if the BOOTP server is receiving BOOTP requests but
failing to respond, or failing to forward the kernel, configuration, application, or
string files.
Table A-1. BOOTP Messages
Message Explanation
hostname:/etc> request from IP addr
192.16.24.12
The UNIX hostname, the path (
/etc
) of the
bootptab
file, and the IP address of the
AN.
found 192.16.24.12 AN.Boston The IP address (192.16.24.12) mapped to
the hostname, AN.Boston, in the
bootptab
file.
bootfile2
/$HOME/.builder_dir/rel812/an
krnl_an.exe
The pathname of the kernel file, as
specified in the
bootptab
file.
couldn't access
/$HOME/.builder_dir/rel812/an
krnl_an.exe.AN.Boston
Disregard this message. The BOOTP
server tries to access the host both by its
name and by its 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.
vendor magic field is 99.130.83.99 Disregard this message.
sending RFC1048-style reply The BOOTP server is sending a BOOTP
response in compliance with RFC 1048.
Kommentare zu diesen Handbüchern