Configuring Bond Interfaces in Gaia Clish

In Gaia Clish, bond interfaces are called bonding groups.

Step

Instructions

1

Make sure that the physical subordinate interfaces do not have IP addresses.

2

Add a new bonding group.

3

Set the state of the physical subordinate interfaces to UP.

4

Add subordinate interfaces to the bonding group.

5

Configure the bond operating mode.

6

Configure other bond parameters: primary interface, media monitoring, and delay rate.

7

Examine the bonding group configuration.

8

Save the configuration.

Notes:

  • You configure an IP address on a Bonding Group in the same way as you do on a physical interface (see Physical Interfaces).

  • The name of a Bond interface in Gaia is "bond<Bond Group ID>".

    For example, the name of a bond interface with a Bond Group ID of 5 is "bond5".

  • To configure MTU on a Bond subordinate interface, you must configure MTU on the Bond interface.

    This MTU applies to all subordinate interfaces assigned to this Bond interface.

    See Configuring Physical Interfaces in Gaia Clish.

Important:

  • On Scalable Platforms, you must run the applicable commands in Gaia gClish of the applicable Security Group.

  • After you add, configure, or delete features, run the "save config" command to save the settings permanently. Scalable Platforms save the changes automatically.

Syntax

Syntax

add bonding group <Bond Group ID>

Example

gaia> add bonding group 777

Note - Do not change the state of bond interface manually using the "set interface <Bond ID> state" command. This is done automatically by the bonding driver.

Syntax

add bonding group <Bond Group ID> interface <Name of Subordinate Interface>

Important:

  • Make sure that the subordinate interfaces, which you wish to add to the Bonding Group, do not have IP addresses.

  • The Bond interface gets its MAC Address from the first subordinate interface you add to the bonding group.

Example

gaia> add bonding group 777 interface eth4

gaia> add bonding group 777 interface eth5

Notes:

  • The subordinate interfaces must not have IP addresses assigned to them.

  • The subordinate interfaces must not have aliases assigned to them.

  • In this example, the first subordinate interface is eth4.

    Therefore, the Bond interface 777 gets is MAC Address from the interface is eth4.

  • A bond interface can contain between two and eight subordinate interfaces.

Syntax

set bonding group <Bond Group ID>
      mode active-backup [primary <Name of Subordinate Interface>]
      mode round-robin
      mode 8023AD [lacp-rate {slow | fast}]
      mode xor xmit-hash-policy {layer2 | layer3+4}
      mode ABXOR xmit-hash-policy {layer2 | layer3+4} [abxor-threshold <min number of UP subordinate interfaces>]
      [up-delay <0-5000>]
      [down-delay <0-5000>]
      [mii-interval <1-5000>]
      [min-links <0-8>]

Bond operating mode specifies how subordinate interfaces are used in a bond interface.

Syntax

set bonding group <Bond Group ID> mode
      round-robin
      active-backup [primary <Name of Subordinate Interface>]
      xor xmit-hash-policy {layer2 | layer3+4}
      8023AD [lacp-rate {slow | fast}]
      ABXOR xmit-hash-policy {layer2 | layer3+4} [abxor-threshold <Min number of UP subordinate interfaces>]

Example

gaia> set bonding group 1 mode active-backup primary eth2

gaia> set bonding group 2 mode xor xmit-hash-policy layer3+4

Notes:

  • The Active-Backup mode supports configuration of the primary subordinate interface.

  • The XOR mode requires the configuration of the transmit hash policy.

  • The 8023AD mode supports the configuration of the LACP packet transmission rate and the transmit hash policy.

The Up-Delay specifies show much time in milliseconds to wait before enabling a subordinate interface after link recovery was detected.

Syntax

set bonding group <Bond Group ID> up-delay <0-5000>

Example

gaia> set bonding group 1 up-delay 100

Note - The default up-interval value is 200 ms.

