We’ve come across an issue with DHCP scopes and IPAM.
The process we follow when allocating new subnets to sites is:
1. A new subnets is allocated in IPAM using the subnet allocation wizard after first selecting the desired supernet.
2. We then create the scope on the DHCP server.
3. As the server is already in IPAM, the scope is automatically scanned.
The issue is at this point IPAM creates a duplicate subnet entry in the DB with all the DHCP information as opposed to first checking the database, finding the existing entry and populating that. This results in corruption of the database. The only way around this is to delete the originally created entry and move the new IPAM DHCP server created entry into the correct supernet.
The request is that IPAM checks the database first for entries before creating them, in theory the system would ask the user if they wished to merge the entries too.
