LACP between Linux and a switch
Configure an 802.3ad bond and verify that both links join the same aggregator.
Two gigabit links can carry more aggregate traffic, but the copy speed of a single TCP flow may stay around the throughput of one link.
Linux with systemd-networkd
# /etc/systemd/network/10-bond0.netdev
[NetDev]
Name=bond0
Kind=bond
[Bond]
Mode=802.3ad
TransmitHashPolicy=layer3+4
LACPTransmitRate=fast
MIIMonitorSec=100ms
# /etc/systemd/network/20-slaves.network
[Match]
Name=enp1s0f0 enp1s0f1
[Network]
Bond=bond0
Switch configuration
Use an active LACP port channel on the switch. The static on setting does not negotiate with the host and can disrupt traffic if a cable is attached to the wrong port.
interface range Gi1/0/1-2
channel-group 1 mode active
interface Port-channel1
switchport mode trunk
What the hash distributes
The bond chooses a physical link using a hash of flow attributes. A TCP flow stays on one member. layer3+4 can distribute multiple flows better than layer2 when they all use the same gateway MAC.
Verification
cat /proc/net/bonding/bond0
Both members should show the same Aggregator ID. Check switch membership and LACP packets if the IDs differ.
How to check both links
On the sending host, record TX counters before and after one large transfer. For incoming traffic, compare RX. Repeat with several client and server pairs so the hash has different flows to distribute.
ip -s link show dev enp1s0f0
ip -s link show dev enp1s0f1
With both links in the active aggregator, one growing TX counter during a single transfer is expected. If a member is down, investigate that link first. The Linux bonding guide explains outbound port selection.