Bind multiple NICs under LinuxCentOS

Bind multiple NICs under LinuxCentOS recently touched on a piece of server load. The following describes how to bind multiple NICs to IP addresses in Linux. here is an experiment with CentOS6.3, the environment is completed under VMwareWorkstation9. First, the virtual machine LinuxCentOS... binding multiple NICs in Linux CentOS recently touched on a piece of server load. The following describes how to bind multiple NICs to IP addresses in Linux. here is an experiment using CentOS6.3, the environment is completed under VMware Workstation 9. First, there are two Nic devices in the CentOS system of the virtual machine Linux. here, we use NAT for the convenience of using the CRT software SSH. Let's not talk about it. let's get the CAT configuration directly: www.2cto.com first tells the system what driver to start bond0: [root @ localhost ~] # Cat/etc/modprobe. d/bonding. confalias bond0 bonding creates a file named: ifcfg-bond0 under the/etc/sysconfig/network-scripts/directory. [Root @ localhost ~] # Cat/etc/sysconfig/network-scripts/ifcfg-bond0DEVICE = bond0 // device name IPADDR = 192.168.8.20.// IP address PREFIX = 24 // PREFIX 24 equivalent to NETMASK = 255.255.255.0GATEWAY = 192.168.8.2 // Gateway DNS1 = 192.168.8.2 // DNS server address ONBOOT = yes // whether to start the device BOOTPROTO = none // USERCTL = no // whether to allow user control BONDING_OPTS = "mode = 1 miimon = 50″ // The Mode 0 used is round robin, 1 for the backup ifcfg-eth0 configuration: [root @ localhost ~] # Cat/etc/sysconfig/network-scripts/ifcfg-eth0DEVICE = "eth0" BOOTPROTO = "none" HWADDR = "00: 0C: 29: 72: 88: d2 "NM_CONTROLLED =" yes "ONBOOT =" yes "TYPE =" Ethernet "UUID =" Comment "MASTER = bond0SLAVE = yesUSERCTL = noifcfg-eth1 configuration: [root @ localhost ~] # Cat/etc/sysconfig/network-scripts/ifcfg-eth1DEVICE = "eth1" BOOTPROTO = "none" HWADDR = "00: 0C: 29: 72: 88: DC "NM_CONTROLLED =" yes "ONBOOT =" yes "TYPE =" Ethernet "MASTER = bond0SLAVE = yesUSERCTL = no restart network: service network restart binding is complete, the similarities between the two physical machines and multiple physical machines are similar. Nothing to say ....