Nortel Networks 14.2 (see Figure2-1 on page 2-8) and correct any inconsistency.

Troubleshooting Network Boot Problems
308614-14.20 Rev 00 B-13
3. Compare the bootptab file with the sample bootptab file in Chapter 2
(see Figure2-1 on page 2-8) and correct any inconsistency.
4. If you cannot find an inconsistency, boot the router and view the bootpd
debugger messages to determine the cause of th e error.
Tabl e B-1 provides an example of the sequence of messages when a BootP
exchange is successful.
Table B-1. BootP Messages
Message Explanation
hostname:/etc> request from IP
addr 192.16.24.12
The UNIX host name, 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 host name, AN.Boston, in the
bootptab
file
bootfile2 /$HOME/.builder_dir/
rel1200/an krnl_an.exe
The path name of the kernel file, as
specified in the
bootptab file
couldn't access /$HOME/
.builder_dir/rel1200/an
krnl_an.exe.AN.Boston
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.
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.