Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c85bb25531015bc4122a4f0003, userName='null'}
REV5UserResourceIdentifier{userKey=8a00a0c857f0393d01583fcf9db40009, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc1e0747, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c86a195e2c016a28f1445d000a, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ced60ca3, userName='null'}
REV2UserResourceIdentifier{userKey=8a00a0c85fd202bb01600fc680190023, userName='null'}

...

bgColorwhite

Related articles:

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

Spacevars
0series6
 hypervisor.

Prerequisites
Workflow
StepActionProcedure
1

Prepare the system.

...

Prior to the upgrade, the new software load is uploaded from the 

Spacevars
0company
 Global

...

Software Center onto a space accessible by the KVM, VMWare, OpenStack or 

Spacevars
0series6
hypervisor.

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

Spacevars
0series6
 hypervisor.

The upgrade process comprises of the following tasks:

...

on Management/Routing VM of the hypervisor that contains this file

...


Info
titleNote

In this documentation, the application software is referred to as

Spacevars
0model1
1bold
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 
    Spacevars
    0model1
     software.

...

  • The 
    Spacevars
    0model1
    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 
    Spacevars
    0model1
     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. 

...


Info
titleNote

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.

It is recommended that you upgrade the software when the traffic levels are low to avoid the risk of triggering network congestion on the active system.

If you have to reset the system date and time, it is recommended that you perform this task during the maintenance window. For more information, refer to the DSC - SP2000 Platform Manager User Guide.

...

.


Note
titleCaution

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.

...