Linux – Network Interface (NIC) Bonding Types

Linux – Network Interface (NIC) Bonding Types

In my previous article related to “Linux NIC Bonding“, I had explained how can you setup NIC Bonding.

I will now mention the different Network Interface (NIC) Bonding Types that can be used to setup NIC bonding.

While defining bond you mention something similar in the /etc/modprobe.conf file:

options bond0 mode=balance-alb miimon=100

Or you use the following command:

modprobe bonding mode=0 miimon=100

In both the cases you will find different values/strings mentioned against mode.

Bonding works on different modes. You can set up your bond interface according to your needs. Changing one parameters (mode=X) you can have the various bonding types.

Different modes of bonding / Network Interface (NIC) Bonding Types

The following are the various bonding modes/types:

mode=0 (balance-rr)
Round-robin policy: Transmit packets in sequential order from the first available slave through the last. This mode provides load balancing and fault tolerance.

mode=1 (active-backup)
Active-backup policy: Only one slave in the bond is active. A different slave becomes active if, and only if, the active slave fails. The bond’s MAC address is externally visible on only one port (network adapter) to avoid confusing the switch. This mode provides fault tolerance. The primary option affects the behavior of this mode.

mode=2 (balance-xor)
XOR policy: Transmit based on [(source MAC address XOR’d with destination MAC address) modulo slave count]. This selects the same slave for each destination MAC address. This mode provides load balancing and fault tolerance.

mode=3 (broadcast)
Broadcast policy: transmits everything on all slave interfaces. This mode provides fault tolerance.

mode=4 (802.3ad)
IEEE 802.3ad Dynamic link aggregation. Creates aggregation groups that share the same speed and duplex settings. Utilizes all slaves in the active aggregator according to the 802.3ad specification.

Pre-requisites:

   1. Ethtool support in the base drivers for retrieving
   the speed and duplex of each slave.
   2. A switch that supports IEEE 802.3ad Dynamic link
   aggregation.
   Most switches will require some type of configuration
   to enable 802.3ad mode.

mode=5 (balance-tlb)
Adaptive transmit load balancing: channel bonding that does not require any special switch support. The outgoing traffic is distributed according to the current load (computed relative to the speed) on each slave. Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed receiving slave.

Prerequisite:

   Ethtool support in the base drivers for retrieving the
   speed of each slave.

mode=6 (balance-alb)
Adaptive load balancing: includes balance-tlb plus receive load balancing (rlb) for IPV4 traffic, and does not require any special switch support. The receive load balancing is achieved by ARP negotiation. The bonding driver intercepts the ARP Replies sent by the local system on their way out and overwrites the source hardware address with the unique hardware address of one of the slaves in the bond such that different peers use different hardware addresses for the server.

The most used are the first four network interface (nic) bonding types or mode…

Linux – Network Interface (NIC) Bonding Types

No Comments

Post a Comment

Time limit is exhausted. Please reload CAPTCHA.