Installed as a small scale deployment with the DA and DC on the same host
After installing a new DC, it will not connect to the DA
Cam 3.x on linux
Installed as a small scale deployment with the DA and DC on the same host
When you build a small scale deployment, we make some changes to the setup that will prevent you from simply moving the DC to a new host.
One example is the ports will be limited to just 61616 and the activemq will not listen for new DC’s to try to connect.
Here are the steps you will need to convert your small scale deployment to a large scale deployment:
1) Snapshot (using vmware) DA/DC, and backup DR
2) Make sure you have the dradmin and dauser passwords.
3) Save the DCM_ID of the DC.
https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=48474
4) Uninstall DA/DC on same box.
5) Install DA and point to existing DR with same usernames/passwords for dauser/dradmin
6) Install DC on new box with export DCM_ID=hostname:UUID from DC that was on DA/DC box. Yes hostname will not match the new box, it's an ID only. IP/hostname columns will update for new DC during DC registration.
DC will download the same set of devices it was polling when it was on the DA itself.
Move a DC
https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=48474
Reference:
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/performance-management/3-6/back-up-the-data-repository1.html
…
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/performance-management/3-6/uninstall-the-data-aggregator-component.html
…
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/performance-management/3-6/installing/uninstall-ca-performance-management/uninstall-the-data-collectors.html
…