Information Technology Reference
In-Depth Information
Table 3-10 outlines the problems that might cause this symptom and describes solutions to those
problems.
Table3-10
Booting: Router Cannot Network Boot from TFTP Server
Possible Problem
Solution
Network is
disconnected or
isolated
1.
Boot the router from ROM or Flash memory, if possible.
2.
Use the
ping
exec command to send a message to the
broadcast address (255.255.255.255).
3.
If there is no response from the server, use the
show arp
exec
command to look for an entry in the ARP table that is
associated with the server.
4.
Use the
show ip route
exec command to view the IP routing
table. Look for an entry in the table for the network or subnet
of the server.
Sample display:
The following is sample output from the
show ip route
command
when entered without an address:
Router#
show ip route
Codes: I - IGRP derived, R - RIP derived, O - OSPF
derived
C - connected, S - static, E - EGP derived, B - BGP
derived
candidate default route, IA - OSPF inter area route
Gateway of last resort is 131.119.254.240 to network
129.140.0.0
O E2 150.150.0.0 [160/5] via 131.119.254.6, 0:01:00,
Ethernet2
E 192.67.131.0 [200/128] via 131.119.254.244,
0:02:22, Ethernet2
O E2 192.68.132.0 [160/5] via 131.119.254.6, 0:00:59,
Ethernet2
O E2 130.130.0.0 [160/5] via 131.119.254.6, 0:00:59,
Ethernet2
E 128.128.0.0 [200/128] via 131.119.254.244, 0:02:22,
Ethernet2
E 129.129.0.0 [200/129] via 131.119.254.240, 0:02:22,
Ethernet2
E 192.65.129.0 [200/128] via 131.119.254.244,
0:02:22, Ethernet2
If a path to a boot server exists, a disconnected network is not the
problem. If no path exists, make sure that a path is available
before again attempting to network boot.
continues
