NetApp ONTAP Data Management Software Data Collector
Contributors
Download PDF of this page
This data collector acquires inventory and performance data from storage systems running ONTAP using read-only API calls from an administrator account.
Terminology
Cloud Insights acquires inventory and performance data from the ONTAP data collector. For each asset type acquired, the most common terminology used for the asset is shown. When viewing or troubleshooting this data collector, keep the following terminology in mind:
Vendor/Model Term | Cloud Insights Term |
---|---|
Disk |
Disk |
Raid Group |
Disk Group |
Cluster |
Storage |
Node |
Storage Node |
Aggregate |
Storage Pool |
LUN |
Volume |
Volume |
Internal Volume |
Requirements
The following are requirements to configure and use this data collector:
-
You must have access to an Administrator account used for read-only API calls.
-
Username (with read-only role name to ontapi application to the default Vserver) and password to log into NetApp cluster)
-
Port requirements: 80 or 443
Configuration
Field | Description |
---|---|
NetApp Management IP |
IP address or fully-qualified domain name of the NetApp cluster |
User Name |
User name for NetApp cluster |
Password |
Password for NetApp cluster |
Advanced configuration
Field | Description |
---|---|
Communication Port |
Port used for NetApp API |
Inventory Poll Interval (min) |
Default is 60 minutes. |
Performance Poll Interval (sec) |
Default is 900 seconds. |
Troubleshooting
Some things to try if you encounter problems with this data collector:
Inventory
Problem: | Try this: |
---|---|
Receive 401 HTTP response or 13003 ZAPI error code and ZAPI returns “Insufficient privileges” or “not authorized for this command” |
Check username and password, and user privileges/permissions. |
Cluster version is < 8.1 |
Cluster minimum supported version is 8.1. Upgrade to minimum supported version. |
ZAPI returns "cluster role is not cluster_mgmt LIF" |
AU needs to talk to cluster management IP. Check the IP and change to a different IP if necessary |
Error: “7 Mode filers are not supported” |
This can happen if you use this data collector to discover 7 mode filer. Change IP to point to cdot filer instead. |
ZAPI command fails after retry |
AU has communication problem with the cluster. Check network, port number, and IP address. User should also try to run a command from command line from the AU machine. |
AU failed to connect to ZAPI via HTTP |
Check whether ZAPI port accepts plaintext. If AU tries to send plaintext to an SSL socket, the communication fails. |
Communication fails with SSLException |
AU is attempting to send SSL to a plaintext port on a filer. Check whether the ZAPI port accepts SSL, or use a different port. |
Additional Connection errors: |
Check network, port number, and IP address. User should also try to run a command from command line from the AU machine. |
Performance
Problem: | Try this: |
---|---|
“Failed to collect performance from ZAPI” error |
This is usually due to perf stat not running. Try the following command on each node: |
Additional information may be found from the Support page or in the Data Collector Support Matrix.