You said, “there is no such IP address ANYMORE except on the F5.” Did that IP address used to exist on another device? If so, it is possible that the F5 still has an ARP entry for that “old” MAC address. Also, is there a firewall on that same VLAN somewhere. If so, the firewall may be Proxy ARP’ing for that address if it is configured for a NAT translation for that address or address space.
I did the arp -a but I got no match found, what does grep do?
If arp -a outputs multiple lines, piping it to grep allows you to output only the matching lines. If the issue isn’t still logging, I’d probably ignore it…doesn’t seem like the F5 knows about it…
Wow. How big is that subnet? 10.0.0.0/8 or what? Seriously though, if you haven’t seen the error log recently it has probably aged out of the arp cache and you don’t need to worry about it.
Not sure if this can help someone - have just seen something similar. For us the address conflict seen on an LB HA pair was caused by a disabled virtual server on another standalone load balancer on the same VLAN. After deleting the disabled VS from the other LB, the log entries no longer appear.
tmm[5861]01190004address conflict detected for xxx.xxx.xxx.xxx (xx:xx:xx:xx:xx:xx) on vlan XXX