From: Erick B. (erickbe@xxxxxxxxx)
Date: Thu Mar 07 2002 - 21:44:27 GMT-3
Hi,
VTP lets other switches learn the VLANs configured in
your network. Just the VLAN #, and other related info.
The main reason is for VLAN trunking - trunking won't
work if a VLAN isn't defined on the switch. VTP
doesn't assign ports to VLANs.
For Example:
A --- B --- C
VLAN trunks between A and B, and B and C. All VLANs
allowed in trunk.
You have 3 VLANs. Switch A has VLANs 1, and 2.
Switch B is in VLANs 1, and 3. Switch C is in 1, and
2.
Without VTP (all transparent), VLAN 1 will make it
across all the switches. VLAN 2 won't be trunked
together between A and C. VLAN 3 is on B only.
The reason why VLAN 2 won't be trunked is because
switch B doesn't have a VLAN 2 defined in its local
VLAN database. So it just drops everything for VLAN 2
cause it doesn't know about VLAN 2.
Now, if we make Switch A a VTP server and put all the
switches in the same VTP domain Switch B will add VLAN
2 to its database and send that to Switch C also. Now,
VLAN 2 will work between A and C.
HTH, Erick
--- "Lupi, Guy" <Guy.Lupi@eurekaggn.com> wrote:
> I understand vtp modes and all that stuff, my
> question is probably pretty
> simple but I don't have much experience with layer 2
> switching within a vtp
> domain. My question is, if you have a switch and it
> is the vtp server, it
> sends updates and can delete and add vlans. A
> client receives and processes
> updates, but cannot create or delete vlans. So on
> the client, you still
> assign certain ports to certain vlans correct? It's
> just that if that vlan
> is not configured on the vtp server it will not work
> properly? Thanks.
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:56 GMT-3