LifeKeeper for Linux
7.4
Storage and Adapter Configuration

January 2012

This document and the information herein is the property of SIOS Technology Corp. (previously
known as SteelEye® Technology, Inc.) and all unauthorized use and reproduction is prohibited. SIOS
Technology Corp. makes no warranties with respect to the contents of this document and reserves
the right to revise this publication and make changes to the products described herein without priornotification. It is the policy of SIOS Technology Corp. to improve products as new technology,
components and software become available. SIOS Technology Corp., therefore, reserves the right tochange specifications without prior notice.
LifeKeeper, SteelEye and SteelEye DataKeeper are registered trademarks of SIOS Technology
Corp.
Other brand and product names used herein are for identification purposes only and may be
trademarks of their respective companies.
To maintain the quality of our publications, we welcome your comments on the accuracy, clarity,organization, and value of this document.
Address correspondence to:
ip@us.sios.com
Copyright © 2012
By SIOS Technology Corp.
San Mateo, CA U.S.A.
All rights reserved

Table of Contents
Storage and Adapter Configuration Version 7.4

1

HP Multipath I/O Configurations

14

EMC PowerPath Multipath I/O Configurations

16

IBM SDD Multipath I/O Configurations

19

Hitachi Dynamic Link Manager Software Multipath I/O Configurations

20

Device Mapper Multipath I/O Configurations

28

Table of ContentsiStorage and Adapter Configuration Version 7.4
Item

Multipath
I/O and
Redundant
Controllers

Description
There are several multipath I/O solutions either already available or currently being
developed for the Linux environment. SIOS Technology Corp. is actively working
with a number of server vendors, storage vendors, adapter vendors and driver
maintainers to enable LifeKeeper to work with their multipath I/O solutions.
LifeKeeper’s use of SCSI reservations to protect data integrity presents some special
requirements that frequently are not met by the initial implementation of thesesolutions.
Refer to the technical notes below for supported disk arrays to determine if a given
array is supported with multiple paths and with a particular multipath solution. Unlessan array is specifically listed as being supported by LifeKeeper with multiple paths
and with a particular multipath solution, it must be assumed that it is not.

LifeKeeper for Linux1

Storage and Adapter Configuration Version 7.4

Description

Item
Heavy I/O in Multipath
Configurations

In multipath configurations, performing heavy I/O while paths are being
manipulated can cause a system to temporarily appear to be
unresponsive. When the multipath software moves the access of a
LUN from one path to another, it must also move any outstanding I/Os
to the new path. The rerouting of the I/Os can cause a delay in the
response times for these I/Os. If additional I/Os continue to be issued
during this time, they will be queued in the system and can cause asystem to run out of memory available to any process. Under very
heavy I/O loads, these delays and low memory conditions can cause
the system to be unresponsive such that LifeKeeper may detect aserver as down and initiate a failover.
There are many factors that will affect the frequency at which this issue
may be seen.
l

The speed of the processor will affect how fast I/Os can bequeued. A faster processor may cause the failure to be seen
more frequently.

l

The amount of system memory will affect how many I/Os can bequeued before the system becomes unresponsive. A systemwith more memory may cause the failure to be seen lessfrequently.

l

The number of LUNs in use will affect the amount of I/O that canbe queued.

lCharacteristics of the I/O activity will affect the volume of I/Oqueued. In test cases where the problem has been seen, thetest was writing an unlimited amount of data to the disk. Most
applications will both read and write data. As the reads areblocked waiting on the failover, writes will also be throttled,
decreasing the I/O rate such that the failure may be seen lessfrequently.

For example, during testing of the IBM DS4000 multipath configuration
with RDAC, when the I/O throughput to the DS4000 was greater than
190 MB per second and path failures were simulated, LifeKeeper would(falsely) detect a failed server approximately one time out of twelve.
The servers used in this test were IBM x345 servers with dual Xeon
2.8GHz processors and 2 GB of memory connected to a DS4400 with 8
volumes (LUNs) per server in use. To avoid the failovers, theLifeKeeper parameter LCMNUMHBEATS(in /etc/default/LifeKeeper) was increased to 16. The change
to this parameter results in LifeKeeper waiting approximately 80
seconds before determining that an unresponsive system is dead,rather than the default wait time of approximately 15 seconds.
Special Considerations for With some large storage configurations (for example, multiple logical
Switchovers with Large
Storage Configurations

2

Storage and Adapter Configuration Version 7.4

Storage and Adapter Configuration Version 7.4

Item

Description
volume groups with 10 or more LUNs in each volume group), LifeKeeper
may not be able to complete a sendevent within the default timeout of
300 seconds when a failure is detected. This results in the switchoverto the backup system failing. All resources are not brought in-service
and the following error message is logged in the LifeKeeper log:***ERROR*** recover[51,mes.C]:lcdsendremote:::receive(300) did not receive
message within 300 seconds on
incoming_mailbox PM1798.21634/opt/LifeKeeper/bin/recover:lcdsendremote transfer resource "<resourcename>" to "<resource-name>" on machine"system-name" failed (rt=-1)

HP MA8000
HP MSA1000 and
MSA1500

HP 3PAR
F200/F400/T400/T800

The recommendation with large storage configurations is to change
SCSIERROR from “event” to “halt” in the /etc/default/LifeKeeper file.
This will cause LifeKeeper to perform a “halt” on a SCSI error.
LifeKeeper will then perform a successful failover to the backup
system.
Certified by SIOS Technology Corp. with QLogic 2200 adapters. Use
the qla2200 driver version 6.04.50 or later.
Certified by SIOS Technology Corp. with HP FCA2214 (QLA 2340)
adapters in both single and multiple path configurations. Configuration
requirements and notes for support of the MSA1000 in a multipath
configuration are provided in the separate HP Multipath I/O
Configurations section.
The HP 3PAR was tested by a SIOS Technology Corp. partner with thefollowing configurations: HP 3PAR T400 (Firmware (InForm OS)
version 2.3.1 MU4) using HP 82Q 8Gb Dual Port PCI-e FC HBA
AJ764A (Firmware version 5.03.02, driver version 8.03.01.05.05.06-k)with DMMP (device-mapper-1.02.55-2.el5, device-mapper-multipath0.4.7-42.el5).

The test was performed with LifeKeeper for Linux v7.3 using RHEL 5.6(kernel 2.6.18-238.el5).
Certified by SIOS Technology Corp. with HP FCA2214 (QLA 2340)
HP EVA 3000/5000 andadapters in both single and multiple path configurations. Configuration
EVA 4X00/6X00/8X00(XCS 6.x series firmware) requirements and notes for support of the EVA in a multipath
configuration are provided in the separate HP Multipath I/O
Configurations section.
Certified by Hewlett-Packard Company. Both single path and multipath
HP EVA4400
configuration require the DMMP Recovery Kit and the HP DMMP
software.The EVA4400 has been qualified to work with LifeKeeper on
Red Hat EL 5 Update 3 and Novell SLES 11. Novell testing wascompleted by the HP Storage Group.
Certified by Hewlett-Packard Company. Both single path and multipath
HP EVA6400/8400
configuration require the DMMP Recovery Kit and the HP DMMPLifeKeeper for Linux

3

Storage and Adapter Configuration Version 7.4

Item

Description

HP EVA 8100 (XCS 6.x
series firmware)

software.The EVA6400/8400 has been qualified to work with
LifeKeeper on Red Hat EL 5 Update 3 and Novell SLES 11. Novell
testing was completed by the HP Storage Group.
Certified by a SIOS Technology Corp. partner with HP FC 1142SR
adapters in DMMP multiple path configurations. Configuration
requirements and notes for support of the EVA in a multipath
configuration are provided in the separate Device Mapper Multipath I/O
Configurations section.

EVA 8100 was tested with XCS v6.200 firmware with device-mappermultipath-0.4.7.-23.el5 with the DMMP Recovery Kit v7.3 with RHEL
5.3.
Certified by SIOS Technology Corp. with Smart Array 5i and 532 host
HP MSA500 (formerly
adapters with the cciss driver.LifeKeeper does support the HP Modular
known as Smart Array
Cluster Storage or SACS) Smart Array 500 system in a redundant controller configuration. This is
not a multipath I/O solution, but it does eliminate all potential storagerelated single points of failure.

