Versions Compared

Old Version 24

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
AUTH1UserResourceIdentifier{userKey=8a00a0c86820e56901685f374974002d, userName='null'}
JIRAIDAUTHSBX-7185899207
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cbbf066d, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cbbf066d, userName='null'}



Panel

In this section...

Table of Contents
maxLevel3

 


Overview

The

Spacevars
0product2
 performance metrics for simultaneous sessions under a full-fledged Denial of Service (DoS) attack 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 in conjunction with a Denial of Service attack may result in poor call performance, including longer call setup times and/or poor voice quality. Sonus recommends
Spacevars
0company
 recommends maintaining call rates within the performance limits benchmarked below.

Server and VM Details

Div
classpdf6pttext


Caption
0Table
1Server and VM Details



Configuration

Server DetailVM Details


Max Link
Size

Server TypeCPU Speed
(GHz)		Processor
sockets		RAM
(GB)		HyperthreadingvCPUs
allocated		Memory
(GB)		Disk Size
(GB)		Network
Interface Mode
Config-1HP DL380 Gen10
Gold 6140		2.
Expand
titleClick here to expand VMware Hypervisor Performance Metrics...
32256ACTIVE432100Pass-Through Mode
 (Direct I/O)		10 Gbps
Config-28Pass-Through Mode
 (Direct I/O)
Config-320SR-IOV
Config-432SR-IOV



Benchmarking Setup

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


Info

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


Caption
0Figure
1Benchmarking Setup for SBC SWe Using SR-IOV interfaces

Image Added



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

 Image Added


Performance Metrics

This section includes benchmarking results using the following configurations with and without DoS. Contact your

Spacevars
0company
 representative if you are interested in benchmarking data for other call scenarios

Multiexcerpt include
MultiExcerptNameVMware Hypervisor Performance Metrics
addpaneltrue
PageWithExcerptVMware Hypervisor Performance Metrics
ExpandtitleClick here to expand KVM Hypervisor Performance Metrics..

.

Multiexcerpt include
MultiExcerptName

KVM

VMware Hypervisor Performance Metrics

addpaneltrue

PageWithExcerpt

KVM

VMware Hypervisor Performance Metrics

Expandtitle

Click here to expand Hypervisor Performance with Traffic Profiles


Multiexcerpt include
MultiExcerptNameKVM Hypervisor Performance

with Traffic Profilesaddpaneltrue

Metrics
PageWithExcerptKVM Hypervisor Performance

with Traffic Profiles
Info

Test data was obtained from a system using Direct I/O networking and a VMWare hypervisor.

 

Metrics


SBC SWe Memory Sizes Based on Capacity Requirements

The following tables define the amount of VM memory required based on the call capacity expected and the configuration requirements.

Info
titleInfo

The

Spacevars
0product2
uses the small configuration when the VM memory is less than 18 GB and the large configuration when the VM memory is 18 GB or greater. See  SBC Provisioning Limits for an explanation of
Spacevars
0product2
small and large configurations.


Info
titleNote

The SBC SWe requires a minimum memory size of 10 GB.


Info
titleNote

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


Caption
0Table
1Small Configuration
3Small Configuration


Number of Sessions
Desired

Memory Size
Required

5,000

10 GB

18,000

14 GB
24,00016 GB

28,000

17 GB



Caption
0Table
1Large Configuration
3Large Configuration


Number of Sessions
Desired

Memory Size
Required

12,000

18 GB

22,000

20 GB


 Maximum Initial (challenged) REGISTER Rate with Background Load

Caption

0Table
1Maximum Initial (challenged) REGISTER Rate

Large direct 10 vCPU with 24 GB memory:

Protocol

Initial SIP 
Registration/Sec

Number of 
Subscribers

Interval of Refresh
REGISTER (Seconds)

SIP Calls/Sec

UDP

400

60000

30

100

400

120000

60

100

TCP

400

256000

300

100

TLS

400

256000

300

100

 

SIP Session and Registration Capacity Limits


Caption
0Table
1SIP Session and Registration Capacity Limits

Large direct 10 vCPU with 24 GB memory:

Protocol

Sessions

SIP Calls/Sec

Call Hold
(seconds)

Interval of Refresh
REGISTER (Seconds)

Subscribers

UDP

18000

150

120

60

120000

18000

150

120

30

60000

TCP

18000

150

120

300

256000

Include Page
TCP_Buffer_Size_64KB_Limitation
TCP_Buffer_Size_64KB_Limitation

Increasing RAM on Active SBC SWe Systems

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

StepAction
1

Power down the designated

Standby

standby SBC.

2

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

Standby

standby SBC.

3

Perform a manual switchover, and then power-down the previously

Active

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
active/
Standby
standby SBCs back to their original states prior to beginning this procedure.
6Follow LSWU steps if you are upgrading to the next release.

Pagebreak