Nortel Networks 14.2 manual Router Fails to Netboot

Troubleshooting Network Boot Problems

Router Fails to Netboot

If the AN/ANH or ARN router fails to receive the configuration file or boot image using a netboot option, first do the following:

•Ensure 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 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 AN/ANH or ARN router and the BootP server. See “Displaying the Number of Packets Forwarded and Dropped” on page B-16.

If you perform the instructions in these sections and cannot find and correct the problem, contact the Nortel 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.

For instructions, see “Displaying Parameter Settings” on page B-10 and “Debugging the BootP Server” on page B-12.

2.Ensure that the 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.

308614-14.20 Rev 00 B-3