HP MSA500 G2

HP MSA2000fc

HP MSA2000i

HP MSA2000sa

HP MSA 2300fc

4

Note: LifeKeeper only supports LUN numbers 00 thru 99.
Certified by SIOS Technology Corp. with the Smart Array 6i and 642
host adapter with the cciss driver. LifeKeeper does support the HP
Modular Smart Array 500 G2 system in a redundant controller
configuration with both the 2-port and 4-port EMU modules. This is notsupported in a multipath I/O configuration, but it does eliminate all
potential storage-related single points of failure. The 4-port module
provides support for up to a 4-node cluster. LifeKeeper does not support
the HP Smart Array Multipath Software for the MSA500 G2.
Note: LifeKeeper only supports LUN numbers 00 thru 99.
Certified by Hewlett-Packard Company with Fibre Channel in both
single path and multipath configurations. Models tested were the
MSA2012fc and the MSA2212fc with the QLogic QMH2462 HBA using
driver version 8.01.07.25 in a single path configuration. The multipath
configuration testing was completed using the same models with HP
DMMP and the LifeKeeper DMMP Recovery Kit.
Certified by Hewlett-Packard Company with iSCSI in a multipath
configuration. The model used for testing was the MSA2012i with HP
DMMP. Single path testing was not performed by HP; however, SIOS
Technology Corp. supports single path configurations with HP DMMP
and the LifeKeeper DMMP Recovery Kit.
Certified by Hewlett-Packard Company with SA in both single path andmultipath configurations. The model used for testing was the
MSA2012sa. Both single path and multipath configuration require the
DMMP Recovery Kit and the HP DMMP software. HP supports directconnect configurations only at this time.
Certified by Hewlett-Packard Company with Fibre Channel in both
single and multipath configurations. The model tested was theStorage and Adapter Configuration Version 7.4

Storage and Adapter Configuration Version 7.4

Description

Item

HP MSA 2300i

HP MSA 2300sa

HP P2000 G3 MSA SAS

HP P4000/P4300 G2

HP P4500 G2
HP P6300 EVA FC

HP P9500/XP

MSA2324fc with the HP AE312A (FC2142SR) HBA using driver
version 8.02.09-d0-rhel4.7-04 in a single path configuration. The
multipath configuration testing was completed using the same modelwith HP DMMP and the LifeKeeper DMMP Recovery Kit.
Certified by Hewlett-Packard Company. Both single path and multipath
configuration require the DMMP Recovery Kit and the HP DMMP
software.
Certified by Hewlett-Packard Company. Both single path and multipath
configuration require the DMMP Recovery Kit and the HP DMMP
software.Only MSA2300sa rack and tower configurations with DMMP
are supported. Blade configurations with LifeKeeper are not supported.
Certified by SIOS Technology Corp. in multipath configurations using
the Device Mapper Multipath Recovery Kit. LifeKeeper for Linux can
support up to 11 LUNs in a single cluster with the P2000 G3 SAS array.
Certified by SIOS Technology Corp. in both a single path and multipath
configuration on RHEL 5.5 using the built-in SCSI support in the core of
LifeKeeper with iSCSI Software Initiators. Model tested was the HP
P4300 G2 7.2TB SAS Starter SAN BK716A. The default kit supports
single path storage as well as some multipath storage. In general, themultipath storage is limited to active/passive configurations.
Certified by Hewlett-Packard Company guaranteeing the compatibilityof P4500 with P4000 (shown above).
This storage unit was tested by a SIOS Technology Corp. partner inmultipathconfiguration on RHEL 6.1 using the Device Mapper Multipath
Recovery Kit.
Certified by Hewlett-Packard Company using SteelEye LifeKeeper forLinux v7.2 or later. Model tested was the HP P9500/XP and has been
qualified to work with LifeKeeper on the following:l

Red Hat Enterprise for 32-bit, x64 (64-bit; Opteron and Intel
EMT64)RHEL 5.3, RHEL 5.4, RHEL 5.5l

SuSE Enterprise Server for 32-bit, x64 (64-bit; Opteron and Intel
EMT64)SLES 10 SP3, SLES 11, SLES 11 SP1

HP XP20000/XP24000

l Native or Inbox Clustering Solutions RHCS and SLE HA
Certified by SIOS Technology Corp. using LifeKeeper forLinux with
DMMP ARK in RHEL 5, SLES10 and SLES 11,configured as multipath
by DMMP. The model numbers of tested storage are XP20000 andXP24000. The connection interface is FC. The model number of tested
HBA is QLogic QMH2562 and firmware is 4.04.09; driver version is
8.03.00.10.05.04-k. SIOS Technology Corp. recommends that userchange setting of path_checker into readsector0 in XP storage.

LifeKeeper for Linux

5

Storage and Adapter Configuration Version 7.4

Item

Description

IBM DS4000 Storage(formerly known as IBM
FAStT)

Certified by SIOS Technology Corp. with QLogic 2200 and 2340
adapters in both single and multiple path configurations. Use
the qla2200 or qla2300 driver, version 6.03.00 or later, as defined byIBM.When using IBM DS4000 storage arrays systems with Emulex FC
adapters, use the lpfc driver versions specified in the Emulex
Drivers item below. Single path (i.e. single loop) support: In a single
path configuration, a fibre channel switch or hub is required for
LifeKeeper to operate properly. Multiple path (i.e. dual loop) support:
Multiple paths are supported with the DS4000 storage array models thatare released with RDAC support (currently the DS4300, DS4400 andDS4500 models). Fibre channel switches and hubs are not requiredwith multiple path configurations with RDAC. RDAC is a software
package that handles path failovers so that an application is notaffected by a path failure. The steps to install and setup RDAC areslightly different depending on the version being used. Refer to the IBM
RDAC documentation for the instructions to install, build and setup.
Certified by partner testing in a multipath configuration using IBM
RDAC. Please consult the IBM website to obtain the supported RDAC
drivers for your distribution.
Certified by SIOS Technology Corp. in single path and multipath
configurations on Red Hat Enterprise Linux Server Release 5.5(Tikanga), HBA: QLE2560, QLE2460, RDAC: RDAC
09.03.0C05.0331. RDAC is needed for both single path and multipath.

IBM DS5000

IBM DS3500(FC Model)

IBM DS3400 Storage

IBM System Storage
DS3300IBM System StorageDS3200IBM DS400
IBM San Volume6

Note: SAS and iSCSI connect are not supported.
Certified by SIOS Technology Corp. with QLogic 2300 adapters in both
single and multiple path configurations. Use
the qla2200 or qla2300 driver, version 6.03.00 or later, as defined byIBM. Please refer to the table entry for IBM DS4000 Storage for more
information on single and multiple path support.
Certified by SIOS Technology Corp. with iSCSI Software Initiators.
This storage device works in a two node LifeKeeper cluster in both
single and multipath configurations. It is required that the IBM RDAC
driver be installed on both servers for either single or multipath
configurations. If you are using a multipath configuration, you must set
SCSIHANGMAX to 50 in the /etc/default/LifeKeeper file.Please consult
the IBM website to obtain the supported RDAC drivers for your
distribution.
Certified by SIOS Technology Corp. with the IBM SAS HBA(25R8060). This storage device works in a two node LifeKeeper cluster
in both single and multipath configurations. It is required that the IBM
RDAC driver be installed on both servers for either single or multipath
configurations. Please consult the IBM website to obtain the supported
SAS and RDAC drivers for your Linux distribution.
Certified by SIOS Technology Corp. in single path configurations only.
Use the firmware version 7.01 build 0838 or later, as defined by IBM.
Certified by partner testing in a single path configuration. Certified by

Storage and Adapter Configuration Version 7.4

Storage and Adapter Configuration Version 7.4

Item

Description

