Alias And Clone Files - Red Hat ENTERPRISE LINUX 4.5.0 Reference Manual

Table of Contents

Advertisement

install bond0 /sbin/modprobe bonding -o bond0
Once
/etc/modprobe.conf
interfaces are configured, the
interface.
Important
Important aspects of the channel bonding interface are controlled through the
kernel module. For more information about controlling the
refer to

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>
For example, an
ifcfg-eth0:0
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
dynamic IP address, but the same physical network card can receive request 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>
interface, a clone file is used to specify additional options for an interface. For example, a
standard DHCP Ethernet interface called
DEVICE=eth0 ONBOOT=yes BOOTPROTO=dhcp
Since the default value for the
this interface up and down. To give users the ability to control the interface, create a clone by
copying
to
ifcfg-eth0
USERCTL=yes
is configured, and the channel bonding interface and network
command can be used to bring up the channel bonding
ifup
Section 5.2, "The Channel Bonding
file could be configured to specify
. Under this configuration,
ifcfg-eth0
. While an alias file allows multiple addresses for an existing
eth0
directive is
USERCTL
and add the following line to
ifcfg-eth0-user
Module".
naming scheme.
DEVICE=eth0:0
, may look similar to this:
if it is not specified, users cannot bring
no
Alias and Clone Files
modules,
bonding
and a static
is bound to a
eth0
:
ifcfg-eth0-user
125

Advertisement

Table of Contents
loading

Table of Contents