In this section:

Note

When the SBC is deployed in a 1:1 scenario and registered with the RAMP, you must only configure the SWe Configuration Profiles through the RAMP or EMA.


Use the system parameter sweConfigProfileSelection to configure the SBC SWe provisioning limits based on the following profiles:

  • extrasmall
  • small
  • large
  • largeuseracl
  • largemedia

Command Syntax

% set system sweConfigProfileSelection name <extrasmall | large | largemedia | largeuseracl | small>


Command Parameters

Parameter

Description

name

This parameter indicates the name of the configuration provisioning profile to apply.

The profile options are:

  • extrasmall – applicable when the VM RAM is between 6 and 10 GiB
  • large – applicable when the VM RAM is >=18 GiB
  • largemedia – applicable when the VM RAM is >=18 G.  This profile reduces the number of media IPs required, but the provisioning limits and the session capacity are the same as the large profile option. For details regarding the difference in the sessions and the media IPs between the largemedia and large profiles, refer to, Number of IP Addresses per Call Leg Size.
  • largeuseracl – applicable when the VM RAM is >=18 GiB  (supports up to 10,5926 IP ACLs)
  • small (Default) – applicable when the VM RAM is >=10 GiB
Note

When an instance comes up in an environment that has between 6 and 10 GB of memory, the value for sweConfigProfileSelection is automatically set to extrasmall. It is not valid to reconfigure a deployment from one of the larger sizes (small, large, largemedia, or largeuseracl) to the extrasmall size.

For feature provisioning limits of the large, largemedia, largeuseracl and small profiles, refer to SBC Provisioning Limits. 
For feature provisioning limits of the extrasmall profile, refer to Small SBC SWe Deployment Characteristics.

Note
  • The memory values represent actual memory allocated to the VM. When provisioning a VM on KVM, VMware, and OpenStack platforms, the VM allocated memory is less than the provisioned memory (from dashboard/template/flavor) by a factor of 1.024. Therefore, you must increase the provisioned memory appropriately. For example, if the VM provisioned memory is 10GB, the VM is allocated with 9.76GB of memory.
  • If the SBC VM is provisioned with 10 GB memory, the memory available for session handling is very less. You must provision additional memory for the VM to handle more sessions.

Command Example

set system sweConfigProfileSelection name large
 
The following warnings were generated:
'system sweConfigProfileSelection':To Activate the configuration profile system will be rebooted. Operator to confirm that the existing configuration fits into the new profile being assigned to avoid unexpected behavior (Refer to Provisioning Limits section in Documentation). All active calls will be lost during this process. Do you wish to continue?
Proceed? [yes,no]
Note

The preceding warning applies to non-Cloud SBC SWe only.

The SBC does not support downgrading the SBC SWe Config Profile setting. For example, downgrading from large, largemedia, or largeuseracl to small, or small to extrasmall is not supported.

SBC N:1 Deployments

Activation of the SBC SWe Config profile from OAM is supported from SBC 9.0 onwards.

For extra small deployments, start up the SBCs as well as the OAM with <10 GB Memory. The default activated profiles of the SBC SWe config profile based on memory are provided in the following table:

SBC SWe Config Profile Based on Memory

The following table shows the SBC SWe Config profiles based on memory.

RAM on SBC and OAMSWe Config Profile
< 10GBextrasmall
>=10GBsmall

On the SBC, activate the SWe config profile using a manual reboot of all the managed SBCs under an OAM. For extrasmall deployments, all of the nodes in a redundancy group under an OAM node are extrasmall. That is, a separate OAM node is required to manage extrasmall nodes.

The OAM does not validate the H/W(Memory) resources on the SBC while activating a config profile. Therefore, ensure that adequate resources are provided to the SBCs for activating a config profile.

The OAM does not require a reboot for activation of config profile.

If you activate an SBC SWe config profile from the OAM, which requires a higher than available H/W resources on the SBC, it raises the alarm sonusConfigProfileActivationNotification with the corresponding failure reason.

Recovery Steps

Scenario 1: Attempt to downgrade the SBC SWe config profile

An attempt to downgrade the config profile raises the alarm sonusConfigProfileActivationNotification, with the corresponding reason of failure. Reboot the SBC to recover. Upon reboot, the SBC starts up with the unchanged SweConfigProfile, rejecting the downgrade request from the OAM.

Example:

If the initial SweConfigProfileSelection configuration on the SBC and the OAM is large and the operator commits and activates a small SBC SweConfigProfileSelection on the OAM, the SBC raises the failure alarm. When you reboot the SBC, the application starts up with the large configuration and rejects the small configuration as seen from the OAM.

To downgrade the SweConfigProfile from large to small, rebuild the SBC. In such scenarios, the SBC starts up with the small configuration, honoring the configuration from the OAM.

Scenario 2: Error due to requirement of hardware resources

Note

On the OAM, downgrading the SweConfigProfile from large to small is supported for the recovery of the SBC instances.

  1. On the OAM, activate the SweConfigProfile as small. 
  2. Reboot all the SBCs under the OAM. Do not reboot the OAM.

The SBC starts up with the small config profile.