[c-nsp] Spanning-tree migration from MST to RSTP

Hi List, I am working at a new datacenter that has a spine/leaf (all Nexus 9ks) topology. The spine switches (two of them) are configured for MST but all of the leaf switches are running rapid-pvst. I would like to migrate the spine's to rapid-pvst but I want to make sure i'm not missing anything

Re: [c-nsp] spanning-tree for local switching on ASR920

On Thu, 2018-03-15 at 13:29 +, Nick Cutting wrote: > In the output of show spanning tree - is the port with the untagged > service instance forwarding on vlan 4093? > Unless something changed from 16.6 -> 16.7 I imagine that it is only > forwarding and processing BPDU's on vlans 2 and 10.

Re: [c-nsp] spanning-tree for local switching on ASR920

use BPDU's were not processed on this VLan it may be bad. NIck -Original Message- From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Peter Rathlev Sent: Thursday, March 15, 2018 7:06 AM To: Nick Cutting <ncutt...@edgetg.com> Cc: cisco-nsp@puck.nether.net Subject: R

Re: [c-nsp] spanning-tree for local switching on ASR920

For what it's worth I have working Rapid PVST+ on ARS 920 IOS 16.7.1 with the following configuration: spanning-tree mode rapid-pvst spanning-tree vlan 2,10,2302 priority 24576 ! interface TenGigabitEthernet0/0/25 description => Towards HP 5700FF mtu 9216 no ip address load-interval 30

Re: [c-nsp] spanning-tree for local switching on ASR920

Gert Doering <g...@greenie.muc.de>; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] spanning-tree for local switching on ASR920 This message originates from outside of your organisation. I actually just got this kind of working, but had to use MST. Cisco IOS XE Software, Version 03.18.00.SP.1

Re: [c-nsp] spanning-tree for local switching on ASR920

-Original Message- From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Mark Tinka Sent: Monday, March 12, 2018 5:04 PM To: Nick Cutting <ncutt...@edgetg.com>; Gert Doering <g...@greenie.muc.de>; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] spanning-tree for loc

Re: [c-nsp] spanning-tree for local switching on ASR920

On 12/Mar/18 22:21, Nick Cutting wrote: > Sorry to drag this one up - Gert did you ever get a working config for this? > > I plan on using a pair of 920's with a layer 2 broadcast domain on the 12 > gigabit Ethernet ports, and using the 10g ports to connect to separate > carriers, bust also

Re: [c-nsp] spanning-tree for local switching on ASR920

Of Gert Doering Sent: Thursday, October 19, 2017 2:46 AM To: Peter Rathlev <pe...@rathlev.dk> Cc: Gert Doering <g...@greenie.muc.de>; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] spanning-tree for local switching on ASR920 This Message originated outside your organization. Hi, On

Re: [c-nsp] spanning-tree for local switching on ASR920

I believe you should use "l2protocol forward/tunnel stp" instead of "l2protocol peer stp" under si 10, assuming FWs run STP (?) and it's untagged. But another questions comes to my mind: are the two FWs L2 connected by some other media too, besides through the ASR920? -- Tassos Gert Doering

Re: [c-nsp] spanning-tree for local switching on ASR920

Hi, > From: Gert Doering [mailto:g...@greenie.muc.de] > Sent: Thursday, October 19, 2017 10:15 AM > > Hi, > On Thu, Oct 19, 2017 at 09:45:08AM +0100, adamv0...@netconsultings.com > wrote: > > Hmm and if you enable debug can you actually see the stp packets being > > issued (or even received) on

Re: [c-nsp] spanning-tree for local switching on ASR920

Hi, On Thu, Oct 19, 2017 at 09:45:08AM +0100, adamv0...@netconsultings.com wrote: > Hmm and if you enable debug can you actually see the stp packets being > issued (or even received) on either of the ports? > The config looks good for catching and processing such PDUs. It's not sending PDUs, so

Re: [c-nsp] spanning-tree for local switching on ASR920

On 19/Oct/17 10:48, James Bensley wrote: > We wouldn't offer dual connections to the same layer 3 edge device as > a "resilient" service nor have it participate in layer 2 service if it > is layer 3 edge. I'd stick a switch in place, the FW could have two > links to the switch and the switch

Re: [c-nsp] spanning-tree for local switching on ASR920

