<div dir="ltr"><div>Which flavor of spanning tree are you running?</div><div><br></div><div>-- <br></div><div>Eldon<br></div></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Oct 10, 2018 at 11:32 AM Howard, Christopher <<a href="mailto:Christopher-Howard@utc.edu">Christopher-Howard@utc.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="text-align:left;direction:ltr">
<div>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.</div>
<div><br>
</div>
<div><br>
</div>
<div>Here's config from one of my switches. This is an ICX7750 with 8.0.30r code, same code that ICX6610 can run.</div>
<div><br>
</div>
<pre>lag lag-name dynamic id 1</pre>
<pre> ports ethernet 1/1/2 ethernet 2/1/2 </pre>
<pre> primary-port 1/1/2</pre>
<pre> deploy</pre>
<pre>!</pre>
<pre>vlan 123 name vlan-name by port</pre>
<pre> tagged ethe 1/1/2 ethe 2/1/2</pre>
<pre> spanning-tree 802-1w</pre>
<pre>!</pre>
<pre>interface ethernet 1/1/2</pre>
<pre> spanning-tree 802-1w admin-pt2pt-mac</pre>
<div><br>
</div>
<div><br>
</div>
<div>A snipped output from "show 802-1w" below with vlans in both discarding and forwarding states on that lag.</div>
<div><br>
</div>
<div>--- VLAN 404 [ STP Instance owned by VLAN 404 ] ----------------------------</div>
<div>1/1/2 128 2000 T F ALTERNATE DISCARDING 2000 0001609c9fd73700 </div>
<div><br>
</div>
<div>--- VLAN 999 [ STP Instance owned by VLAN 999 ] ----------------------------</div>
<div>1/1/2 128 2000 T F ALTERNATE DISCARDING 2000 0001609c9fd73700 </div>
<div><br>
</div>
<div>--- VLAN 2007 [ STP Instance owned by VLAN 2007 ] ---------------------------</div>
<div>1/1/2 128 2000 T F ROOT FORWARDING 0 0000609c9fd73700 </div>
<div><br>
</div>
<div>--- VLAN 2057 [ STP Instance owned by VLAN 2057 ] ---------------------------</div>
<div>1/1/2 128 2000 T F ROOT FORWARDING 0 0000609c9fd73700 </div>
<div></div>
<div></div>
<div><span>
<div><br>
</div>
<div>-Christopher</div>
<div><br>
</div>
</span></div>
<div><br>
</div>
<div>On Wed, 2018-10-10 at 11:59 -0500, Frank Bulk wrote:</div>
<blockquote type="cite" style="margin:0 0 0 .8ex;border-left:2px #729fcf solid;padding-left:1ex">
<pre>We had network event deeper in our network that resulted in some kind of</pre>
<pre>spanning tree event as evidenced by a TC (topology change) on our L2-only</pre>
<pre>ICX6610 stack. What surprised us was that one VLAN going into a blocking</pre>
<pre>state resulted in the south bound LAG going down.</pre>
<pre><br></pre>
<pre>This is probably not right, but the root bridge for VLAN 294 is on the</pre>
<pre>ICX6610 stack. VLAN 294 is on both LAGs (and no other port/LAG)</pre>
<pre><br></pre>
<pre>Three questions:</pre>
<pre>a) when a STP event occurs is it normal that a VLAN goes into Blocking on</pre>
<pre>all the ports where it is present?</pre>
<pre>b) when a VLAN goes into blocking should all the physical (or LAG) ports</pre>
<pre>associated with that VLAN go down?</pre>
<pre>c) does configuring spanning tree on the port-based VLAN but disabling</pre>
<pre>spanning-tree on the physical (or LAG) ports prevent the physical port (or</pre>
<pre>LAG) going down?</pre>
<pre><br></pre>
<pre>Frank</pre>
<pre><br></pre>
<pre>============================================================================</pre>
<pre>====</pre>
<pre>Oct 9 21:35:22 STP: VLAN 294 Port 1/3/6 Bridge TC Event (MakeBlking) </pre>
<pre>Oct 9 21:35:22 STP: VLAN 294 Port 1/3/6 STP State -> BLOCKING (MakeBlking) </pre>
<pre>Oct 9 21:35:25 System: Logical link on dynamic lag interface ethernet 2/3/8</pre>
<pre>is down. </pre>
<pre>Oct 9 21:35:25 System: Logical link on dynamic lag interface ethernet 3/3/4</pre>
<pre>is down. </pre>
<pre>Oct 9 21:35:26 System: Logical link on dynamic lag interface ethernet 3/3/8</pre>
<pre>is down. </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</pre>
<pre>link-aggregation module. </pre>
<pre>Oct 9 21:35:29 STP: VLAN 4 Port 1/3/8 STP State -> BLOCKING (PortDown) </pre>
<pre>Oct 9 21:35:29 STP: VLAN 4 Port 1/3/8 STP State -> DISABLED (PortDown)</pre>
<pre>etc.</pre>
<pre><br></pre>
<pre> Event</pre>
<pre> |</pre>
<pre>Transport</pre>
<pre> | | </pre>
<pre> | | (1/3/6 & 2/3/6)</pre>
<pre> | | </pre>
<pre>ICX6610 (L2)</pre>
<pre> | | | |</pre>
<pre> | | | | (1/3/8, 2/3/8, 3/3/4, 3/3/8)</pre>
<pre> | | | |</pre>
<pre>Core (L3)</pre>
<pre> </pre>
<pre><br></pre>
<pre><br></pre>
<pre>_______________________________________________</pre>
<pre>foundry-nsp mailing list</pre>
<pre><a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a></pre>
<pre><a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a></pre>
<pre><br></pre>
</blockquote>
</div>
_______________________________________________<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" rel="noreferrer" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
</blockquote></div>