You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

 

Warning

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.

The SBC application revert from this release to the previous version is performed using the SBC EMA with the following prerequisites:

  • The firmware is not reverted back to an earlier version because it is backward compatible with earlier
    Unable to show "metadata-from": No such page "_space_variables"
    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-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.
  • Only the systems upgraded (offline or LSWU) can be reverted. The system can not be reverted to an older version when the server/system is ISOed or the SBC software is installed.
Note

This procedure is service impacting.

Note

The Revert procedure is not supported on the

Unable to show "metadata-from": No such page "_space_variables"
Unable to show "metadata-from": No such page "_space_variables"
or
Unable to show "metadata-from": No such page "_space_variables"
. 

Note

The images depicted here are only for examples and does not indicate the latest build. To know more about the latest build information, refer to Production Releases. 

The following procedure describes the 

Unable to show "metadata-from": No such page "_space_variables"
application revert using the EMA:

  1. Launch the EMA (from either the active or standby server). Refer to Logging On to EMA in Platform Mode for guidance.

     

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

    New Application and OS Version

  3. Navigate to Administration > System Administration screen.

    System Administration Screen

  4. Click Revert Software Version.
    The Revert Software Version screen is 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).

    Revert Software Screen

  5. Click to start the revert.

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

    Caution

    The Revert Software application simultaneously reverts both the Active and Standby server. Continuing the revert will reboot the upgraded server(s) to an earlier release. During this process, the browser session 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 06.02.00R000 version. You can see the revert status in the Log section.

    Revert Logs

    Continuing Revert Operation

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

    Rebooting SBC Platform

Note

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

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.

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.

  • No labels