![skybox 7000 Quick Start Manual Download Page 20](http://html.mh-extra.com/html/skybox/7000/7000_quick-start-manual_1290110020.webp)
Skybox Appliance 5500 Quick Start Guide
Skybox version 10.1.200
20
mode=1 (active-backup)
Active-backup policy: Only a single 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 a single port (network adapter) to avoid confusing the
switch. This mode provides fault tolerance. The primary option affects the
behavior of the mode.
mode=2 (balance-xor)
XOR policy: Transmits based on [(source MAC address XORed 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.
Prerequisites:
›
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
require 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 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 transmit load balancing and receive load
balancing 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 a
slave in the bond such that different peers use different hardware addresses for
the server.