On 19 October 2017 at 09:38, Mark Tinka wrote: > > > On 19/Oct/17 10:24, Gert Doering wrote: > > So, how do you bridge together two ports on an ASR1k, with STP? ;-) > > I do understand the bits about no global VLAN significance, etc., > and tieing bridge-groups to

Re: [c-nsp] spanning-tree for local switching on ASR920

Hmm and if you enable debug can you actually see the stp packets being issued (or even received) on either of the ports? The config looks good for catching and processing such PDUs. Btw I'm still not getting the setup, so you have FW1 in port 1 and FW2 in port 2 and p1 and p2 are in BD1. Now how

Re: [c-nsp] spanning-tree for local switching on ASR920

On 19/Oct/17 10:24, Gert Doering wrote: > So, how do you bridge together two ports on an ASR1k, with STP? ;-) > > I do understand the bits about no global VLAN significance, etc., > and tieing bridge-groups to pseudowires, etc. - I just want the more > basic stuff to be more explosion-robust

Re: [c-nsp] spanning-tree for local switching on ASR920

Hello Gert, 2017-10-18 15:39 GMT+02:00 Gert Doering : > IOS is asr920-universalk9_npe.03.18.03.S.156-2.S3-std.bin Well PVST+/RPVST+ is a fancy feature on this platform, and for fancy features you need fancy releases :) 16.6.1 in this case:

Re: [c-nsp] spanning-tree for local switching on ASR920

Hi, On Thu, Oct 19, 2017 at 10:19:22AM +0200, Mark Tinka wrote: > Treat more like an ASR1000 router, and you'll be just fine. So, how do you bridge together two ports on an ASR1k, with STP? ;-) I do understand the bits about no global VLAN significance, etc., and tieing bridge-groups to

Re: [c-nsp] spanning-tree for local switching on ASR920

Hi, On Thu, Oct 19, 2017 at 09:08:31AM +0100, James Bensley wrote: > Open a TAC case, they'll probably tell you STP isn't supported and the > documentation is infact wrong, that is what has happened for me > recently with some ASR920s and ME3600s with a different feature than > STP :D That is

Re: [c-nsp] spanning-tree for local switching on ASR920

On 19/Oct/17 10:08, James Bensley wrote: > Open a TAC case, they'll probably tell you STP isn't supported and the > documentation is infact wrong, that is what has happened for me > recently with some ASR920s and ME3600s with a different feature than > STP :D I think the presence of any such

Re: [c-nsp] spanning-tree for local switching on ASR920

On 19/Oct/17 09:46, Gert Doering wrote: > I wasn't particularily asking for suggestions, but for "I have this > working, and this is how it looks like". > > This box is unlike any other Cisco "switch-like thing" I've had in my > hands before, so it might very well be just not supported at

Re: [c-nsp] spanning-tree for local switching on ASR920

On 19 October 2017 at 08:46, Gert Doering wrote: > Hi, > > On Thu, Oct 19, 2017 at 08:21:27AM +0100, James Bensley wrote: >> >> Then configure STP for VLAN "10". It doesn't seem like there is any way >> >> to map to an arbitrary PVST instance, VLAN ID and bridge domain ID has

Re: [c-nsp] spanning-tree for local switching on ASR920

Hi, On Thu, Oct 19, 2017 at 08:21:27AM +0100, James Bensley wrote: > >> Then configure STP for VLAN "10". It doesn't seem like there is any way > >> to map to an arbitrary PVST instance, VLAN ID and bridge domain ID has > >> to match. > > I don't know the answer to you question but Peter's

Re: [c-nsp] spanning-tree for local switching on ASR920

On 19 October 2017 at 07:46, Gert Doering wrote: > On Thu, Oct 19, 2017 at 06:05:47AM +0200, Peter Rathlev wrote: >> On Wed, 2017-10-18 at 15:39 +0200, Gert Doering wrote: >> > I have an ASR920 that is supposed to have gi0/0/10 and gi0/0/11 in >> > the same bridge group, with

Re: [c-nsp] spanning-tree for local switching on ASR920

