CCNA online course

VTP Modes Explained: Server, Client, and Transparent

Learn how Cisco VTP server, client, and transparent modes manage VLANs, synchronize VLAN databases, advertise changes, and forward VTP messages.

What Is VTP?

VLAN Trunking Protocol (VTP) is a Cisco protocol that distributes VLAN database information among switches in a VTP domain. A VLAN is a logical Layer 2 network segment, while the VLAN database is the collection of VLAN definitions known by a switch.

VTP advertisements are control messages that communicate VLAN database information. They can travel across operational trunk links, which are switch-to-switch links capable of carrying traffic for multiple VLANs.

A Cisco switch operates in one VTP mode at a time:

• Server mode: permits VLAN database changes and advertises those changes.
• Client mode: learns VLAN information from VTP updates but does not permit local VLAN database changes.
• Transparent mode: manages VLANs locally, does not synchronize its VLAN database from VTP advertisements, and forwards received advertisements.

The selected mode determines four important behaviors: whether the switch can modify local VLANs, whether it synchronizes VLAN information, whether it advertises its own VLAN changes, and whether it forwards advertisements received from another switch.

VTP Server Mode

VTP server mode is the traditional default VTP mode on Cisco switches. A server can create, modify, and delete VLANs in its local VLAN database.

When a server changes its VLAN database, it can generate a VTP advertisement for other eligible switches in the same VTP domain. Those switches can use the advertisement to update their VLAN information, provided that the VTP domain, version, and trunk connectivity are compatible.

Domain-wide VTP settings, including the VTP version and VTP pruning, can be configured on a server. VTP pruning is a feature that reduces unnecessary VLAN traffic on trunk links.

Switch# configure terminal
Switch(config)# vtp mode server

For example, in a three-switch design, an administrator can create VLAN 30 on the server. VTP clients in the same domain may then learn VLAN 30 from the server's advertisement.

VTP Client Mode

VTP client mode is intended for switches that receive their VLAN database information from VTP servers. A client processes applicable VTP advertisements and uses them to learn VLAN definitions.

A client cannot create, modify, or delete VLANs locally. If an administrator attempts local VLAN administration on a client, the operation is intentionally blocked because VLAN management is expected to occur on a server.

After processing received advertisements, a client can forward VTP advertisements over appropriate trunk links. Therefore, a client can help carry VTP information through a topology even though it does not originate its own VLAN database changes.

Switch# configure terminal
Switch(config)# vtp mode client

The key contrast is that a server is a source of permitted VLAN database changes, while a client consumes synchronized information and does not provide local VLAN administration.

VTP Transparent Mode

VTP transparent mode keeps VLAN configuration local to the switch. A transparent switch can create, change, and remove VLANs locally, but it does not synchronize its own VLAN database from received VTP advertisements.

Switch# configure terminal
Switch(config)# vtp mode transparent

Local VLAN changes on a transparent switch are not advertised as VTP database updates to other switches. This makes transparent mode a practical choice when an administrator wants independent VLAN management rather than VTP-based synchronization.

Transparent mode does not make VTP advertisements disappear. The switch forwards received VTP advertisements through appropriate trunk links, even though it does not use those advertisements to replace or synchronize its local VLAN database.

VTP Mode Comparison

Reading the Comparison Correctly

There are two separate traffic-flow questions:

1. Does the switch advertise its own VLAN database changes? Servers can do this. Transparent switches do not advertise their local changes, and clients cannot make the local changes that would be advertised.
2. Does the switch forward an advertisement received from another switch? Clients and transparent switches can forward received advertisements over suitable trunks. Forwarding a message does not mean that the switch originated the VLAN change or synchronized its own database.

VTP Mode Configuration Commands

Use global configuration mode to select the VTP mode. The command changes the operating mode of the switch; it does not by itself create VLANs or establish trunk connectivity.

Verifying VTP and the VLAN Database

After configuring a mode, verify the active mode and related VTP status:

Switch# show vtp status

This output is useful for checking the VTP operating mode, domain information, version-related settings, and other status details. Compare the output on switches that are expected to participate in the same VTP domain.