The Down-Delay specifies how much time in milliseconds to wait before disabling a subordinate interface after link failure was detected.

Syntax

set bonding group <Bond Group ID> down-delay <0-5000>

Example

gaia> set bonding group 1 down-delay 100

Note - The default down-interval value is 200 ms.

The Media Monitoring Interval specifies how much time in milliseconds to wait before checking the link on subordinate interfaces for a failure.

Syntax

set bonding group <Bond Group ID> mii-interval <1-5000>

Example

gaia> set bonding group 1 mii-interval 100

Note - The default mii-interval value is 100 ms.

You can configure the minimum number of required interface links for a bonding group in the 802.3AD / 802.1AX mode.

If fewer subordinate interfaces in a bonding group have their link in the "up" state, the Gaia changes the state of the bonding group to "down".

Syntax

set bonding group <Bond Group ID> min-links <0-8>

Example

gaia> set bonding group 1 min-links 2

Note - The default "min-links" value is 0. With this value, the minimum number of required subordinate interfaces that must stay in the "up" state in a bond of N subordinate interfaces is N-1.

 
set interface <Bond Group ID>
      comments "Text"
      ipv4-address <IPv4 Address> {subnet-mask <Mask> | mask-length <Mask Length>}
      ipv6-address <IPv6 Address> mask-length <Mask Length>
      ipv6-autoconfig {on | off}
      link-speed {10M/half | 10M/full | 100M/half | 100M/full | 1000M/full | 10000M/full}
      mac-addr <MAC Address>

For more information, see Configuring Physical Interfaces in Gaia Clish.

Syntax

delete bonding group <Bond Group ID> [interface <Interface Name> | force-ignore-routes]

Example

gaia> delete bonding group 777 interface eth4

Note - You must delete all non-primary subordinate interfaces before you remove the primary subordinate interface.

Syntax

delete bonding group <Bond Group ID> interface <Name of Subordinate Interface 1>

delete bonding group <Bond Group ID> interface <Name of Subordinate Interface 2>

delete bonding group <Bond Group ID> interface <Name of Subordinate Interface ...>

delete bonding group <Bond Group ID> interface <Name of Subordinate Interface N>

delete bonding group <Bond Group ID>

Example

gaia> delete bonding group 777

Notes:

  • You must delete all non-primary subordinate interfaces before you remove the primary subordinate interface.

  • You must delete all subordinate interfaces from the bonding group before you remove the bonding group.

  • Do not change the state of bond interface manually using the "set interface bondID state" command.

    This is done automatically by the bonding driver.

Syntax

show bonding {group <Bond Group ID> | groups}

Parameters

Parameter

Description

<Bond Group ID>

Configures the Bond Group ID.

  • Range: 0 - 1024

  • Default: No default value

<Name of Subordinate Interface>

Specifies the name of the subordinate physical interface, which you add to (or remove from) the bond group.

Make sure that the subordinate interfaces do not have any IP addresses or aliases configured.

mode <Mode>

Configures the Bond operating mode (see Bond Interfaces (Link Aggregation)):

  • round-robin

    Bond uses all subordinate interfaces sequentially (High Availability + Load Sharing).

    This is the default mode.

    Note - Scalable Platform Security Groups do not support this feature (Known Limitation MBS-4080).

  • active-backup [primary <Name of Subordinate Interface>]

    Bond uses one subordinate interface at a time (High Availability)

  • xor xmit-hash-policy {layer2 | layer3+4}

    Bond uses subordinate interfaces based on a hash function (High Availability + Load Sharing)

  • 8023AD [lacp-rate {slow | fast}]

    Dynamic bonding according to IEEE 802.3ad / 802.1ax - LACP (Load Sharing)

  • ABXOR xmit-hash-policy ...

    Subordinate interfaces in the UP state are assigned to sub-groups called bundles.

    Only one bundle is Active at a time.

    All subordinate interfaces in the Active bundle share the traffic load.

    The system assigns traffic to all interfaces in the Active bundle based on the defined transmit hash policy.

    Note - Scalable Platform Security Groups do not support this feature (Known Limitation MBS-1520).

