How to Optimize LACP Bond Bandwidth with Layer3+4 Hashing on Hyperion

Written By Sebastian Sime (Administrator)

Updated at April 21st, 2026

→ Applies to: Hyperion 9.x and above

Network bonding (LACP) often limits traffic between two specific IPs to a single physical link. By changing the xmit_hash_policy to layer3+4, the system uses TCP/UDP ports to distribute traffic, allowing for true aggregate speeds across all links in the bond.

PREREQUISITES
- Ensure that any external physical switch ports connected to the Hyperion unit are configured in an LACP (802.3ad) Port-Channel.
- Ensure bond was already created between the network adapters (“How to Add an Additional Uplink to a vSwitch via CLI in Hyperion”).

IMPORTANT
Ensure steps below are performed on all Hyperion hosts connected between them.

 

Step 1. Connect to Hyperion appliance via SSH as admin

ssh admin@<your_ip_address_or_hostname>

 

Step 2. Become Super User

sudo su

 

Step 3. Configure Advanced LACP Hashing (replace <bond_name> with the bond name)

echo layer3+4 > /sys/class/net/<bond_name>/bonding/xmit_hash_policy

EXAMPLE

echo layer3+4 > /sys/class/net/bond0/bonding/xmit_hash_policy

 

Step 4. Make the changes persistent (replace <bond_name> with the bond name)

nmcli con mod <bond_name> +bond.options "xmit_hash_policy=layer3+4"
nmcli con up <bond_name>

This will restart the bond, your network connection will drop for a few seconds.