The VLAN Trunking Protocol (VTP)

 VTP allows switches to synch their VLAN databases by advertising their VLAN info to other switches in the same VTP domain. This allows switches with no ports in a particular VLAN to still handle traffic for that VLAN. When a VLAN is created on one switch in a VTP domain, all other switches in that VTP domain are notified of that VLAN's existence. 

A switch can run in on e of three VTP modes:

Server mode allows the switch to create, name, and delete VLANs. 

Client mode prevents the switch from creating, naming, or deleting VLANs. 

Transparent mode switches forward the VTP advertisements received from other switches, but do not actually process the info in those ads. VLANs can be created, named, and deleted on switches running in transparent mode, but these changes are not advertised to the other switches in the VTP domain. 

VTP domain name is case sensitive.

SW1#show vtp status

SW1(config)#vtp domain CCNA

Changing VTP domain name from NULL to CCNA

A switch from another physical location, SW4, is brought to this client site and placed into the VTP domain CCNP. The CRN on that switch is 500, and this switch only knew about VLAN1 at its prior location which means it only knows about VLAN 1 at its new location. 

SW4 doesn't even have to be in Server mode to ruin things. While a Client generally spends its time listening for and forwarding VTP ads, a Client will send a full VTP summary ad when it first coms online. That's enough to cause a lot of trouble here. 

Cisco theory hold there are two ways to ensure the CRN is set to zero:

Change the VTP domain name to a non-existent domain, then change it back to the original name. 

Change the VTP mode from server to transparent, then back to server. 

Pruning: 

SW1#vtp status

VTP Pruning Mode: Disabled




Comments

Popular posts from this blog

IP Version 6

OSPF

Wireless Security