29/08/13

4.2.2. Channel Bonding Interfaces

Prev

Next

4.2.2. Channel Bonding Interfaces

Fedora allows administrators to bind multiple network interfaces together into a single channel using the b o n d i n gkernel 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 / e t c / s y s c o n f i g / n e t w o r k s c r i p t s /directory called i f c f g b o n d < 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 D E V I C E =directive must be b o n d < N > , replacing < N >with the number for the interface. The following is a sample channel bonding configuration file:

D E V I C E = b o n d 0 I P A D D R = 1 9 2 . 1 6 8 . 1 . 1 N E T M A S K = 2 5 5 . 2 5 5 . 2 5 5 . 0 O N B O O T = y e s B O O T P R O T O = n o n e U S E R C T L = n o B O N D I N G _ O P T S = " < b o n d i n gp a r a m e t e r ss e p a r a t e db ys p a c e s > "

Example 4.1. Sample ifcfgbond0 interface configuration file

After the channel bonding interface is created, the network interfaces to be bound together must be configured by adding the M A S T E R =and S L A V E =directives to their configuration files. The configuration files for each of the channelbonded interfaces can be nearly identical. For example, if two Ethernet interfaces are being channel bonded, both e t h 0and e t h 1may look like the following example:
D E V I C E = e t h < N > B O O T P R O T O = n o n e O N B O O T = y e s M A S T E R = b o n d 0 S L A V E = y e s U S E R C T L = n o

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, create a new file as root named < b o n d i n g > . c o n fin the / e t c / m o d p r o b e . d /directory. Note that you can name this file anything you like as long as it ends with a . c o n fextension. Insert the following line in this new file:
a l i a sb o n d < N >b o n d i n g

Replace < N >with the interface number, such as 0 . For each configured channel bonding interface, there must be a corresponding entry in your new / e t c / m o d p r o b e . d / < b o n d i n g > . c o n ffile.

Important: put all bonding module parameters in ifcfgbondN files

docs.fedoraproject.org/en-US/Fedora/13/html/Deployment_Guide/s2-networkscripts-interfaces-chan.html 1/2

29/08/13

4.2.2. Channel Bonding Interfaces

Parameters for the bonding kernel module must be specified as a spaceseparated list in the B O N D I N G _ O P T S = " < b o n d i n gp a r a m e t e r s > "directive in the ifcfgbond< N >interface file. Do not specify options for the bonding device in / e t c / m o d p r o b e . d / < b o n d i n g > . c o n f , or in the deprecated / e t c / m o d p r o b e . c o n ffile. For further instructions and advice on configuring the bonding module and to view the list of bonding parameters, refer to Section 30.5.2, The Channel Bonding Module.

Prev
4.2. Interface Configuration Files

Up

Home

Next
4.2.3. Alias and Clone Files

docs.fedoraproject.org/en-US/Fedora/13/html/Deployment_Guide/s2-networkscripts-interfaces-chan.html

2/2