Configuring VLAN trunking on an active/backup bonded interface

Last Updated : Oct 30, 2026 |
Prolog information
Metadata
Keywords:
This section outlines the implementation of the following topology: Single bridge selection with VLAN trunking and bonding in an ASP 130 R7.0 – Hypervisor Layer.
The host management interface will be re-configured to support VLAN trunking on bond0 for in-band host management access and application traffic.
Note:
VLAN trunking can also be configured on bond1 for bridge1 when selecting a 2-bridge configuration.
  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>. Type 1, in this example a single bridge will be configured.
    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.
      ADDITIONAL INFORMATION:
      In this example option 1 will be selected.
    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 configure additional VLANs on the Management/VM's ports, type y.
    10. Enter 1 to 4 VLAN IDs separated by spaces. Enter a value <1-4094>, for example 2010 2011 2014.
      ADDITIONAL INFORMATION:
      Note:
      The network script automatically detects current configuration. If management interface has been previously configured with 1 or more VLANs, these will be displayed e.g. Current VLANs: 2010 2011 2014
      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.
    11. 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 (_).
    12. Repeat for the remaining bridges.
    13. 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.
Figure: Output example with single bridge selection and VLAN trunking on a bonded interface
[root@asp130-r660xs]# ./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) 1


 === Configuring bridge0 (Management/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


 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) y
Enter 1 to 4 VLAN IDs separated by spaces (q=none): 2010 2011 2014
Enter the name of the bridge to connect to VLAN 2010 (bridge0-2010):
Enter the name of the bridge to connect to VLAN 2011 (bridge0-2011):
Enter the name of the bridge to connect to VLAN 2014 (bridge0-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
Add bridge0-2011 on bridge0-2011-port VLAN=2011
Bridge bridge0-2011: initialization successful
Vlan 2011 on bridge0-2011-port initialization successful
Add bridge0-2010 on bridge0-2010-port VLAN=2010
Bridge bridge0-2010: initialization successful
Vlan 2010 on bridge0-2010-port initialization successful
Add bridge0-2014 on bridge0-2014-port VLAN=2014
Bridge bridge0-2014: initialization successful
Vlan 2014 on bridge0-2014-port initialization successful
Bridge bridge0: IP initialization successful.
Figure: Output example – 2 bridge configuration with VLAN trunking on a second active/backup bond (bond1)
Host Networking Construct
  • Host in-band management access will be configured with a single VLAN using bond0->bridge0, however, VLAN trunking can be configured on bond0 as well.
  • For Application traffic, bond1->bridge1 will be configured with multiple VLANs 2011 2010 2014.
Note:
Port selection for every bonded interface in this example is for reference only.
[root@asp130-r660xs]# ./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) 1
Configuring 1G active/backup bond for bridge1
Available 1G ports:
 0) eno12419
 1) eno12429
 2) eno12399
 Enter the first port # to use in the bond: 0
Available 1G ports for second bond interface:
 0) eno12419 (first port)
 1) eno12429
 2) 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: eno12419, eno12429


 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 eno12419 initialization successful
Bond port bond1-port2 eno12429 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.
Related links
Configuring VLAN trunking with bonded interfaces