LACP up with receive lacp-bpdu

  • 1
  • Idea
  • Updated 2 years ago
  • Implemented
Hi, all!

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.

Can we do this in Summit X770?

As I know in Summit LAG-LACP links is up only when receive lacp-bpdu.
Need to connect with servers.

Thank you!
Photo of Alexandr P

Alexandr P, Embassador

  • 12,042 Points 10k badge 2x thumb

Posted 3 years ago

  • 1
Photo of Prashanth KG

Prashanth KG, Employee

  • 5,300 Points 5k badge 2x thumb
Official Response
HI Alexandr,

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. 

For the clear-flow solution, refer the following article: 
https://gtacknowledge.extremenetworks.com/articles/How_To/LACP-configured-ports-interfere-with-PXE-DHCP-on-servers

For the UPM solution, refer the following article: 

https://gtacknowledge.extremenetworks.com/articles/Solution/Work-around-for-LACP-fallback-backup-feature-support-in-EXOS

I have tested the UPM solution in my lab, it seems to work fine: 

Sharing enabled on the connected device: 
Load Sharing MonitorConfig    Current    Agg       Ld Share    Ld Share  Agg   Link    Link Up
Master    Master     Control   Algorithm   Group     Mbr   State   Transitions
==============================================================================
   1:1    1:1        LACP      L2          1:1        Y      A        1
                               L2          1:2        Y      A        1
==============================================================================
Link State: A-Active, D-Disabled, R-Ready, NP-Port not present, L-Loopback
Load Sharing Algorithm: (L2) Layer 2 address based, (L3) Layer 3 address based
                        (L3_L4) Layer 3 address and Layer 4 port based
                        (custom) User-selected address-based configuration
Custom Algorithm Configuration: ipv4 L3-and-L4, xor
Number of load sharing trunks: 1
* Slot-1 Stack.9 # sh log10/07/2015 03:20:21.30 <Info:LACP.AddPortToAggr> Slot-1: Add port 1:2 to aggregator
10/07/2015 03:20:21.30 <Info:LACP.AddPortToAggr> Slot-1: Add port 1:1 to aggregator
10/07/2015 03:20:19.08 <Info:System.userComment> Slot-1: Enabled_share_1:1
10/07/2015 03:20:18.94 <Noti:UPM.Msg.upmMsgExshLaunch> Slot-1: Launched profile dynamiclacp for the event UPM Timer check_lacp_timer
Sharing disabled on the connected device: 
* Slot-1 Stack.10 # sh log10/07/2015 03:22:19.16 <Info:System.userComment> Slot-1: Disabled_share_1:1
10/07/2015 03:22:18.97 <Noti:UPM.Msg.upmMsgExshLaunch> Slot-1: Launched profile dynamiclacp for the event UPM Timer check_lacp_timer
10/07/2015 03:21:38.93 <Noti:UPM.Msg.upmMsgExshLaunch> Slot-1: Launched profile dynamiclacp for the event UPM Timer check_lacp_timer
10/07/2015 03:21:14.86 <Info:LACP.RemPortFromAggr> Slot-1: Remove port 1:2 from aggregator
10/07/2015 03:21:14.86 <Info:LACP.RemPortFromAggr> Slot-1: Remove port 1:1 from aggregator
* Slot-1 Stack.10 # sh sharing
Load Sharing Monitor
Config    Current    Agg       Ld Share    Ld Share  Agg   Link    Link Up
Master    Master     Control   Algorithm   Group     Mbr   State   Transitions
==============================================================================
==============================================================================
Link State: A-Active, D-Disabled, R-Ready, NP-Port not present, L-Loopback
Load Sharing Algorithm: (L2) Layer 2 address based, (L3) Layer 3 address based
                        (L3_L4) Layer 3 address and Layer 4 port based
                        (custom) User-selected address-based configuration
Custom Algorithm Configuration: ipv4 L3-and-L4, xor
Number of load sharing trunks: 0
I would suggest doing more tests before implementing in production. 

Hope this helps! 

P.S. 
Thanks to Oscar Koot for both the solutions.