The configuration of a VLAN includes the VLAN number, name and a few more parameters which will be analysed further on.
This information is then stored on each switch's NVRAM and any VLAN changes made to any switch must again be replicated manually on all switches.
A typical setup involves at least one switch configured as a VTP Server, and multiple switches configured as VTP Clients.
Any change in the VLAN database will trigger an update from the VTP Server towards all VTP clients so they can update their database.
Lastly, be informed that these VTP updates will only traverse Trunk links.
It’s been around for a while but until recent IOS versions it wasn’t supported on Cisco Catalyst Switches.
Here are some of the new additions to VTP version 3: I’ll walk you through each of those and show you how to configure VTP version 3.
To help keep things simple and in order to avoid confusion, we will work with the first version of the VTP protocol - VTP v1, covering more than 90% of networks.
Below you'll find the 3 modes the VTP protocol can operate on any switch throughout the network: Each mode has been designed to cover specific network setups and needs, as we are about to see, but for now, we need to understand the purpose of each mode and the following network diagram will help us do exactly that.
Just like the VLAN feature, we require a primary server that will create the MST configuration.
You can use the same switch for this role or you can pick another one.
In an earlier lesson I explained the basics of VTP (version 1 and 2).
The main goal of VTP version 3 remains to synchronize VLANs but it has a number for extras.
This means that you must ensure that all switches connect to the network backbone via Trunk links, otherwise no VTP updates will get to your switches.