
Troubleshooting Network Boot Problems
117341-A Rev. A B-3
Router Fails to Netboot
If the BayStack router fails to receive the configuration file or boot image using a
netboot option, first do the following:
• Ensure that all cables between the BayStack router and the BootP server are
firmly connected.
• If using the
ifconfig command, be sure to specify the boot image file
krnl_an.exe for an AN/ANH or krnl_arn.exe for an ARN.
Then, refer to the instructions in the following sections to find and correct the
problem:
• Upstream Router Not Receiving BootP Requests
• Router Not Sending BootP Responses
• BootP Server Not Sending BootP Responses
If you have not isolated the problem to a specific interface, retrieve the number of
BootP packets forwarded and dropped from all routers between the BayStack
router and the BootP server. See “Displaying the Number of Packets Forwarded
and Dropped” on pa
ge B-16.
If you perform the instructions in these sections and cannot find and correct the
problem, contact the Bay Networks Technical Solutions Center.
Upstream Router Not Receiving BootP Requests
If the upstream router is not receiving BootP requests, do the following:
1. Issue the Technician Interface getcfg command to display the router
parameters and the
bconfig or ifconfig command to correct them, if
necessary.
See “Displaying Parameter Settings” on pa
ge B-10 and “Debugging the
BootP Server” on pa
ge B-12 for instructions.
2. Ensure that the BayStack router’s netboot interface is cabled properly.
For EZ-Install, ensure that the synchronous port is cabled to the upstream
router. For Netboot or Directed Netboot, ensure that the configured
synchronous, Ethernet, or ARN token ring interface is cabled to the IP
network.
Komentáře k této Příručce