SIOS Technology Corp. in multipath configurations using the SDD
Recovery Kit and the Device Mapper Multipath Recovery Kit.
Certified by partner testing with IBM TotalStorage FC2-133 Host Bus
IBM eServer xSeries
Adapters in multiple path configurations. Use the qla2300 driver,
Storage Solution Server
Type445-R / Type445-FR version 7.00.61(non-failover) or later, as defined by IBM.Multiple path
support: Multiple paths are supported with the IBM eServer xSeries
for SANmelody
Storage Solution Server Type445-R / Type445-FR for SANmelody,using the Multipath Linux Driver for IBM SANmelody Solution Server,
version 1.0.0 or later.
Dell PowerVault with Dell SIOS Technology Corp. has certified the Dell PowerVault storage arrayfor use in a 2-node cluster with the Dell PERC 2/DC, Dell PERC 4/DC,
PERC and LSI Logic
and LSI Logic MegaRAID Elite 1600 storage controllers, as long as the
MegaRAID controllers
following set of configuration requirements are met. (Note that the Dell
PERC 3/DC is the OEM version of the MegaRAID Elite 1600.) These
requirements are necessary because these host-based RAID
controllers do not provide support for SCSI reservations and uniquedevice IDs, which LifeKeeper normally requires.
Controller (SVC)

1. The Dell PowerVault storage should not be mixed with any othertypes of shared storage to be managed by LifeKeeper within thesame cluster.
2. Follow the instructions provided with your hardware for
configuring the Dell PowerVault storage and the controllers foruse in a cluster. Specifically, this includes getting into thecontroller firmware setup screens simultaneously on both
systems, selecting the adapter properties page, setting “Cluster
Mode” to “Enabled”, and setting the “Initiator ID” to 6 on one
system and to 7 on the other. You should then make sure thatboth controllers can see the same LUNs, and that theLinuxmegaraid driver is properly configured to be loaded.
3. Because this storage configuration does not support SCSI
reservations, you must disable the use of SCSI reservations
within LifeKeeper. This is accomplished by adding the option“RESERVATIONS=none” to the LifeKeeper defaults
file, /etc/default/LifeKeeper, on both nodes in the cluster. You
must manually configure a unique ID for each LUN to be
managed by LifeKeeper, using
the /opt/LifeKeeper/bin/lkID utility. The assigned ID must be
unique within the cluster and should be sufficiently constructed
to avoid potential future conflicts. The lkID utility willautomatically generate a unique ID for you if desired. Refer tothelkID(8) man page for more details about the use of the utility,
the IDs that it generates, where the ID is placed, and any
possible restrictions. Also, see the note regarding the use oflkID with LVM in the Known Issues section for the LVM
Recovery Kit.

LifeKeeper for Linux

7

Storage and Adapter Configuration Version 7.4

Description

Item

Dell | EMC (CLARiiON)
CX200

DELL MD3000

Dell PowerVault
MD3200/3220

Dell EqualLogic PS5000

4. Obtain and configure a STONITH device or devices to provide
I/O fencing. This is required due to the lack of SCSI reservation
support in this configuration. Note that for this configuration, you
should configure your STONITH devices to do a system“poweroff” command rather than a “reboot”. You must also takecare to avoid bringing a device hierarchy in-service on both
nodes simultaneously via a manual operation when LifeKeeper
communications have been disrupted for some reason.
EMC has approved two QLogic driver versions for use with this arrayand the QLA2340 adapter: the qla2x00-clariion-v6.03.00-1 and theqla2x00-clariion-v4.47.18-1. Both are available from the QLogic
website at www.qlogic.com.
Certified by Partner testing in both single path and multipath
configurations with DELL SAS 5/e adapters. This was specificallytested with RHEL4; however, there are no known issues using other
LifeKeeper supported Linux distributions or versions.RDAC is requiredfor both single path and multipath configurations.For single pathconfigurations, use the HBA host type of "Windows MSCS Cluster
single path". For multipath configurations, use the HBA host type of“Linux".
Dell PowerVault MD3200/3220 was tested by a SIOS Technology
Corp. partner with the following configuration:
DMMP with the DMMP Recovery Kit on RHEL 5.5. Must be used withthe combination of Quorum/Witness Server Kit and STONITH. To
disable SCSI reservation, set RESERVATIONS=none
in "/etc/default/LifeKeeper". Server must have interface based on IPMI
2.0.
The Dell EqualLogic was tested by a SIOS Technology Corp. partnerwith the following configurations:lDell EqualLogic PS5000 using SCSI -2 reservations with theiscsi-initiator(Software initiator) using Red Hat Enterprise LinuxES release 4 (Nahant Update 5) with kernel 2.6.9-55.EL. The
testing was completed using iscsi-initiator-utils-4.0.3.0-5 andmultipath configuration using bonding with active-backup(mode=1).

Dell EqualLogic PS5000 using DMMP with the DMMP Recovery
Kit with RHEL 5 with iscsi-initiator-utils-6.2.0.865-0.8.el5. Witha large number of luns (over 20), change the REMOTETIMEOUT
setting in /etc/default/LifeKeeper to REMOTETIMEOUT=600.
The Dell EqualLogic was tested by a SIOS Technology Corp. partnerwith the following configurations: Dell EqualLogic
PS4000/4100/6000/6100/6500/6010/6510 using DMMP with the DMMP
Recovery Kit with RHEL 5.3 with iscsi-initiator-utils-6.2.0.868-0.18.el5.
With a large number of luns (over 20), change the REMOTETIMEOUT
setting in /etc/default/LifeKeeper to REMOTETIMEOUT=600.
lDell EqualLogic
PS4000/4100/6000/6100
6500/6010/6510

8

Storage and Adapter Configuration Version 7.4

Storage and Adapter Configuration Version 7.4

Item
FalconStor Network
Storage Server (NSS)

Description
Certified by SIOS Technology Corp.The following parameters should be
set in /etc/multipath.conf:
polling_interval 5

Hitachi HDS 9570V,
9970V and 9980V

no_path_retry 36
Certified by SIOS Technology Corp. in a single path configuration with
QLogic 23xx adapters. Use the qla2300 driver, version 6.04 or later.
Note: SIOS Technology Corp. recommends the use of only single
controller (i.e. single loop) configurations with these arrays, using a fibre
channel switch or hub. However, it is also possible to configure a
LifeKeeper cluster in which each server is connected directly to a
separate controller or port on the Hitachi array, without the use of aswitch or hub, as long as each server has only a single path to thestorage. It should be noted that LifeKeeper behaves quite differently
from its normal behavior in a split-brain scenario using thisconfiguration. LifeKeeper normally performs a failover of an active
hierarchy in a split-brain scenario causing the original primary node toreboot as a result of the stolen SCSI reservation. When the Hitachi
arrays are configured with the servers directly connected to multiple
controllers or ports, certain timing peculiarities within the Hitachi arrays
prevent LifeKeeper from acquiring a SCSI reservation on the backup
node and the failover attempt fails, leaving at least part of the hierarchy
running on the original primary node. For this reason, it is importantthat all LifeKeeper resources in such a configuration have a direct lineof dependencies to one of the disk resources such that no resources
can be brought in-service if the disk resources cannot be transferred.
This is particularly true of any IP resources in the hierarchy.
There are certain specific “host mode” settings required on the Hitachi
arrays in order to allow LifeKeeper to work properly in this kind of
directly connected configuration.For the 9570V array, the following
settings are required:Hitachi HDS 9980V

nStor NexStor 4320F

Host connection mode1 --> Standard mode
Host connection mode2 --> Target Reset mode (Bus Device Reset)
Third Party Process Logout Spread mode
LIP port all reset mode --> LIP port all reset mode
For the 9970V and 9980V arrays, the “host mode” must be set to“SUN”.The HDS 9980V was tested by a SIOS Technology Corp.
partner organization in a multipath configuration using DMMP on SLES9SP3 with LSI Logic Fusion HBAs. Refer to the Device Mapper
Multipath I/O Configurations section for details.
This storage was tested by a SIOS Technology Corp. partnerorganization, in a dual controller configuration with each server in a 2node cluster directly connected to a separate controller in the array.
With this configuration, the LifeKeeper behavior in a split-brain scenario
is the same as that described above for the Hitachi HDS storage

LifeKeeper for Linux

9

Storage and Adapter Configuration Version 7.4

Description

Item

ADTX ArrayMasStor
L and FC-II

Fujitsu ETERNUS3000

Fujitsu ETERNUS 6000

Fujitsu FibreCAT S80

