Technical data

4. Packages
OPT_BONDING_DEV Default: OPT_BONDING_DEV=’no’
’yes’ activates the bonding package, ’no’ deativates the bonding package completely.
BONDING_DEV_N Default: BONDING_DEV_N=’0’
Number of bonding devices to be configured.
BONDING_DEV_x_DEVNAME Default: BONDING_DEV_x_DEVNAME=”
Name of the bonding device to be created. It should consist of the prefix ’bond’ and a
trailing number with out a leading ’0’. The numbers of the bonding devices don’t have
to start with ’0’ and need not be consecutive. Possible values could be ’bond0’, ’bond8’
or ’bond99’.
BONDING_DEV_x_MODE Default: BONDING_DEV_x_MODE=”
Specifies the bonding method. Default is round-robin ’balance-rr’. Possible values are
listed below:
balance-rr Round-robin method: Submit sequentially over all slaves from the first to the
last. This method provides both load balancing and fault tolerance.
active-backup Active backup: Only one slave in the bond is active. The other slaves are
activated only when the active slave fails. The MAC address of the bond is only
visible on one port (network adapter) so it does not confuse the switch. This mode
provides fault tolerance.
balance-xor XOR method: Submit based on the formula [ (Source-MAC-address XOR
destination-MAC-address) modulo the number of slaves]. This ensures that the
same slave always is used for the same destination-MAC-address. This method
provides both load balancing and fault tolerance.
broadcast Broadcast method: Transmits everything on all slave devices. This mode
provides fault tolerance.
802.3ad IEEE 802.3ad dynamic link aggregation. Creates aggregation groups that share
the same speed and duplex settings. Transmits on all slaves in the active aggregator.
Requirements:
• ethtool support in the base device driver to retrieve speed and duplex status
for each device.
• a switch that supports dynamic IEEE 802.3ad connection aggregation.
balance-tlb Adaptive load balancing for outgoing data: channel bonding that does not
need any special features in the switch. The outgoing network traffic is distributed
on each slave according to the current load. Incoming network traffic is received
by the current slave. If the receiving slave fails, another slave takes over the MAC
address of the slave gone down.
Requirements:
• ethtool support in the base device driver to retrieve speed and duplex status
for each device.
79