From: NET HE (he_net@hotmail.com)
Date: Thu Feb 26 2009 - 20:56:05 ARST
Thanks for your information.
Best Regards,
Net (Xin) He
Date: Thu, 26 Feb 2009 17:48:38 -0500
Subject: Re: LACP over dot1q-tunnels
From: all.from.nj@gmail.com
To: he_net@hotmail.com
CC: navin.ms@gmail.com; ccielab@groupstudy.com
Hey Net and Naveen,
I have tried this and I also can not get it to work with ISL on the edge
switches ... only dot1q. I labbed it this afternoon.
Here is a relevant excerpt from the 3560 guide:
"
When configuring IEEE 802.1Q tunneling on an edge switch, you must use IEEE
802.1Q trunk ports for sending packets into the service-provider network.
However, packets going through the core of the service-provider network can be
carried through IEEE 802.1Q trunks, ISL trunks, or nontrunking links.
"
Looks like the connection into the SP (in this case SW4) must be dot1q. In
the SP's network, they can run ISL. I tested this in my lab and it works this
way. Here is a link to the 3560 guide (watch the word wrap):
http://www.cisco.com/en/US/docs/switches/lan/catalyst3560/software/release/12
.2_44_se/configuration/guide/swtunnel.html
HTH,
Andrew
On Thu, Feb 26, 2009 at 5:37 PM, NET HE <he_net@hotmail.com> wrote:
Are you sure the question? I don't think dot1qtunnel supports isl-in-q. To my
understanding, dot1qtunnel only support q-in-q.
Best Regards,
Net (Xin) He
> Date: Wed, 25 Feb 2009 21:56:43 -0800
> Subject: LACP over dot1q-tunnels
> From: navin.ms@gmail.com
> To: ccielab@groupstudy.com
>
> Guys,
>
> In IEWB Lab-20, the task it to do LACP port-channel b/n SW1 and SW3, where
> SW4 is in the middle.
>
> SW1==(19,21)==============(13,15)==SW4==(19,21)==============(19,21)==SW3
>
> *Task:*
> Configure interfaces 19 & 21 on SW1 and SW3 as ISL Trunks.
> These links should be bound togather by LACP negotiation.
> Do not use DTP to accomplish this.
> SW1 and SW3 are in VTP domain 789. SW4 is in domain 10.
>
> *Problem:*
> I could get following config working for dot1q encapsulation, but *not for
> ISL*. Can someone plz try on their rack ?
>
> *SW4:*
> interface GigabitEthernet1/0/13
> switchport access vlan 100
> switchport trunk encapsulation dot1q
> switchport mode dot1q-tunnel
> switchport nonegotiate
> l2protocol-tunnel point-to-point lacp
> !
> interface GigabitEthernet1/0/15
> switchport access vlan 200
> switchport trunk encapsulation dot1q
> switchport mode dot1q-tunnel
> switchport nonegotiate
> l2protocol-tunnel point-to-point lacp
> !
> interface GigabitEthernet1/0/19
> switchport access vlan 100
> switchport trunk encapsulation dot1q
> switchport mode dot1q-tunnel
> switchport nonegotiate
> l2protocol-tunnel point-to-point lacp
> !
> interface GigabitEthernet1/0/21
> switchport access vlan 200
> switchport trunk encapsulation dot1q
> switchport mode dot1q-tunnel
> switchport nonegotiate
> l2protocol-tunnel point-to-point lacp
> !
>
> *SW1 and SW3:*
> interface GigabitEthernet1/0/19
> switchport trunk encapsulation dot1q
> switchport mode trunk
> switchport nonegotiate
> channel-group 1 mode active
> !
> interface GigabitEthernet1/0/21
> switchport trunk encapsulation dot1q
> switchport mode trunk
> switchport nonegotiate
> channel-group 1 mode active
> !
> interface Port-channel1
> switchport trunk encapsulation dot1q
> switchport mode trunk
> switchport nonegotiate
>
> TIA,
> Naveen.
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
This archive was generated by hypermail 2.1.4 : Sun Mar 01 2009 - 09:44:13 ARST