Troubleshooting Network Boot Problems
3.Compare the bootptab file with the sample bootptab file in Chapter 2 (see Figure
4.If you cannot find an inconsistency, boot the router and view the bootpd debugger messages to determine the cause of the error.
Table
Table | BootP Messages |
|
|
|
|
Message |
| Explanation |
|
| |
hostname:/etc> request from IP | The UNIX host name, the path (/etc) of the | |
addr 192.16.24.12 | 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/ | The path name of the kernel file, as | |
rel1200/an krnl_an.exe | specified in the bootptab file | |
|
| |
couldn't access /$HOME/ | Disregard this message. The BootP server | |
.builder_dir/rel1200/an | tries to access the host by both its name | |
krnl_an.exe.AN.Boston | 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 | Disregard this message. | |
99.130.83.99 |
|
|
|
| |
sending | The BootP server is sending a BootP | |
|
| response in compliance with RFC 1048. |
|
|
|