Versions Compared

Old Version 3

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=8a00a02355cd1c2f0155cd26cb41059c, userName='null'}
AUTH1REV5REV6REV3REV4REV1REV2
Anchor
BackToTopBackToTop
Noprint
Panel
borderColorgreen
bgColortransparent
borderWidth2
Back to SBC SWe Lite Installation Guide
UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
JIRAIDAUTHCHOR-3017
REV5UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cef30cd0, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c9d6032b, userName='null'}
REV2UserResourceIdentifier{userKey=8a00a0c86062358001607df6f45d0013, userName='null'}


Panel

In this section:

Table of Contents
maxLevel4

 


This section describes

Spacevars
0product
hardware and software requirements and recommendations .for To install and configure
Spacevars
0product
, make sure the Virtual Machine (VM) host meets the following recommended hardware, server platform and software requirements.

 

series3
installations using VMware ESXi.


warning
Warning
iconfalse

The recommended hardware and software settings are intended to ensure optimum 

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

 


Note

 

titleSBC SWe Lite Operations in an ESXi Cluster are Supported, with Restrictions


The SBC SWe Lite supports operations within an ESXi host under the control of a vCenter Server (centralized management utility for VMware) provided the operations and features invoked on the ESXi host by the vCenter Server match those invoked by the ESXi host console when running outside the control of the vCenter Server.

Refer to the following guidelines and restrictions:

  1. Select operations on the ESXi host initiated by the vCenter Server (such as those not available with the ESXi host console when running in standalone mode) may result in a disruption of SBC SWe Lite operations. Examples of popular vCenter Server-initiated operations that are not supported by the SBC SWe Lite include vMotion and Fault Tolerance.
  2. If unsupported vCenter Server-initiated operations result in a disruption of the SBC SWe Lite, a new unprovisioned (blank) and unlicensed SBC SWe Lite may need to instantiated to replace the original SBC SWe Lite instance.  Please contact Ribbon TAC to initiate a licence re-issuance.


License Requirements

You must obtain and apply a valid 

Spacevars
0product3
 license in order to configure and use the 
Spacevars
0product3
. See below:

Server Hardware Requirements

Multiexcerpt
MultiExcerptNameVMware Hardware


Configuration
Warning
titleNOTE TO REVIEWERS

NOTE TO REVIEWERS: ALL CONTENT FROM THIS POINT ON HAS BEEN BORROWED FROM SBC CORE SWE. PLEASE REVIEW ACCORDINGLY.

 

Server Hardware Requirements

The following table lists the server hardware requirements:

Caption
0Table
1Server Hardware Requirements

 

 Configuration
Requirement
Processor2nd Generation Intel Core or Intel Xeon Processor (Sandy bridge or later)
RAMMinimum 16 GBHard DiskMinimum ??? GBNetwork Interface Cards (NICs)???
Ports

Number of ports allowed:

  • ??? Management port
  • ??? HA port
  • ??? Media ports
Host OSWindows Server 2012 R2 StandardHypervisorHyper-V, KVM, ESXi, VMWare ESXiSystem Type64-bit architecture and 64-bit OS
Host OSESXi 5.5 or above
Architecture64-bit Intel processor
RAMEach SBC SWe Lite instance requires from 1 GiB to 2.5 GiB of RAM depending on the configuration
DatastoreHard disk requirements are dependent upon the number of VMs hosted, the size of each VM at full size, and whether snapshots will be enabled.


Warning
The 
Spacevars
0product2
software only runs on platforms using Intel processors.
Warning
iconfalse

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)???For hardware virtualization
Intel VT-d (Directed I/O)???If available
Intel Hyper-Threading??? 
Intel Turbo Boost??? 
CPU power management??? 

 

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

 

Software Requirements - VMware ESXi

The following are the VMware ESXi and

Spacevars
0product2
software requirements:

VMware ESXi Requirements

Customized ESXi images for various server platforms are available on VMware and Hardware platform vendor sites.

  • It ensures that all the required drivers for network and storage controllers are available to run ESXi server.
  • Most of the customized ESXi images comes with customized management software to manage server running ESXi software.
  • Customized ESXi images for HP ProLiant and IBM servers are available at:
vSphere Client

Minimum ESXi hosting requirements are posted by VMware.

VMware ESXi

Caption
0Table
1VMWare ESXi Requirements
SoftwareVersionTested and Qualified VersionFor More Information
vSphere ESXi 5.1 or above
  • VMware 6.0 tested with VM version 11
5.1 or above VMware Knowledge Base
vCenter Server5.1 or above vCenter Server
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 

Spacevars
0series3
unless the PKT interfaces for 
Spacevars
0series3
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:

please visit the VMware Knowledge Base

Refer to VMware Compatibility Guide (external site) for a list of VMware supported Intel processors. 

Refer to ESXi hardware requirements to ensure the VMware supported Intel processors meet ESXi hardware requirements.

Sonus Recommendations for Optimum Performance

Following are recommended VMware ESXi and 

Spacevars
0series3
virtual machine (VM) configurations. 

General ESXi Recommendations

Following are recommended VMware ESXi configurations:


Ribbon Recommendations for SBC SWe Lite

General Recommendations

  • Plan enough resources (RAM, CPU, NIC ports, hard disk, etc.) for all the virtual machines (VMs) to run on the server platform, including resources needed by ESXi itself.
  • Allocate each VM with 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

    devices that you will not be using (floppy drives, 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
0series3
:


Div
classpdf6pttext
Caption
0Table
1
ESXi 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

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

 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 an

Spacevars
0series3
HA pair.

Note

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

VM Configuration Recommendations


SettingMinimum
vCPU1, 2, 4, and 10 supported
RAM

1 GiB (1024 MiB) to support 1 vCPU

1.5 GiB (1536 MiB) to support 2 vCPUs

2.5 GiB (2560 MiB) to support 4 vCPUs

2.5 GiB (2560 MiB) to support 10 vCPUs

vNIC

5

(Up to 3 may be disabled, if only a single vNIC is required for media. Note: One vNIC is mandatory for management)

Virtual Hard Disk5 GiB


 


Additional Information

  • Minimal networking configuration requires the Management Network Interface and at least one Media Interface to be assigned.
  • Each SBC SWeLite VM will use approximately 5 GiB of Virtual Hard Drive space. Drive size is predetermined by the imported image.


Info
iconfalse

Refer to Downloading the SBC SWe Lite Package for On-Premises Deployment for software download instructions.

 

Pagebreak