Add_workflow_for_techpubs | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Panel | ||||
---|---|---|---|---|
In this section...
|
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 maintaining call rates within the performance limits benchmarked below. Spacevars 0 product2
title | Click here to expand VMware Hypervisor Performance Metrics... |
---|
Div | |||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||
|
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 | ||||
---|---|---|---|---|
| ||||
Caption | ||||
---|---|---|---|---|
| ||||
|
Multiexcerpt include | ||||||
---|---|---|---|---|---|---|
|
This section includes Sonus' benchmarking results using the following configurations with and without DoS. Please contact your Sonus representative if you are interested in benchmarking data for other call scenarios.
Multiexcerpt include | |
---|---|
|
|
|
|
title | Click here to expand Hypervisor Performance with Traffic Profiles |
---|
Multiexcerpt include | ||
---|---|---|
|
|
|
Info |
---|
Test data was obtained from a system using Direct I/O networking and a VMWare hypervisor. |
The following tables define the amount of VM memory required based on the call capacity expected and the configuration requirements.
Info | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
The
|
Info | ||
---|---|---|
| ||
The SBC SWe requires a minimum memory size of 10 GB. |
Caption | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
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)
UDP
400
60000
30
100
400
120000
60
100
TCP
400
256000
300
100
TLS
400
256000
300
100
Caption
0 | Table |
---|---|
1 | SIP 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
Include Page | ||||
---|---|---|---|---|
|
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. |
Pagebreak |
---|