In this section:
These instructions include the procedure for upgrading the SBC SWe Lite to the latest software release for the following platforms:
Comply with the following Prerequisites:
Clear all outstanding alarms. To clear alarm(s), refer to Acting on Displayed Alarms.
Contact Ribbon Support for any problems you encounter during the software upgrade that you cannot resolve.
The Azure-based instance of SBC SWe Lite is initially acquired and deployed via Azure Marketplace. For a subsequent upgrade to the SBC SWe Lite, go to the Ribbon Support Portal - Download Center to download the latest compressed software image bundle (.zip ) that contains the upgrade file and upload it onto the SBC SWe Lite. Software upgrades are available for Ribbon customers current on maintenance. (This upgrade offering is established upon initial license purchase from Ribbon.)
Ensure all Prerequisites are complete before attempting an upgrade.
Follow these steps for upgrading to the latest Azure instance of SBC SWe Lite:
Upgrade for Microsoft Azure Deployments
Step | Action |
---|---|
1 | From the Ribbon Support Portal request and download the latest compressed software bundle for Microsoft Hyper-V: (SWeLite-Hyperv-release.X.x.xbuildxxx.zip, where X is the major software release number and additional x'es further detail the software release and build number). For software request and download instructions, refer to the Ribbon Support Portal. For Azure, upgrades are offered for SBC SWe Lite Release 8.0.1 and later. Example filename for an SBC SWe Lite compressed software image bundle that is compatible with an Azure-based instance: SWeLite-Hyperv-release-8.0.1build181.zip NOTE: For detailed information on SBC SWe Lite latest releases, refer to the Release Notes. |
2 | To extract the actual image file within the compressed software bundle file:
An example image file that can be used for an upgrade in Azure is SBCSWeLite-hyperv-release-8.0.1.build181.img.gz. This aforementioned image file is found inside the SWeLite-Hyperv-release-8.0.1build181.zip compressed software bundle file. |
3 | Perform one of the upgrade methods available:
|
USE OF KVM, VMWARE, AND PRE-8.0 HYPER-V IMAGES IN AZURE WILL CAUSE A SOFTWARE UPLOAD FAILURE!
Do not upgrade an Azure-based SBC SWe Lite instance with any image with the "kvm" or "esxi" characters in the filename. Images that include these characters in the filename do not operate in an Azure-based SBC SWe Lite instance and will result in SBC failure. Only use Hyper-V images that are labeled with the 8.0.1 release or later.
NOTE: Hyper-V releases earlier than 8.0.1 (such as 7.0.x) cause faulty SBC operation, and are not supported by Ribbon in an Azure context.
Ensure all Prerequisites are complete before attempting an upgrade.
Follow these steps for upgrading an SBC SWe Lite deployed via KVM, VMware ESXi, or Microsoft Hyper-V.
Upgrade for On Premises Deployments
Step | Action |
---|---|
1 | From the Ribbon Support Portal, request and download the latest compressed software image bundle:(SWeLite-<PlatformName>-release.X.x.x.buildxxx.zip, where <PlatformName> is the on-premises hypervisor type, X is the major software release number, and additional x'es further detail the software release and build number). For software request and download instructions, refer to the Ribbon Support Portal. NOTE: Ensure you download the appropriate file for your hypervisor. Examples of SBC SWe Lite compressed software bundle files for upgrade purposes: For Hyper-V: SWeLite-Hyperv-release.8.0.1build181.zip For VMware: SWeLite-VMware-release.8.0.1build181.zip For KVM: SWeLite-KVM-release.8.0.1build181.zip |
2 | To extract the actual image file within the compressed software bundle file:
|
3 | Perform one of the upgrade methods available:
|
The One-Step Upgrade method automatically upgrades the currently inactive partition, makes it active, and boots the SBC from the newly upgraded partition in a single step. Upon completion, the system is 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, click System > Software Upgrade.
Upload Software
Enter an optional Passphrase (refer to Using the Custom Passphrase).
Click Backup.
Under Select File, click the Browse button and select the SBC SWe Lite image file you extracted from the downloaded software bundle.
Select File
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, (sample screen displayed below). Once the upgrade is complete, the system automatically reboots.
Sample - Upload Progress Screen
Verify the system is booting from the new partition: check the active partition or vview the software Version.
Ensure the SBC SWe Lite has upgraded by verifying the running software version.
The Upgrading the Inactive Partition method upgrades and activates the new version without rebooting the SBC SWe Lite or interrupting active call services during maintenance hours.
In the left navigation pane, go to System > Software Management > Application Partitions.
Partitions Table
Click Upload Software, located on the left side of the pane.
Under Select File, click Browse and select the SBC SWe Lite image file you extracted from the downloaded software bundle.
Select File
On the partition page, verify the Last Upload Status associated with the inactive partition is listed as Success.
Last Upload Status - Success
To set as the active partition, refer to Setting the Active Partition.
To verify a successful upgrade, verify the running software version.
Step | Action |
---|---|
1 | Clear the web browser cache before logging into the SBC SWe Lite. |
2 | Perform a backup on the new SBC SWe Lite version. Ribbon recommends renaming the backup filename to indicate the current software version and build number. |
3 | Verify no new alarms were generated following the upgrade. In the event of new alarms, refer to Acting on Displayed Alarms. |