This document describes the standard, recommended procedure for upgrading to
Before You Begin
- Software upgrades should be performed during off peak hours.
- Before upgrading or staging an upgrade, its recommended to set all Logging to Error level unless advised by Sonus support. For information about logging, see Supported Logging Levels.
You will need current software maintenance to perform the upgrade.
|Read the release notes for the version of Sonus SBC 1000/2000 you are upgrading to and the associated upgrade notes. The upgrade notes (in particular) contain important information that may be relevant to your Sonus SBC 1000/2000 configuration. A newer version of Sonus SBC 1000/2000 may have different requirements than the previous version.|
- Make sure that your environment still complies with the Sonus SBC 1000/2000 requirements and supported platforms.
The End of Support Announcements for Sonus SBC 1000-2000 page also has important information regarding platform support for future versions of Sonus SBC 1000/2000.
- You must Backup your Sonus SBC 1000/2000 data in the unlikely event that you encounter an issue with your Sonus SBC 1000/2000 upgrade and need to 'roll back' by downgrading back.
We recommend you rename the backup filename to indicate the current software version and build number. For example, rename the backup to
Sonus SBC 1000/2000-1.3.0-b80.tar.gz if you are currently running a Sonus SBC 1000/2000 version 1.3.0 build 80.
- In the event of new alarms raised after upgrading the Sonus SBC 1000/2000, ensure you have no outstanding alarms before upgrading the Sonus SBC 1000/2000. To clear alarm(s), follow the instructions outlined in Acting on Displayed Alarms.
- If you have any problems with your production upgrade which you cannot resolve, create an issue at our support site so that we can assist you.