Page History

Minimum 4 vCPUs required. But

in case where there are only four physical cores available, you must configure the VM with only 3 vCPUs. Any number of vCPUs may be configured depending upon the call capacity requirements

.

3-vCPUs configuration is supported only from SBC 4.2.4 release.

KVM Direct-IO mode is only supported for PKT ports for vCPUs >=4.

Keep Resource Allocation setting marked as 'unlimited'. Reserve the memory based on the VM capacity requirement.
For capacity and performance related information, see VMware Hypervisorcall capacity and configuration requirements. Refer to benchmarking data for supported call capacities with different configuration limits.

Set Hard Disk (virtual) size as 100 GB or more (based on requirements of retaining CDRs, logs, etc. for number of days)

.

Note: Hard disk size cannot be changed after the SBC SWe software is installed.

Set number of virtual NICs as 4 (1-MGMT, 1-HA, 1-PKT0 and 1-PKT1).

• Use

• only Virt-IO driver.

• Associate each vNIC to separate

• Use four different vSwitches for each vNICs onSBC VM. This ensures various traffic to be physically separated on SBC.

  • Assign 1 physical NIC port (1 Gbps) to each vSwitch if physical NIC redundancy is not needed, otherwise assign 2 physical NIC ports (in active-standby mode using NIC team feature) to each vSwitch.

    The same physical NIC port cannot be associated with different vSwitches.

• Use four different virtual networking labels, each with different VLANs or subnets.
• Always run active and standbySBC VMs on different physical servers
• Disable VM logging

• bridges.