Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
Expand All close
Expand All close
list Table of Contents
file_download PDF
{ "lCode": "en_US", "lName": "English", "folder": "en_US" }
English
 

Upgrading Sites Overview

date_range 27-Jun-18

When you upgrade Contrail Service Orchestration (CSO), the existing sites continue to have the functionality of earlier releases. However, there might be changes in:

  • Device templates

  • Image version of a device

  • Application configurations (For example, SD-WAN policies)

  • Stage-1 and Stage-2 configurations of a device

For CSO to support sites that are created in earlier releases, you must upgrade the existing sites to the new version. For example, in CSO Release 4.0.0 you must upgrade sites that were created in releases earlier than Release 3.3.0.

You can upgrade a single site or upgrade multiple sites simultaneously.

Users with the SP Administrator or Tenant Administrator role can upgrade a site from the Sites page. The Sites page provides information about sites that must be upgraded and sites for which the upgrade is optional. In the Sites page, following two new columns have been added to indicate whether the site upgrade is mandatory or optional:

  • Site Status—Indicates the status of the site. If the site status is Configured or Provisioned, the upgrade is optional. If the site status is UPGRADE-REQUIRED, the site upgrade is mandatory. You cannot upgrade a site if the site status is Created, Provision Failed, and Activation Failed.

  • Site Version—Indicates the release number in which the site was created.

Upgrading sites that were created in Release 3.3.0 and Release 3.3.1 is optional. You must upgrade sites that were created in releases earlier than Release 3.3.0. You can upgrade a cloud hub device that is created by the SP Administrator and is shared with multiple tenants.

If you create a site in a release that is tagged as a Long Term Support (LTS) release, the site remains functional in the subsequent two LTS releases. For example, if you have created a site in Release X.2 (LTS release), upgrading the site in Release (X+1).2 and Release (X+2).2 is optional, while it is mandatory to upgrade the site in Release (X+3).2.

If you have created a site in a non-LTS release, the site remains functional in the successive release only. For example if you have created a site in Release X.0 (non-LTS), upgrading the site in Release X.1 is optional, while it is mandatory to upgrade the site in Release X.2.

Limitations

Site upgrade has the following limitations:

  • During the upgrade, you experience a downtime.

  • You cannot upgrade a site for centralized deployments.

footer-navigation