Several modes of the Linux NIC Bond __linux

Linux Network card bond: Maps two physical network adapters (or port) to interfaces with the same logical IP. Bond technology is similar to the port convergence between switches and the commonly used storage multipath (Multiputh) in San technology.
Role: Increase bandwidth, such as two precursor to a network card after the bond can be the local host's single IP bandwidth increased by twice times.
Increase availability, do ha protection, and the IP address is still available after a single network port down.

Bond has been in contact for a long time, and the original Project Center computer server and database services are set up bond. The current project mainly uses bond to increase data bandwidth.
There are very detailed English information on the Internet: http://www.linuxfoundation.org/collaborate/workgroups/networking/bonding#Requirements_for_specific_modes
Here's a summary of the differences between the several bond modes:
Mode 1 Active-backup
The simplest method of master-slave hot standby is to use only one physical network in bond, and to enable the standby network port immediately if the current main network port is down.
Mode 2 Banlance-xor
The simplest load sharing mode, all current physical ports are available, bond driver simple calculation hash value to select the physical port of the packet. The rule is to take source and destination of the difference or value, and then divided by the number of physical network in bond, the result is the number of selected network port.
Mode 4 802.3ad
Similar to Mode2, load sharing mode, all current physical ports are available. The difference between the Mode2 and the port selection policy. The MOD4 adopts the xmit_hash_policy stipulated in the 802.3AD protocol.
Requirements: Ethtool is able to recognize the speed and duplex of the physical port.
Switch supports dynamic link aggregation as defined in the 802.3AD protocol.

Mode 5 banlance-tlb

The port load selection strategy is more intelligent than Mode 2, which takes into account the local bond port speed when making port hashes.        Unlike mode 4, special support for switch is required. Requirements: Ethtool is able to recognize the speed and duplex of the physical port.

Description:

Both mode 2 and Mode 5 do not require special support for the switch. In this mode, the bond driver modifies the underlying ARP stack. When the bond host host responds to ARP reply messages, the bond driver modifies the local MAC address in the ARP reply message to the Mac of the bond driver specified physical port. For the two different external hosts Host2 and host3 of the same LAN, they see that the MAC address of the host1 of the configuration bond may be different. If you configure Bond's host1 host to communicate with the local area network, then all MAC layer packets have the same destination, which means that mode 2, 4, and 5 will cause only one physical port to do the transceiver.

Mode 0 BANLANCE-RR

Load sharing mode, the only mode that can load the same TCP socket into all physical ports in stripe mode. The bond driver packet the same socket, and in turn chooses a different physical port in Rond-robin, similar to RAID 0. Switch support trunking or EtherChannel is required.

This method may cause the TCP message to send and receive in the disorderly order, therefore needs to adjust the host host's TCP retransmission system parameter: net.ipv4.tcp_reordering.

Mode 0 guarantees the host host TCP stripe, but whether the host can do stripe at the time of the contract, depends on whether the switch supports TCP stripe. A lot of switches in a ether channel contract, just according to the TCP/UDP port number of a hash value to select the physical port, so that the same TCP socket message can only be sent to the fixed physical port at a time. At this point, mode 0 's stripe is only one-way rather than duplex.

Description:

EtherChannel is actually a technology that says multiple physical ports are mapped to the same logical physical port as Cisco switch. The 802.3AD is an open standard for EtherChannel, and it is the same kind of technology.

Original address: http://m.blog.csdn.net/blog/load2006/10001835