Versions Compared

Old Version 17

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
AUTH1UserResourceIdentifier{userKey=8a00a0c86820e56901685f374974002d, userName='null'}
JIRAIDAUTHNASBX-94084
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cbfd06fb, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cbfd06fb, userName='null'}
REV2UserResourceIdentifier{userKey=8a00a0c8618299760161895020da0004, userName='null'}


Warning
titleWarning

The recommended hardware and software settings are intended to ensure optimum 

Spacevars
0product2
stability and performance. If the recommended settings are not used, the
Spacevars
0product2
system may not behave as expected.



Panel

In this section:

Table of Contents
maxLevel4



Info
iconfalse

Related articles:


 

This section describes

Spacevars
0product2
hardware and software requirements and recommendations.

To install and configure the 

Spacevars
0product2
, make sure the Virtual Machine (VM) host meets the following recommended hardware, server platform and software requirements.

 

WarningThe recommended hardware and software settings are intended to ensure optimum 
Spacevars
0product2
stability and performance

.

If the recommended settings are not used, the

Spacevars

0product2
system may not behave as expected. MultiexcerptMultiExcerptName

SBC SWe for VMware – Server Hardware Requirements

Multiexcerpt
MultiExcerptNameSBC SWe for VMware – Server Hardware Requirements


Warning
titleWarning

The 

Spacevars
0product2
software only runs on platforms using Intel processors. Platforms using AMD processors are not supported.

The following table lists the server hardware requirements:

Caption
0Table
1Server Hardware Requirements
 



 ConfigurationRequirement
Processor

Intel Xeon processors (Nehalem micro-architecture or above) with 6 cores and above (processors should support hyper threading).

Note
Info
titleNote

Ribbon

Sonus

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


Info
note
titleNote

The supported CPU Family

Number

number is 6 and CPU Model

Number

number must be newer than 26. Refer to the Intel Architecture and Processor Identification document for more information.


Info
title
note
Note

ESXi 6.5 and later releases

requires

require approximately 2 physical cores to be set aside for hypervisor functionality.

Number

The number of VMs which can be hosted on a server

needs to

must be planned for accordingly.


 RAMMinimum 24 GB
Hard DiskMinimum 500 GB
Network Interface Cards (NICs)

Minimum 4 NICs, if physical NIC redundancy is not required.

Otherwise, 8 NICs (preferably with SR-IOV capability to support future SWe optimizations).

Info
titleNote
note

Make sure

NIC has

NICs have multi-queue support which enhances network performance by allowing RX and TX queues to scale with the number of CPUs on multi-processor systems.

NoteOnly Intel I350 Ethernet adapter is


Info
titleNote
  • The following NICs are supported for configuring as
VMDirectPath
  • SR-IOV and DirectPath I/O pass-through
device
  • devices. SR-IOV is supported only with 10 Gbps interfaces (x540/82599/x710):

Intel I350, x540, x550, x710 and 82599, Mellanox Connect - 4x, and Mellanox Connect - 5x. 

  • The VMware Enterprise Plus license is required for SR-IOV.


Ports

Number of ports allowed:

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

The 

Spacevars
0product2
software only runs on platforms using Intel processors. Platforms using AMD processors are not supported.



 

BIOS Setting Recommendations

Sonus recommends the following BIOS settings for optimum performance:

Caption
0Table
1Recommended BIOS Settings for Optimum Performance
BIOS ParameterRecommended
Setting		Details
Intel VT-x (Virtualization Technology)EnabledFor hardware virtualization
Intel VT-d (Directed I/O)EnabledIf available
Intel Hyper-ThreadingEnabled 
Intel Turbo BoostEnabled 
CPU power managementMaximum Performance 

Pagebreak

For example, the BIOS settings are shown below for HP DL 380p Gen8 servers. For BIOS settings of other servers, refer to the respective vendor website.

 

