16.2.3. Channel Bonding Interfaces
bondingkernel module and a special network interface called a channel bonding interface. Channel bonding enables two or more network interfaces to act as one, simultaneously increasing the bandwidth and providing redundancy.
ifcfg-bond<N>, replacing <N> with the number for the interface, such as
DEVICE=directive must be
bond<N>, replacing <N> with the number for the interface.
DEVICE=bond0 IPADDR=192.168.1.1 NETMASK=255.255.255.0 ONBOOT=yes BOOTPROTO=none USERCTL=no BONDING_OPTS="<bonding parameters separated by spaces>"
SLAVE=directives to their configuration files. The configuration files for each of the channel-bonded interfaces can be nearly identical.
eth1may look like the following example:
DEVICE=eth<N> BOOTPROTO=none ONBOOT=yes MASTER=bond0 SLAVE=yes USERCTL=no
alias bond<N> bonding
BONDING_OPTS="directive in the
ifcfg-bondNinterface file. Do not specify options for the bonding device in the
max_bondsparameters are not interface specific and therefore, if required, should be specified in
options bonding debug=1 max_bonds=1
max_bondsparameter should not be set when using
ifcfg-bondNfiles with the
BONDING_OPTSdirective as this directive will cause the network scripts to create the bond interfaces as required.
/etc/modprobe.confwill not take effect until the module is next loaded. A running module must first be unloaded. For further instructions and advice on configuring the bonding module, as well as to view the list of bonding parameters, refer to Section 45.5.1, “The Channel Bonding Module”.