This site best when viewed with a modern standards-compliant browser. We recommend Firefox Get Firefox!.

Linux-HA project logo
Providing Open Source High-Availability Software for Linux and other OSes since 1999.

USA Flag UK Flag

Japanese Flag

Homepage

About Us

Contact Us

Legal Info

How To Contribute

Security Issues

This web page is no longer maintained. Information presented here exists only to avoid breaking historical links.
 The Project stays maintained, and lives on: see the Linux-HA Reference Documentation.

1 February 2010 Hearbeat 3.0.2 released see the Release Notes

18 January 2009 Pacemaker 1.0.7 released see the Release Notes

16 November 2009 LINBIT new Heartbeat Steward see the Announcement

Last site update:
2010-03-16 06:27:27

cl_status - command for retrieving cluster status information

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.

    • -p list only 'ping' type nodes -n list only 'normal' type nodes

  • 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.

rscstatus details

Many people find the rscstatus output difficult to understand.

For this example, we'll use the following ActiveActive haresources file 

paul 1.2.3.4
silas 5.6.7.8

On paul:

  • local == 1.2.3.4
  • foreign == 5.6.7.8
  • all == 1.2.3.4, 5.6.7.8

On silas:

  • foreign == 1.2.3.4
  • local == 5.6.7.8
  • all == 1.2.3.4, 5.6.7.8

rscstatus relationships

  • paul(local) implies silas(local)
  • paul(foreign) implies silas(foreign)
  • paul(all) implies silas(none) (or silas down)
  • paul(none) implies silas(all)
  • silas(local) implies paul(local)
  • silas(foreign) implies paul(foreign)
  • silas(all) implies paul(none) (or paul down)
  • silas(none) implies paul(all)

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.

See Also

mon