Skip to end of metadata
Go to start of metadata

 

 

In this section:

Overview

The DSC SWe supports the migration method upgrade and rollback and in-container upgrade and rollback as shown in the following table.

SystemUpgrade/Rollback MethodUpgradeRollback
Software on System
(before the upgrade)

Software on System
(after the upgrade)

Software on System
(before the rollback)
Software on System
(after the rollback)
DSC SWe
(on KVM and on VMWare)
Migration
  • 15.0.x
  • 15.1.x
  • 15.2.x
17.x.y17.x.y
  • 15.0.x
  • 15.1.x
  • 15.2.x
DSC SWe
(on KVM, on VMware, and on OpenStack) 
In-Container
  • 16.0.0.R00
  • 16.1.0.R01
  • 16.1.0.R02
17.x.y17.x.y
  • 16.0.0.R00
  • 16.1.0.R01
  • 16.1.0.R02

The DSC SWe (on OpenStack) Upgrade Guide using the migration upgrade and rollback method has not been and will not be published for this platform. 

For detailed information about the software upgrade and rollback, refer to the respective upgrade guide for your system.

Migration Upgrade and Rollback Method

Using this upgrade method, new VMs are created (as required), the data is migrated from the old VMs to the new VMs, and the old VMs are deleted.

Process for the Migration Upgrade Method

Process for this upgrade method includes the following steps:

  1. Create the new VMs with the 17.x.y installation medium at the hypervisor (KVM or VMware) installation process [refer to Creating a New DSC SWe VM or Deploying and Creating a DSC SWe VM, respectively].
     
  2. Run the pre-upgrade and upgrade scripts on the new VMs.

  3. Power off and delete the previous (old) VMs.

Process for the Migration Rollback Method

Process for this rollback method includes the following steps:

  1. Execute the rollback command at the system prompt on the new Routing and Management VM.

  2. Power-on and execute the rollback command at the system prompt on each previous (old) VM.   
     
  3. Restore the previous VMs and power-off and delete the new VMs.

In-container Upgrade and Rollback Method

This upgrade and rollback method is not hypervisor-specific and uses partition switching to reuse the existing VM container.

For detailed information, refer to DSC SWe In-container Software Upgrade and DSC SWe In-container Software Rollback.
    

Note

VM container in this document refers to a VM that is separate from the operating system (OS) and DSC software.  

Process for the In-container Upgrade Method

Process for this upgrade method includes the following steps:

  1. Upload the 17.0.0.R00 upgrade package (dsc_swe_17_0_0_nbYYYYmmdd_upgrade.sh) to an existing/running Management and Routing VM.

  2. Execute the upgrade on this VM using the upgrade script that was uploaded to this VM.

Process for the In-container Rollback Method

Process for this rollback method includes the following step:

  1. Roll back to the previous software version using the rollback script.