Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Are there any plans to prevent IPAM from entering duplicate subnets?

Core issue - IPAM will allow you to create and/or import duplicate subnets.

Example #1 - If two different DHCP servers contain the same subnet (for HA purposes), but with a different scope allocation, each subnet is treated independently and entered in as two duplicate subnets.

Example #2 - If a subnet is created, you can readily create another identical subnet without warning.

Example #3 - If a subnet is created, an overlapping subnet scan be created conflicting with the IP space. 10.10.10.0/24, 10.10.10.0/23, 10.10.8.0/22 can all be created.

Find more posts tagged with

ip_address_management

Accepted answers

mark_wiggans

http://knowledgebase.solarwinds.com/kb/questions/2385/Managing+Duplicate+Subnets+in+IPAM

All comments

Ralphr

To piggyback on jon0966's post, not only can you create overlapping subnets but it treats the addresses as separate entities. So if I reserve an IP Address in one such subnet it will still appear as available in the other

ynchan38

I agree that allowing creation of duplicate subnets and IP's deficit the purpose of an IP management tool. It makes more sense if you can create different customers (or areas/planets/sites/...etc) and allow duplicate subnets only if it is for a different customer.

mavturner

Thanks for the feedback everyone. There are some specific use cases where duplicate subnets are desirable. Most of those involve using IPAM as a passive address management system. For example, if an MSP has customers on duplicate internal addresses, we would allow you to create the duplicate space and give the subnet a different name. Obviously in this scenario, they are not scanning because the scan would return the same results. I definitely understand your frustration around this and we are considering options for a future release.

Would you prefer a global setting to prevent you from entering duplicate subnets or just a warning message when you try to add them?

Mav

ynchan38

A warning message with option to proceed or not is good enough for me.

I understand there are use cases for creating duplicate subnets. In your example, customer ID and IP address should be unique key then different customers can have duplicate addresses while all IP addresses are unique for each customer.

Thanks

jon0966

I would prefer the option that it is not allowed and a warning is displayed saying you cannot do it.