Hi,
We recently found two entries on our ACE logs constantly complaining about ip/arp collisions(%ACE-4-405001), and on further investigation we saw that these IP's related to the mac addresses no longer existed anywhere in our network.
1 5 2014-06-07 06:00:03 2014-06-08 02:00:04 WARNING LOCAL4 ACE-CORE1: %ACE-4-405001: Received ARP RESPONSE collision from x.x.x.x yy.yy.yy.yy.yy.yy on interface vlan5
2 4 2014-06-07 10:59:48 2014-06-08 02:59:49 WARNING LOCAL4 ACE-CORE1: %ACE-4-405001: Received ARP RESPONSE collision from x.x.x.x yy.yy.yy.yy.yy.yy on interface vlan5
3 2 2014-06-07 06:59:48 2014-06-07 22:59:48 WARNING LOCAL4 ACE-CORE1: %ACE-4-405001: Received ARP RESPONSE collision from x.x.x.x yy.yy.yy.yy.yy.yy on interface vlan5
4 1 2014-06-07 10:00:04 2014-06-07 10:00:04 WARNING LOCAL4 ACE-CORE1: %ACE-4-405001: Received ARP RESPONSE collision from x.x.x.x yy.yy.yy.yy.yy.yy on interface vlan5
I exhausted the search for these two "ghost" ip's in our network, and finally remembered that our ACE configuration had a context we removed a few months back.
From this context we had the following configured on the interface:
interface vlan 18
description CHAT-DMZ-FW
bridge-group 1
mac-sticky enable
no shutdown
I want to confirm with you guys if anyone has seen something similar, or knows of this, but I believe the IP's learned mac addresses got "sticky" on the ACE admin context due to the mac-sticky enable command, even after we removed the context these entries persisted?
I finally used this command to remove the "ghost" IP's related to the mac addresses:
clear arp x.x.x.x no-refresh
