<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic RE: Port flap on LACP load sharing group causes permanent network loop in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/port-flap-on-lacp-load-sharing-group-causes-permanent-network/m-p/36974#M7739</link>
    <description>Case open for 3 weeks.</description>
    <pubDate>Thu, 05 Jun 2014 01:27:00 GMT</pubDate>
    <dc:creator>Tim_DeNike</dc:creator>
    <dc:date>2014-06-05T01:27:00Z</dc:date>
    <item>
      <title>Port flap on LACP load sharing group causes permanent network loop</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/port-flap-on-lacp-load-sharing-group-causes-permanent-network/m-p/36972#M7737</link>
      <description>Had a neat issue that killed our network the other day.  Tracked it down to a flaky port on a single switch that was connected to a stack with LACP.  I was able to reproduce the problem.&lt;BR /&gt;
&lt;BR /&gt;
Take a stack and LACP load share one port from each stack member to 2 ports on another switch, send some multicast traffic across it (VRRP or ELRP is enough), then unplug and plug in one of the ports several times.&lt;BR /&gt;
&lt;BR /&gt;
Eventually, the LACP link will stop forwarding within the confines of the algorith and it turns the ports into a big L2 loop.  Doesnt seem to happen with static sharing, just LACP.  Reproduced on x450e-48p, but appears to happen on x460s as well, 15.3.3.5p1-2&lt;BR /&gt;</description>
      <pubDate>Wed, 04 Jun 2014 17:04:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/port-flap-on-lacp-load-sharing-group-causes-permanent-network/m-p/36972#M7737</guid>
      <dc:creator>Tim_DeNike</dc:creator>
      <dc:date>2014-06-04T17:04:00Z</dc:date>
    </item>
    <item>
      <title>RE: Port flap on LACP load sharing group causes permanent network loop</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/port-flap-on-lacp-load-sharing-group-causes-permanent-network/m-p/36973#M7738</link>
      <description>Please call the TAC and report the bug.</description>
      <pubDate>Thu, 05 Jun 2014 00:04:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/port-flap-on-lacp-load-sharing-group-causes-permanent-network/m-p/36973#M7738</guid>
      <dc:creator>Sumit_Tokle</dc:creator>
      <dc:date>2014-06-05T00:04:00Z</dc:date>
    </item>
    <item>
      <title>RE: Port flap on LACP load sharing group causes permanent network loop</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/port-flap-on-lacp-load-sharing-group-causes-permanent-network/m-p/36974#M7739</link>
      <description>Case open for 3 weeks.</description>
      <pubDate>Thu, 05 Jun 2014 01:27:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/port-flap-on-lacp-load-sharing-group-causes-permanent-network/m-p/36974#M7739</guid>
      <dc:creator>Tim_DeNike</dc:creator>
      <dc:date>2014-06-05T01:27:00Z</dc:date>
    </item>
    <item>
      <title>RE: Port flap on LACP load sharing group causes permanent network loop</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/port-flap-on-lacp-load-sharing-group-causes-permanent-network/m-p/36975#M7740</link>
      <description>Can I have case number?</description>
      <pubDate>Thu, 05 Jun 2014 10:35:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/port-flap-on-lacp-load-sharing-group-causes-permanent-network/m-p/36975#M7740</guid>
      <dc:creator>Sumit_Tokle</dc:creator>
      <dc:date>2014-06-05T10:35:00Z</dc:date>
    </item>
  </channel>
</rss>