arrays, and the same hierarchy configuration precautions should beobserved.
These storage units were tested by a SIOS Technology Corp. partnerorganization, both in a single path configuration with a switch and in adual controller configuration with each server in a 2-node cluster directly
connected to a separate controller in the array. In both configurations,the LifeKeeper behavior in a split-brain scenario is the same as that
described above for the Hitachi HDS storage arrays, and the samehierarchy configuration precautions should be observed.The
ArrayMasStor L was also tested and certified by our partnerorganization in a multipath configuration using QLogic 2340 and 2310
host bus adapters and the QLogic failover driver, version 6.06.10.
This storage unit was tested by a SIOS Technology Corp. partnerorganization in a single path configuration only, using the PG-FC105(Emulex LP9001), PG-FC106 (Emulex LP9802), and PG-PC107 hostbus adapters and the lpfc driver v7.1.14-3.
This storage unit was tested by a SIOS Technology Corp. partnerorganization in a single path configuration only, using the PG-FC106(Emulex LP9802) host bus adapter and the lpfc driver v7.1.14-3.
This array requires the addition of the following entry
to /etc/default/LifeKeeper:

ADD_LUN_TO_DEVICE_ID=TRUE
Fujitsu ETERNUS SX300 This storage unit was tested by a SIOS Technology Corp. partnerorganization in a multipath configuration only using the PG-FC106(Emulex LP9802) and PG-FC107 host bus adapters and the lpfc driverv7.1.14. The RDAC driver that is bundled with the SX300 is required.
This storage unit was tested by a SIOS Technology Corp. partner
Fujitsu ETERNUS2000
organization in a multipath configuration with dual RAID controllers
Model 50
using the PG-FC202 (LPe1150-F) host bus adapter with the EMPD
multipath driver. Firmware version WS2.50A6 and driver version
EMPD V2.0L12 were used in the testing. Testing was performed with
LifeKeeper for Linux v6.2 using RHEL4 (kernel 2.6.9-67.ELsmp) andRHEL5 (kernel 2.6.18-53.el5).
This storage unit was tested by a SIOS Technology Corp. partner
Fujitsu ETERNUS4000
organization in a multipath configuration with dual RAID controllers
Model 300
using the PG-FC202 (LPe1150-F) host bus adapter with the EMPD
multipath driver.
This storage unit was tested by Fujitsu Limited in a multipath
Fujitsu ETERNUS2000
configuration using PG-FC203L (Emulex LPe1250-F8) host bus adapter
Model 200
(Firmware version 1.11A5, driver version 8.2.0.48.2p) with EMPD
multipath driver (driver version V2.0L20, patch version T000973LP-1).
The test was performed with LifeKeeper for Linux v7.1 using RHEL5(kernel 2.6.18-164.el5).

10Storage and Adapter Configuration Version 7.4

Storage and Adapter Configuration Version 7.4

Item
Fujitsu
ETERNUS VS850
NEC iStorage Storage
Path Savior Multipath I/O

Description
Certified by vendor support statement in a single path configuration andin multipath configurations using the Device Mapper Multipath
Recovery Kit.
Protecting Applications and File Systems That Use Multipath
Devices:In order for LifeKeeper to configure and protect applications orfile systems that use SPS devices, the SPS recovery kit must be
installed.
Once the SPS kit is installed, simply creating an application hierarchy
that uses one or more of the multipath device nodes will automaticallyincorporate the new resource types provided by the SPS kit.
Multipath Device Nodes:To use the SPS kit, any file systems and raw
devices must be mounted or configured on the multipath device nodes(/dev/dd*) rather than on the native /dev/sd* device nodes.
Use of SCSI-3 Persistent Reservations:The SPS kit uses SCSI-3
persistent reservations with a "Write Exclusive" reservation type. Thismeans that devices reserved by one node in the cluster will remain
read-accessible to other nodes in the cluster, but those other nodes will
be unable to write to the device. Note that this does not mean that you
can expect to be able to mount file systems on those other nodes forongoing read-only access.
LifeKeeper uses the sg_persist utility to issue and monitor persistentreservations. If necessary, LifeKeeper will install the sg_persist(8)utility.
Hardware Requirements:The SPS kit has been tested and certified
with the NEC iStorage diskarray using Emulex LP952, LP9802, LP1050
HBAs and Emulex lpfc driver. This kit is expected to work equally wellwith other NECiStorage D and S supported by SPS.
Multipath Software Requirements: The SPS kit has been tested withSPS for Linux 3.3.001. There areno known dependencies on theversion of the SPS package installed.
Installation Requirements:SPS software must be installed prior to
installing the SPS recovery kit.
Adding or Repairing SPS Paths:When LifeKeeper brings an SPS
resource into service, it establishes a persistent reservation registeredto each path that was active at that time. If new paths are added after
the initial reservation, or if failed paths are repaired and SPS
automatically reactivates them, those paths will not be registered as apart of the reservation until the next LifeKeeper quickCheck execution
for the SPS resource. If SPS allows any writes to that path prior to thatpoint in time, reservation conflicts that occur will be logged to thesystem message file. The SPS driver will retry these IOs on theregistered path resulting in no observable failures to the application.

LifeKeeper for Linux

11

Storage and Adapter Configuration Version 7.4

Description

Item

Newtech SweeperStor
SATA and SAS

Once quickCheck registers the path, subsequent writes will be
successful.
This storage unit was tested by a SIOS Technology Corp. partnerorganization, in a multipath configuration with dual RAID controllers,
using the QLogic PCI to Fibre Channel Host Adapter for QLE2462 (withFirmware version 4.03.01 [IP], Driver version 8.02.08) with storage
firmware J200. Testing was performed with LifeKeeper for Linux v6.2
with DMMP Recovery Kit v6.2 using the following distributions andkernels:
RHEL4 DMMP
Emulex LP 11002
8.0.16.32 or later
Emulex LPe 11002 8.0.16.32 or later
Qlogic QLA 2462 8.01.07 or later
Qlogic QLE 2462 8.01.07 or later
RHEL5 DMMP
Emulex LP 11002 8.1.10.9 or later
Emulex LPe 11002 8.1.10.9 or later
Qlogic QLA 2462 8.01.07.15 or later
Qlogic QLE 2462 8.01.07.15 or later
SLES10 DMMP
Emulex LP 11002
8.1.10.9 or later
Emulex LPe 11002 8.1.10.9 or later
Qlogic QLA 2462 8.01.07.15 or later
Qlogic QLE 2462 8.01.07.15 or later

TID MassCareRAID

Note: DMMP is required for multipath configurations.
This storage unit was tested by a SIOS Technology Corp. partner withthe following single path configuration:l

Host1 Qlogic QLE2562 (HBA BIOS 2.10, driver version qla2xxx8.03.01.04.05.05-k *)l

Host2 HP AE312A (HBA BIOS 1.26, driver version qla2xxx-8.03.01.04.05.05-k*)l

The test was performed with LifeKeeper for Linux v7.3 using Red Hat
Enterprise Linux 5.5 (kernel2.6.18-194.el5)

LifeKeeper for Linux can support up to 11 LUNs in a single cluster with the
TID MassCareRAID array.

TIDMassCareRAID

12This storage unit was tested by a SIOS Technology Corp. partnerorganization in a multipath configuration using the Qlogic driver withSCSI-2 reservations with no Fibre Channel switches. Red Hat
Enterprise Linux ES release 4 Update6 was used with the 2.6.967.ELsmp kernel. The FAILFASTTIMER setting in/etc/default/LifeKeeper needs to be changed from 5 to 30.

Storage and Adapter Configuration Version 7.4

Storage and Adapter Configuration Version 7.4

Item

Description

This storage unit was tested by a SIOS Technology Corp. partnerorganization, in a multipath configuration using RDAC with Dual RAID
Controllers, using the StorageTek 4Gb PCI-E Dual FC Host Bus
Adapter and the Sun StorageTek 4Gb PCI Dual FC Network Adapter.
For other supported fibre channel arrays with QLogic adapters, use
QLogic Drivers
the qla2200 or qla2300 driver, version 6.03.00 or later.
For the supported Emulex fibre channel HBAs, you must use
Emulex Drivers
the lpfc driver v8.0.16 or later.
For supported SCSI arrays with Adaptec 29xx adapters, use
Adaptec 29xx Drivers
the aic7xxx driver, version 6.2.0 or later, provided with the OS
distribution.
DataCore SANsymphony This storage device was successfully tested with SUSE SLES 9
Service Pack 3, Device Mapper - Multipath and Qlogic 2340 adapters.
We expect that it should work with other versions, distributions andadapters; however, this has not been tested. See DataCore for specificsupport for these and other configurations.
Sun StorageTek 2540

