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

Installation Instructions

A full-version installer is available for Release 3.3. You must use this installer for a production environment. You can also use it to install a trial environment if you want to customize the installation settings.

After copying the installer tar file to CSO server and expanding the file, you provision the VMs, and run a script to create a file of settings for the installation. You then run the installer, which takes approximately an hour to install CSO. Finally, you start the CSO infrastructure services and microservices.

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

If your installed version is CSO Release 3.2.1, you can use a script (upgrade.sh) to directly upgrade to CSO Release 3.3. 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 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

  • Deployments where CSO is behind NAT require spokes and hubs to be able to reach the VRR without NAT.
  • For SD-WAN deployments, CPE behind NAT is not supported.
  • If the Kubernetes minion node in the central or regional microservices 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, the virtual machine (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 the Junos OS Release 15.1X53-D472 for the CSO Release 3.3.

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

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

For more information, refer to https://www.juniper.net/documentation/en_US/release-independent/junos/information-products/pathway-pages/nfx-series/product/ .

Software Downloads

Software Downloads for SRX Series Devices

The CSO software package does not contain the images for the SRX1500, SRX4100, and SRX4200 devices. You can download these images by using the following links:

Modified: 2018-03-31