VLAN configuration, scope, limitations, and supportability

Last Updated : Oct 30, 2026 |
Prolog information
This section outlines the supported VLAN deployment models for ASP 130 R7.0 systems running KVM on . It defines tested configurations, documents known limitations, and provides clear guidance on what changes are allowed or restricted to preserve supportability across the platform.

Supported and Validated VLAN Configuration Methods

The following VLAN configuration methods are validated and supported on ASP 130 R7.x:
  • VLAN tagging must be configured at the hypervisor level (host OS layer). VLAN tagging within guest operating systems (VMs) is not supported.
  • The default VLAN configuration workflow uses the configNetwork script for assigning a single VLAN per physical NIC or per bridge (e.g., bridge0, bridgeoob).
  • Advanced VLAN trunking and multi-VLAN configurations are now supported with the configNetwork script , specifically for:
    • Multiple VLANs on a single NIC
    • VLAN trunking with bonded interfaces (e.g., bond0)
    • LACP on 10/25 GbE ports.
  • Each VLAN will be mapped to a dedicated Linux bridge (e.g., bridge0-2011, bridge0-2014).
  • These supported methods apply to both initial deployments and subsequent reconfigurations of ASP 130 servers.