DX NetOps

How to Delete IM Data Collector?

Tks,

Nicholas Pierri

Hi Nicholas,

There is no direct way to remove the Data Collector. Usually what happens in the Data Collector List page in CA PC admin, the Data Collector has the status Unknown due to wrong DCM_ID environmental variable. This is probably caused by an attempt to remove a former collector or reinstalling the collector. The new DCM_ID will not match with the one in the DA and the Collector will have a status Unknown due to wrong DCM_ID environment variable. If that is the case, then the knowledge article TEC606412 has the solution below:

The proper process to reinstall or move a DC when you want it to resume polling for existing devices is as follows:

1. Obtain the ID of the DC you’d like to replace.  This is shown in the DA admin view for the DCs in the ID column.  Or you can get it from REST with this call: http://<da-name>:8581/rest/dcms  look for the <DcmID> tag
2. Shut down the DC you want to replace.  It is recommended to go to the host and shutting it down using /etc/init.d/dcmd stop. 

The UI control only partially shuts down the DC.

3. Uninstall the DC that you want to replace.
4. On the system where you will install the replacement DC set the environment variable DCM_ID to the string DcmID you collected in step one.

For example:  export DCM_ID=custdemo-dc1.ca.com:b25abfe9-f51b-4a21-b75c-59a23dde5bbf

5. Run the DC installer on the new system, the newly installed DC will take on the identity of the one you’ve replaced
6. After the newly installed DC connects to the DA it will start loading up poll configurations, and begin polling within a few minutes.

IMPORTANT:  You don’t want to ever have two DCs running with the same ID, so you must ensure that the original is uninstalled such that it can’t be inadvertently restarted.

Remove the data collector from its IPDomain and it will no longer be displayed in the performance center GUI. You will have to use the rest api to accomplish this.

Can you expand on this please?

We have a ghost DC in our performance center which is causing discoveries to fail, we have a work around but would rather have it removed and not causing issues.

I would ask support what the proper fix for this would be.

You can go to http://dataaggregator:8581/rest/dcms and write down the ID of the data collector.

Then issue a delete to http://dataaggregator:8581/rest/ipdomainmember/id/ , where id is that of the DC.

e.g. `curl -X DELETE http://dataaggregator:8581/rest/ipdomainmember/id/`

Can someone from CA chime in here and let us known whether this method is supported?

I have uninstalled unwanted data collector and facing error with DELETE REST API Command while deleting Data collector using ID.

GET is working fine which I tracked ID for the unwanted data collector, however, DELETE is giving HTTP SERVER ERROR 500

Issue is resolved now

Hello All,

There is no current supported or documented method of removing or deleting existing Data Collectors.

Also, a Data Collector in an unknown or disconnected state should not be causing discovery problems unless its the only Data Collector linked to the Data Aggregator.

If there is a situation where more than one Data Collector is linked to a Data Aggregator, where one Data Collector is down or not connected, and Discover Profile runs are failing, there is something else going on. That would be something best addressed with a new support issue being opened for investigation.

Thanks,

Michael

Since this post is more than two years old I wanted to know if this is still valid?

Or is there now a supported way to delete DCs?