Xiotech Magnitude 3D

One issue was found during failover testing with heavy stress runningwhere multiple server reboots would result in a server only configuring asingle path. The test configuration consisted of a 3-node cluster where
2 servers would be killed simultaneously. After the 2 servers rebooted,
about 50% of the time one server would only have a single pathconfigured. A reboot of the server would resolve the problem. Thisissue was never seen when only a single server was rebooted. Thisissue has been reported to DataCore. This item is not considered a
critical issue since at least one path continues to be available.
This storage device was successfully tested with Red Hat EL 4 Update
3 and Qlogic 2340 adapters. We expect that LifeKeeper would also
work with other versions, distributions and adapters; however, this has
not been tested. See Xiotech for specific support for these and otherconfigurations.
The Magnitude 3D was tested in a single path configuration.
During setup, one configuration issue was detected where only 8 LUNs
were configured in the OS. This is due to the Magnitude 3D specifying
in the SCSI inquiry data that it is a SCSI-2 device. The SCSI driver inthe 2.6 kernel will not automatically address more than 8 LUNs on a
SCSI-2 device unless the device is included in its exception list. The
Magnitude 3D is not in that list. Xiotech provided a workaround fortesting to issue a command to /proc/scsi/scsi to configure each LUN.

LifeKeeper for Linux

13

HP Multipath I/O Configurations

HP Multipath I/O Configurations
Item

Description

MSA1000 and
MSA1500
Multipath
Requirementswith Secure
Path

LifeKeeper supports Secure Path for multipath I/O configurations with the
MSA1000 and MSA1500. This support requires the use of the Secure Path v3.0C
or later.

HP P2000

LifeKeeper supports the use of HP P2000 MSA FC. This storage unit was tested
by SIOS Technology Corp. in a multipath configuration on RHEL 5.4.

EVA3000 and
EVA5000
Multipath
Requirementswith Secure
Path

LifeKeeper requires the following in order to support the EVA3000 and EVA5000 ina multipath I/O configuration using Secure Path:
1. EVA VCS v2.003, or v3.00 or later. For each server, use Command View
v3.00 to set the Host OS type to Custom and the Custom Mode Number
as hex000000002200282E. See the HP Secure Path Release Notes fordetailed instructions.
2. HP Secure Path v3.0C or later.

Multipath
Cluster
Installation
Using SecurePath

For a fresh installation of a multiple path cluster that uses Secure Path, performthese steps:
1. Install the OS of choice on each server.
2. Install the clustering hardware: FCA2214 adapters, storage, switches andcables.
3. Install the HP Platform Kit.
4. Install the HP Secure Path software. This will require a reboot of thesystem. Verify that Secure Path has properly configured both paths to thestorage. See Secure Path documentation for further details.
5. Install LifeKeeper.

Multipath
Support for
MSA1000 and
MSA1500 with
QLogicFailover Driver

LifeKeeper for Linux supports the use of the QLogic failover driver for multipath I/O
configurations with the MSA1000 and MSA1500. This support requires the use of
the QLogic driver v7.00.03 or later..

Multipath
Support for
EVA with
QLogicFailover Driver

LifeKeeper supports the EVA 3000/5000 and the EVA 4X00/6X00/8X00 with the
QLogic failover driver. The 3000/5000 requires firmware version 4000 or higher.
The 4000/6000/8000 requires firmware version 5030 or higher. The latest QLogic
driver supplied by HP (v8.01.03 or later) should be used. The host connection
must be "Linux". There is no restriction on the path/mode setting by LifeKeeper.
Notice that previous restrictions for a special host connection, the setting of thepreferred path/mode and the ports that can be used on the EVA do not exist forthis version of firmware and driver.

14

Storage and Adapter Configuration Version 7.4

HP Multipath I/O Configurations

Upgrading aSingle Path
MSA1000/
MSA1500 or
EVA
Configuration
to Multiple
Paths with
Secure Path

To upgrade a cluster from single path to multiple paths, perform the following
steps (this must be a cluster-wide upgrade):
1. Upgrade LifeKeeper to the latest version following the normal upgrade
procedures. This step can be accomplished as a rolling upgrade such thatthe entire cluster does not have to be down.
2. Stop LifeKeeper on all nodes. The cluster will be down until the hardware
upgrade is complete and step 5 is finished for all nodes.
3. Install/upgrade the HP Platform Kit on each node.
4. Install the HP Secure Path software on each node. This will require a
reboot of the system. Verify that Secure Path has properly configured both
paths to the storage. See Secure Path documentation for further details.
5. Start LifeKeeper. All hierarchies should work as they did before theupgrade.
Note: This is a change from how the previous version of LifeKeeper supported an
upgrade.

Secure Path
Persistent
Device Nodes

Secure Path supports “persistent” device nodes that are in the form of/dev/spdev/spXX where XX is the device name. These nodes are symbolic links
to the specific SCSI device nodes /dev/sdXX. LifeKeeper v4.3.0 or later willrecognize these devices as if they were the “normal” SCSI device nodes/dev/sdXX. LifeKeeper maintains its own device name persistence, both acrossreboots and across cluster nodes, by directly detecting if a device is /dev/sda1 or/dev/sdq1, and then directly using the correct device node.
Note: Support for symbolic links to SCSI device nodes was added in LifeKeeper
v4.3.0.

Active/Passive
Controllers andController
Switchovers

The MSA1000 implements multipathing by having one controller active with theother controller in standby mode. When there is a problem with either the active
controller or the path to the active controller, the standby controller is activated totake over operations. When a controller is activated, it takes some time for thecontroller to become ready. Depending on the number of LUNs configured on thearray, this can take 30 to 90 seconds. During this time, IOs to the storage will beblocked until they can be rerouted to the newly activated controller.

Single Path on
Boot Up Does
Not Cause
Notification

If a server can access only a single path to the storage when the system isloaded, there will be no notification of this problem. This can happen if a system isrebooted where there is a physical path failure as noted above, but transient pathfailures have also been observed. It is advised that any time a system is loaded,
the administrator should check that all paths to the storage are properly
configured, and if not, take actions to either repair any hardware problems or
reload the system to resolve a transient problem.

LifeKeeper for Linux

15

EMC PowerPath Multipath I/O Configurations

EMC PowerPath Multipath I/O Configurations

16

Storage and Adapter Configuration Version 7.4

EMC PowerPath Multipath I/O Configurations

Protecting
Applications
and File
Systems That
Use Multipath
Devices

In order for LifeKeeper to configure and protect applications or file systems thatuse EMC PowerPath devices, the PowerPath recovery kit must be installed.Once
the PowerPath kit is installed, simply creating an application hierarchy that uses
one or more of the multipath device nodes will automatically incorporate the new
resource types provided by the PowerPath kit.

Multipath
DeviceNodes

To use the PowerPath kit, any file systems and raw devices must be mounted orconfigured on the multipath device nodes (/dev/emcpower*) rather than on thenative /dev/sd* device nodes.

Use of SCSI3 PersistentReservations

The PowerPath kit uses SCSI-3 persistent reservations with a "Write Exclusive"
reservation type. This means that devices reserved by one node in the cluster willremain read-accessible to other nodes in the cluster, but those other nodes will be
unable to write to the device. Note that this does not mean that you can expect
to be able to mount file systems on those other nodes for ongoing read-onlyaccess.
LifeKeeper uses the sg_persist utility to issue and monitor persistent reservations.
If necessary, LifeKeeper will install the sg_persist(8) utility.
SCSI-3 Persistent Reservations must be enabled on a per LUN basis when using
EMC Symmetrix (including VMAX) arrays with multipathing software and
LifeKeeper. This applies to both DMMP and PowerPath.

