Red Hat GFS 6.0 Administrator's Manual page 154

140
b. Create the
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
node-specific I/O fencing parameters. The file should look like the following:
nodes {
n01 {
ip_interfaces {
}
fence {
}
}
n02 {
ip_interfaces {
}
fence {
}
}
n03 {
ip_interfaces {
}
fence {
}
}
}
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
rather than relying on an IP address from
optional
Example 6-26. Refer to Table 6-3 for syntax description of the
d. Create the
method(s) used by the GFS cluster. The file should look like the following:
file. This file contains the name of the cluster and the name of
cluster.ccs
file. This file contains the name of each node, its IP address, and
nodes.ccs
eth0 = "10.0.1.1"
power {
apc {
port = 1
}
}
eth0 = "10.0.1.2"
power {
apc {
port = 2
}
}
eth0 = "10.0.1.3"
power {
apc {
port = 3
}
}
parameter, refer to the file format in Figure 6-23 and the example in
usedev
file. This file contains information required for the fencing
fence.ccs
Appendix C. Basic GFS Examples
parameter to explicitly specify an IP address
usedev
. For more information about the
libresolv
parameter.
usedev