UniFi Switch Uplinks and Link Aggregation: LACP Guide

UniFi switch uplinks determine how much traffic can leave a switch at once. Link aggregation can add capacity across concurrent connections, but choosing a faster physical uplink is the relevant option when one connection needs more speed. This guide covers that distinction, the VLANs carried by the link, and the checks to make before configuring LACP.

For device power calculations, use AP and switch PoE planning. Select the wired path here after the power requirements are settled.

The uplink is the bottleneck nobody plans for

Here’s the mistake that survives even careful PoE planning: a switch full of fast access ports connected back to the rest of the network through a single, slower uplink.

Think about where traffic goes. Devices on a switch mostly talk to things not on that switch — the gateway, the internet, a NAS on another switch. All of that crosses the uplink. If you have a switch serving several busy access points and cameras, but it reaches the core through one ordinary uplink, that uplink is the ceiling for everything leaving the switch — no matter how fast the individual ports are.

The reasoning to apply:

• Estimate aggregate uplink demand, not per-port speed. Several APs and cameras can collectively push more than a single modest uplink carries at peak.
• Prefer a switch with a faster uplink path (higher-speed uplink ports, or SFP+/aggregation-capable ports) when that switch aggregates a lot of downstream traffic — distribution switches feeding APs and cameras especially.
• Topology matters. A chain of switches each daisy-chained off the previous one funnels everything through the first thin link. A star topology — switches home-running back to a capable core — avoids stacking everyone’s traffic onto one early bottleneck.

You don’t need every link to be the fastest tier. You need the uplink of any switch that aggregates significant traffic to not be the thing throttling all of it.

Link aggregation (LACP): what it does, and what it does not

Link aggregation bonds multiple physical links between two devices into one logical link. Support depends on the exact UniFi model; check Ubiquiti’s port aggregation FAQ before choosing ports. It is widely misunderstood, so be precise about what you get:

What aggregation does: it increases total throughput across many flows and adds link redundancy. Bond two links between a switch and a capable upstream device, and the combined pipe can carry more aggregate traffic, and survive one link failing.

What aggregation does not do: it does not make a single connection faster. Aggregation hashes each traffic flow onto one of the member links. One file transfer between two hosts rides a single physical link at that link’s speed — bonding two links does not double a single stream. You get more capacity for many simultaneous conversations, not a faster single one.

So aggregation is worth it when:

• A switch carries many simultaneous flows to an upstream device (a busy distribution switch to the core; a switch to a NAS many clients hit at once) and you want more aggregate headroom and a redundant path.
• Both ends support it and are configured as a matched aggregation group.

It is not the fix for “one device’s single transfer is slow.” That’s a per-link-speed problem; aggregation won’t change it. Reaching for LACP to speed up a single stream is the classic wasted effort here.

Faster uplink or LACP: choose by traffic pattern

The following are planning examples, not measured throughput. Link rates describe the physical connections; protocol overhead and other bottlenecks reduce usable capacity.

Need	Link choice to evaluate	Limitation to check
One transfer needs more than a 1 GbE link	A faster port at both ends	The client, server, and intermediate links must also support it
Several independent clients share a congested uplink	A faster uplink or a supported LACP group	Flow distribution need not be even across members
Keep a path during one member-link failure	LACP between supported endpoints	The surviving links have less total capacity
Carry guest, IoT, and trusted networks together	A VLAN trunk on the uplink	Trunking carries VLANs; it does not add bandwidth
Slow internet with a lightly used switch uplink	Check the gateway and WAN first	Changing the switch cannot increase the WAN service rate

A switch’s chassis capacity is a different number from its uplink speed. For example, Ubiquiti lists 16 Gbps switching capacity for the Lite 8 PoE, whose Ethernet ports are each 1 GbE. That chassis figure does not make any one port a 16 Gbps connection. List the ports along the actual client-to-destination path instead.

Keep UniFi VLAN assignments consistent across the uplink

Ubiquiti’s switch port VLAN documentation distinguishes the native network from allowed tagged networks. A switch-to-switch link carrying multiple networks needs the intended VLANs allowed along the complete path.

Write down the native network and tagged VLAN list before replacing an uplink or forming a group. Apply consistent assignments at the two ends. A link that negotiates at the expected speed can still fail to carry an IoT SSID if its VLAN is missing upstream. Use the UniFi VLAN setup guide for the access-port and SSID mappings, then validate a client on each VLAN after the uplink change.

Keep the controller’s management path available while changing these settings. Move one link or group at a time so a tagging mistake has a clear rollback point.

Check LACP support and validate the result

The official aggregation FAQ requires sequential ports and LACP rather than static LAG. It also advises configuring downstream switches before moving upstream toward the console. Gateway support is model-specific; a second cable to a gateway does not automatically create an aggregate.

Before a maintenance window, record both endpoint models, selected ports, negotiated speeds, and the existing VLAN assignments. Save the current configuration and arrange local access if this is the only management path.

After configuration, verify the intended group appears at both ends and check port counters during ordinary traffic. Compare more than one client connection when assessing aggregate capacity: a single transfer cannot demonstrate the benefit across multiple flows. If you plan a member-link failover check, perform it during the maintenance window and confirm that the controller and clients stay reachable through the surviving member.

Finish by reviewing UniFi gateway throughput if internet traffic remains constrained, or Wi-Fi speed troubleshooting if only wireless clients are slow. Use the UniFi network planner to keep the AP and switch inventory together.