
Troubleshooting Network Boot Problems
A-3
8. If you are using EZ-Install over a Frame Relay permanent virtual circuit
(PVC) in group access mode, make sure the upstream router’s BOOTP
client interface table is configured properly.
Router Fails to Netboot
If the router fails to receive the configuration file or image using a network boot
option, first
• Make sure that all cables between the router and the BOOTP server are firmly
connected.
• If using the
ifconfig command, be sure to specify the boot image krnl_an.exe
(not an.exe).
Then refer to the instructions in the following sections until you 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 router and
the BOOTP server. Refer to “Displaying the Number of Packets Forwarded and
Dropped” later in this appendix.
Contact your local Bay Networks Technical Response Center if you perform the
instructions in these sections and cannot find and correct the problem.
Upstream Router Not Receiving BOOTP Requests
If the upstream router is not receiving BOOTP request messages, do the
following:
1. Execute the Technician Interface getcfg or ifconfig command to display
the router parameters and the
bconfig command to correct them if
necessary.
Refer to “Displaying Parameter Settings” and “Debugging the BOOTP
Server” later in this appendix if you need instructions.
Commentaires sur ces manuels