cl_status(1) [debian man page]

CL_STATUS(1)							   User commands						      CL_STATUS(1)

NAME

       cl_status - Check status of the High-Availability Linux (Linux-HA) subsystem

SYNOPSIS

       cl_status sub-command options parameters

DESCRIPTION

       cl_status is used to check the status of the High-Availability Linux subsystem.

SUPPORTED SUB-COMMANDS
       hbstatus
	   Indicate if heartbeat is running on the local system.

       listnodes
	   List the nodes in the cluster.

       nodetype ping|normal
	   List the nodes of the given type.

	       Note
	       Ping nodes are obsolete in Pacemaker cluster, having been replaced with the pingd resource agent.

       listhblinks node
	   List the network interfaces used as heartbeat links.  node should be specified as listed in the ha.cf(5) file for the cluster.

       hblinkstatus node link
	   Show the status of a heartbeat link.  node should be specified as listed in the ha.cf(5) file for the cluster.  link should be as per
	   the output of the listhblinks subcommand.

       clientstatus node client [timeout]
	   Show the status of heartbeat clients.  node and client should be specified as listed in the ha.cf(5) file for the cluster. Timeout is
	   in milliseconds, the default is 100ms.

       rscstatus
	   Show the status of cluster resources. Status will be one of: local, foreign, all or none.

	       Note
	       This option is deprecated, it is obsolete in Pacemaker clusters.

       parameter -p parameter
	   Retrieve the value of cluster parameters. The parameters may be one of the following: apiauth, auto_failback, baud, debug, debugfile,
	   deadping, deadtime, hbversion, hopfudge, initdead, keepalive, logfacility, logfile, msgfmt, nice_failback, node, normalpoll, stonith,
	   udpport, warntime, watchdog.

	       Note
	       Some of these options are deprecated; see ha.cf(5)

OPTIONS

       The following options are supported by heartbeat:

       -m
	   Make the output more human readable. The default output should be easier for scripts to parse. Available with all commands.

       -p
	   List only 'ping' nodes. Available with listnodes sub-command.

	       Note
	       Ping nodes are obsolete in Pacemaker cluster, having been replaced with the pingd resource agent.

       -n
	   List only 'normal' nodes. Available with listnodes sub-command.

SEE ALSO

       heartbeat(8), ha.cf(5), authkeys(5)

AUTHORS

       Alan Robertson <alanr@unix.sh>
	   cl_status

       Juan Pedro Paredes Caballero <juampe@retemail.es>
	   man page

       Simon Horman <horms@verge.net.au>
	   man page

       Florian Haas <florian.haas@linbit.com>
	   man page

Heartbeat 3.0.5 						    24 Nov 2009 						      CL_STATUS(1)

CRM_MON(8)							  [FIXME: manual]							CRM_MON(8)

NAME

       crm_mon - monitor the cluster's status

SYNOPSIS

	   crm_mon [-V] -d -pfilename -h filename

	   crm_mon [-V] [-1|-n|-r] -h filename

	   crm_mon [-V] [-n|-r] -X filename

	   crm_mon [-V] [-n|-r] -c|-1

	   crm_mon [-V] -i interval

	   crm_mon -?

DESCRIPTION

       The crm_mon command allows you to monitor your cluster's status and configuration. Its output includes the number of nodes, uname, uuid,
       status, the resources configured in your cluster, and the current status of each. The output of crm_mon can be displayed at the console or
       printed into an HTML file. When provided with a cluster configuration file without the status section, crm_mon creates an overview of nodes
       and resources as specified in the file.

OPTIONS

       --help, -?
	   Provide help.

       --verbose, -V
	   Increase the debug output.

       --interval seconds, -i seconds
	   Determine the update frequency. If -i is not specified, the default of 15 seconds is assumed.

       --group-by-node, -n
	   Group resources by node.

       --inactive, -r
	   Display inactive resources.

       --as-console, -c
	   Display the cluster status on the console.

       --one-shot, -1
	   Display the cluster status once on the console then exit (does not use ncurses).

       --as-html filename, -h filename
	   Write the cluster's status to the specified file.

       --daemonize, -d
	   Run in the background as a daemon.

       --pid-file filename, -p filename
	   Specify the daemon's pid file.

       --xml-file filename, -X filename
	   Specify an XML file containing a cluster configuration and create an overview of the cluster's configuration.

EXAMPLES

       Display your cluster's status and get an updated listing every 15 seconds:

	       crm_mon

       Display your cluster's status and get an updated listing after an interval specified by -i. If -i is not given, the default refresh
       interval of 15 seconds is assumed:

	       crm_mon -i interval[s]

       Display your cluster's status on the console:

	       crm_mon -c

       Display your cluster's status on the console just once then exit:

	       crm_mon -1

       Display your cluster's status and group resources by node:

	       crm_mon -n

       Display your cluster's status, group resources by node, and include inactive resources in the list:

	       crm_mon -n -r

       Write your cluster's status to an HTML file:

	       crm_mon -h filename

       Run crm_mon as a daemon in the background, specify the daemon's pid file for easier control of the daemon process, and create HTML output.
       This option allows you to constantly create HTML output that can be easily processed by other monitoring applications:

	       crm_mon -d -p filename -h filename

       Display the cluster configuration laid out in an existing cluster configuration file (filename), group the resources by node, and include
       inactive resources. This command can be used for dry-runs of a cluster configuration before rolling it out to a live cluster.

	       crm_mon -r -n -X filename

FILES

       /var/lib/heartbeat/crm/cib.xml--the CIB (minus status section) on disk. Editing this file directly is strongly discouraged.

AUTHOR

       crm_mon was written by Andrew Beekhof.

[FIXME: source] 						    07/05/2010								CRM_MON(8)