Virtual Network Card and network card Aggregation

In many cases, when the traffic exceeds MB and the network adapter is only MB, what should we do? In this case, using two M NICs to increase the bandwidth is a good solution. How can the two NICs be combined? 1. add virtual NIC: vi/etc/sysconfig/network-scripts/ifcfg-bond0 DEVICE = bond0 BOOTPROTO = static BROADCAST = 192.168.1.255 IPADDR = 192.168.1.2 NETMASK = 255.255.255.0 ONBOOT = yes 2. modify the original physical Nic settings: Nic 1 DEVICE = eth0 ONBOOT = yes BOOTPROTO = dhcp Nic 2 DEVICE = eth1 ONBOOT = yes BOOTPROTO = dhcp 3. added the virtual Nic Module vi/etc/modprobe. conf alias bond0 bonding options bond0 miimon = 100 mode = 0 Note: miimon is used for link monitoring. For example: miimon = 100, The system monitors the link connection status every Ms. If one line fails, it is transferred to another line. The value of mode indicates the working mode, which has a total, two or three modes, commonly used: 0, 1. Mode = 0 indicates that the load balancing (round-robin) method is load balancing, and both NICs work. Mode = 1 indicates that fault-tolerance (active-backup) provides redundancy, working in the active/standby mode. That is to say, by default, only one network card works and the other is used for backup. bonding can only provide link monitoring, that is, whether the link from the host to the switch is connected. If the switch's external link is down, and the switch itself is not faulty, therefore, bonding considers that the link is correct and continues to use the mode = 0 configuration in this case for load balancing to improve system performance and increase concurrency bandwidth. 4. add to automatically run vi/etc/rc at startup. d/rc. local ifenslave bond0 eth0 eth1 route add-net 192.168.1.254 netmask 255.255.255.0 bond0 after restarting the system, you can see three NICs. The bond0 traffic is the sum of eth0 + eth1. View bond0 virtual Nic cat/proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.1.2 (January 20,200 7) Bonding Mode: load balancing (round-robin) MII Status: up MII Polling Interval (MS): 100 Up Delay (MS): 0 Down Delay (MS): 0 Slave Interface: eth0 MII Status: up Link Failure Count: 0 Permanent HW addr: 00: 1e: 4d: 24: ec: 49 Slave Interface: eth1 MII Status: up Link Failure Count: 0 Permanent HW addr: 00: 1e: 4d: 24: ed: 4b 5. test and verify that the ping test is performed on a machine with the same external network segment. Manually unplug any network line from the machine with two NICs (or use ifup eth0 & ifdown eth1 ), the terminal on which the machine is pinged should have no interruption information, or a "timeout" will be restored quickly, which proves that the test was successful.