Information Technology Reference
In-Depth Information
In some cases, there might be an initial response from a server, but the network boot sequence still fails.
The boot message would be similar to the following:
Booting gs3-bfx!..........[failed]
Table 3-13 outlines the problems that might cause this symptom and describes solutions to those
problems.
Table3-13 Booting: Invalid Routes Prevent Network Booting
Possible Problem
Solution
Bad routing paths
on neighbor
routers
Verify that neighbor routers can
ping
the server.
1.
Use the
trace
exec command to determine the path to the
server.
2.
Use the
show arp
1
privileged exec command to examine the
ARP tables, or the
show ip route
privileged exec command
to view the IP routing table. Verify that the server is listed
and that the routing table entries are appropriate.
3.
Use the
clear arp-cache
and
clear ip-route
privileged exec
commands to force the router to repopulate its ARP and
routing tables.
4.
Try to network boot the router again.
5.
Problems caused
by multiple paths
1.
Shut down all extra interfaces except the one over which
you intend to network boot the router.
2.
Use the
no ip proxy-arp
interface configuration command
on all neighboring routers to disable their capability to
provide proxy ARP responses.
Make this change with care because it can cause problems for
other network traffic.
If you do not want to disable proxy ARP, boot the router from
ROM and configure the
ip default-gateway
global
configuration command.
3.
Try to network boot the router again.
1.
ARP = Address Resolution Protocol
Booting: Client ARP Requests Timeout During Network Boot
Symptom:
Client ARP requests a timeout during a network boot. If the router does not receive an ARP
response, a message similar to the following is displayed on the console:
Booting gs3-bfx..........[timed out]
