[f-nsp] Spanning tree on brocade

Nick Cutting ncutting at edgetg.com
Wed May 18 10:37:35 EDT 2016


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

________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20160518/af1b6b31/attachment-0001.html>


More information about the foundry-nsp mailing list