[f-nsp] Spanning tree on brocade

[Eldon Koyle]

You can run 802-1w either as a single instance or per-vlan.

Since all of our VLANs go the same way, we use 'spanning-tree single
802-1w' (which changes the single spanning tree instance to rstp) to
save some CPU.  Then just make sure that 'spanning-tree' is enabled in
each VLAN, which will make them a member of the single spanning tree
instance.  We also configure all of our edge ports with
"stp-bpdu-guard" and "spanning-tree 802-1w admin-edge-port", as Jethro
suggested.

How big of a meltdown was it?  We have seen that deleting a VLAN can
cause brocade switches to move every port to blocking and restart the
entire STP process (this may only be with single spanning tree).
Also, loops can do unexpected things with single spanning tree since
not every port has every VLAN (another argument for 802-1w and setting
admin-edge-port anywhere you can).

-- 
Eldon

On Wed, May 18, 2016 at 8:37 AM, Nick Cutting <ncutting at edgetg.com> wrote:
> No routing at all
>
>
>
> The meltdown is almost certainly the result of 6 Fastirons, 2 turboIrons
> running a combination of IEEE, 802.1w and No spanning tree at all. Ive
> diagrammed this now for each vlan, and I have found some serious deisgn
> issues.
>
>
> MGT wanted me to figure out what happened, All I can think about is how to
> fix this – i.e 801.w everywhere, on all vlans – It seems that this runs as a
> per-vlan spanning tree flavor?
>
>
>
> NickC
>
>
>
> From: Nick Hilliard [mailto:nick at foobar.org]
> Sent: Wednesday, May 18, 2016 10:28 AM
> To: Eldon Koyle
> Cc: Nick Cutting; foundry-nsp
> Subject: Re: [f-nsp] Spanning tree on brocade
>
>
>
> Eldon Koyle wrote:
>
>
>> That is _really_ old code on the turboiron. It may be the version they
>> shipped with, which was extremely buggy. You are correct that it is
>> routing code (TIR is routing, TIS is switching). Are you doing any
>> routing on that device?
>
> old and buggy, but stp on 4.02.00c was fine. If there was an STP
> meltdown, it's more likely to have been the result of a network misconfig.
>
> 7.3.00f was the next usable version of the tix code after 4.02.00c.
> Upgrading would be a really good idea, not least due to the unicast
> flooding problem in all versions of the turboiron code before 7.3
> (DEFECT000362191).
>
> Nick
>