Beginning with SBC Core release 12.0, the SBC interoperates with the Ribbon Application Management Platform (RAMP), replacing the Insight EMS.
However, the EMA, CLI and API will continue to include EMS-labeled parameters and screens to facilitate SBC migrations from older releases. Accordingly, any references to "EMS" in this documentation apply to the RAMP platform.
Clear the upgrade directory from both servers before reattempting further upgrades using the command rm -fr /var/log/sonus/upgrade/*
under all the following conditions:
In this section:
This section describes the different methods to upgrade the
When an
Prior to performing an upgrade on the
Before upgrading the application, upgrade the SBC firmware to the latest version on both the active and standby SBCs for an HA pair.
Increase the memory to the larger of:
The performance/capacity of the
The amount of disk space used during the upgrade process depends on how the hypervisor internally handles the disk lifecycle for an instance. The following table provides Ribbon's recommendation for extra disk space for different types of nodes/instances.
For proper performance, you must provide the minimum resources shown here.
Node Type | Extra Disk Space* (in GB) |
---|---|
S-SBC | 80 |
M-SBC | 80 |
PSX-M | 360 |
PSX-S | 360 |
PSX-Test | 360 |
EMS_SA | 150 |
To recover from the default indices, refer to Recovering from Default Indices in 1:1 HA SBC SWe, if applicable.
The E1000E network interface type is unsupported in VMware.
LSWU allows a user to upgrade the
The non-LSWU upgrade process requires taking the SBC system offline to perform an application upgrade. This refers to upgrading the
Once the upgrade is complete, rediscover the SBC from the