Multiple bonding devices on a single host

[Ujjwal_Rajbhandari at Dell.com]

Instructions on setting up a Bonding device
1.	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. 
2.	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. 
3.	The contents of the file can be identical to whatever type of
interface that 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. 
4.	The following is a sample channel bonding configuration file:
		
		DEVICE=bond0
		BOOTPROTO=none
		ONBOOT=yes
		NETWORK=10.0.1.0
		NETMASK=255.255.255.0
		IPADDR=10.0.1.27
		USERCTL=no
5.	After the channel bonding interfaces are 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.

6.	For example, if channel bonding two Ethernet interfaces, both
eth0 and eth1 may look like the following example: 
		
		DEVICE=eth<N>
		BOOTPROTO=none
		ONBOOT=yes
		MASTER=bond0
		SLAVE=yes
		USERCTL=no
7.	In this example, replace <N> with the numerical value for the
interface. 
8.	For a channel bonding interface to be valid, the kernel module
must be loaded. The procedure for loading the module is slightly
different on Red Enterprise Linux Version 3 and Red Hat Enterprise Linux
Version 4. 
9.	Red Hat Enterprise Linux Version 4
10.	To ensure that the module is loaded when the channel bonding
interface is brought up, add the following line to /etc/modprobe.conf:
11.	alias bond0 bonding
12.	options bonding miimon=100 mode=6
13.	For each configured channel bonding interface, there must be a
corresponding entry in /etc/modprobe.conf. Note: Prior to Update 2 of
Red Hat Enterprise Linux version 4, there was no support for multiple
bonding interfaces. If you are trying to configure more than one bonding
interface, you will need to update your system to Red Hat Enterprise
Linux 4 Update 2 or later. 
14.	Follow the above mentioned instructions to set up the second
(any additional bonded devices).  Modify /etc/modprobe.conf and change
the options line for the bonding module such that max_bonds parameter is
added.  The max_bonds determines the total number bonded device the
system will support.  So in a system with 2 bonding devices the entry in
the /etc/modprobe.conf will look as follows:
	
		alias bond0 bonding
		options bond0 miimon=100 mode=6 max_bonds=2
		alias bond1 bonding
		options bond1 miimon=100 mode=6
15.	Once /etc/modprobe.conf is configured and the channel bonding
interface and network interfaces are configured, the ifup command can be
used to bring up the channel bonding interface or you can restart your
networking services with service network restart. 
For more information about controlling the bonding modules, refer to
Section A.3.2 - The Channel Bonding Module at:
https://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/ref-guide/s
1-modules-ethernet.html
In the Red Hat Enterprise Linux 4 Reference Guide located at:
https://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/ref-guide/.
There is also information in the file
/usr/share/doc/kernel-doc-2.6.9/Documentation/networking/bonding.txt .


Ujjwal

Ujjwal Rajbhandari (ujjwal_rajbhandari at dell.com)
DB & Apps., GSE
Dell Inc.
PS2-2, MS PS2-39
One Dell Way, Round Rock, Texas 78682
Tel: 512.724.2593 (office)
Tel: 512.725.0046 (lab)
Fax: 512.283.1111

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/oraclesolutions/attachments/20080317/824a1fd1/attachment.htm