Caption
0Table
1BIOS Setting Recommendations for HP DL380p Gen8 Server
BIOS ParameterRecommended
Setting		Default Value
HP Power Profile Maximum PerformanceBalanced Power and Performance
Thermal ConfigurationMaximum CoolingOptimal Cooling
HW PrefetchersDisabledEnabled
Adjacent Sector PrefetcherDisabledEnabled
Processor Power and Utilization MonitoringDisabledEnabled
Memory Pre-Failure NotificationDisabledEnabled
Memory Refresh Rate1x Refresh2x Refresh
Data Direct I/OEnabledDisabled
SR-IOVEnabledDisabled
Intel® VT-dEnabledDisabled
MultiexcerptMultiExcerptName

SBC SWe for VMware – Software Requirements

Multiexcerpt
MultiExcerptNameSBC SWe for VMware – Software Requirements


Warning
titleWarning

Using older versions of ESXi can trigger a VM instance shutdown. To prevent this from occurring, you must upgrade the VMware ESXi -- refer to the End of General Support column on https://lifecycle.vmware.com/#/ for supported versions.


The following are the

VMware ESXi and 

Spacevars
0product2

 software requirements

 requirements for VMware ESXi environments:

VMware ESXi Requirements

Caption
0Table
1VMWare ESXi Requirements


SoftwareVersion*Tested and Qualified VersionFor More Information
vSphere ESXi
5
6.
1
0 or above
  • VMware 6.0 tested with VM version 11
  • VMware 6.5 tested with VM version 13
  • Customized ESXi images for various server platforms are available on VMware and
