VTP Mode = Client accepts updates?!

j4rt02

If I understand this right:

VTP Mode Client will not send VTP advertisements for changes locally, UNLESS it is first joined to a new domain AND has a higher revision number?

So, to add further to the higher database revision problems, it breaks the rules when it first joins a new VTP domain?

j4rt02

Here is a video that shows what I am talking about: Cisco Systems Inc. - VLAN Trunk Protocol

cisco_trooper

Yeah, don't add a VTP client to the network until you've cleared the revision number. Bad news.

j4rt02

This concept really tripped me up until I figured that out. Seriously, why did they make the once exception to the roles of server / client be so potentially harmful?

cisco_trooper

My advice is to just not even use it unless you've got some good people on your team. Rookies will screw it up even if they know about the theory. Everyone makes mistakes, and rookies make them often.

atorven

In big networks how else could you guard against such mess ups, set one server as transparent, manually back up the vlan.dat file?

NewInBussines

A device set in transparent mode allow vtp updates to pass, so no, the advice is to have multiple devices set as servers and reset revision number to zero on any device you add on the network by changing the domain name.
Hope I was clear.

Thanks

atorven

I already know what transparent mode does. Now, if you had a current server and you converted it to transparent mode, and if someone accidentally introduced a device with a higher revision and messed up your vlans it would not affect the transparent device, is this not a valid way to safe guard your vlans?

cisco_trooper

Just run them in transparent mode unless you have a real good reason not to.