Supported and validated configuration methods

Last Updated : Oct 30, 2026 |
Prolog information
Metadata
Keywords:
The following VLAN configuration methods are officially supported and validated by Avaya for the ASP 130 R7.x solution. Any deviations from these methods require prior written approval from Avaya.

Supported Methods

  • Single VLAN per Interface (Standard Configuration):
    The configNetwork script can be used to assign a single VLAN to a physical interface. This is the default and most supported deployment for basic management and application separation.
  • VLAN Trunking on a Single Adapter:
    VLAN tagging using 802.1Q can be applied to a single NIC using the configNetwork script. Multiple VLANs are supported, with each VLAN requiring its own Linux bridge (e.g., bridge0-2011, bridge0-2014). This method enables multiple traffic segments over a single 1/10/25 GbE port.
  • VLAN Trunking with Bonded Interfaces:
    • Bonded interfaces in active-standby mode (1 GbE Ports ONLY) may be used as parent interfaces for trunked VLANs. VLANs must be created on the bond (e.g., bond0.1010, bond0.2011) and assigned to independent bridges. This topology offers resiliency and simplifies cable management while preserving VLAN segmentation.
    • Bonded interfaces in active-active mode (10/25 GbE Ports ONLY) may be used as parent interfaces for trunked VLANs. VLANs must be created on the bond (e.g., bond0.1010, bond0.2011) and assigned to independent bridges. This topology offers resiliency and simplifies cable management while preserving VLAN segmentation. This configuration requires having Link Aggregation Control Protocol (LACP) configured on the customer switch ports connecting ASP 130 servers to the network.
IEEE 802.3ad, also known as Link Aggregation Control Protocol (LACP), is a standard for bundling multiple Ethernet links into a single logical link. This approach enhances bandwidth, provides redundancy, and ensures fault tolerance. It is widely used in networking environments to improve performance and reliability.
Key Features of IEEE 802.3ad
  1. Link Aggregation: Combines multiple physical Ethernet links into one logical interface, increasing aggregate bandwidth and providing failover capabilities.
  2. Dynamic Negotiation: Uses LACP to dynamically negotiate and manage link aggregation between devices, ensuring compatibility and optimal configuration.
  3. Load Balancing: Distributes traffic across aggregated links based on algorithms like source/destination MAC or IP addresses, ensuring efficient utilization of all links.
  4. Fault Tolerance: Automatically reroutes traffic to active links if one or more links in the bundle fail, maintaining uninterrupted communication.

Configuration Requirements

  • All aggregated links must operate at the same speed and in full-duplex mode.
  • LACP must be supported and enabled on both the host (ASP 130 KVM on RHEL 9.6 server) and the connected customer data switch.
  • Adapters of different line speeds or duplex modes may cause performance issues if improperly configured.

Modes of Operation

  • Active Mode: The port actively sends LACP packets to negotiate link aggregation.
  • Passive Mode: The port responds to LACP packets but does not initiate negotiation.
Note:
Both modes can form a link aggregation if at least one side is in active mode.
LACP periodically transmits keepalive frames over an aggregated link to verify the connectivity of each member link and to trigger a failover in the event of a malfunction. LACP can be configured with a fast or slow periodic rate, resulting in an effective detection time of approximately ~3 seconds or ~90 seconds, respectively, assuming the standard default timeout of three missed LACP PDUs. In VoIP environments, the fast rate is recommended to ensure rapid failover and minimize call disruption, while the slow rate can significantly delay failure detection and impact active calls.

LACP Load Balancing Hash Policy

For KVM workloads carrying real-time VoIP traffic, Layer 3+4 hashing is recommended to ensure even traffic distribution, minimize jitter, and avoid congestion on individual links. However, the selected policy must also be supported and configured consistently on the customer switch; mismatched policies can lead to uneven traffic flows and degraded performance.
  • Layer 2 (MAC-based hashing): Uses source and destination MAC addresses to determine the outgoing interface. This provides predictable distribution but may not effectively balance traffic when most flows share the same MAC pairs, which is common in virtualized servers.
  • Layer 3+4 (IP and port-based hashing): Uses source/destination IP addresses and transport-layer ports (TCP/UDP) in the calculation. This method provides more granular distribution across links and is generally preferred for environments running multiple sessions or real-time applications, such as VoIP. It reduces the risk of oversubscription on a single link and helps maintain consistent call quality.

Benefits of IEEE 802.3ad

  • Increased Bandwidth: Aggregates the capacity of multiple links.
  • Redundancy: Ensures continuous operation even if one link fails.
  • Interoperability: Adheres to a standard, allowing compatibility across devices from different vendors.
  • Cost Efficiency: Utilizes existing hardware to achieve higher performance without requiring upgrades.

Considerations

  • Ensure that the customer data switch supports IEEE 802.3ad.
  • Use consistent configurations across all aggregated links to avoid issues.
  • Monitor the aggregation to ensure proper load balancing and fault tolerance.
IEEE 802.3ad is a robust solution for environments requiring high availability and scalable bandwidth, making it a cornerstone of modern network design.
OOBM VLAN Support:
A single VLAN ID can be applied to the Out-of-Band Management interface using the configNetwork script. VLAN trunking is not supported on OOBM interfaces.

Constraints

  • Only the above configurations are validated and supported.
  • VLAN tagging within the guest OS is not supported.