<?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: LACP up with receive lacp-bpdu in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lacp-up-with-receive-lacp-bpdu/m-p/47041#M12031</link>
    <description>Thank you a lot!!!</description>
    <pubDate>Wed, 07 Oct 2015 09:47:00 GMT</pubDate>
    <dc:creator>Alexandr_P</dc:creator>
    <dc:date>2015-10-07T09:47:00Z</dc:date>
    <item>
      <title>LACP up with receive lacp-bpdu</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lacp-up-with-receive-lacp-bpdu/m-p/47037#M12027</link>
      <description>Hi, all!&lt;BR /&gt;
&lt;BR /&gt;
I heared that Cisco and Juniper switches have behavior (configure lacp) that ports working in stand-alone mode, but when receive lacp-bpdu then these ports became a LAG LACP.&lt;BR /&gt;
&lt;BR /&gt;
Can we do this in Summit X770?&lt;BR /&gt;
&lt;BR /&gt;
As I know in Summit LAG-LACP links is up only when receive lacp-bpdu.&lt;BR /&gt;
Need to connect with servers.&lt;BR /&gt;
&lt;BR /&gt;
Thank you!</description>
      <pubDate>Mon, 05 Oct 2015 19:17:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lacp-up-with-receive-lacp-bpdu/m-p/47037#M12027</guid>
      <dc:creator>Alexandr_P</dc:creator>
      <dc:date>2015-10-05T19:17:00Z</dc:date>
    </item>
    <item>
      <title>RE: LACP up with receive lacp-bpdu</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lacp-up-with-receive-lacp-bpdu/m-p/47038#M12028</link>
      <description>Hi Alexandr,&lt;BR /&gt;
This feature, as I understand it to be implemented in a future EXOS release, is called LACP Fallback.&lt;BR /&gt;
The LACP Fallback feature lets the user select a single port which will be automatically added to the aggregator if LACPDUs are not seen on any of the member ports within specified period of time.&lt;BR /&gt;
&lt;BR /&gt;
At present, I can't provide a specific release version or date (sorry!), but I see that it's in the works.  If there's something similar to this that already exists, I'm hopeful that someone will call it out here &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;
&lt;BR /&gt;
-Drew</description>
      <pubDate>Mon, 05 Oct 2015 20:01:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lacp-up-with-receive-lacp-bpdu/m-p/47038#M12028</guid>
      <dc:creator>Drew_C</dc:creator>
      <dc:date>2015-10-05T20:01:00Z</dc:date>
    </item>
    <item>
      <title>RE: LACP up with receive lacp-bpdu</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lacp-up-with-receive-lacp-bpdu/m-p/47039#M12029</link>
      <description>Can we try to use ACL with? &lt;BR /&gt;
if - lacp-bpdu &lt;BR /&gt;
then - run in CLI "ena sh 1 gr 1-2 "&lt;BR /&gt;
&lt;BR /&gt;
Thank you!</description>
      <pubDate>Mon, 05 Oct 2015 20:01:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lacp-up-with-receive-lacp-bpdu/m-p/47039#M12029</guid>
      <dc:creator>Alexandr_P</dc:creator>
      <dc:date>2015-10-05T20:01:00Z</dc:date>
    </item>
    <item>
      <title>RE: LACP up with receive lacp-bpdu</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lacp-up-with-receive-lacp-bpdu/m-p/47040#M12030</link>
      <description>HI Alexandr,&lt;BR /&gt;
&lt;BR /&gt;
As Drew pointed out, this is in the roadmap for the future EXOS releases. Work-around can be implemented using ACL and UPM or clear-flow and ACL. &lt;BR /&gt;
&lt;BR /&gt;
For the clear-flow solution, refer the following article: &lt;BR /&gt;
&lt;A href="https://gtacknowledge.extremenetworks.com/articles/How_To/LACP-configured-ports-interfere-with-PXE-DHCP-on-servers" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/How_To/LACP-configured-ports-interfere-with-PXE-DHCP-on-servers&lt;/A&gt; &lt;BR /&gt;
&lt;BR /&gt;
For the UPM solution, refer the following article: &lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://gtacknowledge.extremenetworks.com/articles/Solution/Work-around-for-LACP-fallback-backup-feature-support-in-EXOS" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/Solution/Work-around-for-LACP-fallback-backup-feature-support-in-EXOS&lt;/A&gt; &lt;BR /&gt;
&lt;BR /&gt;
I have tested the UPM solution in my lab, it seems to work fine: &lt;BR /&gt;
&lt;BR /&gt;
Sharing enabled on the connected device: &lt;BR /&gt;
Load Sharing MonitorConfig    Current    Agg       Ld Share    Ld Share  Agg   Link    Link Up&lt;BR /&gt;
Master    Master     Control   Algorithm   Group     Mbr   State   Transitions&lt;BR /&gt;
==============================================================================&lt;BR /&gt;
   1:1    1:1        LACP      L2          1:1        Y      A        1&lt;BR /&gt;
                               L2          1:2        Y      A        1&lt;BR /&gt;
==============================================================================&lt;BR /&gt;
Link State: A-Active, D-Disabled, R-Ready, NP-Port not present, L-Loopback&lt;BR /&gt;
Load Sharing Algorithm: (L2) Layer 2 address based, (L3) Layer 3 address based&lt;BR /&gt;
                        (L3_L4) Layer 3 address and Layer 4 port based&lt;BR /&gt;
                        (custom) User-selected address-based configuration&lt;BR /&gt;
