The upgrade file is installed to an existing/running Management/Routing VM on a KVM, VMWare, OpenStack or vSP2000 hypervisor.

Prerequisites
Workflow
StepActionProcedure
1

Prepare the system.

Prior to the upgrade, the new software load is uploaded from the Ribbon Global Software Center onto a space accessible by the KVM, VMWare, OpenStack or vSP2000 hypervisor.

Before you Begin the DSC SWe - vSP2000 Software Upgrade
2

Run the upgrade script on Management/Routing VM of the hypervisor that contains this file.

Upgrade DSC SWe - vSP2000 Software
3

Complete post-upgrades tasks, if needed.

Upgrade Software on the MA-RMS TDM I/O Cards

Update MIB Files on Trap Receivers


Note

In this documentation, the application software is referred to as DSC SWe - vSP2000 software.

Reference System Configuration

  • The system configuration referenced in this section consists of two host hardware platforms directly connected and running two virtual machines (VMs) each with DSC SWe - vSP2000 software.
  • The DSC SWe - vSP2000 supports up to ten VMs on each host hardware platform.
  • The host hardware platform is equipped with a VM that has routing and management capabilities (referred to as the Routing and Management VM). The host hardware platform may be equipped with additional VMs that only have routing capability (referred to as the Routing VMs). For information about all supported hardware configurations, refer to the Installation Guide. 
  • Service on a properly configured DSC SWe - vSP2000 should not be impacted by the software upgrade process. During this process, the VMs are stopped, are upgraded to the new software, and are restarted in such an order that the traffic is not interrupted on the system.
  • It is assumed that your network is configured with redundancy such as two VMs to accommodate a switchover of traffic from VM to the other, while the software upgrade takes place. 


Note

The VM that is being upgraded is referred to as the standby system and the VM that is managing the additional traffic is referred to as the active system.

All the examples in this document assume a Linux/Unix environment. Alternatively, utilities such as psftp.exe and putty.exe can be used in a Windows environment to SSH.

The screen captures for the system pre-upgrade, upgrade, and rollback between releases are the same with the exception of the version numbers in these screen captures.


Caution

Do not log onto the platform using the shared IP address on the Routing and Management VMs during the upgrade procedures provided in this section. The address is disabled as part of the upgrade process.