LACP config on Fedora
Create the file: /etc/sysconfig/network-scripts/ifcfg-bond0
DEVICE=bond0
BONDING_OPTS="mode=4 miimon=500 lacp-rate=1" #mode=4 is LACP(802.3ad)
BOOTPROTO=none
ONBOOT=yes
USERCTL=no
PEERDNS=no
IPV6INIT=no
NM_CONTROLLED=no
TYPE=Ethernet
NETMASK=255.255.255.0
IPADDR=172.16.0.6
GATEWAY=172.16.0.1
DNS1=8.8.8.8
DNS2=8.8.4.4
Then, for each interface (network card) you want to bond to the bond0 interface, edit the respective device’s configuration file: /etc/sysconfig/network-scripts/ifcfg-[interface] (e.g., eth0, eth1, ra0)
DEVICE=eth0
MASTER=bond0
SLAVE=yes
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
PEERDNS=no
IPV6INIT=no
NM_CONTROLLED=no
TYPE=Ethernet
I chose to use mode=1 which is “active backup mode.” mode=0 is “round-robin.” What does that mean? Definitions are below. (There are several “modes,” but these 4 are the most popular.)
mode=0 (balance-rr)
Round-robin policy: Transmit packets in sequential order from the first available slave through the last. This mode provides load balancing and fault tolerance.
mode=1 (active-backup)
Active-backup policy: Only one slave in the bond is active. A different slave becomes active if, and only if, the active slave fails. The bond’s MAC address is externally visible on only one port (network adapter) to avoid confusing the switch. This mode provides fault tolerance. The primary option affects the behavior of this mode.
mode=3 (broadcast)
Broadcast policy: transmits everything on all slave interfaces. This mode provides fault tolerance.
mode=4 (802.3ad)
IEEE 802.3ad Dynamic link aggregation. Creates aggregation groups that share the same speed and duplex settings. Utilizes all slaves in the active aggregator according to the 802.3ad specification.
A service network restart is all that was needed to activate bond0. If not, a reboot will do it.









