I have a Cisco 4006 Switch which is working as a VTP Server in my network and serving almost more than 40 VTP Client switches in my network. Due to hardware issue, I have to replace this switch with 2950 Switch on temporary basis but for at least two weeks.
Now is this possible that if i configure the 2950 as VTP Server with the same configuration as of Cisco 4006 than the switches those are working as VTP Clients will update their VTP information via this new 2950 switch?
Do I need to perform any additional thing in this regard?
Switches will prefer VTP information that has a higher revision number than what they have already. If you install a new switch into the network, there is a good possibility that the revision number of that switch will be less than that of the existing switches. If that is the case, the VLAN configuration of the new switch will be overwritten by that of the existing switches, even if the new switch is a VTP server and the rest of the switches are VTP clients.
While there may be other ways of doing this, one method that could work is for you to do the following:
- determine the current revision level of the client switches using 'show vtp status'
- artificially increase the revision number of the new 2950 switch before installing it into the network. One way to do this is to simply make changes to the VLAN database until the revision number is higher
- then, introduce the 2950 into the network
Hope that helps - pls do rate the post if it does.
are you sure a switch configured as VTP server will be updated by VTP clients, if the revision number is lower? My idea was, that only servers send VTP updates, and clients just receive (or forward) them. Removing the 4006 first would leave no server and thus no switch with current VLAN information in the vlan.dat file. I would not like to run a network under this condition.
So the 2950 could be added to the network as VTP client (clears the vlan.dat), then converted to server, while the 4006 is still in place. The 2950 should then be updated by the 4006 to the latest revision and the 4006 could be removed (assuming it is still alive now).
Check the revision on the 4006 and the 2950 before and after adding it with "show vtp status".
AFAIK, there is a limit of 64 VLANs on a 2950 switch. If that limit is reached, the switch changes to VTP transparent mode. So, before introducing the 2950 as a VTP server switch, make sure that the VLAN limitation does not give you problems...
There is no need to configure switch as client and then turn it on to be a server again. Just make sure the revision number on that switch is lower then on "live" server. Then attach 2950 into the network, make sure it has recieved updates (it will if the domain name match or wasn't change from NULL even though it's a server too), detach 4006, voila.
The switch config will be overwritten by the clients if the revision number on the clients is higher than the new 2950 . Also as best practice it is advisable to have 2 servers in your network thus avoiding problems like this . If you have a larger switch still in the network you might be able to change that to a server temporarily which should have the up to date revision number.
change the mode to transparent and then back to server or change the vtp domain to something different to the current domain and then back to the original domain. This forces it to a revision # of zero.
Now let me summarize what can be the possible workarounds, please verify
1. If i change the revision number of 2950 to the higher number than current VTP revision number and introduce it as a server into the network, the switches will not update themselves from it or in other words this workaround may lead to some mis-configuration especially if we donot have any Server available on the Network as VTP Server.
2. The Workaround which is applicable as far as i understand. Make 2950 as VTP Server, Change its mode to transparent or change the name of vtp domain so that its revision number will become zero, than convert this switch to the Server mode. Once it will update its Database, we can remove the 4006 happily. The Clients will update themselves only with the 2950 Switch lateron for any update.
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...