not performed when new information is obtained from a VTP message or when information is read from NVRAM. If the MD5 digest on a received VTP message is correct, its information is accepted. VTP Version 3 VTP version 3 supports these features that are not supported in version 1 or version 2: • Enhanced authentication—You can configure the authentication as hidden or secret . When hidden , the secret key from the password string is saved in the VLAN database file, but it does not appear in plain text in the configuration. Instead, the key associated with the password is saved in hexadecimal format in the running configuration.
You must reenter the password if you enter a takeover command in the domain. When you enter the secret keyword, you can directly configure the password secret key. • Support for extended range VLAN (VLANs 1006 to 4094) database propagation—VTP versions 1 and 2 propagate only VLANs 1 to 1005. VTP pruning still applies only to VLANs 1 to 1005, and VLANs 1002 to 1005 are still reserved and cannot be modified. Note • Private VLAN support. • Support for any database in a domain—In addition to propagating VTP information, version 3 can propagate Multiple Spanning Tree (MST) protocol database information. A separate instance of the VTP protocol runs for each application that uses VTP.
• VTP primary server and VTP secondary servers—A VTP primary server updates the database information and sends updates that are honored by all devices in the system. A VTP secondary server can only back up the updated VTP configurations received from the primary server to its NVRAM. By default, all devices come up as secondary servers. You can enter the vtp primary privileged EXEC command to specify a primary server. Primary server status is only needed for database updates when the administrator issues a takeover message in the domain. You can have a working VTP domain without any primary servers.
Primary server status is lost if the device reloads, after a switchover, or domain parameters change, even when a password is configured on the device. • With VTP version 3 in server mode the VLAN configuration is saved into vlan.dat file. VLAN configuration is not saved in NVRAM as is the case in the transparent mode. While taking a backup of the switch configuration, you also have to take a backup of the vlan.dat file. Note VTP versions 1 and 2 are capable of publishing only standard VLANs (VLANs 1 to 1001) and extended VLANs (VLANs 1006 to 4094) are stored locally in the flash drive or the running configuration.
VTP version 3 is capable of publishing extended VLANs to the entire VTP domain and extended VLANs are not stored locally. Configuring VTP VTP Version 3 VLAN Configuration Guide, Cisco IOS XE 17.16.x (Catalyst 9300 Switches) 5