Switching: Difference between revisions
→VLAN
(→VLAN) |
(→VLAN) |
||
Line 14:
;VTP
Source: [http://www.firewall.cx/networking-topics/vlan-networks/virtual-trunk-protocol/223-vtp-introduction.html firewall.cx]
*When a new VLAN is created and configured on a switch without the VTP protocol enabled, this must be manually replicated to all switches on the network so they are all aware of the newly created VLAN.
*This means that the administrator must configure each switch separately, a task that requires a lot of time and adds a considerable amount of overhead depending on the size of the network.
*With the VTP protocol configured, the changes on the VTP server switch will get replicated across the network itself.
*This will also ensure these changes are magically propagated to all other switches.
*VTP information can traverse only through a trunk Link.▼
;VTP Modes
▲VTP information can traverse only through a trunk Link.
The default mode for all switches supporting VTP.
VTP Client mode▼
You can create, modify, and delete VLANs and specify other configuration parameters (such as VTP version) for the entire VTP domain.
VTP Transparent mode▼
VTP servers advertise their VLAN configurations to other switches in the same VTP domain and synchronize their VLAN configurations with other switches based on advertisements received over trunk links.
VLAN configurations are saved in NVRAM.
Behaves like a VTP server, but you cannot create, change, or delete VLANs on a VTP client.
VLAN configurations are saved in NVRAM.
Does not advertise its VLAN configuration and does not synchronize its VLAN configuration based on received advertisements.
However, they will forward VTP advertisements as they are received from other switches.
You can create, modify, and delete VLANs on a switch in VTP transparent mode.
VLAN configurations are saved in NVRAM, but they are not advertised to other switches.
==STP==
| |||