Versions Compared

Old Version 11

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 12

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: changed panel type on Table 3 - was "Figure"

Add_workflow_for_techpubs
AUTH2
AUTH1
REV5
REV6
REV3
REV1

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 maintaining call rates within the performance limits benchmarked below.


Expand
titleClick here to expand VMware Hypervisor Performance Metrics...


Multiexcerpt include
MultiExcerptNameVMware Hypervisor Performance Metrics
addpaneltrue
PageWithExcerptVMware Hypervisor Performance Metrics

Expand
titleClick here to expand KVM Hypervisor Performance Metrics...

Multiexcerpt include
MultiExcerptNameKVM Hypervisor Performance Metrics
addpaneltrue
PageWithExcerptKVM Hypervisor Performance 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.

Note

In its current release SBC SWe requires a minimum memory 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
0FigureTable
1Maximum Initial (challenged) REGISTER Rate

Large direct 10 vCPU with 24 GB memory:

 

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:

 

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

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

Pagebreak