This document describes the recommended procedure for upgrading
In this section....
You will need current software maintenance to perform the upgrade.
Upgrading Release 6.1.x to Release 7.0 on KVM:
Installing Release 7.0 on KVM requires VirtIO as the disk bus. If IDE is used, performance decreases and packet loss occurs after 100 calls.
Step | Action | Note |
---|---|---|
1 | Make sure your environment still complies with the Unable to show "metadata-from": No such page "_space_variables" requirements and supported platforms. | The End of Support Announcements for SWe Lite page has important information regarding platform support for future versions of Unable to show "metadata-from": No such page "_space_variables" . |
2 | Backup your Sonus SBC SWe data in the unlikely event that you encounter an issue with your Unable to show "metadata-from": No such page "_space_variables" upgrade and need to roll back. | |
3 | Clear all outstanding alarms. To clear alarm(s), follow the instructions outlined in Acting on Displayed Alarms. | 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. |
Step | Action | Notes |
---|---|---|
1 | From the Sonus SBC Download Center, download the SBCSWeLite-hv-release-x.y.z.buildnnn.img.gz where hv indicates the hypervisor, x.y.z indicates the upgrade version number and nnn indicates the build number. Make note of the location to which you saved the file. Ensure you download the appropriate file for your hypervisor. | Refer to Downloading the SBC SWe Lite Package for details. |
2 | Select the desired
| |
3 | Ensure the Unable to show "metadata-from": No such page "_space_variables" has upgraded by verifying the running software version. |
In the left navigation pane, click System > Software Upgrade.
Backup the configuration file.
Enter an optional Passphrase (see Using the Custom Passphrase).
Under Select File, click the Browse button and select the SBC SWe Lite file you previously saved.
Click Upgrade.
Click OK to upload the new software. Do not close or navigate away from the browser window, or you may receive partial results. Throughout the upload process, the web interface displays update messages to indicate the progression of the upgrade, as shown below. (If you navigate to this view from another browser, it will also display the progress.) Once the upgrade is complete, the system automatically reboots.
A typical upgrade takes about 5 minutes. During the upgrade process, the remaining time estimates in the different steps becomes more accurate as the process progresses.
Upon completion, you will be automatically redirected to the Login screen. Verify that you are booting from the new partition either by checking the active partition, or by Viewing the Software Version.
In the left navigation pane, go to System > Software Management > Application Partitions.
Click the Upload Software link located on the top right hand side of the pane
Under Select File, click the Browse button and select the SBC SWe Lite file you previously saved.
Throughout the upload process, the web interface displays update messages to indicate the progression of the upgrade of the inactive partition, as shown below. (If you navigate to this view from another browser, it will also display the progress.)
Under normal conditions, a typical upgrade takes about 5 minutes. During the upgrade process, the remaining time estimates in the different steps becomes more accurate as the process progresses.
At this stage, the inactive partition is upgraded to the the new software without rebooting the SBC SWe Lite and without interrupting active call services. To set as the active partition, refer to Setting the Active Partition.
Step | Action |
---|---|
1 | Clear your web browser cache before you login to the Unable to show "metadata-from": No such page "_space_variables" . |
2 | Perform a backup of your data on the new Unable to show "metadata-from": No such page "_space_variables" version. Sonus recommends that 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. |