Customer is not able to use Console service

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

Cause

When multiple IP addresses are assigned and service binds to an internal IP then communication will not happen it will fail

 

Environment

Release : 20.2

Component : PERFORMANCE MANAGEMENT INSTALLATIONS/UPGRADES

Resolution

Backup the file consul.service under /etc/systemd/system 

edit

/etc/systemd/system

vi consul.service

modify Exec start line

remove -bind=192.168.250.36

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

Set that to -advertise=

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

systemctl stop consul

Follow the same with Data Aggregator 2 after the upgrade

now the consul members shows Public IP instead of the private

Powered by Wolken Software