Deploy Cloud Data Sense on prem without internet access

Contributors netapp-tonacki

Complete a few steps to deploy Cloud Data Sense on a host in an on-premises site that doesn’t have internet access. This type of installation is perfect for your secure sites.

Supported data sources

When installed in this manner (sometimes called an "offline" or "dark" site), Data Sense can only scan data from data sources that are also local to the on-premises site. At this time, Data Sense can scan the following local data sources:

  • On-premises ONTAP systems

  • Database schemas

  • Non-NetApp NFS or CIFS file shares

  • Object Storage that uses the Simple Storage Service (S3) protocol

There is no support currently for scanning Cloud Volumes ONTAP, Azure NetApp Files, FSx for ONTAP, OneDrive accounts, or AWS S3 accounts.

Limitations

Most Data Sense features work when it is deployed in a site with no internet access. However, certain features that require internet access are not supported, for example:

  • Managing Microsoft Azure Information Protection (AIP) labels

  • Automated software upgrades from Cloud Manager

    Both the Cloud Manager Connector and Data Sense will require periodic manual upgrades to enable new features. You can see the Data Sense version at the bottom of the Data Sense UI pages. Check the Cloud Manager What’s New to see the new features in each release and for when a software update package is available.

Quick start

Get started quickly by following these steps, or scroll down to the remaining sections for full details.

One Install the Cloud Manager Connector

If you don’t already have a Connector installed at your offline on-premises site, deploy the Connector on a Linux host now.

Two Review Data Sense prerequisites

Ensure that your Linux system meets the host requirements, that it has all required software installed, and that your offline environment meets the required permissions and connectivity.

Three Deploy Data Sense

Download the Cloud Data Sense software from the NetApp Support Site and copy the installer file to the Linux host you plan to use. Then launch the installation wizard and follow the prompts to deploy the Cloud Data Sense instance.

Four Subscribe to the Cloud Data Sense service

The first 1 TB of data that Cloud Data Sense scans in Cloud Manager is free. A BYOL license from NetApp is required to continue scanning data after that point.

Install the Cloud Manager Connector

If you don’t already have a Cloud Manager Connector installed at your offline on-premises site, deploy the Connector on a Linux host in your offline site.

Prepare the Linux host system

Data Sense software must run on a host that meets specific operating system requirements, RAM requirements, software requirements, and so on.

  • Operating system: Red Hat Enterprise Linux or CentOS version 8.0 or 8.1

    • Version 7.8 can be used, but the Linux kernel version must be 4.14 or greater

    • The OS must be capable of installing the Docker Engine (for example, disable the firewalld service if needed)

  • Disk: SSD with 500 GiB available on /, or

    • 100 GiB available on /opt

    • 400 GiB available on /var

  • RAM: 64 GB (swap memory must be disabled on the host)

  • CPU: 16 cores

    Note that you can deploy Data Sense on a system with fewer CPUs and less RAM, but there are limitations when using these systems. See Using a smaller instance type for details.

The following software must be installed on the host before you install Data Sense:

Verify Cloud Manager and Data Sense prerequisites

Review the following prerequisites to make sure that you have a supported configuration before you deploy Cloud Data Sense.

  • Ensure that Cloud Manager has permissions to deploy resources and create security groups for the Cloud Data Sense instance.

  • Ensure that the Cloud Manager Connector can access the Data Sense instance. The security group for the Connector must allow inbound and outbound traffic over port 443 to and from the Data Sense instance.

    This connection enables deployment of the Data Sense instance and enables you to view compliance and governance information.

    Make sure port 8080 is open so you can see the installation progress in Cloud Manager.

  • Ensure that you can keep Cloud Data Sense running. The Cloud Data Sense instance needs to stay on to continuously scan your data.

  • Ensure web browser connectivity to Cloud Data Sense. After Cloud Data Sense is enabled, ensure that users access the Cloud Manager interface from a host that has a connection to the Data Sense instance.

    The Data Sense instance uses a private IP address to ensure that the indexed data isn’t accessible to others. As a result, the web browser that you use to access Cloud Manager must have a connection to that private IP address. That connection can come from a host that’s inside the same network as the Data Sense instance.

Deploy Data Sense

For typical configurations you’ll install the software on a single host system. See those steps here.

For very large configurations where you’ll be scanning petabytes of data, you can include multiple hosts to provide additional processing power. See those steps here.

Single-host installation for typical configurations

Follow these steps when installing Data Sense software on a single on-premises host in an offline environment.

What you’ll need
  • Verify that your Linux system meets the host requirements.

  • Verify that you have installed the two prerequisite software packages (Docker Engine and Python 3).

  • Make sure you have root privileges on the Linux system.

  • Verify that your offline environment meets the required permissions and connectivity.

