IP Conflict Alert

[Yonairo_Argu]

Greetings, we are receiving between 4 to 5 emails per day reporting an IP conflict between two devices. The point is that after checking the MACs of these two devices, both are not on the network since October 28, and being disconnected, they are still registered with the same IP, but meraki continues to report this conflict even though the two devices are disconnected. How do we disable this particular alert? Since it is not a problem on the production network, but rather a confusion of meraki. 

Thanks!

[KarstenI]

Are you sure that no other device is using that IP for example because of a misconfiguration? Do you see the IP in the ARP-table of the L3 devices?

[Andre_Afonso]

Hi Yonairo,

Are you sure that Ip´s address are not being use? Make a double check on the Arp table.

How is the DHCP status? any rule? Did you try to remove it? 
Suggestion, try to remove the alerts configuration and add again.

[Yonairo_Argu]

However, the report is sent from a Meraki MX appliance. The DHCP service is working normally. I will try to disable the alerts for a few minutes.

[Yonairo_Argu]

This is the event log of one of the two devices.Curiously, the ip shown, 10.2.2.1, is an ip that is located in another site with subnet 10.2.x.x, however, this ip (10.2.2.1) in this site, is not claimed by any equipment. The last time both computers were registered was on October 28th at the main site which has subnet 10.1.2.x.

[CptnCrnch]

It looks like 00:0b:82:ac:74:55 is also trying to be 10.2.2.1. I'd guess that this is the IP address that's configured on your MX interface?

[Yonairo_Argu]

Yes, It looks like 00:0b:82:ac:74:55 is also trying to be 10.2.2.1. But, the ip of the MX is 10.2.1.254. However, this ip is located at another site, which is obviously in another ip range. The subnet of this site is 10.2.0.0/16. But meraki reports that these two devices, or this ips conflict, is on the main site, which is 10.1.x.x. How is this possible?

[Yonairo_Argu]

I changed the IP of both computers to a fixed Ip but for a strange reason meraki continues to alert conflict for the IP 10.2.2.1.