nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cluster is already being moitored

ahmada

Greetings,

We had removed a cluster from OCUM.

Recently we upgraded OCUM to 9.4P1 and trying to re-add the cluster (ONTAP 9.3P4), we get the below error:

Cluster is already being monitored.

any suggestions?

is the below aplicable to our case

https://community.netapp.com/t5/Data-Infrastructure-Management-Software-Discussions/OPM-2-0-and-Multiple-Instances-How-to-remove-Cluster/td-p/109203

Regards,

Ahmad

Find more posts tagged with

Active IQ Unified Manager

Accepted answers

ahmada

It was resolved by following the below KB :-

https://kb.netapp.com/app/answers/answer_view/a_id/1071140/loc/en_US

I had to modify the script to fit my case.

All comments

helge

In my opinion there are 2 things to start with.

The application record entry in ONTAP. If there are too many it will not work.

If this is OK you need to check the database entries in all related tables´if there are entries left of the old record.

ahmada

@helge wrote:
In my opinion there are 2 things to start with.
The application record entry in ONTAP. If there are too many it will not work.
If this is OK you need to check the database entries in all related tables´if there are entries left of the old record.

There are 10 application records, two of whcih are related to OCUM:-

CDC_Cluster2::*> cluster application-record show -fields name

vserver      name

------------ ----------------------

CDC_Cluster2 Advanced_Setup_Clicked

CDC_Cluster2 "app-OnCommand Unified Manager-1b25b4ae-e0bb-4582-8e51-8427c95f8362"

CDC_Cluster2 "app-OnCommand Unified Manager-c65ce198-e6f4-418e-88c8-5dbec977efe2"

is deleting the application records not service affecting ?

I can see old records of the cluster in OCUM, such as aggregate capacity (not up to date).

ahmada

It was resolved by following the below KB :-

https://kb.netapp.com/app/answers/answer_view/a_id/1071140/loc/en_US

I had to modify the script to fit my case.