Red Hat GFS 6.0 -, Administrator'S Manual

Page: 154 / 192

140 Appendix C. Basic GFS Examples
b. Create the
cluster.ccs
file. This file contains the name of the cluster and the name of
the nodes where the LOCK_GULM server is run. The file should look like the following:
cluster {
name = "alpha"
lock_gulm {
servers = ["n01", "n02", "n03"]
}
}
c. Create the
nodes.ccs
file. This file contains the name of each node, its IP address, and
node-specific I/O fencing parameters. The file should look like the following:
nodes {
n01 {
ip_interfaces {
eth0 = "10.0.1.1"
}
fence {
power {
apc {
port = 1
}
}
}
}
n02 {
ip_interfaces {
eth0 = "10.0.1.2"
}
fence {
power {
apc {
port = 2
}
}
}
}
n03 {
ip_interfaces {
eth0 = "10.0.1.3"
}
fence {
power {
apc {
port = 3
}
}
}
}
}
Note
If your cluster is running Red Hat GFS 6.0 for Red Hat Enterprise Linux 3 Update 5
and later, you can use the optional
usedev
parameter to explicitly specify an IP address
rather than relying on an IP address from
libresolv
. For more information about the
optional
usedev
parameter, refer to the file format in Figure 6-23 and the example in
Example 6-26. Refer to Table 6-3 for syntax description of the
usedev
parameter.
d. Create the
fence.ccs
file. This file contains information required for the fencing
method(s) used by the GFS cluster. The file should look like the following: