Network Requirements for Cirrus Migrate Cloud Installation

This article is about network requirements during installation of Cirrus Migrate Cloud software. For operational network requirements post-installation, please see Inbound and Outbound Network Requirements for Host Managed by CMC / CPC.

Network Requirements During Installation

Cirrus Data Cloud provides a simple single-line installation command for convenience. This single-line installation process is a sophisticated process that helps find the most appropriate package to install based on many factors in your host environment, including kernel versions, OS versions, network configurations, OS packages installed, etc.

In order to provide the best performance and global availability, this installation command is hosted at our CDN and the software packages are hosted at separate CDNs powered by Amazon S3 and other cloud providers.

As a result, in order to use the one-line installation command, your host has to:
Have a valid DNS that can resolve public internet domain names.
Have valid common root certificates builtin in order to verify the validity of the CDN and Cirrus Data Cloud endpoints. These certificates come with OS installation and is usually not a concern.
Be able to (outbound) communicate with the CDN and software repository via https.

Note: Cirrus Migration Cloud fully supports connections over http/https proxies. See Using HTTP / HTTPS Proxy with Cirrus Migrate Cloud for more information.

To test connectivity prior to installation, see
How to test if my host can connect to the cloud endpoint?

Restricted Environments

If you are on a heavily restricted host environment, where only network connectivities can be established to very specific destination only, you can do the following:

Ensure and can be resolved to the Cirrus Data Cloud IP address. See this article for the current IP address. If you do not have a valid DNS server, you can modify the OS's host file.

Replace the portion of the installation command with our cloud-hosted CDN proxy:

Add a -no-cdn flag to the installation command.


Original installation command obtained from Cirrus Data Cloud UI:
# Linux
curl | bash -s -- -rgc XXXXXXXXXXXXXXX

# Windows
iex "& { $(irm } -rgc XXXXXXXXXXXXXXX"

After confirming and are resolvable and ping-able, execute the following command to start installation:
# Linux
curl | bash -s -- -rgc XXXXXXXXXXXXXXX -no-cdn

# Windows
iex "& { $(irm } -rgc XXXXXXXXXXXXXXX -no-cdn"

Installation Proxy TLS Requirements

Since TLS 1.0 and 1.1 have been deprecated by the Internet Engineering Task Force (IETF) as of March 25, 2021 and they have been disabled in all major operation systems and browsers for security reason, our installation proxy service only supports TLS 1.2.

Although Microsoft has officially disabled TLS 1.0 and TLS 1.1, depending on the Windows PowerShell version and Windows Update settings, your may still encounter SSL/TLS error when attempting to install CMC via the installation proxy such as the following:

irm : The request was aborted: Could not create SSL/TLS secure channel

In order to force PowerShell session to use TLS 1.2, run the following PowerShell command before executing the installation command.

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

Once you verified the above line works, you can have it automatically executed whenever a new PowerShell session is started by running this command in PowerShell:

$ProfileFile = "${PsHome}\Profile.ps1"

if (! (Test-Path $ProfileFile)) {New-Item -Path $ProfileFile -Type file -Force}

'[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12' | Out-File -FilePath $ProfileFile -Encoding ascii -Append

Offline Installation

If the above is not possible for your environment, please contact support for additional information on how to deploy CMC offline.


Updated on: 17/09/2022

Was this article helpful?

Share your feedback


Thank you!