Novell SUSE LINUX ENTERPRISE SERVER 10 SP2 HEARTBEAT Manual page 70

Hide thumbs Also See for SUSE LINUX ENTERPRISE SERVER 10 SP2 HEARTBEAT:
Table of Contents

Advertisement

Managing Configuration Changes
The crm_diff command assists you in creating and applying XML patches. This
can be useful for visualizing the changes between two versions of the cluster con-
figuration or saving changes so they can be applied at a later time using
(page 64). See
and command syntax.
Manipulating CIB Attributes
The crm_attribute command lets you query and manipulate node attributes
and cluster configuration options that are used in the CIB. See
(page 74) for a detailed introduction to this tool's usage and command syntax.
Validating the Cluster Configuration
The crm_verify command checks the configuration database (CIB) for consis-
tency and other problems. It can check a file containing the configuration or connect
to a running cluster. It reports two classes of problems. Errors must be fixed before
Heartbeat can work properly while warning resolution is up to the administrator.
crm_verify assists in creating new or modified configurations. You can take a
local copy of a CIB in the running cluster, edit it, validate it using crm_verify,
then put the new configuration into effect using cibadmin. See
(page 100) for a detailed introduction to this tool's usage and command syntax.
Managing Resource Configurations
The crm_resource command performs various resource-related actions on the
cluster. It lets you modify the definition of configured resources, start and stop re-
sources, or delete and migrate resources between nodes. See
(page 89) for a detailed introduction to this tool's usage and command syntax.
Managing Resource Fail Counts
The crm_failcount command queries the number of failures per resource on
a given node. This tool can also be used to reset the failcount, allowing the resource
to again run on nodes where it had failed too often. See
for a detailed introduction to this tool's usage and command syntax.
Generate and Retrieve Node UUIDs
UUIDs are used to identify cluster nodes to ensure that they can always be
uniquely identified. The command crm_uuid displays the UUID of the node on
which it is run. In very rare circumstances, it may be necessary to set a node's UUID
to a known value. This can also be achieved with crm_uuid, but you should use
62
Heartbeat
crm_diff(8)
(page 78) for a detailed introduction to this tool's usage
cibadmin(8)
crm_attribute(8)
crm_verify(8)
crm_resource(8)
crm_failcount(8)
(page 81)

Advertisement

Table of Contents
loading

Table of Contents