DEVICE=eth<N>
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no
In this example, replace <N> with the numerical value for the interface.
For a channel bonding interface to be valid, the kernel module must be loaded. To ensure that the
module is loaded when the channel bonding interface is brought up, add the following line to /etc/
modprobe.conf:
alias bond<N> bonding
Replace <N> with the number of the interface, such as 0.
Important: put all bonding module parameters in ifcfg-bondN
files
Parameters for the bonding kernel module must be specified as a space-separated list
in the BONDING_OPTS="<bonding parameters>" directive in the ifcfg-bond<N>
interface file. They should not be placed in /etc/modprobe.conf. For further
instructions and advice on configuring the bonding module and to view the list of bonding
parameters, refer to
14.2.4. Alias and Clone Files
Two lesser-used types of interface configuration files are alias and clone files.
Alias interface configuration files, which are used to bind multiple addresses to a single interface, use
the ifcfg-<if-name>:<alias-value> naming scheme.
For example, an ifcfg-eth0:0 file could be configured to specify DEVICE=eth0:0 and a static
IP address of 10.0.0.2, serving as an alias of an Ethernet interface already configured to receive its
IP information via DHCP in ifcfg-eth0. Under this configuration, eth0 is bound to a dynamic IP
address, but the same physical network card can receive requests via the fixed, 10.0.0.2 IP address.
Caution
Alias interfaces do not support DHCP.
A clone interface configuration file should use the following naming convention: ifcfg-<if-
name>-<clone-name>. While an alias file allows multiple addresses for an existing interface, a clone
file is used to specify additional options for an interface. For example, a standard DHCP Ethernet
interface called eth0, may look similar to this:
DEVICE=eth0
ONBOOT=yes
Section 41.5.2, "The Channel Bonding
Alias and Clone Files
Module".
159
Need help?
Do you have a question about the ENTERPRISE LINUX 5 - DEPLOYMENT and is the answer not in the manual?
Questions and answers