We have a single MX84 device in place at a client network that is notifying us of Client IP Conflicts daily or more often. One device that is involved is a Canon LBP6670 printer with a static IP address set for 192.168.3.31 on our Data network. The IP conflicts that are being reported almost always involve this printer and another device, but the reported IP address is always for a network that is not configured on the MX84 device. The most commonly reported IP addresses are in the self assigned ranges for systems not getting DHCP, 169.254.0.0/16, and the numbers in the last 2 octets appear to be random. We also occasionally see an address in the 192.168.100.0/24 scope but that configuration is nowhere programmed on the Meraki device. The Only IP Scopes that are programmed into the MX84 are 192.168.3.0/24, 192.168.2.0/24, 192.168.30.0/24, and 192.168.60.0/24. None of the programmed network scopes are being flagged for a duplicate IP address. I have tried opening a support case with Meraki but they are not able to help unless we get a packet capture when the duplication is being reported, but the timing is always random and even if we check the devices within seconds of the alert coming through our system the duplication is no longer present. To catch a packet capture during the event that triggered the alert we would need to run a 24 hour packet capture. I'm not sure that is possible from the Meraki itself, as support has never suggested a way to do so and we cannot trigger the alert on command. Another thing that we have not been able to get an answer about is why the Meraki is reporting IP Conflicts for networks it is not programmed to even see? We are looking for any suggestions for narrowing down the issue and finding a solution.
... View more