Steps
  1. On an internet-configured system, download the Cloud Data Sense software from the NetApp Support Site. The file you should select is named DataSense-offline-bundle-<version>.tar.gz.

  2. Copy the installer bundle to the Linux host you plan to use in the dark site.

  3. Unzip the installer bundle on the host machine, for example:

    tar -xzf DataSense-offline-bundle-v1.7.2.tar.gz

    This extracts required software and the actual installation file cc_onprem_installer_<version>.tar.gz.

  4. Launch Cloud Manager and click the Data Sense tab.

  5. Click Activate Data Sense.

    A screenshot of selecting the button to activate Cloud Data Sense.

  6. Click Deploy to start the on-prem deployment wizard.

    A screenshot of selecting the button to deploy Cloud Data Sense on premises.

  7. In the Deploy Data Sense On Premises dialog, copy the provided command and paste it in a text file so you can use it later, and click Close. For example:

    sudo ./install.sh -a 12345 -c 27AG75 -t 2198qq --darksite

  8. Unzip the installer file on the host machine, for example:

    tar -xzf cc_onprem_installer_1.7.2.tar.gz
  9. When prompted by the installer, you can enter the required values in a series of prompts, or you can enter the complete command in the first prompt:

    Enter parameters as prompted: Enter the full command:
    1. Paste the information you copied from step 7:
      sudo ./install.sh -a <account_id> -c <agent_id> -t <token> --darksite

    2. Enter the IP address or host name of the Data Sense host machine so it can be accessed by the Connector instance.

    3. Enter the IP address or host name of the Cloud Manager Connector host machine so it can be accessed by the Data Sense instance.

    4. Enter proxy details as prompted. If your Cloud Manager already uses a proxy, there is no need to enter this information again here since Data Sense will automatically use the proxy used by Cloud Manager.

    Alternatively, you can create the whole command in advance and enter it in the first prompt:
    sudo ./install.sh -a <account_id> -c <agent_id> -t <token> --host <ds_host> --cm-host <cm_host> --proxy-host <proxy_host> --proxy-port <proxy_port> --proxy-scheme <proxy_scheme> --proxy-user <proxy_user> --proxy-password <proxy_password> --darksite

    Variable values:

    • account_id = NetApp Account ID

    • agent_id = Connector ID

    • token = jwt user token

    • ds_host = IP address or host name of the Data Sense Linux system.

    • cm_host = IP address or host name of the Cloud Manager Connector system.

    • proxy_host = IP or host name of the proxy server if the host is behind a proxy server.

    • proxy_port = Port to connect to the proxy server (default 80).

    • proxy_scheme = Connection scheme: https or http (default http).

    • proxy_user = Authenticated user to connect to the proxy server, if basic authentication is required.

    • proxy_password = Password for the user name that you specified.

Result

The Data Sense installer installs packages, registers the installation, and installs Data Sense. Installation can take 10 to 20 minutes.

If there is connectivity over port 8080 between the host machine and the Connector instance, you will see the installation progress in the Data Sense tab in Cloud Manager.

What’s Next

From the Configuration page you can select the local on-prem ONTAP clusters and databases that you want to scan.

Multi-host installation for large configurations

For very large configurations where you’ll be scanning petabytes of data, you can include multiple hosts to provide additional processing power. When using multiple host systems, the primary system is called the Manager node and the additional systems that provide extra processing power are called Scanner nodes.

Follow these steps when installing Data Sense software on multiple on-premises hosts in an offline environment.

What you’ll need
  • Verify that all your Linux systems for the Manager and Scanner nodes meet the host requirements.

  • Verify that you have installed the two prerequisite software packages (Docker Engine and Python 3).

  • Make sure you have root privileges on the Linux systems.

  • Verify that your offline environment meets the required permissions and connectivity.

  • You must have the IP addresses of the scanner node hosts that you plan to use.

  • The following ports and protocols must be enabled on all hosts:

    Port Protocols Description

    2377

    TCP

    Cluster management communications

    7946

    TCP, UDP

    Inter-node communication

    4789

    UDP

    Overlay network traffic

    50

    ESP

    Encrypted IPsec overlay network (ESP) traffic

    111

    TCP, UDP

    NFS Server for sharing files between the hosts (needed from each scanner node to manager node)

    2049

    TCP, UDP

    NFS Server for sharing files between the hosts (needed from each scanner node to manager node)

Steps
  1. Follow steps 1 through 8 from the Single-host installation on the manager node.

  2. As shown in step 9, when prompted by the installer, you can enter the required values in a series of prompts, or you can enter the complete command in the first prompt.

    In addition to the variables available for a single-host installation, a new option -n <node_ip> is used to specify the IP addresses of the scanner nodes. Multiple node IPs are separated by a comma.

    For example, this command adds 3 scanner nodes:
    sudo ./install.sh -a <account_id> -c <agent_id> -t <token> --host <ds_host> --cm-host <cm_host> -n <node_ip1>,<node_ip2>,<node_ip3> --proxy-host <proxy_host> --proxy-port <proxy_port> --proxy-scheme <proxy_scheme> --proxy-user <proxy_user> --proxy-password <proxy_password> --darksite

  3. Before the manager node installation completes, a dialog displays the installation command needed for the scanner nodes. Copy the command and save it in a text file. For example:

    sudo ./node_install.sh -m 10.11.12.13 -t ABCDEF-1-3u69m1-1s35212

  4. On each scanner node host:

    1. Copy the Data Sense installer file (cc_onprem_installer_<version>.tar.gz) to the host machine.

    2. Unzip the installer file.

    3. Paste and execute the command that you copied in step 3.

      When the installation finishes on all scanner nodes and they have been joined to the manager node, the manager node installation finishes as well.

Result

The Cloud Data Sense installer finishes installing packages, and registers the installation. Installation can take 15 to 25 minutes.

What’s Next

From the Configuration page you can select the local on-prem ONTAP clusters and databases that you want to scan.