Network interface card (NIC) bonding (also referred to as NIC teaming) is the bonding together of two or more physical NICs so that they appear as one logical device. This allows for improvement in network performance by increasing the link speed beyond the limits of one single NIC and increasing the redundancy for higher availability. For example, you can use two 1-gigabit NICs bonded together to establish a 2-gigabit connection to a central file server.
When bonded together, two or more physical NICs can be assigned one IP address. And they will represent the same MAC address. If one of the NICs fails, the IP address remains accessible because it is bound to the local NIC rather than to a single physical NIC.
Use the commands below to create, remove, or list the network bonds.
Note: During bond create and bond remove the ssh connection may be disconnected.
To create a network bond between two or more NICs, enter:
Network> bond create interfacelistmode
Network> bond create pubeth1,pubeth2 0
A comma-separated list of public devices that are going to be bonded.
balance-rr or 0
Transmits packet in sequential order from the first available slave through the last. This mode provides load balancing and
active-backup or 1
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.
balance-xor or 2
Transmits based on the selected transmit hash policy.
The default policy is a simple [(source MAC address XOR'd with destination MAC address) modulo slave count]. Alternate transmit
policies may be selected via the xmit_hash_policy option. This mode provides load balancing and fault tolerance.
broadcast or 3
Transmits everything on all of the slave interfaces. This mode provides fault tolerance.
802.3ad or 4
Creates aggregation groups that share the same speed and duplex settings. Utilizes all slaves in the active aggregator according
to the 802.3ad specification. Slave selection for outgoing traffic is done according to the transmit hash policy, which may
be changed from the default simple XOR policy via the xmit_hash_policy option.
Ethtool support in the base drivers for retrieving the speed and duplex of each slave.
A switch that supports IEEE 802.3ad Dynamic link aggregation. Most switches will require some type of configuration to enable
balance-tlb or 5
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.
Ethtool support in the base drivers for retrieving the speed of each slave.
balance-alb or 6
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.