VTP is a protocol that lets your switches share the same VLAN list, so you don’t have to create VLANs on every switch one by one. Switches that are in the same VTP domain (a name you choose) exchange this VLAN list across a trunk link (a link that carries traffic for many VLANs at once). On a server switch you add or rename VLANs; client switches automatically copy and stay in sync with that list. A transparent switch simply passes the VTP messages along but keeps its own local VLAN list separate. VTP itself doesn’t carry user traffic—it only keeps the VLAN database consistent across the network. In this lab, you’ll set one switch as a server, one as a client, build a trunk, and confirm the client learns the server’s VLANs.
Devices: SW0 (server) — SW1 (client).
Link:
SW0 SW1
Gi0/1 <— trunk —> Gi0/1.
Platform/IOS family: Classic Cisco IOS (Catalyst IOS style).
VTP domain name: lab_network (chosen to match Cisco’s documented outputs).
VTP version: 2
SW0 — VTP server
vtp version 2 enables VTPv2; it is backward-compatible with v1 and allows token-ring VLANs (rare today).
vtp domain lab_network puts SW0 in the same sharing group.
vtp mode server makes SW0 the source of VLAN database changes.
VLANs 10 and 20 are created here so clients can learn them automatically.
SW1 — VTP client
Same domain and version ensures SW1 joins the same database.
vtp mode client makes SW1 learn VLANs from SW0 and blocks local creation.
SW0 — trunk toward SW1
SW1 — trunk toward SW0
Trunking lets both VLAN traffic and VTP advertisements travel between switches. Without the trunk, SW1 would not learn VLANs from SW0.
VTP is running version 2, in domain lab_network, and the switch is in Server mode.
The device is sending/receiving VTP advertisements on trunks.
Domain mismatch → client shows empty VLAN list → check vtp domain lab_network.
Trunk missing → counters stay zero → enable switchport mode trunk.
Wrong version (1 vs 2) → VLANs not syncing → force vtp version 2 on all.
Trying to create VLAN on client → error → client mode blocks local VLAN changes; use server.
Revision number mismatch after reloading → old switch with higher revision overwrote VLANs → reset revision (change domain, then set back).
Add VLAN 30 named HR on SW0 and confirm it appears on SW1 with show vlan brief.
Prediction Challenge:
If you delete VLAN 20 on SW0 (server), what will happen on SW1 (client)?
If SW1 were in Transparent mode instead, what would happen?