You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

In this section...

 

Overview

The

Unable to show "metadata-from": No such page "_space_variables"
 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.



VMware Hypervisor Performance Metrics | VMware Hypervisor Performance Metrics

VMware Benchmarking Results

Call Scenario/ConfigurationConfigTraffic ProfileCPS/CHTSimultaneous
Sessions 
G729a passthruConfig-1 (4 vCPU)standard_passthrough_profile50/50025,000

G729a passthru

config-2 (8 vCPU)standard_passthrough_profile50/28341,150

Call Mix (x-code G729a->G711u + G729a passthru)

config-2 (8 vCPU)standard_callmix_profile150/14722,050


KVM Hypervisor Performance Metrics | KVM Hypervisor Performance Metrics

KVM Hypervisor Benchmarking Results

Call Scenario/Configuration

Config

Traffic Profile

CPS/CHT

Simultaneous
Sessions 

G729a passthru

Config-3 (20 vCPU)

standard_passthrough_profile

600/77.5

46,500

x-code G729a->G711u

config-4 (32 vCPU)

standard_transcoding_profile

180/31

5,580

G729a pass through with TLS/SRTP enabled on ingress leg

config-4 (32 vCPU)

standard_passthrough_profile

500/88

44,000

G729a Direct Media

config-4 (32 vCPU)

standard_signaling_profile

1000/60

60,000

 

 

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

The

Unable to show "metadata-from": No such page "_space_variables"
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
Unable to show "metadata-from": No such page "_space_variables"
small and large configurations.

In its current release SBC SWe requires a minimum memory of 10 GB.

Small Configuration

Number of Sessions
Desired

Memory Size
Required

5,000

10 GB

18,000

14 GB
24,00016 GB

28,000

17 GB

Large Configuration

Number of Sessions
Desired

Memory Size
Required

12,000

18 GB

22,000

20 GB
 

Maximum Initial (challenged) REGISTER Rate with Background Load

Maximum Initial (challenged) REGISTER Rate

 

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

SIP Session and Registration Capacity Limits

 

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.