
Troubleshooting Guide 3-17
Failed RARP Requests (Got a MAC, need the IP):
The device (for example, an EMME) sends out a RARP request with its MAC address and uses the TID portion
of the packet to target the IP address of itself, 134.141.55.25. The RARP request will fail if the EMME RARPs
with a TID IP address of 0.0.0.0 rather than 134.141.55.25. Then the device will just reboot. If this is the
failure, you can fix this in one of two ways: either re-assign the IP address at the device, via LM, or clear
NVRAM on the device. Then you must re-enter the IP address. (Clearing the NVRAM on the device is the less
painful of the two fixes.)
Failed ARP Requests (Got an IP, need the MAC):
After the RARP is successful, the device will ARP with the server IP for the server’s MAC address. If the
server does not respond, it is probably because of the subnet mask. Make sure the target address in the packet is
targeting the server. The only remedy here is to try to set up another server.
Failed TFTP Read Request:
Please, can I read the file? Does the file exist? Do I have read privileges? Does a checksum reveal a good file?
Is this file for me (my device type)? You will see some explanation in the packet. “File not found” or checksum
error. These errors are intuitive. Sometimes the TFTP download will fail after it begins TFTP read requests and
TFTP data acknowledge. This could be a corrupt file that did not fail during the initial read.
Komentáře k této Příručce