802.3ad LACP Link Aggregation Setup Guide for Switches & NAS

Updated 2026-10-09 • By Elena Rostova, CCNP (Network Infrastructure Architect)

To configure IEEE 802.3ad Dynamic Link Aggregation Control Protocol (LACP) without locking yourself out of your network, first enable the LACP bond on your downstream NAS or secondary switch, and then group the matching switch ports into an Active LACP LAG using a Layer 2+3 (MAC + IP) load-balance hash. Remember that 802.3ad increases multi-client aggregate capacity and failover redundancy, never single-stream TCP speed.

Key Technical Takeaways
  • Aggregate Capacity vs Single-Stream Speed: Bonding two 1GbE ports via 802.3ad LACP gives two simultaneous clients 1 Gbps each (2 Gbps total) and instant cable failover, but one single TCP stream never exceeds 1 Gbps.
  • Dynamic LACP Beats Static LAG: Always select 802.3ad Dynamic LACP rather than Static LAG so switches exchange LACP Data Units (LACPDUs) on multicast MAC 01:80:C2:00:00:02 to prevent switching loops.
  • Upgrade Hash Mode to L2+L3/L4: Change your switch's LAG hashing algorithm from default Src/Dst MAC to Src/Dst MAC + IP + TCP/UDP Port for even traffic distribution across inter-switch trunks.
  • Avoid Management Lockout: Always connect your laptop to an unbonded switch port when building or deleting an LACP trunk.

How IEEE 802.3ad / 802.1AX LACP Works (And the Single-Stream Myth)

Link Aggregation Control Protocol (originally standardized in IEEE 802.3ad and migrated to IEEE 802.1AX) bundles two to eight physical full-duplex Ethernet ports of identical speed into a single logical interface called a Link Aggregation Group (LAG), Port-Channel, or Bond. To Spanning Tree Protocol (802.1D/802.1w), the bonded bundle appears as one logical link, preventing STP from blocking redundant parallel cables between switches.

However, IEEE 802.3ad strictly prohibits splitting packets from the same TCP/UDP conversation across multiple physical wires because tiny differences in cable length or queue depth would cause packets to arrive out of order, triggering catastrophic TCP retransmissions. Instead, the switch runs a deterministic XOR hash on each packet header. Think of a 2x 1GbE LACP bond not as a 140-mph highway, but as expanding a one-lane 70-mph road into a two-lane 70-mph highway: one car still drives at 70 mph, but two cars can travel side-by-side at 70 mph each with instant lane failover if one cable fails.

Dynamic LACP (802.3ad) vs Static LAG vs Adaptive Load Balancing

When configuring link aggregation on a managed switch, NAS, or Linux Proxmox host (`bonding`), you will encounter three primary operating modes:

  • IEEE 802.3ad Dynamic LACP (Linux mode=4 / 802.3ad): Both the switch and the endpoint actively negotiate the bond using LACPDUs every 1 second (Fast LACP) or 30 seconds (Slow LACP). If a cable is accidentally patched into the wrong switch port, LACP detects the partner mismatch and withholds the port from the bundle instead of causing a broadcast storm.
  • Static LAG / EtherChannel Mode ON (Linux mode=0 / balance-rr or mode=2 / balance-xor): Forces aggregation with zero negotiation protocol. If one side reboots into a factory state before the other, a severe Layer 2 switching loop can bring down your entire LAN.
  • Adaptive Load Balancing / Balance-ALB (Linux mode=6): Used on NAS appliances connected to unmanaged switches. It balances outbound and inbound ARP traffic without switch configuration, though SMB3 Multichannel is far superior for 1-to-1 file transfers.

Step-by-Step LACP Setup on Ubiquiti UniFi, TP-Link Omada & Netgear

To avoid losing web access to your NAS or downstream switch during setup, connect your workstation to an unbonded port on the main switch and configure the endpoint first:

  • Ubiquiti UniFi Network 8.x+: UniFi requires LACP member ports to be consecutive (e.g., Ports 7 and 8). Open UniFi Devices > [Select Switch] > Port Manager, click the lower port number (Port 7), change Operation from Switching to Aggregate, select ending port 8, and click Apply. UniFi automatically negotiates 802.3ad Dynamic LACP.
  • TP-Link Omada / JetStream: Navigate to L2 Features > Switching > LAG > LACP Config. Select LAG1, set LAG Type to LACP (never Static), check your member ports, and set Hash Algorithm to SRC MAC + DST MAC + SRC IP + DST IP.
  • Netgear Smart Managed Pro / Plus: Go to Switching > LAG > Advanced > LAG Configuration, set LAG Type to LACP, assign member ports, and ensure the VLAN PVID and tagged VLAN trunk membership on the logical ch1/lag1 interface match your physical ports.

VLAN Trunking Over LACP & Choosing the Right Load-Balance Hash

