Hello Rene,
VTP transparent is also able to overwrite the VTP server and client when its revision number is higher?
Hello Danilo
A switch in the transparent VTP mode will not overwrite the VLAN database on VTP servers or clients, even if its own revision number is higher. Switches in transparent mode do not participate in VTP at all. If they receive a VTP message, they will simply relay it without making any changes to their own VLAN database or any changes to the values found within the message itself.
Indeed, the revision number on a transparent switch is always set to 0 and does not change.
So a switch in VTP transparent mode simply forwards advertisements without applying them to its own configuration, and it wonât overwrite a VTPâenabled domainâs VLAN database.
I hope this has been helpful!
Laz
Hello Lazarus,
Thank you so much!
I really appreciate it! 
Regards,
Danilo
1 Like
Hey,
Canât we added all the switches to a domain, then create the VLANs on one switch, and then disable the VTP?
Sir Renemolenaar
I did it this lab with my packa tracer
little different for what i did it considering what is the introduction to vtp is
I do not know why, may be because of different switch.
please sir tell me
Hello Pamod
Yes, you absolutely can add all switches to a VTP domain, create the VLANs on one switch (typically a VTP server), let the advertisements propagate, and then disable VTP afterward. This is a valid approach to avoid ongoing VTP synchronization issues, especially in networks with dozens or hundreds of VLANs. This will definitely help you to minimize configuration time.
You should however keep in mind that there will be no ongoing synchronization once this is done. If you need to add or remove a VLAN, you need to go into every switch and make the change. In this case, it may be worth looking into other automation tools like Ansible/Python scripting in order to maintain VLAN consistency across your switches.
I hope this has been helpful!
Laz
1 Like
Hello Liban
It could be that the differences you saw have to do with the switch being used. The labs in the lessons are created using Ciscoâs CML. Can you tell us more about the differences that you saw so that we can address those specifically?
I hope this has been helpful!
Laz
1 Like
Sir Lazarus,
When I written vlan 10 name printers in switch 1. It would not synchronise to others switch. Number one. Number two when I show vlan. It written each switch printers servers management. That means one of them are server all other Clint. For me what I got it. Switch 1 I wrote printers it is only
Switch 2 servers it is there only switch 2 I wrote management it it there only. My lab there is no synchronised.
Many thanks
Liban
Thank you Sir, I have got it help with that
Hello Liban
If I understand correctly, youâre saying that when you make changes to the VLANs in the VTP server, the changes arenât always synchronized with other switches, correct? Indeed, in some cases, if you find that no synchronization has taken place, you may need to force a VTP message to be sent. You can do this by creating a VLAN and then deleting it in the server. This should force the VTP server to send updates to all clients, making them update their VLAN databases.
In any case, you mention that you resolved the issue. Is this the resolution that you came to or was there something else? Let us know how else we can be of helpâŚ
I hope this has been helpful!
Laz
1 Like
I am having trouble understanding why this occurring using VTP pruning and manual pruning on a trunk interface.
prune 300 prune 200,300
+---------+ +---------+
| | v1 - 4094 | |
| sw2 +--------------------| sw3 |
| |e4/0 e4/0 | |
| | | |
+---------+ +---------+
on SW2 interface e4/0 I am manually pruning v300 and on SW3 int e4/0 I am manually pruning v200 and v300. In the VMAâs I am seeing the advertised active not include 200 and 300. However, when I do a show int trunk v200 is in the forwarding state on both sides. I was expecting the forwarding state to only be active on one side. I have no access ports in v200 on either side.
Hello Andrew
Great question. The key here is that the output of the show interfaces trunk command is a per-switch local view, not an end-to-end view.
When you run show interfaces trunk on SW2, the âVlans in spanning tree forwarding state and not prunedâ line tells you what SW2 is willing to forward out that trunk port. It does not tell you what SW3 is doing on its side. Thatâs the asymmetry youâre seeing, and itâs completely normal.
The practical result is that no VLAN 200 traffic actually crosses the trunk. When SW2 tries to send a VLAN 200 frame to SW3, SW3 drops it on ingress because VLAN 200 isnât in its allowed list.
Manual pruning with the switchport trunk allowed vlan remove command is a local, unidirectional control. It only affects the switch where you configure it. SW3âs removal of VLAN 200 doesnât reach back and modify SW2âs configuration, nor does it inform SW2 about this change, it only tells SW3 to drop VLAN 200 frames.
To make the output symmetric and clearer, when you manually prune VLANs, simply remove VLAN 200 from SW2âs trunk as well. Keep it symmetric so that you can keep track of the config.
Now, having said that, if you also have VTP pruning enabled, over time, SW2 should learn that no downstream switch needs VLAN 200 (because SW3 never sends a VTP Join for it) and prune it automatically. However, this takes a convergence cycle and is slower than manual pruning. Make sense?
I hope this has been helpful!
Laz
Hey Laz,
Thank you for the response and what you mentioned does make sense. I am however, still a tad confused on why I am seeing VLAN 200 in the forwarding state on interface E4/0 from SW3âs perspective when I issue a show interfaces trunk. I am pruning the VLAN by issuing a switchport trunk pruning vlan 200,300 command on SW3 interface 4/0.
From what you stated the show interfaces trunk is a per-switch local view for what I am willing to forward. I thought because I was pruning VLAN 200 I would not see it in the forwarding state from SW3âs perspective? On both trunk interfaces I am allowing all VLANs (switchport mode trunk). If I add switchport trunk pruning vlan add 200 to SW2 then issue show interfaces trunk I no longer see v200 in the forwarding state.
Thanks for the help,
Andrew