Versions Compared

Old Version 2

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=

8a00a0c86e9b2550016ec54396b5000a

8a00a0c880e94aad0181077fa2530009, userName='null'}
JIRAIDAUTHSBX-

110943

126002
REV5UserResourceIdentifier{userKey=

8a00a02355cd1c2f0155cd26cb8305e9

8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV6UserResourceIdentifier{userKey=

8a00a02355cd1c2f0155cd26cb8305e9

8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV3UserResourceIdentifier{userKey=

8a00a02355cd1c2f0155cd26cbfd06fb

8a00a0c86573c09001659db4327e0018, userName='null'}
REV1UserResourceIdentifier{userKey=

8a00a02355cd1c2f0155cd26cbfd06fb

8a00a0c86573c09001659db4327e0018, userName='null'}


Internal_display_only


Include Page
_Clear_upgrade_directory_warning
_Clear_upgrade_directory_warning


Panel

In this section:

Table of Contents
maxLevel4



Info
iconfalse

Related articles:

Include Page_Clear_upgrade_directory_warning_Clear_upgrade_directory_warning Info
titleNote
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 

Spacevars
0series4
(SBC 7000 series and SBC SWe) application 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.


Prerequisities

Prior to performing an upgrade on the

Spacevars
0series4
, ensure the following activies are accomplished.

For 

Spacevars
0series4

 

(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.

For 

Spacevars
0product2

:

  • 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 the 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 users to upgrade the

Spacevars
0product
 application application software on HA pairs without impacting service (dropping calls). This is mainly recommended for HA SBC systems. You can also perform a an LSWU on the 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 EMS/RAMP, if present, and edit any modified attributes that may have been modified post-upgrade. Attributes are listed under the EMS page at:

If the SBC is configured and registered in RAMP, the connection may be lost after the first server upgrade. RAMP may take time to show the SBC as Registered again until both servers are completely upgraded.



Notes for Performing Upgrade from 11.1.0x Release

On a

Spacevars
0product
7000 setup, the active node takes more 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:

pagebreak
  1.  Confirm that the cnixpmadmin password is not default by running the following command as root on the active and standby nodes:
    $ENCRYPTED_STORE_SH cnxipmadmin
    NOTE: The command must not show the default password "Cnx1PmAdm1n"
  2. If the password is still default, randomize the password by running the following command as root on the active node:
    $CHANGE_DEFAULT_PASSWDS_SH
  3. Check the cnxipmadmin password is updated to random on the active and standby node by running the following command:
    $ENCRYPTED_STORE_SH cnxipmadmin