From CSO Release 4.0.0 onward, you can install CSO using a new GUI-based installer as well as through the existing CLI installer.
Note
When you install or upgrade CSO by using the CLI, 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.
If you are using the GUI installer, after the installation is successful, click the View all IP addresses and passwords link to view all the IP addresses used by CSO and the passwords for various CSO components.
Ensure that you save the passwords for each CSO component (the cspadmin password, used for the Administration Portal login, is the most important) because these passwords are not displayed again.
Table 2 displays the supported versions and download links for CSO Release 4.0.0 and associated software components. We recommend that you use the CSO Downloader to download and install CSO.
Table 2: CSO and Associated Software Components
A full-version installer is available for CSO Release 4.0.0, which can be used for small, medium, and large deployments. For more information, follow the instructions in the Installation and Upgrade Guide or the README file that is included with the software installation package.
Note The physical servers on which you install CSO must have
Internet access to download the libvirt packages. After the packages are downloaded, you do not need Internet
access for the rest of the CSO installation.
When you set up a distributed deployment with an NFX150 or an NFX250 device, you must use Administration Portal or the CSO API to:
For more information, see https://www.juniper.net/documentation/en_US/release-independent/junos/information-products/pathway-pages/nfx-series/product/ .
Note You can upgrade to CSO Release 4.0.0 from CSO Release 3.3.1 or Release 3.3.0.
You can also upgrade from CSO Release 3.2.1 to Release 4.0.0 by first upgrading to CSO Release 3.3.1.
If your installed version of CSO is not Release 3.3.1, 3.3.0, or 3.2.1, then you must perform a fresh installation of CSO Release 4.0.0.
If your installed version is CSO Release 3.3.1 or Release 3.3.0, you can use a script (upgrade.sh) to directly upgrade to CSO Release 4.0.0. If the upgrade is unsuccessful, you can roll back to CSO Release 3.3.1 or Release 3.3.0, respectively.
For more information, see Upgrading Contrail Service Orchestration Overview in the Installation and Upgrade Guide.
For SD-WAN deployments, CPE devices behind NAT are supported only for Internet links.
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 another Kubernetes minion node. When you bring the minion node back up, the pods do not automatically rebalance across the nodes.
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.
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 Contrail Services Orchestration GUIs in the Deployment Guide.