When the Address Resolution Protocol (ARP) sanity check for ARP packets fails, a router cannot install or learn an ARP entry. This means that an incorrect reply was received from the peer device. In this case, the recommendation is to check the ARP reply content to identify if there are any errors.
This article shows how it is done.
The router is unable to learn ARP for a peer even though the router has received ARP packets from the peer.
Check ARP statistics by using show system statistics arp . An example is given from the DUT router as follows:
show system statistics arp
{master:member0-re0} labroot@mxvc> show system statistics arp member 0 |except "0 " Dec 02 17:56:10 member0: -------------------------------------------------------------------------- arp: 39315 datagrams received 1532 ARP requests received 1436 ARP replies received 26 resolution request received 1187 datagrams with multicast target address <<Target mac address is multicast mac. </span> 12235 datagrams for an address not on the interface << Sender IP address is not correct(not with same subnet as DUT’s interface). 116768 datagrams which were not for me << Target mac address or target protocol address is not correct(not DUT’s interface mac or IP address). 315 datagrams with source address duplicate to mine << Sender IP address was duplicated to DUT's IP address. 17978 packets discarded waiting for resolution 16 packets sent after waiting for resolution 1532 ARP replies sent 16 Current Public ARP nexthops present 36 Current IRI ARP nexthops present 3 Current Management ARP nexthops present {master:member0-re0} labroot@mxvc>
To resolve this issue, perform the following:
Check the peer ARP reply packet's content to determine whether it is correct or not.
You can use monitor traffic interface to check the sender's IP address.
monitor traffic interface
You can use write-file option or print-hex option to check the content value for the target MAC address and IP address of the ARP reply.
write-file
print-hex
Then if the ARP reply from the peer is found to be incorrect, ask the peer device to correct it.