This procedure did not actually change very much from RHEL 5.0. Knowing the changes however are pretty critical to getting it right.
Gone is the Administrator’s friend and potential cestpool, /etc/modpprobe.conf
Its replaced by anything you want to load in /etc/modprobe.d
Naming guidelines? Who needs them. Name the file anything you want.
Procedure: Still pretty darned easy.
Pre-requisite: You need two network connections to the same network subnet. Unlike HP-UX APA (Auto port aggregation) you don’t normally need special switch configuration. Though it is possible for Cisco switches to mess this up.
I’m recommending use of a standard naming convention in your shop. I, in a fit of creativity have chosen the name, bonding.conf
All you do is rip the bonding configuration you used from modeprobe.conf on RHEL 5 and put it in the fil:
options bond0 miimon=200 mode=5
alias eth0 e1000
alias eth1 e1000
This system has two Intel 1 GB cards in it, plugged into the same network and subnet.
[root@viper ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Intel Corporation 82541GI Gigabit Ethernet Controller
[root@viper ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth1
# Intel Corporation 82540EM Gigabit Ethernet Controller
Now the all critical bond0 configuration which has not changed.
[root@viper ~]# cat /etc/sysconfig/network-scripts/ifcfg-bond0
/sbin/service network restart
[root@viper ~]# service network restart
Shutting down interface bond0: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface bond0: [ OK ]
One little warning. Red Has put a little tool in the OS called Network manager. It thinks it owns the network configuration.
If you for example copy in the configuration from another system with the intent of changing the IP address on a new one, be quick about it. Copy in ifcfg-bond0 without ifcfg-eth0/1 and you lose network access to the system.
It is highly recommended you do this with some form of console access.