Appendix B. Fence Device Parameters


This appendix provides tables with parameter descriptions of fence devices.

Note

The Name parameter for a fence device specifies an arbitrary name for the device that will be used by Red Hat Cluster Suite. This is not the same as the DNS name for the device.

Note

Certain fence devices have an optional Password Script parameter. The Password Script parameter 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).
Table B.1. APC Power Switch
FieldDescription
NameA name for the APC device connected to the cluster.
IP AddressThe IP address assigned to the device.
LoginThe login name used to access the device.
PasswordThe 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.
Power wait Number of seconds to wait after issuing a power off or power on command.
PortThe port.
Switch (optional) The switch number for the APC switch that connects to the node when you have multiple daisy-chained switches.
Use SSH (Red Hat Enterprise Linux 5.4 and later) Indicates that system will use SSH to access the device.
fence_apc The fence agent for APC.
Table B.2. APC Power Switch over SNMP (Red Hat Enterprise Linux 5.2 and later)
FieldDescription
NameA name for the APC device connected to the cluster into which the fence daemon logs via the SNMP protocol.
IP AddressThe IP address or hostname assigned to the device.
UDP/TCP Port The UDP/TCP port to use for connection with the device; the default value is 161.
LoginThe login name used to access the device.
PasswordThe 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.
SNMP version The SNMP version to use (1, 2c, 3); the default value is 1.
SNMP community The SNMP community string; the default value is private.
SNMP security level The SNMP security level (noAuthNoPriv, authNoPriv, authPriv).
SNMP authentication protocol The SNMP authentication protocol (MD5, SHA).
SNMP privacy protocol The SNMP privacy protocol (DES, AES).
SNMP privacy protocol password The SNMP privacy protocol password.
SNMP privacy protocol script The script that supplies a password for SNMP privacy protocol. Using this supersedes the SNMP privacy protocol password parameter.
Power wait Number of seconds to wait after issuing a power off or power on command.
PortThe port.
fence_apc_snmp The fence agent for APC that logs into the SNP device via the SNMP protocol.
Table B.3. Brocade Fabric Switch
FieldDescription
NameA name for the Brocade device connected to the cluster.
IP AddressThe IP address assigned to the device.
LoginThe login name used to access the device.
PasswordThe 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.
PortThe switch outlet number.
fence_brocade The fence agent for Brocade FC switches.
Table B.4. Bull PAP (Platform Administration Processor)
FieldDescription
NameA name for the Bull PAP system connected to the cluster.
IP AddressThe IP address assigned to the PAP console.
LoginThe login name used to access the PAP console.
PasswordThe 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.
DomainDomain of the Bull PAP system to power cycle.
fence_bullpap The fence agent for Bull’s NovaScale machines controlled by PAP management consoles.
Table B.5. Cisco MDS (Red Hat Enterprise Linux 5.4 and later)
FieldDescription
NameA name for the Cisco MDS 9000 series device with SNMP enabled.
IP address or hostnameThe IP address or hostname assigned to the device.
UDP/TCP port (optional) The UDP/TCP port to use for connection with the device; the default value is 161.
LoginThe login name used to access the device.
PasswordThe 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.
SNMP version The SNMP version to use (1, 2c, 3).
SNMP community The SNMP community string.
SNMP security level The SNMP security level (noAuthNoPriv, authNoPriv, authPriv).
SNMP authentication protocol The SNMP authentication protocol (MD5, SHA).
SNMP privacy protocol The SNMP privacy protocol (DES, AES).
SNMP privacy protocol password The SNMP privacy protocol password.
SNMP privacy protocol script The script that supplies a password for SNMP privacy protocol. Using this supersedes the SNMP privacy protocol password parameter.
Power wait Number of seconds to wait after issuing a power off or power on command.
PortThe port.
fence_cisco_mds The fence agent for Cisco MDS.
Table B.6. Cisco UCS (Red Hat Enterprise Linux 5.6 and later)
FieldDescription
NameA name for the Cisco UCS device.
IP AddressThe IP address or hostname assigned to the device.
IP port (optional) The TCP port to use to connect to the device.
LoginThe login name used to access the device.
PasswordThe 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 SSL connections Use SSL connections to communicate with the device.
Sub-organizationAdditional path needed to access suborganization.
Power wait Number of seconds to wait after issuing a power off or power on command.
PortName of virtual machine.
fence_cisco_ucs The fence agent for Cisco UCS.
Table B.7. Dell DRAC
FieldDescription
NameThe name assigned to the DRAC.
IP AddressThe IP address assigned to the DRAC.
LoginThe login name used to access the DRAC.
PasswordThe 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) (Red Hat Enterprise Linux 5.4 and later) Indicates that system will use SSH to access the device.
Power wait Number of seconds to wait after issuing a power off or power on command.
fence_drac The fence agent for Dell Remote Access Card (DRAC).
Table B.8. Egenera SAN Controller
FieldDescription
NameA name for the BladeFrame device connected to the cluster.
CServerThe 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)
lpanThe logical process area network (LPAN) of the device.
pserverThe processing blade (pserver) name of the device.
fence_egenera The fence agent for the Egenera BladeFrame.
Table B.9. Fujitsu Siemens Remoteview Service Board (RSB)
FieldDescription
NameA name for the RSB to use as a fence device.
HostnameThe hostname assigned to the device.
LoginThe login name used to access the device.
PasswordThe 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.
fence_rsb The fence agent for Fujitsu-Siemens RSB.
Table B.10. GNBD (Global Network Block Device)
FieldDescription
NameA 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.
Servers 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 whitespace.
IP AddressThe cluster name of the node to be fenced. Refer to the fence_gnbd(8) man page for more information.
fence_gnbd The fence agent for GNBD-based GFS clusters.
Table B.11. HP iLO (Integrated Lights Out)
FieldDescription
NameA name for the server with HP iLO support.
HostnameThe hostname assigned to the device.
LoginThe login name used to access the device.
PasswordThe 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 SSL connections Use SSL connections to communicate with the device.
Power wait Number of seconds to wait after issuing a power off or power on command.
fence_ilo The fence agent for HP servers with the Integrated Light Out (iLO) PCI card.
Table B.12. HP iLO (Integrated Lights Out) MP (Red Hat Enterprise Linux 5.5 and later)
FieldDescription
NameA name for the server with HP iLO support.
HostnameThe hostname assigned to the device.
IP port (optional)TCP port to use for connection with the device.
LoginThe login name used to access the device.
PasswordThe 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 (Red Hat Enterprise Linux 5.4 and later) Indicates that system will use SSH to access the device.
Path to SSH identity file The identity file for SSH.
Force command prompt The command prompt to use. The default value is ’MP>’, ’hpiLO->’.
Power wait Number of seconds to wait after issuing a power off or power on command.
fence_ilo_mp The fence agent for HP iLO MP devices.
Table B.13. IBM Blade Center
FieldDescription
NameA name for the IBM BladeCenter device connected to the cluster.
IP AddressThe IP address assigned to the device.
LoginThe login name used to access the device.
PasswordThe 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.
Power wait Number of seconds to wait after issuing a power off or power on command.
BladeThe blade of the device.
Use SSH (Red Hat Enterprise Linux 5.4 and later) Indicates that system will use SSH to access the device.
fence_bladecenter The fence agent for IBM BladeCenter.
Table B.14. IBM iPDU (Red Hat Enterprise Linux 5.9 and later)
FieldDescription
NameA name for the IBM iPDU device connected to the cluster into which the fence daemon logs via the SNMP protocol.
IP AddressThe IP address or hostname assigned to the device.
UDP/TCP Port The UDP/TCP port to use for connection with the device; the default value is 161.
LoginThe login name used to access the device.
PasswordThe 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.
SNMP version The SNMP version to use (1, 2c, 3); the default value is 1.
SNMP community The SNMP community string; the default value is private.
SNMP security level The SNMP security level (noAuthNoPriv, authNoPriv, authPriv).
SNMP authentication protocol The SNMP authentication protocol (MD5, SHA).
SNMP privacy protocol The SNMP privacy protocol (DES, AES).
SNMP privacy protocol password The SNMP privacy protocol password.
SNMP privacy protocol script The script that supplies a password for SNMP privacy protocol. Using this supersedes the SNMP privacy protocol password parameter.
Power wait Number of seconds to wait after issuing a power off or power on command.
PortThe port.
fence_ipdu The fence agent for iPDU over SNMP.
Table B.15. IBM Remote Supervisor Adapter II (RSA II)
FieldDescription
NameA name for the RSA device connected to the cluster.
HostnameThe hostname assigned to the device.
LoginThe login name used to access the device.
PasswordThe 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.
Power wait Number of seconds to wait after issuing a power off or power on command.
fence_rsa The fence agent for the IBM RSA II management interface.
Table B.16. IF MIB (Red Hat Enterprise Linux 5.6 and later)
FieldDescription
NameA name for the IF MIB device connected to the cluster.
IP address or hostnameThe IP address or hostname assigned to the device.
UDP/TCP port (optional) The UDP/TCP port to use for connection with the device; the default value is 161.
LoginThe login name used to access the device.
PasswordThe 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.
SNMP version The SNMP version to use (1, 2c, 3); the default value is 1.
SNMP community The SNMP community string.
SNMP security level The SNMP security level (noAuthNoPriv, authNoPriv, authPriv).
SNMP authentication protocol The SNMP authentication protocol (MD5, SHA).
SNMP privacy protocol The SNMP privacy protocol (DES, AES).
SNMP privacy protocol password The SNMP privacy protocol password.
SNMP privacy protocol script The script that supplies a password for SNMP privacy protocol. Using this supersedes the SNMP privacy protocol password parameter.
Power wait Number of seconds to wait after issuing a power off or power on command.
PortPhysical plug number or name of virtual machine.
fence_ifmib The fence agent for IF-MIB devices.
Table B.17. IPMI (Intelligent Platform Management Interface) LAN
FieldDescription
NameA name for the IPMI LAN device connected to the cluster.
IP AddressThe IP address assigned to the IPMI port.
LoginThe login name of a user capable of issuing power on/off commands to the given IPMI port.
PasswordThe 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 Typenone, password, md2, or md5.
Privilege LevelThe privilege level on the IPMI device.
Use LanplusTrue or 1. If blank, then value is False.
fence_ipmilan The fence agent for machines controlled by IPMI.
Table B.18. Manual Fencing
FieldDescription
NameA 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.
Table B.19. McData SAN Switch
FieldDescription
NameA name for the McData device connected to the cluster.
IP AddressThe IP address assigned to the device.
LoginThe login name used to access the device.
PasswordThe 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.
PortThe switch outlet number.
fence_mcdata The fence agent for McData FC switches.
Table B.20. QLogic SANBox2 Switch
FieldDescription
NameA name for the SANBox2 device connected to the cluster.
IP AddressThe IP address assigned to the device.
LoginThe login name used to access the device.
PasswordThe 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.
Power wait Number of seconds to wait after issuing a power off or power on command.
PortThe switch outlet number.
fence_sanbox2 The fence agent for QLogic SANBox2 FC switches.
Table B.21. RHEV-M REST API (RHEL 5.8 and later against RHEV 3.0 and later)
FieldDescription
NameName of the RHEV-M REST API fencing device.
IP AddressThe IP address or hostname assigned to the device.
IP port (optional) The TCP port to use for connection with the device.
Login The login name used to access the device.
PasswordThe 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 SSL connections Use SSL connections to communicate with the device.
Power wait Number of seconds to wait after issuing a power off or power on command.
Port Physical plug number or name of virtual machine.
fence_rhevm The fence agent for RHEV-M REST API.
Table B.22. RPS-10 Power Switch (two-node clusters only)
FieldDescription
NameA name for the WTI RPS-10 power switch connected to the cluster.
Device NameThe device name of the device the switch is connected to on the controlling host (for example, /dev/ttys2).
PortThe switch outlet number.
fence_wti The fence agent for the WTI Network Power Switch.
Table B.23. SCSI Fencing
FieldDescription
NameA name for the SCSI fence device.
Node nameName of the node to be fenced. Refer to the fence_scsi(8) man page for more information.
fence_scsi The fence agent for SCSI persistent reservations.

