DO NOT SHARE THESE DOCS WITH CUSTOMERS!

This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.

In this section...

Overview

The SBC SWe performance metrics for simultaneous sessions for various call scenarios are summarized in the "Benchmarking Results" section of the following pages. Note that these numbers apply to our recommended CPU and memory configurations, and the results may vary depending on the actual CPUs used. Exceeding these simultaneous sessions metrics may result in poor call performance, including longer call setup times and/or poor voice quality. Ribbon recommends maintaining call rates within the performance limits benchmarked below.

Server and VM Details

Server and VM Details


Configuration

Server Details

VM Details

Max Link
Size

Server Type

CPU Speed 
(GHz)

Processor
Sockets

RAM
(GB)

Hyperthreading

vCPUs 
Allocated

Memory
(GB)

Disk Size
(GB)

Network Interface
Mode


Config-1

HP DL380 Gen10

Gold 6140


2.3

2

256

ACTIVE

32

32

100

Pass-Through Mode
(SR-IOV)

10 Gbps

Config-2

32

Direct I/O

Note

For deployments that require it, you can instantiate the SBC SWe in smaller-sized configurations that use limited memory and vCPU resources. However, the limited resources place some restrictions on capacity and capabilities. Refer to Small SBC SWe Deployment Characteristics and Performance Metrics for Small SBC SWe Configurations for more information.

Benchmarking Setup

The two test beds used to collect benchmarking data are depicted below.


The VM is hosted on a single NUMA node, where the NIC is connected.

Benchmarking Setup for SBC SWe Using SR-IOV interfaces



Benchmarking Setup for SBC SWe Configured in Pass-Through Mode (Direct I/O)


Performance Metrics

This section includes benchmarking results using the following configurations with and without DoS. Contact your Ribbon representative if you are interested in benchmarking data for other call scenarios.

SWe VMware Benchmarking Data

Call Scenario/ConfigurationConfigurationTraffic ProfileCPS/CHTSimultaneous
Sessions 
G729a passthruConfig-2 (32 vCPU)standard_passthrough_profile

450/106

47,700

x-code G729a->G711u

Config-2 (32 vCPU)

standard_transcoding_profile

79/514,029

G729a pass through with TLS/SRTP enabled on ingress leg

config-2 (32 vCPU)standard_passthrough_profile

430/51

21,930

G729a Direct Media

config-2 (32 vCPU)

standard_signaling_profile

1000/40

40,000

SWe KVM Benchmarking Data

Call Scenario/Configuration

Configuration

Traffic Profile

CPS/CHT

Simultaneous
Sessions 

G729a passthru

Config-1 (32 vCPU)

standard_passthrough_profile

550/90

49,500

x-code G729a → G711u

Config-1 (32 vCPU)

standard_transcoding_profile

54/90

4,860

G729a pass through with TLS/SRTP enabled on ingress leg

Config-1 (32 vCPU)

standard_passthrough_profile

550/90

49,500

G729a Direct Media

Config-1 (32 vCPU)

standard_signaling_profile

1000/40

40,000

       

Increasing RAM on Active SBC SWe Systems

Use the following procedure to increase RAM size on active (live) systems to increase SBC SWe session capacity.

Note

The SBC SWe requires a minimum memory reservation of 6 GB.

StepAction
1

Power down the designated standby SBC.

2

Increase the RAM size of the VM system, and then power-on the standby SBC.

3

Perform a manual switchover, and then power-down the previously active SBC. Refer to the following pages for details:

EMA: System - Admin

CLI: Admin - CLI

4

Increase the RAM size of the VM system for the powered-down SBC, and then power it back up.

5Manually switchover to revert the active/standby SBCs back to their original states prior to beginning this procedure.
6Follow LSWU steps if you are upgrading to the next release.