Properties of bond interfaces

enabled

Enable/disable the interface:

• on

• off

node-name

Cluster node where the bond interface is created.

netflow-profile

The Netflow profile to send statistical data to the Netflow collector. For more details on Netflow profile settings, see Configuring Netflow Profiles.

bonding

Additional bond interface parameters:

• aggr-mode: bond operation mode. The available options:

  • round-robin: Round robin mode (packets are sent sequentially starting with the first available interface and ending with the last one. This policy is used to provide load balancing and high availability.)

  • active-backup: Active backup mode (only one network interface in the bond will be active. Another slave interface can become active only if the currently active interface fails. With this policy, the MAC address of the bond interface is only visible externally through one network port to avoid problems with the switch. This policy is used to provide high availability).

  • xor: XOR mode (the transmission is allocated among the NICs using the following formula: [( XOR ) MOD ]. This means that the same NIC sends packets to the same recipients. Optionally, the transmission allocation can also be based on the xmit_hash policy. The XOR policy is used for load balancing and high availability).

  • broadcast: Broadcast mode (broadcasts everything to all network interfaces. This policy is used for high availability).

  • 802.3ad: IEEE 802.3ad mode (the default mode supported by most network switches. Creates aggregated groups of NICs with identical speed and duplex settings. When combined like this, all links in the active aggregation participate in transmission as per IEEE 802.3ad. The choice of interface for packet transmission is determined by the policy. By default, the XOR policy is used, with the xmit_hash policy as a possible alternative).

  • transmit: Adaptive transmit load balancing mode (outgoing traffic is distributed depending on the loading of each NIC (determined by the load speed). No additional configuration on the switch is required. The incoming traffic is received by the current network card. If this card fails, another card assumes the MAC address of the failed one).

  • load: Adaptive load balancing mode. Includes the previous policy plus incoming traffic balancing. No additional configuration on the switch is required. The incoming traffic is balanced through ARP negotiation. The driver intercepts ARP responses sent from the local NICs to the outside and overwrites the source MAC address with one of the unique MAC addresses of the NIC in the bond. Thus, different peers use different server MAC addresses. The incoming traffic is balanced sequentially (round-robin) among the interfaces.

• mii-monitoring: MII monitoring period in milliseconds. Determines how often the link state will be checked for failures.

• down-delay: delay time (in milliseconds) before an interface is disabled if a connection failure occurs. This option is only valid for MII monitoring (miimon). The parameter value must be a multiple of miimon,

• up-delay: delay time in milliseconds before deploying the channel if it is detected to be restored. This parameter is only valid with MII monitoring (miimon). The parameter value must be a multiple of miimon,

• lacp-rate: interval with which the partner transmits LACPDU packets in 802.3ad mode. Enumerated options:

  • slow: requests that the partner send LACPDU packets every 30 seconds.

  • fast: requests that the partner send LACPDU packets every second.

• failover-mac: define the assignment type of MAC addresses to bond interfaces in Active backup mode when switching interfaces. Enumerated options:

  • disabled: the same MAC address is set on all interfaces during switching.

  • active: the MAC address on the bond interface will always be identical to that on the currently active slave. The MAC addresses on the backup interfaces are not changed. The MAC address on the bond interface changes during the failover processing.

  • follow: the MAC address on the bond interface will be the same as that on the first slave added to the bond. This MAC is not set on the second and subsequent interfaces while they are in backup mode. That MAC address gets assigned during a failover: when a backup slave interface becomes active, it assumes a new MAC (the one on the bond interface), and the formerly active slave is assigned the MAC that the currently active one used to have.

• xmit-hash: define a hash policy for sending packets over bond interfaces in XOR or IEEE 802.3ad mode. Enumerated options:

  • l2: use only MAC addresses to generate the hash. With this algorithm, the traffic for a particular network host is always sent over the same interface. This algorithm is compatible with IEEE 802.3ad.

  • l2-3: use both MAC and IP addresses to generate the hash. This algorithm is compatible with IEEE 802.3ad.

  • l3-4: uses IP addresses and transport layer protocols (TCP or UDP) to generate the hash. This algorithm is not universally compatible with IEEE 802.3ad, as both fragmented and non-fragmented packets can be transmitted within a single TCP or UDP interaction. Fragmented packets lack the source and destination ports. As a result, packets from the same session can reach the recipient in an order other than the intended one because they are sent via different slaves.

• interface: interfaces to be bonded.

ip-addresses

Assign an IP address to the interface.

The IP addresses are specified as [ <ip_address/mask> ] or [ <ip_address/mask> <ip_address/mask> ]. In case of several IP addresses (with space used as the separator), the subnet mask is entered in the decimal format.

Important! Make sure to separate the square brackets with spaces on both sides.

mtu

Specify the MTU size.

ip-addresses

Specified IP address.

bonding interface

Bonded interfaces.