Novell LINUX ENTERPRISE 11 - HIGH AVAILABILITY, Руководство пользователя, Страница: 150 / 298

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 cibadmin(8)
(page 142). See crm_diff(8) (page 154) for a detailed introduction to this tool's usage
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 crm_attribute(8)
(page 151) 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 crm_verify(8)
(page 190) 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 crm_resource(8)
(page 166) 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 crm_failcount(8) (page 157)
for a detailed introduction to this tool's usage and command syntax.
Managing a Node's Standby Status
The
crm_standby
command can manipulate a node's standby attribute. Any
node in standby mode is no longer eligible to host resources and any resources that
are there must be moved. Standby mode can be useful for performing maintenance
tasks, such as kernel updates. Remove the standby attribute from the node for it to
140 High Availability Guide