Hi,
Cisco declare some restriction for propagation BPDU across EoMPLS
cloud,
may be this decision for your
problem...
The following
restrictions apply to using trunks with EoMPLS:
– To
support Ethernet spanning tree bridge protocol data units (BPDUs)
across an EoMPLS cloud,
you must
On 23-03-2010 11:47, Gert Doering wrote:
The bug is in SXI2 and SXI3, and not in SXH4 (which confirms what we
saw ourselves, it's not in SXH3a).
Does anyone know if SXH7 is affected?
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
Hi,
On Thu, Mar 25, 2010 at 08:26:12AM +1000, David Hughes wrote:
Hi, and thanks for the update.
On 23/03/2010, at 8:47 PM, Gert Doering wrote:
The problem could be reproduced with our combination of ingress/egress
modules in the TAC lab, and a bug ID has been assigned: CSCtf77954=
Hi, and thanks for the update.
On 23/03/2010, at 8:47 PM, Gert Doering wrote:
The problem could be reproduced with our combination of ingress/egress
modules in the TAC lab, and a bug ID has been assigned: CSCtf77954=
So TAC confirmed it's specific to the linecards in use as well as the IOS
Hi,
On Tue, Mar 09, 2010 at 03:44:42PM +0100, Gert Doering wrote:
maybe a stupid question: are there any issues known with Rapid-PVSTP,
EoMPLS links, and IOS SXI2?
I promised to keep you updated, and here we go :-)
TAC Case number is SR 613877519.
The (very friendly and competent) TAC
On 11/03/2010, at 11:00 PM, Gert Doering wrote:
(Well, actually you can, by plugging a loop between two ports, one port
being a switchport/trunk and the other port being the EoMPLS link. But that
won't gain me much compared to what I have now - if the IOS combination
is broken with
Hi,
On Mon, Mar 15, 2010 at 04:25:56PM +1000, David Hughes wrote:
On 11/03/2010, at 11:00 PM, Gert Doering wrote:
(Well, actually you can, by plugging a loop between two ports, one port
being a switchport/trunk and the other port being the EoMPLS link. But that
won't gain me much
Hi,
On Mon, Mar 15, 2010 at 12:54:54AM -0700, Ben Basler (bbasler) wrote:
The question is if the ingress linecard has a DFC3B/BXL or DFC3C/CXL or
a CFC (and if a CFC if the Sup is a PFC3B/3BXL or PFC3C/3CXL). You might
be hitting CSCtb41832 which from what I understand will be resolved in
-Original Message-
From: Gert Doering [mailto:g...@greenie.muc.de]
Sent: Monday, March 15, 2010 3:29 AM
To: Ben Basler (bbasler)
Cc: Gert Doering; Cisco Mailing list
Subject: Re: [c-nsp] Spanning-Tree vs. EoMPLS links in SXI2?
Hi,
On Mon, Mar 15, 2010 at 12:54:54AM -0700, Ben Basler
Hi,
On Mon, Mar 15, 2010 at 09:10:13AM -0700, Ben Basler (bbasler) wrote:
As you might know - Cat6500 is an ingress forwarding model - so the
forwarding engine on the ingress linecard does the work. If there is no
local FWD engine, the PFC on the sup does the work. In case of 67xx
modules a
Gert,
-Original Message-
Having said that, there are some subtle differences how L2 PDUs
(read:
LACP, STP, VTP, CDP, 802.1x, etc.) are handled by the 3B/3BXL and
3C/3CXL.
... and that's what I assumed, since both your bug ID and the other
one specifically mention 3C.
On 15/03/2010, at 5:41 PM, Gert Doering wrote:
and it's passing MST BPDUs just fine.
Now that is good news :-) - what line card are you terminating the EoMPLS
on? (I'm asking because I'm wondering whether our problem is specific to
6724-SFP)
These are on 6748-GE-TX with SXI3. Also have
What a fantastic work around. There's a bug that breaks STP so the work around
is not to use STP. Pure genius.
David
...
On 11/03/2010, at 7:33 AM, Gert Doering wrote:
Workaround:
Not to Send BPDU over EOMPLS.
___
cisco-nsp mailing list
Hi,
On Thu, Mar 11, 2010 at 06:36:44PM +1000, David Hughes wrote:
On 11/03/2010, at 7:33 AM, Gert Doering wrote:
Workaround:
Not to Send BPDU over EOMPLS.
What a fantastic work around. There's a bug that breaks STP so the
work around is not to use STP. Pure genius.
*g*
Actually, this
you could probably do something like this
R1 ==(trunk)== Q1 -- R2 --(MPLS cloud)-- R3 -- Q2 ==(trunk)== R4
Where Q1 and Q2 would on the trunk side:
switchport mode dot1q-tunnel
switchport access vlan QinQ
l2tunnel-protocol STP
and then the tunneled STP may get forwarded via xconnect.
Hi,
Cisco declare some restriction for propagation BPDU across EoMPLS cloud,
may be this decision for your problem...
The following restrictions apply to using trunks with EoMPLS:
– To support Ethernet spanning tree bridge protocol data units (BPDUs)
across an EoMPLS cloud,
you must disable
Hi,
On Thu, Mar 11, 2010 at 10:51:15AM +, Mateusz Blaszczyk wrote:
you could probably do something like this
R1 ==(trunk)== Q1 -- R2 --(MPLS cloud)-- R3 -- Q2 ==(trunk)== R4
This might work as a workaround, or might not, depending on whether
R2/R3 would be willing to forward
Hi,
On Thu, Mar 11, 2010 at 01:56:29PM +0200, Anrey Teslenko wrote:
Cisco declare some restriction for propagation BPDU across EoMPLS cloud,
may be this decision for your problem...
Well...
http://www.cisco.com/en/US/docs/routers/7600/ios/12.2SXF/configuration/guide/pfc3mpls.html#wp1279824
Hi,
(is it OK if I CC my reply back to c-nsp?)
On Tue, Mar 09, 2010 at 06:43:57PM +0100, Peter Rathlev wrote:
On Tue, 2010-03-09 at 15:44 +0100, Gert Doering wrote:
maybe a stupid question: are there any issues known with Rapid-PVSTP,
EoMPLS links, and IOS SXI2?
Probably not much help,
Gert,
maybe you are hitting some old bug as I did long time ago on SXH1, it
was 3C bug...
http://www.gossamer-threads.com/lists/cisco/nsp/81589 ?
Best Regards,
-mat
On 9 March 2010 14:44, Gert Doering g...@greenie.muc.de wrote:
Hi,
maybe a stupid question: are there any issues known with
Hi,
On Wed, Mar 10, 2010 at 07:44:27PM +, Mateusz Blaszczyk wrote:
maybe you are hitting some old bug as I did long time ago on SXH1, it
was 3C bug...
http://www.gossamer-threads.com/lists/cisco/nsp/81589 ?
Thanks for the pointer. This is very similar to what we experience - except
that
Hi,
maybe a stupid question: are there any issues known with Rapid-PVSTP,
EoMPLS links, and IOS SXI2?
We just had a nice problem due to a broadcast loop which should have
been broken by STP in the first place, but wasn't - and investigation
afterwards showed an EoMPLS link that just refuses to
On Tue, 2010-03-09 at 21:26 +0100, Gert Doering wrote:
On cisco.com, I found configuration options for 12.0S on GSRs to
enable/disable forwarding of VTP, STP, CDP individually
(l2protocol stp ...), but that's not available on SXI2.
There seems to be a l2protocol-tunnel proto interface config
23 matches
Mail list logo
