- OnCommand Performance Manager (OPM) 1.1, 2.0, 2.1, 7.0, 7.1.
- OnCommand Unified Manager (OCUM) 7.3+
OPM registers as an application with ONTAP when the cluster is added as a datasource. Changes in ONTAP behavior for policy groups between releases 8.2 and 8.3 forced a change in OPM 1.1 to prevent detrimental behavior. A restriction in OPM 1.1 was added to prevent the addition of a single cluster as a datasource to more than one OPM 1.1 instance to prevent detrimental behavior.
In very specific scenarios, it might be essential to remove an OPM application record manually from a cluster, to allow the cluster to be moved to a new or different OPM instance. One or more of the following messages might be reported:
You must remove cluster from the instance of OnCommand Performance Manager above before adding it to this instance of OnCommand Performance Manager.
Cluster is currently managed by the following instance of OnCommand Performance Manager. Managing a cluster with multiple instances of the same application will impact the performance of the cluster.
Cluster settings are modified successfully in Unified Manager. But cluster add failed for Performance Manager. Cluster <<CLUSTER_NAME>> is already managed by OnCommand Performance Manager with system id <<UNIQUE_UUID>> at https://<<IP_ADDRESS>>:443.