From: dampened (cheechew@hotmail.com)
Date: Mon Apr 02 2007 - 07:54:37 ART
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
This archive was generated by hypermail 2.1.4 : Tue May 01 2007 - 08:28:34 ART