Red Hat GFS 6.0 -, Administrator'S Manual

Page: 57 / 192

Chapter 6. Creating the Cluster Configuration System Files 43
Note
Do not use
fence_gnbd
to fence GNBD server nodes.
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.
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-9 for a
fence.ccs
file that specifies an
HP-RILOE-card fencing device.
h. For each xCAT fencing device, specify the following parameters:
DeviceName
, the
fencing agent (
agent =
) as
fence_xcat
, and
RpowerBinaryPath
. Refer to
Example 6-10 for a
fence.ccs
file that specifies an xCAT fencing device.
i. For each Egenera BladeFrame fencing device, specify the following parameters:
DeviceName
, the fencing agent (
agent =
) as
fence_egenera
, and
CserverName
.
Refer to Example 6-11 for a
fence.ccs
file that specifies an Egenera BladeFrame
fencing device.
j. For each manual fencing device, specify
DeviceName
and the fencing agent (
agent =
)
as
fence_manual
. Refer to Example 6-12 for a
fence.ccs
file that specifies a manual
fencing device.
Warning
Manual fencing should not be used in a production environment. Manual fencing de-
pends on human intervention whenever a node needs recovery. Cluster operation is
halted during the intervention.
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