The upgrade from IPAM 1.6 to 1.7 was smooth and without issue. Subnet scans have not frozen as before.
But, just noticed this error when I attempted to scan a DHCP Server. Has anyone seen this before?
This might happens because some scopes has been deleted from DHCP server. Please verify which scopes do not longer exists on that DHCP server and remove those scopes from IPAM.
Please be aware that scope subnet will be also deleted unless you uncheck 'Remove corresponding subnets'.
If a scope is removed from the DHCP Server, does IPAM have any mechanism to detect that a scope has been deleted and act upon it? Either with a warning and prompt to remove the DHCP Scope from IPAM or the ability to ignore it?
What exactly is the IPAM mechanism with dealing with deleted scopes from a DHCP Server?
IPAM ignores if DHCP scope is removed from server. You can identify such scope by 'last update' value.
However, there was a bug in 1.6 and older IPAM versions which might have stored unexpected value in database for deleted scopes and after upgrade IPAM 1.7 is crashing on that values. So fix I have described above is one time fix and after cleaning those scopes IPAM will work as expected - i.e. ignoring deleted scopes on DHCP server and work without error.
If someone such as me or another user with 500+ scopes over multiple dhcp servers, what is the process to easily identify and remove dhcp scopes from IPAM that have been deleted from the dhcp server?
