Installation and Upgrade
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.
A full-version installer is available for CSO Release 3.3.1, which can be used for both trial and production environments.
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.
You can upgrade to CSO Release 3.3.1 only from CSO Release 3.3.0 or CSO Release 3.2.1. If your installed version of CSO is not Release 3.3.0 or Release 3.2.1, then you must perform a fresh installation of CSO Release 3.3.1.
If your installed version is CSO Release 3.3.0 or CSO Release 3.2.1, you can use a script (upgrade.sh) to directly upgrade to CSO Release 3.3.1. If the upgrade is unsuccessful, you can roll back to CSO Release 3.3.0 or CSO Release 3.2.1 respectively.
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.1, 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-D473 for the CSO Release 3.3.1.
When you set up a distributed deployment with an NFX250 device, you must use Administration Portal or the CSO API to:
- Upload the software image to CSO.
- Specify this image as the boot image when you configure activation data.
Table 2 displays the supported versions and download links for CSO Release 3.3.1 and associated software components.
Table 2: CSO and Associated Software Components