Versions Compared

Old Version 6

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c880e94aad0181077fa2530009, userName='null'}
JIRAIDAUTHSBX-128576
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c880e94aad0181077fa2530009, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c880e94aad0181077fa2530009, userName='null'}

Include Page
_EMS in EMA, CLI, API
_EMS in EMA, CLI, API

Include Page
_Clear_upgrade_directory_warning
_Clear_upgrade_directory_warning


Panel

In this section:

Table of Contents
maxLevel4



Info
iconfalse

Related articles:



This section describes the different methods to upgrade the 

Spacevars
0series4
 application.

When an 

Spacevars
0product
 upgrade is available, the software is posted on the Ribbon Support Portal. Refer to Downloading Software from the Ribbon Support Portal for more information.


Prerequisites

Prior to performing an upgrade on the

Spacevars
0series4
, ensure the following activities are accomplished.

Spacevars
0series4

SBC Core (in general)

  • Before upgrading the ConnexIP OS, firmware, and the 
    Spacevars
    0product
    application, you must first save the configuration in case you encounter any issues during the upgrade.

  • Before upgrading the application, upgrade the SBC firmware to the latest version on both the active and standby SBCs for an HA pair.

Spacevars0product2

SBC SWe

  • Increase the memory to the larger of:

    • the minimum memory required for the release.
      or
    • the memory required for the desired session capacity.
    Info
    titleNote

    The performance/capacity of the 

    Spacevars
    0product2
    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.

     

  • Ensure the
    Spacevars
    0product2
     memory reservation meets the requirements for the current release. Refer to SBC SWe Performance Metrics.
  • Check minimum disk space requirements: 
    Multiexcerpt include
    MultiExcerptNamedisk_space_requirement
    PageWithExcerpt_Disk_Space_Requirement_SWe_Cloud_Upgrades


Info
titleNote

To recover from a mismatch in session estimates in an HA pair, refer to Recovering from Default Indices in 1:1 HA SBC SWe, if applicable.


Info
titleNote

The E1000E network interface type is unsupported in VMware.

Span


Live Software Upgrade (LSWU)

LSWU allows a user to upgrade the

Spacevars
0product
 application software on HA pairs without impacting service (dropping calls). This is mainly recommended for HA SBC systems. You can also perform a LSWU on the 
Spacevars
0product
 EMA and in 
Spacevars
0product
 EMA Platform Mode. Refer to Live Software Upgrade using CLI and System Administration - Software Install-Upgrade for more information.

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

Spacevars
0product
 application in a standalone or HA configuration using EMA Platform Mode. Refer to Upgrading SBC Application using EMA Platform Mode for more information.

Info
titleNote

Once the upgrade is complete, rediscover the SBC from the

Spacevars
0model3
, if present, and edit any attributes that may have been modified post-upgrade. Attributes are listed under the
Spacevars
0model3
page Register an SBC Core Device.

Notes for Performing Upgrade from

Notes for Performing LSWU from Release 11.1.0x

Release

On an

Spacevars
0product
7000 setup setups, the active node takes more time than expected the time for the services to come up after an upgrade to V12.00.00R000 from 11.1.0x. Before performing an upgrade from 11.1.0x, apply the following steps:

  1.  Confirm Confirm that the cnixpmadmin password is not default by running the following command as root on the active and standby nodes:
    Code Block
    [root@SBC]# $ENCRYPTED_STORE_SH cnxipmadmin

    NOTE: 
     Info
    titleNote
    The command must not show the default password "Cnx1PmAdm1n"
  2. If the password is still the default, randomize the password by running the following command as root on the active node:
     Code Block
    [root@SBC]# $CHANGE_DEFAULT_PASSWDS_SH
  3. Check Verify the cnxipmadmin password is updated to a random one on both the active and standby node by running the following commandnodes:
     Code Block
    [root@SBC]# $ENCRYPTED_STORE_SH cnxipmadmin

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 
 Spacevars
0product
 application in a standalone or HA configuration using EMA Platform Mode. Refer to Upgrading SBC Application using EMA Platform Mode for more information.

 Info
titleNote
Once the upgrade is complete, rediscover the SBC from the 
 Spacevars
0model3
, if present, and edit any attributes that may have been modified post-upgrade. Attributes are listed under the 
 Spacevars
0model3
 page Register an SBC Core Device.