Re: Call Manager 5.1.3 - Database Replication status - Cluster s
NO, it's not cumultative.
Status 2 Shows that the node is correct Syncronized within the Cluster.In the cluster, that matches for every node.( Every node shows 2 = replication is good )
If there is a 3 on the cluster you can see a 3 everywhere except the host that isn't synchronizing right, this shows a 1 when i remember right .
Here is the RTMT description of this behavoiur:
This displays the state of replication: Thus 0 = Initializing (Will be 0 if server is not defined OR if server is defined but realize template is not done); 1 = Replicates created but their count isn't right; 2 = Replication is good; 3 = Replication is bad in the cluster; 4 = Replication Setup didn't succeed. When the counter shows a value of 3, it means replication is bad in the cluster. It doesn't means that replication is bad on that particular node. It is advised that the user run utils dbreplication status cli to find out where and what exactly is broken.
@ Topic starter:
I would suggest you try running " utils dbreplication" from CLI as metioned in the RTMT Text.
I'm sure you will find the reason why your cluster is in state "4"
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...