Linux Bond binding Rollup __linux

1. Edit the file:
#vi/etc/modprobe.conf
Alias Eth0 TG3
Alias Eth1 TG3
Alias eth2 e1000 Note: e1000 for server Tanga network card
Add to:
Alias Bond0 Bonding
Options Bond0 miimon=100 mode=1
(0 indicates that load blance 1 means hot standby)
2. Create Bond0 Starter Profile:
Cd/etc/sysconfig/network-scripts/vi ifcfg-bond0
The contents are as follows:

Device=bond0
Onboot=yes
Bootproto=static
ipaddr=192.168.0.36
netmask=255.255.255.0
Userctl=no
3. Edit Ifcfg-eth0, ifcfg-eth1 two network card configuration files, as follows:
#vi Ifcfg-eth0
Device=eth0
Userctl=no
Onboot=yes
#MASTER =bond0
#SLAVE =yes
Bootproto=none
#HWADDR =xxxxxxxxxxxxxx
Note: The following is best in the ifcfg-eth* file marked Master and slave, easy to arrange the wrong, if not written here, the platoon will have to reboot the server.
#vi ifcfg-eth1
Device=eth1
Userctl=no
Onboot=yes
#MASTER =bond0
#SLAVE =yes
Bootproto=none
#HWADDR =xxxxxxxxxxxxxx 4. Edit Startup file
#vi/etc/rc.d/rc.local
In the final add:
Ifenslave bond0 eth0 eth1 This sentence is equivalent to adding eth0 eth1 in Master=bond0 and Slave=yes, respectively.
(If you change the order of the network card and eth0, etc. corresponding physical network card, must do bond0 come to do, otherwise not change, change the network card order file for/etc/sysconfig/hwconf) 5. Edit host name and default gateway
#vi/etc/sysconfig/network
hostname=test01
Note: If you need to bind two bond, you need to create multiple bond*conf files under/etc/modprobe.d/to invoke
6, turn off the network card NetworkManager startup mode
Service NetworkManager Stop
Chkconfig NetworkManager off
Service Network restart
Ifenslave bond0 eth0 eth1 Effective

If it does not work or if the above command has errors, type modprobe bonding load Bond driver