LACP Link Aggregation: How It Works for Business Networks

What Is LACP?

LACP stands for Link Aggregation Control Protocol. It is defined in IEEE standard 802.3ad (now incorporated into IEEE 802.1AX) and provides a standardised method for combining multiple physical network links between two devices — typically switches — into a single logical channel, known as a Link Aggregation Group (LAG) or port channel.

Before LACP was standardised, vendors implemented proprietary link aggregation methods that only worked between equipment from the same manufacturer. LACP solved this interoperability problem, allowing link aggregation to work across switches from different vendors, provided both ends support the 802.3ad standard.

How LACP Works

When LACP is configured on a switch port, the port enters a negotiation phase with the connected device. LACP packets (called LACPDUs — Link Aggregation Control Protocol Data Units) are exchanged between the two ends to confirm that both sides are willing and able to form an aggregated group, and to agree on which ports to include in the group.

Once the negotiation is complete, the ports are combined into a LAG. From the perspective of devices on the network, the LAG appears as a single high-speed link. Traffic is distributed across the member ports according to a hashing algorithm — typically based on source and destination MAC address, IP address, or port number, depending on the switch configuration.

Active vs Passive LACP Mode

LACP supports two negotiation modes:

• Active: The switch initiates LACP negotiation, sending LACPDUs to the connected device. This is the recommended setting in most deployments.
• Passive: The switch waits for the connected device to initiate negotiation before joining a LAG. Passive mode on both ends means negotiation never starts — at least one end must be in Active mode.

LACP vs Static Link Aggregation

Link aggregation can also be configured statically — without the LACP protocol. In static mode, ports are manually assigned to a LAG without any negotiation. While simpler to configure, static link aggregation has meaningful disadvantages:

• No automatic detection of misconfiguration or cabling errors on member ports
• No automatic recovery if a member link fails — the switch continues to forward traffic on what it believes to be a functioning aggregate, even if the physical link is down at the far end
• Interoperability with non-identical equipment is less reliable

LACP adds the overhead of protocol negotiation but provides dynamic membership management — ports are only active in the LAG when both ends confirm they are operational, which prevents the silent failure modes that static aggregation can produce. For production business networks, LACP is the preferred approach.

What LACP Can and Cannot Do

What LACP Does

• Increases the total available bandwidth between two switches or between a server and a switch — up to the combined capacity of all member ports
• Provides link-level redundancy — if one member port or cable fails, traffic continues across the remaining members with no manual intervention
• Enables standardised interoperability between switches from different manufacturers
• Provides automatic recovery — when a failed port returns to service, LACP re-negotiates and adds it back to the LAG automatically

What LACP Does Not Do

• LACP does not provide device-level redundancy. If one of the two switches participating in a LAG fails completely, the aggregated link fails regardless of how many member ports were configured.
• LACP does not increase the bandwidth of a single flow beyond the capacity of one member port. A single TCP session uses one hash-selected path. Aggregated bandwidth is only achievable across multiple concurrent sessions.
• LACP operates at Layer 2 — it does not provide WAN-level link aggregation or allow you to combine internet connections from different ISPs. That requires channel bonding at the WAN level.

Typical LACP Deployments in Business Networks

Switch-to-Switch Uplinks

The most common use of LACP in business networks is on uplinks between access switches and distribution or core switches. Instead of a single Gigabit or 10 Gigabit uplink, two or four ports are bonded together to increase the available bandwidth between layers of the network. This is particularly relevant for networks with many users on an access switch or where large file transfers between network segments are common.

Server Network Interface Card (NIC) Bonding

Servers with multiple network interfaces can use LACP to present a single aggregated link to the network switch. This is common on file servers, hypervisors and storage systems where network bandwidth is a bottleneck. NIC bonding using LACP requires the switch to support LACP and to be configured to form a LAG with the server's interfaces.

Storage Area Network (SAN) Connectivity

For iSCSI or NFS storage networks, LACP is frequently used to aggregate the bandwidth between storage arrays and the network. Storage traffic is highly parallel — many simultaneous I/O operations — which makes it well-suited to the per-flow distribution model that LACP uses.

Configuring LACP: Key Considerations

When deploying LACP in a business network, the following configuration points are worth reviewing:

• Hash algorithm: Choose a hash algorithm that distributes traffic evenly across member ports for your traffic profile. IP-based hashing typically distributes traffic more evenly in environments with many different client IP addresses; MAC-based hashing may work better in VLAN-heavy environments.
• Timer rate: LACP supports fast (1-second) and slow (30-second) PDU intervals. Fast timers detect failures more quickly but add protocol overhead. For most business deployments, fast timers on uplink connections are appropriate.
• Maximum member ports: IEEE 802.3ad allows up to 16 ports per LAG, of which a maximum of 8 can be active simultaneously. The remaining ports are standby, ready to take over if an active member fails.
• VLAN configuration: LAG interfaces inherit VLAN membership from their member ports. Ensure VLAN trunk and access configurations are applied to the LAG interface, not the individual member ports, to avoid inconsistent behaviour.

LACP in Managed vs Unmanaged Network Environments

LACP requires managed switches at both ends of the link. Unmanaged switches — the kind typically found in small offices — do not support LACP and cannot participate in link aggregation. For small businesses, this is rarely a limitation, as unmanaged switches are typically used for desktop connectivity where a single Gigabit port per device is more than sufficient.

For medium-sized businesses with server rooms, structured cabling and multiple switch layers, AMVIA recommends managed switches from Cisco Meraki, Ubiquiti or HPE Aruba that support LACP natively with straightforward configuration interfaces.