Adding clusters

You can add a cluster to OnCommand Unified Manager 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.

Before you begin

About this task

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.

Steps

  1. In the left navigation pane, click Configuration > Cluster Data Sources.
  2. From the Cluster Data Sources page, click Add.
  3. In the Add Cluster page, specify the required values, such as the host name or IP address (IPv4 or IPv6) of the cluster, user name, password, protocol for communication, and port number.

    By default, the HTTPS protocol and port 443 are selected.

    You can change the cluster-management IP address from IPv6 to IPv4 or from IPv4 to IPv6. The new IP address is reflected in the cluster grid and the cluster configuration page after the next monitoring cycle is complete.

  4. Click Save.
  5. If HTTPS is selected, perform the following steps:
    1. In the Authorize Host dialog box, click View Certificate to view the certificate information about the cluster.
    2. Click Yes.
      Unified Manager checks the certificate only when the cluster is added initially. Unified Manager does not check the certificate for each API call to ONTAP.
      If the certificate has expired, you cannot add a new cluster. You must first renew the SSL certificate and then add the cluster.

Result

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.

Note: Because the collection of 15 days of performance data is CPU intensive, it is suggested that you stagger the addition of new clusters so that data continuity collection polls are not running on too many clusters at the same time.