We have an established network on VTP domain say - CORP where we have a core switch performing the VLAN/VTP updates.
Someone plugs in a rogue switch to the network - say configured for a different VTP domain TEST, or maybe just a default undefined VTP domain. If the VTP Revision number of the rogue switch is higher than the Core Switch(CORP) - can the rogue switch wipe out the VLANs on CORP ?
My understanding from VTP is that the server and client need to be on the same domain for updates to occur flowing from the Server to the Client. But, also read somewhere that VTP revision is more something that needs to be a watch out for.
In question would be a CAT 6506 being the Server, and the roque being any switch - even a Cisco 2940 which we might typically user for conference rooms.
I thought they had to be in the same domain then if the new switch had a higher revision number it would overwrite the vtp database even if it is a client . the way to avoid this is to give the new switch a different domain name than the current then change it back to the right one and this will set the revision number back to 0.
A switch if not configured for any vtp domain, defaulting to null, when plugged into a life network, it will join the domain that it learns about via vtp.
Also, a switch in vtp client mode, eventhough is not possible to configure vlan info on it, but will still propagate it's vlan d/b info via vtp. Therefore, if a client has a higher revision number then the one in the life network, therefore it will still wipe out the current VLANs in the life network replacing it with whatever that it has in it's own database.
There are 3 ways to avoid this:
1. Configure vtp mode of switch fr client to transparent, then switch it back to client mode. This will reset the vtp rev. back to 0.
2. Configure it to a different vtp domain, then switch it back. This will also reset the vtp rev. back to 0.
3. Configure ur switch uplink as an access port. VTP info will only propagate through trunks.
In my Experience with the VTP things, I have also noticed that if you are introducing any switch in a VTP domain with a differnt domain name, the new switch will still join the VTP domain and it will be overwritten with the VTP config of the domain that it is joining and will have all the vlans and config revision number.
As posted above that if a client/server switch that you are introducing in your VTP domain with high revision number, it will still overwrite all the VTP info.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...