Dual bridge selection with VLAN trunking and LACP bonded interface

Last Updated : Oct 30, 2026 |
Prolog information
Metadata
Keywords:
This section outlines the implementation of the following topology: Dual bridge selection with different bonding configurations in an ASP 130 R7.0 – Hypervisor Layer.
The network script supports configuring VLAN trunking on bonded interfaces for both KVM in-band management access and application traffic. If an existing bond configuration is present, it will be replaced when LACP is enabled using 10/25 GbE interfaces. To avoid extensive service disruption, ensure proper planning and prerequisites are in place before performing the maintenance activity, as the host may lose all network connectivity once the changes are applied.
Other:
Failure to comply with prerequisites will result in the host losing network connectivity once changes are applied. In the event of misconfiguration, the server will only be accessible through the services port or console.
Before you begin
  • Both 10/25 GbE interfaces (ens1f0np0 and ens1f1np1) must be physically connected to the customer data switches.
  • IEEE 802.3ad, also known as Link Aggregation Control Protocol (LACP) must be properly configured on each data switch port connected to the ASP 130 server interfaces ens1f0np0 and ens1f1np1.
  • The customer data switch ports assigned to the LACP group for ens1f0np0 and ens1f1np1 must be configured with the appropriate VLAN IDs and have IEEE 802.1Q VLAN tagging enabled.
  • Port Speed Consistency Requirement:
    Mixing port speeds is not supported. All server NIC ports must be connected exclusively to switch ports operating at the same speed (10 GbE or 25 GbE). Configurations that connect one NIC port to a 10 GbE switch port and another to a 25 GbE switch port are not supported.
  • Cabling and Transceiver Requirements:
    Proper cabling (fiber optic or Direct Attach Copper [DAC]) and compatible transceivers are required to operate the 10/25 GbE interfaces. These interfaces use the industry-standard Small Form-Factor Pluggable 28 (SFP28) form factor. Customers must select cables and transceivers that are supported and qualified by their respective network switch vendor. Refer to the switch vendor’s documentation for the approved SFP28 cables and transceivers to ensure compatibility and correct operation.
  • Dell R660xs A3/A31 Server must be running at a minimum firmware V2 when using 10/25GbE ports and LACP bonding. Failure to comply could result in LACP bonding malfunction.
  1. Connect to the ASP host using the services port connection.
  2. Log in to the ASP host by using a Secure Shell (SSH) client e.g., PuTTY.
  3. Authenticate using the existing custadm credentials or craft if EASG is enabled.
  4. Execute the following CLI command: configNetwork.
  5. Follow the script prompts:
    1. Type y to continue if the connection is via services port.
    2. Type n to continue (OOBM configuration is not part of this procedure).
      ADDITIONAL INFORMATION:
      Note:
      The network script automatically detects if OOBM has been previously configured on the management interface. If OOBM is found, the script will display a "Y" by default. To retain the current OOBM configuration, simply press Enter without making any changes to keep the existing OOBM configuration intact.
    3. Type n to continue. Configuring OOBM bridge for VM use is not part of this procedure.
    4. Enter the number of bridges to configure <1-2>. In this example, type 2 to get a dual bridge configuration.
    5. Select the desired configuration for bridge0 (Management/VM Bridge). Type 1. In this example, a 1G active/backup bond.
    6. Script by default fixes the first bond interface to: eno8303. From the remaining list of available 1G ports, enter the second port number to use in the bond and press Enter to continue.
    7. Type y to configure a Management/VM's VLAN.
      ADDITIONAL INFORMATION:
      Note:
      The network script automatically detects if a VLAN has been previously configured on the management interface. If a VLAN is found, the script will display a “Y” by default. Press Enter to continue with the next prompt.
    8. Enter a value <1-4094> for the Management/VM's VLAN ID. For example, 1010.
      ADDITIONAL INFORMATION:
      Note:
      Some network switch vendors may support only a subset of the IEEE 802.1Q valid VLAN ID range (1–4094). Therefore, verify that the VLAN ID entered is supported by the customer’s data switch before applying any changes.
      If a VLAN has already been configured, it will be displayed in parentheses — for example: Enter the Management/VM’s VLAN ID (1010). To keep the same VLAN for management, press Enter to continue to the next prompt. Otherwise, type the appropriate VLAN ID to update the configuration.
    9. To continue without configuring additional VLANs on the Management/VM ports, type n.
      ADDITIONAL INFORMATION:
      In this example a single VLAN will be configured on the management interface (bond0->bridge0).
    10. Select the desired configuration for bridge1 (Secondary VM Bridge). Type 3, in this example a LACP bond with 10/25G interfaces will be configured.
      ADDITIONAL INFORMATION:
      Note:
      The 10 GbE or 25 GbE port selection for either an LACP bond or an A/B bond is available only if these ports have not already been selected or previously configured as members of bridge0.
    11. Select the LACP Data Units exchange rate <fast | slow>. Type 0, in this example fast will be configured.
      ADDITIONAL INFORMATION:
      Note:
      To ensure a reliable network connection, the LACP mode on the customer switch must match the server configuration. Fast mode detects link failures more quickly but can generate additional overhead, while Slow mode is the recommended default, providing stable operation with fewer false alarms, though with slower failure detection.
    12. Select the LACP load balance HASH policy <layer2 | layer3+4>. Type 1, in this example layer3+4 will be configured.
      ADDITIONAL INFORMATION:
      Note:
      Hash policy used on the server must align with what the customer switch supports, otherwise traffic distribution can become inconsistent or ineffective.
    13. The script automatically selects the available 10/25G ports (ens1f0np0, ens1f1np1) for configuring the Active/Back Up bond.
    14. To configure VLANs on the bridge1 ports, type y.
      ADDITIONAL INFORMATION:
      Note:
      The network script automatically detects current configuration. If bridge1 has been previously configured with 1 or more VLANs, these will be displayed e.g. Current VLANs: 2011
    15. Enter 1 to 5 VLAN IDs separated by spaces. Enter a value <1-4094>, for example 2010 2011 2014.
      ADDITIONAL INFORMATION:
      Note:
      Some network switch vendors may support only a subset of the IEEE 802.1Q valid VLAN ID range (1–4094). Therefore, verify that the VLAN ID entered is supported by the customer’s data switch before applying any changes.
      At this stage, the script will prompt the user to begin configuring a bridge for each VLAN ID entered in the previous step. In this example, one additional bridge will be created for VLAN IDs 2010, 2011, and 2014.
      The configNetwork script automatically assigns a default label to each new bridge including the VLAN ID. If changing the default label, it is strongly recommended to configure these labels in a way that is easy to identify, for example: VoIP-2011, Management-1010, etc.
    16. Enter the name of the bridge associated with the VLAN configured in the previous step. The script assigns a default name e.g. bridge0-2011 for VLAN 2011, bridge0-2010 for VLAN 2010 etc. Press Enter to accept the default value, or enter a different name.
      ADDITIONAL INFORMATION:
      Other:
      Bridge name must be unique. Do NOT assign the same name to multiple bridges.
      Note:
      Bridge labels must be between 2 and 15 characters in length and must contain only alphanumeric characters, a dash (-), or an underscore (_).
    17. Repeat for the remaining bridges.
      ADDITIONAL INFORMATION:
      Note:
      Although multiple changes at the same time are supported by the network script, IP address changes are not part of this procedure.
    18. Press Enter key (7 times) until prompt displays Continue with these values? y=continue/n=retry/q=quit (n). If satisfied with current selections type y.
  6. Gracefully shut down all virtual machines (VMs) and update each VM’s network configuration to assign the appropriate bridge (for example, bridge0, bridge1-2010, bridge1-2011, bridge1-2014) to each virtual network interface. This ensures proper VLAN connectivity. Power on the VMs after completing the configuration changes.
    ADDITIONAL INFORMATION:
    Figure: Output example - dual bridge selection with active/backup bond0 and LACP bond1
    [root@asp130-r660xs-20841 4ports]# ./configNetwork
    ===================  Server Network Configuration  ===================
    Note: you should run this command from the console or services port
          After making configuration changes running VMs should be restarted.


    Do you want to continue (y/n) y


    The configured or default value is displayed in parentheses ().
    Press 'enter' to accept it, enter 'd' to delete it or type a new value.


    Connect this server to an Out Of Band Management network (OOBM)? y/n (n) n
    Create an OOBM bridge for VMs use? y/n (n) n


    ========== Network Bridge Configuration ==========
    Configure network bridges for management and VMs.


    Do you want to configure 1 or 2 bridges? (1) 2


    === Configuring bridge0 (Management Bridge) ===
     0) 1G direct interface
     1) 1G active/backup bond
     2) 10/25G direct interface
     3) 10/25G LACP bond
     4) 10/25G active/backup bond


    Select configuration for bridge0: (0) 1
    Configuring 1G active/backup bond for bridge0
    Using fixed management port for first bond interface: eno8303
    Available 1G ports for second bond interface:
     0) eno8303 (first port)
     1) eno12409
     2) eno12419
     3) eno12429
     4) eno12399
    Enter the second port # to use in the bond: 1
    Note: bond ports must not be used as a direct attachment interface for any VM
    Selected ports: eno8303, eno12409




    Do you want to configure a Management/VM's VLAN? y/n (n) y
    Enter the Management/VM's VLAN ID (): 1010
    Configure additional VLANs on the bridge0 (Management/VM's) ports? y/n (n) n


     === Configuring bridge1 (Secondary VM Bridge) ===
     0) 1G direct interface
     1) 1G active/backup bond
     2) 10/25G direct interface
     3) 10/25G LACP bond
     4) 10/25G active/backup bond
     5) No second bridge


    Select configuration for bridge1: (5) 3
    Configuring 10/25G LACP bond for bridge1
     0) fast
     1) slow
    Select the LACP Data Units exchange rate (): 0
     0) layer2
     1) layer3+4
    Select the LACP load balance HASH policy (): 1
    Using available 10/25G ports for bond: ens1f0np0, ens1f1np1Enter Server
    Configure VLANs on the bridge1 ports? y/n (n) y
    Enter 1 to 5 VLAN IDs separated by spaces (q=none): 2010 2011 2014
    Enter the name of the bridge to connect to VLAN 2010 (bridge1-2010):
    Enter the name of the bridge to connect to VLAN 2011 (bridge1-2011):
    Enter the name of the bridge to connect to VLAN 2014 (bridge1-2014):
    Enter Server hostname (asp130-r660xs-20841.acp.avaya.com):
    Enter Server IPv4 (192.168.208.41):
    Enter Server netmask or /prefix (/26):
    Enter the IPv4 default gateway (192.168.208.1):
    Do you want to configure IPv6? y/n (n)
    Enter comma separated DNS servers (198.152.8.8,198.152.8.11):
    Enter comma separated IPv4 domain search (avaya.com):
     Continue with these values? y=continue/n=retry/q=quit (n) y


     Bridge bridge0: initialization successful
    Bond: initialization successful
    Bond VLAN 1010 on bridge0-port initialization successful
    Bond port bond0-port1 eno8303 initialization successful
    Bond port bond0-port2 eno12409 initialization successful
    Bridge bridge1: initialization successful
    Bond: initialization successful
    Bond port bond1-port1 ens1f0np0 initialization successful
    Bond port bond1-port2 ens1f1np1 initialization successful
    Add bridge1-2011 on bridge1-2011-port VLAN=2011
    Bridge bridge1-2011: initialization successful
    Vlan 2011 on bridge1-2011-port initialization successful
    Add bridge1-2010 on bridge1-2010-port VLAN=2010
    Bridge bridge1-2010: initialization successful
    Vlan 2010 on bridge1-2010-port initialization successful
    Add bridge1-2014 on bridge1-2014-port VLAN=2014
    Bridge bridge1-2014: initialization successful
    Vlan 2014 on bridge1-2014-port initialization successful
    Bridge bridge0: IP initialization successful.
  7. Run the following command to validate the configuration and operational status of the newly created LACP bond:
    ADDITIONAL INFORMATION: su – root
    Enter password for root account.
    cat /proc/net/bonding/bondx
    Note:
    Replace x with bond number e.g. bond0 or bond1.
    Some information will not be displayed including aggregator info if command is not executed as root/sroot (if EASG is enabled).
    In a properly functioning LACP bond configuration, the host must successfully learn both the Partner MAC Address and the Partner Key from the connected switch ports. When validating the bonding status, if the output shows Partner Key: 1 and Partner Mac Address: 00:00:00:00:00:00, this indicates that LACP negotiation has not been successfully completed between the host and the connected switch ports.
    This condition reflects an LACP misconfiguration, which may exist on the host, the switch, or both. The LACP mode, hashing policy, port membership, and aggregation settings must be configured consistently on both the host and the customer switch. Until the configurations are aligned and proper LACP negotiation occurs, the LACP bond will not operate as expected.
    Figure: Output example – LACP bond1
    Note:
    In this example, LACP Partner key on Data Switches has been configured to 131.

    [root@asp130-r660xs-20841 4ports]# cat /proc/net/bonding/bond1
    Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)


     Bonding Mode: IEEE 802.3ad Dynamic link aggregation
    Transmit Hash Policy: layer3+4 (1)
    MII Status: up
    MII Polling Interval (ms): 100
    Up Delay (ms): 0
    Down Delay (ms): 0
    Peer Notification Delay (ms): 0


     802.3ad info
    LACP active: on
    LACP rate: fast
    Min links: 0
    Aggregator selection policy (ad_select): stable
    System priority: 65535
    System MAC address: 00:62:0b:7e:b2:f0
    Active Aggregator Info:
            Aggregator ID: 2
            Number of ports: 2
            Actor Key: 21
            Partner Key: 131
            Partner Mac Address: 20:9e:f7:a4:84:00
    Slave Interface: ens1f0np0
    MII Status: up
    Speed: 25000 Mbps
    Duplex: full
    Link Failure Count: 0
    Permanent HW addr: 8c:84:74:34:f8:90
    Slave queue ID: 0
     Aggregator ID: 2
    Actor Churn State: monitoring
    Partner Churn State: monitoring
    Actor Churned Count: 0
    Partner Churned Count: 0
    details actor lacp pdu:
        system priority: 65535
        system mac address: 8c:84:74:34:f8:90
        port key: 21
        port priority: 255
        port number: 1
        port state: 63
    details partner lacp pdu:
        system priority: 32768
        system mac address: 20:9e:f7:a4:84:00
        oper key: 131
        port priority: 32768
        port number: 197
        port state: 63


     Slave Interface: ens1f1np1
    MII Status: up
    Speed: 25000 Mbps
    Duplex: full
    Link Failure Count: 0
    Permanent HW addr: 8c:84:74:34:f8:91
    Slave queue ID: 0
     Aggregator ID: 2
    Actor Churn State: monitoring
    Partner Churn State: monitoring
    Actor Churned Count: 0
    Partner Churned Count: 0
    details actor lacp pdu:
        system priority: 65535
        system mac address: 8c:84:74:34:f8:90
        port key: 21
        port priority: 255
        port number: 2
        port state: 63
    details partner lacp pdu:
        system priority: 32768
        system mac address: 20:9e:f7:a4:84:00
        oper key: 131
        port priority: 32768
        port number: 199
        port state: 63






     
Related links
Configuring VLAN trunking with bonded interfaces