Information Technology Reference
In-Depth Information
Table3-14 Booting: Client ARP Requests Timeout During Network Boot
Possible Problem
Solution
Intermediate
routers have ARP
filtering enabled
1.
Boot the router from ROM.
2.
Make sure that you can
ping
the server from the router.
3.
Use the copy
running-config tftp
privileged exec command
to test TFTP connectivity to the server.
4.
If the preceding steps are successful, check the configuration
at the intermediate router using the
show arp
exec
command.
5.
Enable the
debug arp
privileged exec command to
determine whether neighbor proxy ARP responses are being
generated.
Caution:
Because debugging output is assigned high priority in
the CPU process, it can render the system unusable. For this
reason, use
debug
commands only to troubleshoot specific
problems or during troubleshooting sessions with Cisco
technical support staff. Moreover, it is best to use
debug
commands during periods of lower network traffic and fewer
users. Debugging during these periods decreases the likelihood
that increased
debug
command processing overhead will affect
system use.
6.
If the neighbor is not sending proxy ARP responses and its
configuration contains the
no ip proxy-arp
interface
configuration command, disable ARP filtering by removing
the entry.
Note that proxy ARP is enabled by default.
If you need to have a
no ip proxy-arp
entry in the neighbor
router configurations, use the
ip default-gateway
global
configuration command on the router to specify a default
gateway.
7.
