Chapter 5. Fence Devices

This chapter documents the fence devices currently supported in Red Hat Enterprise Linux High-Availability Add-On.

Table 5.1, "Fence Device Summary" lists the fence devices, the fence device agents associated with the fence devices, and provides a reference to the table documenting the parameters for the fence devices.

Table 5.1. Fence Device Summary

Fence Device	Fence Agent	Reference to Parameter Description
APC Power Switch (telnet/SSH)	fence_apc	Section 5.2, "APC Power Switch over Telnet and SSH"
APC Power Switch (SNMP)	fence_apc_snmp	Section 5.1, "APC Power Switch over SNMP"
Brocade Fabric Switch	fence_brocade	Section 5.3, "Brocade Fabric Switch"
Cisco MDS	fence_cisco_mds	Section 5.4, "Cisco MDS"
Cisco UCS	fence_cisco_ucs	Section 5.5, "Cisco UCS"
Dell DRAC 5	fence_drac5	Section 5.6, "Dell Drac 5"
Egenera SAN Controller	fence_egenera	Section 5.7, "Eaton Network Power Switch"
Egenera SAN Controller	fence_egenera	Section 5.8, "Egenera BladeFrame"
ePowerSwitch	fence_eps	Section 5.9, "ePowerSwitch"
Fence virt	fence_virt	Section 5.10, "Fence Virt"
Fujitsu Siemens Remoteview Service Board (RSB)	fence_rsb	Section 5.11, "Fujitsu-Siemens RemoteView Service Board (RSB)"
HP BladeSystem	fence_hpblade	Section 5.12, "Hewlett-Packard BladeSystem"
HP iLO/iLO2 (Integrated Lights Out)	fence_ilo	Section 5.13, "Hewlett-Packard iLO"
HP iLO (Integrated Lights Out) MP	fence_ilo_mp	Section 5.14, "Hewlett-Packard iLO MP"
IBM BladeCenter	fence_bladecenter	Section 5.15, "IBM BladeCenter"
IBM BladeCenter SNMP	fence_ibmblade	Section 5.16, "IBM BladeCenter over SNMP"
IBM iPDU	fence_ipdu	Section 5.17, "IBM iPDU"
IF MIB	fence_ifmib	Section 5.18, "IF-MIB"
Intel Modular	fence_intelmodular	Section 5.19, "Intel Modular"
IPMI (Intelligent Platform Management Interface) LAN	fence_ipmilan	Section 5.20, "IPMI over LAN"
RHEV-M REST API	fence_rhevm	Section 5.21, "RHEV-M REST API"
SCSI Fencing	fence_scsi	Section 5.22, "SCSI Persistent Reservations"
VMware Fencing (SOAP Interface)	fence_vmware_soap	Section 5.23, "VMWare over SOAP API"
WTI Power Switch	fence_wti	Section 5.24, "WTI Power Switch"

5.1. APC Power Switch over SNMP

Table 5.2, "APC Power Switch over SNMP" lists the fence device parameters used by fence_apc_snmp, the fence agent for APC that logs into the SNP device via the SNMP protocol.

Table 5.2. APC Power Switch over SNMP

luci Field	`cluster.conf` Attribute	Description
Name	`name`	A name for the APC device connected to the cluster into which the fence daemon logs via the SNMP protocol.
IP Address or Hostname	`ipaddr`	The IP address or hostname assigned to the device.
UDP/TCP port	`udpport`	The UDP/TCP port to use for connection with the device; the default value is 161.
Login	`login`	The login name used to access the device.
Password	`passwd`	The password used to authenticate the connection to the device.
Password Script (optional)	`passwd_script`	The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
SNMP Version	`snmp_version`	The SNMP version to use (1, 2c, 3); the default value is 1.
SNMP Community	`community`	The SNMP community string; the default value is `private`.
SNMP Security Level	`snmp_sec_level`	The SNMP security level (noAuthNoPriv, authNoPriv, authPriv).
SNMP Authentication Protocol	`snmp_auth_prot`	The SNMP authentication protocol (MD5, SHA).
SNMP Privacy Protocol	`snmp_priv_prot`	The SNMP privacy protocol (DES, AES).
SNMP Privacy Protocol Password	`snmp_priv_passwd`	The SNMP privacy protocol password.
SNMP Privacy Protocol Script	`snmp_priv_passwd_script`	The script that supplies a password for SNMP privacy protocol. Using this supersedes the SNMP privacy protocol password parameter.
Power Wait	`power_wait`	Number of seconds to wait after issuing a power off or power on command.
Port (Outlet) Number	`port`	The port.

Figure 5.1, "APC Power Switch over SNMP" shows the configuration screen for adding an APC Power Switch fence device.

The APC Power Switch over SNMP fence device configuration page.

Figure 5.1. APC Power Switch over SNMP

The following is the cluster.conf entry for the fence_apc_snmp device:

 <fencedevice>  <fencedevice agent="fence_apc_snmp" community="private" ipaddr="192.168.0.1" login="root" \ name="apcpwsnmptst1" passwd="password123" power_wait="60" snmp_priv_passwd="password123"/> </fencedevices>

5.2. APC Power Switch over Telnet and SSH

Table 5.3, "APC Power Switch (telnet/SSH)" lists the fence device parameters used by fence_apc, the fence agent for APC over telnet/SSH.

Table 5.3. APC Power Switch (telnet/SSH)

luci Field	`cluster.conf` Attribute	Description
Name	`name`	A name for the APC device connected to the cluster into which the fence daemon logs via telnet/ssh.
IP Address or Hostname	`ipaddr`	The IP address or hostname assigned to the device.
IP Port (optional)	`ipport`	The TCP port to use to connect to the device..
Login	`login`	The login name used to access the device.
Password	`passwd`	The password used to authenticate the connection to the device.
Password Script (optional)	`passwd_script`	The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
Power wait	`power_wait`	Number of seconds to wait after issuing a power off or power on command.
Port	`port`	The port.
Switch (optional)	`switch`	The switch number for the APC switch that connects to the node when you have multiple daisy-chained switches.
Use SSH	`secure`	Indicates that system will use SSH to access the device.
Path to SSH Identity File	`identity_file`	The identity file for SSH.

