IPAM reporting false duplicate addresses during DHCP failover synchronization

Question

IPAM reporting false duplicate addresses during DHCP failover synchronization

Jones Oscar 40

Dear support team,

Our IPAM server is responsible for tracking address usage across three separate DHCP failover pairs.

Most of the time everything works as expected, but during the morning rush, when thousands of clients renew their leases within a short window, synchronization between the DHCP servers seems to fall behind.

IPAM reports a number of perfectly valid addresses as rogue duplicates even though no actual conflicts exist on the network. Once replication catches up, the alerts disappear on their own. How do you adjust the validation timing so IPAM waits for DHCP failover replication to settle before scanning for duplicate addresses?

Thank you for your help.

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Hi Jones,

There is no built-in IPAM setting that makes duplicate-address validation wait for DHCP failover lease replication to finish. IPAM evaluates the data it collects from DHCP servers at the time of its scheduled discovery and auditing tasks, so during periods of heavy lease renewals it can temporarily report false duplicate addresses until failover synchronization catches up.

The recommended approach is to adjust the timing of IPAM data collection, auditing, or discovery tasks so they run after the peak lease-renewal period rather than during it. This reduces the chance that IPAM scans one DHCP partner before the lease updates have been replicated to the other partner.

In short, there is no supported "replication settling delay" parameter in IPAM; the workaround is to tune the IPAM task schedule to avoid scanning while DHCP failover replication is still catching up.

Harry.