Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > IP Address Manager (IPAM) > IPAM - Knowledgebase Articles > 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 Nigel on Apr 16, 2018

Views: 2,088 Votes: 1 Revisions: 12

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

Tags

Classifications

Public