Versions Compared

Old Version 2

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.

...

Section


Children Display


Column
width5%


Column
width95%

Before You Begin

Note
titleRecommendations
  • Software upgrades should be performed during off-peak hours.
  • Before upgrading or staging an upgrade, set all Logging to Error level unless advised otherwise by
    Spacevars
    0company
    support. For information about logging, see Supported Logging Levels.

You will need current software maintenance to perform the upgrade.

Warning
titleSTOP

Read the release notes for the target

Spacevars
0longproduct
software version. The upgrade notes (in particular) contain important information that may be relevant to your 
Spacevars
0longproduct
configuration. A newer version of 
Spacevars
0longproduct
may have different requirements than the previous version.


  1. Make sure your environment still complies with the 

    Spacevars
    0longproduct
    requirements and supported platforms.

    Tip

      The End of Support Announcements for SBC Edge and SWe Lite page has important information regarding platform support for future versions of

    Spacevars
    0longproduct
    .


  2. You must Backup your SBC Edge data in the unlikely event that you encounter an issue with your 

    Spacevars
    0longproduct
    upgrade and need to roll back by downgrading.

    Tip

    Spacevars
    0company
    recommends renaming the backup filename to indicate the current software version and build number . For example, rename the backup to Ribbon SBC 1000/2000-1.3.0-b80.tar.gz if you are currently running a 
    Spacevars
    0longproduct
    version 1.3.0 build 80.


  3. In the event of new alarms raised after upgrading the
    Spacevars
    0longproduct
    , ensure you have no outstanding alarms before upgrading the
    Spacevars
    0longproduct
    . To clear alarm(s), follow the instructions outlined in Acting on Displayed Alarms.
  4. If you encounter any problems with your production upgrade that you cannot resolve in a timely manner, create an issue at our support site so we can assist you.


...

Section


Column
width5%


Column
width95%

Performing the Upgrade

Refer to the appropriate upgrade instructions below for your 

Spacevars
0longproduct
hardware configuration:

Note

Starting in Release 5.0, the ASM uses the Windows Server 2012R2 in order to prepare for Skype for Business SBA.

Prepare to Upgrade the
Spacevars
0longproduct
with a Built-in ASM
Anchor
ASM
ASM

Excerpt Include
Upgrading the SBC Communication Service Version
Upgrading the SBC Communication Service Version
nopaneltrue

You now may proceed with upgrading the

Spacevars
0longproduct
; follow the instructions below.

Upgrade the
Spacevars
0longproduct
Anchor
NoASM
NoASM

  1. From the Ribbon Support Portal - Download Center, download the sw-release-x.y.zfile where x.y.z indicates the version number you are upgrading to:
    • Spacevars
      0series
       Model - the filename uses file extension .img .
    • Spacevars
      0series2
       Model - the filename uses file extension  .img .
  2. Select the desired 
    Spacevars
    0longproduct
    upgrade method:
  3. Ensure the 
    Spacevars
    0longproduct
    has upgraded by verifying the running SBC Edge software version.

Congratulations, you have completed upgrading the

Spacevars
0longproduct
! Proceed to the 327758306 Upgrade Check List.




Section


Column
width5%


Column
width95%

Post-upgrade Check List

  1. You must clear your web browser cache before you login to the
    Spacevars
    0longproduct
    .
  2. Perform a backup of your data on the new 
    Spacevars
    0longproduct
    version. Similarly to the backup preformed in step 3 of the 327758306 Before You Begin section above, we recommend you rename the backup filename to indicate the current software version and build number.
  3. Ensure there are no new alarms generated after the upgrade. In the event of finding new alarms, address what is causing them.


...