Fence Device and Agent Information for Red Hat Enterprise Linux

已更新2015年二月8日02:35 - 

English 

Overview

Fencing is the disconnection of a node from shared storage. Fencing cuts off I/O from shared storage, thus ensuring data integrity. A fence device is a hardware device that can be used to cut a node off from shared storage. This can be accomplished in a variety of ways: powering off the node via a remote power switch, disabling a Fibre Channel switch port, or revoking a host's SCSI 3 reservations. A fence agent is a software program that connects to a fence device in order to ask the fence device to cut off access to a node's shared storage (via powering off the node or removing access to the shared storage by other means).

This article outlines many commercial fence devices and maps them to the  fence agents that support them. Where available, information on  specific firmware revisions is provided.

For more detailed information on fencing and fence devices, see the official product documentation:

• Red Hat Enterprise Linux 5 Fencing Overview
• Red Hat Enterprise Linux 6 Fencing overview

NOTE:

• This is not a comprehensive list of devices, and not all of these devices are supported in Red Hat Enterprise Linux or Red Hat Enterprise Virtualization.
• 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 of listing multiple outlets.
• Not every IPMI-capable device is listed here. Generally, if your device supports IPMI v1.5+ and IPMI over LAN, 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. In general, it is preferred to use the ipmilanagent on devices that properly implement IPMI. However, in some cases this is not possible due to incomplete implementations, firmware bugs, or blade chassis devices that require a slot/port parameter. In the cases where fence_ipmilan cannot be used, the native fence agent can be used instead.

Support Status

NOTE: This article does not comment on the supportability of the software fence agents that are shipped with Red Hat Enterprise Linux and Red Hat Enterprise Virtualization. It does list which specific hardware fence devices are supported for a given software fence agent. The below tables contain hardware devices that might be either unsupported or in Technology Preview status. Contact Red Hat Global Support Services to determine if your fence agent and/or device is supported.

Fence Device and Agent Matrix

Vendor /

Fence Device

Fence

Agent

Fence TypeStyle

Connection

Methods

Supports

List

Action

Tested On:

Hardware /

Firmware

SNMP

Support

IPMI

v1.5+

Support

Notes

IPMI v1.5+ Compliant Devices

over LAN

ipmilanPowerC + ipmitoolipmiN/A noyes[1]Virtualization (libvirt)xvmVirt GuestC (client/server app)

custom protocol

using multicast and

libvirt remote connections

no nono Virtualization (libvirt)virtVirt GuestC (client/server app)

custom protocol using either

multicast or serial vmchannel and

QMF/libvirt

no nono Virtualization (libvirt)virshVirt Guestpythonlibvirt remove connectionsno nono Virtualization (RHEVM)rhevmVirt GuestpythonRHEVM REST APIno nono[2]Virtualization (VMware)vmwareVirt Guest

python + fencing lib + VMware utils +

PerlVI based helper

Running vmrun/helperyes nono[3]

Virtualization

(VMware)

vmware_soapVirt Guestpython + fencing lib + python-sudsSOAP APIyes nono[4]SCSI 3 Persistent ReservationsscsiLUN accessperl + sg3_utilsioctlsN/A nono[5]General IF:MIBifmibNetwork Portpython + SNMP fencing libsnmpyes yesno APCapc

External

Power

Switch

python + fencing libssh + telnetyesAP7951 & AOS v2.7.0yesno[6][15]APCapc

External

Power

Switch

python + fencing libssh + telnetyesAP7941 & AOS v3.5.7yesno[15]APCapc

External

Power

Switch

python + fencing libssh + telnetyesAP9606 & AOS v2.5.4yesno[15]APCapc_snmp

External

Power

Switch

python + SNMP fencing libsnmpyes yesno[15]Baytech / RPCbaytech

External

Power Switch

perltelnet (ssh, kermit possible)no

RPC27-20nc +

Cyclades TS

yesno Blade Technologies / Rackswitchrackswitch

External

Power Switch

Ctelnet-likeno    BrocadebrocadeFibre Channel Portperltelnetno yesno Bull / NovaScalebullpapPower

perl

PAP console (using

vendor tools)

no yesno Cisco MDScisco_mdsNetwork Portpython + SNMP fencing libsnmpyes yesno[7]Cisco UCScisco_ucsPowerpython + fencing libhttpyes noyes[8]Dell / DRAC 3 & DRAC/MCdracPowerperltelnetnoDRAC/MC & v1.1, v1.2, v1.3read-onlyno (some models) Dell / DRAC 4dracPowerperltelnetnoDRAC 4/I & v1.0, v1.40yesno (some models) Dell / DRAC 5 / CMCdrac5Powerpython + fencing libssh + telnetN/ADRAC 5 & v1.0, v1.21yesyes Dell / iDRAC (DRAC 6)ipmilanPowerC + ipmitoolipmino noyes[9]EgeneraegeneraPowerperlsshno yesno ePowerSwitchepsPowerpython + fencing libhttpyesePowerSwitch 8M+ & v1.0.0.4some models  Fujitsu / RSBrsbPowerpython + telnet libtelnetno yesno (some models) HP / iLO, iLO2iloPowerpython + fencing libhttps (-z added always)N/AiLO & 1.91, iLO2 & 1.22, 1.50yesyes[10]HP / iLO MPilo_mpPowerpython + fencing libssh + telnetN/AiLO2 MPyesyes HP / iLO3, iLO4ipmilanPowerC + ipmitoolipmino noyes

