<?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: Lossless LACP recovery? in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lossless-lacp-recovery/m-p/49710#M13223</link>
    <description>Hi Zsolt, &lt;BR /&gt;
&lt;BR /&gt;
I don't believe EXOS supports lossless recovery for LACP.&lt;BR /&gt;
&lt;BR /&gt;
I would recommend you to try some actions (if not yet done) like:&lt;BR /&gt;
&lt;UL&gt; 
&lt;LI&gt;Change the Linux Ubuntu machines from passive to active mode&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt; 
&lt;LI&gt;Change the sharing algorithm in EXOS from l2 to l3_l4 (you will need to delete and create the LAG again)&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt; 
&lt;LI&gt;Change the lacp timeout from long to short&lt;/LI&gt;&lt;/UL&gt;                    &lt;I&gt;configure sharing &lt;MASTER_PORT&gt; lacp timeout short&lt;BR /&gt;
&lt;BR /&gt;
&lt;/MASTER_PORT&gt;&lt;/I&gt;&lt;B&gt;Note:&lt;/B&gt; Since the issue is related when the port goes down/up, LACP timeout might not fix the issue, but I think it's worth a try. &lt;I&gt;&lt;BR /&gt;
&lt;/I&gt;</description>
    <pubDate>Wed, 30 Mar 2016 17:56:00 GMT</pubDate>
    <dc:creator>Henrique</dc:creator>
    <dc:date>2016-03-30T17:56:00Z</dc:date>
    <item>
      <title>Lossless LACP recovery?</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lossless-lacp-recovery/m-p/49709#M13222</link>
      <description>We configure LAG/LACP with "algorithm address-based L2 lacp" mode and on host side Ubuntu Linux machines are  in mode passive from LACP aspect (bond_mode=balance-slb, lacp=passive). However when link recovery happens - one of the links was offline then gets online again - significant packet loss occurs even on the earlier active link which was used for traffic forwarding. Is there any way configuring a lossless recovery with LACP? (Something like this: &lt;A href="https://www.ibm.com/support/knowledgecenter/ssw_aix_71/com.ibm.aix.networkcomm/lossless_rcvr.htm" target="_blank" rel="nofollow noreferrer noopener"&gt;https://www.ibm.com/support/knowledgecenter/ssw_aix_71/com.ibm.aix.networkcomm/lossless_rcvr.htm&lt;/A&gt;)&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 30 Mar 2016 14:48:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lossless-lacp-recovery/m-p/49709#M13222</guid>
      <dc:creator>Zsolt_Babindai</dc:creator>
      <dc:date>2016-03-30T14:48:00Z</dc:date>
    </item>
    <item>
      <title>RE: Lossless LACP recovery?</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lossless-lacp-recovery/m-p/49710#M13223</link>
      <description>Hi Zsolt, &lt;BR /&gt;
&lt;BR /&gt;
I don't believe EXOS supports lossless recovery for LACP.&lt;BR /&gt;
&lt;BR /&gt;
I would recommend you to try some actions (if not yet done) like:&lt;BR /&gt;
&lt;UL&gt; 
&lt;LI&gt;Change the Linux Ubuntu machines from passive to active mode&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt; 
&lt;LI&gt;Change the sharing algorithm in EXOS from l2 to l3_l4 (you will need to delete and create the LAG again)&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt; 
&lt;LI&gt;Change the lacp timeout from long to short&lt;/LI&gt;&lt;/UL&gt;                    &lt;I&gt;configure sharing &lt;MASTER_PORT&gt; lacp timeout short&lt;BR /&gt;
&lt;BR /&gt;
&lt;/MASTER_PORT&gt;&lt;/I&gt;&lt;B&gt;Note:&lt;/B&gt; Since the issue is related when the port goes down/up, LACP timeout might not fix the issue, but I think it's worth a try. &lt;I&gt;&lt;BR /&gt;
&lt;/I&gt;</description>
      <pubDate>Wed, 30 Mar 2016 17:56:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lossless-lacp-recovery/m-p/49710#M13223</guid>
      <dc:creator>Henrique</dc:creator>
      <dc:date>2016-03-30T17:56:00Z</dc:date>
    </item>
    <item>
      <title>RE: Lossless LACP recovery?</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lossless-lacp-recovery/m-p/49711#M13224</link>
      <description>Hi Henrique,&lt;BR /&gt;
&lt;BR /&gt;
Thank you for your response but we have tried as many LACP options and configuration as possible with no luck. We have to conclude that there is no way to change this behaviour.&lt;BR /&gt;
&lt;BR /&gt;
Br,&lt;BR /&gt;
Zsolt&lt;BR /&gt;</description>
      <pubDate>Thu, 31 Mar 2016 11:51:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lossless-lacp-recovery/m-p/49711#M13224</guid>
      <dc:creator>Zsolt_Babindai</dc:creator>
      <dc:date>2016-03-31T11:51:00Z</dc:date>
    </item>
    <item>
      <title>RE: Lossless LACP recovery?</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lossless-lacp-recovery/m-p/49712#M13225</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
with 21.1 we are introducing resilient hashing, which might help in your case (if your platform support 21.1). Have a look at it.&lt;BR /&gt;</description>
      <pubDate>Thu, 31 Mar 2016 14:31:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lossless-lacp-recovery/m-p/49712#M13225</guid>
      <dc:creator>Stephane_Grosj1</dc:creator>
      <dc:date>2016-03-31T14:31:00Z</dc:date>
    </item>
  </channel>
</rss>

