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.

• 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 call capacity and configuration requirements. Refer to benchmarking data SBC SWe Performance Metrics 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)

• • Use Thick provisioning (eager zero)
  • Hard disk size cannot be changed once 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 on

  Spacevars
  0 product

  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.

    Note
    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 standby

  Spacevars
  0 product

  VMs on different physical servers
• Disable VM logging