LACP configuration
Team,
I'm trying to setup an LAG with LACP.
On the switch site, I use lacp-passive with "source and desination mac" address hashing.
On the server side, I use lacp-active with "layer2" hashing.
Not sure if these two are doing exactly the same calculation.
The bond-port comes up but without lacp response (source: /var/log/syslog).
As a validation I did a tcpdump on the server with "tcpdump -v -ni bond0 ether proto 0x8809" there are no lacp packets.
I also tried a tcpdump on the corresponding vmbr0 interface and the 2 underlying physical ethernet ports - same result.
The settings on the server side are:
# Add enp1s0 to bond0 auto enp1s0 iface enp1s0 inet manual bond-master bond0 bond-primary enp1s0 # Dito for enp5s0 auto enp5s0 iface enp5s0 inet manual bond-master bond0 # The bonding network interface auto bond0 iface bond0 inet dhcp bond-slaves enp1s0 enp5s0 bond-mode 4
It looks like the current result is that only one interface is used - no load balancing.
Any suggestions?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @ITV,
Did you configure server connection as Bonding? Bonding is similar, but not the same as LACP.
- Copy Link
- Report Inappropriate Content
I don't understand your question - please elaborate.
In addition: did you notice the posted server config?
It says bonding mode 4 for 2 interfaces - meaning lacp/802.3ad for 2 interfaces.
- Copy Link
- Report Inappropriate Content
@ITV, I looked at the config, but not obvious (at least to me) it was LACP. What OS/version are you using?
- Copy Link
- Report Inappropriate Content
No problem - thank you for your time and patience!
OS and version:
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
This is the version with Proxmox 8.3.2 community edition and stable channel.
I also have Ubuntu running - same issue - OS version:
PRETTY_NAME="Ubuntu 24.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.1 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
- Copy Link
- Report Inappropriate Content
Hi @ITV
Thanks for posting in our business forum.
This discussion should be brought up on the LINUX Reddit which might be more effective in order to get an answer. We do not offer support beyond the Omada switch.
- Copy Link
- Report Inappropriate Content
Well - I probably will have (more-or-less) the same answer because the Linux guys can argue that they don't support Omada switches.
Om top of that there is a difference in terminology and features.
On Linux it say layer2 hashing. On Omada it says source-mac-and-destination-mac. Is this the same? If yes - does this include the hashing algoritm for the calculation?
On Linux I can hashing om L2 and L3 at the same time. While the Omada switches can not - its either L2 or L3.
It is my believe that dropping this question here is more effective because this boils down to the question: to what extend are the Omada switches supporting 802.3ad? Which can only be answered by...
- Copy Link
- Report Inappropriate Content
Hi @ITV
Thanks for posting in our business forum.
ITV wrote
Well - I probably will have (more-or-less) the same answer because the Linux guys can argue that they don't support Omada switches.
Om top of that there is a difference in terminology and features.
On Linux it say layer2 hashing. On Omada it says source-mac-and-destination-mac. Is this the same? If yes - does this include the hashing algoritm for the calculation?
On Linux I can hashing om L2 and L3 at the same time. While the Omada switches can not - its either L2 or L3.
It is my believe that dropping this question here is more effective because this boils down to the question: to what extend are the Omada switches supporting 802.3ad? Which can only be answered by...
If it is layer 2, it is MAC. That's correct.
Omada only has two hash policies, either L2 or L3. Not gonna be both.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 112
Replies: 7
Voters 0
No one has voted for it yet.