Device Mapper Multipath Enablement Kit for HP StorageWorks Disk Arrays v4.3.
Legal and notice information © Copyright 2009 Hewlett-Packard Development Company, L.P.
Overview This release notes discusses the recent product information about HP Device Mapper Multipath (HPDM Multipath) Enablement Kit for HP StorageWorks Disk Arrays v4.3.1. This incremental release is to provide support for RedHat Enterprise Linux 5 Update 4 and SuSE Linux Enterprise Server 10 SP3 operating systems.
NOTE: The following features are available only on SLES 11 operating system: • Least pending I/O path • DM service time For details on multipathing support for SAN Boot environment, see the Booting Linux x86 and x86_64 systems from a Storage Area Network with Device Mapper Multipath document available at: http://h18006.www1.hp.com/storage/networking/bootsan.html What's new HPDM Multipath 4.3.
System feature Supported hardware and software Servers HP BladeSystem c-Class Server Blades, ProLiant x86, ProLiant AMD64, ProLiant EM64T Servers, Integrity Servers EVA4000 (HSV200) XCS 5.110/6.200 or later EVA6000 (HSV200) XCS 5.110/6.200 or later EVA8000 (HSV210) XCS 5.110/6.200 or later EVA4100 (HSV200) XCS 6.200 or later EVA6100 (HSV200) XCS 6.200 or later EVA8100 (HSV210) XCS 6.
NOTE: • For more information on configuring iSCSI parameters, see Configuring iSCSI parameters. • Device Mapper Multipath does not support coexistence with other multipath products. • Device Mapper Multipath does not support Active-Passive Storage Arrays. • HPDM Multipath Enablement Kit for HP StorageWorks Disk Arrays v4.3.1 does not support SAS and CCISS devices on RHEL 5.4 and SLES 10 SP3. • On SLES 11, Device Mapper Multipath for iSCSI devices is supported with kernel version 2.6.27.370.1.
Installing HPDM Multipath Enablement kit 4.3.1 To install HPDM Multipath 4.3.1, complete the following steps: 1. 2. Download the HPDM Multipath Enablement Kit for HP StorageWorks Disk Arrays v4.3.1 available at http://www.hp.com/go/devicemapper. Log in as root to the host system. 3. Copy the installation tar package to a temporary directory (for example, /tmp/HPDMmultipath). 4. Unbundle the package by executing the following commands: #cd /tmp/HPDMmultipath #tar -xvzf HPDMmultipath-4.3.1.tar.
vendor product getuid_callout hardware_handler path_selector path_grouping_policy failback rr_weight no_path_retry rr_min_io path_checker "HP" "MSA2[02]12fc|MSA2012i" "/sbin/scsi_id -g -u -s /block/%n" "0" "round-robin 0" multibus immediate uniform 18 100 tur } EVA4x00/EVA6x00/EVA8x00 device { vendor product getuid_callout prio_callout hardware_handler path_selector path_grouping_policy failback rr_weight no_path_retry rr_min_io path_checker "HP” "HSV2[01]0|HSV300|HSV4[05]0" "/sbin/scsi_id -g -u -s /blo
device { vendor product getuid_callout hardware_handler path_selector path_grouping_policy failback rr_weight no_path_retry rr_min_io path_checker "HP" "OPEN-.
NOTE: • For SLES 11, in the device section, replace getuid_callout “/sbin/scsi_id -g -u -s /block/%n” with getuid_callout “/lib/udev/scsi_id -g -u /dev/%n” • For SLES 10 SP2/SLES 10 SP3/RHEL 5 U4, in the device section for MSA2012sa, MSA2312sa, and MSA2324sa, replace getuid_callout “/sbin/hp_scsi_id -g -u -n -s /block/%n” with getuid_callout “/sbin/scsi_id -g -u -n -s /block/%n” • For SLES 10 SP2/SLES 10 SP3/SLES 11, in the device section, replace prio_callout “/sbin/mpath_prio_alua %n” with prio
Configuring QLogic HBA parameters To configure the QLogic HBA parameters for QLogic 2xxx family of HBAs, complete the following steps: 1. Edit the /etc/modprobe.conf file in RHEL hosts and /etc/modprobe.conf.
#mv /boot/initrd-.img /boot/initrd-.img.old b. Make a new initrd image by executing the following command: • For SLES 10/SLES 11 operating systems: #mkinitrd -k -i • For other operating systems: #mkinitrd /boot/initrd-.img `uname -r` c. Edit the value for default parameter in /boot/grub/menu.lst file to boot with the new initrd image.
c. Edit the value for default parameter in /boot/grub/menu.lst file to boot with the new initrd image. SAN configuration supported by DM Multipath Table 2 lists the maximum SAN configuration supported by DM Multipath.
/etc/sysconfig/iscsi file depending on the number of LUNs, or run the multipath -v0 command after the reboot. • On SLES 11 operating systems: • Multipath may not always activate all partitions on reboot. • The multipathd daemon may fail to stop immediately after it is started in large SAN configurations. • The multipathd daemon may consume more memory in large SAN configurations.