Figure 5.2, "APC Power Switch" shows the configuration screen for adding an APC Power Switch fence device.

The APC Power Switch fence device configuration page.

Figure 5.2. APC Power Switch

The following command creates a fence device instance for a APC device:

ccs -f cluster.conf --addfencedev apc agent=fence_apc ipaddr=192.168.0.1 login=root passwd=password123

The following is the cluster.conf entry for the fence_apc device:

 <fencedevices>   <fencedevice agent="fence_apc" name="apc" ipaddr="apc-telnet.example.com" login="root" passwd="password123"/> </fencedevices>

5.3. Brocade Fabric Switch

Table 5.4, "Brocade Fabric Switch" lists the fence device parameters used by fence_brocade, the fence agent for Brocade FC switches.

Table 5.4. Brocade Fabric Switch

luci Field	`cluster.conf` Attribute	Description
Name	`name`	A name for the Brocade device connected to the cluster.
IP Address or Hostname	`ipaddr`	The IP address assigned to the device.
Login	`login`	The login name used to access the device.
Password	`passwd`	The password used to authenticate the connection to the device.
Password Script (optional)	`passwd_script`	The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
Port	`port`	The switch outlet number.

Figure 5.3, "Brocade Fabric Switch" shows the configuration screen for adding an Brocade Fabric Switch fence device.

The Brocade Fabric Switch fence device configuration page.

Figure 5.3. Brocade Fabric Switch

The following command creates a fence device instance for a Brocade device:

ccs -f cluster.conf --addfencedev brocadetest agent=fence_brocade ipaddr=brocadetest.example.com login=root \ passwd=password123

The following is the cluster.conf entry for the fence_brocade device:

 <fencedevices>  <fencedevice agent="fence_brocade" ipaddr="brocadetest.example.com" login="brocadetest" \ name="brocadetest" passwd="brocadetest"/> </fencedevices>

5.4. Cisco MDS

Table 5.5, "Cisco MDS" lists the fence device parameters used by fence_cisco_mds, the fence agent for Cisco MDS.

Table 5.5. Cisco MDS

luci Field	`cluster.conf` Attribute	Description
Name	`name`	A name for the Cisco MDS 9000 series device with SNMP enabled.
IP Address or Hostname	`ipaddr`	The IP address or hostname assigned to the device.
UDP/TCP port	`udpport`	The UDP/TCP port to use for connection with the device; the default value is 161.
Login	`login`	The login name used to access the device.
Password	`passwd`	The password used to authenticate the connection to the device.
Password Script (optional)	`passwd_script`	The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
Port (Outlet) Number	`port`	The port.
SNMP Version	`snmp_version`	The SNMP version to use (1, 2c, 3).
SNMP Community	`community`	The SNMP community string.
SNMP Security Level	`snmp_sec_level`	The SNMP security level (noAuthNoPriv, authNoPriv, authPriv).
SNMP Authentication Protocol	`snmp_auth_prot`	The SNMP authentication protocol (MD5, SHA).
SNMP Privacy Protocol	`snmp_priv_prot`	The SNMP privacy protocol (DES, AES).
SNMP Privacy Protocol Password	`snmp_priv_passwd`	The SNMP privacy protocol password.
SNMP Privacy Protocol Script	`snmp_priv_passwd_script`	The script that supplies a password for SNMP privacy protocol. Using this supersedes the SNMP privacy protocol password parameter.
Power Wait	`power_wait`	Number of seconds to wait after issuing a power off or power on command.

Figure 5.4, "Cisco MDS" shows the configuration screen for adding an Cisco MDS fence device.

The Cisco MDS fence device configuration page.

Figure 5.4. Cisco MDS

The following command creates a fence device instance for a Cisco MDS device:

ccs -f cluster.conf --addfencedev mds agent=fence_cisco_mds ipaddr=192.168.0.1 name=ciscomdstest1 login=root \ passwd=password123 power_wait=60 snmp_priv_passwd=password123 udpport=161

The following is the cluster.conf entry for the fence_cisco_mds device:

 <fencedevices>   <fencedevice agent="fence_cisco_mds" community="private" ipaddr="192.168.0.1" login="root" \ name="ciscomdstest1" passwd="password123" power_wait="60" snmp_priv_passwd="password123" \ udpport="161"/> </fencedevices>

5.5. Cisco UCS

Table 5.6, "Cisco UCS" lists the fence device parameters used by fence_cisco_ucs, the fence agent for Cisco UCS.

Table 5.6. Cisco UCS

luci Field	`cluster.conf` Attribute	Description
Name	`name`	A name for the Cisco UCS device.
IP Address or Hostname	`ipaddr`	The IP address or hostname assigned to the device.
IP port (optional)	`ipport`	The TCP port to use to connect to the device.
Login	`login`	The login name used to access the device.
Password	`passwd`	The password used to authenticate the connection to the device.
Password Script (optional)	`passwd_script`	The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
Use SSL	`ssl`	Use SSL connections to communicate with the device.
Sub-Organization	`suborg`	Additional path needed to access suborganization.
Port (Outlet) Number	`port`	Name of virtual machine.
Power Wait	`power_wait`	Number of seconds to wait after issuing a power off or power on command.

Figure 5.5, "Cisco UCS" shows the configuration screen for adding a Cisco UCS fence device.

The Cisco UCS fence device configuration page.

Figure 5.5. Cisco UCS

The following command creates a fence device instance for a Cisco UCS device:

ccs -f cluster.conf --addfencedev ucs agent=fence_cisco_ucs ipaddr=192.168.0.1 login=root passwd=password123 \ suborg=/org-RHEL/org-Fence/

