Configuring - Red Hat CLUSTER SUITE - CONFIGURING AND MANAGING A CLUSTER 2006 Manual

Table of Contents

Advertisement

Chapter 2. Hardware Installation and Operating System Configuration
2.5.1. Configuring Ethernet Channel Bonding
Ethernet channel bonding in a no-single-point-of-failure cluster system allows for a fault
tolerant network connection by combining two Ethernet devices into one virtual device.
The resulting channel bonded interface ensures that in the event that one Ethernet device
fails, the other device will become active. This type of channel bonding, called an active-
backup policy allows connection of both bonded devices to one switch or can allow each
Ethernet device to be connected to separate hubs or switches, which eliminates the single
point of failure in the network hub/switch.
Channel bonding requires each cluster node to have two Ethernet devices installed. When it
is loaded, the bonding module uses the MAC address of the first enslaved network device
and assigns that MAC address to the other network device if the first device fails link
detection.
To configure two network devices for channel bonding, perform the following:
1. Create a bonding devices in
alias bond0 bonding
options bonding miimon=100 mode=1
This loads the bonding device with the
options to the bonding driver to configure it as an active-backup master device for
the enslaved network interfaces.
2. Edit the
/etc/sysconfig/network-scripts/ifcfg-ethX
for both eth0 and eth1 so that the files show identical contents. For example:
DEVICE=ethX
USERCTL=no
ONBOOT=yes
MASTER=bond0
SLAVE=yes
BOOTPROTO=none
This will enslave ethX (replace X with the assigned number of the Ethernet devices)
to the bond0 master device.
3. Create
a
/etc/sysconfig/network-scripts/ifcfg-bond0
the following example:
DEVICE=bond0
USERCTL=no
ONBOOT=yes
BROADCAST=192.168.1.255
NETWORK=192.168.1.0
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
IPADDR=192.168.1.10
4. Reboot the system for the changes to take effect.
/etc/modprobe.conf
network
script
. For example:
interface name, as well as passes
bond0
for
the
bonding
configuration file
device
(for
example,
), which would appear like
29

Advertisement

Table of Contents
loading

This manual is also suitable for:

Cluster suite

Table of Contents