We currently have 1 VTP domain where all our network devices are configured.
We now want to join another VTP domain to this domain and I wander what the best approach will be to do this.
1. I can configure all the VLAN ID's at my own VTP server ( there are no overlapping ID's ) and configure the devices from the other domain as clients ( but what happens to the VLAN configurations made on the old VTP server ? ).
2. connect our 2 networks
or is it better to change only the VTP domain on the other VTP server ( the same as ours now ) and then connect the networks together ( what will happen with the VTP/vlan configuration of both servers, will they be added or will the sever with the highest revision number just copy his database to the other server and probably delete the current VTP/VLAN configuration ?
As soon as the VTP server you want to get rid of will be moved in the other domain, its config revision number will be 0 (The change of domain name will reset the config revision number). Its vlan database will be erased by the VTP server of the new domain. All the vlans of the old VTP domain will be lost.
I would proceed in this way (VTP A is the VTP you want to keep, VTP B is the VTP you want to merge into VTP A):
1) configure all the VLANs of VTP B in VTP A
2) reconfigure all VTP B's switches as VTP A client.
As long as you have configured every vlans of VTP B into VTP A, when you will change the domain name of one VTP B's switch, this switch will replace its vlan database by the VTP A's vlan database. Since you have configured all VTP B's vlan in VTP A you wont loose any vlans.
The vlan interfaces on the L3 device won't noticed the VTP change.
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 custome...