VMware ESXi and vSphere Cluster Management

VTP Modes Explained: Server, Client, and Transparent

Learn how Cisco VTP server, client, and transparent modes handle VLAN changes, advertisements, synchronization, and local VLAN administration.

VLAN Trunking Protocol (VTP) is a Cisco protocol that distributes VLAN database information among switches in the same VTP domain. A VLAN database is the collection of VLAN definitions stored by a switch. VTP behavior depends partly on the switch's operating mode: server, client, or transparent.

VTP advertisements carry VLAN-related updates across eligible trunk links. A trunk link is a switch-to-switch connection that can carry traffic and control information for multiple VLANs. The receiving switch may apply, ignore, or forward an advertisement depending on its VTP mode.

How VTP Distributes VLAN Information

A VTP domain is a logical group of switches that share VTP information and configuration context. When an authorized switch changes a VLAN database, VTP can advertise that change to other applicable switches in the domain.

For example, an administrator can create VLAN 30 on a VTP server. The server advertises the VLAN change over eligible trunks. VTP client switches in the same domain process the advertisement and add the VLAN definition to their local VLAN databases. A transparent switch can forward the advertisement, but it does not use the advertisement to synchronize its own database.

The Three VTP Modes

Cisco VTP provides three commonly taught operating modes:

• Server mode: Permits local VLAN administration and advertises local VLAN changes.
• Client mode: Receives and uses VTP VLAN updates but does not permit local VLAN database administration.
• Transparent mode: Maintains a locally managed VLAN database, does not synchronize it from received VTP advertisements, and forwards received advertisements.

VTP Server Mode

Server mode is the default VTP mode on Cisco switches in the configuration model covered here. A switch in server mode can create, modify, and delete VLANs locally.

When a VLAN change is made on a server, the server advertises the change to other applicable switches in the VTP domain. Client switches can then synchronize their VLAN information from that advertisement. A server also processes relevant advertisements received from other switches.

Domain-wide VTP settings, including the VTP version and VTP pruning, can be configured from a VTP server. VTP version identifies the protocol version used for VTP operation. VTP pruning is a feature that can reduce unnecessary VLAN traffic on trunk links.

Selecting Server Mode

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

Example: Central VLAN Administration

Suppose a distribution switch is authorized to manage VLANs and several access switches are VTP clients in the same domain. The administrator creates VLAN 30 on the distribution switch. The server advertises the new VLAN, and participating clients receive the VLAN definition without an administrator creating it separately on each client.

Switch(config)# vlan 30
Switch(config-vlan)# name Engineering

The VLAN becomes available in the server's local database, and the server advertises the change according to the VTP domain and trunk connectivity.

VTP Client Mode

A switch in client mode cannot locally create, modify, or delete VLANs in its VLAN database. Instead, it processes received VTP advertisements and synchronizes its VLAN information from them.

A client also forwards received VTP updates through eligible connections. This allows VTP information to continue through a topology rather than stopping at the client. However, the client does not originate advertisements for local VLAN changes because local VLAN database administration is not permitted.

Selecting Client Mode

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

Why a Local VLAN Edit Fails

If an administrator attempts to create or remove a VLAN directly on a client, the operation is unavailable because client mode prevents local VLAN database changes. The correct administrative action is usually to make the change on an authorized VTP server.

Client mode is appropriate for access switches that should receive centrally managed VLAN information but should not have independent authority to change the shared VLAN database.

VTP Transparent Mode

A switch in transparent mode does not synchronize its VLAN database from received VTP advertisements. It can create, modify, and delete VLANs locally, but those changes remain local to the transparent switch.

A transparent switch does not advertise its own local VLAN database changes to the VTP domain. It does, however, forward VTP advertisements received from other switches. Forwarding and processing are different actions: forwarding passes the message onward, while processing would apply the message to the local VLAN database.

Selecting Transparent Mode

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

Example: Keeping VLAN Changes Local

Assume a transparent switch is connected between other VTP-connected switches. An administrator creates VLAN 50 on the transparent switch:

Switch(config)# vlan 50
Switch(config-vlan)# name Local-Services

