RHEL6 dual Nic bonding configuration

RHEL6 dual Nic bonding configuration 1) modprobe is no longer available under RHEL6. conf file in/etc/modprobe. d/build bond0 [root@servermodprobe.d] # cat/etc/modprobe. d/bond0aliasbond0bondingoptionsbond0miimon = 100 mode = 42) The LACP mode is applied to the interface on the switch.

RHEL6 dual Nic bonding configuration
 
1) there is no modprobe. conf file in RHEL6.
Create bond0 in/etc/modprobe. d/

[Root @ server modprobe. d] # cat/etc/modprobe. d/bond0
Alias bond0 bonding
Options bond0 miimon = 100 mode = 4

2) The LACP mode is applied to the interfaces on the vswitch.

3) configure the NIC/etc/sysconfig/network-scripts/ifcfg-ethX
My configuration mode is:
DEVICE = eth0
USERCTL = no
ONBOOT = yes
MASTER = bond0
SLAVE = yes
BOOTPROTO = none
# HWADDR = 84: 2b: 2b: 59: 43: AE
# NM_CONTROLLED = yes
# IPADDR = 192.168.3.243
# NETMASK = 255.255.255.0
# TYPE = Ethernet
# IPV6INIT = no

4) Configure bond0 Nic
[Root @ server ~] # Vim/etc/sysconfig/network-scripts/ifcfg-bond0
DEVICE = bond0
USERCTL = no
BOOTPROTO = none
ONBOOT = yes
NETMASK = 255.255.255.0
GATEWAY = 192.168.3.254
IPADDR = 192.168.3.247
# BROADCAST = 192.168.3.255
# NETWORK = 192.168.3.0

5) It takes effect only after the system is restarted.

6) troubleshooting
RHEL6 starts very quickly. When the system enters, the NIC is not available, and the light on the switch is yellow. Wait a moment. If the switch light turns green, it means it is normal. But at this moment, the system still cannot ping other machines.
After/etc/init. d/network restart, the system prompts bond0 connection ativation failed: device not managed by networkmanager. The NIC light on the switch turns yellow.

Solution: chkconfig NetworkManager off;/etc/init. d/NetworkManager stop; chkconfig network on;/etc/init. d/network restart
The system prompts bond0 OK. Wait a moment. The NIC light on the switch changes from yellow to green. At this time, the machine is normal and can be pinged to other machines.