VLAN management
Add VLANs with an 802.1Q ID, name, purpose and description. Reserved and well known IDs, such as VLAN 1, the legacy Cisco range 1002 to 1005 and VLAN 4095, are flagged so they are not used by mistake.
Plan IPv4 VLANs, VRFs, subnets, devices and interfaces in one place, catch address conflicts before deployment, and generate starter configuration for Cisco IOS and Arista EOS.
Included in the 14-day Pro trial on every new account. No credit card.
Walkthrough
Start a new project, open a saved one, or load the example schema to see a worked design. Projects save in the browser and to your account, and can be exported to JSON and imported again.
Tag subnets with a VRF so the same range can exist in separate VRFs without false warnings. Duplicate address, overlap and DHCP checks all respect VRF boundaries.
Group interfaces into LACP or static port channels with a trunk, access or routed mode. The member interfaces take their settings from the bundle.
Choose Cisco IOS and IOS XE, Arista EOS or generic pseudocode and generate interface configuration for one device or all of them. Copy or download the output and review it before use.
Export the full design to JSON for backup and reloading, or to CSV for spreadsheets, CMDB and IPAM tools.
Overview
Every new site, refresh or network merger starts with the same work: define the VLANs, plan the subnets, list the devices, assign addresses and prepare the configuration. Mistakes made at this stage often stay hidden until later, such as a duplicate address that only matters when both devices are online, a static address inside a DHCP pool, or a trunk whose two ends disagree on the native VLAN.
The VLAN, Subnet, and IP Address Planner keeps that work in one structured workspace. You define VLANs, plan subnets with their gateways, DHCP pools, reserved addresses and VRFs, and record each device with its interfaces, modes, VLANs, addresses and trunk peers. An address space view shows the free blocks in a site range and finds the next free subnet of a given size, and a VLSM split divides a subnet into equal parts.
Checks run as the design grows. The planner flags reserved VLAN IDs, duplicate addresses within a VRF, subnet overlaps, static addresses inside DHCP pools, duplicate port names and trunk mismatches. When the plan is ready it produces vendor style interface configuration as a starting point, and the whole schema exports to JSON or CSV.
Add VLANs with an 802.1Q ID, name, purpose and description. Reserved and well known IDs, such as VLAN 1, the legacy Cisco range 1002 to 1005 and VLAN 4095, are flagged so they are not used by mistake.
Each subnet carries its network and prefix, gateway, DHCP pool, reserved addresses, VLAN, VRF and description. The planner calculates the usable range, host count and utilisation, and checks that the gateway, pool and reservations sit inside the subnet.
Subnets can be tagged with a VRF, and duplicate address, overlap and DHCP checks respect those boundaries. The same address range can exist in two VRFs without false warnings, while true overlaps within a VRF are still flagged.
Record switches, routers, firewalls, servers and endpoints with their interfaces. Each interface can be access, trunk, routed, loopback or management, with VLANs, voice VLAN, address and DNS name, and interfaces can be bundled into LACP port channels.
Document the far end of a trunk and the planner checks both ends for native VLAN and allowed VLAN agreement, and for a trunk that lands on a non-trunk port. It also warns about undefined VLANs on a trunk and a native VLAN of 1.
Map the allocations inside a site block for a chosen VRF, see the free space as CIDR blocks, and find the next free subnet of a chosen size. A VLSM split divides an existing subnet into equal child subnets.
Generate interface configuration for each device in Cisco IOS and IOS XE, Arista EOS or generic pseudocode, covering VLANs, VRFs, port channels, interface modes and addresses. The output is a planning starting point, not a complete device configuration, and should be reviewed before use.
Export the full schema to JSON for backup and reloading, or to CSV for spreadsheets, CMDB and IPAM tools. Projects save in the browser and to your account.
Inputs and outputs
Inputs 11
Outputs 11
Use cases
No. The planner works with IPv4 and CIDR prefixes, which is where most VLAN, subnet and DHCP planning on enterprise and industrial networks still happens.
These IDs are reserved or well known and are best kept away from general traffic. VLAN 1 is the default VLAN on many switches and a common VLAN hopping vector when used as a native VLAN. VLANs 1002 to 1005 are reserved for legacy FDDI and Token Ring on Cisco IOS, and VLAN 4095 is reserved by 802.1Q.
Each subnet can carry a VRF label. Duplicate address, subnet overlap and DHCP checks only compare subnets in the same VRF, so overlapping ranges in separate VRFs, such as separate tenants or IT and OT networks, do not raise false warnings.
It flags duplicate addresses within a VRF, subnets that overlap within a VRF, static addresses inside a DHCP pool, duplicate port names on a device, and trunk mismatches on native VLAN or allowed VLANs. Each warning links to the entry that needs attention.
It produces interface level configuration for each device in Cisco IOS and IOS XE, Arista EOS or generic pseudocode, including VLANs, VRFs, port channels, interface modes and addresses. It does not cover AAA, routing protocols, ACLs, first hop redundancy, QoS or other global settings, and it should be reviewed before it is applied to a device.
Yes. Enter a site block and a VRF, or let the planner find the smallest block covering that VRF, and it maps the existing allocations and lists the free space. It can also name the first free subnet of a chosen prefix length and add it to the plan.
Projects are saved in your browser and to your account, so they are kept between sessions. You can also export the design to JSON as a backup or to share it, and import it again later.
Included in the 14-day Pro trial on every new account. No credit card.