The following is an example cluster.conf entry for the fence_cisco_ucs device as created using either Conga or ccs:

 <fencedevices>  <fencedevice agent="fence_cisco_ucs" ipaddr="192.168.0.1" login="root" name="ciscoucstest1" \ passwd="password123" power_wait="60" ssl="on" suborg="/org-RHEL/org-Fence/"/> </fencedevices>

5.6. Dell Drac 5

Table 5.7, "Dell DRAC 5" lists the fence device parameters used by fence_drac5, the fence agent for Dell DRAC 5.

Table 5.7. Dell DRAC 5

luci Field	`cluster.conf` Attribute	Description
Name	`name`	The name assigned to the DRAC.
IP Address or Hostname	`ipaddr`	The IP address or hostname assigned to the DRAC.
IP Port (optional)	`ipport`	The TCP port to use to connect to the device.
Login	`login`	The login name used to access the DRAC.
Password	`passwd`	The password used to authenticate the connection to the DRAC.
Password Script (optional)	`passwd_script`	The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
Use SSH	`secure`	Indicates that the system will use SSH to access the device.
Path to SSH Identity File	`identity file`	The identity file for SSH.
Module Name	`module_name`	(optional) The module name for the DRAC when you have multiple DRAC modules.
Force Command Prompt	`cmd_prompt`	The command prompt to use. The default value is '\$'.
Power Wait	`power_wait`	Number of seconds to wait after issuing a power off or power on command.

Figure 5.6, "Dell Drac 5" shows the configuration screen for adding a Dell Drac 5 device

The Dell Drac 5 fence device configuration page.

Figure 5.6. Dell Drac 5

The following command creates a fence device instance for a Dell Drac 5 device:

ccs -f cluster.conf --addfencedev delldrac5test1 agent=fence_drac5 ipaddr=192.168.0.1 login=root passwd=password123\ module_name=drac1 power_wait=60

The following is the cluster.conf entry for the fence_drac5 device:

 <fencedevices>   <fencedevice agent="fence_drac5" cmd_prompt="\$" ipaddr="192.168.0.1" login="root" module_name="drac1" \ name="delldrac5test1" passwd="password123" power_wait="60"/> </fencedevices>

5.7. Eaton Network Power Switch

Table 5.8, "Eaton Network Power Controller (SNMP Interface) (Red Hat Enterprise Linux 6.4 and later)" lists the fence device parameters used by fence_eaton_snmp, the fence agent for the Eaton over SNMP network power switch.

Table 5.8. Eaton Network Power Controller (SNMP Interface) (Red Hat Enterprise Linux 6.4 and later)

luci Field	`cluster.conf` Attribute	Description
Name	`name`	A name for the Eaton network power switch connected to the cluster.
IP Address or Hostname	`ipaddr`	The IP address or hostname assigned to the device.
UDP/TCP Port (optional)	`udpport`	The UDP/TCP port to use for connection with the device; the default value is 161.
Login	`login`	The login name used to access the device.
Password	`passwd`	The password used to authenticate the connection to the device.
Password Script (optional)	`passwd_script`	The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
SNMP Version	`snmp_version`	The SNMP version to use (1, 2c, 3); the default value is 1.
SNMP Community	`community`	The SNMP community string; the default value is `private`.
SNMP Security Level	`snmp_sec_level`	The SNMP security level (noAuthNoPriv, authNoPriv, authPriv).
SNMP Authentication Protocol	`snmp_auth_prot`	The SNMP authentication protocol (MD5, SHA).
SNMP Privacy Protocol	`snmp_priv_prot`	The SNMP privacy protocol (DES, AES).
SNMP Privacy Protocol Password	`snmp_priv_passwd`	The SNMP privacy protocol password.
SNMP Privacy Protocol Script	`snmp_priv_passwd_script`	The script that supplies a password for SNMP privacy protocol. Using this supersedes the SNMP privacy protocol password parameter.
Power wait (seconds)	`power_wait`	Number of seconds to wait after issuing a power off or power on command.
Port (Outlet) Number	`port`	Physical plug number or name of virtual machine. This parameter is always required.

Figure 5.7, "Eaton Network Power Switch" shows the configuration screen for adding an Eaton Network Power Switch fence device.

The Eaton Network Power Switch fence device configuration page.

Figure 5.7. Eaton Network Power Switch

The following command creates a fence device instance for an Eaton Network Power Switch device:

ccs -f cluster.conf --addfencedev eatontest agent=fence_eaton_snmp ipaddr=192.168.0.1 login=root \ passwd=password123 power_wait=60 snmp_priv_passwd=eatonpassword123 udpport=161

The following is the cluster.conf entry for the fence_eaton_snmp device:

 <fencedevices>  <fencedevice agent="fence_eaton_snmp" community="private" ipaddr="eatonhost" login="eatonlogin" \   name="eatontest" passwd="password123" passwd_script="eatonpwscr" power_wait="3333" \   snmp_priv_passwd="eatonprivprotpass" snmp_priv_passwd_script="eatonprivprotpwscr" udpport="161"/> </fencedevices>

5.8. Egenera BladeFrame

Table 5.9, "Egenera SAN Controller" lists the fence device parameters used by fence_egenera, the fence agent for the Egenera BladeFrame.

Table 5.9. Egenera SAN Controller

