<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">It was a 4 hour layer2 loop.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I would rather per-vlan rapid everywhere – and this is general plan going forward.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">One switch had no spanning tree at all – this is definitely the culprit (I will not find the trigger)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I’m going to add syslog to all devices to our syslog-ng server<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Do I need to run a command to make sure spanning tree events are sent to the syslog?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><br>
Thank you all Brocade experts )<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> ekoyle@gmail.com [mailto:ekoyle@gmail.com]
<b>On Behalf Of </b>Eldon Koyle<br>
<b>Sent:</b> Wednesday, May 18, 2016 12:10 PM<br>
<b>To:</b> Nick Cutting<br>
<b>Cc:</b> foundry-nsp<br>
<b>Subject:</b> Re: [f-nsp] Spanning tree on brocade<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">You can run 802-1w either as a single instance or per-vlan.<br>
<br>
Since all of our VLANs go the same way, we use 'spanning-tree single<br>
802-1w' (which changes the single spanning tree instance to rstp) to<br>
save some CPU. Then just make sure that 'spanning-tree' is enabled in<br>
each VLAN, which will make them a member of the single spanning tree<br>
instance. We also configure all of our edge ports with<br>
"stp-bpdu-guard" and "spanning-tree 802-1w admin-edge-port", as Jethro<br>
suggested.<br>
<br>
How big of a meltdown was it? We have seen that deleting a VLAN can<br>
cause brocade switches to move every port to blocking and restart the<br>
entire STP process (this may only be with single spanning tree).<br>
Also, loops can do unexpected things with single spanning tree since<br>
not every port has every VLAN (another argument for 802-1w and setting<br>
admin-edge-port anywhere you can).<br>
<br>
-- <br>
Eldon<br>
<br>
On Wed, May 18, 2016 at 8:37 AM, Nick Cutting <<a href="mailto:ncutting@edgetg.com%3e">ncutting@edgetg.com></a> wrote:<br>
> No routing at all<br>
><br>
><br>
><br>
> The meltdown is almost certainly the result of 6 Fastirons, 2 turboIrons<br>
> running a combination of IEEE, 802.1w and No spanning tree at all. Ive<br>
> diagrammed this now for each vlan, and I have found some serious deisgn<br>
> issues.<br>
><br>
><br>
> MGT wanted me to figure out what happened, All I can think about is how to<br>
> fix this – i.e 801.w everywhere, on all vlans – It seems that this runs as a<br>
> per-vlan spanning tree flavor?<br>
><br>
><br>
><br>
> NickC<br>
><br>
><br>
><br>
> From: Nick Hilliard [<a href="mailto:nick@foobar.org">mailto:nick@foobar.org</a>]<br>
> Sent: Wednesday, May 18, 2016 10:28 AM<br>
> To: Eldon Koyle<br>
> Cc: Nick Cutting; foundry-nsp<br>
> Subject: Re: [f-nsp] Spanning tree on brocade<br>
><br>
><br>
><br>
> Eldon Koyle wrote:<br>
><br>
><br>
>> That is _really_ old code on the turboiron. It may be the version they<br>
>> shipped with, which was extremely buggy. You are correct that it is<br>
>> routing code (TIR is routing, TIS is switching). Are you doing any<br>
>> routing on that device?<br>
><br>
> old and buggy, but stp on 4.02.00c was fine. If there was an STP<br>
> meltdown, it's more likely to have been the result of a network misconfig.<br>
><br>
> 7.3.00f was the next usable version of the tix code after 4.02.00c.<br>
> Upgrading would be a really good idea, not least due to the unicast<br>
> flooding problem in all versions of the turboiron code before 7.3<br>
> (DEFECT000362191).<br>
><br>
> Nick<br>
><br>
<br>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
</body>
</html>