Configuring VLAN trunking with bonded interfaces

Last Updated : Oct 30, 2026 |
Prolog information
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.
Updated network script now supports assigning multiple VLAN IDs over a bonded interface. Script can also support configuring more than one bond when configuring VLAN trunking.
Consideration
  • When VLAN trunking is used in conjunction with bonded interfaces, the VLAN tag is applied to a bonded interface rather than to an individual physical interface. This represents a change from the original single VLAN configuration method.
  • As part of this procedure, the existing VLAN/bond configuration, if any, will be removed and re-configured automatically by the new network script.
Before you begin
The customer’s data switch ports connected to the ASP server must already be configured with the appropriate VLAN IDs, and IEEE 802.1Q VLAN tagging must be enabled.
Note:
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.