Summary: Defines the naming convention for VLANs configured on IOS-XE switches and Meraki MS/MX networks.
| Field | Value |
|---|---|
| Author | Peter |
| Owner | Network Team |
| Status | Draft |
| Version | 0.4 |
| Last Reviewed | 2026-06-12 |
| Review Due | 2026-12-12 |
| Approver | — |
| Approved Date | — |
| Version | Date | Author | Description |
|---|---|---|---|
| 0.4 | 2026-06-12 | Peter | Added note on the LAB_LAN expansion zone (VLANs 14–20 spaced by 2, names increment by 1) |
| 0.3 | 2026-06-12 | Peter | DMZ naming convention changed to DMZ0X_<TECHNOLOGY> format |
| 0.2 | 2026-06-12 | Peter | Updated VLAN 240 example from EDGE_IT_TRANSIT to WAN_IT_TRANSIT; DMZ VLAN example renumbered to start at 401 |
| 0.1 | 2026-06-12 | Peter | Initial draft |
⚠️ Draft
This standard is a draft and has not been reviewed or approved. Do not apply it until it has been signed off.
This standard defines how VLANs are named on IOS-XE switches and Meraki MS/MX networks. A consistent naming convention makes VLAN purpose self-evident from dashboards and show output, reduces ambiguity when working across multiple sites, and supports scripts and tools that parse VLAN names.
This standard applies to the VLAN name field configured for every VLAN on IOS-XE switches (via the name command) and Meraki MS/MX networks (the VLAN name field in the dashboard) managed by the Network Team.
It does not apply to:
_) — not hyphens, spaces, or camelCase.SERVER_LAN, VOICE, GUEST_WIRELESS), not a site code, department abbreviation, or the VLAN ID itself._#N, starting at 1 (e.g. LAB_LAN_#1, LAB_LAN_#2).DMZ0X_<TECHNOLOGY>, where 0X is a two-digit zero-padded zone number appended directly to DMZ with no underscore or #, followed by an underscore and a generic name for the technology or service hosted in that zone (e.g. DMZ01_WEB, DMZ02_VPN). This pattern is distinct from the _#N suffix used for duplicate-purpose segments in requirement 4._LAN — wired data subnet (e.g. SERVER_LAN, OFFICE_LAN)_WIRELESS — wireless client segment (e.g. GUEST_WIRELESS)_TRANSIT — point-to-point or inter-device routing segment (e.g. WAN_IT_TRANSIT)VOICE, VIDEO, DEVICE_MANAGEMENT)name SERVER_LAN, not name Server_Lan or name server-lan.The table below illustrates the naming pattern using VLAN IDs and names from an existing site. The VLAN IDs are illustrative only and are not a fixed allocation required by this standard.
| VLAN ID | VLAN Name |
|---|---|
| 10 | SERVER_LAN |
| 12 | OFFICE_LAN |
| 14 | LAB_LAN_#1 |
| 16 | LAB_LAN_#2 |
| 18 | LAB_LAN_#3 |
| 20 | LAB_LAN_#4 |
| 40 | GOV_LAN |
| 60 | VOICE |
| 90 | VIDEO |
| 120 | SECURITY_DEVICES |
| 172 | ELEMENT_WIRELESS |
| 192 | GUEST_WIRELESS |
| 220 | DEVICE_MANAGEMENT |
| 240 | WAN_IT_TRANSIT |
| 241 | FTD_IT_TRANSIT |
| 401 | DMZ01_<TECHNOLOGY> |
VLANs 14–20 form an expansion zone reserved for LAB_LAN segments. VLAN IDs are spaced by 2 (14, 16, 18, 20) to leave room for future numbering, but the _#N name suffix increments by 1 regardless (LAB_LAN_#1 through LAB_LAN_#4). Only VLAN 14 (LAB_LAN_#1) needs to be provisioned initially — VLANs 16, 18, and 20 are added only as additional lab LAN segments are required.
Uppercase, underscore-separated names with consistent suffixes make VLAN purpose immediately clear from show vlan output and the Meraki dashboard, without needing to cross-reference site documentation. Numbered suffixes (_#N) for duplicate-purpose segments (e.g. multiple lab VLANs) avoid ambiguous duplicate names while preserving the underlying function in the name. Consistent naming also supports automation that parses VLAN names, such as scripts referenced in KBA-030 - TCL Script to Update Default Route.
Existing VLANs with non-conforming names may be retained where renaming would cause a configuration or documentation impact disproportionate to the benefit. All new VLANs must follow this standard. Any deviation for a new VLAN requires Network Team approval and must be documented in the relevant site's configuration notes.