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.
Test data was obtained from a system using Direct I/O networking and a VMWare hypervisor.
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.Note
The SBC SWe requires a minimum memory size of 10 GB.
Small Configuration
Number of Sessions | Memory Size Required |
|---|---|
5,000 | 10 GB |
18,000 | 14 GB |
| 24,000 | 16 GB |
28,000 | 17 GB |
Large Configuration
Number of Sessions | Memory Size Required |
|---|---|
12,000 | 18 GB |
22,000 | 20 GB |
Maximum Initial (challenged) REGISTER Rate with Background Load
Maximum Initial (challenged) REGISTER Rate
Large direct 10 vCPU with 24 GB memory:
| Protocol | Initial SIP | Number of | Interval of Refresh |
|
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
Large direct 10 vCPU with 24 GB memory:
Protocol | Sessions | SIP Calls/Sec | Call Hold | Interval of Refresh | Subscribers |
UDP | 18000 | 150 | 120 | 60 | 120000 |
18000 | 150 | 120 | 30 | 60000 | |
TCP | 18000 | 150 | 120 | 300 | 256000 |
Note
In the current implementation, the “send” and “receive” buffer size for TCP packets is restricted to 64 kilobytes. Due to this limitation, the SBC cannot handle traffic where the product of the TCP packet size (measured in kilobytes) and the processor rate (measured in cycles per second) exceeds 64. For example, if the packet size is 3 kilobytes and the processor rate is 25 cycles per second, the product is 75 - which is greater than the TCP buffer size. If the TCP buffer overflows, the SBC resets the connection. This is particularly important when the packet sizes are large, as in case of packets containing the INFO header that bloats the packet sizes.
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.
| Step | Action |
|---|---|
| 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. |
| 5 | Manually switchover to revert the Active/Standby SBCs back to their original states prior to beginning this procedure. |
| 6 | Follow LSWU steps if you are upgrading to the next release. |
Overview
Content Tools