Skip to main content

Connecting to NetApp

How to connect and troubleshoot NetApp connections

Support Kappa avatar
Written by Support Kappa
Updated over a week ago

Overview

OneIQ Pulse allows NetApp endpoints to be discovered by IP or hostname using an authorized read-only user account.

Discovering NetApp allows monitoring the resources of all the HA nodes, performance and SVMs.

You will need to add certificate to the trusted list if NetApp is being discovered for the first time by clicking "Trust" button.

Viewing discovered NetApp endpoints

Upon successful discovery, a new endpoint tile will appear in the Dashboard screen and display the IP address or FQDN, credentials used and the current endpoint status.

OneIQ Pulse does not display tiles for individual virtual machines or other managed resources. This detailed information is only available in the OneIQ Portal. OneIQ Pulse is designed to collect detailed inventory and performance data for core resources managed by ONTAP (clusters, nodes, virtual machines).

Supported Versions

  • ONTAP- up to 9.12.1

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

Data Collection Requirements

Permissions

Read-only user for ONTAP, which can list all entities and gather their performance data and capacity usage.

Endpoint Lifecycle

Discovering

When the Create button is clicked, OneIQ Pulse will attempt to discover the specified hostname or IP address and check if the Nutanix Prism Central responds. The discovery process typically takes less than 10 minutes. During this time, OneIQ Pulse connects to the Nutanix API and attempts to login and identify the target endpoint.

Detected

If the endpoint is successfully discovered, OneIQ Pulse will

  • Set its status to Detected and

  • 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 minute, but may take longer in larger environments managed by Prism Central.

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


​

Did this answer your question?