Page MenuHomeClusterLabs Projects

index.html
No OneTemporary

index.html

This document is not UTF8. It was detected as ISO-8859-1 (Latin 1) and converted to UTF8 for display.
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 1. Managing a Cluster</title><meta name="generator" content="DocBook XSL Stylesheets V1.71.1"><link rel="start" href="index.html" title="Chapter 1. Managing a Cluster"><link rel="next" href="re01.html" title="cibadmin"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 1. Managing a Cluster</th></tr><tr><td width="20%" align="left"> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="re01.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="cha.hb.management"></a>Chapter 1. Managing a Cluster</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="refentrytitle"><a href="re01.html">cibadmin</a></span><span class="refpurpose"> &#8212; read, modify, or administer Heartbeat Cluster Information
Base</span></dt><dt><span class="refentrytitle"><a href="re02.html">crmadmin</a></span><span class="refpurpose"> &#8212; control the Cluster Resource Manager</span></dt><dt><span class="refentrytitle"><a href="re03.html">crm_attribute</a></span><span class="refpurpose"> &#8212; manipulate attributes in the CIB</span></dt><dt><span class="refentrytitle"><a href="re04.html">crm_diff</a></span><span class="refpurpose"> &#8212; identify changes to the cluster configuration and apply patches
to the configuration files</span></dt><dt><span class="refentrytitle"><a href="re05.html">crm_failcount</a></span><span class="refpurpose"> &#8212; manipulate the failcount attribute on a given
resource</span></dt><dt><span class="refentrytitle"><a href="re06.html">crm_master</a></span><span class="refpurpose"> &#8212; determine which resource instance to promote to master</span></dt><dt><span class="refentrytitle"><a href="re07.html">crm_mon</a></span><span class="refpurpose"> &#8212; monitor the cluster's status</span></dt><dt><span class="refentrytitle"><a href="re08.html">crm_resource</a></span><span class="refpurpose"> &#8212; interact with the Cluster Resource Manager</span></dt><dt><span class="refentrytitle"><a href="re09.html">crm_standby</a></span><span class="refpurpose"> &#8212; manipulate a node's standby attribute to determine whether
resources can be run on this node</span></dt><dt><span class="refentrytitle"><a href="re10.html">crm_uuid</a></span><span class="refpurpose"> &#8212; get a node's UUID</span></dt><dt><span class="refentrytitle"><a href="re11.html">crm_verify</a></span><span class="refpurpose"> &#8212; check the CIB for consistency</span></dt></dl></div><p>
Heartbeat ships with a comprehensive set of tools that assist you in managing your
cluster from the command line. This chapter introduces the tools needed for
managing the cluster configuration in the CIB and the cluster resources.
Other command line tools for managing resource agents or tools used for
debugging and troubleshooting your setup are covered in ??? and ???.
</p><p>The following list presents several tasks related to cluster management
and briefly introduces the tools to use to accomplish these tasks:</p><div class="variablelist"><dl><dt><span class="term">Monitoring the Cluster's Status</span></dt><dd><p>The <span><strong class="command">crm_mon</strong></span> 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
<span><strong class="command">crm_mon</strong></span> can be displayed at the console or printed into
an HTML file. When provided with a cluster configuration file without the
status section, <span><strong class="command">crm_mon</strong></span> creates an overview of nodes
and resources as specified in the file. See <a href="re07.html" title="crm_mon"><span class="refentrytitle">crm_mon</span>(8)</a> for a detailed introduction to this tool's usage
and command syntax.</p></dd><dt><span class="term">Managing the CIB</span></dt><dd><p>The <span><strong class="command">cibadmin</strong></span> command is the low-level
administrative command for manipulating the Heartbeat CIB. It can be used
to dump all or part of the CIB, update all or part of it, modify all or
part of it, delete the entire CIB, or perform miscellaneous CIB
administrative operations. See <a href="re01.html" title="cibadmin"><span class="refentrytitle">cibadmin</span>(8)</a> for a
detailed introduction
to this tool's usage and command syntax.</p></dd><dt><span class="term">Managing Configuration Changes</span></dt><dd><p>The <span><strong class="command">crm_diff</strong></span> command assists you in creating and
applying XML patches. This can be useful for visualizing the changes
between two versions of the cluster configuration or saving changes so
they can be applied at a later time using <a href="re01.html" title="cibadmin"><span class="refentrytitle">cibadmin</span>(8)</a>.
See <a href="re04.html" title="crm_diff"><span class="refentrytitle">crm_diff</span>(8)</a> for a detailed introduction to this
tool's usage and command syntax.</p></dd><dt><span class="term">Manipulating CIB Attributes</span></dt><dd><p>The <span><strong class="command">crm_attribute</strong></span> command lets you query and
manipulate node attributes and cluster configuration options that are
used in the CIB. See <a href="re03.html" title="crm_attribute"><span class="refentrytitle">crm_attribute</span>(8)</a> for a
detailed introduction to this tool's usage and command syntax.</p></dd><dt><span class="term">Validating the Cluster Configuration</span></dt><dd><p>The <span><strong class="command">crm_verify</strong></span> command checks the
configuration database (CIB) for consistency 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. <span><strong class="command">crm_verify</strong></span> 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
<span><strong class="command">crm_verify</strong></span>, then put the new configuration into
effect using <span><strong class="command">cibadmin</strong></span>. See <a href="re11.html" title="crm_verify"><span class="refentrytitle">crm_verify</span>(8)</a> for a detailed introduction to this tool's
usage and command syntax.
</p></dd><dt><span class="term">Managing Resource Configurations</span></dt><dd><p>The <span><strong class="command">crm_resource</strong></span> command performs
various resource-related actions on the cluster. It lets you modify the
definition of configured resources, start and stop resources, or delete
and migrate resources between nodes. See <a href="re08.html" title="crm_resource"><span class="refentrytitle">crm_resource</span>(8)</a> for
a detailed introduction to this tool's usage and command syntax.</p></dd><dt><span class="term">Managing Resource Fail Counts</span></dt><dd><p>The <span><strong class="command">crm_failcount</strong></span> 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 <a href="re05.html" title="crm_failcount"><span class="refentrytitle">crm_failcount</span>(8)</a> for
a detailed introduction to this tool's usage and command syntax.</p></dd><dt><span class="term">Generate and Retrieve Node UUIDs</span></dt><dd><p>UUIDs are used to identify cluster nodes to ensure that they can
always be uniquely identified. The command <span><strong class="command">crm_uuid</strong></span>
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 <span><strong class="command">crm_uuid</strong></span>, but you should use this command
with extreme caution. For more information, refer to <a href="re10.html" title="crm_uuid"><span class="refentrytitle">crm_uuid</span>(8)</a>.</p></dd><dt><span class="term">Managing a Node's Standby Status</span></dt><dd><p>The <span><strong class="command">crm_standby</strong></span> 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 as it should
become a fully active member of the cluster again. See <a href="re09.html" title="crm_standby"><span class="refentrytitle">crm_standby</span>(8)</a> for a detailed introduction to this
tool's usage and command syntax.
</p></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="re01.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"> </td><td width="20%" align="center"> </td><td width="40%" align="right" valign="top"> cibadmin</td></tr></table></div></body></html>

File Metadata

Mime Type
text/html
Expires
Tue, Jul 8, 5:10 PM (1 d, 15 h)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
1980857
Default Alt Text
index.html (9 KB)

Event Timeline