Checking consul member states in CA Performance Management (CAPM) Fault Tolerant Data Aggregator systems
search cancel

Checking consul member states in CA Performance Management (CAPM) Fault Tolerant Data Aggregator systems


Article ID: 190207


Updated On:


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


How can the state of the Fault Tolerant Data Aggregator consul proxy be checked?

How to check the status of consul proxy?

How to check the connection status for Fault Tolerant Data Aggregators?


All supported Performance Management installations running Fault Tolerant Data Aggregators


The commands shown below will be found in these default paths:

  1. On DA in /opt/IMDataAggregator/consul/bin
  2. On Proxy host in /opt/CA/daproxy/bin

Both commands referenced below must be run when consul proxy services are running on the host it's run on.

To check the proxy/consul membership and connection states run the 'consul members' command. In release 20.2.8 onwards, we moved to token usage for consul, so you need you need to pass -token <token> on command line. The Token is in the file:


So you would run the command as per the following example (Sample output from a support lab running Fault Tolerant Data Aggregators. This is from the consul proxy host.):

[root@bin]# ./consul members -token 9845e08e-0201-f027-999f-672b015bf4ce

Node                            Address            Status  Type    Build  Protocol  DC

DA1_HostName                 <IPAddress>:8301      alive   server  0.8.3  2         capm

DA2_HostName                 <IPAddress>:8301      alive   server  0.8.3  2         capm

ProxyHost                    <IPAddress>:8301      alive   server  0.8.3  2         capm

To check the state of the consul proxy and determine which DA is active run the following command.

[root@consulProxyHost bin]# ./consul operator raft list-peers -token <Token>


  • If run before all systems are up for proxy services we'll see the following error:
    • [root@consulProxyHost bin]# ./consul operator raft list-peers
      Error getting peers: Failed to retrieve raft configuration: Unexpected response code: 500 (No cluster leader)
  • When run with everything up, one DA Active, one Inactive, the Active DA will be set as the leader and DA2 and proxy host as followers.
  • When run with only consul services running, with both DAs in Maintenance, the proxy host will show as the leader.

Sample support lab output when one DA is Active and the other is Inactive.

[root@consulProxyHost bin]# ./consul operator raft list-peers -token 9845e08e-0201-f027-999f-672b015bf4ce

Node                            ID                 Address            State     Voter  RaftProtocol

lProxyHost                      <IPAddress>:8300  <IPAddress>:8300    follower  true   2

DA1_HostName                    <IPAddress>:8300  <IPAddress>:8300    leader    true   2

DA2_HostName                    <IPAddress>:8300  <IPAddress>:8300    follower  true   2


Additional Information

Also make sure that both TCP and UDP ports are open for ports 8300 and 8301