Cl_status will retrieve many different types of cluster status according to the subcommand given as its first argument.
hbstatus - indicate if Heartbeat is running on the local system.
listnodes [-p|-n] - List the nodes in the cluster.
nodestatus <node-name> - list the status of the given node.
nodetype <node-name> - list the nodes of a given type. Currently the available types are ping and normal.
listhblinks <node-name> - list the network interfaces used as heartbeat links.
hblinkstatus <node-name> <link-name> - show the status of a heartbeat link. This indicates up if we are able to hear from that node across that link. Note that if <node-name> is the current node, the status is not meaningful, since with few exceptions we don't receive messages from ourselves on any links.
clientstatus <node-name> <client-id> [<timeout>] - Show the status of Heartbeat clients. For example, ping or ipfail.
rscstatus - show the status of cluster resources. Status will be one of: local, foreign, all or none, or transition.
hbparameter -p <parameter-name> - return value of a given ha.cf parameter.
Many people find the rscstatus output difficult to understand.
paul 220.127.116.11 silas 18.104.22.168
If you issue this command on both nodes (one at a time): hb_standby local then after this, both machines will be running foreign resources. Weird, but if you want, you can do it. This is about the only way to make a node run only foreign resources.