Note

Use of SCSI persistent reservations as a fence method is supported with the following limitations:
  • As of Red Hat Enterprise Linux 5.5 and fully-updated releases of Red Hat Enterprise Linux 5.4, SCSI fencing can be used in a 2-node cluster; previous releases did not support this feature.
  • 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.
  • As of Red Hat Enterprise Linux 5.5 and fully-updated releases of Red Hat Enterprise Linux 5.4, SCSI fencing can be used in conjunction with qdisk; previous releases did not support this feature. You cannot use fence_scsi on the LUN where qdiskd resides; it must be a raw LUN or raw partition of a LUN.
Table B.24. Virtual Machine Fencing
FieldDescription
NameName of the virtual machine fencing device.
DomainUnique domain name of the guest to be fenced.
Table B.25. VMware (SOAP Interface) (Red Hat Enterprise Linux 5.7 and later)
FieldDescription
NameName of the virtual machine fencing device.
HostnameThe IP address or hostname assigned to the device.
IP port (optional) The TCP port to use for connection with the device.
Login The login name used to access the device.
PasswordThe 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 SSL connections Use SSL connections to communicate with the device.
Power wait Number of seconds to wait after issuing a power off or power on command.
Virtual machine name Name of virtual machine in inventory path format (e.g., /datacenter/vm/Discovered_virtual_machine/myMachine).
Virtual machine UUID The UUID of the virtual machine to fence.
fence_vmware_soap The fence agent for VMWare over SOAP API.
Table B.26. Vixel SAN Switch
FieldDescription
NameA name for the Vixel switch connected to the cluster.
IP AddressThe IP address assigned to the device.
PasswordThe 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.
PortThe switch outlet number.
fence_vixel The fence agent for Vixel switches.
Table B.27. WTI Power Switch
FieldDescription
NameA name for the WTI power switch connected to the cluster.
IP AddressThe IP address assigned to the device.
PasswordThe 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.
Power wait Number of seconds to wait after issuing a power off or power on command.
PortThe switch outlet number.
Use SSH (Red Hat Enterprise Linux 5.4 and later) Indicates that system will use SSH to access the device.
fence_wti The fence agent for the WTI network power switch.
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.

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.

© 2024 Red Hat, Inc.