Hardware
  • hardware platform vendor sites.
    It ensures
      • These ensure that all the required drivers for network and storage controllers are available to run ESXi server.
      • Most of the customized ESXi images
    comes
    (under Download images)
    vSphere Client5.1 or above
     

    		VMware Knowledge Base
    vCenter Server5.1 or above
     

    		vCenter Server


    *    The version must be supported. See the End of General Support column at https://lifecycle.vmware.com/#/ for supported versions. 

    Info
    titleNote

    The VMware Enterprise Plus license is required for SR-IOV.


    Warning

    Virtual network interfaces will not come up using VMware ESXi 5.5 Update 3. For more information, refer to 5.0.x Release Notes.

    Note

    The VMware Standard License will be sufficient for SWe SBC unless the PKT interfaces for SBC SWe needs to be configured in Direct IO Pass-through mode. In that case, the Enterprise Plus version of VMware ESXi software is required.

     Third-Party References:

    Downloading the SBC SWe Software Package

    For more information, refer to Downloading SBC SWe Installation Files from SalesForce Portal.

    Sonus Recommendations for Optimum Performance

    Following are recommended VMware ESXi and

    Spacevars
    0product2
    virtual machine (VM) configurations. 

    General ESXi Recommendations

    Following are recommended VMware ESXi configurations:

    • Plan enough resources (RAM, CPU, NIC ports, hard disk, etc.) for all the virtual machines (VMs) to run on server platform, including resources needed by ESXi itself.
    • Allocate each VM only as much virtual hardware as that VM requires. Provisioning a VM with more resources than it requires can, in some cases, reduce the performance of that VM as well as other virtual machines sharing the same host.
    • Disconnect or disable any physical hardware devices (Floppy devices, Network interfaces, Storage controllers, Optical drives, USB controllers, etc.) under BIOS settings that you will not be using to free up interrupt/CPU resources.

    • Use virtual hardware version 8 and above while creating new VMs (available starting ESXi 5.x). This provides additional capabilities to VMs such as supporting VM with up to 1 TB RAM, up to 32 vCPUs etc.

    AnchorESXi_ParamESXi_ParamESXi Host Configuration Parameters

    Use VMware vSphere client to configure the following ESXi host configuration parameters on the Advanced Settings page (see figure below) before installing the

    Spacevars
    0product2
    :

    Div
    classpdf6pttext
    Caption
    0Table
    1ESXi Advanced Settings

     

    ESXi Parameter

    		ESXi 5.1 SettingsESXi 5.5 SettingsESXi 6.0 Settings

    Recommended

    Default

    Recommended

    Default

    Recommended

    Default

    Cpu.CoschedCrossCall

    0

    1

    0

    1

    0

    1

    Cpu.CreditAgePeriod

    500

    3000

    		1000100010001000

    DataMover.HardwareAcceleratedInit

    0

    1

    0

    1

    0

    1

    DataMover.HardwareAcceleratedMove

    0

    1

    0

    1

    0

    1

    Disk.SchedNumReqOutstanding

    256

    32

    		(error)(error)(error)(error)

    Irq.BestVcpuRouting

    1

    0

    1

    0

    1

    0

    Mem.BalancePeriod

    0

    15

    0

    15

    (error)

    (error)

    Mem.SamplePeriod

    0

    60

    0

    60

    (error)

    (error)

    Mem.ShareScanGHz

    0

    4

    0

    4

    0

    4

    Mem.VMOverheadGrowthLimit

    0

    4294967295

    0

    4294967295

    0

    4294967295

    Misc.TimerMaxHardPeriod

    2000

    100000

    2000

    100000

    2000

    100000

    Misc.TimerMinHardPeriod

    		100

    100

    		(error)(error)(error)(error)

    Net.AllowPT

    1

    0

    1

    0

    1

    0

    Net.MaxNetifRxQueueLen

    500

    100

    500

    100

    500

    100

    Net.MaxNetifTxQueueLen

    1000

    500

    1000

    500

    1000

    500

    Net.NetTxCompletionWorldlet

    0

    1

    		01(error)(error)

    Net.NetTxWordlet

    0

    2

    		1212

    Numa.LTermFairnessInterval

    0

    5

    0

    5

    0

    5

    Numa.MonMigEnable

    0

    1

    0

    1

    0

    1

    Numa.PageMigEnable

    0

    1

    0

    1

    0

    1

    Numa.PreferHT

    1

    0

    1

    0

    1

    0

    Numa.RebalancePeriod

    60000

    2000

    60000

    2000

    60000

    2000

    Numa.SwapInterval

    1

    3

    1

    3

    1

    3

    Numa.SwapLoadEnable

    0

    1

    0

    1

    0

    1

     

     

    Caption
    0Figure
    1ESXi Parameters

    Image Removed

     

    VM Configuration Recommendations

    Caption
    0Table
    1VM Configuration Recommendations

     

     SettingsRecommended Configuration
    vCPU

    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".
    Note

    3 vCPUs configuration is supported only from SBC 4.2.4 release.

    Note

    VMDirectPath mode is only supported for PKT ports for vCPUs >=4.

    Warning

    In Direct I/O, if you want to notified with link detection failure using LinkMonitor, use a server with more than 4 vCPUs.

     vRAM

    Keep Resource Allocation setting marked as 'unlimited'. Reserve the memory based on call capacity and configuration requirements. Refer to SBC SWe Performance Metrics for supported call capacities with different configuration limits.

    Virtual Hard Disk

    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
    vNICs

    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.
    vSwitch settings
    • Use four different vSwitches for each vNICs on
      Spacevars
      0product
      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
      0product
      VMs on different physical servers
    • Disable VM logging
    Note

    Make sure the Processors, ESXi version and VM configuration (vCPUs, vRAMs, Virtual Hard Disk, vNICs, and vSwitch Settings) must be identical for SBC SWe HA pair.

    Note

    Make sure that the BIOS and ESXi settings and recommendations must not be changed once it is applied on the server.

    NoteOn a server with a single 4 cores processor, ESXi 6.5 and above releases are not supported since there is not enough CPU available for launching 3 vCPUs SBC SWe VM after considering overhead required for ESXi
    • -supported Intel processor meets the ESXi hardware requirements.


    Pagebreak