Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
howtos:misc:network_interace_bonding [2018/03/08 18:10 (UTC)]
lamerix adding balancing algorighm modes description
howtos:misc:network_interace_bonding [2018/03/08 18:15 (UTC)] (current)
lamerix small fixes
Line 40: Line 40:
 ====== Bonding modes ====== ====== Bonding modes ======
  
-  * **balance-rr ​or 0** 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 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.  
-  * **active-backup ​or 1** 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.  +  * **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.  
-  * **balance-xor ​or 2** XOR policy: Transmit based on the selected transmit,​hash policy.,The default policy is a simple [(source MAC address XOR'd with destination MAC address XOR packet type ID) modulo slave count].,​Alternate transmit policies may be,selected via the xmit_hash_policy option, described below. This mode provides load balancing and fault tolerance.  +  * **mode 2 / balance-xor** ​XOR policy: Transmit based on the selected transmit,​hash policy.,The default policy is a simple [(source MAC address XOR'd with destination MAC address XOR packet type ID) modulo slave count].,​Alternate transmit policies may be,selected via the xmit_hash_policy option, described below. This mode provides load balancing and fault tolerance.  
-  * **broadcast or 3** Broadcast policy: transmits everything on all slave,​interfaces.,​This mode provides fault tolerance.  +  * **mode / broadcast** Broadcast policy: transmits everything on all slave,​interfaces.,​This mode provides fault tolerance.  
-  * **802.3ad ​or 4** 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.  +  * **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.  
-  * **balance-tlb ​or 5**  Adaptive transmit load balancing: channel bonding that,does not require any special switch support.In tlb_dynamic_lb=1 mode; the outgoing traffic is,​distributed according to the current load (computed,​relative to the speed)on each slave., In tlb_dynamic_lb=0 mode; the load balancing based on,current load is disabled and the load is distributed,​only using the hash distribution.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.  +  * **mode 5 / balance-tlb** ​Adaptive transmit load balancing: channel bonding that,does not require any special switch support.In tlb_dynamic_lb=1 mode; the outgoing traffic is,​distributed according to the current load (computed,​relative to the speed)on each slave., In tlb_dynamic_lb=0 mode; the load balancing based on,current load is disabled and the load is distributed,​only using the hash distribution.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.  
-  * **balance-alb ​or 6**  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.+  * **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.
  
 <​note>​ <​note>​
-**mode 4 802.3ad** and **mode 5 balance-tlb** have some prerequisites. Check kernel docs for more information+**mode 4 802.3ad** and **mode 5 balance-tlb** have some prerequisites. Check kernel docs for more information
 </​note>​ </​note>​
  
Line 56: Line 56:
 **xmit_hash_policy** option sets the balancing algorithm used. **xmit_hash_policy** option sets the balancing algorithm used.
  
-The default value is layer2. ​+//The default value is layer2.// 
  
  
-  * **layer2** Uses XOR of hardware MAC addresses to generate the hash. This algorithm will place all traffic to a particular network peer on the same slave. +  * **layer2** ​Uses XOR of hardware MAC addresses to generate the hash. This algorithm will place all traffic to a particular network peer on the same slave. 
-  * **layer2+3** Uses XOR of hardware MAC addresses and IP addresses to generate the hash. This algorithm will place all traffic to a particular network peer on the same slave. +  * **layer2+3** ​Uses XOR of hardware MAC addresses and IP addresses to generate the hash. This algorithm will place all traffic to a particular network peer on the same slave. 
-  * **layer3+4** This policy uses upper layer protocol information,​ when available, to generate the hash. This allows for traffic to a particular network peer to span multiple slaves, although a single connection will not span multiple slaves. +  * **layer3+4** ​This policy uses upper layer protocol information,​ when available, to generate the hash. This allows for traffic to a particular network peer to span multiple slaves, although a single connection will not span multiple slaves. 
-  * **encap2+3** This policy uses the same formula as layer2+3 but it relies on skb_flow_dissect to obtain the header fields which might result in the use of inner headers if an encapsulation protocol is used. +  * **encap2+3** ​This policy uses the same formula as layer2+3 but it relies on skb_flow_dissect to obtain the header fields which might result in the use of inner headers if an encapsulation protocol is used. 
-  * **encap3+4** This policy uses the same formula as layer3+4 but it relies on skb_flow_dissect to obtain the header fields which might result in the use of inner headers if an encapsulation protocol is used.+  * **encap3+4** ​This policy uses the same formula as layer3+4 but it relies on skb_flow_dissect to obtain the header fields which might result in the use of inner headers if an encapsulation protocol is used.
  
  

In Other Languages
QR Code
QR Code howtos:misc:network_interace_bonding (generated for current page)