Help: Enabling LACP (802.3ad) results in loss of connectivity with TRENDnet TEG-3284WS

Michael Conrad

New Member
Feb 13, 2025
1
0
1
LACP is not working for me. Whenever I switch the bond from `balance-alb` to `LACP (802.34ad)` in the ProxMox UI and apply it, all communications cease. I have to then login via the iDRAC console, (via a docker image), to login and change the bond back to `balance-alb` to regain operational status.

## Systems:

* 2 each Dell R710, using onboard NICs, 4 ports.
* 1 each Dell R730xd, using onboard NICs, 4 ports.
* 1 each TRENDnet Switch TEG-3284WS

### Switch

ports 21-24, untagged vlan 1, tagged vlan 2
trunk 1, LACP Active, ports 21-24

### ProxMox

```bash
auto lo
iface lo inet loopback

auto eno2
iface eno2 inet manual

auto eno1
iface eno1 inet manual

auto eno3
iface eno3 inet manual

auto eno4
iface eno4 inet manual

auto bond0
iface bond0 inet manual
bond-slaves eno1 eno2 eno3 eno4
bond-miimon 100
bond-mode balance-alb
#Production

auto vmbr0
iface vmbr0 inet static
address 192.168.1.4/24
gateway 192.168.1.1
bridge-ports bond0
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4094

source /etc/network/interfaces.d/*
```

```bash
cat sdn
#version:5

auto test
iface test
bridge_ports vmbr0.2
bridge_stp off
bridge_fd 0
```