Consider 4 switches vtp pruning enabled in a full mesh way.The administrator wants to add a another switch 5 to switch4 without vtp pruning enabled on switch 5.switch 4 is vtp enabled and switch 5 isnt.So switch 4 cant decide what are vlans that are required by switch 5.So switch 4 breaks the vtp pruning and forward all the vlan traffic to ...

Hi Ing and thanks! OK, so Cisco does recommend not to use it for an established network. However, based on what you posted and what I have heard as well and found online, the only reason EVER that a switch added to a VTP network will overwrite its VLANs is if the VTP domain is not set up properly with a VTP domain name AND a VTP password that only the IT admins …

Scenario 4: vtp version 3 server - vtp version 1 client -----vtp client changes version from 1 to 2. VTP works, vlans are propagated. But VTP doesn't work when a password is configured. Scenario 5: vtp version 2 server - vtp version 3 client -----This scenario is obscure to me. DTP works, but newly added VLANs are not propogated via VTP.

That is - i think the question is, if you configure VTP and add or remove some VLANs - this configuration is not shown in the running-config. For example: configure terminal. vtp mode server. vtp version 2. vlan 10. name engineering. vlan 20. name students. vlan 30. name staff

Changes in the VTP transparent switch are not sent over the trunk to other VTP switches. VTP transparent switches store the VLAN information in the running-config. 2. Yes, VTP client can forward VTP messages to other switches (transparent, clients and/or servers). Note that a client could even change the VLAN database of a server switch. 3.

Dist1#vtp prim. This system is becoming primary server for feature vlan. No conflicting VTP3 devices found. Do you want to continue? [confirm] Dist1# Dist1# *Jan 19 23:47:47.468: %SW_VLAN-4-VTP_PRIMARY_SERVER_CHG: fa16.3e0b.225e has become the primary server for the VLAN VTP featuresh vtp status. VTP Version capable : 1 to 3

While VTP pruning does have some drawbacks there are valid use-cases for deploying VTP and VTP pruning. For instance, small remote sites with a small number of switches and a limited number of VLANs can safely benefit from VTP and VTP pruning.

To avoid incorrectly configuring a VTP domain name, set the VTP domain name on only one VTP server switch. All other switches in the same VTP domain will accept and automatically configure their VTP domain name when they receive the first VTP summary advertisement. I just finish my Packet tracer practical on VTP.

VTP VLAN configuration not allowed when device is in CLIENT mode. But, many people consider this the way to go for various reasons, like convenience and saving time. Others, such as David Hucaby say go all transparent for local administration control, and safety.

SM1(config) #vtp? domain Set the name of the VTP administrative domain. file Configure IFS filesystem file where VTP configuration is stored. interface Configure interface as the preferred source for the VTP IP updater. address. mode Configure VTP device mode. password Set the password for the VTP administrative domain