Red Hat SummitFence Configuration Guide
Red Hat Enterprise Linux 6
Configuring and Managing Fence Devices for the High Availability Add-On
Abstract
Fencing is the disconnection of a node from the cluster's shared storage. Fencing cuts off I/O from shared storage, thus ensuring data integrity. This manual documents the configuration of fencing on clustered systems using High Availability Add-On and details the configuration of supported fence devices.
Chapter 1. Fencing Pre-Configuration
Copy linkLink copied to clipboard!
This chapter describes tasks to perform and considerations to make before deploying fencing on clusters using Red Hat High Availability Add-On, and consists of the following sections.
1.1. Configuring ACPI For Use with Integrated Fence Devices
Copy linkLink copied to clipboard!
If your cluster uses integrated fence devices, you must configure ACPI (Advanced Configuration and Power Interface) to ensure immediate and complete fencing.
If a cluster node is configured to be fenced by an integrated fence device, disable ACPI Soft-Off for that node. Disabling ACPI Soft-Off allows an integrated fence device to turn off a node immediately and completely rather than attempting a clean shutdown (for example,
shutdown -h now). Otherwise, if ACPI Soft-Off is enabled, an integrated fence device can take four or more seconds to turn off a node (refer to note that follows). In addition, if ACPI Soft-Off is enabled and a node panics or freezes during shutdown, an integrated fence device may not be able to turn off the node. Under those circumstances, fencing is delayed or unsuccessful. Consequently, when a node is fenced with an integrated fence device and ACPI Soft-Off is enabled, a cluster recovers slowly or requires administrative intervention to recover.
Note
The amount of time required to fence a node depends on the integrated fence device used. Some integrated fence devices perform the equivalent of pressing and holding the power button; therefore, the fence device turns off the node in four to five seconds. Other integrated fence devices perform the equivalent of pressing the power button momentarily, relying on the operating system to turn off the node; therefore, the fence device turns off the node in a time span much longer than four to five seconds.
To disable ACPI Soft-Off, use
chkconfig management and verify that the node turns off immediately when fenced. The preferred way to disable ACPI Soft-Off is with chkconfig management: however, if that method is not satisfactory for your cluster, you can disable ACPI Soft-Off with one of the following alternate methods:
- Changing the BIOS setting to "instant-off" or an equivalent setting that turns off the node without delay
Note
Disabling ACPI Soft-Off with the BIOS may not be possible with some computers. - Appending
acpi=offto the kernel boot command line of the/boot/grub/grub.conffileImportant
This method completely disables ACPI; some computers do not boot correctly if ACPI is completely disabled. Use this method only if the other methods are not effective for your cluster.
The following sections provide procedures for the preferred method and alternate methods of disabling ACPI Soft-Off:
- Section 1.1.1, “Disabling ACPI Soft-Off with
chkconfigManagement” — Preferred method - Section 1.1.2, “Disabling ACPI Soft-Off with the BIOS” — First alternate method
- Section 1.1.3, “Disabling ACPI Completely in the
grub.confFile” — Second alternate method
1.1.1. Disabling ACPI Soft-Off with chkconfig Management
Copy linkLink copied to clipboard!
You can use
chkconfig management to disable ACPI Soft-Off either by removing the ACPI daemon (acpid) from chkconfig management or by turning off acpid.
Note
This is the preferred method of disabling ACPI Soft-Off.
Disable ACPI Soft-Off with
chkconfig management at each cluster node as follows:
- Run either of the following commands:
chkconfig --del acpid— This command removesacpidfromchkconfigmanagement.— OR —chkconfig --level 2345 acpid off— This command turns offacpid.
- Reboot the node.
- When the cluster is configured and running, verify that the node turns off immediately when fenced.
Note
You can fence the node with thefence_nodecommand or Conga.
1.1.2. Disabling ACPI Soft-Off with the BIOS
Copy linkLink copied to clipboard!
The preferred method of disabling ACPI Soft-Off is with
chkconfig management (Section 1.1.1, “Disabling ACPI Soft-Off with chkconfig Management”). However, if the preferred method is not effective for your cluster, follow the procedure in this section.
Note
Disabling ACPI Soft-Off with the BIOS may not be possible with some computers.
You can disable ACPI Soft-Off by configuring the BIOS of each cluster node as follows:
- Reboot the node and start the
BIOS CMOS Setup Utilityprogram. - Navigate to the menu (or equivalent power management menu).
- At the menu, set the function (or equivalent) to (or the equivalent setting that turns off the node by means of the power button without delay). Example 1.1, “
BIOS CMOS Setup Utility: set to ” shows a menu with set to and set to .Note
The equivalents to , , and may vary among computers. However, the objective of this procedure is to configure the BIOS so that the computer is turned off by means of the power button without delay. - Exit the
BIOS CMOS Setup Utilityprogram, saving the BIOS configuration. - When the cluster is configured and running, verify that the node turns off immediately when fenced.
Note
You can fence the node with thefence_nodecommand or Conga.
Example 1.1. BIOS CMOS Setup Utility: set to
This example shows set to , and set to .
1.1.3. Disabling ACPI Completely in the grub.conf File
Copy linkLink copied to clipboard!
The preferred method of disabling ACPI Soft-Off is with
chkconfig management (Section 1.1.1, “Disabling ACPI Soft-Off with chkconfig Management”). If the preferred method is not effective for your cluster, you can disable ACPI Soft-Off with the BIOS power management (Section 1.1.2, “Disabling ACPI Soft-Off with the BIOS”). If neither of those methods is effective for your cluster, you can disable ACPI completely by appending acpi=off to the kernel boot command line in the grub.conf file.
Important
This method completely disables ACPI; some computers do not boot correctly if ACPI is completely disabled. Use this method only if the other methods are not effective for your cluster.
You can disable ACPI completely by editing the
grub.conf file of each cluster node as follows:
- Open
/boot/grub/grub.confwith a text editor. - Append
acpi=offto the kernel boot command line in/boot/grub/grub.conf(see Example 1.2, “Kernel Boot Command Line withacpi=offAppended to It”). - Reboot the node.
- When the cluster is configured and running, verify that the node turns off immediately when fenced.
Note
You can fence the node with thefence_nodecommand or Conga.
Example 1.2. Kernel Boot Command Line with acpi=off Appended to It
In this example,
acpi=off has been appended to the kernel boot command line — the line starting with "kernel /vmlinuz-2.6.32-193.el6.x86_64.img".
1.2. SELinux
Copy linkLink copied to clipboard!
The High Availability Add-On for Red Hat Enterprise Linux 6 supports SELinux in the
enforcing state with the SELinux policy type set to targeted.
Note
When using SELinux with the High Availability Add-On in a VM environment, you should ensure that the SELinux boolean
fenced_can_network_connect is persistently set to on. This allows the fence_xvm fencing agent to work properly, enabling the system to fence virtual machines.
For more information about SELinux, see Deployment Guide for Red Hat Enterprise Linux 6.
Chapter 2. Configuring Fencing with the ccs Command
Copy linkLink copied to clipboard!
As of the Red Hat Enterprise Linux 6.1 release and later, the Red Hat High Availability Add-On provides support for the
ccs cluster configuration command. The ccs command allows an administrator to create, modify and view the cluster.conf cluster configuration file. You can use the ccs command to configure a cluster configuration file on a local file system or on a remote node. Using the ccs command, an administrator can also start and stop the cluster services on one or all of the nodes in a configured cluster.
This chapter describes how to configure the Red Hat High Availability Add-On cluster configuration file using the
ccs command.
This chapter consists of the following sections:
Note
Make sure that your deployment of High Availability Add-On meets your needs and can be supported. Consult with an authorized Red Hat representative to verify your configuration prior to deployment. In addition, allow time for a configuration burn-in period to test failure modes.
Note
This chapter references commonly used
cluster.conf elements and attributes. For a comprehensive list and description of cluster.conf elements and attributes, see the cluster schema at /usr/share/cluster/cluster.rng, and the annotated schema at /usr/share/doc/cman-X.Y.ZZ/cluster_conf.html (for example /usr/share/doc/cman-3.0.12/cluster_conf.html).
2.1. Configuring Fence Devices
Copy linkLink copied to clipboard!
Configuring fence devices consists of creating, updating, and deleting fence devices for the cluster. You must create and name the fence devices in a cluster before you can configure fencing for the nodes in the cluster. For information on configuring fencing for the individual nodes in the cluster, see Section 2.3, “Configuring Fencing for Cluster Members”.
Before configuring your fence devices, you may want to modify some of the fence daemon properties for your system from the default values. The values you configure for the fence daemon are general values for the cluster. The general fencing properties for the cluster you may want to modify are summarized as follows:
- The
post_fail_delayattribute is the number of seconds the fence daemon (fenced) waits before fencing a node (a member of the fence domain) after the node has failed. Thepost_fail_delaydefault value is0. Its value may be varied to suit cluster and network performance. - The
post-join_delayattribute is the number of seconds the fence daemon (fenced) waits before fencing a node after the node joins the fence domain. Thepost_join_delaydefault value is6. A typical setting forpost_join_delayis between 20 and 30 seconds, but can vary according to cluster and network performance.
You reset the values of the
post_fail_delay and post_join_delay attributes with the --setfencedaemon option of the ccs command. Note, however, that executing the ccs --setfencedaemon command overwrites all existing fence daemon properties.
For example, to configure a value for the
post_fail_delay attribute, execute the following command. This command will overwrite the values of all other existing fence daemon properties that you can set with this command.
ccs -h host --setfencedaemon post_fail_delay=value
ccs -h host --setfencedaemon post_fail_delay=value
To configure a value for the
post_join_delay attribute, execute the following command. This command will overwrite the values of all other existing fence daemon properties that you can set with this command.
ccs -h host --setfencedaemon post_join_delay=value
ccs -h host --setfencedaemon post_join_delay=value
To configure a value for both the
post_join_delay attribute and the post_fail_delay attribute, execute the following command:
ccs -h host --setfencedaemon post_fail_delay=value post_join_delay=value
ccs -h host --setfencedaemon post_fail_delay=value post_join_delay=valueNote
For more information about the
post_join_delay and post_fail_delay attributes as well as the additional fence daemon properties you can modify, see the fenced(8) man page and see the cluster schema at /usr/share/cluster/cluster.rng, and the annotated schema at /usr/share/doc/cman-X.Y.ZZ/cluster_conf.html.
To configure a fence device for a cluster, execute the following command:
ccs -h host --addfencedev devicename [fencedeviceoptions]
ccs -h host --addfencedev
devicename
[fencedeviceoptions]
For example, to configure an APC fence device in the configuration file on the cluster node
node-01 named myfence with an IP address of apc_ip_example, a login of login_example, and a password of password_example, execute the following command:
ccs -h node-01 --addfencedev myfence agent=fence_apc ipaddr=apc_ip_example login=login_example passwd=password_example
ccs -h node-01 --addfencedev myfence agent=fence_apc ipaddr=apc_ip_example login=login_example passwd=password_example
The following example shows the
fencedevices section of the cluster.conf configuration file after you have added this APC fence device:
<fencedevices>
<fencedevice agent="fence_apc" ipaddr="apc_ip_example" login="login_example" name="myfence" passwd="password_example"/>
</fencedevices>
<fencedevices>
<fencedevice agent="fence_apc" ipaddr="apc_ip_example" login="login_example" name="myfence" passwd="password_example"/>
</fencedevices>
When configuring fence devices for a cluster, you may find it useful to see a listing of available devices for your cluster and the options available for each device. You may also find it useful to see a listing of fence devices currently configured for your cluster. For information on using the
ccs command to print a list of available fence devices and options or to print a list of fence devices currently configured for your cluster, see Section 2.2, “Listing Fence Devices and Fence Device Options”.
To remove a fence device from your cluster configuration, execute the following command:
ccs -h host --rmfencedev fence_device_name
ccs -h host --rmfencedev fence_device_name
For example, to remove a fence device that you have named
myfence from the cluster configuration file on cluster node node-01, execute the following command:
ccs -h node-01 --rmfencedev myfence
ccs -h node-01 --rmfencedev myfence
If you need to modify the attributes of a fence device you have already configured, you must first remove that fence device then add it again with the modified attributes.
Note that when you have finished configuring all of the components of your cluster, you will need to sync the cluster configuration file to all of the nodes.
2.2. Listing Fence Devices and Fence Device Options
Copy linkLink copied to clipboard!
You can use the
ccs command to print a list of available fence devices and to print a list of options for each available fence type. You can also use the ccs command to print a list of fence devices currently configured for your cluster.
To print a list of fence devices currently available for your cluster, execute the following command:
ccs -h host --lsfenceopts
ccs -h host --lsfenceopts
For example, the following command lists the fence devices available on the cluster node
node-01, showing sample output.
To print a list of the options you can specify for a particular fence type, execute the following command:
ccs -h host --lsfenceopts fence_type
ccs -h host --lsfenceopts fence_type
For example, the following command lists the fence options for the
fence_wti fence agent.
To print a list of fence devices currently configured for your cluster, execute the following command:
ccs -h host --lsfencedev
ccs -h host --lsfencedev
2.3. Configuring Fencing for Cluster Members
Copy linkLink copied to clipboard!
Once you have completed the initial steps of creating a cluster and creating fence devices, you need to configure fencing for the cluster nodes. To configure fencing for the nodes after creating a new cluster and configuring the fencing devices for the cluster, follow the steps in this section. Note that you must configure fencing for each node in the cluster.
This section documents the following procedures:
2.3.1. Configuring a Single Power-Based Fence Device for a Node
Copy linkLink copied to clipboard!
Use the following procedure to configure a node with a single power-based fence device that uses a fence device named
apc, which uses the fence_apc fencing agent.
- Add a fence method for the node, providing a name for the fence method.
ccs -h host --addmethod method node
ccs -h host --addmethod method nodeCopy to Clipboard Copied! Toggle word wrap Toggle overflow For example, to configure a fence method namedAPCfor the nodenode-01.example.comin the configuration file on the cluster nodenode-01.example.com, execute the following command:ccs -h node01.example.com --addmethod APC node01.example.com
ccs -h node01.example.com --addmethod APC node01.example.comCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Add a fence instance for the method. You must specify the fence device to use for the node, the node this instance applies to, the name of the method, and any options for this method that are specific to this node:
ccs -h host --addfenceinst fencedevicename node method [options]
ccs -h host --addfenceinst fencedevicename node method [options]Copy to Clipboard Copied! Toggle word wrap Toggle overflow For example, to configure a fence instance in the configuration file on the cluster nodenode-01.example.comthat uses the APC switch power port 1 on the fence device namedapcto fence cluster nodenode-01.example.comusing the method namedAPC, execute the following command:ccs -h node01.example.com --addfenceinst apc node01.example.com APC port=1
ccs -h node01.example.com --addfenceinst apc node01.example.com APC port=1Copy to Clipboard Copied! Toggle word wrap Toggle overflow
You will need to add a fence method for each node in the cluster. The following commands configure a fence method for each node with the method name
APC. The device for the fence method specifies apc as the device name, which is a device previously configured with the --addfencedev option, as described in Section 2.1, “Configuring Fence Devices”. Each node is configured with a unique APC switch power port number: The port number for node-01.example.com is 1, the port number for node-02.example.com is 2, and the port number for node-03.example.com is 3.
Example 2.1, “
cluster.conf After Adding Power-Based Fence Methods ” shows a cluster.conf configuration file after you have added these fencing methods and instances to each node in the cluster.
Example 2.1. cluster.conf After Adding Power-Based Fence Methods
Note that when you have finished configuring all of the components of your cluster, you will need to sync the cluster configuration file to all of the nodes.
2.3.2. Configuring a Single Storage-Based Fence Device for a Node
Copy linkLink copied to clipboard!
When using non-power fencing methods (that is, SAN/storage fencing) to fence a node, you must configure unfencing for the fence device. This ensures that a fenced node is not re-enabled until the node has been rebooted. When you configure unfencing for a node, you specify a device that mirrors the corresponding fence device you have configured for the node with the notable addition of the explicit action of
on or enable.
For more information about unfencing a node, see the
fence_node(8) man page.
Use the following procedure to configure a node with a single storage-based fence device that uses a fence device named
sanswitch1, which uses the fence_sanbox2 fencing agent.
- Add a fence method for the node, providing a name for the fence method.
ccs -h host --addmethod method node
ccs -h host --addmethod method nodeCopy to Clipboard Copied! Toggle word wrap Toggle overflow For example, to configure a fence method namedSANfor the nodenode-01.example.comin the configuration file on the cluster nodenode-01.example.com, execute the following command:ccs -h node01.example.com --addmethod SAN node01.example.com
ccs -h node01.example.com --addmethod SAN node01.example.comCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Add a fence instance for the method. You must specify the fence device to use for the node, the node this instance applies to, the name of the method, and any options for this method that are specific to this node:
ccs -h host --addfenceinst fencedevicename node method [options]
ccs -h host --addfenceinst fencedevicename node method [options]Copy to Clipboard Copied! Toggle word wrap Toggle overflow For example, to configure a fence instance in the configuration file on the cluster nodenode-01.example.comthat uses the SAN switch power port 11 on the fence device namedsanswitch1to fence cluster nodenode-01.example.comusing the method namedSAN, execute the following command:ccs -h node01.example.com --addfenceinst sanswitch1 node01.example.com SAN port=11
ccs -h node01.example.com --addfenceinst sanswitch1 node01.example.com SAN port=11Copy to Clipboard Copied! Toggle word wrap Toggle overflow - To configure unfencing for the storage based fence device on this node, execute the following command:
ccs -h host --addunfence fencedevicename node action=on|off
ccs -h host --addunfence fencedevicename node action=on|offCopy to Clipboard Copied! Toggle word wrap Toggle overflow
You will need to add a fence method for each node in the cluster. The following commands configure a fence method for each node with the method name
SAN. The device for the fence method specifies sanswitch as the device name, which is a device previously configured with the --addfencedev option, as described in Section 2.1, “Configuring Fence Devices”. Each node is configured with a unique SAN physical port number: The port number for node-01.example.com is 11, the port number for node-02.example.com is 12, and the port number for node-03.example.com is 13.
Example 2.2, “
cluster.conf After Adding Storage-Based Fence Methods ” shows a cluster.conf configuration file after you have added fencing methods, fencing instances, and unfencing to each node in the cluster.
Example 2.2. cluster.conf After Adding Storage-Based Fence Methods
Note that when you have finished configuring all of the components of your cluster, you will need to sync the cluster configuration file to all of the nodes.
2.3.3. Configuring a Backup Fence Device
Copy linkLink copied to clipboard!
You can define multiple fencing methods for a node. If fencing fails using the first method, the system will attempt to fence the node using the second method, followed by any additional methods you have configured. To configure a backup fencing method for a node, you configure two methods for a node, configuring a fence instance for each method.
Note
The order in which the system will use the fencing methods you have configured follows their order in the cluster configuration file. The first method you configure with the
ccs command is the primary fencing method, and the second method you configure is the backup fencing method. To change the order, you can remove the primary fencing method from the configuration file, then add that method back.
Note that at any time you can print a list of fence methods and instances currently configured for a node by executing the following command. If you do not specify a node, this command will list the fence methods and instances currently configured for all nodes.
ccs -h host --lsfenceinst [node]
ccs -h host --lsfenceinst [node]
Use the following procedure to configure a node with a primary fencing method that uses a fence device named
apc, which uses the fence_apc fencing agent, and a backup fencing device that uses a fence device named sanswitch1, which uses the fence_sanbox2 fencing agent. Since the sanswitch1 device is a storage-based fencing agent, you will need to configure unfencing for that device as well.
- Add a primary fence method for the node, providing a name for the fence method.
ccs -h host --addmethod method node
ccs -h host --addmethod method nodeCopy to Clipboard Copied! Toggle word wrap Toggle overflow For example, to configure a fence method namedAPCas the primary method for the nodenode-01.example.comin the configuration file on the cluster nodenode-01.example.com, execute the following command:ccs -h node01.example.com --addmethod APC node01.example.com
ccs -h node01.example.com --addmethod APC node01.example.comCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Add a fence instance for the primary method. You must specify the fence device to use for the node, the node this instance applies to, the name of the method, and any options for this method that are specific to this node:
ccs -h host --addfenceinst fencedevicename node method [options]
ccs -h host --addfenceinst fencedevicename node method [options]Copy to Clipboard Copied! Toggle word wrap Toggle overflow For example, to configure a fence instance in the configuration file on the cluster nodenode-01.example.comthat uses the APC switch power port 1 on the fence device namedapcto fence cluster nodenode-01.example.comusing the method namedAPC, execute the following command:ccs -h node01.example.com --addfenceinst apc node01.example.com APC port=1
ccs -h node01.example.com --addfenceinst apc node01.example.com APC port=1Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Add a backup fence method for the node, providing a name for the fence method.
ccs -h host --addmethod method node
ccs -h host --addmethod method nodeCopy to Clipboard Copied! Toggle word wrap Toggle overflow For example, to configure a backup fence method namedSANfor the nodenode-01.example.comin the configuration file on the cluster nodenode-01.example.com, execute the following command:ccs -h node01.example.com --addmethod SAN node01.example.com
ccs -h node01.example.com --addmethod SAN node01.example.comCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Add a fence instance for the backup method. You must specify the fence device to use for the node, the node this instance applies to, the name of the method, and any options for this method that are specific to this node:
ccs -h host --addfenceinst fencedevicename node method [options]
ccs -h host --addfenceinst fencedevicename node method [options]Copy to Clipboard Copied! Toggle word wrap Toggle overflow For example, to configure a fence instance in the configuration file on the cluster nodenode-01.example.comthat uses the SAN switch power port 11 on the fence device namedsanswitch1to fence cluster nodenode-01.example.comusing the method namedSAN, execute the following command:ccs -h node01.example.com --addfenceinst sanswitch1 node01.example.com SAN port=11
ccs -h node01.example.com --addfenceinst sanswitch1 node01.example.com SAN port=11Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Since the
sanswitch1device is a storage-based device, you must configure unfencing for this device.ccs -h node01.example.com --addunfence sanswitch1 node01.example.com port=11 action=on
ccs -h node01.example.com --addunfence sanswitch1 node01.example.com port=11 action=onCopy to Clipboard Copied! Toggle word wrap Toggle overflow
You can continue to add fencing methods as needed.
This procedure configures a fence device and a backup fence device for one node in the cluster. You will need to configure fencing for the other nodes in the cluster as well.
Example 2.3, “
cluster.conf After Adding Backup Fence Methods ” shows a cluster.conf configuration file after you have added a power-based primary fencing method and a storage-based backup fencing method to each node in the cluster.
Example 2.3. cluster.conf After Adding Backup Fence Methods
Note that when you have finished configuring all of the components of your cluster, you will need to sync the cluster configuration file to all of the nodes.
Note
The order in which the system will use the fencing methods you have configured follows their order in the cluster configuration file. The first method you configure is the primary fencing method, and the second method you configure is the backup fencing method. To change the order, you can remove the primary fencing method from the configuration file, then add that method back.
2.3.4. Configuring a Node with Redundant Power
Copy linkLink copied to clipboard!
If your cluster is configured with redundant power supplies for your nodes, you must be sure to configure fencing so that your nodes fully shut down when they need to be fenced. If you configure each power supply as a separate fence method, each power supply will be fenced separately; the second power supply will allow the system to continue running when the first power supply is fenced and the system will not be fenced at all. To configure a system with dual power supplies, you must configure your fence devices so that both power supplies are shut off and the system is taken completely down. This requires that you configure two instances within a single fencing method, and that for each instance you configure both fence devices with an
action attribute of off before configuring each of the devices with an action attribute of on.
To configure fencing for a node with dual power supplies, follow the steps in this section.
- Before you can configure fencing for a node with redundant power, you must configure each of the power switches as a fence device for the cluster. For information on configuring fence devices, see Section 2.1, “Configuring Fence Devices”.To print a list of fence devices currently configured for your cluster, execute the following command:
ccs -h host --lsfencedev
ccs -h host --lsfencedevCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Add a fence method for the node, providing a name for the fence method.
ccs -h host --addmethod method node
ccs -h host --addmethod method nodeCopy to Clipboard Copied! Toggle word wrap Toggle overflow For example, to configure a fence method namedAPC-dualfor the nodenode-01.example.comin the configuration file on the cluster nodenode-01.example.com, execute the following command:ccs -h node01.example.com --addmethod APC-dual node01.example.com
ccs -h node01.example.com --addmethod APC-dual node01.example.comCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Add a fence instance for the first power supply to the fence method. You must specify the fence device to use for the node, the node this instance applies to, the name of the method, and any options for this method that are specific to this node. At this point you configure the
actionattribute asoff.ccs -h host --addfenceinst fencedevicename node method [options] action=off
ccs -h host --addfenceinst fencedevicename node method [options] action=offCopy to Clipboard Copied! Toggle word wrap Toggle overflow For example, to configure a fence instance in the configuration file on the cluster nodenode-01.example.comthat uses the APC switch power port 1 on the fence device namedapc1to fence cluster nodenode-01.example.comusing the method namedAPC-dual, and setting theactionattribute tooff, execute the following command:ccs -h node01.example.com --addfenceinst apc1 node01.example.com APC-dual port=1 action=off
ccs -h node01.example.com --addfenceinst apc1 node01.example.com APC-dual port=1 action=offCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Add a fence instance for the second power supply to the fence method. You must specify the fence device to use for the node, the node this instance applies to, the name of the method, and any options for this method that are specific to this node. At this point you configure the
actionattribute asofffor this instance as well:ccs -h host --addfenceinst fencedevicename node method [options] action=off
ccs -h host --addfenceinst fencedevicename node method [options] action=offCopy to Clipboard Copied! Toggle word wrap Toggle overflow For example, to configure a second fence instance in the configuration file on the cluster nodenode-01.example.comthat uses the APC switch power port 1 on the fence device namedapc2to fence cluster nodenode-01.example.comusing the same method as you specified for the first instance namedAPC-dual, and setting theactionattribute tooff, execute the following command:ccs -h node01.example.com --addfenceinst apc2 node01.example.com APC-dual port=1 action=off
ccs -h node01.example.com --addfenceinst apc2 node01.example.com APC-dual port=1 action=offCopy to Clipboard Copied! Toggle word wrap Toggle overflow - At this point, add another fence instance for the first power supply to the fence method, configuring the
actionattribute ason. You must specify the fence device to use for the node, the node this instance applies to, the name of the method, and any options for this method that are specific to this node, and specifying theactionattribute ason:ccs -h host --addfenceinst fencedevicename node method [options] action=on
ccs -h host --addfenceinst fencedevicename node method [options] action=onCopy to Clipboard Copied! Toggle word wrap Toggle overflow For example, to configure a fence instance in the configuration file on the cluster nodenode-01.example.comthat uses the APC switch power port 1 on the fence device namedapc1to fence cluster nodenode-01.example.comusing the method namedAPC-dual, and setting theactionattribute toon, execute the following command:ccs -h node01.example.com --addfenceinst apc1 node01.example.com APC-dual port=1 action=on
ccs -h node01.example.com --addfenceinst apc1 node01.example.com APC-dual port=1 action=onCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Add another fence instance for second power supply to the fence method, specifying the
actionattribute asonfor this instance. You must specify the fence device to use for the node, the node this instance applies to, the name of the method, and any options for this method that are specific to this node as well as theactionattribute ofon.ccs -h host --addfenceinst fencedevicename node method [options] action=on
ccs -h host --addfenceinst fencedevicename node method [options] action=onCopy to Clipboard Copied! Toggle word wrap Toggle overflow For example, to configure a second fence instance in the configuration file on the cluster nodenode-01.example.comthat uses the APC switch power port 1 on the fence device namedapc2to fence cluster nodenode-01.example.comusing the same method as you specified for the first instance namedAPC-dualand setting theactionattribute toon, execute the following command:ccs -h node01.example.com --addfenceinst apc2 node01.example.com APC-dual port=1 action=on
ccs -h node01.example.com --addfenceinst apc2 node01.example.com APC-dual port=1 action=onCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Example 2.4, “
cluster.conf After Adding Dual-Power Fencing ” shows a cluster.conf configuration file after you have added fencing for two power supplies for each node in a cluster.
Example 2.4. cluster.conf After Adding Dual-Power Fencing
Note that when you have finished configuring all of the components of your cluster, you will need to sync the cluster configuration file to all of the nodes.
2.3.5. Testing the Fence Configuration
Copy linkLink copied to clipboard!
As of Red Hat Enterprise Linux Release 6.4, you can test the fence configuration for each node in a cluster with the
fence_check utility.
The following example shows the output of a successful execution of this command.
For information on this utility, see the
fence_check(8) man page.
2.3.6. Removing Fence Methods and Fence Instances
Copy linkLink copied to clipboard!
To remove a fence method from your cluster configuration, execute the following command:
ccs -h host --rmmethod method node
ccs -h host --rmmethod method node
For example, to remove a fence method that you have named
APC that you have configured for node01.example.com from the cluster configuration file on cluster node node01.example.com, execute the following command:
ccs -h node01.example.com --rmmethod APC node01.example.com
ccs -h node01.example.com --rmmethod APC node01.example.com
To remove all fence instances of a fence device from a fence method, execute the following command:
ccs -h host --rmfenceinst fencedevicename node method
ccs -h host --rmfenceinst fencedevicename node method
For example, to remove all instances of the fence device named
apc1 from the method named APC-dual configured for node01.example.com from the cluster configuration file on cluster node node01.example.com, execute the following command:
ccs -h node01.example.com --rmfenceinst apc1 node01.example.com APC-dual
ccs -h node01.example.com --rmfenceinst apc1 node01.example.com APC-dual
Chapter 3. Configuring Fencing with Conga
Copy linkLink copied to clipboard!
This chapter describes how to configure fencing in Red Hat High Availability Add-On using Conga.
Note
Conga is a graphical user interface that you can use to administer the Red Hat High Availability Add-On. Note, however, that in order to use this interface effectively you need to have a good and clear understanding of the underlying concepts. Learning about cluster configuration by exploring the available features in the user interface is not recommended, as it may result in a system that is not robust enough to keep all services running when components fail.
3.1. Configuring Fence Daemon Properties
Copy linkLink copied to clipboard!
Clicking on the tab displays the page, which provides an interface for configuring and . The values you configure for these parameters are general fencing properties for the cluster. To configure specific fence devices for the nodes of the cluster, use the menu item of the cluster display, as described in Section 3.2, “Configuring Fence Devices”.
- The parameter is the number of seconds the fence daemon (
fenced) waits before fencing a node (a member of the fence domain) after the node has failed. The default value is0. Its value may be varied to suit cluster and network performance. - The parameter is the number of seconds the fence daemon (
fenced) waits before fencing a node after the node joins the fence domain. The default value is6. A typical setting for is between 20 and 30 seconds, but can vary according to cluster and network performance.
Enter the values required and click for changes to take effect.
Note
For more information about and , see the fenced(8) man page.
3.2. Configuring Fence Devices
Copy linkLink copied to clipboard!
Configuring fence devices consists of creating, updating, and deleting fence devices for the cluster. You must configure the fence devices in a cluster before you can configure fencing for the nodes in the cluster.
Creating a fence device consists of selecting a fence device type and entering parameters for that fence device (for example, name, IP address, login, and password). Updating a fence device consists of selecting an existing fence device and changing parameters for that fence device. Deleting a fence device consists of selecting an existing fence device and deleting it.
This section provides procedures for the following tasks:
- Creating fence devices — Refer to Section 3.2.1, “Creating a Fence Device”. Once you have created and named a fence device, you can configure the fence devices for each node in the cluster, as described in Section 3.3, “Configuring Fencing for Cluster Members”.
- Updating fence devices — Refer to Section 3.2.2, “Modifying a Fence Device”.
- Deleting fence devices — Refer to Section 3.2.3, “Deleting a Fence Device”.
From the cluster-specific page, you can configure fence devices for that cluster by clicking on along the top of the cluster display. This displays the fence devices for the cluster and displays the menu items for fence device configuration: and . This is the starting point of each procedure described in the following sections.
Note
If this is an initial cluster configuration, no fence devices have been created, and therefore none are displayed.
Figure 3.1, “luci fence devices configuration page” shows the fence devices configuration screen before any fence devices have been created.
Figure 3.1. luci fence devices configuration page
3.2.1. Creating a Fence Device
Copy linkLink copied to clipboard!
To create a fence device, follow these steps:
- From the configuration page, click . Clicking displays the Add Fence Device (Instance) dialog box. From this dialog box, select the type of fence device to configure.
- Specify the information in the Add Fence Device (Instance) dialog box according to the type of fence device. In some cases you will need to specify additional node-specific parameters for the fence device when you configure fencing for the individual nodes.
- Click .
After the fence device has been added, it appears on the configuration page.
3.2.2. Modifying a Fence Device
Copy linkLink copied to clipboard!
To modify a fence device, follow these steps:
- From the configuration page, click on the name of the fence device to modify. This displays the dialog box for that fence device, with the values that have been configured for the device.
- To modify the fence device, enter changes to the parameters displayed.
- Click and wait for the configuration to be updated.
3.2.3. Deleting a Fence Device
Copy linkLink copied to clipboard!
Note
Fence devices that are in use cannot be deleted. To delete a fence device that a node is currently using, first update the node fence configuration for any node using the device and then delete the device.
To delete a fence device, follow these steps:
- From the configuration page, check the box to the left of the fence device or devices to select the devices to delete.
- Click and wait for the configuration to be updated. A message appears indicating which devices are being deleted.
When the configuration has been updated, the deleted fence device no longer appears in the display.
3.3. Configuring Fencing for Cluster Members
Copy linkLink copied to clipboard!
Once you have completed the initial steps of creating a cluster and creating fence devices, you need to configure fencing for the cluster nodes. To configure fencing for the nodes after creating a new cluster and configuring the fencing devices for the cluster, follow the steps in this section. Note that you must configure fencing for each node in the cluster.
The following sections provide procedures for configuring a single fence device for a node, configuring a node with a backup fence device, and configuring a node with redundant power supplies:
3.3.1. Configuring a Single Fence Device for a Node
Copy linkLink copied to clipboard!
Use the following procedure to configure a node with a single fence device.
- From the cluster-specific page, you can configure fencing for the nodes in the cluster by clicking on along the top of the cluster display. This displays the nodes that constitute the cluster. This is also the default page that appears when you click on the cluster name beneath from the menu on the left side of the luci page.
- Click on a node name. Clicking a link for a node causes a page to be displayed for that link showing how that node is configured.The node-specific page displays any services that are currently running on the node, as well as any failover domains of which this node is a member. You can modify an existing failover domain by clicking on its name.
- On the node-specific page, under , click . This displays the dialog box.
- Enter a for the fencing method that you are configuring for this node. This is an arbitrary name that will be used by Red Hat High Availability Add-On; it is not the same as the DNS name for the device.
- Click . This displays the node-specific screen that now displays the method you have just added under .
- Configure a fence instance for this method by clicking the button that appears beneath the fence method. This displays the drop-down menu from which you can select a fence device you have previously configured, as described in Section 3.2.1, “Creating a Fence Device”.
- Select a fence device for this method. If this fence device requires that you configure node-specific parameters, the display shows the parameters to configure.
Note
For non-power fence methods (that is, SAN/storage fencing), is selected by default on the node-specific parameters display. This ensures that a fenced node's access to storage is not re-enabled until the node has been rebooted. For information on unfencing a node, see thefence_node(8) man page. - Click . This returns you to the node-specific screen with the fence method and fence instance displayed.
3.3.2. Configuring a Backup Fence Device
Copy linkLink copied to clipboard!
You can define multiple fencing methods for a node. If fencing fails using the first method, the system will attempt to fence the node using the second method, followed by any additional methods you have configured.
Use the following procedure to configure a backup fence device for a node.
- Use the procedure provided in Section 3.3.1, “Configuring a Single Fence Device for a Node” to configure the primary fencing method for a node.
- Beneath the display of the primary method you defined, click .
- Enter a name for the backup fencing method that you are configuring for this node and click . This displays the node-specific screen that now displays the method you have just added, below the primary fence method.
- Configure a fence instance for this method by clicking . This displays a drop-down menu from which you can select a fence device you have previously configured, as described in Section 3.2.1, “Creating a Fence Device”.
- Select a fence device for this method. If this fence device requires that you configure node-specific parameters, the display shows the parameters to configure.
- Click . This returns you to the node-specific screen with the fence method and fence instance displayed.
You can continue to add fencing methods as needed. You can rearrange the order of fencing methods that will be used for this node by clicking on and .
3.3.3. Configuring a Node with Redundant Power
Copy linkLink copied to clipboard!
If your cluster is configured with redundant power supplies for your nodes, you must be sure to configure fencing so that your nodes fully shut down when they need to be fenced. If you configure each power supply as a separate fence method, each power supply will be fenced separately; the second power supply will allow the system to continue running when the first power supply is fenced and the system will not be fenced at all. To configure a system with dual power supplies, you must configure your fence devices so that both power supplies are shut off and the system is taken completely down. When configuring your system using Conga, this requires that you configure two instances within a single fencing method.
To configure fencing for a node with dual power supplies, follow the steps in this section.
- Before you can configure fencing for a node with redundant power, you must configure each of the power switches as a fence device for the cluster. For information on configuring fence devices, see Section 3.2, “Configuring Fence Devices”.
- From the cluster-specific page, click on along the top of the cluster display. This displays the nodes that constitute the cluster. This is also the default page that appears when you click on the cluster name beneath from the menu on the left side of the luci page.
- Click on a node name. Clicking a link for a node causes a page to be displayed for that link showing how that node is configured.
- On the node-specific page, click .
- Enter a name for the fencing method that you are configuring for this node.
- Click . This displays the node-specific screen that now displays the method you have just added under .
- Configure the first power supply as a fence instance for this method by clicking . This displays a drop-down menu from which you can select one of the power fencing devices you have previously configured, as described in Section 3.2.1, “Creating a Fence Device”.
- Select one of the power fence devices for this method and enter the appropriate parameters for this device.
- Click . This returns you to the node-specific screen with the fence method and fence instance displayed.
- Under the same fence method for which you have configured the first power fencing device, click . This displays a drop-down menu from which you can select the second power fencing devices you have previously configured, as described in Section 3.2.1, “Creating a Fence Device”.
- Select the second of the power fence devices for this method and enter the appropriate parameters for this device.
- Click . This returns you to the node-specific screen with the fence methods and fence instances displayed, showing that each device will power the system off in sequence and power the system on in sequence. This is shown in Figure 3.2, “Dual-Power Fencing Configuration”.
Figure 3.2. Dual-Power Fencing Configuration
3.3.4. Testing the Fence Configuration
Copy linkLink copied to clipboard!
As of Red Hat Enterprise Linux Release 6.4, you can test the fence configuration for each node in a cluster with the
fence_check utility.
The following example shows the output of a successful execution of this command.
For information on this utility, see the
fence_check(8) man page.
Chapter 4. Fence Devices
Copy linkLink copied to clipboard!
This chapter documents the fence devices currently supported in Red Hat Enterprise Linux High-Availability Add-On.
Table 4.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.
4.1. APC Power Switch over Telnet and SSH
Copy linkLink copied to clipboard!
Table 4.2, “APC Power Switch (telnet/SSH)” lists the fence device parameters used by
fence_apc, the fence agent for APC over 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 by means of telnet/ssh. |
| IP Address or Hostname | ipaddr | The IP address or host name assigned to the device. |
| IP Port (optional) | ipport | The TCP port to use to connect to the device. The default port is 23, or 22 if Use SSH is selected. |
| 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 parameter. |
| Power Wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
| 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. |
| Delay (optional) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
| Use SSH | secure | Indicates that system will use SSH to access the device. When using SSH, you must specify either a password, a password script, or an identity file. |
| SSH Options | ssh_options | SSH options to use. The default value is -1 -c blowfish. |
| Path to SSH Identity File | identity_file | The identity file for SSH. |
Figure 4.1, “APC Power Switch” shows the configuration screen for adding an APC Power Switch fence device.
Figure 4.1. 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
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>
<fencedevices>
<fencedevice agent="fence_apc" name="apc" ipaddr="apc-telnet.example.com" login="root" passwd="password123"/>
</fencedevices>
4.2. APC Power Switch over SNMP
Copy linkLink copied to clipboard!
Table 4.3, “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 by means of the SNMP protocol.
| luci Field | cluster.conf Attribute | Description |
|---|---|---|
| Name | name | A name for the APC device connected to the cluster into which the fence daemon logs by means of the SNMP protocol. |
| IP Address or Hostname | ipaddr | The IP address or host name 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 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 parameter. |
| Power Wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
| Port (Outlet) Number | port | The port. |
| Delay (optional) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
Figure 4.2, “APC Power Switch over SNMP” shows the configuration screen for adding an APC Power Switch fence device.
Figure 4.2. 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>
<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>
4.3. Brocade Fabric Switch
Copy linkLink copied to clipboard!
Table 4.4, “Brocade Fabric Switch” lists the fence device parameters used by
fence_brocade, the fence agent for Brocade FC switches.
| 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 or host name 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 parameter. |
| Force IP Family | inet4_only, inet6_only | Force the agent to use IPv4 or IPv6 addresses only |
| Force Command Prompt | cmd_prompt | The command prompt to use. The default value is '\$'. |
| Power Wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
| Port | port | The switch outlet number. |
| Delay (optional) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
| Use SSH | secure | Indicates that the system will use SSH to access the device. When using SSH, you must specify either a password, a password script, or an identity file. |
| SSH Options | ssh_options | SSH options to use. The default value is -1 -c blowfish. |
| Path to SSH Identity File | identity_file | The identity file for SSH. |
| Unfencing | unfence section of the cluster configuration file | When enabled, this ensures that a fenced node is not re-enabled until the node has been rebooted. This is necessary for non-power fence methods (that is, SAN/storage fencing). When you configure a device that requires unfencing, the cluster must first be stopped and the full configuration including devices and unfencing must be added before the cluster is started. For more information about unfencing a node, see the fence_node(8) man page. |
Figure 4.3, “Brocade Fabric Switch” shows the configuration screen for adding an Brocade Fabric Switch fence device.
Figure 4.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
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>
<fencedevices>
<fencedevice agent="fence_brocade" ipaddr="brocadetest.example.com" login="brocadetest" \
name="brocadetest" passwd="brocadetest"/>
</fencedevices>
4.4. Cisco MDS
Copy linkLink copied to clipboard!
Table 4.5, “Cisco MDS” lists the fence device parameters used by
fence_cisco_mds, the fence agent for 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 host name 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 parameter. |
| 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 parameter. |
| Power Wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
| Port (Outlet) Number | port | The port. |
| Delay (optional) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
Figure 4.4, “Cisco MDS” shows the configuration screen for adding an Cisco MDS fence device.
Figure 4.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
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:
4.5. Cisco UCS
Copy linkLink copied to clipboard!
Table 4.6, “Cisco UCS” lists the fence device parameters used by
fence_cisco_ucs, the fence agent for 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 host name 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 parameter. |
| Use SSL | ssl | Use SSL connections to communicate with the device. |
| Sub-Organization | suborg | Additional path needed to access suborganization. |
| Power Wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
| Port (Outlet) Number | port | Name of virtual machine. |
| Delay (optional) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
Figure 4.5, “Cisco UCS” shows the configuration screen for adding a Cisco UCS fence device.
Figure 4.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/
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>
<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>
4.6. Dell Drac 5
Copy linkLink copied to clipboard!
Table 4.7, “Dell DRAC 5” lists the fence device parameters used by
fence_drac5, the fence agent for 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 host name 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 parameter. |
| Use SSH | secure | Indicates that the system will use SSH to access the device. When using SSH, you must specify either a password, a password script, or an identity file. |
| SSH Options | ssh_options | SSH options to use. The default value is -1 -c blowfish. |
| 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 (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Delay (seconds) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
Figure 4.6, “Dell Drac 5” shows the configuration screen for adding a Dell Drac 5 device
Figure 4.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
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>
<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>
4.7. Eaton Network Power Switch
Copy linkLink copied to clipboard!
Table 4.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.
| 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 host name 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 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 parameter. |
| Power wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
| Port (Outlet) Number | port | Physical plug number or name of virtual machine. This parameter is always required. |
| Delay (optional) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
Figure 4.7, “Eaton Network Power Switch” shows the configuration screen for adding an Eaton Network Power Switch fence device.
Figure 4.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
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:
4.8. Egenera BladeFrame
Copy linkLink copied to clipboard!
Table 4.9, “Egenera BladeFrame” lists the fence device parameters used by
fence_egenera, the fence agent for the Egenera BladeFrame.
| luci Field | cluster.conf Attribute | Description |
|---|---|---|
| Name | name | A name for the Egenera BladeFrame device connected to the cluster. |
| CServer | cserver | The host name (and optionally the user name 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. |
| Delay (optional) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
| Unfencing | unfence section of the cluster configuration file | When enabled, this ensures that a fenced node is not re-enabled until the node has been rebooted. This is necessary for non-power fence methods (that is, SAN/storage fencing). When you configure a device that requires unfencing, the cluster must first be stopped and the full configuration including devices and unfencing must be added before the cluster is started. For more information about unfencing a node, see the fence_node(8) man page. |
Figure 4.8, “Egenera BladeFrame” shows the configuration screen for adding an Egenera BladeFrame fence device.
Figure 4.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
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>
<fencedevices>
<fencedevice agent="fence_egenera" cserver="cservertest" name="egeneratest" user="root"/>
</fencedevices>
4.9. Emerson Network Power Switch (SNMP interface)
Copy linkLink copied to clipboard!
Table 4.10, “Emerson Network Power Switch (SNMP interface) (Red Hat Enterprise Linux 6.7 and later)” lists the fence device parameters used by
fence_emerson, the fence agent for Emerson over SNMP.
| luci Field | cluster.conf Attribute | Description |
|---|---|---|
| Name | name | A name for the Emerson Network Power Switch device connected to the cluster. |
| IP Address or Hostname | ipaddr | The IP address or host name 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 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 parameter. |
| Power Wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
| Port (Outlet) Number | port | Physical plug number or name of virtual machine. |
| Delay (optional) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
4.10. ePowerSwitch
Copy linkLink copied to clipboard!
Table 4.11, “ePowerSwitch” lists the fence device parameters used by
fence_eps, the fence agent for 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 host name 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 parameter. |
| Name of Hidden Page | hidden_page | The name of the hidden page for the device. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
| Port (Outlet) Number | port | Physical plug number or name of virtual machine. |
| Delay (optional) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
Figure 4.9, “ePowerSwitch” shows the configuration screen for adding an ePowerSwitch fence device.
Figure 4.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
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>
<fencedevices>
<fencedevice agent="fence_eps" hidden_page="hidden.htm" ipaddr="192.168.0.1" login="root" name="epstest1" \
passwd="password123"/>
</fencedevices>
4.11. Fence Virt (Serial/VMChannel Mode)
Copy linkLink copied to clipboard!
Table 4.12, “Fence virt (Serial/VMChannel Mode)” lists the fence device parameters used by
fence_virt, the fence agent for virtual machines using VM channel or serial mode .
| 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 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. |
| Timeout (optional) | timeout | Fencing timeout, in seconds. The default value is 30. |
| Domain | port (formerly domain) | 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. | |
| Delay (optional) | delay | Fencing delay, in seconds. The fence agent will wait the specified number of seconds before attempting a fencing operation. The default value is 0. |
The following command creates a fence device instance for virtual machines using serial mode.
ccs -f cluster.conf --addfencedev fencevirt1 agent=fence_virt serial_device=/dev/ttyS1 serial_params=19200, 8N1
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>
<fencedevices>
<fencedevice agent="fence_virt" name="fencevirt1" serial_device="/dev/ttyS1" serial_params="19200, 8N1"/>
</fencedevices>
4.12. Fence Virt (Multicast Mode)
Copy linkLink copied to clipboard!
Table 4.13, “Fence virt (Multicast Mode) ” lists the fence device parameters used by
fence_xvm, the fence agent for virtual machines using multicast.
| luci Field | cluster.conf Attribute | Description |
|---|---|---|
| Name | name | A name for the Fence virt fence device. |
| Timeout | timeout | Fencing timeout, in seconds. The default value is 30. |
| Domain | port (formerly domain) | Virtual machine (domain UUID or name) to fence. |
| Delay (optional) | delay | Fencing delay, in seconds. The fence agent will wait the specified number of seconds before attempting a fencing operation. The default value is 0. |
4.13. Fujitsu-Siemens RemoteView Service Board (RSB)
Copy linkLink copied to clipboard!
Table 4.14, “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).
| 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 host name 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 parameter. |
| TCP Port | ipport | The port number on which the telnet service listens. The default value is 3172. |
| Force Command Prompt | cmd_prompt | The command prompt to use. The default value is '\$'. |
| Power Wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Delay (seconds) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
Figure 4.10, “Fujitsu-Siemens RSB” shows the configuration screen for adding an Fujitsu-Siemens RSB fence device.
Figure 4.10. 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
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>
<fencedevices>
<fencedevice agent="fence_rsb" ipaddr="192.168.0.1" login="root" name="fsrsbtest1" passwd="password123" telnet_port="3172"/>
</fencedevices>
4.14. Hewlett-Packard BladeSystem
Copy linkLink copied to clipboard!
Table 4.15, “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.
| 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 host name 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 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. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
| Use SSH | secure | Indicates that the system will use SSH to access the device. When using SSH, you must specify either a password, a password script, or an identity file. |
| SSH Options | ssh_options | SSH options to use. The default value is -1 -c blowfish. |
| Path to SSH Identity File | identity_file | The identity file for SSH. |
Figure 4.11, “HP BladeSystem” shows the configuration screen for adding an HP BladeSystem fence device.
Figure 4.11. 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
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:
4.15. Hewlett-Packard iLO
Copy linkLink copied to clipboard!
The fence agents for HP iLO devices
fence_ilo and HP iLO2 devices fence_ilo2. share the same implementation. Table 4.16, “HP iLO (Integrated Lights Out) and HP iLO2” lists the fence device parameters used by these agents.
| 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 host name assigned to the device. |
| IP Port (optional) | ipport | TCP port to use for connection with the device. The default value is 443. |
| 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 parameter. |
| Power Wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Delay (seconds) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
Figure 4.12, “HP iLO” shows the configuration screen for adding an HP iLO fence device.
Figure 4.12. 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
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>
<fencedevices>
<fencedevice agent="fence_ilo" ipaddr="192.168.0.1" login="root" name="hpilotest1" passwd="password123" \
power_wait="60"/>
</fencedevices>
4.16. HP iLO over SSH
Copy linkLink copied to clipboard!
The fence agents for HP iLO devices over SSH (
fence_ilo_ssh), HP iLO3 devices over SSH (fence_ilo3_ssh), and HP iLO4 devices over SSH (fence_ilo4_ssh) share the same implementation. Table 4.17, “HP iLO over SSH, HP iLO3 over SSH, HPiLO4 over SSH (Red Hat Enterprise Linux 6.7 and later)” lists the fence device parameters used by these agents.
| 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 host name 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 parameter. |
| Use SSH | secure | Indicates that the system will use SSH to access the device. When using SSH, you must specify either a password, a password script, or an identity file. |
| Path to SSH Identity File | identity_file | The Identity file for SSH. |
| TCP Port | ipport | UDP/TCP port to use for connections with the device; the default value is 23. |
| Force Command Prompt | cmd_prompt | The command prompt to use. The default value is 'MP>', 'hpiLO->'. |
| Method to Fence | method | The method to fence: on/off or cycle |
| Power Wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Delay (seconds) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
4.17. Hewlett-Packard iLO MP
Copy linkLink copied to clipboard!
Table 4.18, “HP iLO (Integrated Lights Out) MP” lists the fence device parameters used by
fence_ilo_mp, the fence agent for HP iLO MP devices.
| 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 host name 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 parameter. |
| Use SSH | secure | Indicates that the system will use SSH to access the device. When using SSH, you must specify either a password, a password script, or an identity file. |
| SSH Options | ssh_options | SSH options to use. The default value is -1 -c blowfish. |
| 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 (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Delay (seconds) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
Figure 4.13, “HP iLO MP” shows the configuration screen for adding an HP iLO MPfence device.
Figure 4.13. 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
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>
<fencedevices>
<fencedevice agent="fence_ilo_mp" cmd_prompt="hpiLO->" ipaddr="192.168.0.1" login="root" name="hpilomptest1" passwd="password123" power_wait="60"/>
</fencedevices>
4.18. HP Moonshot iLO
Copy linkLink copied to clipboard!
Table 4.19, “HP Moonshot iLO (Red Hat Enterprise Linux 6.7 and later)” lists the fence device parameters used by
fence_ilo_moonshot, the fence agent for HP Moonshot iLO devices.
| 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 host name 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 parameter. |
| Use SSH | secure | Indicates that the system will use SSH to access the device. When using SSH, you must specify either a password, a password script, or an identity file. |
| Path to SSH Identity File | identity_file | The Identity file for SSH. |
| TCP Port | ipport | UDP/TCP port to use for connections with the device; the default value is 22. |
| Force Command Prompt | cmd_prompt | The command prompt to use. The default value is 'MP>', 'hpiLO->'. |
| Power Wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Delay (seconds) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
4.19. IBM BladeCenter
Copy linkLink copied to clipboard!
Table 4.20, “IBM BladeCenter” lists the fence device parameters used by
fence_bladecenter, the fence agent for 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 host name 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 parameter. |
| Power Wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
| Use SSH | secure | Indicates that system will use SSH to access the device. When using SSH, you must specify either a password, a password script, or an identity file. |
| SSH Options | ssh_options | SSH options to use. The default value is -1 -c blowfish. |
| Path to SSH Identity File | identity_file | The identity file for SSH. |
Figure 4.14, “IBM BladeCenter” shows the configuration screen for adding an IBM BladeCenter fence device.
Figure 4.14. 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
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>
<fencedevices>
<fencedevice agent="fence_bladecenter" ipaddr="192.168.0.1" login="root" name="bladecentertest1" passwd="password123" \
power_wait="60"/>
</fencedevices>
4.20. IBM BladeCenter over SNMP
Copy linkLink copied to clipboard!
Table 4.21, “IBM BladeCenter SNMP” lists the fence device parameters used by
fence_ibmblade, the fence agent for IBM BladeCenter over 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 host name 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 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 parameter. |
| Power Wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
| Port (Outlet) Number | port | Physical plug number or name of virtual machine. |
| Delay (optional) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
Figure 4.15, “IBM BladeCenter SNMP” shows the configuration screen for adding an IBM BladeCenter SNMP fence device.
Figure 4.15. 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
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>
<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>
4.21. IBM iPDU
Copy linkLink copied to clipboard!
Table 4.22, “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.
| 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 by means of the SNMP protocol. |
| IP Address or Hostname | ipaddr | The IP address or host name 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 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 parameter. |
| Power Wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
| Port (Outlet) Number | port | Physical plug number or name of virtual machine. |
| Delay (optional) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
Figure 4.16, “IBM iPDU” shows the configuration screen for adding an IBM iPDU fence device.
Figure 4.16. 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
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:
4.22. IF-MIB
Copy linkLink copied to clipboard!
Table 4.23, “IF MIB” lists the fence device parameters used by
fence_ifmib, the fence agent for IF-MIB devices.
| 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 host name 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 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 parameter. |
| Power Wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
| Port (Outlet) Number | port | Physical plug number or name of virtual machine. |
| Delay (optional) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
Figure 4.17, “IF-MIB” shows the configuration screen for adding an IF-MIB fence device.
Figure 4.17. 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
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>
<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>
4.23. Intel Modular
Copy linkLink copied to clipboard!
Table 4.24, “Intel Modular” lists the fence device parameters used by
fence_intelmodular, the fence agent for 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 host name 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 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 parameter. |
| Power Wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
| Port (Outlet) Number | port | Physical plug number or name of virtual machine. |
| Delay (optional) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
Figure 4.18, “Intel Modular” shows the configuration screen for adding an Intel Modular fence device.
Figure 4.18. 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
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>
<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>
4.24. IPMI over LAN
Copy linkLink copied to clipboard!
The fence agents for IPMI over LAN (
fence_ipmilan,) Dell iDRAC (fence_idrac), IBM Integrated Management Module (fence_imm), HP iLO3 devices (fence_ilo3), and HP iLO4 devices (fence_ilo4) share the same implementation. Table 4.25, “IPMI (Intelligent Platform Management Interface) LAN, Dell iDrac, IBM Integrated Management Module, HPiLO3, HPiLO4” lists the fence device parameters used by these agents.
| luci Field | cluster.conf Attribute | Description |
|---|---|---|
| Name | name | A name for the fence device connected to the cluster. |
| IP Address or Hostname | ipaddr | The IP address or host name assigned to the device. |
| Login | login | The login name of a user capable of issuing power on/off commands to the given port. |
| Password | passwd | The password used to authenticate the connection to the port. |
| Password Script (optional) | passwd_script | The script that supplies a password for access to the fence device. Using this supersedes the parameter. |
| Authentication Type | auth | Authentication type: none, password, or MD5. |
| Use Lanplus | lanplus | True or 1. If blank, then value is False. It is recommended that you enable Lanplus to improve the security of your connection if your hardware supports it. |
| 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 device. |
| IPMI Operation Timeout | timeout | Timeout in seconds for IPMI operation. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
| Power Wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. The default value is 2 seconds for fence_ipmilan, fence_idrac, fence_imm, and fence_ilo4. The default value is 4 seconds for fence_ilo3. |
| Delay (optional) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
| Method to Fence | method | The method to fence: on/off or cycle |
Figure 4.19, “IPMI over LAN” shows the configuration screen for adding an IPMI over LAN device
Figure 4.19. 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
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>
<fencedevices>
<fencedevice agent="fence_ipmilan" auth="password" cipher="3" ipaddr="192.168.0.1" lanplus="on" login="root" \
name="ipmitest1" passwd="password123"/>
</fencedevices>
4.25. Fence kdump
Copy linkLink copied to clipboard!
Table 4.26, “Fence kdump” lists the fence device parameters used by
fence_dkump, the fence agent for kdump crash recovery service. Note that fence_kdump is not a replacement for traditional fencing methods; The fence_kdump agent can detect only that a node has entered the kdump crash recovery service. This allows the kdump crash recovery service to complete without being preempted by traditional power fencing methods.
| luci Field | cluster.conf Attribute | Description |
|---|---|---|
| Name | name | A name for the fence_kdump device. |
| IP Family | family | IP network family. The default value is auto. |
| IP Port (optional) | ipport | IP port number that the fence_kdump agent will use to listen for messages. The default value is 7410. |
| Operation Timeout (seconds) (optional) | timeout | Number of seconds to wait for message from failed node. |
| Node name | nodename | Name or IP address of the node to be fenced. |
4.26. Multipath Persistent Reservation Fencing (Red Hat Enterprise Linux 6.7 and later)
Copy linkLink copied to clipboard!
Table 4.27, “Multipath Persistent Reservation Fencing (Red Hat Enterprise Linux 6.7 and later)” lists the fence device parameters used by
fence_mpath, the fence agent for multipath persistent reservation fencing.
| luci Field | cluster.conf Attribute | Description |
|---|---|---|
| Name | name | A name for the fence_mpath device. |
| Devices (Comma delimited list) | devices | Comma-separated list of devices to use for the current operation. Each device must support SCSI-3 persistent reservations. |
| Use sudo when calling third-party software | sudo | Use sudo (without password) when calling 3rd party software. |
| Path to sudo binary (optional) | sudo_path | Path to sudo binary (default value is /usr/bin/sudo. |
| Path to mpathpersist binary (optional) | mpathpersist_path | Path to mpathpersist binary (default value is /sbin/mpathpersist. |
| Path to a directory where the fence agent can store information (optional) | store_path | Path to directory where fence agent can store information (default value is /var/run/cluster. |
| Power Wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
| Unfencing | unfence section of the cluster configuration file | When enabled, this ensures that a fenced node is not re-enabled until the node has been rebooted. This is necessary for non-power fence methods. When you configure a device that requires unfencing, the cluster must first be stopped and the full configuration including devices and unfencing must be added before the cluster is started. For more information about unfencing a node, see the fence_node(8) man page. |
| Key for current action | key | Key to use for the current operation. This key should be unique to a node and written in /etc/multipath.conf. For the "on" action, the key specifies the key use to register the local node. For the "off" action, this key specifies the key to be removed from the device(s). This parameter is always required. |
| Delay (optional) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
4.27. RHEV-M REST API
Copy linkLink copied to clipboard!
Table 4.28, “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.
| 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 host name 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 parameter. |
| Use SSL | ssl | Use SSL connections to communicate with the device. |
| Power Wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
| Port (Outlet) Number | port | Physical plug number or name of virtual machine. |
| Delay (optional) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
Figure 4.20, “RHEV-M REST API” shows the configuration screen for adding an RHEV-M REST API device
Figure 4.20. 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
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>
<fencedevices>
<fencedevice agent="fence_rhevm" ipaddr="192.168.0.1" login="root" name="rhevmtest1" passwd="password123" \
power_wait="60" ssl="on"/>
</fencedevices>
4.28. SCSI Persistent Reservations
Copy linkLink copied to clipboard!
Table 4.29, “SCSI Reservation 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.
It is recommended that devices used for the cluster volumes be specified in the format
/dev/disk/by-id/xxx where possible. Devices specified in this format are consistent among all nodes and will point to the same disk, unlike devices specified in a format such as /dev/sda which can point to different disks from machine to machine and across reboots.
| luci Field | cluster.conf Attribute | Description |
|---|---|---|
| Name | name | A name for the SCSI fence device. |
| Unfencing | unfence section of the cluster configuration file | When enabled, this ensures that a fenced node is not re-enabled until the node has been rebooted. This is necessary for non-power fence methods (that is, SAN/storage fencing). When you configure a device that requires unfencing, the cluster must first be stopped and the full configuration including devices and unfencing must be added before the cluster is started. For more information about unfencing a node, see the fence_node(8) man page. |
| Node name | nodename | The node name is used to generate the key value used for the current operation. |
| Key for current action | key | (overrides node name) Key to use for the current operation. This key should be unique to a node. For the "on" action, the key specifies the key use to register the local node. For the "off" action,this key specifies the key to be removed from the device(s). |
| Delay (optional) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
Figure 4.21, “SCSI Fencing” shows the configuration screen for adding an SCSI fence device
Figure 4.21. SCSI Fencing
The following command creates a fence device instance for a SCSI Fence device:
ccs -f cluster.conf --addfencedev scsifencetest1 agent=fence_scsi
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>
<fencedevices>
<<fencedevice agent="fence_scsi" name="scsifencetest1"/>
</fencedevices>
4.29. VMware over SOAP API
Copy linkLink copied to clipboard!
Table 4.30, “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.
| luci Field | cluster.conf Attribute | Description |
|---|---|---|
| Name | name | Name of the virtual machine fencing device. |
| IP Address or Hostname | ipaddr | The IP address or host name assigned to the device. |
| IP Port (optional) | ipport | The TCP port to use for connection with the device. The default port is 80, or 443 if Use SSL is selected. |
| 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 parameter. |
| Power Wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
| VM name | port | Name of virtual machine in inventory path format (for example, /datacenter/vm/Discovered_virtual_machine/myMachine). |
| VM UUID | uuid | The UUID of the virtual machine to fence. |
| Delay (optional) | delay | The number of seconds to wait before fencing is started. The default value is 0. |
| Use SSL | ssl | Use SSL connections to communicate with the device. |
Figure 4.22, “VMware over SOAP Fencing” shows the configuration screen for adding a VMware over SOAP fence device
Figure 4.22. 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=,
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>
<fencedevices>
<fencedevice agent="fence_vmware_soap" ipaddr="192.168.0.1" login="root" name="vmwaresoaptest1" passwd="password123" \
power_wait="60" separator="."/>
</fencedevices>
4.30. WTI Power Switch
Copy linkLink copied to clipboard!
Table 4.31, “WTI Power Switch” lists the fence device parameters used by
fence_wti, the fence agent for the WTI network 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 address or host name 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 parameter. |
| Force command prompt | cmd_prompt | The command prompt to use. The default value is ['RSM>', '>MPC', 'IPS>', 'TPS>', 'NBB>', 'NPS>', 'VMR>'] |
| Power Wait (seconds) | power_wait | Number of seconds to wait after issuing a power off or power on command. |
| Power Timeout (seconds) | power_timeout | Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. |
| Shell Timeout (seconds) | shell_timeout | Number of seconds to wait for a command prompt after issuing a command. The default value is 3. |
| Login Timeout (seconds) | login_timeout | Number of seconds to wait for a command prompt after login. The default value is 5. |
| Times to Retry Power On Operation | retry_on | Number of attempts to retry a power on operation. The default value is 1. |
| Use SSH | secure | Indicates that system will use SSH to access the device. When using SSH, you must specify either a password, a password script, or an identity file. |
| SSH Options | ssh_options | SSH options to use. The default value is -1 -c blowfish. |
| Path to SSH Identity File | identity_file | The identity file for SSH. |
| Port | port | Physical plug number or name of virtual machine. |
Figure 4.23, “WTI Fencing” shows the configuration screen for adding a WTI fence device
Figure 4.23. 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
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>
<fencedevices>
<fencedevice agent="fence_wti" cmd_prompt="VMR>" ipaddr="192.168.0.1" login="root" name="wtipwrsw1" \
passwd="password123" power_wait="60"/>
</fencedevices>
Appendix A. Revision History
Copy linkLink copied to clipboard!
| Revision History | |||
|---|---|---|---|
| Revision 4-2 | Wed Mar 8 2017 | ||
| |||
| Revision 4-1 | Fri Dec 16 2016 | ||
| |||
| Revision 3-5 | Wed Apr 27 2016 | ||
| |||
| Revision 3-4 | Wed Mar 9 2016 | ||
| |||
| Revision 2-2 | Wed Jul 8 2015 | ||
| |||
| Revision 2-1 | Thu Apr 16 2015 | ||
| |||
| Revision 1-13 | Wed Oct 8 2014 | ||
| |||
| Revision 1-11 | Thu Aug 7 2014 | ||
| |||
| Revision 1-9 | Wed Nov 20 2013 | ||
| |||
| Revision 1-4 | Mon Nov 28 2012 | ||
| |||
| Revision 1-2 | Mon Nov 28 2012 | ||
| |||
Index
Copy linkLink copied to clipboard!
A
- ACPI
- APC power switch over SNMP fence device , APC Power Switch over SNMP
- APC power switch over telnet/SSH fence device , APC Power Switch over Telnet and SSH
B
- Brocade fabric switch fence device , Brocade Fabric Switch
C
- CISCO MDS fence device , Cisco MDS
- Cisco UCS fence device , Cisco UCS
- cluster administration
- configuring ACPI, Configuring ACPI For Use with Integrated Fence Devices
D
- Dell DRAC 5 fence device , Dell Drac 5
- Dell iDRAC fence device , IPMI over LAN
E
- Eaton network power switch, Eaton Network Power Switch
- Egenera BladeFrame fence device , Egenera BladeFrame
- Emerson network power switch fence device , Emerson Network Power Switch (SNMP interface)
- ePowerSwitch fence device , ePowerSwitch
F
- fence
- configuration, Fencing Pre-Configuration
- devices, Fence Devices
- fence agent
- fence_apc, APC Power Switch over Telnet and SSH
- fence_apc_snmp, APC Power Switch over SNMP
- fence_bladecenter, IBM BladeCenter
- fence_brocade, Brocade Fabric Switch
- fence_cisco_mds, Cisco MDS
- fence_cisco_ucs, Cisco UCS
- fence_drac5, Dell Drac 5
- fence_eaton_snmp, Eaton Network Power Switch
- fence_egenera, Egenera BladeFrame
- fence_emerson, Emerson Network Power Switch (SNMP interface)
- fence_eps, ePowerSwitch
- fence_hpblade, Hewlett-Packard BladeSystem
- fence_ibmblade, IBM BladeCenter over SNMP
- fence_idrac, IPMI over LAN
- fence_ifmib, IF-MIB
- fence_ilo, Hewlett-Packard iLO
- fence_ilo2, Hewlett-Packard iLO
- fence_ilo3, IPMI over LAN
- fence_ilo3_ssh, HP iLO over SSH
- fence_ilo4, IPMI over LAN
- fence_ilo4_ssh, HP iLO over SSH
- fence_ilo_moonshot, HP Moonshot iLO
- fence_ilo_mp, Hewlett-Packard iLO MP
- fence_ilo_ssh, HP iLO over SSH
- fence_imm, IPMI over LAN
- fence_intelmodular, Intel Modular
- fence_ipdu, IBM iPDU
- fence_ipmilan, IPMI over LAN
- fence_kdump, Fence kdump
- fence_mpath, Multipath Persistent Reservation Fencing (Red Hat Enterprise Linux 6.7 and later)
- fence_rhevm, RHEV-M REST API
- fence_rsb, Fujitsu-Siemens RemoteView Service Board (RSB)
- fence_scsi, SCSI Persistent Reservations
- fence_virt, Fence Virt (Serial/VMChannel Mode)
- fence_vmware_soap, VMware over SOAP API
- fence_wti, WTI Power Switch
- fence_xvm, Fence Virt (Multicast Mode)
- fence configuration, Fencing Pre-Configuration, Configuring Fencing with Conga
- SELinux, SELinux
- fence device
- APC power switch over SNMP, APC Power Switch over SNMP
- APC power switch over telnet/SSH, APC Power Switch over Telnet and SSH
- Brocade fabric switch, Brocade Fabric Switch
- Cisco MDS, Cisco MDS
- Cisco UCS, Cisco UCS
- Dell DRAC 5, Dell Drac 5
- Dell iDRAC, IPMI over LAN
- Eaton network power switch, Eaton Network Power Switch
- Egenera BladeFrame, Egenera BladeFrame
- Emerson network power switch, Emerson Network Power Switch (SNMP interface)
- ePowerSwitch, ePowerSwitch
- Fence virt, Fence Virt (Serial/VMChannel Mode)
- Fence virt (Multicast Mode), Fence Virt (Multicast Mode)
- Fujitsu Siemens RemoteView Service Board (RSB), Fujitsu-Siemens RemoteView Service Board (RSB)
- HP BladeSystem, Hewlett-Packard BladeSystem
- HP iLO, Hewlett-Packard iLO
- HP iLO MP, Hewlett-Packard iLO MP
- HP iLO over SSH, HP iLO over SSH
- HP iLO2, Hewlett-Packard iLO
- HP iLO3, IPMI over LAN
- HP iLO3 over SSH, HP iLO over SSH
- HP iLO4, IPMI over LAN
- HP iLO4 over SSH, HP iLO over SSH
- HP Moonshot iLO, HP Moonshot iLO
- IBM BladeCenter, IBM BladeCenter
- IBM BladeCenter SNMP, IBM BladeCenter over SNMP
- IBM Integrated Management Module, IPMI over LAN
- IBM iPDU, IBM iPDU
- IF MIB, IF-MIB
- Intel Modular, Intel Modular
- IPMI LAN, IPMI over LAN
- multipath persistent reservation fencing, Multipath Persistent Reservation Fencing (Red Hat Enterprise Linux 6.7 and later)
- RHEV-M REST API, RHEV-M REST API
- SCSI fencing, SCSI Persistent Reservations
- VMware (SOAP interface), VMware over SOAP API
- WTI power switch, WTI Power Switch
- fence devices, Fence Devices
- Fence virt fence device , Fence Virt (Serial/VMChannel Mode), Fence Virt (Multicast Mode)
- fence_apc fence agent, APC Power Switch over Telnet and SSH
- fence_apc_snmp fence agent, APC Power Switch over SNMP
- fence_bladecenter fence agent, IBM BladeCenter
- fence_brocade fence agent, Brocade Fabric Switch
- fence_cisco_mds fence agent, Cisco MDS
- fence_cisco_ucs fence agent, Cisco UCS
- fence_drac5 fence agent, Dell Drac 5
- fence_eaton_snmp fence agent, Eaton Network Power Switch
- fence_egenera fence agent, Egenera BladeFrame
- fence_emerson fence agent, Emerson Network Power Switch (SNMP interface)
- fence_eps fence agent, ePowerSwitch
- fence_hpblade fence agent, Hewlett-Packard BladeSystem
- fence_ibmblade fence agent, IBM BladeCenter over SNMP
- fence_idrac fence agent, IPMI over LAN
- fence_ifmib fence agent, IF-MIB
- fence_ilo fence agent, Hewlett-Packard iLO
- fence_ilo2 fence agent, Hewlett-Packard iLO
- fence_ilo3 fence agent, IPMI over LAN
- fence_ilo3_ssh fence agent, HP iLO over SSH
- fence_ilo4 fence agent, IPMI over LAN
- fence_ilo4_ssh fence agent, HP iLO over SSH
- fence_ilo_moonshot fence agent, HP Moonshot iLO
- fence_ilo_mp fence agent, Hewlett-Packard iLO MP
- fence_ilo_ssh fence agent, HP iLO over SSH
- fence_imm fence agent, IPMI over LAN
- fence_intelmodular fence agent, Intel Modular
- fence_ipdu fence agent, IBM iPDU
- fence_ipmilan fence agent, IPMI over LAN
- fence_kdump fence agent, Fence kdump
- fence_mpath fence agent, Multipath Persistent Reservation Fencing (Red Hat Enterprise Linux 6.7 and later)
- fence_rhevm fence agent, RHEV-M REST API
- fence_rsb fence agent, Fujitsu-Siemens RemoteView Service Board (RSB)
- fence_scsi fence agent, SCSI Persistent Reservations
- fence_virt fence agent, Fence Virt (Serial/VMChannel Mode)
- fence_vmware_soap fence agent, VMware over SOAP API
- fence_wti fence agent, WTI Power Switch
- fence_xvm fence agent, Fence Virt (Multicast Mode)
- fencing
- fencing configuration, Configuring Fencing with the ccs Command
- Fujitsu Siemens RemoteView Service Board (RSB) fence device, Fujitsu-Siemens RemoteView Service Board (RSB)
H
- HP Bladesystem fence device , Hewlett-Packard BladeSystem
- HP iLO fence device, Hewlett-Packard iLO
- HP iLO MP fence device , Hewlett-Packard iLO MP
- HP iLO over SSH fence device, HP iLO over SSH
- HP iLO2 fence device, Hewlett-Packard iLO
- HP iLO3 fence device, IPMI over LAN
- HP iLO3 over SSH fence device, HP iLO over SSH
- HP iLO4 fence device, IPMI over LAN
- HP iLO4 over SSH fence device, HP iLO over SSH
- HP Moonshot iLO fence device, HP Moonshot iLO
I
- IBM BladeCenter fence device , IBM BladeCenter
- IBM BladeCenter SNMP fence device , IBM BladeCenter over SNMP
- IBM Integrated Management Module fence device , IPMI over LAN
- IBM iPDU fence device , IBM iPDU
- IF MIB fence device , IF-MIB
- integrated fence devices
- configuring ACPI, Configuring ACPI For Use with Integrated Fence Devices
- Intel Modular fence device , Intel Modular
- IPMI LAN fence device , IPMI over LAN
M
- multipath persistent reservation fence device , Multipath Persistent Reservation Fencing (Red Hat Enterprise Linux 6.7 and later)
R
- RHEV-M REST API fence device , RHEV-M REST API
S
- SCSI fencing, SCSI Persistent Reservations
- SELinux
- configuring, SELinux
T
- tables
- fence devices, parameters, Fence Devices
V
- VMware (SOAP interface) fence device , VMware over SOAP API
W
- WTI power switch fence device , WTI Power Switch
Legal Notice
Copy linkLink copied to clipboard!
Copyright © 2017 Red Hat, Inc.
This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}