Custom Algorithm Configuration: ipv4 L3-and-L4, xor&lt;BR /&gt;
Number of load sharing trunks: 1* Slot-1 Stack.9 # sh log10/07/2015 03:20:21.30 &lt;I&gt; Slot-1: Add port 1:2 to aggregator&lt;BR /&gt;
10/07/2015 03:20:21.30 &lt;I&gt; Slot-1: Add port 1:1 to aggregator&lt;BR /&gt;
10/07/2015 03:20:19.08 &lt;I&gt; Slot-1: Enabled_share_1:1&lt;BR /&gt;
10/07/2015 03:20:18.94 &lt;UPM.MSG.UPMMSGEXSHLAUNCH&gt; Slot-1: Launched profile dynamiclacp for the event UPM Timer check_lacp_timer&lt;BR /&gt;
Sharing disabled on the connected device: &lt;BR /&gt;
* Slot-1 Stack.10 # sh log10/07/2015 03:22:19.16 &lt;I&gt; Slot-1: Disabled_share_1:1&lt;BR /&gt;
10/07/2015 03:22:18.97 &lt;UPM.MSG.UPMMSGEXSHLAUNCH&gt; Slot-1: Launched profile dynamiclacp for the event UPM Timer check_lacp_timer&lt;BR /&gt;
10/07/2015 03:21:38.93 &lt;UPM.MSG.UPMMSGEXSHLAUNCH&gt; Slot-1: Launched profile dynamiclacp for the event UPM Timer check_lacp_timer&lt;BR /&gt;
10/07/2015 03:21:14.86 &lt;I&gt; Slot-1: Remove port 1:2 from aggregator&lt;BR /&gt;
10/07/2015 03:21:14.86 &lt;I&gt; Slot-1: Remove port 1:1 from aggregator&lt;BR /&gt;
* Slot-1 Stack.10 # sh sharing&lt;BR /&gt;
Load Sharing Monitor&lt;BR /&gt;
Config    Current    Agg       Ld Share    Ld Share  Agg   Link    Link Up&lt;BR /&gt;
Master    Master     Control   Algorithm   Group     Mbr   State   Transitions&lt;BR /&gt;
==============================================================================&lt;BR /&gt;
==============================================================================&lt;BR /&gt;
Link State: A-Active, D-Disabled, R-Ready, NP-Port not present, L-Loopback&lt;BR /&gt;
Load Sharing Algorithm: (L2) Layer 2 address based, (L3) Layer 3 address based&lt;BR /&gt;
                        (L3_L4) Layer 3 address and Layer 4 port based&lt;BR /&gt;
                        (custom) User-selected address-based configuration&lt;BR /&gt;
Custom Algorithm Configuration: ipv4 L3-and-L4, xor&lt;BR /&gt;
Number of load sharing trunks: 0I would suggest doing more tests before implementing in production. &lt;BR /&gt;
&lt;BR /&gt;
Hope this helps! &lt;BR /&gt;
&lt;BR /&gt;
P.S. &lt;BR /&gt;
Thanks to Oscar Koot for both the solutions. &lt;BR /&gt;
&lt;BR /&gt;&lt;/I&gt;&lt;/I&gt;&lt;/UPM.MSG.UPMMSGEXSHLAUNCH&gt;&lt;/UPM.MSG.UPMMSGEXSHLAUNCH&gt;&lt;/I&gt;&lt;/UPM.MSG.UPMMSGEXSHLAUNCH&gt;&lt;/I&gt;&lt;/I&gt;&lt;/I&gt;</description>
      <pubDate>Wed, 07 Oct 2015 09:47:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lacp-up-with-receive-lacp-bpdu/m-p/47040#M12030</guid>
      <dc:creator>Prashanth_KG</dc:creator>
      <dc:date>2015-10-07T09:47:00Z</dc:date>
    </item>
    <item>
      <title>RE: LACP up with receive lacp-bpdu</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lacp-up-with-receive-lacp-bpdu/m-p/47041#M12031</link>
      <description>Thank you a lot!!!</description>
      <pubDate>Wed, 07 Oct 2015 09:47:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lacp-up-with-receive-lacp-bpdu/m-p/47041#M12031</guid>
      <dc:creator>Alexandr_P</dc:creator>
      <dc:date>2015-10-07T09:47:00Z</dc:date>
    </item>
    <item>
      <title>RE: LACP up with receive lacp-bpdu</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lacp-up-with-receive-lacp-bpdu/m-p/47042#M12032</link>
      <description>Hello, all!&lt;BR /&gt;
&lt;BR /&gt;
FYI&lt;BR /&gt;
LACP Fallback is appear in EXOS in 21.1 version.&lt;BR /&gt;
&lt;BR /&gt;
Thank you!</description>
      <pubDate>Fri, 18 Mar 2016 12:32:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/lacp-up-with-receive-lacp-bpdu/m-p/47042#M12032</guid>
      <dc:creator>Alexandr_P</dc:creator>
      <dc:date>2016-03-18T12:32:00Z</dc:date>
    </item>
  </channel>
</rss>