Hardware
The PowerPath kit has been tested and certified with the EMC CLARiiON CX300
Requirements disk array using QLogic QLA2340 HBAs with the EMCrecommendedqla2xxx driver and using Emulex LP10000 HBAs with the EMCrecommended lpfc driver. The PowerPath kit has also been tested and certified
with the EMC CLARiX CX3-20 using Qlogic QLA2340 HBAs.
Note: LifeKeeper on RHEL 6 cannot support reservations connected to an EMC
Clariion.
This kit is expected to work equally well with other CLARiiON models from EMC
or models OEMed from EMC by Dell or other vendors.
Multipath
The PowerPath kit v6.4.0-2 requires PowerPath for Linux v5.3The PowerPath kit
Softwareversions prior to v6.4.0-2 requires PowerPath for Linux v4.4.x, v4.5.x, v5.0.x, or
Requirements v5.1.x
Migrating tothePowerPathv5.3 driver

Option A
1. Upgrade to the PowerPath 5.3 driver by doing the following:a. Remove the old PowerPath driverb. Install the PowerPath 5.3 driver
2. Upgrade PowerPath 6.4.0-2 kit
3. Reboot the server
Note: When the server reboots, the PowerPath 6.4.0-2 kit will be used for the
LifeKeeper PowerPath resources. If there is a problem with the Power Path 5.3

LifeKeeper for Linux

17

EMC PowerPath Multipath I/O Configurations

driver and the older PowerPath driver needs to be used, this option will require reinstalling the version of the PowerPath kit that was used before the installation of
the v6.4.0-2 kit.
Option B
1. Upgrade to the PowerPath 5.3 driver by doing the following:a. Remove the old PowerPath driverb. Install the PowerPath 5.3 driverc. Reboot the server
2. Upgrade to the PowerPath 6.4.0-2 kit and do one of the following to start thePowerPath resources using the upgraded Recovery Kit:
Option 1: Take the PowerPath resources out-of-service and then back inservice.
Note: This will require that all applications using the PowerPath devices be
stopped and then restarted. This option allows the actions to be done
serially and perhaps at different times to avoid a lot of change.
Option 2: Stop LifeKeeper (lkstop) and start LifeKeeper (lkstart). This willtake all resources out-of-service and then back in-service.
Note: As in Option 1, it will stop all applications, but this option requires
less user intervention as two commands will ensure that all PowerPathresources are using the new kit.
Option 3: Stop LifeKeeper quickly (lkstop -f) and start LifeKeeper (lkstart).
Note: This will leave the applications running while LifeKeeper reloads how
it is accessing the storage. There will be no application downtime.

18

Storage and Adapter Configuration Version 7.4

IBM SDD Multipath I/O Configurations

IBM SDD Multipath I/O Configurations
Protecting
Applications
and File
Systems That
Use Multipath
Devices

In order for LifeKeeper to configure and protect applications or file systems that use
IBM SDD devices, the SDD recovery kit must be installed.

Multipath
DeviceNodes

To use the SDD kit, any file systems and raw devices must be mounted orconfigured on the multipath device nodes (/dev/vpath*) rather than on the native/dev/sd* device nodes.

Use of SCSI3 PersistentReservations

The SDD kit uses SCSI-3 persistent reservations with a "Write Exclusive"
reservation type. This means that devices reserved by one node in the cluster willremain read-accessible to other nodes in the cluster, but those other nodes will be
unable to write to the device. Note that this does not mean that you can expect tobe able to mount file systems on those other nodes for ongoing read-only access.

Once the SDD kit is installed, simply creating an application hierarchy that uses
one or more of the multipath device nodes will automatically incorporate the new
resource types provided by the SDD kit.

LifeKeeper uses the sg_persist utility to issue and monitor persistent reservations.
If necessary, LifeKeeper will install the sg_persist(8) utility.
Hardware
The SDD kit has been tested and certified with IBM ESS, 6800 and 8100 disk
Requirements arrays and IBM SAN Volume Controller (SVC) using Qlogic QLA2340 HBAs andthe IBM-recommended qla2xxx driver. The kit is expected to work equally wellwith other IBM disk arrays and HBA adapters (Emulex) that are supported by the
SDD driver. The IBM-recommended HBA drivers must be used in all cases.
Multipath
Software
The SDD kit requires the IBM SDD driver v1.6.0.1-8 or later.
Requirements
Adding orRepairing
SDD Paths

When LifeKeeper brings an SDD resource into service, it establishes a persistentreservation registered to each path that was active at that time. If new paths areadded after the initial reservation, or if failed paths are repaired and SDD
automatically reactivates them, those paths will not be registered as a part of thereservation until the next LifeKeeper quickCheck execution for the SDD resource.
If SDD allows any writes to that path prior to that point in time, reservation conflicts
occur that will be logged in both the SDD log file as well as the system message
file. The SDD driver will retry the IOs on the registered path resulting in noobservable failures to the application. Once quickCheck registers the path,subsequent writes will be successful.

LifeKeeper for Linux

19

Hitachi Dynamic Link Manager Software Multipath I/O Configurations

Hitachi Dynamic Link Manager Software Multipath I/O
Configurations

20

Storage and Adapter Configuration Version 7.4

Hitachi Dynamic Link Manager Software Multipath I/O Configurations

Protecting
Applications
and File
Systems That
Use Multipath
Devices

In order for LifeKeeper to configure and protect applications or file systems that use
HDLM devices, the HDLM recovery kit must be installed.

Multipath
DeviceNodes

To use the HDLM kit, any file systems and raw devices must be mounted orconfigured on the multipath device nodes (/dev/sddlm*) rather than on the native/dev/sd* device nodes.

Use of SCSI3 PersistentReservations

The HDLM kit uses SCSI-3 persistent reservations with a "Write Exclusive"
reservation type. This means that devices reserved by one node in the cluster willremain read-accessible to other nodes in the cluster, but those other nodes will be
unable to write to the device. Note that this does not mean that you can expect tobe able to mount file systems on those other nodes for ongoing read-only access.

Once the HDLM kit is installed, simply creating an application hierarchy that uses
one or more of the multipath device nodes will automatically incorporate the new
resource types provided by the HDLM kit.

LifeKeeper uses the sg_persist utility to issue and monitor persistent reservations.
If necessary, LifeKeeper will install the sg_persist(8) utility.
Hardware
The HDLM kit has been tested and certified with the Hitachi AMS500 disk array
Requirements using QLogic QLA2340 HBAs and default qla2xxx driver. This kit is expected towork equally well with other Hitachi disk arrays. The HDLM kit has also beentested and certified with the SANRISE AMS series and the SANRISE USP. The
HBA and the HBA driver must be supported by HDLM.
Multipath
The HDLM kit has been tested with HDLM for Linux 05-80, 05-81, 05-90, 05-91, 05Software
92, 05-93, 05-94, 6.0.0, 6.0.1, 6.1.0, 6.1.1, 6.1.2, 6.2.0, 6.2.1, 6.3.0, 6.4.0, 6.4.1
Requirements and 6.5.0. There are no known dependencies on the version of the HDLM package
installed.
Note: The product name changed to “Hitachi Dynamic Link Manager Software(HDLM)” for HDLM 6.0.0 and later. Versions older than 6.0.0 (05-9x) are named“Hitachi HiCommand Dynamic Link Manager (HDLM)”.
Note: HDLM version 6.2.1 or later is not supported by HDLM Recovery Kit v6.4.02. If you need to use this version of HDLM, you can use HDLM Recovery Kit
v7.2.0-1 or later with LK Core v7.3.
LinuxLinux Distribution Requirements
Distribution
Requirements The HDLM kit is supported in the following distributions:
RHEL 4 (AS/ES) (x86 or x86_64) Update 1, 2, 3, 4, Update 4 Security Fix (*2),
4.5，4.5 Security Fix(*4)，4.6，4.6 Security Fix(*8)，4.7，4.7 Security Fix(*9)，
4.8 (x86/x86_64)(*1)
RHEL 5(x86 or x86_64) 5.1, 5.1 Security Fix(*5), 5.2，5.2 Security Fix(*6)，
5.3, 5.3 Security Fix(*10)，5.4 , 5.4 Security Fix (*11), 5.5 (x86/x86_64)(*1)(*1) AMD Opteron(Single Core，Dual Core) or Intel EM64T architecture CPU
with x86_64 kernel.
(*2) The following kernels are supported

LifeKeeper for Linux

21

Hitachi Dynamic Link Manager Software Multipath I/O Configurations

