Installation guide

Command Line
Tool
Used With Purpose
ccs_tool —
Cluster Configur-
ation System
Tool
Cluster Infra-
structure
ccs_tool is a program for making online updates to the
cluster configuration file. It provides the capability to
create and modify cluster infrastructure components
(for example, creating a cluster, adding and removing a
node). For more information about this tool, refer to the
ccs_tool(8) man page.
cman_tool —
Cluster Manage-
ment Tool
Cluster Infra-
structure
cman_tool is a program that manages the CMAN cluster
manager. It provides the capability to join a cluster,
leave a cluster, kill a node, or change the expected
quorum votes of a node in a cluster. For more informa-
tion about this tool, refer to the cman_tool(8) man page.
fence_tool —
Fence Tool
Cluster Infra-
structure
fence_tool is a program used to join or leave the de-
fault fence domain. Specifically, it starts the fence dae-
mon (fenced) to join the domain and kills fenced to
leave the domain. For more information about this tool,
refer to the fence_tool(8) man page.
clustat —
Cluster Status
Utility
High-availability
Service Manage-
ment Compon-
ents
The clustat command displays the status of the
cluster. It shows membership information, quorum view,
and the state of all configured user services. For more
information about this tool, refer to the clustat(8) man
page.
clusvcadm —
Cluster User
Service Adminis-
tration Utility
High-availability
Service Manage-
ment Compon-
ents
The clusvcadm command allows you to enable, disable,
relocate, and restart high-availability services in a
cluster. For more information about this tool, refer to the
clusvcadm(8) man page.
Table 1.1. Command Line Tools
5. Configuration Considerations
You can configure a Red Hat Cluster in a variety of ways to suit your needs. Take into account
the following considerations when you plan, configure, and implement your Red Hat Cluster.
No-single-point-of-failure hardware configuration
Clusters can include a dual-controller RAID array, multiple bonded network channels, mul-
tiple paths between cluster members and storage, and redundant un-interruptible power
supply (UPS) systems to ensure that no single failure results in application down time or
loss of data.
Alternatively, a low-cost cluster can be set up to provide less availability than a no-
single-point-of-failure cluster. For example, you can set up a cluster with a single-controller
RAID array and only a single Ethernet channel.
5. Configuration Considerations
11