<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)"><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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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>Daniel,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The feedback I received from another consultant is that perhaps the topology change seen by VLAN 294 passed down from the ICX6610 to our core router (Cisco 7600), but since we don’t have dual-mode enabled on the Brocade the core router’s PVST updates to the ICX6610 (which are typically on VLAN 1, untagged) resulted in the LAG between the ICX6610 and core router being torn down.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We’re planning to move to RSTP or RPVST.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Frank<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>From:</b> Daniel Schmidt <daniel.schmidt@wyo.gov> <br><b>Sent:</b> Tuesday, October 16, 2018 1:54 PM<br><b>To:</b> frnkblk@iname.com<br><b>Cc:</b> foundry-nsp@puck.nether.net<br><b>Subject:</b> Re: [f-nsp] Spanning-tree event on single VLAN brings down LAG?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>If you have a lag, perhaps you have no loops and can filter bpdu's to see if it stops happening. Also consider rstp instead of stp. <o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Thu, Oct 11, 2018 at 4:33 PM Frank Bulk <<a href="mailto:frnkblk@iname.com">frnkblk@iname.com</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>We did not expect the “1/3/8, 2/3/8, 3/3/4, 3/3/8” LAG to drop, either – two network engineering consultants that I’ve shared this with don’t have good theories yet, either.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>You’re right, the ICX6610 could have just been documenting the LAG member drops instead of initiating it, I just don’t know how to figure that out.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Frank <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>From:</b> Howard, Christopher <<a href="mailto:Christopher-Howard@utc.edu" target="_blank">Christopher-Howard@utc.edu</a>> <br><b>Sent:</b> Thursday, October 11, 2018 8:55 AM<br><b>To:</b> <a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a>; <a href="mailto:frnkblk@iname.com" target="_blank">frnkblk@iname.com</a><br><b>Subject:</b> Re: [f-nsp] Spanning-tree event on single VLAN brings down LAG?<o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Looking at your log, 1/3/6 is where the block event happened. I would not expect the 6610 to have dropped the lag because of this, no matter which version of spanning tree you're running, because 1/3/6 is not a part of that lag. <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Just some ideas: <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>- It could have been dropped on the other end by either the same or an unrelated event and you're just seeing the documentation of that on the 6610. <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>- I've seen before where a loop drove the switch CPU high enough to flap lags. Since spanning tree blocked the port that should have protected the CPU, unless there are other ports not participating in spanning tree on that vlan.<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>- A coincidence, but I admit the chances of that are unlikely with the timing of the lag drop.<o:p></o:p></p></div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>-Christopher<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Thu, 2018-10-11 at 08:07 -0500, <a href="mailto:frnkblk@iname.com" target="_blank">frnkblk@iname.com</a> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #729FCF 1.5pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Christopher,<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Thanks for sharing. Your explanation regarding vlan enablement versus port disablement makes sense to me. <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I plan to turn up 802.1w in a future maintenance window.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>From the Brocade ICX6610 logs is it clear if the ICX6610 turned down the 10G ports, or did the core router link it down and the ICX6610 was merely documenting that it was being pulled down?<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Frank <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>From:</b> Howard, Christopher <<a href="mailto:Christopher-Howard@utc.edu" target="_blank">Christopher-Howard@utc.edu</a>> <br><b>Sent:</b> Wednesday, October 10, 2018 12:32 PM<br><b>To:</b> <a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a>; <a href="mailto:frnkblk@iname.com" target="_blank">frnkblk@iname.com</a><br><b>Subject:</b> Re: [f-nsp] Spanning-tree event on single VLAN brings down LAG?<o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>One vlan getting blocked by spanning tree should not bring down the lag. The vlan should only block on the interfaces required to remove the loop. As far as I know, if you have spanning tree enabled on the vlan, but disabled on the physical port, then the physical port no longer participates in spanning tree for any vlan.<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Here's config from one of my switches. This is an ICX7750 with 8.0.30r code, same code that ICX6610 can run.<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><pre>lag lag-name dynamic id 1<o:p></o:p></pre><pre> ports ethernet 1/1/2 ethernet 2/1/2 <o:p></o:p></pre><pre> primary-port 1/1/2<o:p></o:p></pre><pre> deploy<o:p></o:p></pre><pre>!<o:p></o:p></pre><pre>vlan 123 name vlan-name by port<o:p></o:p></pre><pre> tagged ethe 1/1/2 ethe 2/1/2<o:p></o:p></pre><pre> spanning-tree 802-1w<o:p></o:p></pre><pre>!<o:p></o:p></pre><pre>interface ethernet 1/1/2<o:p></o:p></pre><pre> spanning-tree 802-1w admin-pt2pt-mac<o:p></o:p></pre><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>A snipped output from "show 802-1w" below with vlans in both discarding and forwarding states on that lag.<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>--- VLAN 404 [ STP Instance owned by VLAN 404 ] ----------------------------<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>1/1/2 128 2000 T F ALTERNATE DISCARDING 2000 0001609c9fd73700 <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>--- VLAN 999 [ STP Instance owned by VLAN 999 ] ----------------------------<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>1/1/2 128 2000 T F ALTERNATE DISCARDING 2000 0001609c9fd73700 <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>--- VLAN 2007 [ STP Instance owned by VLAN 2007 ] ---------------------------<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>1/1/2 128 2000 T F ROOT FORWARDING 0 0000609c9fd73700 <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>--- VLAN 2057 [ STP Instance owned by VLAN 2057 ] ---------------------------<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>1/1/2 128 2000 T F ROOT FORWARDING 0 0000609c9fd73700 <o:p></o:p></p></div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>-Christopher<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Wed, 2018-10-10 at 11:59 -0500, Frank Bulk wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #729FCF 1.5pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><pre>We had network event deeper in our network that resulted in some kind of<o:p></o:p></pre><pre>spanning tree event as evidenced by a TC (topology change) on our L2-only<o:p></o:p></pre><pre>ICX6610 stack. What surprised us was that one VLAN going into a blocking<o:p></o:p></pre><pre>state resulted in the south bound LAG going down.<o:p></o:p></pre><pre> <o:p></o:p></pre><pre>This is probably not right, but the root bridge for VLAN 294 is on the<o:p></o:p></pre><pre>ICX6610 stack. VLAN 294 is on both LAGs (and no other port/LAG)<o:p></o:p></pre><pre> <o:p></o:p></pre><pre>Three questions:<o:p></o:p></pre><pre>a) when a STP event occurs is it normal that a VLAN goes into Blocking on<o:p></o:p></pre><pre>all the ports where it is present?<o:p></o:p></pre><pre>b) when a VLAN goes into blocking should all the physical (or LAG) ports<o:p></o:p></pre><pre>associated with that VLAN go down?<o:p></o:p></pre><pre>c) does configuring spanning tree on the port-based VLAN but disabling<o:p></o:p></pre><pre>spanning-tree on the physical (or LAG) ports prevent the physical port (or<o:p></o:p></pre><pre>LAG) going down?<o:p></o:p></pre><pre> <o:p></o:p></pre><pre>Frank<o:p></o:p></pre><pre> <o:p></o:p></pre><pre>============================================================================<o:p></o:p></pre><pre>====<o:p></o:p></pre><pre>Oct 9 21:35:22 STP: VLAN 294 Port 1/3/6 Bridge TC Event (MakeBlking) <o:p></o:p></pre><pre>Oct 9 21:35:22 STP: VLAN 294 Port 1/3/6 STP State -> BLOCKING (MakeBlking) <o:p></o:p></pre><pre>Oct 9 21:35:25 System: Logical link on dynamic lag interface ethernet 2/3/8<o:p></o:p></pre><pre>is down. <o:p></o:p></pre><pre>Oct 9 21:35:25 System: Logical link on dynamic lag interface ethernet 3/3/4<o:p></o:p></pre><pre>is down. <o:p></o:p></pre><pre>Oct 9 21:35:26 System: Logical link on dynamic lag interface ethernet 3/3/8<o:p></o:p></pre><pre>is down. <o:p></o:p></pre><pre>Oct 9 21:35:29 Trunk: Group (1/3/8, 2/3/8, 3/3/4, 3/3/8) removed by 802.3ad<o:p></o:p></pre><pre>link-aggregation module. <o:p></o:p></pre><pre>Oct 9 21:35:29 STP: VLAN 4 Port 1/3/8 STP State -> BLOCKING (PortDown) <o:p></o:p></pre><pre>Oct 9 21:35:29 STP: VLAN 4 Port 1/3/8 STP State -> DISABLED (PortDown)<o:p></o:p></pre><pre>etc.<o:p></o:p></pre><pre> <o:p></o:p></pre><pre> Event<o:p></o:p></pre><pre> |<o:p></o:p></pre><pre>Transport<o:p></o:p></pre><pre> | | <o:p></o:p></pre><pre> | | (1/3/6 & 2/3/6)<o:p></o:p></pre><pre> | | <o:p></o:p></pre><pre>ICX6610 (L2)<o:p></o:p></pre><pre> | | | |<o:p></o:p></pre><pre> | | | | (1/3/8, 2/3/8, 3/3/4, 3/3/8)<o:p></o:p></pre><pre> | | | |<o:p></o:p></pre><pre>Core (L3)<o:p></o:p></pre><pre> <o:p></o:p></pre><pre> <o:p></o:p></pre><pre> <o:p></o:p></pre><pre>_______________________________________________<o:p></o:p></pre><pre>foundry-nsp mailing list<o:p></o:p></pre><pre><a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><o:p></o:p></pre><pre><a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><o:p></o:p></pre><pre> <o:p></o:p></pre></blockquote></blockquote></div></div><p class=MsoNormal>_______________________________________________<br>foundry-nsp mailing list<br><a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br><a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><o:p></o:p></p></blockquote></div><p class=MsoNormal><br><br>E-Mail to and from me, in connection with the transaction <br>of public business, is subject to the Wyoming Public Records <br>Act and may be disclosed to third parties.<o:p></o:p></p></div></body></html>