primary <Name of Subordinate Interface>

Specifies the name of the primary subordinate interface in the bond.

By default, the first subordinate interface added to the bond group, becomes the primary.

Important - You must not configure the primary subordinate interface explicitly in ClusterXL when you configure the Sync interface on a bonding group for redundancy. For more information, see the R82 ClusterXL Administration Guide > Chapter ClusterXL Requirements and Compatibility > Section Supported Topologies for Synchronization Network.

Note - Applies only to the Active-Backup bond mode.

up-delay <0-5000>

Specifies the time in milliseconds to wait before enabling a subordinate interface after link recovery was detected.

  • Range: 0 - 5000 ms

  • Default: 200 ms

down-delay <0-5000>

Specifies the time in milliseconds to wait before disabling a subordinate interface after link failure was detected.

  • Range: 0 - 5000 ms

  • Default: 200 ms

lacp-rate {fast | slow}

Specifies the Link Aggregation Control Protocol (LACP) packet transmission rate:

  • slow - LACPDU packets are sent every 30 seconds

  • fast - LACPDU packets are sent every second

Note - Applies only to the 802.3AD bond mode.

mii-interval <1-5000>

Specifies the time in milliseconds to wait before checking the link on subordinate interfaces for a failure.

  • Range: 1 - 5000 ms

  • Default: 100 ms

min-links <0-8>

Specifies the minimum number of required interface links for a bonding group in the 802.3AD mode.

If fewer subordinate interfaces in a bonding group have their link in the "up" state, the Gaia changes the state of the bonding group to "down".

  • Range: 0 - 8

  • Default: 0 (the minimum number of required subordinate interfaces that must stay in the "up" state in a bond of N subordinate interfaces is N-1)

Notes:

  • Applies only to the 802.3AD bond mode.

  • In a cluster, also refer to the command "set interface <Bond Group ID> links". For more information, see the R82 ClusterXL Administration Guide > Chapter ClusterXL Requirements and Compatibility > Section Configuring the Minimum Number of Required Subordinate Interfaces for Bond Load Sharing.

xmit-hash-policy {layer2 | layer3+4}

Specifies the algorithm to use for assigning the traffic to Active subordinate interfaces:

  • layer2 - Based on the XOR of hardware MAC addresses

  • layer3+4 - Based on the IP addresses and Ports

Note - Applies only to the XOR and the 802.3AD bond modes.

abxor-threshold <Min number of UP subordinate interfaces>

Specifies the minimum number of subordinate interfaces that must be in the UP sate for a bundle to be Active.

Notes:

  • Applies only to the ABXOR and the 802.3AD bond modes.

  • Scalable Platform Security Groups do not support this feature (Known Limitation MBS-1520).

Examples

gaia> add bonding group 1
gaia> add bonding group 1 interface eth2
gaia> add bonding group 1 interface eth3
gaia> set bonding group 1 mode active-backup primary eth2
gaia> show bonding group 1
Bond Configuration
    xmit-hash-policy Not configured
    down-delay 200
    primary eth2
    lacp-rate Not configured
    mode active-backup
    up-delay 200
    mii-interval 100
    Bond Interfaces
        eth2
        eth3
gaia>
 
gaia> add bonding group 1
gaia> add bonding group 1 interface eth2
gaia> add bonding group 1 interface eth3
gaia> set bonding group 1 mode xor xmit-hash-policy layer3+4
gaia> show bonding group 1
Bond Configuration
    xmit-hash-policy layer3+4
    down-delay 200
    primary Not configured
    lacp-rate Not configured
    mode xor
    up-delay 200
    mii-interval 100
    Bond Interfaces
        eth2
        eth3
gaia>