Table of Contents Previous Next


4 Using Failover Manager : 4.2 Monitoring a Failover Manager Cluster

You can use either the Failover Manager efm cluster-status command or the PEM Client graphical interface to check the current status of a monitored node of a Failover Manager cluster.
The cluster-status command returns a report that contains information about the status of the Failover Manager cluster. To invoke the command, enter:
The following status report is for a cluster with five nodes running:
Cluster Status: acctg
VIP:


Agent Type Address Agent DB Info
-------------------------------------------------------
Idle 172.24.38.106 UP UNKNOWN
Standby 172.24.38.123 UP UP
Standby 172.24.38.103 UP UP
Idle 172.24.38.152 UP UNKNOWN
Master 172.24.38.163 UP UP


Allowed node host list:
172.24.38.106 172.24.38.163 172.24.38.103 172.24.38.123 172.24.38.152


Membership coordinator: 172.24.38.123

Standby priority host list:
172.24.38.103 172.24.38.123


Promote Status:


DB Type Address XLog Loc Info
-------------------------------------------------------
Master 172.24.38.163 2/35000230
Standby 172.24.38.103 2/35000230
Standby 172.24.38.123 2/35000230


Standby database(s) in sync with master. It is safe to promote.


Idle Node Status (idle nodes ignored in XLog location comparisons):


Address XLog Loc Info
-------------------------------------------------------
172.24.38.152 2/35000160 DB is not in recovery.
172.24.38.106 UNKNOWN Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
The Cluster Status section provides an overview of the status of the agents that reside on each node of the cluster:
Cluster Status: acctg

Agent Type Address Agent DB Info
-------------------------------------------------------
Idle 172.24.38.106 UP UNKNOWN
Standby 172.24.38.123 UP UP
Standby 172.24.38.103 UP UP
Idle 172.24.38.152 UP UNKNOWN
Master 172.24.38.163 UP UP
The Allowed node host list and Standby priority host list provide an easy way to tell which nodes are allowed to join the cluster, and the promotion order of the standby nodes:
The Promote Status section of the report is the result of a direct query from the node on which you are invoking the cluster-status command to each database in the cluster; the query also returns the transaction log location of each database.
Promote Status:

DB Type Address XLog Loc Info
-------------------------------------------------------
Master 172.24.38.163 2/35000230
Standby 172.24.38.103 2/35000230
Standby 172.24.38.123 2/35000230


Standby
database(s) in sync with master. It is safe to promote.
If a database is down (or if the database has been restarted, but the resume command has not yet been invoked), the state of the agent that resides on that host will be Idle. If an agent is idle, the cluster status report will include a summary of the condition of the node.
Idle Node Status (idle nodes ignored in XLog location comparisons):

Address XLog Loc Info
-------------------------------------------------------
172.24.38.152 2/35000160 DB is not in recovery.
172.24.38.106 UNKNOWN Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.

4 Using Failover Manager : 4.2 Monitoring a Failover Manager Cluster

Table of Contents Previous Next