Troubleshooting Network Boot Problems308614-14.20 Rev 00 B-3Router Fails to NetbootIf the AN/ANH or ARN router fails to receive the configuration file or boot imageusing a netboot option, first do the following:• Ensure that all cables between the router and the BootP server are firmlyconnected.• If using the ifconfig command, be sure to specify the boot image filekrnl_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 theproblem:• Upstream Router Not Receiving BootP Requests• Router Not Sending BootP Responses• BootP Server Not Sending BootP ResponsesIf you have not isolated the problem to a specific interface, retrieve the number ofBootP packets forwarded and dropped from all routers between the AN/ANH orARN router and the BootP server. See “Displaying the Number of PacketsForwarded and Dropped” on page B-16.If you perform the instructions in these sections and cannot find and correct theproblem, contact the Nortel Networks Technical Solutions Center.Upstream Router Not Receiving BootP RequestsIf the upstream router is not receiving BootP requests, do the following:1. Issue the Technician Interface getcfg command to display the routerparameters and the bconfig or ifconfig command to correct them, ifnecessary.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 upstreamrouter. For Netboot or Directed Netboot, ensure that the configuredsynchronous, Ethernet, or ARN token ring interface is cabled to the IPnetwork.
