zNetLaB › Guided labs › Enterprise
VTP — create a VLAN once and have it appear everywhere
Enterprise Intermediate 3 devices 4 checked tasks 100 points Plan lab
Three switches in a chain should share one VLAN database. Make SW1 the VTP server, the other two clients in the same domain with the same password, trunk the links, and create three VLANs on SW1 only — then check they arrived on the clients, and remember why VTP is also a way to wipe a network (revision numbers). You build it in a browser, type real commands at each device, and every task below is
checked against the running configuration — so you find out it is wrong before anybody else does.
Open this lab in the simulator
The simulator runs in your browser with nothing to install. This lab is part of the full simulator: open it free for 7 days with a new account, then with a plan. It needs an account, which keeps your progress.
The scenario
Three switches in a chain should share one VLAN database. Make SW1 the VTP server, the other two clients in the same domain with the same password, trunk the links, and create three VLANs on SW1 only — then check they arrived on the clients, and remember why VTP is also a way to wipe a network (revision numbers).
Your role: a network engineer on the enterprise team. Level: Intermediate Done when: all 4 goals show as passed (100 points).
Network status
Devices: 3 switchs, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. SW1-Server, SW2-Client, SW3-Client start with an empty configuration. Known problems
None: nothing is misconfigured. The network is simply not finished: what the goals list is what you have to build or secure. Goals
SW1 is the VTP server in the domain (20 pts) SW2 and SW3 are VTP clients (20 pts) VLANs 10, 20 and 30 exist on SW1 (20 pts) All three VLANs arrived on SW3 without being typed there (40 pts) The activity, in order
SW1 is the VTP server in the domain Why: Reading a show command is the core skill of troubleshooting: the output is the truth, not your configuration. Verify with: show vtp status SW2 and SW3 are VTP clients Why: Reading a show command is the core skill of troubleshooting: the output is the truth, not your configuration. Verify with: show vtp status VLANs 10, 20 and 30 exist on SW1 Why: A port assigned to a VLAN that does not exist carries nothing. Verify with: show vlan brief All three VLANs arrived on SW3 without being typed there Why: A port assigned to a VLAN that does not exist carries nothing. Verify with: show vlan brief Tips
Work in the order given: later goals depend on the earlier ones. After every change, run the verify command before moving on; do not guess. Stuck? Read the verify output first. It names the interface, neighbour or route that is wrong. Common mistake: Plugging in a client with a higher revision number Common mistake: Different domain names or passwords Common mistake: Trunks that are not trunking, so nothing propagates Why this matters
VTP distributes the VLAN database from servers to clients. It saves typing and is also a way to wipe a network: a switch with a higher revision number and an empty database can delete every VLAN.
What you will be able to do
Set VTP domain, mode and password
Create VLANs on the server and verify propagation
Explain revision numbers and why transparent mode is the safe default
The network
Catalyst 2960-24TT — 3 devices in all, already cabled.
Gi0/1 Gi0/1 Gi0/2 Gi0/1 SW1-Server SW2-Client SW3-Client Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
SW1-Server Catalyst 2960-24TT configure it SW2-Client Catalyst 2960-24TT configure it SW3-Client Catalyst 2960-24TT configure it
Cabling
SW1-Server Gi0/1 ↔ SW2-Client Gi0/1 SW2-Client Gi0/2 ↔ SW3-Client Gi0/1
What is configured at the start
These are already configured when the lab opens — including, where this is a troubleshooting lab, the fault itself:
SW1-Server interface g0/1
switchport mode trunk
exit SW2-Client interface range g0/1 - 2
switchport mode trunk
exit SW3-Client interface g0/1
switchport mode trunk
exit Tasks, and how each one is checked
Every task is decided by reading the live network — a neighbour in FULL, a ping that succeeds, a line in the running configuration — not by looking for a keyword you typed. The same command shows you what the lab sees.
# Task Pts How to verify it yourself
1 SW1 is the VTP server in the domain 20 On SW1-Server: show vtp status output matches VTP Operating Mode\s*:\s*Server. 2 SW2 and SW3 are VTP clients 20 On SW2-Client: show vtp status output matches VTP Operating Mode\s*:\s*Client. and On SW3-Client: show vtp status output matches VTP Operating Mode\s*:\s*Client. 3 VLANs 10, 20 and 30 exist on SW1 20 On SW1-Server: show vlan brief lists VLAN 10. and On SW1-Server: show vlan brief lists VLAN 20. and On SW1-Server: show vlan brief lists VLAN 30. 4 All three VLANs arrived on SW3 without being typed there 40 On SW3-Client: show vlan brief lists VLAN 10. and On SW3-Client: show vlan brief lists VLAN 20. and On SW3-Client: show vlan brief lists VLAN 30.
Stuck? Ask the coach
Tell the coach what you see or what you tried. It gives you a hint, not the answer, the way a senior engineer would. Included with a free trial or any plan.
Ask the coach
Common mistakes
Plugging in a client with a higher revision number
Different domain names or passwords
Trunks that are not trunking, so nothing propagates
Reference solution
Try it yourself first — the lab checks your work either way. This is one configuration that makes every task pass, device by device:
SW1-Server vtp domain ZNETLAB
vtp mode server
vtp password Vtp-S3cret
vlan 10
name SALES
vlan 20
name ENG
vlan 30
name GUEST SW2-Client vtp domain ZNETLAB
vtp mode client
vtp password Vtp-S3cret SW3-Client vtp domain ZNETLAB
vtp mode client
vtp password Vtp-S3cret Where this is examined
CCNA (VLANs), CCNP ENCOR (VTP), Network+ (switching).
This lab practises these topics in the zNetLaB certification courses:
Related labs
Where to start
The lessons all guided labs plans
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.