From: Ramiro Garza (ccie15xxx@gmail.com)
Date: Wed Feb 22 2006 - 02:49:07 GMT-3
To get rid of the problem just configure the port 3/7 as dot1q, you probably
have it configured as an access port. I have seen this problem when there
are several switches connected to a hub.
HTH,
Ramiro Garza
On 2/21/06, Ivan Kuchin <ivan@iip.net> wrote:
>
> I think that switch try parse isl-frame received on dot1q-ports. It can
> parse
> this frame but it's wrong. And some field will have impossible values.
>
> For example you can sh mac- int XXXX and you'll see that mac-address-table
> is
> broken.
>
> > Well, somehow it is configured in my network. Just to let you know,
> > before I got here....
> >
> > I just implemented syslogging, and I am receiving these messages:
> >
> > 2006 Feb 21 10:49:24 CST -06:00 %SPANTREE-2-RX_1QNON1QTRUNK: Rcved
> > 1Q-BPDU on non-1Q-trunk port 3/6 vlan 4
> >
> > 2006-02-21 08:30:00 2006 Feb 21 08:57:22 CST -06:00
> > %SPANTREE-2-RX_1QNON1QTRUNK: Rcved 1Q-BPDU on non-1Q-trunk port 3/7 vlan
> > 999
> >
> > Look up what they meant, and Cisco reports that trunks are configured
> > different on each end.
> >
> > %SPANTREE-2-RX_1QNON1QTRUNK: Rcved 1Q-BPDU on non-1Q-trunk port
> > [chars] vlan [dec] from [chars]
> >
> > This message indicates that the non-1Q-trunking (ISL) port has received
> > at least one 1Q-tagged spantree BPDU frame on the receiving VLAN. [dec]
> > is the module number, [chars] is the port number, [dec] is the VLAN
> > number, and the second [chars] is the source MAC address of the BPDU.
> >
> > Recommended Action: Either reconfigure the non-1Q-trunking port into a
> > 1Q-trunking port, or reconfigure the peer 1Q-trunking port into the
> > corresponding non-1Q-trunking port.
> >
> > Does anyone know what would happen if this is the case...what traffic
> > would get passed and/or dropped...? I am not receiving any complaints
> > about problems so I am assuming something is working correctly.
> >
> >
> > Chuck Brantley
> >
> >
> > -----Original Message-----
> > From: Ivan [mailto:ivan@iip.net]
> > Sent: Tuesday, February 21, 2006 10:44 AM
> > To: ccielab@groupstudy.com; Brantley, Charles
> > Subject: Re: OT: dot1Q and ISL
> >
> > no.
> > It's impossible.
> > Size dot1q tag is 4 bytes
> > ISL - 20 byte
> >
> > And different algoritm used to encapsulate payload.
> > ISL: there is header and footer(CRC) for payload packet.
> > dot1q: this tag inject after src dst mac addreses and before remain
> > packet.
> >
> > > Is it possible to have to switches trunking with one another using
> > > dot1q on one side and ISL on the other...?
> > >
> > > i.e
> > > SW1 port 3/6 (ISL) --> SW2 port 1/2 (dot1Q)
> > >
> > > Thanks
> > >
> > > Chuck Brantley
> > >
> > > ______________________________________________________________________
> > > _ Subscription information may be found at:
> > > http://www.groupstudy.com/list/CCIELab.html
> >
> > --
> > Ivan
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
> --
> iWAN kU^IN (mail to: ivan@iip.net)
> NOC iip.net
> 137-31-04
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Wed Mar 01 2006 - 11:28:18 GMT-3