Adding clusters
You can add a cluster to Unified Manager for DM Series so that you can monitor the cluster. This includes the ability to obtain cluster information such as the health, capacity, performance, and configuration of the cluster so that you can find and resolve any issues that might occur.
- You must have the Application Administrator or Storage Administrator role.
- You must have the following information:
- Host name or cluster-management IP address
The host name is the FQDN or short name that Unified Manager uses to connect to the cluster. The host name must resolve to the cluster-management IP address.
The cluster-management IP address must be the cluster-management LIF of the administrative storage virtual machine (SVM). If you use a node-management LIF, the operation fails.
- The cluster must be running ONTAP version 9.4 or later.
- ONTAP administrator user name and password
This account must have the admin role with Application access set to ontapi, ssh, and http.
- The port number to connect to the cluster using the HTTPS protocol (typically port 443)
NoteYou can add clusters which are behind a NAT/firewall by using theUnified Manager NAT IP address. Any connected Workflow Automation or SnapProtect systems must also be behind the NAT/firewall, and SnapProtect API calls must use the NAT IP address to identify the cluster. - Host name or cluster-management IP address
- You must have adequate space on the Unified Manager server. You are prevented from adding a cluster to the server when greater than 90% of space in the database directory is already consumed.
For a MetroCluster configuration, you must add both the local and remote clusters, and the clusters must be configured correctly.
You can monitor a single cluster by two instances of Unified Manager provided that you have configured a second cluster-management LIF on the cluster so that each instance of Unified Manager connects through a different LIF.
After all the objects for a new cluster are discovered (about 15 minutes), Unified Manager starts to gather historical performance data for the previous 15 days. These statistics are collected using the data continuity collection functionality. This feature provides you with over two weeks of performance information for a cluster immediately after it is added. After the data continuity collection cycle is completed, real-time cluster performance data is collected, by default, every five minutes.