Cisco vtp client not updating
Hello, I am confused about VTP terminology can you help?
XX.64.199 at 12-26-13 interface Fast Ethernet1/0/47 description Crossover to 9.12 switchport trunk encapsulation dot1q switchport mode trunk sh int fa1/0/47 trunk Port Mode Encapsulation Status Native vlan Fa1/0/47 on 802.1q trunking 1 Port Vlans allowed on trunk Fa1/0/47 1-4094 Port Vlans allowed and active in management domain Fa1/0/47 1-2,5-6,8-9,11,17,22,25-27,30-31,34-35,38,43,46-47,49-50,52,55,57,60,62,68,71-72,74,77-78,93-95,105,112,118,202,227-229,233-234,262,520,907 Port Vlans in spanning tree forwarding state and not pruned Fa1/0/47 1-2,5-6,8-9,11,17,22,25-27,30-31,34-35,38,43,46-47,49-50,52,55,57,60,62,68,71-72,74,77-78,93-95,105,112,118,202,227-229,233-234,262,520,907 It turns out that the Client switches had a VTP Password set.
I can probabaly repost the results tonight but I compared the results last night while I was working on this.
I did not originally configure these switches and I didn't think there was a vtp password.
If you have a unique situation where your client switch has a higher version # than the server, you either have to increase the version on the server (through multiple changes in the DB), or reset the client's version count by switching the VTP to another value, and then back to match the existing server, which will click the client's version to 0, making it request the newest DB from the server.
I always do both (change domain name and vtp mode).
Two of the switches pulled in the current configuration.
Does anyone know why the vtp client SW are not updating their vlan database even with the correct config pasted in?
You can't manually force updates because VTP configs are pushed based on the highest current VLAN database revision number.