Use the following command to inspect VLANs known locally by the switch:

Switch# show vlan brief

For a synchronization demonstration, configure a consistent VTP domain and compatible VTP settings, connect the switches with functioning trunk links, create a VLAN on the intended server, and then use show vlan brief on the clients to check whether they learned it.

Practical Example: Server and Clients

Assume three switches belong to the same VTP domain and are connected by operational trunk links. One switch is the VTP server, and the other two are VTP clients.

1. On the server, enter global configuration mode and select server mode.
2. On each access switch, select client mode.
3. On the server, create a new VLAN, such as VLAN 30.
4. Use show vlan brief on the server to confirm the local VLAN.
5. Use show vtp status and show vlan brief on the clients to verify their mode and learned VLAN information.
6. Attempting to create VLAN 30 locally on a client should fail because client mode prevents local VLAN database modification.

This design centralizes VLAN administration: the server changes the database, while clients receive and relay applicable VTP information.

Practical Example: Transparent VLAN Isolation

Suppose a switch is placed between VTP-participating switches but must be managed independently.

1. Configure the switch with vtp mode transparent.
2. Create a VLAN locally on the transparent switch.
3. Use show vlan brief to confirm that the VLAN exists locally.
4. Check neighboring VTP clients. The locally created VLAN should not appear there as a result of VTP synchronization.
5. Verify that trunk links remain operational. VTP advertisements received from another switch can still traverse the transparent switch.

The result is a local VLAN-management boundary without automatically stopping every VTP frame from crossing the switch.

Choosing a VTP Mode

Troubleshooting VTP Modes

A Switch Cannot Create a VLAN Locally

Likely cause: The switch is operating in VTP client mode.

1. Run show vtp status and identify the active mode.
2. Determine whether the switch is intended to receive centrally managed VLANs.
3. If central management is intended, create the VLAN on the appropriate VTP server.
4. If local administration is intended, change to a mode that permits local VLAN administration, such as transparent mode, according to the network design.

A Transparent VLAN Does Not Appear on Other Switches

Likely cause: Transparent mode keeps locally created VLAN changes local and does not advertise them as VTP database updates.

Confirm transparent mode with show vtp status and compare show vlan brief on the local and neighboring switches. If the VLAN must be shared, create it on the designated VTP server or configure the VLAN independently on each switch where local management is intended.

A Transparent Switch Still Passes VTP Advertisements

This is expected behavior. Transparent mode prevents the switch from participating in VLAN database synchronization, but received VTP advertisements can still be forwarded over operational trunk links.

Confirm the mode with show vtp status and verify trunk operation. If advertisements must not propagate through the topology, use a design and configuration that controls VTP propagation rather than assuming transparent mode drops every VTP frame.

A Client Does Not Learn Expected VLANs

Possible causes include a VTP domain mismatch, incompatible VTP settings, missing or nonoperational trunk connectivity, or the absence of a valid server advertisement.

1. Compare VTP domain and version information with show vtp status.
2. Verify trunk status between the switches.
3. Confirm that the expected VLAN exists on the intended VTP server.
4. Correct the VTP and trunk configuration so the client can receive applicable advertisements.

Exam-Relevant Notes

• A switch has one active VTP mode at a time.
• Server mode permits VLAN creation, modification, and deletion and can advertise those changes.
• Client mode learns VLAN information from VTP and does not permit local VLAN database changes.
• Transparent mode permits local VLAN changes but does not synchronize its VLAN database from received advertisements.
• Transparent switches forward received VTP advertisements; they do not necessarily remove VTP messages from the topology.
• Forwarding an advertisement received from another switch is not the same as advertising the transparent switch's own local VLAN changes.
• VTP synchronization depends on compatible VTP settings and working trunk connectivity.

Summary

VTP distributes VLAN database information within a VTP domain. Server mode is used for permitted centralized VLAN changes and advertisements. Client mode receives and processes VTP updates but blocks local VLAN database changes. Transparent mode keeps VLAN administration local, does not synchronize from VTP advertisements, and still forwards advertisements received from other switches. Select the mode according to whether VLAN management should be centralized, delegated through synchronization, or kept independent.