VTP pruning takes effect several seconds after you enable it. VTP pruning does not prune traffic from VLANs that are pruning-ineligible. VLAN 1 and VLANs 1002 to 1005 are always pruning-ineligible; traffic from these VLANs cannot be pruned. Extended-range VLANs (VLAN IDs higher than 1005) are also pruning-ineligible. VTP and Device Stacks VTP configuration is the same in all members of a device stack. When the device stack is in VTP server or client mode, all devices in the stack carry the same VTP configuration. When VTP mode is transparent, the stack is not taking part in VTP. • When a device joins the stack, it inherits the VTP and VLAN properties of the active device.
• All VTP updates are carried across the stack. • When VTP mode is changed in a device in the stack, the other devices in the stack also change VTP mode, and the device VLAN database remains consistent. VTP version 3 functions the same on a standalone device or a stack except when the switch stack is the primary server for the VTP database. In this case, the MAC address of the active device is used as the primary server ID. If the active device reloads or is powered off, a new active device is elected. • If you do not configure the persistent MAC address feature, when the new active device is elected, it sends a takeover message with the new active MAC address as the primary server.
• If a persistent MAC address is configured, the new active device waits for the configured timer value. If the previous active device does not rejoin the stack during this time, then the new active device issues the takeover message. VTP Configuration Guidelines This section provides information about VTP configuration guidelines: VTP Configuration Requirements When you configure VTP, you must configure a trunk port so that the device can send and receive VTP advertisements to and from other devices in the domain. VTP versions 1 and 2 do not support private VLANs. VTP version 3 does support private VLANs. If you configure private VLANs, the device must be in VTP transparent mode.
When private VLANs are configured on the device, do not change the VTP mode from transparent to client or server mode. VTP Settings The VTP information is saved in the VTP VLAN database. When VTP mode is transparent, the VTP domain name and mode are also saved in the device running configuration file, and you can save it in the device startup configuration file by entering the copy running-config startup-config privileged EXEC command. You must use this command if you want to save VTP mode as transparent, even if the device resets. When you save VTP information in the device startup configuration file and reboot the device, the device configuration is selected as follows:
• 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 Configuring VTP VTP and Device Stacks VLAN Configuration Guide, Cisco IOS XE 17.16.x (Catalyst 9300 Switches) 7