Configurations réseau : bonding Linux

De $1

 

Différentes configurations possibles 

 

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 mode types... 

 

 

 howto05_small.pngPour connaître l'état d'un Bond sous Linux

 

less /proc/net/bonding/bond0 

 

Exemple de réponse :

Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)


Bonding Mode: IEEE 802.3ad Dynamic link aggregation

Transmit Hash Policy: layer2+3 (2)

MII Status: up

MII Polling Interval (ms): 100

Up Delay (ms): 0

Down Delay (ms): 0


802.3ad info

LACP rate: slow

Aggregator selection policy (ad_select): stable

Active Aggregator Info:

        Aggregator ID: 3

        Number of ports: 2

        Actor Key: 17

        Partner Key: 213

        Partner Mac Address: f0:92:1c:c8:98:40


Slave Interface: eth10

MII Status: up

Speed: 1000 Mbps

Duplex: full

Link Failure Count: 1

Permanent HW addr: 00:15:17:61:98:27

Aggregator ID: 3

Slave queue ID: 0


Slave Interface: eth11

MII Status: up

Speed: 1000 Mbps

Duplex: full

Link Failure Count: 1

Permanent HW addr: 00:1b:21:2c:ab:a5

Aggregator ID: 3

Slave queue ID: 0 

 

 

 

 howto05_small.pngVous en pensez quoi ?


 

 

 

  

Cette page n'a encore aucun contenu. Enrichissez Yakakliker en y contribuant vous aussi.

FichierTailleDateAttaché par 
 etherchannel.pdf
Aucune description
73.66 Ko10:40, 29 Déc 2011franckActions
Images (0)
 
Commentaires (0)
Vous devez être connecté pour poster un commentaire.