•
If the VTP mode is transparent in the startup configuration and the VLAN database and the VTP domain
name from the VLAN database matches that in the startup configuration file, the VLAN database is
ignored (cleared), and the VTP and VLAN configurations in the startup configuration file are used. The
VLAN database revision number remains unchanged in the VLAN database.
•
If the VTP mode or domain name in the startup configuration do not match the VLAN database, the
domain name and VTP mode and configuration for VLAN IDs 1 to 1005 use the VLAN database
information.
The vtp file filename cannot be used to load a new database; it renames only the file in which the existing
database is stored.
Follow these guidelines when configuring a VTP domain name:
•
The device is in the no-management-domain state until you configure a domain name. While in the
no-management-domain state, the device does not send any VTP advertisements even if changes occur
to the local VLAN configuration. The device leaves the no-management-domain state after it receives
the first VTP summary packet on any port that is trunking or after you configure a domain name by
using the vtp domain command. If the device receives its domain from a summary packet, it resets its
configuration revision number to 0. After the device leaves the no-management-domain state, it cannot
be configured to reenter it until you clear the NVRAM and reload the software.
•
Domain names are case-sensitive.
•
After you configure a domain name, it cannot be removed. You can only reassign it to a different domain.
Follow these guidelines when setting VTP mode:
•
The no vtp mode command returns the device to VTP server mode.
•
The vtp mode server command is the same as no vtp mode except that it does not return an error if the
device is not in client or transparent mode.
•
If the receiving device is in client mode, the client device changes its configuration to duplicate the
configuration of the server. If you have devices in client mode, be sure to make all VTP or VLAN
configuration changes on a device in server mode, as it has a higher VTP configuration revision number.
If the receiving device is in server mode or transparent mode, the device configuration is not changed.
•
A device in transparent mode does not participate in VTP. If you make VTP or VLAN configuration
changes on a device in transparent mode, the changes are not propagated to other devices in the network.
•
If you change the VTP or VLAN configuration on a device that is in server mode, that change is
propagated to all the devices in the same VTP domain.
•
The vtp mode transparent command disables VTP from the domain but does not remove the domain
from the device.
•
In VTP Versions 1 and 2, the VTP mode must be transparent for you to add extended-range VLANs or
for VTP and VLAN information to be saved in the running configuration file. VTP supports
extended-range VLANs in client and server mode and saves them in the VLAN database.
•
With VTP Versions 1 and 2, if extended-range VLANs are configured on the device and you attempt
to set the VTP mode to server or client, you receive an error message, and the configuration is not
allowed. Changing VTP mode is allowed with extended VLANs in VTP Version 3.
•
The VTP mode must be transparent for you to add extended-range VLANs or for VTP and VLAN
information to be saved in the running configuration file.
Command Reference, Cisco IOS XE Everest 16.5.1a (Catalyst 3650 Switches)
1068
vtp (global configuration)
To Next Page
Loading...
Need help?
General
