Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 

Installation and Upgrade

Note: During the installation or upgrade process, ensure that you save the passwords for each infrastructure component when they are displayed on the console because these passwords are encrypted and are not displayed again.

In addition, during the installation, ensure that you save the Administration Portal password that is displayed on the console. For the upgrade, you must log in using the password configured for the previously installed version of CSO.

Installation Instructions

A full-version installer is available for CSO Release 3.3.0, which can be used for both trial and production environments.

Note: You do not need Internet access from the CSO server to install CSO.

For more information, follow the instructions in the Deployment Guide or the README file that is included with the software installation package.

Upgrade Instructions

Note: You can upgrade to CSO Release 3.3.0 only from CSO Release 3.2.1. If your installed version of CSO is not Release 3.2.1, then you must perform a fresh installation of CSO 3.3.0.

If your installed version is CSO Release 3.2.1, you can use a script ( to directly upgrade to CSO Release 3.3.0. You can roll back to CSO Release 3.2.1, if the upgrade is unsuccessful.

For more information, see Upgrading Contrail Service Orchestration Overview in the Deployment Guide.

Post-Installation and Post-Upgrade Instructions

  • After you successfully install or upgrade CSO, you must do the following:

    • Configure SMTP settings—After you log in for the first time to the CSO GUI, you must configure the SMTP settings for your deployment on the SMTP Settings page (Administration > SMTP).

    • Configure name servers on CPE devices—Use custom properties to provide the name server details when you are adding a tenant.

  • Accessing GUIs—We recommend that you use Google Chrome version 60 or later to access the CSO GUIs. For more information, see Accessing the CSO GUIs.

Installation and Upgrade Limitations

  • For SD-WAN deployments, CPE devices behind NAT are not supported.

  • If the Kubernetes minion node in the central or regional microservices virtual machine (VM) goes down, the pods on the minion node are moved to the Kubernetes master node. When you bring the minion node back up, the pods do not automatically rebalance across the nodes.

  • In CSO Release 3.3.0, the VM on which the virtual route reflector (VRR) is installed supports only one management interface.

  • Before upgrading vSRX by using CSO, execute the request system storage cleanup command on the vSRX by using Junos OS CLI.

Software Installation Requirements for NFX250 Network Services Platform

The NFX250 requires Junos OS Release 15.1X53-D472 for the CSO Release 3.3.0.

When you set up a distributed deployment with an NFX250 device, you must use Administration Portal or the CSO API to:

  1. Upload the software image to CSO.
  2. Specify this image as the boot image when you configure activation data.

For more information, see .

Software Downloads

Table 2 displays the supported versions and download links for CSO Release 3.3.0 and associated software components.​

Table 2: CSO and Associated Software Components


Supported Version

Download Link

Contrail Service Orchestration


Juniper Identity Management Service (JIMS)


Pre-bundled with CSO and also available here:

Contrail Analytics

Pre-bundled with CSO

Contrail Cloud Platform


NFX250 CPE device

Junos OS 15.1X53-D472

SRX Series CPE device

Junos OS 15.1X49-D133


Junos OS 15.1X49-D133

MX Series (hub device)

Modified: 2018-07-29