x86：2.6.9-42.0.3.EL，2.6.9-42.0.3.ELsmp，2.6.9-42.0.3.ELhugemem
x86_64：2.6.9-42.0.3.EL，2.6.9-42.0.3.ELsmp，2.6.9-42.0.3.Ellargesmp(*3) Hitachi does not support RHEL4 U2 environment(*4) The following kernels are supported
x86：2.6.9-55.0.12.EL，2.6.9-55.0.12.ELsmp，2.6.9-55.0.12.Elhugememx
86_64：2.6.9-55.0.12.EL，2.6.9-55.0.12.ELsmp，2.6.9-55.0.12.Ellargesmp(*5) The following kernels are supported
x86：2.6.18-53.1.13.el5，2.6.18-53.1.13.el5PAE，2.6.18-53.1.21.el5，2.6.1853.1.21.el5PAE
x86_64：2.6.18-53.1.13.el5，2.6.18-53.1.21.el5(*6) The following kernels are supported
x86：2.6.18-92.1.6.el5，2.6.18-92.1.6.el5PAE，2.6.18-92.1.13.el5，2.6.1892.1.13.el5PAE，2.6.18-92.1.22.el5，2.6.18-92.1.22.el5PAE
x86_64：2.6.18-92.1.6.el5，2.6.18-92.1.13.el5，2.6.18-92.1.22.el5(*7) The following kernels are supported
x86：2.6.9-34.0.2.EL，2.6.9-34.0.2.ELsmp，2.6.9-34.0.2.ELhugemem
x86_64：2.6.9-34.0.2.EL，2.6.9-34.0.2.ELsmp，2.6.9-34.0.2.Ellargesmp(*8) The following kernels are supported
x86：2.6.9-67.0.7.EL，2.6.9-67.0.7.ELsmp，2.6.9-67.0.7.ELhugemem，2.6.967.0.22.EL，2.6.9-67.0.22.ELsmp，2.6.9-67.0.22.ELhugemem
x86_64：2.6.9-67.0.7.EL，2.6.9-67.0.7.ELsmp，2.6.9-67.0.7.ELlargesmp，
2.6.9-67.0.22.EL，2.6.9-67.0.22.ELsmp，2.6.9-67.0.22.Ellargesmp(*9) The following kernels are supported
x86：2.6.9-78.0.1.EL，2.6.9-78.0.1.ELsmp，2.6.9-78.0.1.ELhugemem，2.6.978.0.5.EL，2.6.9-78.0.5.ELsmp，2.6.9-78.0.5.ELhugemem，2.6.9-78.0.8.EL，
2.6.9-78.0.8.ELsmp，2.6.9-78.0.8.ELhugemem, 2.6.9-78.0.17.EL，2.6.978.0.17.ELsmp，2.6.9-78.0.17.ELhugemem，2.6.9-78.0.22.EL，2.6.978.0.22.ELsmp，2.6.9-78.0.22.Elhugemem
x86_64：2.6.9-78.0.1.EL，2.6.9-78.0.1.ELsmp，2.6.9-78.0.1.ELlargesmp，
2.6.9-78.0.5.EL，2.6.9-78.0.5.ELsmp，2.6.9-78.0.5.ELlargesmp，2.6.978.0.8.EL，2.6.9-78.0.8.ELsmp，2.6.9-78.0.8.ELlargesmp，2.6.9-78.0.17.EL，
2.6.9-78.0.17.ELsmp，2.6.9-78.0.17.ELlargesmp，2.6.9-78.0.22.EL，2.6.978.0.22.ELsmp，2.6.9-78.0.22.ELlargesmp(*10) The following kernels are supported

22

Storage and Adapter Configuration Version 7.4

Hitachi Dynamic Link Manager Software Multipath I/O Configurations

x86：2.6.18-128.1.10.el5，2.6.18-128.1.10.el5PAE，2.6.18-128.1.14.el5，
2.6.18-128.1.14.el5PAE，2.6.18-128.7.1.el5，2.6.18-128.7.1.el5PAE
x86_64：2.6.18-128.1.10.el5，2.6.18-128.1.14.el5(*11) The following kernels are supported
x86：2.6.18-164.9.1.el5，2.6.18-164.9.1.el5PAE，2.6.18-164.11.1.el5，2.6.18164.11.1.el5PAE
x86_64：2.6.18-164.9.1.el5，2.6.18-164.11.1.el5(*12) The following kernels are supported
x86：2.6.9-89.0.20.EL，2.6.9-89.0.20.ELsmp，2.6.9-89.0.20.Elhugemem
x86_64：2.6.9-89.0.20.EL，2.6.9-89.0.20.ELsmp，2.6.9-89.0.20.Ellargesmp(*13) The following kernels are supported
x86：2.6.18-194.11.1.el5，2.6.18-194.11.1.el5PAE
x86_64：2.6.18-194.11.1.el5
Installation
HDLM software must be installed prior to installing the HDLM recovery kit. Also,
Requirements customers wanting to transfer their environment from SCSI devices to HDLM
devices must run the Installation Support setup script after configuring the HDLM
environment. Otherwise, sg3_utils will not be installed.
Adding orRepairing
HDLM Paths

When LifeKeeper brings an HDLM resource into service, it establishes a persistentreservation registered to each path that was active at that time. If new paths areadded after the initial reservation, or if failed paths are repaired and HDLM
automatically reactivates them, those paths will not be registered as a part of thereservation until the next LifeKeeper quickCheck execution for the HDLM
resource. If HDLM allows any writes to that path prior to that point in time,reservation conflicts that occur will be logged to the system message file. The
HDLM driver will retry these IOs on the registered path resulting in no observable
failures to the application. Once quickCheck registers the path, subsequent writes
will be successful. The status will be changed to “Offline(E)” if quickCheck detects
a reservation conflict. If the status is “Offline(E)”, customers will need to manuallychange the status to “Online” using the online HDLM command.

LifeKeeper for Linux23

Hitachi Dynamic Link Manager Software Multipath I/O Configurations

OS version / Architecture
RHEL4
U1U4

U3

U4

Security
Fix(*7)

Security
Fix(*2)

4.5
4.5

Security
Fix(*4)4.6
4.6

Security
Fix(*8)

4.7
4.7

Security
Fix(*9)4.8

x86/x86_64

HDLM

24

05-80
05-81
05-90

X

05-91
05-92

X

X

05-93

X(*3)

X

X

05-94

X(*3)

X

X

X

X

X

6.0.0

X(*3)

X

X

X

X

X

X

X

X

6.0.1

X(*3)

X

X

X

X

X

X

X

X

6.1.0

X(*3)

X

X

X

X

X

X

X

X

6.1.1

X(*3) X

X

X

X

X

X

X

X

X

6.1.2

X(*3) X

X

X

X

X

X

X

X

X

6.2.0

X(*3) X

X

X

X

X

X

X

X

X

6.2.1

X(*3) X

X

X

X

X

X

X

X

X

6.3.0

X(*3) X

X

X

X

X

X

X

X

X

6.4.0

X(*3) X

X

X

X

X

X

X

X

X

Storage and Adapter Configuration Version 7.4

Hitachi Dynamic Link Manager Software Multipath I/O Configurations

v6.0
X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

6.0.1-2

X

X

X

X

X

X

X

6.1.0-4

X

X

X

X

X

X

X

6.2.2-3

X

X

X

X

X

X

X

6.2.3-1

X

X

X

X

X

X

X

6.4.0-2

X

X

X

X

X

X

X

X

X

X

7.0.0-1

X

X

X

X

X

X

X

X

X

X

v6.0(v6.0.1-2 orlater)
v6.1(v6.1.0-5 or later)
v6.2(v6.2.0-5 or later)
v6.2(v6.2.2-1or later)
LifeKeeper
v6.3(v6.3.2-1or later)
v6.4(v6.4.0-10 orlater)
v7.0(v7.0.0-5 or later)
V7.1(v7.1.0-8 or later)

HDLM
ARK

X = supported blank = not supported

LifeKeeper for Linux

25

Hitachi Dynamic Link Manager Software Multipath I/O Configurations

RHEL5
5.1
No
5.1 Security
UpdatesFix (*5)5.2
5.2 Security
Fix (*6)