Hi, On Thu, Oct 19, 2017 at 06:05:47AM +0200, Peter Rathlev wrote: > On Wed, 2017-10-18 at 15:39 +0200, Gert Doering wrote: > > I have an ASR920 that is supposed to have gi0/0/10 and gi0/0/11 in > > the same bridge group, with a routed IP: > > > > interface GigabitEthernet0/0/10 > >  no ip

Re: [c-nsp] spanning-tree for local switching on ASR920

On Wed, 2017-10-18 at 15:39 +0200, Gert Doering wrote: > I have an ASR920 that is supposed to have gi0/0/10 and gi0/0/11 in > the same bridge group, with a routed IP: > > interface GigabitEthernet0/0/10 >  no ip address >  media-type auto-select >  negotiation auto >  cdp enable >  service

[c-nsp] spanning-tree for local switching on ASR920

Hi, apologies if I've overlooked the obvious, but my google fu is failing me, and my "read cli help and guess" fu is not better today. I have an ASR920 that is supposed to have gi0/0/10 and gi0/0/11 in the same bridge group, with a routed IP: interface GigabitEthernet0/0/10 no ip address

Re: [c-nsp] spanning-tree P2P self-looped

Mohammad, what's on the other end of gig4/19? Could it be some WAN circuit and someone forgot to remove the loop test? On Mon, Dec 14, 2015, 17:37 Mohammad Khalil wrote: > Hi All > I have 7606 with ES20+ module > I have two active connections on this module , one is layer

[c-nsp] spanning-tree P2P self-looped

Hi All I have 7606 with ES20+ module I have two active connections on this module , one is layer 3 (point to point) link and the other one is the link of concern I have configured this link as a trunk with only Vlan 1700 is allowed , and SVI is configured for that Vlan interface G4/19

Re: [c-nsp] Spanning Tree works great - except when it doesn't

