In this section:
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:
- There is a need to revert the upgraded server after a single server upgrade while the peer is still on an older version.
- A revert will be performed by doing a re-ISO.
To recover from the default indices, refer to MOP to Recover from Mismatch in 1:1 SBC SWe HA Session Estimates, if applicable.
This section describes the different methods to upgrade the
When an
Prerequisities
Prior to performing an upgrade on the
For
- Before upgrading the ConnexIP OS, firmware, and the Unable to show "metadata-from": No such page "_space_variables"application, you must first save the configuration in case you encounter any issues during the upgrade.
- This will allow you to restore the system and continue the upgrade.
- Refer to Saving the SBC Configuration and Restoring SBC Configuration.
Before upgrading the application, upgrade the SBC firmware to the latest version on both the active and standby SBCs for an HA pair.
- Refer to the target Release Note for the latest firmware version.
- Upgrade the firmware using Upgrading the BMC and BIOS Firmware procedure.
For
Increase the memory to the larger of:
- the minimum memory required for the release.
or - the memory required for the desired session capacity.
NoteThe performance/capacity of the
Unable to show "metadata-from": No such page "_space_variables"is impacted by the amount of memory assigned to the VM. Review SBC SWe Performance Metrics to see the memory requirements for the current release plus a procedure to upgrade memory, if required. Complete the procedure to upgrade memory prior to performing the upgrade.- the minimum memory required for the release.
- Ensure the Unable to show "metadata-from": No such page "_space_variables"memory reservation meets the requirements for the current release. Refer to SBC SWe Performance Metrics.
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. Extra Disk Space* (in GB)Node Type S-SBC 80 M-SBC 80 PSX-M 360 PSX-S 360 PSX-Test 360 EMS_SA 150
Live Software Upgrade (LSWU)
LSWU allows a user to upgrade the
Non-Live Software Upgrade (Non-LSWU)
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 EMS, if present, and edit any attributes that may have been modified post-upgrade. Attributes are listed under the EMS page Register an SBC Core Node.