Configure the ASP Host Management Interface for VLAN Tagging

Last Updated : Oct 30, 2026 |
Prolog information
The ASP Host (KVM on RHEL 9.6) management interface can be configured to support VLAN tagging (IEEE 802.1Q). The following guidelines provide instructions for configuring the appropriate NICs on the server to enable this functionality.
In this configuration example, a single VLAN will be created and assigned to bridge0. However, the same process can be followed when configuring a VLAN ID to OOBM interface.
Before you begin
During the maintenance activity, the customer network administrator must configure the appropriate VLAN ID on the data switch port that connects the server to the management network and enable VLAN tagging (IEEE 802.1Q) on that port. Failure to do so will result in the server (hypervisor) being disconnected from the network after the VLAN configuration changes are applied.
Note:
When modifying the host network configuration of the primary interface using the configNetwork script, it is mandatory to connect to the server through the designated services port. The script automatically applies the changes and restarts network services, terminating any active connections over the primary interface. If a network misconfiguration occurs, access to the server may only be possible through the services port or local console.
  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 without creating an OOBM bridge.
    4. Enter the number of bridges to configure: 1. In this example, only bridge0 will be reconfigured.
    5. Select the desired configuration for bridge0 (Management/VM Bridge). In this example, type 0 for a 1G direct interface.
      ADDITIONAL INFORMATION:
      Note:
      The network script automatically detects current configuration. If a bond has been previously configured on the management interface the script will display current configuration e.g. (1) for 1G active/backup bond. To retain the current bond configuration, simply press Enter without making any changes to keep the existing bonding configuration intact.
    6. Type y to configure a Management/VM's VLAN.
    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.
    8. Type n to continue. In this example a single VLAN will be configured.
    9. 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.
      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.
Figure: Example output with single bridge selection and single VLAN 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? (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) 0
Selected: 1G direct interface for bridge0
 Using management port: eno8303
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
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.11):
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
Bridge bridge0: IP initialization successful.