Versions Compared

Key

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

...

 

...

The

...

Spacevars

...

0

...

Back to Table of Contents 

Back to Upgrading SBC Application Software

Back to Upgrading SBC Application Using Platform Manager

product
 application

 

...

revert from version 5.1.0R000 to 5.0.0R000 and previous versions is performed using EMA under the following conditions:

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

...

  • Spacevars
    0product
     versions.
  • 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-5.0 SBC release, an upgrade to another pre-5.0 release is not supported. Upgrading to any other pre-5.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.
  • The Revert procedure applies to

...

  • Spacevars
    0product
     upgrades only (both offline and LSWU); it does not apply to ConnexIP ISO or

...

  • Spacevars
    0product
     software installations.

 

Warning
titleWarning

This procedure is service impacting.

Note

The Revert procedure is not supported on

...

the

Spacevars
0product
Spacevars
0model3
or
Spacevars
0product2
.

 

The following procedure describes the 

Spacevars
0series4
application revert using the EMA:

  1. Launch the EMA.

...

  1. Refer to Logging On to 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 Modified

  2. Verify the versions in Monitoring > Dashboard > System and Software Info.

    Caption
    0Figure
    1New Application and OS Version

    Image Modified

  3. Navigate to Administration > System Administration screen.

    Caption
    0Figure
    1System Administration Screen

    Image Modified

  4. Click Revert Software Version.
    The Revert Software Version screen is shown. This displays the System or Partition for the current version and the older version.

    Caption
    0Figure
    1Revert Software Screen

    Image Modified

  5. Click on Image Modified to start the revert.
  6. A confirmation message appears on the screen. Click Ok to proceed.

    Caption
    0Figure
    1Confirmation of Revert Operation

    Image Modified

    Note

    The Revert Software application simultaneously reverts both the Active (WFDSBC01a) and Standby (WFDSBC01b) server. On continuing with revert, the upgraded server(s) will reboot and come up with earlier release. During this process browser session will be lost and need to re-login.


    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 04.02.03R000 version. You can see the revert status in the Log section.

    Caption
    0Figure
    1Revert Logs

    Image Modified

    Caption
    0Figure
    1Continuing Revert Operation

    Image Modified

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

    Caption
    0Figure
    1Rebooting SBC Platform

    Image Modified

    Note

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

  8. Launch the Platform Manager using the default credentials.

    Note

    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.

  9. Verify the revert software versions in Platform > Software Versions.

    Caption
    0Figure
    1Active Server Revert Status

    Image Modified

    Caption
    0Figure
    1Standby Server Revert Status

    Image Modified

    Note

    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