In this section...
The SBC SWe performance metrics for simultaneous sessions 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 may result in poor call performance, including longer call setup times and/or poor voice quality. Ribbon recommends maintaining call rates within the performance limits benchmarked below.
For deployments that require it, you can instantiate the SBC SWe in smaller-sized configurations that use limited memory and vCPU resources. However, the limited resources place some restrictions on capacity and capabilities. Refer to Small SBC SWe Deployment Characteristics and Performance Metrics for Small SBC SWe Configurations for more information.
The two test beds used to collect benchmarking data are depicted below.
The VM is hosted on a single NUMA node, where the NIC is connected.
This section includes benchmarking results using the following configurations with and without DoS. Contact your Ribbon representative if you are interested in benchmarking data for other call scenarios.
Use the following procedure to increase RAM size on active (live) systems to increase SBC SWe session capacity.
The SBC SWe requires a minimum memory reservation of 6 GB.
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. |