Data Aggregator fails to start after upgrade from 25.4.1 -> 25.4.8

Products

• Network Observability
• CA Performance Management

Issue/Introduction

After upgrading DX NetOps Data Aggregator (DA) and Proxy from version 25.4.1 to 25.4.8, the `dadaemon` service fails to start.

Running `consul members` returns an empty list or shows nodes pointing to incorrect IP addresses from a different environment (e.g., Production IPs showing up in a Test environment).

Environment

* DX NetOps Performance Management 25.4.8

* Fault Tolerant Data Aggregator setup

* Data Aggregator Proxy

 

Cause

Incorrect system information (IP addresses or hostnames) provided during the upgrade process, or the use of a cloned environment where Consul state still contains metadata from the source environment.

Resolution

1. Verify the IP configuration in the Consul configuration files located in `/opt/CA/daproxy/data` and `/opt/IMDataAggregator/consul/data`.
2. If incorrect IPs are found, update the configuration to match the current environment.
3. Verify the IP configuration in the DA configuration files located in '/opt/IMDataAggregator/config/install/answers.properties and /etc/DA.cfg '.
   
4. Stop the following services on both DAs and the Proxy:

   ```

   systemctl stop dadaemon

   systemctl stop activemq

   systemctl stop consul

   systemctl stop consul-ext

   ```

5. Restart the Consul service on the Proxy first, followed by the DAs:

   ```

   systemctl start consul

   ```

6. Verify the cluster membership:

   ```

   /opt/IMDataAggregator/consul/bin/consul members

   ```