Migrated Data Collector does not connect to Data Aggregator
search cancel

Migrated Data Collector does not connect to Data Aggregator


Article ID: 259706


Updated On:


CA Performance Management - Usage and Administration DX NetOps


I am testing in a Lab environment migrating a Data Collector from one server to another using the following link : Update the Data Collector (broadcom.com) but the DC stops after in less than one minute after I issue: service dcmd start. 

Here are the steps from the PM documentation:

1. Stop the data collector on the old DC machine.

# systemctl stop dcmd

2. Take note of the Unique Identifier for the Data Collector from the old DC machine:

# cat /opt/IMDataCollector/apache-karaf-4.3.3/etc/com.ca.im.dm.core.collector.cfg

3. Reinstall the data collector on a clean host (new DC machine).

Reinstall the data collector on a clean host using the same data collector unique identifier (DCM_ID). This allows the new data collector to retrieve the original (old) data collector configuration from the data aggregator when the new data collector process starts.

Set an environment variable with the ID of the data collector by issuing the following command:
# export DCM_ID=<data collector id>

# wget -P /tmp -nv http://DA:8581/dcm/InstData/Linux/VM/install.bin
# cd /tmp
# chmod a+x install.bin
# ./install.bin -i console


Release : 21.2


The activemq service was still running on the retired DC host.

Reviewed the 1-2_DA_IMDataAggregator_2_CA_RE.zip --> opt/IMDataAggregator/broker/apache-activemq-5.15.8/data/activemq.log

2023-02-08 15:01:25,735 | INFO  | Started responder end of duplex bridge [email protected]:new-pmdc-35258-1675866316716-0:1 | org.apache.activemq.broker.TransportConnection | ActiveMQ Transport: tcp:///xx.yy.ww.zz:[email protected]
2023-02-08 15:01:25,736 | WARN  | Failed to add Connection id=dc_broker_aeea7480-2b56-4075-9949-533077f29b16->da_broker-35258-1675866316716-4520:3, clientId=da_manager_dc_broker_aeea7480-2b56-4075-9949-533077f29b16_outbound due to {} | org.apache.activemq.broker.TransportConnection | ActiveMQ Transport: tcp:///xx.yy.ww.zz:[email protected]
javax.jms.InvalidClientIDException: Broker: da_broker - Client: da_manager_dc_broker_aeea7480-2b56-4075-9949-533077f29b16_outbound already connected from tcp://aa.bb.cc.dd:54002

Where aa.bb.cc.dd is the IP address of old/retired DC.


 We have to stop both dcmd and activemq on the old/retired  DC machine.

service dcmd stop

service activemq stop


systemctl stop dcmd

systemctl stop activemq