luci Field	`cluster.conf` Attribute	Description
Name	`name`	A name for the Egenera BladeFrame device connected to the cluster.
CServer	`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)	`esh`	The path to the esh command on the cserver (default is /opt/panmgr/bin/esh)
Username	`user`	The login name. The default value is `root`.
lpan	`lpan`	The logical process area network (LPAN) of the device.
pserver	`pserver`	The processing blade (pserver) name of the device.

Figure 5.8, "Egenera BladeFrame" shows the configuration screen for adding an Egenera BladeFrame fence device.

The Egenera BladeFrame fence device configuration page.

Figure 5.8. Egenera BladeFrame

The following command creates a fence device instance for an Egenera BladeFrame device:

ccs -f cluster.conf --addfencedev egeneratest agent=fence_egenera user=root cserver=cservertest

The following is the cluster.conf entry for the fence_egenera device:

 <fencedevices>  <fencedevice agent="fence_egenera" cserver="cservertest" name="egeneratest" user="root"/> </fencedevices>

5.9. ePowerSwitch

Table 5.10, "ePowerSwitch" lists the fence device parameters used by fence_eps, the fence agent for ePowerSwitch.

Table 5.10. ePowerSwitch

luci Field	`cluster.conf` Attribute	Description
Name	`name`	A name for the ePowerSwitch device connected to the cluster.
IP Address or Hostname	`ipaddr`	The IP address or hostname assigned to the device.
Login	`login`	The login name used to access the device.
Password	`passwd`	The password used to authenticate the connection to the device.
Password Script (optional)	`passwd_script`	The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
Name of Hidden Page	`hidden_page`	The name of the hidden page for the device.
Port (Outlet) Number	`port`	Physical plug number or name of virtual machine.

Figure 5.9, "ePowerSwitch" shows the configuration screen for adding an ePowerSwitch fence device.

The ePowerSwitch fence device configuration page.

Figure 5.9. ePowerSwitch

The following command creates a fence device instance for an ePowerSwitch device:

ccs -f cluster.conf --addfencedev epstest1 agent=fence_eps ipaddr=192.168.0.1 login=root passwd=password123 \ hidden_page=hidden.htm

The following is the cluster.conf entry for the fence_eps device:

 <fencedevices>   <fencedevice agent="fence_eps" hidden_page="hidden.htm" ipaddr="192.168.0.1" login="root" name="epstest1" \ passwd="password123"/> </fencedevices>

5.10. Fence Virt

Table 5.11, "Fence virt" lists the fence device parameters used by fence_virt, the fence agent for a Fence virt fence device.

Table 5.11. Fence virt

luci Field	`cluster.conf` Attribute	Description
Name	`name`	A name for the Fence virt fence device.
Serial Device	`serial_device`	On the host, the serial device must be mapped in each domain's configuration file. For more information, see the `fence_virt.conf` man page. If this field is specified, it causes the `fence_virt` fencing agent to operate in serial mode. Not specifying a value causes the `fence_virt` fencing agent to operate in VM channel mode.
Serial Parameters	`serial_params`	The serial parameters. The default is 115200, 8N1.
VM Channel IP Address	`channel_address`	The channel IP. The default value is 10.0.2.179.
Port or Domain (deprecated)	`port`	Virtual machine (domain UUID or name) to fence.
	`ipport`	The channel port. The default value is 1229, which is the value used when configuring this fence device with luci.

Figure 5.10, "Fence Virt" shows the configuration screen for adding a Fence Virt device.

The Fence Virt fence device configuration page.

Figure 5.10. Fence Virt

The following command creates a fence device instance for the Fence Virt device:

ccs -f cluster.conf --addfencedev fencevirt1 agent=fence_virt serial_device=/dev/ttyS1 serial_params=19200, 8N1

The following is the cluster.conf entry for the fence_virt device:

 <fencedevices>   <fencedevice agent="fence_virt" name="fencevirt1" serial_device="/dev/ttyS1" serial_params="19200, 8N1"/> </fencedevices>

5.11. Fujitsu-Siemens RemoteView Service Board (RSB)

Table 5.12, "Fujitsu Siemens RemoteView Service Board (RSB)" lists the fence device parameters used by fence_rsb, the fence agent for Fujitsu-Siemens RemoteView Service Board (RSB).

Table 5.12. Fujitsu Siemens RemoteView Service Board (RSB)

luci Field	`cluster.conf` Attribute	Description
Name	`name`	A name for the RSB to use as a fence device.
IP Address or Hostname	`ipaddr`	The hostname assigned to the device.
Login	`login`	The login name used to access the device.
Password	`passwd`	The password used to authenticate the connection to the device.
Password Script (optional)	`passwd_script`	The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
TCP Port	`ipport`	The port number on which the telnet service listens. The default value is 3172.

Figure 5.11, "Fujitsu-Siemens RSB" shows the configuration screen for adding an Fujitsu-Siemens RSB fence device.

The Fujitsu-Siemens RSB fence device configuration page.

Figure 5.11. Fujitsu-Siemens RSB

The following command creates a fence device instance for a Fujiitsu-Siemens RSB device:

ccs -f cluster.conf --addfencedev fsrbtest1 agent=fence_rsb ipaddr=192.168.0.1 login=root passwd=password123 \ telnet_port=3172

The following is the cluster.conf entry for the fence_rsb device:

 <fencedevices>   <fencedevice agent="fence_rsb" ipaddr="192.168.0.1" login="root" name="fsrsbtest1" passwd="password123" telnet_port="3172"/> </fencedevices>

5.12. Hewlett-Packard BladeSystem

Table 5.13, "HP BladeSystem (Red Hat Enterprise Linux 6.4 and later)" lists the fence device parameters used by fence_hpblade, the fence agent for HP BladeSystem.

Table 5.13. HP BladeSystem (Red Hat Enterprise Linux 6.4 and later)

luci Field	`cluster.conf` Attribute	Description
Name	`name`	The name assigned to the HP Bladesystem device connected to the cluster.
IP Address or Hostname	`ipaddr`	The IP address or hostname assigned to the HP BladeSystem device.
IP Port (optional)	`ipport`	The TCP port to use to connect to the device.
Login	`login`	The login name used to access the HP BladeSystem device. This parameter is required.
Password	`passwd`	The password used to authenticate the connection to the fence device.
Password Script (optional)	`passwd_script`	The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
Force Command Prompt	`cmd_prompt`	The command prompt to use. The default value is '/$'.
Missing port returns OFF instead of failure	`missing_as_off`	Missing port returns OFF instead of failure.
Power Wait (seconds)	`power_wait`	Number of seconds to wait after issuing a power off or power on command.
Use SSH	`secure`	Indicates that the system will use SSH to access the device.
Path to SSH Identity File	`identity_file`	The identity file for SSH.

Figure 5.12, "HP BladeSystem" shows the configuration screen for adding an HP BladeSystem fence device.

The HP BladeSystem fence device configuration page.

Figure 5.12. HP BladeSystem

The following command creates a fence device instance for a BladeSystem device:

ccs -f cluster.conf --addfencedev hpbladetest1 agent=fence_hpblade cmd_prompt=c7000oa> ipaddr=192.168.0.1 \ login=root passwd=password123 missing_as_off=on power_wait=60

The following is the cluster.conf entry for the fence_hpblade device:

 <fencedevices>  <fencedevice agent="fence_hpblade" cmd_prompt="c7000oa>" ipaddr="hpbladeaddr" ipport="13456" \   login="root" missing_as_off="on" name="hpbladetest1" passwd="password123" passwd_script="hpbladepwscr" \   power_wait="60"/> </fencedevices>

5.13. Hewlett-Packard iLO

Table 5.14, "HP iLO/iLO2 (Integrated Lights Out)" lists the fence device parameters used by fence_ilo, the fence agent for HP iLO devices.

Table 5.14. HP iLO/iLO2 (Integrated Lights Out)

luci Field	`cluster.conf` Attribute	Description
Name	`name`	A name for the server with HP iLO support.
IP Address or Hostname	`ipaddr`	The IP address or hostname assigned to the device.
IP Port (optional)	`ipport`	TCP port to use for connection with the device.
Login	`login`	The login name used to access the device.
Password	`passwd`	The password used to authenticate the connection to the device.
Password Script (optional)	`passwd_script`	The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
Power Wait	`power_wait`	Number of seconds to wait after issuing a power off or power on command.

Figure 5.13, "HP iLO" shows the configuration screen for adding an HP iLO fence device.

The HP iLO fence device configuration page.

Figure 5.13. HP iLO

The following command creates a fence device instance for a HP iLO device:

ccs -f cluster.conf --addfencedev hpilotest1 agent=fence_hpilo ipaddr=192.168.0.1 login=root passwd=password123 \ power_wait=60

The following is the cluster.conf entry for the fence_ilo device:

 <fencedevices>  <fencedevice agent="fence_ilo" ipaddr="192.168.0.1" login="root" name="hpilotest1" passwd="password123" \   power_wait="60"/> </fencedevices>

5.14. Hewlett-Packard iLO MP

Table 5.15, "HP iLO (Integrated Lights Out) MP" lists the fence device parameters used by fence_ilo_mp, the fence agent for HP iLO MP devices.

Table 5.15. HP iLO (Integrated Lights Out) MP

luci Field	`cluster.conf` Attribute	Description
Name	`name`	A name for the server with HP iLO support.
IP Address or Hostname	`ipaddr`	The IP address or hostname assigned to the device.
IP Port (optional)	`ipport`	TCP port to use for connection with the device.
Login	`login`	The login name used to access the device.
Password	`passwd`	The password used to authenticate the connection to the device.
Password Script (optional)	`passwd_script`	The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
Use SSH	`secure`	Indicates that the system will use SSH to access the device.
Path to SSH Identity File	`identity_file`	The Identity file for SSH.
Force Command Prompt	`cmd_prompt`	The command prompt to use. The default value is MP>, hpiLO->.
Power Wait	`power_wait`	Number of seconds to wait after issuing a power off or power on command.

Figure 5.14, "HP iLO MP" shows the configuration screen for adding an HP iLO MPfence device.

The HP iLO MP fence device configuration page.

Figure 5.14. HP iLO MP

The following command creates a fence device instance for a HP iLO MP device:

ccs -f cluster.conf --addfencedev hpilomptest1 agent=fence_hpilo cmd_prompt=hpiLO-> ipaddr=192.168.0.1 \ login=root passwd=password123 power_wait=60

The following is the cluster.conf entry for the fence_hpilo_mp device:

 <fencedevices><fencedevice agent="fence_ilo_mp" cmd_prompt="hpiLO->" ipaddr="192.168.0.1" login="root" name="hpilomptest1" passwd="password123" power_wait="60"/> </fencedevices>

5.15. IBM BladeCenter

Table 5.16, "IBM BladeCenter" lists the fence device parameters used by fence_bladecenter, the fence agent for IBM BladeCenter.

Table 5.16. IBM BladeCenter

luci Field	`cluster.conf` Attribute	Description
Name	`name`	A name for the IBM BladeCenter device connected to the cluster.
IP Address or Hostname	`ipaddr`	The IP address or hostname assigned to the device.
IP port (optional)	`ipport`	TCP port to use for connection with the device.
Login	`login`	The login name used to access the device.
Password	`passwd`	The password used to authenticate the connection to the device.
Password Script (optional)	`passwd_script`	The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
Power Wait	`power_wait`	Number of seconds to wait after issuing a power off or power on command.
Use SSH	`secure`	Indicates that system will use SSH to access the device.
Path to SSH Identity File	`identity_file`	The identity file for SSH.

Figure 5.15, "IBM BladeCenter" shows the configuration screen for adding an IBM BladeCenter fence device.

The IBM BladeCenter fence device configuration page.

Figure 5.15. IBM BladeCenter

The following command creates a fence device instance for an IBM BladeCenter device:

ccs -f cluster.conf --addfencedev bladecentertest1 agent=fence_bladecenter ipaddr=192.168.0.1 login=root \ passwd=password123 power_wait=60

The following is the cluster.conf entry for the fence_bladecenter device:

 <fencedevices>  <fencedevice agent="fence_bladecenter" ipaddr="192.168.0.1" login="root" name="bladecentertest1" passwd="password123" \   power_wait="60"/> </fencedevices>

5.16. IBM BladeCenter over SNMP

Table 5.17, "IBM BladeCenter SNMP" lists the fence device parameters used by fence_ibmblade, the fence agent for IBM BladeCenter over SNMP.

Table 5.17. IBM BladeCenter SNMP

luci Field	`cluster.conf` Attribute	Description
Name	`name`	A name for the IBM BladeCenter SNMP device connected to the cluster.
IP Address or Hostname	`ipaddr`	The IP address or hostname assigned to the device.
UDP/TCP Port (optional)	`udpport`	UDP/TCP port to use for connections with the device; the default value is 161.
Login	`login`	The login name used to access the device.
Password	`passwd`	The password used to authenticate the connection to the device.
Password Script (optional)	`passwd_script`	The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
SNMP Version	`snmp_version`	The SNMP version to use (1, 2c, 3); the default value is 1.
SNMP Community	`community`	The SNMP community string.
SNMP Security Level	`snmp_sec_level`	The SNMP security level (noAuthNoPriv, authNoPriv, authPriv).
SNMP Authentication Protocol	`snmp_auth_prot`	The SNMP authentication protocol (MD5, SHA).
SNMP Privacy Protocol	`snmp_priv_prot`	The SNMP privacy protocol (DES, AES).
SNMP privacy protocol password	`snmp_priv_passwd`	The SNMP Privacy Protocol Password.
SNMP Privacy Protocol Script	`snmp_priv_passwd_script`	The script that supplies a password for SNMP privacy protocol. Using this supersedes the SNMP privacy protocol password parameter.
Power Wait	`power_wait`	Number of seconds to wait after issuing a power off or power on command.
Port	`port`	Physical plug number or name of virtual machine.

Figure 5.16, "IBM BladeCenter SNMP" shows the configuration screen for adding an IBM BladeCenter SNMP fence device.

The IBM BladeCenter SNMP fence device configuration page.

Figure 5.16. IBM BladeCenter SNMP

The following command creates a fence device instance for an IBM BladeCenter SNMP device:

ccs -f cluster.conf --addfencedev bladesnmp1 agent=fence_ibmblade community=private ipaddr=192.168.0.1 login=root \ passwd=password123 snmp_priv_passwd=snmpasswd123 power_wait=60

The following is the cluster.conf entry for the fence_ibmblade device:

 <fencedevices>  <fencedevice agent="fence_ibmblade" community="private" ipaddr="192.168.0.1" login="root" name="bladesnmp1" \   passwd="password123" power_wait="60" snmp_priv_passwd="snmpasswd123" udpport="161"/> </fencedevices>

5.17. IBM iPDU

Table 5.18, "IBM iPDU (Red Hat Enterprise Linux 6.4 and later)" lists the fence device parameters used by fence_ipdu, the fence agent for iPDU over SNMP devices.

Table 5.18. IBM iPDU (Red Hat Enterprise Linux 6.4 and later)

luci Field	`cluster.conf` Attribute	Description
Name	`name`	A name for the IBM iPDU device connected to the cluster into which the fence daemon logs via the SNMP protocol.
IP Address or Hostname	`ipaddr`	The IP address or hostname assigned to the device.
UDP/TCP Port	`udpport`	The UDP/TCP port to use for connection with the device; the default value is 161.
Login	`login`	The login name used to access the device.
Password	`passwd`	The password used to authenticate the connection to the device.
Password Script (optional)	`passwd_script`	The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
SNMP Version	`snmp_version`	The SNMP version to use (1, 2c, 3); the default value is 1.
SNMP Community	`community`	The SNMP community string; the default value is `private`.
SNMP Security Level	`snmp_sec_level`	The SNMP security level (noAuthNoPriv, authNoPriv, authPriv).
SNMP Authentication Protocol	`snmp_auth_prot`	The SNMP Authentication Protocol (MD5, SHA).
SNMP Privacy Protocol	`snmp_priv_prot`	The SNMP privacy protocol (DES, AES).
SNMP Privacy Protocol Password	`snmp_priv_passwd`	The SNMP privacy protocol password.
SNMP Privacy Protocol Script	`snmp_priv_passwd_script`	The script that supplies a password for SNMP privacy protocol. Using this supersedes the SNMP privacy protocol password parameter.
Power Wait	`power_wait`	Number of seconds to wait after issuing a power off or power on command.
Port	`port`	The port.

Figure 5.17, "IBM iPDU" shows the configuration screen for adding an IBM iPDU fence device.

The IBM iPDU fence device configuration page.

Figure 5.17. IBM iPDU

The following command creates a fence device instance for an IBM iPDU device:

ccs -f cluster.conf --addfencedev ipdutest1 agent=fence_ipdu community=ipdusnmpcom ipaddr=192.168.0.1 login=root \ passwd=password123 snmp_priv_passwd=snmpasswd123 power_wait=60 snmp_priv_prot=AES udpport=111

The following is the cluster.conf entry for the fence_ipdu device:

 <fencedevices>  <fencedevice agent="fence_ipdu" community="ipdusnmpcom" ipaddr="ipduhost" login="root" name="ipdutest1" \   passwd="password123" power_wait="60" snmp_priv_passwd="ipduprivprotpasswd" snmp_priv_prot="AES" \   udpport="111"/> </fencedevices>

5.18. IF-MIB

Table 5.19, "IF MIB" lists the fence device parameters used by fence_ifmib, the fence agent for IF-MIB devices.

Table 5.19. IF MIB

luci Field	`cluster.conf` Attribute	Description
Name	`name`	A name for the IF MIB device connected to the cluster.
IP Address or Hostname	`ipaddr`	The IP address or hostname assigned to the device.
UDP/TCP Port (optional)	`udpport`	The UDP/TCP port to use for connection with the device; the default value is 161.
Login	`login`	The login name used to access the device.
Password	`passwd`	The password used to authenticate the connection to the device.
Password Script (optional)	`passwd_script`	The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
SNMP Version	`snmp_version`	The SNMP version to use (1, 2c, 3); the default value is 1.
SNMP Community	`community`	The SNMP community string.
SNMP Security Level	`snmp_sec_level`	The SNMP security level (noAuthNoPriv, authNoPriv, authPriv).
SNMP Authentication Protocol	`snmp_auth_prot`	The SNMP authentication protocol (MD5, SHA).
SNMP Privacy Protocol	`snmp_priv_prot`	The SNMP privacy protocol (DES, AES).
SNMP Privacy Protocol Password	`snmp_priv_passwd`	The SNMP privacy protocol password.
SNMP Privacy Protocol Script	`snmp_priv_passwd_script`	The script that supplies a password for SNMP privacy protocol. Using this supersedes the SNMP privacy protocol password parameter.
Power Wait	`power_wait`	Number of seconds to wait after issuing a power off or power on command.
Port	`port`	Physical plug number or name of virtual machine.

Figure 5.18, "IF-MIB" shows the configuration screen for adding an IF-MIB fence device.

The IF-MIB fence device configuration page.

Figure 5.18. IF-MIB

The following command creates a fence device instance for an IF-MIB device:

ccs -f cluster.conf --addfencedev ifmib1 agent=fence_ifmib community=private ipaddr=192.168.0.1 login=root \ passwd=password123 snmp_priv_passwd=snmpasswd123 power_wait=60 udpport=161

The following is the cluster.conf entry for the fence_ifmib device:

 <fencedevices>  <fencedevice agent="fence_ifmib" community="private" ipaddr="192.168.0.1" login="root" name="ifmib1" \   passwd="password123" power_wait="60" snmp_priv_passwd="snmpasswd123" udpport="161"/> </fencedevices>

5.19. Intel Modular

Table 5.20, "Intel Modular" lists the fence device parameters used by fence_intelmodular, the fence agent for Intel Modular.

Table 5.20. Intel Modular

luci Field	`cluster.conf` Attribute	Description
Name	`name`	A name for the Intel Modular device connected to the cluster.
IP Address or Hostname	`ipaddr`	The IP address or hostname assigned to the device.
Login	`login`	The login name used to access the device.
Password	`passwd`	The password used to authenticate the connection to the device.
Password Script (optional)	`passwd_script`	The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
SNMP Version	`snmp_version`	The SNMP version to use (1, 2c, 3); the default value is 1.
SNMP Community	`community`	The SNMP community string; the default value is `private`.
SNMP Security Level	`snmp_sec_level`	The SNMP security level (noAuthNoPriv, authNoPriv, authPriv).
SNMP Authentication Protocol	`snmp_auth_prot`	The SNMP authentication protocol (MD5, SHA).
SNMP Privacy Protocol	`snmp_priv_prot`	The SNMP privacy protocol (DES, AES).
SNMP Privacy Protocol Password	`snmp_priv_passwd`	The SNMP privacy protocol password.
SNMP Privacy Protocol Script	`snmp_priv_passwd_script`	The script that supplies a password for SNMP privacy protocol. Using this supersedes the SNMP privacy protocol password parameter.
Power Wait	`power_wait`	Number of seconds to wait after issuing a power off or power on command.
Port	`port`	Physical plug number or name of virtual machine.

Figure 5.19, "Intel Modular" shows the configuration screen for adding an Intel Modular fence device.

The Intel Modular fence device configuration page.

Figure 5.19. Intel Modular

The following command creates a fence device instance for an Intel Modular device:

ccs -f cluster.conf --addfencedev intelmodular1 agent=fence_intelmodular community=private ipaddr=192.168.0.1 login=root \ passwd=password123 snmp_priv_passwd=snmpasswd123 power_wait=60 udpport=161

The following is the cluster.conf entry for the fence_intelmodular device:

 <fencedevices>  <fencedevice agent="fence_intelmodular" community="private" ipaddr="192.168.0.1" login="root" name="intelmodular1" \   passwd="password123" power_wait="60" snmp_priv_passwd="snmpasswd123" udpport="161"/> </fencedevices>

5.20. IPMI over LAN

Table 5.21, "IPMI (Intelligent Platform Management Interface) LAN" lists the fence device parameters used by fence_ipmilan, the fence agent for IPMI over LAN.

Table 5.21. IPMI (Intelligent Platform Management Interface) LAN

luci Field	`cluster.conf` Attribute	Description
Name	`name`	A name for the IPMI LAN device connected to the cluster.
IP Address or Hostname	`ipaddr`	The IP address or hostname assigned to the device.
Login	`login`	The login name of a user capable of issuing power on/off commands to the given IPMI port.
Password	`passwd`	The password used to authenticate the connection to the IPMI port.
Password Script (optional)	`passwd_script`	The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
Authentication Type	`auth`	IPMI LAN authentication type: `none`, `password`, or `md5`.
Use Lanplus	`lanplus`	`True` or `1`. If blank, then value is `False`.
Ciphersuite to use	`cipher`	The remote server authentication, integrity, and encryption algorithms to use for IPMIv2 lanplus connections.
Privilege level	`privlvl`	The privilege level on the IPMI device.

Figure 5.20, "IPMI over LAN" shows the configuration screen for adding an IPMI over LAN device

The IPMI over LAN fence device configuration page.

Figure 5.20. IPMI over LAN

The following command creates a fence device instance for an IPMI over LAN device:

ccs -f cluster.conf --addfencedev ipmitest1 agent=fence_ipmilan auth=password cipher=3 ipaddr=192.168.0.1 \ lanplus=on login=root passwd=password123

The following is the cluster.conf entry for the fence_ipmilan device:

 <fencedevices>  <fencedevice agent="fence_ipmilan" auth="password" cipher="3" ipaddr="192.168.0.1" lanplus="on" login="root" \   name="ipmitest1" passwd="password123"/> </fencedevices>

5.21. RHEV-M REST API

Table 5.22, "RHEV-M REST API (RHEL 6.2 and later against RHEV 3.0 and later)" lists the fence device parameters used by fence_rhevm, the fence agent for RHEV-M REST API.

Table 5.22. RHEV-M REST API (RHEL 6.2 and later against RHEV 3.0 and later)

luci Field	`cluster.conf` Attribute	Description
Name	`name`	Name of the RHEV-M REST API fencing device.
IP Address or Hostname	`ipaddr`	The IP address or hostname assigned to the device.
IP Port (optional)	`ipport`	The TCP port to use for connection with the device.
Login	`login`	The login name used to access the device.
Password	`passwd`	The password used to authenticate the connection to the device.
Password Script (optional)	`passwd_script`	The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
Use SSL	`ssl`	Use SSL connections to communicate with the device.
Power Wait	`power_wait`	Number of seconds to wait after issuing a power off or power on command.
Port	`port`	Physical plug number or name of virtual machine.

Figure 5.21, "RHEV-M REST API" shows the configuration screen for adding an RHEV-M REST API device

The RHEV-M REST API fence device configuration page.

Figure 5.21. RHEV-M REST API

The following command creates a fence device instance for an RHEV-M REST API device:

ccs -f cluster.conf --addfencedev rhevmtest1 agent=fence_rhevm ipaddr=192.168.0.1 login=root passwd=password123 \ power_wait=60 ssl=on

The following is the cluster.conf entry for the fence_rhevm device:

 <fencedevices>  <fencedevice agent="fence_rhevm" ipaddr="192.168.0.1" login="root" name="rhevmtest1" passwd="password123" \   power_wait="60" ssl="on"/> </fencedevices>

5.22. SCSI Persistent Reservations

Table 5.23, "SCSI Fencing" lists the fence device parameters used by 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:

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.

Table 5.23. SCSI Fencing

luci Field	`cluster.conf` Attribute	Description
Name	`name`	A name for the SCSI fence device.
Node name
Key for current action		(overrides node name)

Figure 5.22, "SCSI Fencing" shows the configuration screen for adding an SCSI fence device

The SCSI Reservation fence device configuration page.

Figure 5.22. SCSI Fencing

The following command creates a fence device instance for a SCSI Fence device:

ccs -f cluster.conf --addfencedev scsifencetest1 agent=fence_scsi

The following is the cluster.conf entry for the fence_scsi device:

 <fencedevices>  <<fencedevice agent="fence_scsi" name="scsifencetest1"/> </fencedevices>

5.23. VMWare over SOAP API

Table 5.24, "VMware Fencing (SOAP Interface) (Red Hat Enterprise Linux 6.2 and later)" lists the fence device parameters used by fence_vmware_soap, the fence agent for VMWare over SOAP API.

Table 5.24. VMware Fencing (SOAP Interface) (Red Hat Enterprise Linux 6.2 and later)

luci Field	`cluster.conf` Attribute	Description
Name	`name`	Name of the virtual machine fencing device.
IP Address or Hostname	`ipaddr`	The IP address or hostname assigned to the device.
IP Port (optional)	`ipport`	The TCP port to use for connection with the device.
Login	`login`	The login name used to access the device.
Password	`passwd`	The password used to authenticate the connection to the device.
Password Script (optional)	`passwd_script`	The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
Separator	`separator`	Separator for CSV created by operation list. The default value is a comma(,).
Power Wait	`power_wait`	Number of seconds to wait after issuing a power off or power on command.
VM name	`port`	Name of virtual machine in inventory path format (e.g., /datacenter/vm/Discovered_virtual_machine/myMachine).
VM UUID	`uuid`	The UUID of the virtual machine to fence.
Use SSL	`ssl`	Use SSL connections to communicate with the device.

Figure 5.23, "VMWare over SOAP Fencing" shows the configuration screen for adding a VMWare over SOAP fence device

The VMWare over SOAP fence device configuration page.

Figure 5.23. VMWare over SOAP Fencing

The following command creates a fence device instance for a VMWare over SOAP fence device:

ccs -f cluster.conf --addfencedev vmwaresoaptest1 agent=fence_vmware_soap login=root passwd=password123 power_wait=60 \ separator=,

The following is the cluster.conf entry for the fence_vmware_soap device:

 <fencedevices>  <fencedevice agent="fence_vmware_soap" ipaddr="192.168.0.1" login="root" name="vmwaresoaptest1" passwd="password123" \   power_wait="60" separator="."/> </fencedevices>

5.24. WTI Power Switch

Table 5.25, "WTI Power Switch" lists the fence device parameters used by fence_wti, the fence agent for the WTI network power switch.

Table 5.25. WTI Power Switch

luci Field	`cluster.conf` Attribute	Description
Name	`name`	A name for the WTI power switch connected to the cluster.
IP Address or Hostname	`ipaddr`	The IP or hostname address assigned to the device.
IP Port (optional)	`ipport`	The TCP port to use to connect to the device.
Login	`login`	The login name used to access the device.
Password	`passwd`	The password used to authenticate the connection to the device.
Password Script (optional)	`passwd_script`	The script that supplies a password for access to the fence device. Using this supersedes the Password parameter.
Port	`port`	Physical plug number or name of virtual machine.
Force command prompt	`cmd_prompt`	The command prompt to use. The default value is ['RSM>', '>MPC', 'IPS>', 'TPS>', 'NBB>', 'NPS>', 'VMR>']
Power Wait	`power_wait`	Number of seconds to wait after issuing a power off or power on command.
Use SSH	`secure`	Indicates that system will use SSH to access the device.
Path to SSH Identity File	`identity_file`	The identity file for SSH.

Figure 5.24, "WTI Fencing" shows the configuration screen for adding a WTI fence device

The WTI fence device configuration page.

Figure 5.24. WTI Fencing

The following command creates a fence device instance for a WTI fence device:

ccs -f cluster.conf --addfencedev wtipwrsw1 agent=fence_wti cmd_prompt=VMR> login=root passwd=password123 \ power_wait=60

The following is the cluster.conf entry for the fence_wti device:

 <fencedevices>  <fencedevice agent="fence_wti" cmd_prompt="VMR>" ipaddr="192.168.0.1" login="root" name="wtipwrsw1" \   passwd="password123" power_wait="60"/> </fencedevices>