Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Appendix B. Fence Device Parameters

This appendix provides tables with parameter descriptions of fence devices.

Note

Certain fence devices have an optional Password Script parameter. The Password Scriptparameter allows specifying that a fence-device password is supplied from a script rather than from the Password parameter. Using the Password Script parameter supersedes the Password parameter, allowing passwords to not be visible in the cluster configuration file (/etc/cluster/cluster.conf).
Expand
Table B.1. APC Power Switch
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 Password parameter.
Port The switch outlet number.
Switch (optional) The switch number for the APC switch that connects to the node when you have multiple daisy-chained switches.
Use SSH (Rhel 4.8 and later) Indicates that system will use SSH to access the device.
Expand
Table B.2. Brocade Fabric 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 Password parameter.
Port The switch outlet number.
Expand
Table B.3. Bull PAP (Platform Administration Processor)
Field Description
Name A name for the Bull PAP system connected to the cluster.
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 Password parameter.
Domain Domain of the Bull PAP system to power cycle.
Expand
Table B.4. Dell DRAC
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.
Module name (optional) The module name for the DRAC when you have multiple DRAC modules.
Password Script (optional) The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
Use SSH (DRAC5 only) (Rhel 4.8 and later) Indicates that system will use SSH to access the device.
Expand
Table B.5. Egenera SAN Controller
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 for more information.
ESH Path (optional) The path to the esh command on the cserver (default is /opt/pan- mgr/bin/esh)
lpan The logical process area network (LPAN) of the device.
pserver The processing blade (pserver) name of the device.
Expand
Table B.6. Fujitsu Siemens Remoteview Service Board (RSB)
Field Description
Name A name for the RSB to use as a fence device.
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 Password parameter.
Expand
Table B.7. GNBD (Global Network Block Device)
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 the server to fence the client from, in either IP address or hostname form. For multiple hostnames, separate each hostname with a space.
IP address The cluster name of the node to be fenced. Refer to the fence_gnbd(8) man page for more information.
Expand
Table B.8. HP iLO (Integrated Lights Out)
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 Password parameter.
Use SSH (Rhel 4.8 and later) Indicates that system will use SSH to access the device.
Expand
Table B.9. IBM Blade Center
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 Password parameter.
Blade The blade of the device.
Use SSH (Rhel 4.8 and later) Indicates that system will use SSH to access the device.
Expand
Table B.10. IBM Remote Supervisor Adapter II (RSA II)
Field Description
Name A name for the RSA device connected to the cluster.
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 Password parameter.
Expand
Table B.11. IPMI (Intelligent Platform Management Interface) LAN
Field Description
Name A name for the IPMI LAN device connected to the cluster.
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 Password parameter.
Authentication Type none, password, md2, or md5
Use Lanplus True or 1. If blank, then value is False.
Expand
Table B.12. LPAR Fencing (RHEL 4.8 and later)
Field Description
Name A name for the LPAR to use as a fence device.
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 Password parameter.
Partition Name of LPAR partition to use as a fence device when there are multiple LPARs.
hmc-version Version 3 or 4. A value of 4 is the default.
Managed Name of the managed system.
Expand
Table B.13. Manual Fencing
Field Description
Name A name to assign the Manual fencing agent. Refer to the fence_manual(8) man page for more information.

Warning

Manual fencing is not supported for production environments.
Expand
Table B.14. McData SAN Switch
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 Password parameter.
Port The switch outlet number.
Expand
Table B.15. QLogic SANBox2 Switch
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 Password parameter.
Port The switch outlet number.
Expand
Table B.16. RPS-10 Power Switch (two-node clusters only)
Field Description
Name A name for the WTI RPS-10 power switch connected to the cluster.
Device Name The device name of the device the switch is connected to on the controlling host (for example, /dev/ttys2).
Port The switch outlet number.
Expand
Table B.17. SCSI Fencing
Field Description
Name A name for the SCSI fence device.
Node name Name of the node to be fenced. Refer to the fence_scsi(8) man page for more information.
Expand
Table B.18. Virtual Machine Fencing
Field Description
Name Name of the virtual machine fencing device.
Domain Unique domain name of the guest to be fenced.
Expand
Table B.19. Vixel SAN Switch
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 Password parameter.
Port The switch outlet number.
Expand
Table B.20. WTI Power 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 Password parameter.
Port The switch outlet number.
Use SSH (Rhel 4.8 and later) Indicates that system will use SSH to access the device.
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat