Bonding Ethernet Devices - AWS Elemental Delta

This is version 2.3 of the AWS Elemental Delta documentation. This is the latest version. For prior versions, see the Previous Versions section of AWS Elemental Delta Documentation.

Bonding Ethernet Devices

You can create as many separate bonds as you want. You can include as many Ethernet devices as you want in each bond (you can bond any number of devices together). You must have already set up the Ethernet devices that are to be bonded, as described in Adding Ethernet Devices.

Step A: Create the Bond

Create the bond to which you will add Ethernet devices in a later step.

To create the bond

  1. Click Add Device and choose Bonded.

  2. In the Add New Network Device dialog, complete the following fields.

    Field Description
    Device Name Must be named bond plus a number, typically starting at 0.
    Description Optional.
    Management Enabled Checked if the bond interface will be used for management. Check this field only if you are bonding eth0 and another Ethernet device.
    Port Bonding Mode Choose the desired mode. See the following Bonding Modes table.
    Link Mode Choose the appropriate mode. See the following MII Link Modes table.
    Carrier Check if appropriate.
    Static Routes Complete fields or leave blank.
  3. Click Create. The bond appears in the Network Devices section.

Bonding Modes

The following table describes the bonding modes that are available.

Mode ID Mode Description
0 Round Robin Sets a round robin policy for fault tolerance and load balancing among the Ethernet ports.Receives and sends out transmissions sequentially on each bonded slave interface, beginning with the first one available.
1 Active Backup Sets an active backup policy for fault tolerance. Receives and sends out transmissions via the first available bonded slave interface. The other bonded slave interface is only used if the active bonded slave interface fails.
2 Balanced XOR Sets an XOR (exclusive-or) policy for fault tolerance and load balancing (among the Ethernet ports). Using this method, the interface matches up the incoming request's MAC address with the MAC address for one of the slave NICs. Once this link is established, sends out transmissions sequentially, beginning with the first available interface.
3 Broadcast Sets a broadcast policy for fault tolerance. Sends out all transmissions on all slave interfaces.
4 IEEE 803.ad Dynamic Link Aggregation Sets an IEEE 802.3ad dynamic link aggregation policy. Creates aggregation groups that share the same speed and duplex settings. Transmits and receives transmissions on all slaves in the active aggregator. Requires a switch that is 802.3ad-compliant.
5 Adaptive Transmit Load Balancing Sets a Transmit Load Balancing (TLB) policy for fault tolerance and load balancing (among the Ethernet ports). Distributes the outgoing traffic according to the current load on each slave interface. The current slave receives incoming traffic. If the receiving slave fails, another slave takes over the MAC address of the failed slave.
6 Adaptive Load Balancing Sets an Active Load Balancing (ALB) policy for fault tolerance and load balancing. This includes transmit and receive load balancing for IPV4 traffic. Achieves receive load balancing through address resolution protocol (ARP) negotiation.

MII Link Mode Fields

The following table describes the fields for MII Link bonding mode.

Field Description
MII Monitoring Frequency Specifies the MII link-monitoring frequency in milliseconds. The frequency determines how often the link state of each slave is inspected for link failures. 100ms is a good starting point.
Down Delay Specifies the time in milliseconds to wait before disabling a slave after a link failure has been detected. Only applies to the MII Link Mode; should be a multiple of the MII Monitoring Frequency (rounded to nearest multiple). Defaults to 0.
Up Delay Specifies the time, in milliseconds, to wait before enabling a slave after a link recovery has been detected. Only applies to the MII Link Mode; should be a multiple of the MII Monitoring Frequency ( rounded to the nearest multiple). Defaults to 0.
Carrier Used in conjunction with the MII Link Mode. If checked, then MII uses MII or ETHTOOL ioctls (less efficient and uses deprecated kernel calling sequences) instead of netif_carrier_ok. This setting relies on the device driver to maintain link state.

ARP Mode Fields

The following table describes the fields for ARP bonding mode.

Field Description
ARP Interval Specifies the ARP link-monitoring frequency in milliseconds. It periodically checks slave devices for traffic; generates regular interval traffic via ARP probes for ARP IP Target.
ARP IP Target Specifies the IP address to use for ARP probes in ARP Link Mode.

Step B: Assign the Bond

After you create the bond, assign devices to it.

To assign the bond

  1. Click Edit at the far right of the first Ethernet device to assign to the bond.

  2. On the Manage Network Device dialog, in Master, choose the bond.

  3. Click Create.

    This device now shows with Master unchecked to indicate that it is bonded.

  4. Repeat for each device to include in the given bond.

  5. Repeat to add other devices to other bonds, if applicable.