The DCM_ID will always be the "original DC hostname:UUID" even when moved to new hostname/IP.
You can't change the hostname in the DCM_ID, as it will create a new DC item in the DA.
It's a unique key. Thinking back, we probably should've come up with something better than hostname.
Did you confirm that 4 ports for AMQ are connected between the new DC and DA? Maybe just start AMQ and confirm:
netstat -an | grep 616 | grep ESTABL
Should see 61616/61618/61620/61622. If not, then need to open ports from new DC to DA.
Also, the replaced DC should be done also if it's not when bringing up new dcmd process.
Yes, IMDataCollector/apache-karaf-*/etc/com.ca.im.dm.core.collector.cfg
collector-manager-id= should reflect the DCM_ID you used when running installer.
Original Message:
Sent: Jan 13, 2022 04:27 PM
From: Glenn Weavind
Subject: How to safely move all workload from a TADCO Data Collector to a new DC instance
Hmm, perhaps this is more difficult than I had hoped. I'm changing the hostname and IP address for my replacement DC, assuming that the cloned DCM_ID will make it acceptable to DA as a replacement. The DA logs don't seem to show any acceptance, the newly installed DC code sits there not connecting and PC GUI DC list shows no connection.
IIRC there's a file in DC somewhere that shows what DCM_ID the installed code has acquired or picked up, but I can't recall where it is?
The docs imply that changing hostname and IP won't be a problem but it's not working in my hands, so I'm missing something.
Original Message:
Sent: Jan 12, 2022 04:28 PM
From: Jeffrey Pinard
Subject: How to safely move all workload from a TADCO Data Collector to a new DC instance
Remember you can only delete a DC if it's assigned to an active IP Domain. If unassigned, can't use DELETE /rest/ipdomainmember/<DC itemid>.
If unassigned, you could assign to a valid IP domain and then delete via REST. Or you'd have to remove DC itemid from item table in vertica DB and restart DB for DA to see the deletion.
Original Message:
Sent: Jan 12, 2022 03:09 PM
From: Glenn Weavind
Subject: How to safely move all workload from a TADCO Data Collector to a new DC instance
Thanks Jeff. This refreshed my memory. Sadly, however, it all crashed around my ears. I had three unallocated DCs prebuilt, so went to remove them from PM using the Delete REST call (which I've successfully used twice today, and 3 times y'day) =HTTP 500. No obvious reason, checked and rechecked my work, still HTTP 500. Shut down the first TADCO (stop dcmd), installed DC with DCM_ID env var set to clone it - never registered. Eventually after much checking, ripped out new DC code, restarted old TADCO DC, it came back. Tried stopping dadaemon to see if that cleared the DELETE REST call - tool 15min to reappear in PC - way after GET call for all DCs was coming back HTTP 200.
Result: failure, reverted to status quo ante.
Retire hurt to lick wounds.
Original Message:
Sent: Jan 10, 2022 01:23 PM
From: Jeffrey Pinard
Subject: How to safely move all workload from a TADCO Data Collector to a new DC instance
If you are just looking to run the TADco DC on a diff box running a newer OS, you need only get the DCM ID "hostname:UUID" (from DC UI or /rest/dcms in DA). And install the DC on a new RHE release box by doing:
as root: DCM_ID="<dcm id>" ./install.bin
or using sudo: sudo DCM_ID="<dcm id>" ./install.bin
See https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/dx-netops/21-2/Performance-Monitoring-with-DX-Performance-Management/administrating/data-aggregator-administration/update-the-data-collector.html#concept.dita_c4a5cc8a3c8a1b20159db12cb8756d3e00c82077_ReinstalltheDataCollectoronaCleanHost
The key is using the same DCM ID, so when the new DC machine registers, the DA sees it as the older DC by it's DCM ID. Be sure to stop the old DC before bringing the new one up.
Original Message:
Sent: Jan 10, 2022 12:31 PM
From: Glenn Weavind
Subject: How to safely move all workload from a TADCO Data Collector to a new DC instance
Hi: Happy moving polling workload from one DC to another (getting off old RHEL version), but need to check if this is as straightforward for a Tenant Agnostic DC handling polling load for a number of Tenants?