Wired Intelligent Edge

last person joined: 2 days ago 

Bring performance and reliability to your network with the HPE Aruba Networking Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of your switching devices, and find ways to improve security across your network to bring together a mobile-first solution
Back to discussions
Expand all | Collapse all

Aruba 3800 LACP policy

This thread has been viewed 2 times

  • 1.  Aruba 3800 LACP policy

    Posted Jul 04, 2020 05:01 AM

    Hi all, I have an Aruba 3800 24SFP 2SFP+ Switch and was wondering if LACP can work in Layer 3 or Layer 4 policy, based on the fact that my switch is classified as Layer 3, but could't find in documentation.



  • 2.  RE: Aruba 3800 LACP policy
    Best Answer

    MVP GURU
    Posted Jul 06, 2020 06:04 AM

    The fact that the load balancing algorithm is engineered to use (benefit) of Layer 4 information has no direct relationship with the Layer 2 or 3 capability of your switch (there are Layer 3 switch not capable to use Layer 4 on LACP).

     

    The Aruba 3810M should support (as the Aruba 5400R zl2) the Layer 4 load balancing through the trunk-load-balance [L3-based|L4-based] CLI global command as per Aruba 3810M/5400R zl2 Management and Configuration Guide for ArubaOS-Switch 16.10:

     

    L4_LACP.png

     

     

     



  • 3.  RE: Aruba 3800 LACP policy

    Posted Jul 06, 2020 02:46 PM

    Thank you for answer, but I am looking to connect a debian server, by the "trunk-load-balance [L3-based|L4-based]" you mean common LACP or special logic link between switches, because linux bonding driver support only standard protocol.



  • 4.  RE: Aruba 3800 LACP policy

    MVP GURU
    Posted Jul 06, 2020 03:18 PM

    Hi, if you're going to create a bond type 4 (AKA IEEE 802.3ad LACP) host side, you must do the same switch side.

     

    The Layer 3/4 setting acts globally at switch level and the Link Aggregation configuration - say you have a two ports port trunking with LACP, that translates into trunk n,m trkX lacp on the Aruba 3810M - is valid for any peer you're connecting through aggregated links.

     

    LAGs simply gather, if available, L4 or L3 info to calculate the egressing port for outgoing traffic through the links aggregation interface (the same could be done - it's not mandatory - host side).