Installing Cloud Manager on an existing Linux host Edit on GitHub Request doc changes

Contributors netapp-bcammett

The most common way to deploy Cloud Manager is from Cloud Central or from a cloud provider’s marketplace. But you have the option to download and install the Cloud Manager software on an existing Linux host in your network or in the cloud.

You can install Cloud Manager on your own host in GCP, but not in your on-premises network. Cloud Manager must be installed in GCP in order to deploy Cloud Volumes ONTAP in GCP.
Before you begin
  • A Red Hat Enterprise Linux system must be registered with Red Hat Subscription Management. If it is not registered, the system cannot access repositories to update required 3rd party software during Cloud Manager installation.

  • The Cloud Manager installer accesses several URLs during the installation process. You must ensure that outbound internet access is allowed to those endpoints. Refer to Networking requirements for Cloud Manager.

About this task
  • Root privileges are not required to install Cloud Manager.

  • Cloud Manager installs the AWS command line tools (awscli) to enable recovery procedures from NetApp support.

    If you receive a message that installing the awscli failed, you can safely ignore the message. Cloud Manager can operate successfully without the tools.

  • The installer that is available on the NetApp Support Site might be an earlier version. After installation, Cloud Manager automatically updates itself if a new version is available.

  1. Review networking requirements:

  2. Review Cloud Manager host requirements.

  3. Download the software from the NetApp Support Site, and then copy it to the Linux host.

    For help with connecting and copying the file to an EC2 instance in AWS, see AWS Documentation: Connecting to Your Linux Instance Using SSH.

  4. Assign permissions to execute the script.


    chmod +x
  5. Run the installation script:

    ./ [silent] [proxy=ipaddress] [proxyport=port] [proxyuser=user_name] [proxypwd=password]

    silent runs the installation without prompting you for information.

    proxy is required if the Cloud Manager host is behind a proxy server.

    proxyport is the port for the proxy server.

    proxyuser is the user name for the proxy server, if basic authentication is required.

    proxypwd is the password for the user name that you specified.

  6. Unless you specified the silent parameter, type Y to continue the script, and then enter the HTTP and HTTPS ports when prompted.

    If you change the HTTP and HTTPS ports, you must ensure that users can access the Cloud Manager web console from a remote host:

    • Modify the security group to allow inbound connections through the ports.

    • Specify the port when you enter the URL to the Cloud Manager web console.

      Cloud Manager is now installed. At the end of the installation, the Cloud Manager service (occm) restarts twice if you specified a proxy server.

  7. Open a web browser and enter the following URL:


    ipaddress can be localhost, a private IP address, or a public IP address, depending on the configuration of the Cloud Manager host. For example, if Cloud Manager is in the public cloud without a public IP address, you must enter a private IP address from a host that has a connection to the Cloud Manager host.

    port is required if you changed the default HTTP (80) or HTTPS (443) ports. For example, if the HTTPS port was changed to 8443, you would enter https://ipaddress:8443

  8. Sign up at NetApp Cloud Central or log in.

  9. After you log in, set up Cloud Manager:

    1. Specify the Cloud Central account to associate with this Cloud Manager system.

    2. Enter a name for the system.

      A screenshot that shows the set up Cloud Manager screen that enables you to select a Cloud Central account and name the Cloud Manager system.

After you finish

Set up permissions so Cloud Manager can deploy Cloud Volumes ONTAP in your cloud provider: