No actually its good to have 2 so if one goes south you have a backup . Just make sure when you insert the vtp revision number on the new one is lower than the currently installed so the vtp database is not overwritten .
If this is indeed a "NEW" switch, out of the box and has never taken part in a VTP domain previously, then the configuration revision number should be set to zero. You can check this with the "show vtp status" command. If this is the case then add it to your VTP domain by configuring the VTP domain on the switch. Make it a client and configure your password and you should be good to go.
Also spare a thought for how your spanning tree configuration may change with the addition of a new switch to the network.
One more note... make sure you check your VTP status on a switch before you connect it to your network.
This is the easiest way to bring every bit of traffic on your network to a screeching halt. If your VTP server's config gets overwritten because a 'new' switch has a higher revision # somehow (you were testing config changes perhaps?), you will get a number of phone calls immediately!
I like the idea of changing the VTP domain that somebody mentioned earlier...
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...