Section – Bonded Network Interfaces
Bonded Network Interfaces

In addition to physical interfaces, Airlock Gateway supports bonding interfaces. These can be used for failover configurations on interface level. Please note that physical interfaces used for bonding can no longer be used as a virtual interface, however bonding interfaces can be used as a base for virtual interfaces.

Logical name

The logical name will be referenced in virtual hosts, virtual network interfaces, back-end addresses, management access and failover configuration.

Physical interface 1 and 2

Specify which two physical interfaces are used to setup a bonding interface.

Bonding mode

Specify which bonding mode to use.

Link aggregation (IEE802.ad) requires special switching hardware.

Bonding Mode
Description
Active-Backup
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.
Balance-RR
Round-robin policy that transmits packets in sequential order from the first available slave through the last. This mode provides load balancing and fault tolerance.
Balance-XOR
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.
Balance-TLB
Adaptive transmit load balancing is a 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.
  • Requires:
  • Ethtool support in the base drivers for retrieving the speed and duplex of each slave.
Balance-ALB
Adaptive load balancing that 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.
Broadcast
Transmits everything on all slave interfaces. This mode provides fault tolerance.
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.
  • Requires:
  • 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 802.3ad mode.

MTU size

Allows to specify the MTU size of an interface. Please note that jumbo frames (more than 1500) may not be supported in all environments. Ask your network administrator for more details.