SBC must be deployed on dedicated Linux bridges mapped to physical NICs in the KVM host for data interfaces (known as A1, A2, B1 and B2).
Network bandwidth
A minimum of 1 GbE connectivity per data interface (A/B sides) must be provisioned.
Bonding in active-backup mode is recommended for resiliency, but a single port may be used if redundancy is not required.
On servers with 10/25 GbE NICs, allocate sufficient bandwidth per SBC instance to meet these capacity requirements, ensuring a minimum guaranteed throughput per interface.
The actual bandwidth requirement is capacity-dependent, based on the number of sessions, encrypted calls, and media handling requirements.
Latency-sensitive SBC traffic (A1, B1, A2, B2) must not share oversubscribed NICs or bridges.
Abstraction
SBC and EMS VMs must never directly bind to physical NICs, only to host-defined bridges.
Consistency
Always maintain the same interface-to-bridge mapping across HA pairs to avoid mismatch.
Isolation
Each latency-sensitive data interface (A1, A2, B1, B2) should have a dedicated bridge backed by a dedicated physical NIC (or bandwidth-guaranteed VF).
Management
Separate bridges will be required for M1 and M2 to ensure clean HA heartbeat separation. A separate bridge should be created for M2 and M1 will remain on bridge 0.
Given the same physical interface will be shared by M1 and M2, it is necessary to configure a VLAN for each interface.
For example, Bridge0 connects to M1 and maps to eno8303 on VLAN 100, while BridgeM2 connects to M2 and maps to eno8303 on VLAN 110.