5.3
5.3 Security
Fix(*10)

5.4
5.4 Security
Fix(*11)5.5

x86/x86_64
05-80
05-81
05-90

X

05-91
05-92

HDLM

26

05-93

X

05-94

X

X

6.0.0

X

X

X

X

X

6.0.1

X

X

X

X

X

6.1.0

X

X

X

X

X

6.1.1

X

X

X

X

X

6.1.2

X

X

X

X

X

X

X

X

X

X

6.2.0

X

X

X

X

X

X

X

X

X

X

6.2.1

X

X

X

X

X

X

X

X

X

X

6.3.0

X

X

X

X

X

X

X

X

X

X

6.4.0

X

X

X

X

X

X

X

X

X

X

Storage and Adapter Configuration Version 7.4

Hitachi Dynamic Link Manager Software Multipath I/O Configurations

v6.0(v6.0.1-2
or later)
v6.1(v6.1.0-5
or later)

X

X

v6.2
(v6.2.0-5
or later)

X

X

v6.2
(v6.2.2-1
or later)

X

X

X

v6.3
LifeKeeper (v6.3.2-1
or later)

X

X

X

X

X

v6.4
(v6.4.0-10 X
or later)

X

X

X

X

X

X

X

X

X

v7.0
(v7.0.0-5
or later)

X

X

X

X

X

X

X

X

X

X

v7.1
(v7.1.0-8
or later)

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

v7.2
(v7.2.0-10
or later)
6.0.1-2

HDLM
ARK

6.1.0-4

XX

6.2.2-3

X

X

X

6.2.3-1

X

X

X

X

X

6.4.0-2

X

X

X

X

X

X

X

X

X

X

7.0.0-1

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

7.2.0-1
X = supported blank = not supported

LifeKeeper for Linux27

Device Mapper Multipath I/O Configurations

Device Mapper Multipath I/O Configurations

28

Storage and Adapter Configuration Version 7.4

Device Mapper Multipath I/O Configurations

Protecting
Applications
and File
Systems That
Use Device
MapperMultipath
DevicesMultipath
DeviceNodes

Use of SCSI3 PersistentReservations

In order for LifeKeeper to operate with and protect applications or file systems thatuse Device Mapper Multipath devices, the Device Mapper Multipath (DMMP)
Recovery Kit must be installed.
Once the DMMP Kit is installed, simply creating an application hierarchy that uses
one or more of the multipath device nodes will automatically incorporate the new
resource types provided by the DMMP Kit.
To use the DMMP Kit, any file systems and raw devices must be mounted orconfigured on the multipath device nodes rather than on the native /dev/sd* device
nodes. The supported multipath device nodes to address the full disk are /dev/dm#, /dev/mapper/<uuid>, /dev/mapper/<user_friendly_name> and/dev/mpath/<uuid>. To address the partitions of a disk, use the device nodes foreach partition created in the /dev/mapper directory.
The Device Mapper Multipath Recovery Kit uses SCSI-3 persistent reservations
with a "Write Exclusive" reservation type. This means that devices reserved by
one node in the cluster will remain read-accessible to other nodes in the cluster, but
those other nodes will be unable to write to the device. Note that this does notmean that you can expect to be able to mount file systems on those other nodes
for ongoing read-only access.
LifeKeeper uses the sg_persist utility to issue and monitor persistent reservations.
If necessary, LifeKeeper will install the sg_persist(8) utility.
SCSI-3 Persistent Reservations must be enabled on a per LUN basis when using
EMC Symmetrix (including VMAX) arrays with multipathing software and
LifeKeeper. This applies to both DMMP and PowerPath.
The Device Mapper Multipath Kit has been tested by SIOS Technology Corp. with
the EMC CLARiiON CX300, the HP EVA 8000, HP MSA1500, HP P2000, the IBM
SAN Volume Controller (SVC), the IBM DS8100, the IBM DS6800, the IBM ESS,
the DataCore SANsymphony, and the HDS 9980V. Check with your storage
vendor to determine their support for Device Mapper Multipath.
Enabling support for the use of reservations on the CX300 requires that the
hardware handler be notified to honor reservations. Set the following parameter in/etc/multipath.conf for this array:

HardwareRequirements

hardware_handler“3 emc 0 1"

The HP MSA1500 returns a reservation conflict with the default path checker
setting (tur). This will cause the standby node to mark all paths as failed. To avoid
this condition, set the following parameter in /etc/multipath.conf for this array:path_checker

readsector0

For the HDS 9980V the following settings are required:l

Host mode: 00

LifeKeeper for Linux29

Device Mapper Multipath I/O Configurationsl

System option: 254 (must be enabled; global HDS setting affecting all
servers)l

Device emulation: OPEN-V

Refer to the HDS documentation "Suse Linux Device Mapper Multipath for HDS
Storage" or "Red Hat Linux Device Mapper Multipath for HDS Storage" v1.15 orlater for details on configuring DMMP for HDS. This documentation also provides acompatible multipath.conf file.
For the EVA storage with firmware version 6 or higher, DMMP Recovery Kit v6.1.23 or later is required. Earlier versions of the DMMP Recovery Kit are supportedwith the EVA storage with firmware versions prior to version 6.
For SUSE, multipath-tools-0.4.5-0.14 or later is required.
Multipath
For Red Hat, device-mapper-multipath-0.4.5-12.0.RHEL4 or later is required.
SoftwareRequirements It is advised to run the latest set of multipath tools available from the vendor. The
feature content and the stability of this multipath product are improving at a very
fast rate.
Some storage vendors such as IBM have not certified DMMP with SLES 11 at this
Linux
time.
Distribution
Requirements SIOS Technology Corp. is currently investigating reported issues with DMMP,SLES 11, and EMCs CLARiiON and Symmetrix arrays.
While running IO tests on Device Mapper Multipath devices, it is not uncommon foractions on the SAN, for example, a server rebooting, to cause paths to temporarily
be reported as failed. In most cases, this will simply cause one path to fail leaving
other paths to send IOs down resulting in no observable failures other than a small
performance impact. In some cases, multiple paths can be reported as failed
leaving no paths working. This can cause an application, such as a file system or
database, to see IO errors. There has been much improvement in Device Mapper
Multipath and the vendor support to eliminate these failures. However, at times,
these can still be seen. To avoid these situations, consider these actions:
Transient
path failures

1. Verify that the multipath configuration is set correctly per the instructions of
the disk array vendor.
2. Check the setting of the “failback” feature. This feature determines how
quickly a path is reactivated after failing and being repaired. A setting of“immediate” indicates to resume use of a path as soon as it comes backonline. A setting of an integer indicates the number of seconds after a pathcomes back online to resume using it. A setting of 10 to 15 generally
provides sufficient settle time to avoid thrashing on the SAN.
3. Check the setting of the "no_path_retry" feature. This feature determines
what Device Mapper Multipath should do if all paths fail. We recommend asetting of 10 to 15. This allows some ability to "ride out" temporary events
where all paths fail while still providing a reasonable recovery time. The

30

Storage and Adapter Configuration Version 7.4

Device Mapper Multipath I/O Configurations

LifeKeeper DMMP kit will monitor IOs to the storage and if they are notresponded to within four minutes LifeKeeper will switch the resources to thestandby server. NOTE: LifeKeeper does not recommend setting "no_path_
retry" to "queue" since this will result in IOs that are not easily killed. The
only mechanism found to kill them is on newer versions of DM, the settingsof the device can be changed:/sbin/dmsetup message -u 'DMid' 0 fail_if_no_path
This will temporarily change the setting for no_path_retry to fail causing any
outstanding IOs to fail. However, multipathd can reset no_path_retry to thedefault at times. When the setting is changed to fail_if_no_path to flush
failed IOs, it should then be reset to its default prior to accessing the device(manually or via LifeKeeper).
If "no_path_retry" is set to "queue" and a failure occurs, LifeKeeper willswitch the resources over to the standby server. However, LifeKeeper will
not kill these IOs. The recommended method to clear these IOs is through areboot but can also be done by an administrator using the dmsetup
command above. If the IOs are not cleared, then data corruption can occur
if/when the resources are taken out of service on the other server thereby
releasing the locks and allowing the "old" IOs to be issued.

LifeKeeper for Linux

31