how to config bond in RHEL

 文/一觉亮天

The Channel Bonding Module [ref2]

 

Red Hat Enterprise Linux allows administrators to bind NICs together into a single channel using the bonding kernel 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.

 

To channel bond multiple network interfaces, the administrator must perform the following steps:

 

1.Add the following line to /etc/modprobe.conf:

 

alias bond<N> bonding

 

Replace <N> with the interface number, such as 0. For each configured channel bonding interface, there must be a corresponding entry in /etc/modprobe.conf.

 

2.Configure a channel bonding interface

Channel Bonding Interfaces[ref1]

 

Red Hat Enterprise Linux allows administrators to bind multiple network interfaces together into a single channel using the bonding kernel 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.

 

To create a channel bonding interface, create a file in the /etc/sysconfig/network-scripts/ directory called ifcfg-bond<N>, replacing <N> with the number for the interface, such as 0.

 

The contents of the file can be identical to whatever type of interface is getting bonded, such as an Ethernet interface. The only difference is that the DEVICE= directive must be bond<N>, replacing <N> with the number for the interface.

 

The following is a sample channel bonding configuration file:

DEVICE=bond0

BONDING_OPTS="mode=1 miimon=500"

BOOTPROTO=none

ONBOOT=yes

NETWORK=10.0.1.0

NETMASK=255.255.255.0

IPADDR=10.0.1.27

USERCTL=no

 

After the channel bonding interface is created, the network interfaces to be bound together must be configured by adding the MASTER= and SLAVE= directives to their configuration files. The configuration files for each of the channel-bonded interfaces can be nearly identical.

 

For example, if two Ethernet interfaces are being channel bonded, both eth0 and eth1 may look like the following example:

 

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.

 

Example

 

#ifcfg-bond0

DEVICE=bond0

BOOTPROTO=static

BONDING_OPTS="mode=1 miimon=500"

ONBOOT=yes

IPADDR=192.168.1.24

GATEWAY=192.168.1.1

NETMASK=255.255.255.0

 

#ifcfg-eth0

DEVICE=eth0

BOOTPROTO=static

ONBOOT=yes

MASTER=bond0

SLAVE=yes

 

#ifcfg-eth1

DEVICE=eth1

BOOTPROTO=static

ONBOOT=yes

MASTER=bond0

SLAVE=yes

 

Reference

[ref1] http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/en-US/RHEL510/Deployment_Guide/s2-networkscripts-interfaces-chan.html

 

[ref2] http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/en-US/RHEL510/Deployment_Guide/s2-modules-bonding.html