A critical pitfall on managed switches from Cisco CBS, MikroTik SwOS/RouterOS, Netgear, and TP-Link is that VLAN assignments apply to the logical LAG interface (`Po1`, `LAG1`, or `bond1`), not to the underlying physical ports (`gi1/0/7` and `gi1/0/8`). Once you group physical ports into `LAG1`, navigate to your switch's 802.1Q VLAN menu and assign your Untagged PVID and Tagged VLANs (`10, 20, 30`) directly to the `LAG1` logical trunk.

Finally, inspect your switch's global LAG hash policy. Entry-level switches default to Layer 2 (Source/Destination MAC) hashing. Because all traffic crossing a router gateway or targeting a single NAS shares the same MAC address pair, a Layer 2 hash often dumps 80% of traffic onto Cable 1 while leaving Cable 2 idle. Upgrading the hash policy to Layer 2+3 (MAC + IP) or Layer 3+4 (IP + TCP/UDP Port) balances multiple streams across all member links evenly.

Link Aggregation Modes Compared: LACP vs Static LAG vs SMB3 vs Balance-ALB

Aggregation MethodSwitch RequirementSingle-Client Max Speed (2x 2.5GbE)Multi-Client / Failover Behavior
IEEE 802.3ad Dynamic LACPManaged Switch with LACP enabled2.5 Gbps (1 link per TCP stream)5.0 Gbps across 2+ clients; automatic LACPDU loop protection
Static LAG (Mode ON / XOR)Managed Switch with Static LAG2.5 Gbps (1 link per hash)5.0 Gbps across 2+ clients; high risk of switching loop if miswired
Adaptive Load Balancing (ALB)Any Unmanaged or Managed Switch2.5 Gbps (ARP-based balancing)5.0 Gbps across multiple IP clients; zero switch config needed
Active-Backup Failover (Mode 1)Any Switch (or two separate switches)2.5 Gbps (1 active, 1 standby)2.5 Gbps total; survives complete switch failure across dual switches
SMB3 Multichannel (No LAG)Any Unmanaged or Managed Switch5.0 Gbps (Stripes 1 client across 2 NICs)5.0 Gbps for single or multiple SMB3 workstations; best for NAS

802.3ad LACP Switch & NAS Configuration Checklist

  1. Confirm both Ethernet ports negotiate identical speed and full-duplex settings and use matching Cat6/Cat6a patch cables.
  2. Connect your admin PC to an independent switch port that is not part of the planned LACP bundle.
  3. Enable IEEE 802.3ad Dynamic LACP on the downstream NAS or secondary switch first before saving the upstream switch LAG.
  4. Use consecutive switch port numbers (e.g., Ports 7–8) if configuring a Ubiquiti UniFi switch.
  5. Re-apply your 802.1Q Tagged VLANs and Untagged PVID to the newly created logical LAG interface (LAG1 / Po1).
  6. Set the switch LAG load-balancing hash algorithm to Src/Dst MAC + IP (L2+L3) and verify Partner Status shows Active/Collecting/Distributing.

Frequently Asked Questions

Should I use 802.3ad LACP or SMB3 Multichannel for my home NAS?

If you have 1 to 3 workstations and want a single PC or Mac to transfer files at 2x speed (such as 550 MB/s over dual 2.5GbE), disable LACP and use SMB3 Multichannel instead. Use 802.3ad LACP primarily for switch-to-switch uplink trunks or office servers accessed simultaneously by 10+ client machines.

Can I combine 802.3ad LACP and SMB3 Multichannel at the same time?

No, not effectively over a single bond. When you create an 802.3ad bond on your NAS, the OS hides the two physical NICs behind one virtual bond0 interface with a single IP address, which prevents SMB3 Multichannel from detecting multiple independent NIC queues and caps single-client speed back to one physical cable.

What is the difference between LACP Active and LACP Passive mode?

An Active LACP port transmits LACP negotiation packets (LACPDUs) unconditionally, whereas a Passive LACP port waits silently until it receives an LACPDU from its partner. At least one side of the link must be set to Active (Active-Active is industry best practice); setting both sides to Passive prevents the LAG from ever forming.

Can I connect one cable of an 802.3ad LACP bond to Switch A and the second cable to Switch B?

Only if Switch A and Switch B support Multi-Chassis Link Aggregation (MLAG / vPC / VSF stacking) and act as a single logical control plane. On standard standalone home and small-business switches, all cables in an 802.3ad LACP group must terminate on the exact same physical switch; use Active-Backup (Failover) mode if connecting a NAS across two separate switches.

Related Switch Setup & Engineering Guides

Reviewed by Elena Rostova, CCNP (Network Infrastructure Architect)

Part of the Packetsaver Network Engineering Team. All configurations and firmware safety instructions follow vendor-verified RFC and IEEE standards. Read our testing methodology →