Skip to end of metadata
Go to start of metadata

In this section:

Upgrading Procedures

Upgrading the software on the DSC SWe with a KVM hypervisor from the 15.x.y to the 16.0.0 software version involves the following procedures.

Execute the following steps in the same order as they are presented to upgrade the VM instance.

To copy the previously generated files under /shared/stats and /shared/log off the system

Use secure copy (SCP) or any other preferred file transfer program to copy the files from the /shared/stats and /shared/log directories to a location that is off the system, because the VM slots on which these directories are located are not available after the upgrade or rollback.

Caution

Copy the /shared/stats and /shared/log to storage (secure location) immediately before the software upgrade or rollback.

  1. Establish an SSH session.

  2. Copy the /shared/stats and /shared/log files off the VM that you are logged onto to a secure location.

To upgrade a VM instance

  1. Create new VM instances for each new VM slot with the new software load (see Creating a New VM Instance, To Create a VM Instance Using a VM Configuration File).

    For example, if your system supports existing VMs 1, 2, 3, 4 (VMs 1, 2 configured on the one host and VMs 3, 4 configured on another host), create four new VMs (two per host).

    The new VM instances that you are creating should be assigned unused numbers. For example, if you have VMs 1 to 4 in service, the new VMs should be numbered 5 to 8 and no IP configuration.

  2. Use the hypervisor console to log onto to one of the new VMs (see Accessing the DSC VM Instance).
     
  3. Execute the upgrade script by following the prompts (see To upgrade the software on the VMs).

    The virtual console connection could be severed when a VM reboots during the upgrade. If this occurs, the operator must reinitialize the console connection. The interruption is dependent on the hypervisor and client-side utilities, and is not controlled by the VM.


  4. Validate the configuration after the upgrade (see To verify that the VM software is properly installed).
     

    For the upgrade example provided on this page, three VMs are running 15.1.0 software and three powered off VMs have 15.0.0 software

     

  5. Delete the old VMs (see Removing a VM).

  6. Perform tasks related to the post upgrade process (see Post Upgrade Process).
     

Caution

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

To upgrade the software on the VMs

Click to Read More... 

To verify that the VM software is properly installed

Click to Read More...

Post Upgrade Processes

After the software upgrade is completed, verify the system configuration and data recorded before the upgrade (see Status Verification Before Upgrading the Software).

With consideration to any feature changes, validate the upgraded system. In case of any discrepancies in the system prior to and after upgrade, contact Customer Support before considering a software rollback to the software prior to the upgrade.

Note

A software rollback should only be performed in case severe issues occur shortly after the software upgrade. Any provisioning or configuration changes that have been made after an upgrade are lost during a rollback process.

 

 

  • No labels