Skip to main content

Connecting to NetApp

Learn how to use OneIQ Pulse to discover NetApp ONTAP clusters, HA nodes and SVMs

Written by Omega Team

Overview

OneIQ Pulse for Datacenter collects configuration, capacity and performance data from NetApp ONTAP. Supported objects include clusters, HA nodes and storage virtual machines (SVMs).

This article explains how to deploy OneIQ Pulse to connect with a NetApp environment.

Prerequisites

  • Outbound Internet connectivity on port 443 (SSL) to OneIQ

  • A read-only ONTAP user that can list all entities and gather their performance data and capacity usage

  • OneIQ Pulse supports Windows Server 2016 or later, and Windows 10 or 11. A dedicated computer is recommended but not required

Verify Supported Versions

  • NetApp ONTAP: up to 9.19.1

Note: An example of a supported ONTAP interface can be seen below:

Verify Networking

  • A network path must exist from OneIQ Pulse to the NetApp ONTAP cluster management address on port 443 (HTTPS). If your environment uses a different port, enter it during discovery.

OneIQ Pulse Windows Services

OneIQ Pulse is designed to run under built-in Windows accounts, which are set automatically during installation:

  • OneIQ Pulse Service runs as Network Service

  • OneIQ Deputy Service runs as Local System

We recommend keeping these default accounts. OneIQ Pulse has not been validated with other service accounts, so changing them after installation may affect how it runs. If your organization requires a specific service account, please contact OneIQ Support to discuss your requirements.

OneIQ Pulse connects to your infrastructure using the credentials you enter for each target platform, so no additional service account is needed for discovery.

Discover NetApp

  1. In the OneIQ portal, go to the Connectors section, click Deploy Connector and select the NetApp platform.

  2. Copy the connection key to the clipboard or save it. Then select Download OneIQ Pulse for Datacenter to download the OneIQ Pulse executable.

  3. Once you've downloaded the OneIQ Pulse for Datacenter binary to a Windows computer in your environment, run the executable.

  4. Paste the Connection key into OneIQ Pulse during setup.

  5. In the Select Discovery Target step, choose NetApp.

  6. Enter the following information:

    • FQDN hostname or IP address of the NetApp ONTAP cluster

    • Port: defaults to 443; update this if your environment uses a non-default port

    • Read-only Username and Password

  7. Click Create to initiate discovery.

  8. Add a certificate to the trusted list if NetApp is being discovered for the first time by clicking Trust.

  9. Upon successful discovery, a new NetApp tile will appear in the Dashboard with the following information:

    • Hostname or IP address

    • Username

    • Status

Repeat the steps above for each NetApp ONTAP cluster.

OneIQ Pulse only displays tiles for discovered NetApp endpoints. Configuration, capacity and performance data for NetApp clusters, HA nodes and SVMs are available in the OneIQ Portal.

Endpoint Lifecycle

Discovering

When the Create button is clicked, OneIQ Pulse attempts to discover the specified hostname or IP address and checks that the NetApp ONTAP cluster responds. The discovery process typically takes less than 10 minutes. During this time, OneIQ Pulse connects to the ONTAP API, logs in and identifies the target endpoint.

Detected

If the endpoint is successfully discovered, OneIQ Pulse will:

  • Set its status to Detected

  • Automatically schedule inventory and performance data collection tasks

Collecting

After a baseline of inventory and performance data is collected, OneIQ Pulse will switch the endpoint status to Collecting and continue gathering:

  • Performance data every 5 minutes

  • Inventory data every 1 hour

Each operation usually takes less than a minute, but may take longer in larger NetApp environments.

Best Practice: Check data collection after 3–4 hours to ensure that all endpoints are still being successfully monitored.

What's next?

Use OneIQ Pulse to discover other supported datacenter platforms and collect network flows to identify dependencies.

Did this answer your question?