From: Aristomenis Zikopoulos (azik@altec.gr)
Date: Fri Feb 24 2006 - 05:11:35 GMT-3
Hi JB,
The task asks for traffic belonging to Vlan8 to be assigned over the port
fa0/13 of SW1....The key phrase is the "Not locally assigned"
In the task 1.1- 1.4 you were forced to make this configuration:
vtp domain ETHERNET
vtp password CISCO
vtp pruning
vlan 7,8,12,36,43,45,77,88,258
So, all "not locally assigned VLAN traffic has "pruned"".
To ensure that port Fa0/13 receives traffic from VLAN8, you have to
configure an interface command, pruning everything accept VLAN8
(switchport trunk pruning vlan 2-7,9-1001)
(Theory: All VLANs are allowed to be sent over any trunk link in the VTP
domain. Therefore, broadcast frames and frames destined for unknown unicast
addresses will be sent over all trunks throughout the domain.
This behaviour is undesirable when one or more switches throughout the VTP
domain receive traffic for VLANs that they do not have locally assigned and
are not in the transit path for. In order to reduce this unnecessary traffic
VTP offers a feature known as pruning. VTP pruning allows a switch to
communicate with its directly connected neighbours about what VLANs they
have locally assigned and are in the transit path for. Therefore VLANs that
are unnecessary can be "pruned" off of the interface. VTP pruning can be
enabled by issuing the vlan database or global configuration command vtp
pruning.)
Best Regards,
Aris
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
jellyboy
Sent: Thursday, February 23, 2006 10:34 PM
To: ccielab@groupstudy.com
Subject: IEWB Lab4 1.3 Traffic Control
Hi all, The task asks for traffic belonging to Vlan8 to be assigned to port
fa0/13 and all other trunk links should not receive Vlan8. The Brians
solution involves removing Vlan8 from the prune eligible list:
#switchport trunk pruning vlan 2-7,9-1001
I can understand the logic behind this, but I originally came up with:
interface FastEthernet0/13
switchport trunk encapsulation dot1q
switchport trunk native vlan 36
switchport trunk allowed vlan 8 <<
switchport mode trunk
!
interface FastEthernet0/14
switchport trunk encapsulation dot1q
switchport trunk native vlan 36
switchport trunk allowed vlan 1-7,9-4094 <<
switchport mode trunk
!
interface FastEthernet0/15
switchport trunk encapsulation dot1q
switchport trunk native vlan 36
switchport trunk allowed vlan 1-7,9-4094 <<
switchport mode trunk
I am wondering if what I did accomplishes the same thing?
If not what are the suttle (or obvious!!) differences? Apart from the static
allocation of vlans on a trunk.
Many Thanks,
JB
This archive was generated by hypermail 2.1.4 : Wed Mar 01 2006 - 11:28:18 GMT-3