Wired Intelligent Edge (Campus Switching and Routing)

Reply
Highlighted
New Contributor

Aruba 3800 LACP policy

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.


Accepted Solutions
Highlighted
MVP Guru

Re: Aruba 3800 LACP policy

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

 

 

 

View solution in original post


All Replies
Highlighted
MVP Guru

Re: Aruba 3800 LACP policy

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

 

 

 

View solution in original post

Highlighted
New Contributor

Re: Aruba 3800 LACP policy

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.

Highlighted
MVP Guru

Re: Aruba 3800 LACP policy

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).

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: