I have 4 switches. One VTP-Server and Three VTP-CLients. Now i want to move these three vtp clients so another location and will introduce a new switch there as vtp server.What are the best possibilites. I want to retain the VLAN info to the new location and want all my clients to sync there info with the new switch which eventually be vtp server? so my new switch also has all the vlans in it and then i can promote it as vtp server after updating its vlan database and revision number.
So you are moving 3 VTP clients and you are installing a new switch in the same location which you want to be a VTP server. And you want this VTP server to start off with the vlans that exist on the VTP client ?.
1) Promote one of the VTP clients to be a VTP server.
2) Set the VTP mode on the new switch to be VTP transparent then set it to be a VTP client with the existing VTP domain name and password if you are using one.
3) Connect the new switch on a trunk link to the one of the existing switches and make sure the vlan database has been synched.
4) Promote the new switch to be a VTP server.
5) Demote the temporary VTP server back to a VTP client.
I'll play devils advocate here . How long does it really take to create the vlans on a new server ? Write down the current ones that the server has and just create them on the new server , this won't take more than 10 minutes . A server only propgates the vlans that are created . It doesn't keep track of what ports are in what vlan etc on any new clients . Temporaily set the clients to transparent mode and temporaily give it a different domain name then just create the new vlans on your new server , create your new domain name , do the same on the clients and change them back from transparent to clients. All the config revision numbers should get reset and the server willl just propagate the vlans to your switches . Jons way will work too . Myself I would just create the vlans on the server , takes no time at all . Change the vtp domain to null and back to the correct one to reset the vtp config revision number and let the server propagate the vlans as normal . A number of ways to do this , just use whatever you feel comfortable with .
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...