VLAN 50 exists in that switch's local VLAN database. It is not automatically added to neighboring VTP switches because transparent mode does not advertise the local VLAN change through VTP.

If the transparent switch receives an advertisement for VLAN 30 from another switch, it forwards that advertisement but does not add VLAN 30 to its own database as a result of the advertisement.

Using Transparent Mode to Avoid VTP-Driven VLAN Changes

In the configuration model covered here, VTP is not fully disabled through a separate disable command. Transparent mode is used when a switch must avoid VTP VLAN database synchronization while still allowing VTP advertisements to pass through it.

This makes transparent mode useful when VLANs are managed independently on a switch or when received VTP changes must not overwrite the switch's local VLAN information. It does not mean that the switch stops forwarding VTP control traffic.

Mode Configuration Commands

Choosing the Correct VTP Mode

Choose Server Mode When

• The switch is authorized to manage a shared VLAN database.
• Administrators need to create, modify, or delete VLANs centrally.
• VLAN changes should be advertised to participating switches in the VTP domain.
• Domain-wide VTP settings such as VTP version or VTP pruning must be configured from that switch.

Choose Client Mode When

• The switch should receive centrally managed VLAN definitions.
• Local administrators should not change the shared VLAN database.
• Multiple access switches should use VLAN information distributed by an authorized server.

Choose Transparent Mode When

• The switch requires an independently managed VLAN database.
• Local VLAN changes must remain on that switch.
• Received VTP advertisements must not alter the local VLAN database.
• The switch should still forward VTP advertisements to other connected switches.

Remember that a VLAN created on a transparent switch is not automatically available on neighboring VTP switches. If the VLAN is intended to be shared through VTP, create it on the authorized VTP server instead, or configure the VLAN independently wherever the design requires it.

End-to-End Mode Example

Consider a network with a core or distribution switch responsible for VLAN policy, several access switches with no local VLAN authority, and one independently managed switch.

1. Assign server mode to the VLAN-management switch.
2. Assign client mode to the centrally controlled access switches.
3. Assign transparent mode to the independently managed switch.
4. Connect the switches with eligible trunk links so VTP advertisements can travel where the topology permits.
5. Create shared VLANs on the server and local-only VLANs on the transparent switch as required by the design.

In this arrangement, server-originated changes can synchronize the clients. The transparent switch can forward those advertisements without applying them locally, while its own VLAN changes remain isolated from the shared VTP database.

Troubleshooting VTP Mode Behavior

Client Cannot Create, Modify, or Delete a VLAN

Likely cause: This is the expected restriction of client mode.

Resolution: Make the VLAN change on an authorized VTP server, or select a mode that permits local VLAN administration if independent management is intentional.

A VLAN Created on One Switch Does Not Appear on Other Switches

Likely cause: The VLAN may have been created on a transparent switch. Transparent-mode changes are not advertised through VTP.

Resolution: Create the shared VLAN on the VTP server, or confirm that the topology intentionally uses independent local VLAN databases.

Transparent Switch Does Not Add VLANs From Advertisements

Likely cause: Transparent mode forwards advertisements but does not synchronize its local VLAN database from them.

Resolution: This is expected behavior. Use client or server mode only if the switch must synchronize its VLAN database through VTP.

VTP Advertisements Still Traverse a Switch in Transparent Mode

Likely cause: Transparent mode prevents synchronization but does not prevent forwarding of received VTP advertisements.

Resolution: Distinguish between refusing to apply a control message locally and refusing to forward that message. Transparent mode does the former, not the latter.

Key Points to Remember

• VTP distributes VLAN database information within a VTP domain through advertisements carried over eligible trunk links.
• Server mode permits local VLAN creation, modification, and deletion and advertises those changes.
• Client mode receives, synchronizes, and forwards VTP information but does not permit local VLAN database edits.
• Transparent mode permits local VLAN administration, does not synchronize from received advertisements, and forwards those advertisements.
• A local VLAN created on a transparent switch is not automatically learned by neighboring VTP switches.
• Use the mode that matches the switch's administrative responsibility: shared VLAN authority, centrally controlled client, or independent local management.

For a concise reference, return to VTP modes explained.