if your vtp client has a higher revision number than the vtp server and you make a change on the server side then the client will not adjust to these changes and thus problems can occur.
e.g. if you create a new vlan on the server and put some ports into this vlan, you expect the vtp client switch to do the same creation process and might connect devices to it, as you think the vlan is now existing, but is actually not.
As said above, if that client in same vtp domain with higher revision number than the existing server then that switch will become as a VTP server and all vlans propigate to other clients.
Your thought is when the switch is in Transperant mode. A VTP transparent switch does not advertise its VLAN configuration and does not synchronize its VLAN configuration based on received advertisements.
Regarding the VTP configuration revision number, see the below explaination..
The configuration revision number is a 32-bit number that indicates the level of revision for a VTP packet. Each VTP device tracks the VTP configuration revision number that is assigned to it. Most of the VTP packets contain the VTP configuration revision number of the sender.
This information is used in order to determine whether the received information is more recent than the current version. Each time that you make a VLAN change in a VTP device, the configuration revision is incremented by one. In order to reset the configuration revision of a switch, change the VTP domain name, and then change the name back to the original name.
The VTP server switch must have the same configuration revision number, and must be the highest in the VTP domain.
Please rate all the helpfull posts. Regards, Naidu.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...