On 10/16/15, Jason Lixfeld wrote: > You could use RANCID, or you could use something like Ansible. Right - I can probably do it with RANCID. On every switch, collect the output from sh int trunk sh cdp nei and then save list of vlans defined (ie. "vlan xxx" or "xxx-yyy"

Re: [c-nsp] Spanning Tree works great - except when it doesn't

On 10/16/15, Ian Henderson wrote: > On 16 Oct 2015, at 11:23 AM, Lee wrote: >> Does anyone know of a program that will check all of the trunk ports >> on switches for vlans allowed + vlans allowed and active on both sides >> of a trunk port? > > Netdisco. I

Re: [c-nsp] Spanning Tree works great - except when it doesn't

On 16 Oct 2015, at 11:23 AM, Lee wrote: > Does anyone know of a program that will check all of the trunk ports > on switches for vlans allowed + vlans allowed and active on both sides > of a trunk port? Netdisco. ___ cisco-nsp mailing

Re: [c-nsp] Spanning Tree works great - except when it doesn't

You could use RANCID, or you could use something like Ansible. Bronwyn and Matt did a great NetDevOps presentation that described how you could use Ansible for things like that in Montreal a couple weeks back. https://www.youtube.com/watch?v=ArqvSGRzUBw > On Oct 15, 2015, at 8:23 PM, Lee

Re: [c-nsp] Spanning Tree works great - except when it doesn't

2015-10-15 11:37 skrev Patrick M. Hausen: Hi, all, we still rely on STP in our data centre. Top-of-rack switches are connected to two core switches with Gigabit configured as trunks. The two core switches have spanning-tree vlan 1-1005 priority 24576 and spanning-tree vlan

Re: [c-nsp] Spanning Tree works great - except when it doesn't

Subject: Re: [c-nsp] Spanning Tree works great - except when it doesn't Hello, first, thanks for all the questions. Precisely the kind of help I hoped for. While I'm really fluent with BGP and OSPF, I do not even know all the features you mention. STP has always "just worked" for us. OK, no

Re: [c-nsp] Spanning Tree works great - except when it doesn't

Hi, Nick, > Am 15.10.2015 um 13:43 schrieb Nick Cutting : > I came across a curly one like this a few months back - turned out the STP > handling of native VLan frames VS a non-created but configured native vlan on > the downstream switch port. > The downstream switchport

Re: [c-nsp] Spanning Tree works great - except when it doesn't

Hello, first, thanks for all the questions. Precisely the kind of help I hoped for. While I'm really fluent with BGP and OSPF, I do not even know all the features you mention. STP has always "just worked" for us. OK, now for some more details ... > Am 15.10.2015 um 12:11 schrieb

[c-nsp] Spanning Tree works great - except when it doesn't

Hi, all, we still rely on STP in our data centre. Top-of-rack switches are connected to two core switches with Gigabit configured as trunks. The two core switches have spanning-tree vlan 1-1005 priority 24576 and spanning-tree vlan 1-1005 priority 28672 respectively, to make

Re: [c-nsp] Spanning Tree works great - except when it doesn't

Regarding switches, what about the WS-C2960X-48TDL-RF; 3357$ list price. It is the refurbished version of WS-C2960X-48TD-L (5595$ list price). 48 copper gig ports and 2x SFP+ port for 10G uplink No real-life experience with the 2960X in general though. On Thu, Oct 15, 2015 at 4:27 PM, Chris Hunt

Re: [c-nsp] Spanning Tree works great - except when it doesn't

Nice one Nick. A three pointer from WAY outside the box.. -Chris On 10/15/2015 4:56 AM, Patrick M. Hausen wrote: > Hi, Nick, > >> Am 15.10.2015 um 13:43 schrieb Nick Cutting : >> I came across a curly one like this a few months back - turned out the STP >> handling of

Re: [c-nsp] Spanning Tree works great - except when it doesn't

>> The downstream switchport was also configured for native vlan of 999 - BUT >> vlan999 was not created in the vlan database so defaulted to ... Does anyone know of a program that will check all of the trunk ports on switches for vlans allowed + vlans allowed and active on both sides of a trunk

Re: [c-nsp] Spanning-tree ports cost Formula

-nsp@puck.nether.net Subject: Re: [c-nsp] Spanning-tree ports cost Formula Hi, I think what he is asking for is how try the values were extracted they are just default values for different interface types. I dont recall there being any formula (unlike eg OSPF/EIGRP calculations on links

Re: [c-nsp] Spanning-tree ports cost Formula

Hi, The newer versions of the STP standards (802.1D udpdated and 802.1W/S) have updated path cost values to cover higher speeds. a-ha! thanks for that - and the link! much appreciated...the ammo I need :-) alan ___ cisco-nsp mailing list

Re: [c-nsp] Spanning-tree ports cost Formula

...@hotmail.com CC: gunner_...@live.com; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Spanning-tree ports cost Formula Hi, I think what he is asking for is how try the values were extracted they are just default values for different interface types. I dont recall there being any formula

[c-nsp] Spanning-tree ports cost Formula

What is the formula to assign a value of 19 to FE interfaces and other values to other interfaces? ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive

Re: [c-nsp] Spanning-tree ports cost Formula

Hi! What is the formula to assign a value of 19 to FE interfaces and other values to other interfaces? It doesn't seem to be a formula, but a fixed table: http://packetlife.net/blog/2008/sep/5/spanning-tree-port-costs/ Lukas

Re: [c-nsp] Spanning-tree ports cost Formula

Hi, What is the formula to assign a value of 19 to FE interfaces and other values to other interfaces? cisco docs are searchable via google: http://www.cisco.com/en/US/tech/tk389/tk621/technologies_configuration_example09186a008009467c.shtml of course,

Re: [c-nsp] Spanning-tree ports cost Formula

I think what he is asking for is how try the values were extracted Date: Sat, 9 Nov 2013 14:33:41 + From: a.l.m.bu...@lboro.ac.uk To: gunner_...@live.com CC: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Spanning-tree ports cost Formula Hi, What is the formula to assign a value

Re: [c-nsp] Spanning-tree ports cost Formula

Hi, I think what he is asking for is how try the values were extracted they are just default values for different interface types. I dont recall there being any formula (unlike eg OSPF/EIGRP calculations on links). cant recall if its CCNA or CCNP SWITCH level stuff: Spanning tree port cost

Re: [c-nsp] Spanning Tree Instances

128 vlans by chance? http://sabotage-networks.blogspot.com/2010/02/cisco-gotchas-max-vlans-and-stp.html -Blake On Fri, Mar 23, 2012 at 7:48 AM, Leigh Harrison lharri...@convergencegroup.co.uk wrote: Hello all, ** ** We have run into an issue on a 3750 switch where it has run out of

Re: [c-nsp] Spanning Tree Instances

: Clive Webster cwebs...@convergencegroup.co.uk Subject: [c-nsp] Spanning Tree Instances Message-ID: BE13605B4C12654284C937196842A00020254F@condc02.ConvergenceGroup.local Content-Type: text/plain; charset=us-ascii Hello all, We have run into an issue on a 3750 switch where it has run

Re: [c-nsp] Spanning Tree Instances

Thus spake Leigh Harrison (lharri...@convergencegroup.co.uk) on Fri, Mar 23, 2012 at 12:48:06PM +: Hello all, We have run into an issue on a 3750 switch where it has run out of spanning tree instances. Is this a limitation of PVST or is it a limitation of the switch? I can't seem

Re: [c-nsp] Spanning Tree Instances

Hi all Please correct me if i'm wrong but i think this is related to a platform limitation. You will run into different (64 up to 256) spanning tree instances depending on the platform, specifically fixed switches. I am not sure about the modular catalyst. We had the same issue in the past,

Re: [c-nsp] Spanning-Tree vs. EoMPLS links in SXI2?

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

[c-nsp] Spanning Tree Instances

Hello all, We have run into an issue on a 3750 switch where it has run out of spanning tree instances. Is this a limitation of PVST or is it a limitation of the switch? I can't seem to find good clarity anywhere. I have some 6509's and nexus 7k's and I'm wondering if they're going to suffer

[c-nsp] Spanning-Tree

HiDoes the difference in the STP mode configured between two switches block the BPDUs from being sent over the trunk connection between the two switches? Thanks ___ cisco-nsp mailing list cisco-nsp@puck.nether.net

Re: [c-nsp] Spanning-Tree

Hi, On Mon, Apr 15, 2013 at 05:14:33PM +0300, M K wrote: HiDoes the difference in the STP mode configured between two switches block the BPDUs from being sent over the trunk connection between the two switches? Only on Fridays. (It would help to give a more reasonable answer if you stated

Re: [c-nsp] spanning tree on me3600x

-nsp] spanning tree on me3600x Hi Aaron See: http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.2_4_S/configuration/guide/swevc.html#wp1002521 *When STP mode is PVST+ or PVRST, EFP information is not passed to the protocol. EVC only supports only MSTP. We're running

[c-nsp] spanning tree on me3600x

I don't see any instances of spanning tree running for various efp's I've created in my ME3600. Is there something different with spanning tree and the Me3600x that is much different than older cisco switches ? voice-3600#sh spanning-tree interface g0/4 efp 336 no spanning tree info

Re: [c-nsp] spanning tree on me3600x

Hi Aaron See: http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.2_4_S/configuration/guide/swevc.html#wp1002521 •When STP mode is PVST+ or PVRST, EFP information is not passed to the protocol. EVC only supports only MSTP. We're running Rapid-PVST but it only

[c-nsp] Spanning Tree help sought

Good day, I'm new to Spanning Trees and have read up on them, but need advice and guidance. I have the manuals and can set STP up - it is the design that is my concern. My LAN is more complicated than this, but the following example will help me explain. I have four switches (A, B, C D)

Re: [c-nsp] Spanning Tree help sought

On Thursday, November 15, 2012 8:14 AM, Christopher Gray wrote: I'm new to Spanning Trees and have read up on them, but need advice and guidance. I have the manuals and can set STP up - it is the design that is my concern. My LAN is more complicated than this, but the following example

Re: [c-nsp] Spanning Tree help sought

On Thu, 15 Nov 2012, Christopher Gray wrote: I have four switches (A, B, C D) linked in a loop comprising 1Gbps fibre. Switch A is connected to a primary WAN router while switch C is connected to the secondary WAN router - the two routers working in a simple HSRP fail-over set. I want to

Re: [c-nsp] Spanning Tree help sought

Ross, Thank you for that: I'm new to Spanning Trees and have read up on them, but need advice and guidance. I have the manuals and can set STP up - it is design that is my concern. My LAN is more complicated than this, but the following example will help me explain. Quick word of

Re: [c-nsp] Spanning Tree help sought

On Thu, 15 Nov 2012, Christopher Gray wrote: On reading your response - and used the links you suggested - I note that I could just leave everything as default and let STP sort itself out. You could...but you really should dictate which switches are the root bridge and backup root bridge.

Re: [c-nsp] Spanning Tree help sought

Justin, I have four switches (A, B, C D) linked in a loop comprising 1Gbps fibre. Switch A is connected to a primary WAN router while switch C is connected to the secondary WAN router - the two routers working in a simple HSRP fail-over set. I want to ensure that this loop will

Re: [c-nsp] Spanning Tree help sought

Gray Cc: 'Ross Halliday'; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Spanning Tree help sought On Thu, 15 Nov 2012, Christopher Gray wrote: On reading your response - and used the links you suggested - I note that I could just leave everything as default and let STP sort itself out. You could

[c-nsp] Spanning-Tree Cisco(Nexus 7k) x Juniper

Dear all, I am experiencing problems with trunks between Nexus and Juniper switches. The network is intermittent, and some hosts do not communicate with each other on the same segment. Could you show me some tips and best practices for interoperability between Cisco and Juniper Networks? for

Re: [c-nsp] Spanning-Tree Cisco(Nexus 7k) x Juniper

What issues are you seeing? One thing to check is that on cisco devices you should specify the long version of costing. Cisco hasn't updated their default to match the newer rfc out there. This alone could be causing your problems. On Aug 30, 2011 10:47 AM, Alessandro Braga sandro.u...@gmail.com

[c-nsp] Spanning-tree boundaries and configuration

Hi, For service provider network how does the spanning-tree boundaries should be configured? And with which options? Should I participate the customer STP in my topology for preventing loops and broadcast storms or ignoring his BPDU's totally? Lately we have some STP problems due to mismatch

Re: [c-nsp] Spanning-tree boundaries and configuration

On Fri, 2011-06-24 at 09:10 +0300, techt...@gmail.com wrote: For service provider network how does the spanning-tree boundaries should be configured? And with which options? Should I participate the customer STP in my topology for preventing loops and broadcast storms or ignoring his BPDU's

Re: [c-nsp] Spanning-tree boundaries and configuration

Peter Rathlev ha scritto: Should I participate the customer STP in my topology for preventing loops and broadcast storms or ignoring his BPDU's totally? ... Otherwise there's AFAICT no way around joining the STP domain of your customers. In that case you should of course try to make sure

[c-nsp] spanning-tree portfast network ??

Does anybody know what the new SXI spanning tree command does ... spanning-tree portfast network I understand and use PORTFAST but the NETWORK option has me stumped. The doc does not explain what the NETWORK option really does. Thanks for any help. Jeff Fitzwater Princeton University

Re: [c-nsp] spanning-tree portfast network ??

-Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Jeff Fitzwater Sent: Thursday, December 16, 2010 11:34 AM To: cisco-nsp@puck.nether.net Subject: [c-nsp] spanning-tree portfast network ?? Does anybody know what the new SXI

Re: [c-nsp] Spanning-Tree Loop (12.2.18SXF7)

-feira, 5 de Novembro de 2010 22:38 To: 'Tony Varriale'; 'cisco-nsp' Subject: Re: [c-nsp] Spanning-Tree Loop (12.2.18SXF7) Everything is resolved. As I mentioned, the 6500 recovered from this by itself. The debuginfo file that was created as the same format as the crashinfo files with lots of stack

[c-nsp] Spanning-Tree Loop (12.2.18SXF7)

Hello group, I'm troubleshooting a STP loop that seemed to be triggered by these errors: %PM_SCP-SP-3-LCP_FW_ABLC: Late collision message from module 1, port:029 %IPC-SP-5-WATERMARK: 15612 messages pending in xmt for the port CHKPT:STANDBY SP(208.B) seat

Re: [c-nsp] Spanning-Tree Loop (12.2.18SXF7)

There could have been any sort of a memory leak since SXF7 and now that caused you to see this. How long was your device up? I hate to say this, but I would go to recent software (eg: SXF15a/SXF16). - Jared On Nov 5, 2010, at 12:25 PM, Antonio Soares wrote: Hello group, I'm

Re: [c-nsp] Spanning-Tree Loop (12.2.18SXF7)

: [c-nsp] Spanning-Tree Loop (12.2.18SXF7) There could have been any sort of a memory leak since SXF7 and now that caused you to see this. How long was your device up? I hate to say this, but I would go to recent software (eg: SXF15a/SXF16). - Jared On Nov 5, 2010, at 12:25 PM, Antonio Soares

Re: [c-nsp] Spanning-Tree Loop (12.2.18SXF7)

, CCIE #18473 (RS/SP) amsoa...@netcabo.pt -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Antonio Soares Sent: sexta-feira, 5 de Novembro de 2010 17:15 To: 'Jared Mauch' Cc: 'cisco-nsp' Subject: Re: [c-nsp] Spanning-Tree

Re: [c-nsp] Spanning-Tree Loop (12.2.18SXF7)

Antonio, Your SP couldn't allocate 1768 bytes of memory from the I/O pool for a spanning tree update because the I/O pool's free 148112 bytes was so fragmented it couldn't find a contiguous block of 1768 bytes. This does not necessarily point to a bug. Eliminating spanning tree storms and a

Re: [c-nsp] Spanning-Tree Loop (12.2.18SXF7)

...@puck.nether.net Cc: 'cisco-nsp' cisco-nsp@puck.nether.net Sent: Friday, November 05, 2010 1:33 PM Subject: Re: [c-nsp] Spanning-Tree Loop (12.2.18SXF7) Interesting, the switch did not crash but a debugfile was generated. And something I can read from that file

Re: [c-nsp] Spanning-Tree Loop (12.2.18SXF7)

for the first time. Thanks. Regards, Antonio Soares, CCIE #18473 (RS/SP) mailto:amsoa...@netcabo.pt amsoa...@netcabo.pt From: Eninja [mailto:eni...@gmail.com] Sent: sexta-feira, 5 de Novembro de 2010 20:17 To: Antonio Soares Cc: cisco-nsp Subject: Re: [c-nsp] Spanning-Tree Loop

Re: [c-nsp] Spanning-Tree Loop (12.2.18SXF7)

-boun...@puck.nether.net] On Behalf Of Tony Varriale Sent: sexta-feira, 5 de Novembro de 2010 20:40 To: 'cisco-nsp' Subject: Re: [c-nsp] Spanning-Tree Loop (12.2.18SXF7) Could be. What's the rest of the file and sh proc cpu say? I'd find out what's eating all that memory first. Also, your

