Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > IP Address Manager (IPAM) > X scopes has not been added because it is overlapping with existing subnet!

X scopes has not been added because it is overlapping with existing subnet!

Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 48 Votes: 1 Revisions: 10

Overview

This article provides steps to resolve the following error when adding discovered scopes overlapping with existing subnets: 

X scopes has not been added because it is overlapping with existing subnet!

Environment

All IPAM versions

Resolution


1. Ensure that the scope is expanded or contracted both ways or in one direction.
2. Modify either the start or the endip address one at a time and immediately applying the changes after each and every change to the start or end ip address of the scope.
3. If two stand-alone DHCP servers are servicing the same subnet, ensure that you are not overlapping the available pool on each DHCP server as they do NOT share the DHCP database and are not aware of the leases that are assigned. By excluding addresses, you ensure that IPs will not be offered that may otherwise be in use.  

4. Drop the subnet from IPAM, rescan the DHCP server and have the scope pulled into IPAM where it will create a new subnet in which to fit itself.
5. Enable Duplicate Subnets through IPAM Settings, Advanced Settings, Enable Duplicate Subnets and have the new scope exist in it's own subnet.
Last modified
19:43, 22 Jun 2016

Tags

Classifications

Public