VLAN Calculator
Plan subnets, look up VLAN IDs, decode 802.1Q frames and build trunk configurations. 100% browser-based.
Enter a base network and click Calculate to plan your VLANs.
| Range | Name | Count | VTP Support | Notes |
|---|---|---|---|---|
| 1 | Default | 1 | All modes | Reserved by system; cannot delete |
| 2 – 1001 | Normal | 1,000 | All modes | Stored in vlan.dat; fully managed via VTP |
| 1002 – 1005 | Reserved | 4 | All modes | FDDI/Token Ring legacy; cannot delete |
| 1006 – 4094 | Extended | 3,089 | Transparent / Off only | Not in vlan.dat; stored in running-config |
The 802.1Q tag inserts 4 bytes (TPID 2B + TCI 2B) between the Source MAC and EtherType fields. This increases the standard Ethernet maximum frame size from 1518 bytes to 1522 bytes. Switches must support "baby giants" or have a larger MTU configured.
| PCP | Priority | Name | Typical Use | Level |
|---|
PCP values are used for QoS (Quality of Service) marking at Layer 2. PCP 7 is the highest priority (network control), PCP 0 is Best Effort. Values are mapped to DSCP at Layer 3 boundaries for end-to-end QoS.
A single physical router interface is divided into multiple sub-interfaces, each carrying traffic for one VLAN. The switch port connecting to the router must be configured as a trunk. Cost-effective for small networks.
All inter-VLAN traffic flows through one physical link — creates a bottleneck. Suitable for low-traffic environments only.
A Layer 3 switch performs routing internally using Switched Virtual Interfaces (SVI). Each VLAN has a virtual interface acting as the default gateway. This provides wire-speed routing without external routers.
Routing happens at hardware speed in the switch ASIC. Ideal for large campus networks. No bandwidth bottleneck between VLANs.
| Criteria | Router-on-a-Stick | L3 Switch (SVI) |
|---|---|---|
| Cost | Low — uses existing router | Higher — requires L3 capable switch |
| Performance | Limited by physical link speed | Wire-speed, hardware-based routing |
| Scalability | Limited (bottleneck) | Excellent |
| Best for | Small offices, labs, <5 VLANs | Enterprise, campus, data centre |
| Config complexity | Low | Medium (need ip routing command) |
Never use VLAN 1 as the native VLAN in production. VLAN 1 is the default and is often targeted by VLAN hopping attacks. Use a dedicated unused VLAN (e.g. VLAN 99) as the native VLAN and ensure it carries no user traffic.
The native VLAN must match on both ends of a trunk link. A mismatch causes a CDP/STP native VLAN mismatch warning and can lead to traffic being forwarded to the wrong VLAN.
| Mode | Syncs from server | Advertises | Extended VLANs | Use case |
|---|---|---|---|---|
| Server | Yes | Yes | No | Authoritative VTP server, manages VLAN database |
| Client | Yes | Yes | No | Receives VLAN updates, cannot create/delete VLANs |
| Transparent | No | Forwards only | Yes | Independent VLAN database, passes VTP but ignores it |
| Off | No | No | Yes | No VTP participation — recommended for security |