VTP 3 updates config revision but vlans don't appear
-
This is certainly bizarre, The "normal" issues like password mismatches, trunk problems, and domain mismatches do not appear to apply. Is the problem switch running the same IOS code release? I wonder what happens if we drop all switches back to VTP Version 2?
-
I went with version 3 because it allows me to hide the password. Version 2 doesnt support that. But, as a test I can certainly try. I thought there was a restriction on going back to version two from version 3. Perhaps not. I’ll give it a go.
-
The three switches I have been using for this testing are running exactly the same ios version as seen below:
The Server is running...
C1.1#show ver
Cisco IOS Software, C3560 Software (C3560-IPSERVICESK9-M), Version 12.2(55)SE12, RELEASE SOFTWARE (fc2)The client that is working fine is running...
C1.89#show ver
Cisco IOS Software, C3560 Software (C3560-IPSERVICESK9-M), Version 12.2(55)SE12, RELEASE SOFTWARE (fc2)The client with the issues is running...
E2.128#show ver
Cisco IOS Software, C3560 Software (C3560-IPSERVICESK9-M), Version 12.2(55)SE12, RELEASE SOFTWARE (fc2)I tried dropping the switches back to version 2 and nothing seemed to work. I suspect this could be because there are a couple of switches between the server and the two clients I'm working with.... I can't be sure. I'll play with it a bit more tomorrow. I don't have a network map and don't want to recreate it tonight.
-
Great idea to find out if there are non VTP switches in between the ones you listed!
-
They are all set to the same VTP version 3 settings. They are all properly responding with the sole exception of the problem switch. I just wasn’t sure if having them in the chain would prevent version 2 BPDUs from properly propagating along the version 3 chain.
-
I changed the problem switch as well as the one adjacent it to version 2. I set the adjacent switch to server mode and they seemed to operate properly. I could add/remove vlans on the server and the problem switch reacted properly to the changes. I changed them back to version 3 and now they won't talk to me. I suspect I lost a vlan or two on each. I'm going to get a console cable and fix the problem. Different building and it's 32 deg and nasty outside. Yuck!
-
Well, you're gonna love this one. I got a wild hair and decided to change the problem switch to server mode. When I did, it started working properly. I added a vlan to the primary server and it showed up on the problem switch. I then removed the vlan and it disappeared fro the problem switch. Now for the weird part... I changed it back to client mode and it still works properly. I added and removed a couple of vlans on the primary server to convince myself that it is working and the changes were always echoed on the problem switch.
I have no idea why this worked but it did. So I'd say my problem is solved.
-
Great way to work through the problem! I just found the same solution online:
https://castroaa.blogspot.com/2016/10/troubleshooting-vtp-version-3.html
-
ROFL.. .timely. <g>
I can't find how to mark this as solved??? -
It's ok it didn't post as question....I'll try and change that when I figure out how to get posted as question! Glad you're a member!
Just changed, it... so if you look in the lower right corner...you'll see
Topic Tools
. that 's a drop down list that will allow you to mark this as solved.