Vtp Version 3 Databases - Cisco WS-C2948G-GE-TX Configuration Manual

Chapter 9 Configuring VTP
•
•
Primary Server
The primary server can initiate or change the VTP configuration. To reach the primary server state, you
must issue a successful takeover from the switch. The takeover is propagated to the entire domain. All
other potential primary servers in the domain resign to secondary server mode to ensure that there is only
one primary server in the VTP domain.
You only need the primary server when the VTP configuration for any instance needs to be modified. A
VTP domain can operate with no active primary server because the secondary servers use the
configuration over reloads. The primary server state is exited due to the following reasons:
•
•
•
•
•
Transparent and VTP Off Modes
In VTP version 3, the transparent mode is specific to the instance. The off mode in VTP version 3 is
similar to the previous VTP versions and is not specific to an instance. In both modes, you are allowed
to configure locally the features that VTP is controlling. In addition, this feature configuration appears
in the running configuration (if applicable). The feature stores its local configuration in the same
NVRAM block that is used by VTP. All NVRAM handling for the feature happens through VTP whether
or not the switch is transparent to the feature. In VTP transparent mode, all VTP messages that are
received by the switch are still flooded. In VTP off mode, the VTP messages are dropped on the trunks.

VTP Version 3 Databases

VTP version 1 and VTP version 2 are tied to VLAN information. VTP version 3 is designed to distribute
any kind of configuration (referred to as a database) over a VTP domain.
Note In software release 8.1(1), the only supported database propagation is for the VLAN database.
VTP version 3 databases are described in the following sections:
•
•
•
•
Catalyst 4500 Series, Catalyst 2948G, Catalyst 2948G-GE-TX, and Catalyst 2980G Switches Software Configuration Guide—Release 8.2GLX
78-15908-01
A VTP server reverts to client mode if it cannot store the configuration in NVRAM.
A VTP version 3 secondary server can issue a takeover to become a primary server.
A switch reload.
A high-availability switchover between the active and redundant supervisor engines.
A takeover from another server.
A change in the mode configuration.
Any VTP domain configuration change (such as version, domain name, or domain password).
Valid Databases, page 9-20
Database Revision Number, page 9-20
Interaction with VTP Version 1 and VTP Version 2, page 9-21
Limitations, page 9-21
Understanding How VTP Version 3 Works
9-19