Configuring VLAN trunking on a single physical adapter (Automated)

Last Updated : Oct 30, 2026 |
Prolog information
Metadata
Keywords:
VLAN trunking is a networking technique that enables the transmission of traffic from multiple Virtual Local Area Networks (VLANs) over a single physical network link. Using industry-standard protocols such as IEEE 802.1Q, VLAN trunking adds a unique VLAN identifier to each Ethernet frame, ensuring that traffic remains logically segmented across the shared link. This method improves network scalability and efficiency by reducing the need for multiple physical interfaces and simplifying cable management.
Putting VoIP and Data on separate networks is a recommended best practice and industry standard. Isolating VoIP traffic from Data/Management Traffic helps enhance network security and allows customers to implement QoS adequately. It also helps by simplifying network traffic management and troubleshooting as each network can be monitored independently. By independently monitoring each network, a network administrator can quickly identify and address issues specific to either VoIP or data/management services, improving response times and minimizing downtime.
Note:
VoIP call signaling, including messages sent to Communication Manager (CM), Session Manager (SM), media servers, Session Border Controller or other SIP/Proxy servers, should always be classified and treated as VoIP traffic. This classification remains essential even when the call does not involve media (RTP) streams at that stage, as signaling is a critical component of the VoIP session setup and control.
For ASP R7.x, VLAN tagging is configured exclusively at the hypervisor layer. VLAN configuration is not applied within the VM guest operating system or application layer.
The updated network script now supports assigning multiple VLAN IDs over the same physical adapter.
In this example, additional VLAN IDs will be configured on the same physical adapter that provides in-band management access to the KVM on a RHEL 9.6 host (e.g., eno8303). For a network topology illustration of this configuration, refer to Single bridge selection with VLAN Trunking and no bonding in an ASP 130 R7.x – Hypervisor Layer.
In the event of a misconfiguration with the primary interface, the host Cockpit UI will only be accessible through the services port.
Other:
Server port assignment and configuration for Avaya Communication Manager duplication traffic are not part of this procedure. DO NOT make changes to the Avaya CM duplication interface or to the hypervisor when configuring VLAN trunking.
Before you begin
The customer’s data switch port connected to the server must already be configured with the appropriate VLAN ID and IEEE 802.1Q VLAN tagging must be enabled.
  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 0 or press Enter to continue. In this example the existing 1G direct interface remains unchanged.
    6. 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.
    7. 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.
    8. To configure additional VLANs on the Management/VM's ports, type y.
    9. Enter 1 to 4 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.
      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: 2011 2010 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.
    10. 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.
    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 each bridge.
    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: Example output with single bridge selection and VLAN Trunking Configured – No Bonding.
[custadm@asp130-r660xs-20841 ~]$ 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? (2) 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) 0
Selected: 1G direct interface for bridge0
Using management port: eno8303
Do you want to configure a Management/VM's VLAN? y/n (y) 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):
Enter comma separated IPv4 domain search (acp.avaya.com):
Continue with these values? y=continue/n=retry/q=quit (n) y

 Bridge bridge0: initialization successful
Bridge slave port eno8303.1010 on bridge0: 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.