Copyright (c) 2010 by Red Hat, Inc. All rights reserved.
Fence device and agent information for RedHat Enterprise Linux
This article outlines many commercial fence devices and maps them to which fence agentsthey are supported by. Where available information on specific firmware revisions exists, itis provided.
is the disconnection of a node from shared storage. Fencing cuts off I/O fromshared storage, thus ensuring data integrity. A
is a hardware device that canbe used to cut a node off from shared storage. This can be accomplished in a variety ofways: powering off the node via a remote power switch, disabling fibre channel a switch portor revoking a host's SCSI 3 reservations. For more detailed information on what fencing and fence devices are, please see the officialRHEL documentation:http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/ Cluster_Suite_Overview/s2-fencing-overview-CSO.html
Every SNMP fence agent has support for SNMP v1/2c/3
N/A in "Supports List Action" indicates that this device can only access one machine and is not capable oflisting multiple outlets.
This is a comprehensive list of devices. Not all of these devices are supported in Red Hat EnterpriseLinux or Red Hat Enterprise Virtualization. Refer toFence Support Matrix for Red Hat Enterprise LinuxHigh Availability/Clustering and Red Hat Enterprise Virtualizationto determine if a particular fence agent issupported on your product.
Not every IPMI-capable device is listed here. Generally, if your device supports IPMI v1.5+ and IPMI overLan, fence_ipmilan is supported for that device.
Any device that has "yes" in the IPMI v1.5+ Support column can be used with the fence_ipmilan agent. Ingeneral, it is preferred to use the ipmilan agent on devices that properly implement IPMI. However, in somecases this is not possible (due to incomplete implementations, firmware bugs or blade chassis devices thatrequire a slot/port parameter). In the cases where fence_ipmilan cannot be used, the native fence agentcan be used instead.