Revision 1 as of 2008-03-04 11:44:12
|Deletions are marked like this.||Additions are marked like this.|
|Line 12:||Line 12:|
|For Redhat RHEL Linux this is documented in `A.3.1. Using Multiple Ethernet Cards||For Redhat RHEL 4 Linux this is documented in `A.3.1. Using Multiple Ethernet Cards|
Using Multiple Ethernet Cards
Some machines, especially servers, are equipped with dual Ethernet ports on the motherboard. In order to use both ports for increased bandwidth and/or redundancy, Linux must be configured appropriately.
Loading the bonding kernel module
Read the A.3.2.1. bonding Module Directives manual.
Add this line to /etc/modprobe.conf (not /etc/modules.conf as documented):
alias bond0 bonding options bond0 mode=6 miimon=100
with suitable parameters such as miimon as documented. The mode=6 refers to:
Sets an Active Load Balancing (ALB) policy for fault tolerance and load balancing. Includes transmit and receive load balancing for IPV4 traffic. Receive load balancing is achieved through ARP negotiation.
Modifying network scripts
In /etc/sysconfig/network-scripts/ new script files should be created:
Create a new bonding device script file ifcfg-bond0 containing:DEVICE=bond0 BOOTPROTO=dhcp ONBOOT=yes USERCTL=no
The normal Ethernet interface scripts ifcfg-ethN should turn eth0 and eth1 into slave devices:DEVICE=eth0 ONBOOT=yes BOOTPROTO=dhcp MASTER=bond0 SLAVE=yes USERCTL=noand similarly for eth1.
When using systemimager to clone the nodes these steps can be performed automatically using post-install scripts, e.g., /var/lib/systemimager/scripts/post-install/20q.eth_bonding_config script for the step 2.:#!/bin/sh # Get the Systemimager variables . /tmp/post-install/variables.txt # Name of the central server on this network SERVER=audhumbla1 DOMAINNAME=dcsc.fysik.dtu.dk # Correct the SystemImager eth0 config, turning eth0 into an Ethernet bonding device (bond0=eth0+eth1) cp -p /etc/sysconfig/network-scripts/ifcfg-eth0 /tmp/ifcfg-eth0.BAK cat <<EOF > /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 ONBOOT=yes BOOTPROTO=dhcp MASTER=bond0 SLAVE=yes USERCTL=no EOF # Finished cd
Restart network services
At this stage the network should be restarted by service network restart, or the system should be rebooted, in order to activate the bond0 device in stead of the normal eth0 device.