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=8a00a02355cd1c2f0155cd26c9b90306, userName='null'}
JIRAIDAUTHSBX-86216
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c7cd0042, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c99d02be, userName='null'}

The procedure to revert the 

Spacevars
0

...

Spacevars
0product

...

series4
application using the EMA is provided below. You can only revert the application for upgraded systems (offline or LSWU). You cannot revert a system to an older version after a server/system is ISO, or after installing the SBC software.

Include Page
Clear_upgrade_directory_warning
Clear_upgrade_directory_warning


Any configurations performed after the upgrade will be lost after the Revert. Once the revert completes, the configuration rolls back to the time stamp in the 'Last Used' field.

Once a revert is performed to a valid pre-6.0 SBC release, an upgrade to another pre-6.0 release is not supported. Upgrading to any other pre-6.0 releases requires the ConnexIP re-ISO installation. Refer to Re-Installing ConnexIP Operating System for SBC 5000 Series or Re-Installing ConnexIP Operating System for SBC 7000 Series for more information on ConnexIP re-ISO installation.

...

Spacevars
0product

...


Note
titleImportant

This procedure is service impacting.


Info
titleNote

The firmware is not reverted back to an earlier version because it is backwards compatible with earlier 

Spacevars
0product

...

versions.

...


Info
icon
Note

This procedure is service impacting.

false
titleNote

...

The Revert procedure is not supported on the

Spacevars
0product
Spacevars
0model3
or
Spacevars
0product2
. If you require reverting these platforms to the previous version, perform an Application installation, and then a Configuration restore.


Info
iconfalse
title

 

...

Note

The images depicted here are only for examples and do not indicate the latest build. Refer to the release notes for correct build versions. 

Procedure

Perform the following procedure to revert the 

Spacevars
0series4
application

...

using the EMA

...

.

  1. Call 
    Spacevars
    0company
     RTS/GPS to request a software upgrade status reset. 

  2. Launch the EMA (from either the active or standby server). Refer to Logging

...

  1. into EMA in Platform Mode for guidance.

Note

You may launch the EMA in either the active or standby server.

Caption
0Figure
1Logging On to EMA Platform

Image Removed

  1. Navigate to Monitoring > Dashboard > System and Software Info to verify the versions.
    (An example screenshot is shown below. Your actual software version may vary).

    Caption
    0Figure
    1New Application and OS Version

    Image Modified


  2. Navigate to Administration > System Administration screen.

    Caption
    0Figure
    1System Administration Screen

    Image Modified


  3. Click Revert Software Version.
    The Revert Software Version screen is

...

  1. displayed displaying the system or partition for the current version and the older version.
    (An example screenshot is shown below. Your actual software version may vary).

    Caption
    0Figure
    1Revert Software Screen

    Image Modified


  2. Click

...

  1. Image Modified to start the revert.

  2. A confirmation message appears on the screen informing you this action will change the boot software version to the previous release, plus warn you that this is a service-impacting action. Click Ok to proceed.

...

  1. Note

...

  1. title

...

Image Removed

...

  1. Caution

    The Revert Software application simultaneously reverts both the Active

...

  1. and Standby

...

  1. server.

...

  1. Continuing the revert will reboot the upgraded server(s)

...

  1. to an earlier release. During this process, the browser session

...

  1. is lost necessitating logging back into the session.


    The Revert Software starts and changes the boot version to earlier version in both the active and standby server. For example, in this case, it is

...

  1. 06.02.

...

  1. 00R000 version. You can see the revert status in the Log section.

    Caption
    0Figure
    1Revert Logs

    Image Modified


    Caption
    0Figure
    1Continuing Revert Operation

    Image Modified


  2. Once you see Rebooting message in the logs, log out from the EMA.

    Caption
    0Figure
    1Rebooting SBC Platform

    Image Modified

...


Info
titleNote

The revert operation takes approximately 15 to 20 minutes to complete.

...

Launch the Platform Manager using the default credentials.


Info
titleNote

...

Beginning with 5.0 release, the Platform Manager is integrated into the EMA and hereafter referred to as EMA Platform Mode. So once it is reverted back to 3.x/4.x release, you may only use Platform Manager tool for further upgrades.

Verify the revert software versions in Platform > Software Versions.

Caption
0Figure
1Active Server Revert Status

Image Removed

Caption
0Figure
1Standby Server Revert Status

Image Removed


Info
titleNote

...

The roles of Active and Standby server may interchange depends upon the server, which is booting first. In this case, WFDSBC01b completed the rebooting first and became active.

Pagebreak