[11]

IBM / BladeCenterbladecenterPowerpython + fencing libssh + telnetyesfirmware BRET58K rev 16yesno IBM / BladeCenteribm_bladePowerpython + SNMP fencing libsnmpyes yesno IBM / LPARlparPowerpython + fencing libssh + telnetyesHMC v3, HMC v4nono IBM / RSArsaPowerpython + fencing libssh + telnetN/A yesyes Intel / Modular Server SystemintelmodularPowerpython + SNMP fencing libsnmpyesMFSYS25 & v2.6yesyes[12]Intel / IMMipmilanPowerC + ipmitoolipmino noyes McDATAmcdata

Fibre

Channel Port

perltelnetno

firmware

v01.03.00

v02.00.00

v04.01.00

yesno QLogic / SANboxsanbox2

Fibre

Channel Port

python + fencing libssh + telnetyes yesno Sun / ILOMipmilanPowerC + ipmitoolipmino noyes Vixel (Emulex)vixel

Fibre

Channel Port

perltelnetno yes  WTI Remote Reboot PDUswti

External

Power

Switch

python + fencing libssh + telnetyes

RSM-8R4, MPC-8H, IPS series, VMR-8,

NPS series

yesno[13]WTI Serial Power Control Devicesrps10External Power SwitchCserial RS232noRPS-10HDnono[14]

Notes:
1. ipmitool works with IPMI v1.5 and v2.0+
2. RHEL 5.7+, RHEL 6.2+.  Red Hat Enterprise Virtualization 3 or later.
3. fence_vmware is not supported. It was superseded by fence_vmware_soap. See [4].
4. RHEL 5.7+, RHEL 6.2+.  VMware vSphere ESX 4.1.  Version 5.0 requires a VMware workaround.
5. Fibre Channel or iSCSI SAN storage: SAN device must be SCSI3 Persistent Reservation Compliant with support for preempt-and-abort command. Seethis article for more information.
6. SSH has to be set to protocol 1 and des/blowfish cipher different menu for admin/user (valid for every APC)
7. Cisco MDS 9124 & 9134 (RHEL 5.4+)
8. The Cisco UCS blades do support ipmi-based fencing, but this requires connecting to each blade individually. The Cisco UCS-based fence agent allows fencing to be done by connecting to the UCS chassis and specifying the blade by name.
9. ipmi over LAN support may be disabled by default on iDRAC/DRAC6 hardware. Follow the manufacturer's instructions for enabling ipmi over LAN support so that the fence_ipmilan agent will work.
10. fence_ipmilan can also be used with iLO2 version 2.00 and later.
11. fence_ipmilan must be used with the -P option to enable Lanplus. It also requires usage of the -T parameter to provide at least a 4 second timeout rather than the default fence_ipmilan default of 2 seconds. The -T parameter is provided in versions of fence_ipmilan from Red Hat Enterprise Linux 5.5.z and up.
12. According to the manual, SNMP access is read-only, but it is in fact read-write. IPMI v2 compatible.
13. When using SSH, sometimes it is necessary to set login_timeout to 10. NPS models are supported with RHEL 5.7, 6.1, and later.
14. Two-node clusters only.
15. Newer revisions of APC switched rack PDUs, particularly those with AOS version 5.0 or later., are not known to work well with fence_apc. Please usefence_apc_snmp instead. The AOS version can be seen immediately after logging in.

Supported External Fence Device Models

ManufacturerModelAPCSwitched Rack PDU AP7902, AP7902JAPCSwitched Rack PDU AP7930, AP7998APCSwitched Rack PDU AP7900APCSwitched Rack PDU AP7901APCSwitched Rack PDU AP7911, AP7911AAPCSwitched Rack PDU AP7920APCSwitched Rack PDU AP7921APCSwitched Rack PDU AP8941 (using SNMP)WTIIPS-15WTIIPS-1600WTIIPS-1600-CEWTIIPS-400WTIIPS-400-CEWTIIPS-800WTIIPS-800-CEWTIMPC-8H (5.3)WTINBB-1600WTINBB-1600-CEWTIRPS-10 Series (Note: Two-node clusters only)WTIRSM-8R4WTITPS-2WTINPS SeriesWTI

VMR Series

Supported SAN-Based Fence Device Models

ManufacturerModelBrocadeSilkworm 2400BrocadeSilkworm 2800BrocadeSilkworm 3200Brocade200EBrocade300Brocade4100Brocade4900Brocade5100Brocade5480DellPowerVault 56FMcDataSphereon 4500Vixel9200

• 产品 
• Red Hat Enterprise Linux

• 类别 
• Supportability

• 元件 
• cluster 
• rhev-hypervisor

• 标记 
• fencing 
• fence_agent 
• hardware 
• rhel_4 
• rhel_5 
• rhel_6 
• rhev 
• rhev_manager

• 文章类型 
• General