From: Sean Khoo \(AU\) (Sean.Khoo@didata.com.au)
Date: Tue Aug 29 2006 - 21:51:42 ART
too late. i have erased the config.. both switches are occupied by other
people now..
Regards,
Sean Khoo
________________________________
From: Plukkie [mailto:plukkie@gmail.com]
Sent: Wednesday, 30 August 2006 5:36 AM
To: Sean Khoo (AU)
Cc: Arun Arumuganainar; David Redfern (AU); ccielab@groupstudy.com;
Jason Bartley (AU)
Subject: Re: EMULATE VTP PRUNING WITH SWITCHPORT TRUNK ALLOWED
Sean, I need also the output of your SW2.
Do you also can paste sh vtp status of both?
THX
On 8/29/06, Sean Khoo (AU) <Sean.Khoo@didata.com.au> wrote:
        Plukkie,
        Switch 1 would add those vlan into requested list even you do
not have any host. this happen because you have an active trunk port
between SW1 and SW2 which cause the SVI to up/up. see the output below..
vlan 5,7,46 have been pruned on SW1 due to lack of request from SW2
while vlan 1,5,7,28,46,100 have been added into the SW1 requested list.
        As a result Switch 2 can not prune those vlan 1,5,7,28,46,100
which requested by SW1 and have to add those vlan into allow list..
        same rules apply to the other switch..
        pls correct me if am wrong.. thanks
        Switch-1#sh vlan brief
        VLAN Name                             Status    Ports
        ---- -------------------------------- ---------
-------------------------------
        1    default                          active    Fa0/5, Fa0/6,
Fa0/7, Fa0/8
                                                        Fa0/9, Fa0/10,
Fa0/11, Fa0/12
                                                        Fa0/14, Fa0/15,
Fa0/16, Fa0/17
                                                        Fa0/18, Fa0/19,
Fa0/20, Fa0/21
                                                        Fa0/22, Fa0/23,
Fa0/24, Gi0/1
                                                        Gi0/2
        5    VLAN0005                         active    Fa0/4
        7    VLAN0007                         active
        28   VLAN0028                         active    Fa0/2
        46   VLAN0046                         active    Fa0/3
        100  VLAN0100                         active    Fa0/1
        1002 fddi-default                     act/unsup
        1003 token-ring-default               act/unsup
        1004 fddinet-default                  act/unsup
        1005 trnet-default                    act/unsup
        Switch-1#sh ip int brief
        Interface              IP-Address      OK? Method Status
Protocol
        Vlan1                  unassigned      YES unset
administratively down down
        Vlan7                  10.10.10.1 <http://10.10.10.1/>       YES
manual up                    up
        FastEthernet0/1        unassigned      YES unset  up
up
        FastEthernet0/2        unassigned      YES unset  up
up
        FastEthernet0/3        unassigned      YES unset  up
up
        FastEthernet0/4        unassigned      YES unset  up
up
        FastEthernet0/5        unassigned      YES unset  up
up
        Switch-1#sh int f0/13 pruning
        Port        Vlans pruned for lack of request by neighbor
        Fa0/13      5,7,46
        Port        Vlan traffic requested of neighbor
        Fa0/13      1,5,7,28,46,100
        Regards,
        Sean Khoo
________________________________
        From: Plukkie [mailto:plukkie@gmail.com]
        Sent: Tuesday, 29 August 2006 4:40 PM
        To: Sean Khoo (AU)
        Cc: Arun Arumuganainar; David Redfern (AU);
ccielab@groupstudy.com ; Jason Bartley (AU)
        Subject: Re: EMULATE VTP PRUNING WITH SWITCHPORT TRUNK ALLOWED
        Sean,
        This is solution three from David:
        Soltution3:
        allows vlan traffic to other side that the OTHER side
        has hosts in as well as all interface vlans on the other side.
        The first part, correct, but what's the use to allow interface
vlans from the other side, while you don't have hosts in that vlan or
neither yourself an interface in that vlan?
        gr
        On 8/29/06, Sean Khoo (AU) <Sean.Khoo@didata.com.au > wrote:
                I think the solution 3 is the correct solution if you
want to emulate
                vtp pruning.
                Regards,
                Sean Khoo
                -----Original Message-----
                From: Arun Arumuganainar [mailto:aarumuga@hotmail.com]
                Sent: Monday, 28 August 2006 11:13 PM
                To: Plukkie; David Redfern (AU)
                Cc: ccielab@groupstudy.com; Sean Khoo (AU); Jason
