Hello everyone,
Now I’d like to share with you configuration corresponding to different types of network bonding
The NIC bonding mode needs to be specified for the connection between the server and the switch. There are seven types of network bonding. Mode0, mode1, mode4, and mode6 are commonly used. Mode0 requires Configuring manual Link Aggregation on the switch. Mode4 requires dynamic lacp on the switch. In other modes, the switch does not need to be configured with the link mode.
Network Bonding Types | Features | Switch Configuration |
mode=0 (balance-rr) | All links are in load balancing mode. Packets are sent to each link in Round robin fashion(That is, the first packet goes through eth0, and the next packet goes through eth1. The process repeats until the last transmission is complete.) | Configuring link aggregation in manual load balancing mode Typical configuration: # interface Eth-Trunk1 # interface GE1/0/1 eth-trunk 1 # |
mode=1(active-backup) | Only one port is in the active state, and the other ports are in the backup state. From the outside, the MAC address of the bond is unique to avoid confusing the switch. | No link aggregation is required, but MAC address flapping may occur. |
mode=2 (balance-xor) | Transmits data packets based on the specified hash policy. Providing load balancing and fault tolerance. Each destination MAC address the same slave is selected. | Configuring link aggregation in manual load balancing mode |
mode=3 (broadcast) | Transfer each packet on each slave interface | Configuring link aggregation in manual load balancing mode |
mode=4 (802.3ad) | In dynamic link aggregation mode, an aggregation group with the same rate is created. The slave selection for outgoing traffic is done based on a transmit hashing method. | Configuring link aggregation in dynamic LACP mode Typical configuration: # interface Eth-Trunk1 mode lacp-dynamic # interface GE1/0/1 eth-trunk 1 # |
mode=5 (balance-tlb) | Adaptive transmit load balancing. The outgoing traffic is distributed based on the current load on each slave and the incoming traffic is received by the current slave. If the incoming traffic fails, the failed receiving slave is replaced by the MAC address of another slave. | No link aggregation is required. |
mode=6 (balance-alb) | Adaptive load balancing. This mode includes the balance-tlb mode and the load balancing (receive load balance, rlb) for IPv4 traffic. Differences from mod=0：The eth0 traffic is fully occupied, and then eth1 is occupied. .ethX | No link aggregation is required. |
This is what I want to share with you today, thank you!
