A number of tools are available (in /usr/lib/heartbeat) to assist Heartbeat administrators with management of the cluster.

Verifying the Configuration

The crm_verify[1] tool is provided with Heartbeat to check the configuration database (ClusterInformationBase[2]) for consistency and other problems. The tool can be used to check a file containing the configuration or can it can connect to a running cluster. It will report two classes of problems, ERRORs and WARNINGs. ERRORs must be fixed while WARNINGs are left to the administrators discretion. An example of an ERROR would be a constraint for a resource that doesn't exist, or objects with conflicting ids. While we would typically only provide a WARNING if a cluster option is not specified.

NOTE: Added in 2.0.3

Cluster Overview

Obtaining an overview of the cluster is possible with crm_mon[3]. The tool is able to indicate active and inactive nodes, known resources and their location (if any). crm_mon has several modes and can either:

• Dump the current status and exit
• Run as a daemon and generate a html file
• Run in a terminal and update itself periodically

NOTE: Added in 2.0.1
NOTE: The dump and exit option was added in 2.0.3

Resource Management

Resource management is primarily done via crm_resource[4]. With this tool, the admin can:

• list and locate the resources in the cluster
• migrated a resource away from its current location or to a specific node
• refresh the cluster after manually cleaning up a resource
• disable and delete resources

NOTE: Added in 2.0.3

Node Standby

A common task is to migrate all resources away from a node. In Heartbeat this is called standby mode and is possible with the crm_standby[5] tool. Nodes can be put into standby-mode indefinitely (until the administrator specifically says its ok to run resources there again), or until Heartbeat is restarted on that node (usually when the node reboots).

NOTE: Added in 2.0.2

Other Configuration Changes

Given the range of objects that can be understood by the CRM, there is no one tool that can create them all. Instead the cibadmin[6] tool was created to allow arbitrary changes to the configuration database. The tool allows existing objects to be queried, modified and deleted as well as new ones to be created.

Some rules must be adhered to when updating the CIB:

• All objects must contain a value for id

• Objects with the same tag may not share the same value for id

These rules are actively enforced - the CIB will modify updates that break these rules.

NOTE: Added in 2.0.0

---

This information provided courtesy of the Linux-HA project at http://linux-ha.org/