When you have lots of incomplete entries there is something that is scanning your network.
Try to get rid of that. Sometimes “autodiscover” options in certain devices or drivers do that.
(e.g. to find a printer on the network)
" I had a lot of double entries that were not complete; however, this is out of control I have a dozen or more, one with a dozen of its own entries showing complete. Is there not a built in arp flush somewhere with this change to 7. I understand the change might be good but we should have a manual flush. Any other scripts?"
***My apologies, the ARP entries status was Complete, so the script to remove incomplete is not going to work for that. The in-complete duplicates were rather minimal.
When you have no special ARP entries you made yourself (static, published) but only entries that show up in the list as DC (with the occasional D) you can clear the entire table using:
/ip arp remove [ find ]
Then it will immediately re-build itself with what is minimally necessary at that moment.
To deal with stale ARP entries, one workaround is scheduling a script to run regularly that clears out old ARP entries using the “/ip arp remove [find where interface=”“]” command.
With default max-neighbor-entries , my arp table grew up to around 4000 with active DHCP client around 1500. now I set my max-neighbor-entries to around 2000, it seem ‘arp-timeout’ working even not exact 30 second. My arp table like clear it self after the arp entry number touch a certain value like 1000 or something when I did an observation. My device is CCR2004 , router OS 7.16rc2 with bridge, 15 vlan and as DHCP server.