search cancel

Not able to use Console service for Fault Tolerant Data Aggregators (DA) in CA Performance Management (CAPM)

book

Article ID: 199016

calendar_today

Updated On:

Products

CA Infrastructure Management CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

Customer is not able to use Console service after upgrade

Environment

DX NetOps CAPM Release : 20.2 or later
Component : PERFORMANCE MANAGEMENT INSTALLATIONS/UPGRADES

Cause

When multiple IP addresses are assigned and the service binds to an internal IP, then communication will fail.

Resolution

Backup the file consul.service under then edit it. It should be located under:

/etc/systemd/system/consul.service

modify Exec start line and remove the arg

 -bind=<IP_Address>

For example, if bind address is:

-bind=192.168.250.36

So remove it:

ExecStart=/opt/IMDataAggregator/consul/bin/consul agent –bind=192.168.250.36 –disable-host-node-id –config-dir=/opt/IMDataAggregator/consul/conf

 

And then set that to -advertise=<Primary_Server_IP>. So for example, if the Primary interface on the server has IP address 98.6.16.237, then:

ExecStart=/opt/IMDataAggregator/consul/bin/consul agent –advertise=98.6.16.237 –disable-host-node-id –config-dir=/opt/IMDataAggregator/consul/conf

Then stop and restart the consul service:

systemctl stop consul 

systemctl start consul 

Follow the same with Data Aggregator 2 after the upgrade. The consul members should then display the Public IP instead of the private.