IFCFG-BONDING(5) Network configuration IFCFG-BONDING(5)NAMEifcfg-bonding - interface bonding configuration
SYNOPSIS
/etc/sysconfig/network/ifcfg-bond*
Bonding Interfaces
To setup a bonding interface you need a configuration file ifcfg-
bond<X> with the usual network settings. But you must add additional
variables
BONDING_MASTER
must be set to 'yes' to identify this interface as a bonding
interface
BONDING_SLAVE_<X>
here you specify the interface name representing the slave net‐
work interfaces.
Note: Please adopt the /etc/udev/rules.d/70-persistent-net.rules
rule file to match the hardware by BUS id and not by the MAC
address (default). Using MAC address, it is not possible to
replace a defect NIC with a new one (having a different MAC),
without to adopt either the MAC or the name of the slave inter‐
face in the configuration files.
Note also: Bonding slave interfaces are reserved for the bonding
and are not usable for any another purposes (unlike e.g. inter‐
faces used for VLANs) and the bonding master manages the slaves
itself, e.g. it sets the MAC address on the slaves by default.
To configure this accordingly, set BOOTPROTO=none in the ifcfg
file of each slave interfaces to avoid any IP or link-layer set‐
up on these interfaces. The bonding script will apply the link
settings (e.g. for fail_over_mode=active) at enslave time.
BONDING_MODULE_OPTS
contains bonding options. Here you can set interface timeouts or
working modes ('mode=active-backup' for backup mode). For addi‐
tional information take a look into the documentation mentioned
at the bottom. Note, that this options are not passed as param‐
eters to the bonding kernel module any more, but set via sysfs
interface. This variable will be renamed in the feature.
BONDING_SKIP_REMOVE_WORKAROUND
When set to "yes", a bonding interface will be not removed while
ifdown any more to avoid problems, e.g. when some third party
kernel module, such as Veritas 'llt' module, does not react cor‐
rectly to the UNREGISTER event and does not remove its refer‐
ences to the bonding interface causing all network related oper‐
ation to stuck.
Note: the bonding options are not reverted when this option is
enabled and it is required to either explicitly keep the old
options and set them to their default setting on bonding config‐
uration changes or to reboot.
Example
Example for a bonding interface on eth0 and eth1 using the backup mode
ifcfg-bond0
STARTMODE='onboot'
BOOTPROTO='static'
IPADDR='192.168.0.1/24'
BONDING_MASTER='yes'
BONDING_SLAVE_0='eth0'
BONDING_SLAVE_1='eth1'
BONDING_MODULE_OPTS='mode=active-backup miimon=100'
ifcfg-eth0
STARTMODE='onboot'
BOOTPROTO='none'
#ETHTOOL_OPTIONS='wol g'
ifcfg-eth1
STARTMODE='onboot'
BOOTPROTO='none'
#ETHTOOL_OPTIONS='wol g'
Note, that the slaves are configured with BOOTPROTO='none', what avoids
link set UP and IP configuration of the slaves. Further also START‐
MODE='hotplug', allowing that some (all) of the slaves are allowed to
be missed at boot time. The hotplug slaves will be added to the bond
as soon as are become available (udev BUS based persistent name rule or
manual ifup bond0 is required). The network script waits for the
slaves, but when there is no slave available at bonding start time
(boot time), the bonding creation will fail and also the network script
will report an error.
Additional Information
For additional and more general information take a look into
/usr/src/linux/Documentation/networking/bonding.txt. Maybe you need to
install the kernel sources to get this additional documentation.
The configuration of routes for this kind of interface does not differ
from ordinary interfaces. See man routes for details.
BUGS
Please report bugs at <http://www.suse.de/feedback>
AUTHOR
Christian Zoz <zoz@suse.de> -- ifup script
Wilken Gottwalt <wgottwalt@suse.de> --ifcfg-bonding manual page
SEE ALSOifcfg(5), ifup(8).
sysconfig April 2005 IFCFG-BONDING(5)
