Chapter 6. Creating the Cluster Configuration System Files
The GFS Cluster Configuration System (CCS) requires the following files:
cluster.ccs — The cluster file contains the name of the cluster and the names of the nodes where LOCK_GULM servers are run.
fence.ccs — The fence file describes each device used for fencing.
nodes.ccs — The nodes file contains an entry for each GFS node and LOCK_GULM server node. This file specifies the IP address and fencing parameters of each node.
This chapter describes how to create the CCS files and contains the following sections:
 | Note |
|---|---|
If you are using GFS with Red Hat Cluster, you can create CCS files with GFS Druid. For information about configuring and using GFS with Red Hat Cluster Suite, refer to Appendix A Using Red Hat GFS with Red Hat Cluster Suite. |
6.1. Prerequisite Tasks
Before creating the CCS files, make sure that you perform the following prerequisite tasks:
Choose a cluster name (user variable, ClusterName).
Create a temporary directory (for example, /root/alpha/) in which to place the new CCS files that are created. Note the temporary directory path; it is used later as a Directory parameter when the CCS files are written to a CCA (Cluster Configuration Archive) device. For more information, refer to Section 7.1 Creating a CCS Archive.
Identify each node that runs the LOCK_GULM server daemons. Those nodes must have entries in the nodes.ccs file. Refer to Section 8.2 LOCK_GULM.
Determine if any GFS node has dual power supplies or multiple paths to FC storage.
Determine if you are using GNBD multipath.
Determine the type of fencing for each node.
For more information about prerequisite tasks, refer to Section 1.5 Before Configuring GFS