<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>Plain STP as this time.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>From:</b> foundry-nsp <foundry-nsp-bounces@puck.nether.net> <b>On Behalf Of </b>Eldon Koyle<br><b>Sent:</b> Wednesday, October 10, 2018 3:32 PM<br><b>To:</b> foundry-nsp <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><div><p class=MsoNormal>Which flavor of spanning tree are you running?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>-- <o:p></o:p></p></div><div><p class=MsoNormal>Eldon<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Wed, Oct 10, 2018 at 11:32 AM Howard, Christopher <<a href="mailto:Christopher-Howard@utc.edu">Christopher-Howard@utc.edu</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><p class=MsoNormal>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><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>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><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><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>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><o:p> </o:p></p></div><div><p class=MsoNormal>--- VLAN 404 [ STP Instance owned by VLAN 404 ] ----------------------------<o:p></o:p></p></div><div><p class=MsoNormal>1/1/2 128 2000 T F ALTERNATE DISCARDING 2000 0001609c9fd73700 <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>--- VLAN 999 [ STP Instance owned by VLAN 999 ] ----------------------------<o:p></o:p></p></div><div><p class=MsoNormal>1/1/2 128 2000 T F ALTERNATE DISCARDING 2000 0001609c9fd73700 <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>--- VLAN 2007 [ STP Instance owned by VLAN 2007 ] ---------------------------<o:p></o:p></p></div><div><p class=MsoNormal>1/1/2 128 2000 T F ROOT FORWARDING 0 0000609c9fd73700 <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>--- VLAN 2057 [ STP Instance owned by VLAN 2057 ] ---------------------------<o:p></o:p></p></div><div><p class=MsoNormal>1/1/2 128 2000 T F ROOT FORWARDING 0 0000609c9fd73700 <o:p></o:p></p></div><div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>-Christopher<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>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-right:0in'><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><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></div></body></html>