Hands-On Lab: Configuring VTP Clients and Servers on Catalyst Switches

This hands-on lab configures VLAN Trunking Protocol between a server switch and a client switch, demonstrating how VLANs created on the server automatically propagate to the client without manual configuration on every device.

VTP Server ModeVTP Client ModeVLAN Propagation

~3 min read · Updated Sep 12, 2026

Lab Objective

Configure one switch as a VTP server and a second switch as a VTP client within the same VTP domain, then create a VLAN on the server and verify it automatically appears on the client.

Lab Purpose

Manually creating identical VLANs on every switch in a large network is tedious and error-prone. VTP allows VLAN database changes made on a server to propagate automatically to client switches, though this convenience comes with real risks that later labs will explore.

Lab Topology

SwitchServer ---- trunk link ---- SwitchClient

Both switches connected via a trunk port
already configured

Task 1: Configure the VTP Domain and Server Mode

On SwitchServer, configure the VTP domain name to CorpNet and explicitly set VTP mode to server.

Task 2: Configure the Client

On SwitchClient, configure the same VTP domain name and set VTP mode to client.

Task 3: Verify VTP Status on Both Switches

Confirm both switches show the same domain name and their respective correct VTP modes.

Task 4: Create a VLAN on the Server

Create VLAN 30 named Engineering on SwitchServer only.

Task 5: Verify Automatic Propagation to the Client

Confirm VLAN 30 automatically appears in SwitchClient's VLAN database without being manually configured there.

Solution and Verification

SwitchServer(config)# vtp domain CorpNet
SwitchServer(config)# vtp mode server

Setting device to VTP SERVER mode

SwitchClient(config)# vtp domain CorpNet
SwitchClient(config)# vtp mode client

Setting device to VTP CLIENT mode

SwitchServer# show vtp status

VTP Operating Mode           : Server
VTP Domain Name              : CorpNet
Configuration Revision       : 0

SwitchClient# show vtp status

VTP Operating Mode           : Client
VTP Domain Name              : CorpNet
Configuration Revision       : 0

SwitchServer(config)# vlan 30
SwitchServer(config-vlan)# name Engineering
SwitchServer(config-vlan)# exit

SwitchServer# show vtp status | include Revision

Configuration Revision       : 1
-- Notice the revision number incremented
-- from 0 to 1 the moment a VLAN was added --
-- this revision number is what SwitchClient
-- checks to know new information exists

SwitchClient# show vlan brief

VLAN Name       Status    Ports
---- ---------- --------- -----
30   Engineering active

-- VLAN 30 appeared automatically, even though
-- it was never manually typed on SwitchClient

Key Takeaway

VTP's revision number is the mechanism that triggers propagation — a client accepts VLAN database updates only when it receives a VTP advertisement with a HIGHER revision number than its own current database, which is exactly why understanding this number matters deeply when troubleshooting unexpected VLAN changes.

Written & researched by Dr. Shahin Siami

Related Articles

Hands-On Lab: Configuring Standard VLANs on Catalyst Switches

This hands-on lab covers creating standard-range VLANs, assigning access ports to them, and verifying that devices in different VLANs are properly isolated from each other at Layer 2.

Continue

Hands-On Lab: Verifying IP Parameters on macOS (GUI)

This hands-on lab covers checking a Mac's current IP configuration using the System Settings network panel, viewing detailed TCP/IP information, and renewing a DHCP lease directly from the graphical interface.

Continue

Hands-On Lab: Verifying IP Parameters on Linux (GUI and CLI)

This hands-on lab covers checking a Linux machine's current IP configuration using both the GUI network settings panel and command-line tools, and demonstrates renewing a DHCP lease using standard Linux networking utilities.

Continue

Hands-On Lab: Verifying IP Parameters on Windows (GUI and CLI)

This hands-on lab covers checking a Windows PC's current IP configuration using both the graphical Network Connections interface and the command-line ipconfig utility, including releasing and renewing a DHCP-assigned address.

Continue

Hands-On Lab: Power over Ethernet (PoE) Basics

This hands-on lab covers verifying PoE capability on a switch port, checking how much power is being drawn by a connected device such as an IP phone or access point, and configuring power priority to protect critical devices during a power budget shortage.

Continue

Hands-On Lab: Configuring GRE Point-to-Point Tunnels

This hands-on lab configures a GRE tunnel between two routers across an intermediate transit network, allowing routing protocols and multicast traffic to pass between sites even when the underlying transport network would not normally support them directly.

Continue