Red Hat GFS 5.2.1 -, Administrator'S Manual

Page: 59 / 192

Chapter 6. Creating the Cluster Configuration System Files 45
d. For each Vixel FC-switch fencing device, specify the following parameters:
DeviceName
, the fencing agent (
agent =
) as
fence_vixel
,
IPAddress
, and
LoginPassword
. Refer to Example 6-6 for a
fence.ccs
file that specifies a Vixel
FC-switch fencing device.
e. For each GNBD fencing device, specify the following parameters:
DeviceName
, the
fencing agent (
agent =
) as
fence_gnbd
, and
ServerName
.
For GNBD multipath, include an
option = "multipath"
line after the
ServerName
line. In addition, for GNBD multipath, you can add two optional lines:
retrys =
" Number "
and
wait_time = " Seconds "
.
For descriptions of those parameters refer to Table 6-2. Refer to Example 6-7 for a
fence.ccs
file that specifies a GNBD fencing device for a configuration that does not
employ GNBD multipath. Refer to Example 6-8 for a
fence.ccs
file that specifies a
GNBD fencing device for a configuration that does employ GNBD multipath.
Note
For GFS clusters using GNBD multipath, do not configure the GNBD server nodes to be
fenced with the GNBD fencing agent,
fence_gnbd
.
f. For Fence Notify GNBD (used with GNBD multipath), specify a device for notifying
GFS clients that a GNBD server node has been fenced. Specify the following parame-
ters:
DeviceName
, the fencing agent (
agent =
) as
fence_notify_gnbd
, and each
GNBD client (a GFS node that is using GNBD),
client =
. Refer to Example 6-9 for a
fence.ccs
file that specifies a Fence Notify GNBD fencing device.
g. For each HP-RILOE-card fencing device, specify the following parameters:
DeviceName
, the fencing agent (
agent =
) as
fence_rib
,
HostName
,
LoginName
,
and
LoginPassword
. Refer to Example 6-10 for a
fence.ccs
file that specifies an
HP-RILOE-card fencing device.
h. For each manual fencing device, specify
DeviceName
and the fencing agent (
agent =
)
as
fence_manual
. Refer to Example 6-11 for a
fence.ccs
file that specifies a manual
fencing device.
3. Save the file.
fence_devices{
DeviceName {
agent = "fence_apc"
ipaddr = "
IPAddress "
login = " LoginName "
passwd = " LoginPassword "
}
DeviceName {
.
.
.
}
}
Figure 6-2. File Structure:
fence_devices
,
fence_apc