The 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 recommends maintaining call rates within the performance limits benchmarked below.
Expand |
---|
Div |
---|
|
Caption |
---|
0 | Table |
---|
1 | Server and VM Details |
---|
|
Configuration | Server Detail | 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 | 4 | 32 | 100 | Pass-Through Mode (Direct I/O) | 10 Gbps | Config-2 | 8 | Pass-Through Mode (Direct I/O) | Config-3 | 20 | SR-IOV | Config-4 | 32 | SR-IOV |
|
|
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 |
---|
0 | Figure |
---|
1 | Benchmarking Setup for SBC SWe Using SR-IOV interfaces |
---|
|
Image Added |
Caption |
---|
0 | Figure |
---|
1 | Benchmarking Setup for SBC SWe Configured in Pass-Through Mode (Direct I/O) |
---|
|
Image Added |
title | Click here to expand VMware Hypervisor Performance Metrics...This section includes benchmarking results using the following configurations with and without DoS. Contact your representative if you are interested in benchmarking data for other call scenarios.
Multiexcerpt include |
---|
MultiExcerptName | VMware Hypervisor Performance Metrics |
---|
|
addpaneltrue | Hypervisor Performance Metrics Expand |
---|
title | Click here to expand KVM Hypervisor Performance Metrics |
|
...
Multiexcerpt include |
---|
MultiExcerptName | KVM Hypervisor Performance Metrics |
---|
|
addpanel | true | PageWithExcerpt | KVM Hypervisor Performance Metrics |
---|
|
The following tables define the amount of VM memory required based on the call capacity expected and the configuration requirements.
Info |
---|
|
The 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 small and large configurations. |
Info |
---|
|
The SBC SWe requires a minimum memory size of 10 GB. |
Info |
---|
|
The |
Note |
---|
In its current release SBC SWe requires a minimum memory reservation of 10 GB. |
Caption |
---|
0 | Table |
---|
1 | Small Configuration |
---|
3 | Small Configuration |
---|
|
Number of Sessions Desired | Memory Size Required |
---|
5,000 | 10 GB | 18,000 | 14 GB | 24,000 | 16 GB | 28,000 | 17 GB |
|
Caption |
---|
0 | Table |
---|
1 | Large Configuration |
---|
3 | Large Configuration |
---|
|
Number of Sessions Desired | Memory Size Required |
---|
12,000 | 18 GB | 22,000 | 20 GB |
|
Caption |
---|
0 | Table |
---|
1 | Maximum 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/SecUDP | 400 | 60000 | 30 | 100 |
400 | 120000 | 60 | 100 |
TCP | 400 | 256000 | 300 | 100 |
TLS | 400 | 256000 | 300 | 100 |
Include Page |
---|
| TCP_Buffer_Size_64KB_Limitation |
---|
| TCP_Buffer_Size_64KB_Limitation |
---|
|
Caption |
---|
0 | Table |
---|
1 | SIP 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 |
|
Use the following procedure to increase RAM size on active (live) systems to meet the desired SBC SWe session capacity.
Step | Action |
---|
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. |
5 | Manually switchover to revert the |
ActiveStandby standby SBCs back to their original states prior to beginning this procedure. |
6 | Follow LSWU steps if you are upgrading to the next release. |