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

Compare with Current View Page History

Version 1 Current »

The

Unable to show "metadata-from": No such page "_space_variables"
application upgrade from version 3.x/4.x to version 5.x or later is performed using Platform Manager. The ConnexIP Operating system and BIOS firmware is also upgraded along with the
Unable to show "metadata-from": No such page "_space_variables"
 application upgrade.

Warning

 This procedure is service impacting.

Note

The BIOS firmware upgrade is not part of

Unable to show "metadata-from": No such page "_space_variables"
application upgrade in both
Unable to show "metadata-from": No such page "_space_variables"
and
Unable to show "metadata-from": No such page "_space_variables"
platforms. 

 

The following procedure describes the 

Unable to show "metadata-from": No such page "_space_variables"
application upgrade using the Platform Manager (non-LSWU):

  1. Download the
    Unable to show "metadata-from": No such page "_space_variables"
     application package from the Ribbon Support Portal to your local folder on a PC or remote server. Refer to Downloading Software from Salesforce.
  2. Validate the SBC md5 checksum using the checksum calculator. Refer to Validating MD5Sum with 'Checksums Calculator' for guidance.
  3. Launch the Platform Manager.
    The Platform Manager main screen appears.

    Platform Manager Main Screen

  4. Upload the SBC application package to the active and standby SBC servers using the Upload Files tab.

    1. Click Upload Files.

      Opening Upload Files Tab

    2. Click Select.
    3. Select the SBC application package files in the File Upload screen.

      Selecting SBC application package

    4. Click Open. The Files are added in the Upload Queue section.

    5. Click Upload to upload the queued files.

      Uploading SBC package


    6. Once the file upload is completed, the SBC application files are moved to the Files section.

      Completing the upload


  5. Stop the application on the active server using Admin > Stop Application.

    Stopping Active Server

  6. Stopping the application is a service-affecting operation. Confirm the stop operation by entering your user credentials and clicking Stop.

    Confirm Stop Application

  7. The application is stopped on the active server.

    Stopping Application on Active Server

     

  8. Launch the Platform Manager on the standby server.

    Note

    Once the active server (WFDSBC01a) stops, automatically the standby server (WFDSBC01b) becomes active. 

    Platform Manager Main Screen

  9. Stop the application on the standby server using Admin > Stop Application.

    Stopping Standby Server

  10. Stopping the application is a service-affecting operation. Confirm the stop operation by entering your user credentials and clicking Stop.

    Confirm Stop Application

  11. The application is stopped on the standby server.

    Stopping Application on Standby Server

     
  12. From the Platform Manager of the initial active server (WFDSBC01a), navigate to the SW Install > Upgrade SBC Application tab. Select the SBC Application Version to upgrade, and click Next.

    Note

    Select the "off-line" upgrade option for Non-LSWU upgrades. Ignore the messages appearing for Live Software Upgrade (LSWU). These messages will be removed in the subsequent releases. 

    Selecting SBC Version

    Note

    The signature file of the SBC package verifies the integrity of the package contents before proceeding with the SBC installation. 

  13. Confirm the upgrade by providing your user credentials and clicking Upgrade.

    Confirming Upgrade

  14. The upgrade process starts on the active server (WFDSBC01a) and displays the upgrade status on the View Application Upgrade Log screen.

    Continuing SBC Upgrade

    Continuing SBC Upgrade

    Note

    You may lose connectivity to the browser session when the server reboots. 

    Note

    This process takes approximately 45 minutes to complete on a single server. 

    Rebooting SBC Platform

    Note

    BIOS upgrade is not part of the SBC application upgrade in both

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

    Once the upgrade is successful, clear the browser cache prior to accessing the SBC EMA.

  15. Launch the EMA Platform Mode.
    Log on using the default credentials.

    Logging On to EMA Platform

    Note

    Beginning with 5.0 release, the Platform Manager is integrated into the EMA and referred to as EMA Platform Mode. Thus, post 5.0 SBC application installation and upgrades are performed using the EMA. 

  16. Verify the SBC application status on the Administration > System Administration > Platform Management screen.

    Verifying Active SBC Status

    Note

    Once all the SBC process starts running, continue upgrading the standby SBC server. 

  17. Follow step 12 through step 16 to perform the upgrade on the standby server (WFDSBC01b).

  18. Verify the standby SBC application status on the Administration > System Administration > Platform Management screen.

    Verifying Standby SBC Status

  19. Verify the firmware, ConnexIP OS and SBC application versions in Monitoring > Dashboard > System and Software Info.

    System and Software Information for HA pair

  20. Log on to EMA. Navigate to Monitoring > Dashboard > System Status to verify the overall HA system status on the active server.

    Overall HA System Status

     

     

  • No labels