Small SBC SWe Deployment Characteristics

For deployments that require it, the SBC SWe can be instantiated in smaller-sized configurations that use limited memory and vCPU resources. Although the basic behavior is similar to a larger-size SBC SWe deployment, the limited resources place some restrictions on capacity and capabilities. These are outlined in the following sections. Despite these restrictions, note that these small deployments support the standard high-availability (HA) functionality and overload controls that larger SBC SWe deployments support, as well as port redundancy. Refer to Performance Metrics for Small SBC SWe Configurations for benchmarking information on small deployments. 

Reduced Memory SBC SWe Deployments 

You can instantiate the SBC SWe in an environment with less than 10 GB of memory (minimum 6 GB) and support basic calls in a manner that is similar to a larger SWe deployment. When a deployment of this size (6 to 10 GB of memory) comes up, it is automatically assigned a SWe config profile (sweConfigProfileSelection) type of "extrasmall." A SWe instance with an extra-small configuration places the following limits on configuration:

Overall access control list (ACL) limits are also limited to 256 with the following distribution:

You can activate all types of SWe traffic profiles in a reduced memory (6 to 10 GB) deployment: default, standard and custom. However, there is a limit of 16 transcoding processes for all types of traffic profiles. For deployments with less than 10 GB of memory, the maximum number of concurrent sessions is 8K, irrespective of the traffic profile. The number of subscribers is limited to 32,000.

If you later increase the memory from less than 10 GB to more than 10 GB, SBC SWe automatically changes the configuration profile from "extrasmall" to "small." You must shut down the VM and restart it for the new configuration profile to take effect. You cannot change an instance's configuration profile to "extrasmall" from either a "small" or "large" profile.

2 vCPU SBC SWe Deployments

You can instantiate the SBC SWe in a VM that contains only 2 vCPUs. By design, to provide overload controls, the SBC SWe derives session capacity and processor capacity estimates based on a configured SWe traffic profile and the available system resources. A 2 vCPU deployment must use the default SWe traffic profile; standard and custom traffic profiles are not supported and cannot be activated. The estimates that result for 2 vCPU deployments, using the default SWe traffic profile, limit the number of concurrent sessions to a maximum of 1000, and the number of calls per second (cps) to 20.