Network and IP Planning · #03
Online VLAN and VLSM IP Planner
Splits one parent block into several VLANs; returns subnet, gateway, DHCP range and spare capacity per VLAN, with XLSX export.
- Data is processed in your browser and not sent to a server
- Export: XLSX, CSV
Tool
What does this tool do?
The IPv4 Subnet Calculator solves one network. This tool allocates space for several VLANs inside one parent block: it takes each VLAN's device count, growth margin, gateways and static reservations, places them without overlap starting with the largest (VLSM) and lists the free blocks that remain. The result is a plan table ready for switch, firewall and DHCP configuration.
How to use it
- Enter the parent block as a network address (e.g.
10.20.0.0/23). - Write one VLAN per line:
VLAN ID; Name; Devices; Gateways; Static reserve. The last two are optional (default 1 and 0). - Enter the growth margin as a percentage; device counts are rounded up by this factor.
- List networks already in use or reserved (server network, VPN pool) as CIDRs; no VLAN is placed there.
- Choose whether gateways take the first or last usable addresses and press Calculate. Download the plan as XLSX or CSV.
Fields
- Parent IPv4 block
- Network address and prefix: 10.20.0.0/23
- Growth margin
- Added to the device count; the result is rounded up.
- Gateway position
- Gateways use the first or last usable addresses; static reservations sit next to the gateway, DHCP takes the remaining range.
- VLAN lines
- Each line: VLAN ID; Name; Devices; Gateways (opt., 1); Static reserve (opt., 0). Separator ; , or tab.
- Fixed / reserved networks (optional)
- Networks inside the block that must not be allocated, one CIDR per line.
Worked example
| Input | Value |
|---|---|
| Parent IPv4 block | 10.20.0.0/24 |
| Growth margin | 0 |
| Gateway position | First usable address |
| VLAN lines | |
Expected result: VLAN 10 → 10.20.0.0/25 (gateway .1, DHCP .2–.126, 24 spare); VLAN 20 → 10.20.0.128/26 (gateway .129, DHCP .130–.190, 11 spare); free block 10.20.0.192/26.
100 devices + 1 gateway = 101 addresses; with network and broadcast that is 103 addresses, which needs at least a /25 (126 usable). 50 devices + 1 gateway = 51 addresses fit a /26 (62 usable). Because the larger network is placed first the block is not fragmented, and the remaining /26 stays available.
Second scenario
| Input | Value |
|---|---|
| Parent IPv4 block | 10.20.0.0/23 |
| Growth margin | 20 |
| Gateway position | First usable address |
| VLAN lines | |
| Fixed / reserved networks (optional) | |
Expected result: 3 VLANs fit in the /23: Office 10.20.0.0/24, Production 10.20.1.0/25, Management 10.20.1.128/27. Cameras (needs /25) and Guest (needs /24) do not fit; the reserved 10.20.1.192/26 is kept and 10.20.1.160/27 stays free.
With 20 % growth, Office needs 217 and Guest 181 addresses; both need a /24, but the reserved block leaves no second free /24 in the /23. Lines that do not fit are red: enlarge the parent to a /22, move the reservation or shrink the Guest VLAN. Running out of aligned blocks even when the total looks sufficient is the typical VLSM limit.
Method and assumptions
Addresses required per VLAN = ⌈devices × (1 + growth)⌉ + gateways + static reserve. The prefix is the smallest block that fits the required addresses plus network and broadcast; the smallest network is /30.
Placement is VLSM: requests are sorted from largest to smallest, and each is put at the first address aligned to its size in the free space left after removing fixed/reserved networks. This order minimises fragmentation; a large network may still not fit even when the total looks sufficient, and that line is reported.
Gateways take the first (or last) usable addresses, static reservations sit next to them, and the DHCP range takes the remaining contiguous space. Spare = usable addresses − required addresses.
Using the result and troubleshooting
Copy subnet and mask to the switch SVI or firewall sub-interface, the gateway to the default gateway and the DHCP range to the scope definition. Validate exclusions and reservations with the DHCP Scope and Reservation Planner.
Lines with less than 10 % spare are marked yellow; reconsider the growth margin. If a line does not fit, enlarge the parent block by one prefix or review the reserved networks.
When extending an existing network, enter the subnets in use as fixed networks; the tool will not overwrite them.
Limits and common mistakes
- IPv4 only; IPv6 end networks are /64, so VLSM is not needed.
- It produces an address plan, not routing, ACL or trunk configuration.
- Up to 500 VLAN lines are processed.
- Common mistake: forgetting printers, access points, IP phones and management interfaces in the device count. Use the static reserve for them.
Frequently asked questions
Why are my VLANs placed by size and not in my order?
Placing aligned blocks from largest to smallest leaves no gaps. The table still lists VLANs in your order; only the addresses follow this rule.
When should I use 2 or 3 gateways?
First-hop redundancy (HSRP/VRRP) needs a virtual IP plus one address per physical device. Enter 3; the virtual IP is usually the first address.
Related tools and service
- IPv4 Subnet CalculatorCalculates the network address, broadcast, mask and usable host range of a single IPv4 network.
- DHCP Scope and Reservation PlannerCalculates how many dynamic addresses a DHCP scope can lease and finds gateway, exclusion and reservation errors.
- Subnet Overlap CheckerLists overlaps within the same VRF and deliberate reuse across VRFs separately.
Related service: VLAN, Routing and Network Segmentation