Offer a method to segment overlapping subnets into folder-like structures for address grouping (essentially a method to document ranges of addresses). Concept similar to a supernet, but without the complexity and wasted addresses.
Example:
We have a /21 network. One VLAN. One default gateway router address. (This would be obvious, I hope).
In that /21 network we assign a range of IP addresses for printers, servers, DHCP scope, IoT, network management devices, etc.
In IPAM there is no way to describe the subnet address ranges, report on them, etc. IPAM only understands the /21 network. Please let us have the ability to create subnets of any range length (not a CIDR which is what supernets require) and use the .0 and .255 addresses within the /21 (supernets force the reservation of the first and last (typically .0/24 and .255/24 within the /21).
IPAM 4.9 Currently Provided Example:
supernet 10.132.32.0/21
subnet 10.132.32.0/22 [static, manually assigned -- 10.132.32.0 and 10.132.35.255 are reserved, wasted]
subnet 10.132.36.0/25 [static, manually assigned -- 10.132.36.0 and 10.132.36.127 are reserved, wasted]
subnet 10.132.36.128/25 [DHCP scope -- 10.132.36.128 and 10.132.36.255 are reserved, wasted]
subnet 10.132.37.0/24 [static, manually assigned -- 10.132.37.0 and 10.132.37.255 are reserved, wasted]
subnet 10.132.38.0/23 [static, manually assigned -- 10.132.38.0 and 10.132.39.255 are reserved, wasted]
Feature Request Example:
subnet 10.132.32.0/21 [description: group master]
subgroup 10.132.32.0-10.132.35.200 [description: subgroup server admins1]
subgroup 10.132.35.201-10.132.36.0 [description: subgroup server admins2]
subgroup 10.132.36.1-10.132.37.100 [description: subgroup DHCP VDI desktops]
subgroup 10.132.37.101-10.132.37.255 [description: subgroup printers]
subgroup 10.132.38.0-10.132.39.255 [description: subgroup network IoT]
.
