HP Serviceguard for Linux Certification Matrix, July 2014

ManualsBrandsHP ManualsSoftwareHP SAP Linux Serviceguard Cluster Extension

HP ProLiant and 3

party industry standard servers

Supported with HP Serviceguard for Linux A.11.18

Notes continued:

(15) For the manuals and software for HPDM Multipath see

http://www.hp.com/go/devicemapper

. Serviceguard for Linux A.11.18 supports

Device Mapper multipathing (DM-MPIO) with HP Fibre Channel and Serial Attached SCSI (SAS) arrays with the following restrictions:

a) The HPDM Multipath tools and documentation must be used if required by array documentation. Only the distributions listed are

supported.

b) LockLUN is supported with DM-MPIO on Red Hat 5.1 and later and Red Hat 4 U5 and later with HPDMtools3.0 and later. LockLUN is

supported with DM-MPIO on SLES10 SP2 and later with HPDMtools4.0 and later. If DM is used with LockLUN, it must be used for all

nodes in the cluster. For LockLUN support, Serviceguard for Linux version A.11.18.02 or later MUST be used. If used for LockLUN

DM-MPIO must be used on all nodes. Device alias names are not allowed for LockLUN. The device names should be in the format of

/dev/mapper/mpathXpY or /dev/mapper/mpathX-partY on SLES (X can be different on different nodes, but not Y).

c) DM-MPIO can be used for other Serviceguard for Linux shared storage with any distribution supported by the HPDM Multipath tools.

Also, DM-MPIO delivered with the distribution is supported if it is also supported by the array (HP and 3

party).

d) To use the disk monitor with HPDM Multipath devices see the section

Monitoring Multipath Devices

below.

e) Serviceguard for Linux Extended Distance Cluster (XDC) is not supported with DM-MPIO.

(16) Non-HP servers are supported with any HP FC HBA supported in those servers with the listed HP and Hitachi storage arrays.

(17) HP StorageWorks EVA supported with firmware v3.01 or later.

(18) Supported with Red Hat EL 4, Red Hat 5, and SLES10. PowerPath 4.3.3 and above. PowerPath must be used for multipath and it is

supported for LockLUN. If a version of PowerPath earlier than 4.5 is used, search for article "emc137801" on EMC PowerLink at

http://powerlink.emc.com.

(19) SG/LX on VMware guest requires storage that supports SCSI “Persistent Reservation” and is not supported with MSA500 or MSA500 G2.

(20) See the release notes for multipath options with the MSA500 G2. Multipath for LockLUN is not supported with the MSA500 G2.

(21) Use of fibre channel switches is recommended. Direct attached is with Quorum Service is supported. LockLUN is not recommended with

MSA2300FC when direct attached. If a node loses its connection to the Primary controller on the MSA2300 and another node fails, the first

node may not be able to access the LockLUN before a timeout. In that case, both nodes may fail.

(22) Any restrictions related to HDS or Hitachi storage listed on

http://www.hp.com/products1/serverconnectivity/mass_storage_devices.html

apply to Serviceguard for Linux as well.

Monitoring Multipath Devices (detailed information for note 15 above)

The command

cmresserviced

cannot be used directly for multipath names that will not change with changes in the storage configuration. To

overcome this limitation create a conversion script in the Serviceguard bin directory called

cmresserviced_custom

. An example is provided below.

The

service_cmd

line for the disk monitor would then be of the form:

SERVICE_CMD[0]="/usr/local/cmcluster/bin/cmresserviced_custom mpathX mpath..."

Where

mpathX

is the default DeviceMapper multipath name for the first monitored LUN. Additional LUNs are represented by

mpath…

#!/bin/sh

. /etc/cmcluster.conf

typeset -a realdm dm

typeset -i i

(( i = 0 ))

for arg in "$@"

dm[$i]=${arg##/dev/mapper/}

realdm[$i]=/dev/$(multipath -ll ${dm[$i]}| grep mpath | awk '{print $3}' )

(( i = i + 1 ))

done

$SGLBIN/cmresserviced "${realdm[*]}"