Bartley (AU)
                Subject: Re: EMULATE VTP PRUNING WITH SWITCHPORT TRUNK
ALLOWED
                Pruning will allow traffic on the trunk side only on
couple of occasions
                .
                1)  VLAN should locally assigned  or
                2)  Switch should act as a transit for those vlan .
                Second condition is does not apply in CCIE LAB
environment . In a two
                switch environment there is not question about switch to
act as a pure
                transit .
                Ideal solution would be ... On SW1 allow all vlan that
assigned locally
                on
                SW2 ( including VLAN 1...the default Vlan ) and vice
versa .
                Thanks and Regards
                Arun
                ----- Original Message -----
                From: "Plukkie" <plukkie@gmail.com >
                To: "David Redfern (AU)" <David.Redfern@didata.com.au>
                Cc: < ccielab@groupstudy.com
<mailto:ccielab@groupstudy.com> >; "Sean Khoo (AU)"
                <Sean.Khoo@didata.com.au>; "Jason Bartley (AU)"
                <Jason.Bartley@didata.com.au>
                Sent: Monday, August 28, 2006 2:54 PM
                Subject: Re: EMULATE VTP PRUNING WITH SWITCHPORT TRUNK
ALLOWED
		> Hi,
		>
		> I would presume only allowing the common vlans that
are used on both
		> switches, so that is 100 and 28.
		>
		> on both switches:
		> switchport trunk allowed vlan 28,100
		>
		> gr Plukkie
		>
		>
		> On 8/28/06, David Redfern (AU)
<David.Redfern@didata.com.au > wrote:
		> >
		> > Guys,
		> >
		> > Struggling to find the correct way to emulate vtp
pruning using
		> > switchport trunk allowed vlan command..
		> >
		> > Question is from InternetExpert Lab 28 Also says to
only send the
		> > minumum amount of traffic necessary across these
trunk links
		> >
		> >
		> >
		> > Eg,
		> >
		> > Sw1 has hosts in vlan 100,28,46,5
		> > Also has interface vlan 7 (but no interfaces in the
vlan)
		> >
		> > Sw2 has hosts in vlans 34,100
		> > Also has interface vlan 8 and 28 (but no interfaces
in the vlan)
		> >
		> >
		> > What do you guys think is the correct solution.
		> >
		> > Solution 1.(only allows vlan traffic  to other side
that both
		> > switches have hosts in. eg 100) SW1.
		> > switchport trunk allowed vlan 100
		> >
		> > SW2
		> > switchport trunk allowed vlan 100
		> >
		> >
		> >
		> > Solution 2. (allows vlan traffic to other side that
the OTHER side
		> > has hosts in as well as interface vlans ((28) where
this traffic
		> > must traverse the trunk)
		> > SW1
		> > switchport trunk allowed vlan 34,100,28
		> >
		> > SW2
		> > switchport trunk allowed vlan 100,28,46,5
		> >
		> >
		> > Solution 3. (allows vlan traffic to other side that
the OTHER side
		> > has hosts in as well as all interface vlans on the
other side)
		> > SW1
		> > switchport trunk allowed vlan 34,100,28,8
		> >
		> > SW2
		> > switchport trunk allowed vlan 100,28,46,5,7
		> >
		> >
		> >
		> >
		> > Solution 4, (Their solution. Confused about the
logic)
		> >
		> > SW1.
		> > switchport trunk allowed vlan 7.28,100
		> > SW2
		> > switchport trunk allowed vlan 8.28.100
		> >
		> >
		> > Or others
		> >
		> > Any ideas about the best way?
		> >
		> >
		> >
		> >
************************************************************************
                ****
                *
		> > *
		> > - NOTICE FROM DIMENSION DATA AUSTRALIA This message
is confidential,
		> > and may contain proprietary or legally privileged
information.  If
		> > you have received this email in error,
                please
		> > notify the sender and delete it immediately.
		> >
		> > Internet communications are not secure. You should
scan this message
		> > and any attachments for viruses.  Under no
circumstances do we
		> > accept liability for any loss or damage which may
result from your
		> > receipt of this message or any attachments.
		> >
		> >
************************************************************************
                ****
                *
		> > *
		> >
		> >
This archive was generated by hypermail 2.1.4 : Fri Sep 01 2006 - 15:41:59 ART