For KVM Hypervisor

Intel Xeon processors (Nehalem micro-architecture or above)

Note: Sonus recommend using Westmere (or newer) processors for better SRTP performance. These processors have the AES-NI instruction set for performing cryptographic operations in hardware.

Note: Make sure NIC has multi-queue support which enhances network performance by allowing RX and TX queues to scale with the number of CPUs on multi-processor systems.

Number of ports allowed:

• 1 Management port
• 1 HA port
• 2 Media ports

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.

Keep Resource Allocation setting marked as 'unlimited' with CPU freq. set to "physical processor CPU speed multiplied by number of vCPUs assigned to VM".

Keep Resource Allocation setting marked as 'unlimited'. Reserve the memory based on the VM capacity requirement.
For capacity and performance related information, see VMware Hypervisor.

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

• • Use Thick provisioning (eager zero)
  • Hard disk size cannot be changed after SBC SWe software is installed

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

• Use only VMXNET3 driver.
• Always use automatic MAC address assignment option while creating vNICs.
• Associate each vNIC to separate vSwitches.
• Use ESXi NIC teaming feature to achieve redundancy at physical NIC level.

• 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