From: Ronnie Angello (ronnie.angello@gmail.com)
Date: Mon Apr 02 2007 - 10:48:47 ART
It should not be a problem to have trunk links between the switches. Only
the ports connected to R3 and R5 need to be access or .1q tunnel ports to
support l2 protocol tunneling.
On 4/2/07, dampened taker <cheechew@hotmail.com> wrote:
>
> But the problem with dot1q is between SWA and SWB.
> Will dot1q between switches will cause problem?
>
>
>
>
>
>
> From: "Ronnie Angello" <ronnie.angello@gmail.com>
> To: dampened <cheechew@hotmail.com>
> CC: "Cisco certification" <ccielab@groupstudy.com>
> Subject: Re: trouble understanding L2 protocol tunneling
> Date: Mon, 2 Apr 2007 08:05:04 -0400
>
> The switch supports tunneling of CDP, STP, including multiple STP (MSTP),
> and VTP. Protocol tunneling is disabled by default but can be enabled for
> the individual protocols on IEEE 802.1Q tunnel ports or on access ports.
>
> Tunneling is not supported on trunk ports. If you enter the
> *l2protocol-tunnel
> *interface configuration command on a trunk port, the command is accepted,
> but Layer 2 tunneling does not take affect unless you change the port to a
> tunnel port or an access port.
> Ronnie
>
> On 4/2/07, dampened <cheechew@hotmail.com> wrote:
> >
> >Dear Josef,
> >
> >Which part of the document states it cannot work with dot1q?
> >
> >It would be strange if the interconnect switch is unable to support
> dot1q.
> >
> >Regards
> >
> >
> >
> >
> >
> >
> >
> > "Josef A" <josefnet@gmail.com>
> > Sent by: nobody@groupstudy.com
> > 03/28/2007 06:43 PM Please respond to
> > "Josef A" josefnet@gmail.com
> >
> >
> >
> >
> >Layer 2 protocol tunnelling only works with access ports or tunnel ports.
> >
> >
> >
>
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat3560/12225see/scg/swtu
> >nnel.htm
> >
> >
> >
> >On 3/27/07, Swan, Jay <jswan@sugf.com> wrote:
> > >
> > > I have the following physical topology:
> > >
> > >
> > >
> > > R3---SwA---SwB---R5
> > >
> > >
> > >
> > > R3 and R5 are in access vlan 35 with "l2protocol-tunnel cdp" on the
> > > access ports.
> > >
> > >
> > >
> > > If I configure the link between SwA and SwB in access vlan 35 with
> > > "l2protocol-tunnel cdp", everything works fine: R3 and R5 see each
> other
> > > as directly connected CDP neighbors. If I configure the link between
> SwA
> > > and SwB as a hard-coded 802.1q trunk, however, the link is
> err-disabled
> > > with an l2ptguard error.
> > >
> > >
> > >
> > > I don't understand why this doesn't work with a trunk link. Thoughts?
> > >
> > >
> > >
> > > Jay
> > >
> > >
> _______________________________________________________________________
> > > Subscription information may be found at:
> > > http://www.groupstudy.com/list/CCIELab.html
> >
> >_______________________________________________________________________
> >Subscription information may be found at:
> >http://www.groupstudy.com/list/CCIELab.html
> >
> >_______________________________________________________________________
> >Subscription information may be found at:
> >http://www.groupstudy.com/list/CCIELab.html
> >
>
> _________________________________________________________________
> Find singles online in your area with MSN Dating and Match.com!
> http://match.my.msn.com/match/mt.cfm?pg=channel&tcid=281206
This archive was generated by hypermail 2.1.4 : Tue May 01 2007 - 08:28:34 ART