The parameter sweConfigProfileSelection is used to configure SBC SWe provisioning limits, and supports three profiles:

  • extrasmall
  • small
  • large

Command Syntax

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

Command Parameters


SWe Config Profile Selection Parameters

Parameter
Description
name

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

The options are:

  • large - the profile that is applicable to the VM RAM >=18 GiB.
  • small - (Default) the profile that is applicable to the VM RAM >=10 GiB.
  • extrasmall - the profile that is applicable when the VM RAM is between 6 and 10 GiB.

Note: When an instance comes up in an environment which 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 or large) to the extrasmall size.

For definitions of large and small provisioning limits, refer to SBC Provisioning Limits. 
For definitions of extrasmall provisioning limits, refer to Small SBC SWe Deployment Characteristics.


Command Example

% set system sweConfigProfileSelection name large
 
The following warnings were generated:
'system sweConfigProfileSelection': To Activate the configuration profile system will be rebooted.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 SWe only.

Downgrading the SWe Config Profile setting is not supported. For example, downgrading from large 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 onward.

For extra small deployments, start up the SBCs as well as OAM with <10GB 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

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 must be 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 of the SBC is required 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 user commits and activates a small SBC SweConfigProfileSelection on the OAM, the SBC raises the failure alarm. Upon reboot of the SBC, the application starts up with the large configuration rejecting 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 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.