| VLAN Name | Hosts Req. | CIDR | Network | Subnet Mask | First Host | Last Host | Broadcast | Usable |
|---|
Start with a base network large enough to hold all required VLANs or subnets. Add each VLAN name and the number of hosts required. The planner sorts larger requirements first and assigns the smallest suitable subnet to each group, reducing wasted address space.
VLSM is useful when different departments or device groups need different subnet sizes. A server VLAN may need 20 addresses, a camera VLAN may need 80 addresses and a point-to-point link may need only two. Fixed-size subnetting would waste addresses; VLSM allocates a more suitable block for each need.
The generated Cisco IOS interface configuration is a starting point. Review interface names, VLAN IDs, gateway addresses and site standards before applying any configuration to production equipment.
Why are larger VLANs allocated first? Allocating the largest subnets first helps avoid fragmentation and makes it more likely that all requirements will fit inside the base network.
Should I leave spare addresses? Yes. Real networks grow. Leave capacity for new devices, printers, wireless access points, cameras, temporary devices and future VLANs.
Can this replace network design review? No. It helps with address planning, but routing, DHCP, DNS, firewall policies, redundancy and documentation still need proper review.