Bonding - Link Aggregation
Linux bonding provides a method for aggregating multiple network interfaces (slaves) into a single logical bonded interface (bond). Link aggregation is useful for linear scaling of bandwidth, load balancing, and failover protection.
Cumulus Linux supports two bonding modes:
- IEEE 802.3ad link aggregation mode that allows you to combine one or more links to form a link aggregation group (LAG) so that a media access control (MAC) client can treat the group as a single link. IEEE 802.3ad link aggregation is the default mode.
- Balance-xor mode, where the bonding of slave interfaces are static and all slave interfaces are active for load balancing and fault tolerance purposes. This is useful for MLAG deployments.
Cumulus Linux uses version 1 of the LAG control protocol (LACP).
To temporarily bring up a bond even when there is no LACP partner, use LACP Bypass.
The switch distributes egress traffic through a bond to a slave based on a packet hash calculation, providing load balancing over the slaves; the switch distributes conversation flows over all available slaves to load balance the total traffic. Traffic for a single conversation flow always hashes to the same slave.
The hash calculation uses packet header data to choose to which slave to transmit the packet:
- For IP traffic, the switch uses IP header source and destination fields in the calculation.
- For IP + TCP/UDP traffic, the switch includes source and destination ports in the hash calculation.
In a failover event, the switch adjusts the hash calculation to steer traffic over available slaves.
LAG Custom Hashing
You can configure the fields you want to use in the LAG hash calculation. For example, if you do not want to use source or destination port numbers in the hash calculation, you can disable the source port and destination port fields.
You can configure the following fields:
- Source MAC
- Source IP
- Destination IP
- Ether type
- VLAN ID
- Source port
- Destination port
- Layer 3 protocol
To configure custom hash, edit the
- To enable custom hashing, uncomment the
lag_hash_config.enable = trueline.
- To enable a field, set the field to
true. To disable a field, set the field to
- Run the
echo 1 > /cumulus/switchd/ctrl/hash_config_reloadcommand. This command does not cause any traffic interruptions.
The following shows an example
cumulus@switch:~$ sudo nano /etc/cumulus/datapath/traffic.conf ... #LAG HASH config #HASH config for LACP to enable custom fields #Fields will be applicable for LAG hash #calculation #Uncomment to enable custom fields configured below lag_hash_config.enable = true lag_hash_config.smac = true lag_hash_config.dmac = true lag_hash_config.sip = true lag_hash_config.dip = true lag_hash_config.ether_type = true lag_hash_config.vlan_id = true lag_hash_config.sport = false lag_hash_config.dport = false lag_hash_config.ip_prot = true ...
Cumulus Linux enables symmetric hashing by default. Make sure that the settings for the source IP (
lag_hash_config.sip) and destination IP (
lag_hash_config.dip) fields match, and that the settings for the source port (
lag_hash_config.sport) and destination port (
lag_hash_config.dport) fields match; otherwise symmetric hashing disables automatically. You can disable symmetric hashing manually in the
/etc/cumulus/datapath/traffic.conf file by setting
symmetric_hash_enable = FALSE.
You can set a unique hash seed for each switch to avoid hash polarization. See Configure a Hash Seed to Avoid Hash Polarization.
Create a Bond
In the example below, the front panel port interfaces swp1 thru swp4 are slaves in bond0, while swp5 and swp6 are not part of bond0.
To create and configure a bond:
cumulus@switch:~$ nv set interface bond0 bond member swp1-4 cumulus@switch:~$ nv config apply
/etc/network/interfaces file to add a stanza for the bond, then run the
ifreload -a command.
cumulus@switch:~$ sudo nano /etc/network/interfaces ... auto bond0 iface bond0 bond-slaves swp1 swp2 swp3 swp4 ...
cumulus@switch:~$ ifreload -a
- By default, the bond uses IEEE 802.3ad link aggregation mode. To configure the bond in balance-xor mode, see Configuration Parameters below.
- If the bond is not going to be part of a bridge, you must specify an IP address.
- Make sure the name of the bond adheres to Linux interface naming conventions and is unique within the switch.
- Cumulus Linux does not support bond members at 200G or greater.
When you start networking, the switch creates bond0 as MASTER and interfaces swp1 thru swp4 come up in SLAVE mode:
cumulus@switch:~$ ip link show ... 3: swp1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT qlen 500 link/ether 44:38:39:00:03:c1 brd ff:ff:ff:ff:ff:ff 4: swp2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT qlen 500 link/ether 44:38:39:00:03:c1 brd ff:ff:ff:ff:ff:ff 5: swp3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT qlen 500 link/ether 44:38:39:00:03:c1 brd ff:ff:ff:ff:ff:ff 6: swp4: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT qlen 500 link/ether 44:38:39:00:03:c1 brd ff:ff:ff:ff:ff:ff ... 55: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT link/ether 44:38:39:00:03:c1 brd ff:ff:ff:ff:ff:ff
All slave interfaces within a bond have the same MAC address as the bond. Typically, the first slave you add to the bond donates its MAC address as the bond MAC address, whereas the MAC addresses of the other slaves are the bond MAC address. The bond MAC address is the source MAC address for all traffic leaving the bond and provides a single destination MAC address to address traffic to the bond.
Removing a bond slave interface from which a bond derives its MAC address affects traffic when the bond interface flaps to update the MAC address.
Configure Bond Options
The table below describes the configuration options for a bond. To configure a bond, run the commands shown or add the parameter to the bond stanza in the
The following example sets the bond mode for bond01 to balance-xor (static):
cumulus@switch:~$ nv set interface bond01 bond mode static cumulus@switch:~$ nv config apply
/etc/network/interfaces file to add the
balance-xor parameter to the bond stanza, then run the
ifreload -a command:
cumulus@switch:~$ sudo nano /etc/network/interfaces ... auto bond1 iface bond1 bond-mode balance-xor bond-slaves swp1 swp2 swp3 swp4 ...
cumulus@switch:~$ ifreload -a
Each bond configuration option, except for
bond slaves, has the recommended value by default in Cumulus Linux. Only configure an option if you need a different setting. For more information on configuration values, refer to the Related Information section below.
|Cumulus Linux supports IEEE 802.3ad link aggregation mode (802.3ad) and balance-xor mode.|
The default mode is 802.3ad.
|This is the miimon frequency that defines how often (in milliseconds) to inspect the link state of each slave for failures. You can specify a value between 0 and 255. The default value is 100.|
The NVUE command is not supported.
|Sets miimon to use either MII or ethtool ioctls, or netif_carrier_ok() to determine the link status. The default setting is |
The NVUE command is not supported.
|Enables LACP bypass.|
|Sets the rate at which the link partner transmits LACP control packets: |
|Defines the minimum number of links (between 0 and 255) that must be active before the bond goes into service. The default value is 1.|
Use a value greater than 1 if you need higher level services to ensure a minimum aggregate bandwidth level before activating a bond. Keeping the
The NVUE command is not supported.
Show Bond Information
To show information for a bond, run the NVUE
nv show interface <bond> bond command:
cumulus@switch:~$ nv show interface bond1 bond operational applied description ---------------- ----------- ------- ------------------------------------------------------ down-delay 0 0 bond down delay lacp-bypass off lacp bypass lacp-rate fast fast lacp rate mode lacp bond mode up-delay 0 0 bond up delay [member] swp1 swp1 Set of bond members mlag enable on Turn the feature 'on' or 'off'. The default is 'off'. id 1 1 MLAG id peer-interface bond1 Peer interface status dual Mlag Interface status
You can also run the Linux
sudo cat /proc/net/bonding/<bond> command:
cumulus@switch:~$ sudo cat /proc/net/bonding/bond01 ... Bonding Mode: IEEE 802.3ad Dynamic link aggregation Transmit Hash Policy: layer3+4 (1) MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 802.3ad info LACP rate: fast Min links: 1 Aggregator selection policy (ad_select): stable System priority: 65535 System MAC address: 44:38:39:be:ef:aa Active Aggregator Info: Aggregator ID: 1 Number of ports: 1 Actor Key: 9 Partner Key: 9 Partner Mac Address: 44:38:39:00:00:12 Slave Interface: swp1 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 44:38:39:00:00:11 Slave queue ID: 0 Aggregator ID: 1 Actor Churn State: none Partner Churn State: none Actor Churned Count: 1 Partner Churned Count: 2 details actor lacp pdu: system priority: 65535 system mac address: 44:38:39:be:ef:aa port key: 9 port priority: 255 port number: 1 port state: 63 details partner lacp pdu: system priority: 65535 system mac address: 44:38:39:00:00:12 oper key: 9 port priority: 255 port number: 1 port state: 63
To show specific bond information, use the
nv show interface <bond> <option> commands:
cumulus@switch:~$ nv show interface bond1 TAB acl bridge ip lldp ptp router bond evpn link pluggable qos
- An interface cannot belong to multiple bonds.
- A bond can have subinterfaces, but subinterfaces cannot have a bond.
- A bond cannot enslave VLAN subinterfaces.
- All slave ports within a bond must have the same speed or duplex and match the slave ports of the link partner.