vtp cfg change not getting propagated

Whether these 2 devices are connected directly or how are these devices connected ?? Please make sure that the links are in trunk mode for the vlans to be propogated.

~ Siva

lfnetwork> Added a couple vlans on the 6500 that weren't updated on the 3750. I

yes the stack is trunked to the 6500 on 1/0/49 and 4/0/49.

ussfof-452-sw3750-1#sh int trunk

Port Mode Encapsulation Status Native vlan Gi1/0/48 on 802.1q trunking 1 Gi1/0/49 desirable 802.1q trunking 1 Gi4/0/49 desirable 802.1q trunking 1

Port Vlans allowed on trunk Gi1/0/48 1,9,13 Gi1/0/49 1,3-4,9,13-14,100-101,200 Gi4/0/49 1,3-4,9,13-14,100-101,200

Port Vlans allowed and active in management domain Gi1/0/48 1,9,13 Gi1/0/49 1,3-4,9,13,100 Gi4/0/49 1,3-4,9,13,100

Port Vlans in spanning tree forwarding state and not pruned Gi1/0/48 1,9,13 Gi1/0/49 1,3-4,9,13,100 Gi4/0/49 none

Siva wrote:

ok It should work then, I donno why is it not getting updated which is evident from the output of Config revision number and no. of vlans....Have you configured any passwords for the vtp domain...if so, make sure that all the switches configured with the same password.

~ Siva

lfnetwork> yes the stack is trunked to the 6500 on 1/0/49 and 4/0/49.

How many switches are in your network?

Are the other switches all receiving the correct number of VLANS?

On the 3750 you many have a space after you domain name ussfof. May check that.

On the show vtp stat your Number of existing VLANs should be the same 24 if client and server.

try "deb sw-vlan vtp". otherwise it's just blind guessing

eventually may help. my predecessors already gave you a few hints. password for the vtp-domain, not allowing vlan 1. sounds stupid, but try adding a vlan, applying the change, and removing the vlan again. worked for me.

greetings \\cd

Thanks for this suggestion. I removed a vlan from the server switch and saw the vtp packet hit the client switch with the latest vlan info, but still the vtp config rev didn't increment and the vlan info remained unchanged on the client. I'm mystified. If all else fails I plan to reboot the master switch after hours.