Red Hat GFS 5.2.1 -, Руководство администратора

Страница: 62 / 192

48 Chapter 6. Creating the Cluster Configuration System Files
fence_devices{
DeviceName {
agent = "fence_rib"
hostname = "
HostName "
login = " LoginName "
passwd = " LoginPassword "
}
DeviceName {
.
.
.
}
}
Figure 6-9. File Structure:
fence_devices
,
fence_rib
fence_devices{
DeviceName {
agent = "fence_manual"
}
DeviceName {
.
.
.
}
}
Figure 6-10. File Structure:
fence_devices
,
fence_manual
Parameter Description
DeviceName
The name of a fencing device. The
DeviceName
parameter
specifies the name of a fencing device and makes that fencing
device available for use by the fence section of a
nodes.ccs
file
(
nodes.ccs: NodeName /fence/ MethodName
). The fence
section of a
nodes.ccs
file also contains
DeviceName
parameters each mapping to a
DeviceName
in the
fence.ccs
file.
HostName
The host name of a RILOE card on the network to which stunnel
connections can be made.
IPAddress
For fencing with power and Fibre Channel switches: The IP
address of a switch to which Telnet connections can be
established.
For GNBD multipath fencing, used with the
fence_notify_gnbd
fencing agent (refer to Figure 6-8): IP
address (or hostname) of the GNBD client (a GFS node that has
imported a GNBD from the GNBD server).
IPAddress
is for
the
client =
entry and indicates which GNBD client to notify
if the GNBD server has failed and has been fenced. The
fence.ccs
file can have multiple
client =
entries — one for
each GNBD client.
LoginName
The login name for a power switch, an FC switch, or a RILOE
card.