This appendix provides tables with parameter descriptions of fence devices.
Note
Certain fence devices have an optional parameter. The parameter allows specifying that a fence-device password is supplied from a script rather than from the parameter. Using the parameter supersedes the parameter, allowing passwords to not be visible in the cluster configuration file (/etc/cluster/cluster.conf).
|
Field
|
Description
|
|---|
|
Name
|
A name for the APC device connected to the cluster.
|
|
IP Address
|
The IP address assigned to the device.
|
|
Login
|
The login name used to access the device.
|
|
Password
|
The password used to authenticate the connection to the device.
|
|
Password Script (optional)
|
The script that supplies a password for access to the fence device. Using this supersedes the parameter.
|
Table B.1. APC Power Switch
|
Field
|
Description
|
|---|
|
Name
|
A name for the Brocade device connected to the cluster.
|
|
IP Address
|
The IP address assigned to the device.
|
|
Login
|
The login name used to access the device.
|
|
Password
|
The password used to authenticate the connection to the device.
|
|
Password Script (optional)
|
The script that supplies a password for access to the fence device. Using this supersedes the parameter.
|
Table B.2. Brocade Fabric Switch
|
Field
|
Description
|
|---|
|
IP Address
|
The IP address assigned to the PAP console.
|
|
Login
|
The login name used to access the PAP console.
|
|
Password
|
The password used to authenticate the connection to the PAP console.
|
|
Password Script (optional)
|
The script that supplies a password for access to the fence device. Using this supersedes the parameter.
|
|
Domain
|
Domain of the Bull PAP system to power cycle
|
Table B.3. Bull PAP (Platform Administration Processor)
|
Field
|
Description
|
|---|
|
Name
|
The name assigned to the DRAC.
|
|
IP Address
|
The IP address assigned to the DRAC.
|
|
Login
|
The login name used to access the DRAC.
|
|
Password
|
The password used to authenticate the connection to the DRAC.
|
|
Password Script (optional)
|
The script that supplies a password for access to the fence device. Using this supersedes the parameter.
|
Table B.4. Dell DRAC
|
Field
|
Description
|
|---|
|
Name
|
A name for the BladeFrame device connected to the cluster.
|
|
CServer
|
The hostname (and optionally the username in the form of username@hostname) assigned to the device. Refer to the fence_egenera(8) man page.
|
|
ESH Path (optional)
|
The path to the esh command on the cserver (default is /opt/pan- mgr/bin/esh)
|
Table B.5. Egenera SAN Controller
|
Field
|
Description
|
|---|
|
Name
|
A name for the GNBD device used to fence the cluster. Note that the GFS server must be accessed via GNBD for cluster node fencing support.
|
|
Server
|
The hostname of each GNBD to disable. For multiple hostnames, separate each hostname with a space.
|
Table B.6. GNBD (Global Network Block Device)
|
Field
|
Description
|
|---|
|
Name
|
A name for the server with HP iLO support.
|
|
Hostname
|
The hostname assigned to the device.
|
|
Login
|
The login name used to access the device.
|
|
Password
|
The password used to authenticate the connection to the device.
|
|
Password Script (optional)
|
The script that supplies a password for access to the fence device. Using this supersedes the parameter.
|
Table B.7. HP iLO (Integrated Lights Out)
|
Field
|
Description
|
|---|
|
Name
|
A name for the IBM BladeCenter device connected to the cluster.
|
|
IP Address
|
The IP address assigned to the device.
|
|
Login
|
The login name used to access the device.
|
|
Password
|
The password used to authenticate the connection to the device.
|
|
Password Script (optional)
|
The script that supplies a password for access to the fence device. Using this supersedes the parameter.
|
Table B.8. IBM Blade Center
|
Field
|
Description
|
|---|
|
Name
|
A name for the RSA device connected to the cluster.
|
|
IP Address
|
The IP address assigned to the device.
|
|
Login
|
The login name used to access the device.
|
|
Password
|
The password used to authenticate the connection to the device.
|
|
Password Script (optional)
|
The script that supplies a password for access to the fence device. Using this supersedes the parameter.
|
Table B.9. IBM Remote Supervisor Adapter II (RSA II)
|
Field
|
Description
|
|---|
|
IP Address
|
The IP address assigned to the IPMI port.
|
|
Login
|
The login name of a user capable of issuing power on/off commands to the given IPMI port.
|
|
Password
|
The password used to authenticate the connection to the IPMI port.
|
|
Password Script (optional)
|
The script that supplies a password for access to the fence device. Using this supersedes the parameter.
|
|
Authentication Type
|
none, password, md2, or md5
|
|
Use Lanplus
|
True or 1. If blank, then value is False.
|
Table B.10. IPMI (Intelligent Platform Management Interface) LAN
|
Field
|
Description
|
|---|
|
Name
|
A name to assign the Manual fencing agent. Refer to fence_manual(8) for more information.
|
Table B.11. Manual Fencing
Warning
Manual fencing is not supported for production environments.
|
Field
|
Description
|
|---|
|
Name
|
A name for the McData device connected to the cluster.
|
|
IP Address
|
The IP address assigned to the device.
|
|
Login
|
The login name used to access the device.
|
|
Password
|
The password used to authenticate the connection to the device.
|
|
Password Script (optional)
|
The script that supplies a password for access to the fence device. Using this supersedes the parameter.
|
Table B.12. McData SAN Switch
|
Field
|
Description
|
|---|
|
Name
|
A name for the WTI RPS-10 power switch connected to the cluster.
|
|
Device
|
The device the switch is connected to on the controlling host (for example, /dev/ttys2).
|
|
Port
|
The switch outlet number.
|
Table B.13. RPS-10 Power Switch (two-node clusters only)
|
Field
|
Description
|
|---|
|
Name
|
A name for the SANBox2 device connected to the cluster.
|
|
IP Address
|
The IP address assigned to the device.
|
|
Login
|
The login name used to access the device.
|
|
Password
|
The password used to authenticate the connection to the device.
|
|
Password Script (optional)
|
The script that supplies a password for access to the fence device. Using this supersedes the parameter.
|
Table B.14. QLogic SANBox2 Switch
|
Field
|
Description
|
|---|
|
Name
|
Name of the node to be fenced. Refer to fence_scsi(8) for more information.
|
Table B.15. SCSI Fencing
Note
Use of SCSI persistent reservations as a fence method is supported with the following limitations:
SCSI fencing is not supported in a two-node cluster.
When using SCSI fencing, all nodes in the cluster must register with the same devices so that each node can remove another node's registration key from all the devices it is registered with.
Devices used for the cluster volumes should be a complete LUN, not partitions. SCSI persistent reservations work on an entire LUN, meaning that access is controlled to each LUN, not individual partitions.
|
Field
|
Description
|
|---|
|
Name
|
Name of the guest to be fenced.
|
Table B.16. Virtual Machine Fencing
|
Field
|
Description
|
|---|
|
Name
|
A name for the Vixel switch connected to the cluster.
|
|
IP Address
|
The IP address assigned to the device.
|
|
Password
|
The password used to authenticate the connection to the device.
|
|
Password Script (optional)
|
The script that supplies a password for access to the fence device. Using this supersedes the parameter.
|
Table B.17. Vixel SAN Switch
|
Field
|
Description
|
|---|
|
Name
|
A name for the WTI power switch connected to the cluster.
|
|
IP Address
|
The IP address assigned to the device.
|
|
Password
|
The password used to authenticate the connection to the device.
|
|
Password Script (optional)
|
The script that supplies a password for access to the fence device. Using this supersedes the parameter.
|
Table B.18. WTI Power Switch
