Avaya SBC requires a minimum of four Virtual Network Interface Cards (vNICs), and depending on the deployment scenario, it use up to six vNICs.
Each vNIC serves a specific role:
M1: Management interface
M2: High Availability (HA) interface
A1: Intranet interface
B1: Internet interface
A2/B2: Optional secondary interfaces for intranet and internet, respectively
In the example configuration below, the SBC will use M1, A1, and B1 interfaces.
For Avaya Solutions Platform 130 Appliance server utilizing 1GB NICs, assign VLANs to ports only on the customer's data switch when possible.
You must configure the network using the following procedure:
Create a new bridge on the hypervisor.
Assign the SBC Virtual Machine (VM) vNIC to the new bridge.
Disable both IPv4 and IPv6 on the bridge interface.
Disabling automatic IP configuration prevents the bridge from attempting to assign an IP address, which could otherwise result in the bridge disabling its port members.
Note:
The R660xs Profile A3/A31 currently does not support dual 10/25GB NICs. Support for these interfaces is targeted for Avaya Solutions Platform 130 Appliance future release. Once available, VLAN tagging within the hypervisor will become more common for these high-speed interfaces. In such cases, VLANs must be explicitly associated with the appropriate bridge.