[c-nsp] Spanning-tree problem

I have three 6509-E daisy chain together i know that's not the best design but it was working fine until this morning. for some reason the second switch took over as the root bridge i changed the spanning tree cost to a higher number and it still claiming to be the bridge. i do a sho

Re: [c-nsp] Spanning-tree problem

- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Renelson Panosky Sent: Thursday, June 03, 2010 8:10 AM To: cisco-nsp@puck.nether.net Subject: [c-nsp] Spanning-tree problem I have three 6509-E daisy chain together i know that's not the best design

Re: [c-nsp] Spanning-Tree vs. EoMPLS links in SXI2?

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

Re: [c-nsp] Spanning-Tree vs. EoMPLS links in SXI2?

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=

Re: [c-nsp] Spanning-Tree vs. EoMPLS links in SXI2?

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

Re: [c-nsp] Spanning-Tree vs. EoMPLS links in SXI2?

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

Re: [c-nsp] Spanning-Tree vs. EoMPLS links in SXI2?

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

Re: [c-nsp] Spanning-Tree vs. EoMPLS links in SXI2?

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

Re: [c-nsp] Spanning-Tree vs. EoMPLS links in SXI2?

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

Re: [c-nsp] Spanning-Tree vs. EoMPLS links in SXI2?

-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

Re: [c-nsp] Spanning-Tree vs. EoMPLS links in SXI2?

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

Re: [c-nsp] Spanning-Tree vs. EoMPLS links in SXI2?

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.

Re: [c-nsp] Spanning-Tree vs. EoMPLS links in SXI2?

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

Re: [c-nsp] Spanning-Tree vs. EoMPLS links in SXI2?

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

Re: [c-nsp] Spanning-Tree vs. EoMPLS links in SXI2?

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

Re: [c-nsp] Spanning-Tree vs. EoMPLS links in SXI2?

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.

Re: [c-nsp] Spanning-Tree vs. EoMPLS links in SXI2?

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

Re: [c-nsp] Spanning-Tree vs. EoMPLS links in SXI2?

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

  1   2   >