Practical tools for system, network, security, and operations administrators.

NET-C0124 · Switching & Layer 2

VLANs Explained

Give one VLAN an id and a sentence about who is in it. VLANs Explained.

Updated 25 October 2026 · Explainer

This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.

What this hour is for

A VLAN is a broadcast domain identified by a number. The access port page and the trunk page are how it is carried. This page is the id and the meaning.

Pick an id that is not already used, and not VLAN 1 for a new user group. Write the name. A range generator can list free ids from a start and an end you type. It does not create them on a switch.

The subnet is a separate decision that should match the VLAN one for one. Two subnets on one VLAN is a design you must justify. The subnetting guide owns the prefix.

Do not create fifty VLANs because the numbers were free.

The change you can finish

Apply nothing during the writing of the note. When the lab window opens, it is one change on the device named in the ticket. Read the draft, then the device, then decide.

Rollback is the file or the revision you saved first. You do not invent a rollback after the only copy is gone.

  1. Name the group of devices.
  2. Choose one unused id.
  3. Write the name.
  4. Point at the prefix, or say it is not chosen yet.
  5. Leave VLAN 1 for what it already does.
  6. Do not configure a switch on this page.

Mistakes that outlive the command

VLANs Explained goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.

Decisions to write down

One decision for VLANs Explained: One id is chosen. The name matches the group. VLAN 1 was not reused. The prefix is linked or explicitly later. And no switch was changed.

Checks before you call it done

Confirm this before you call the change done: The id and name are in the ticket. The group is one sentence. The existing id list was checked. No bulk create happened. And configuration waits for the vendor how-to. If one of those fails, stop.

One VLAN id. One sentence.
Do not fill the range.

Before you leave the device

VLANs Explained ends when the hostname on the device matches the hostname in the ticket. If it does not, you are on the wrong box. Stop. A command that succeeded on the wrong box is not progress.

The draft stays a draft until a person has read the names in it. A generator does not log into the device and does not know which interface is the uplink. You delete a line that names a device, a zone, or a prefix you did not write down.

0.0.0.0/0 is not kept because a sample included it. A source you can say is the source you keep. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. They belong in the note. They are not prefixes you type onto a production device because they appeared in a draft.

prompt-for-this is a reminder that a secret is missing. It is not a password, a key, a community string, or a pre-shared key you save in the ticket or in git. The real secret stays in the store.

One change is the window. A VLAN and a routing protocol and a VPN do not share it. If two things move and the result is wrong, you will not know which one did it. The next feature waits for its own page.

If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a device nobody can rebuild. Restore the copy you took first.

A second person reads the device name and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the device alone.

This page is a planning guide. It is not a vendor manual, not an official standard, and not a permission to touch a network you do not administer. The pillar guide owns the wider design. This page owns one lab proof.

Tools for this guide

These tools run in the browser on this site. They do not log into your machines.

More in this cluster

The pillar for this page, and the next published pages filed with it.