Versions Compared

Old Version 12

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-86216pmohan
REV5gnimmagaddaUserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV6avalenteUserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3paramachandraUserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c7cd0042, userName='null'}
REV1dajeru
REV2kconger
UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c99d02be, userName='null'}

The procedure to revert the 

Spacevars
0series4
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
Include Page
_clear_upgrade_directory_warning_clear
Clear_upgrade_directory_warning

The SBC application revert from version 6.2.0R000 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
    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-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
    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
    iconfalse
    titleNote

    This procedure is service impacting. 


    Info
    iconfalse
    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
    titleNote

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

    Procedure

    Perform the following procedure to revert The following procedure describes the 

    Spacevars
    0series4
    application revert 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 On to into EMA in Platform Mode for guidance.

      caption

    3. 0Figure
      1Logging On to EMA Platform

      Image Removed

      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


    4. Navigate to Administration > System Administration screen.

      Caption
      0Figure
      1System Administration Screen


    5. Click Revert Software Version.
      The Revert Software Version screen is displayed . This displays displaying the System system or Partition 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


    6. Click to start the revert.

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

      Captionnote
      0titleFigure
      1Confirmation of Revert Operation

      Image Removed

      Note
      Caution

      The Revert Software application simultaneously reverts both the Active (WFDSBC01a) and Standby (WFDSBC01b) server. On continuing with Continuing the revert , will reboot the upgraded server(s) will reboot and come up with to an earlier release. During this process, the browser session will be lost and need to re-loginis 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 0406.02.03R000 00R000 version. You can see the revert status in the Log section.

      Caption
      0Figure
      1Revert Logs


      Caption
      0Figure
      1Continuing Revert Operation


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

      note
      Caption
      0Figure
      1Rebooting SBC Platform


    Info
    titleNote

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

    Launch the Platform Manager using the default credentials.


    Info
    titleNote
    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.

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