HP 3PAR RedHat and Oracle Linux Implementation Guide

2. Verify that the multipathd daemon is enabled by the rc script to run on every host boot
up. The following output shows that it is enabled for run-level 3, 4 and 5. Enable it appropriately
for your configuration:
# chkconfig --list multipathd
multipathd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
3. Check that the appropriate rc scripts have been created for each run level. The start number(s)
may not match those shown here.
# ls /etc/rc3.d/*multi*
/etc/rc3.d/S13multipathd
# ls /etc/rc5.d/*multi*
/etc/rc5.d/S13multipathd
You can also use the chkconfig command to enable multipathing:
# chkconfig multipathd on
Setting Up Veritas DMP Multipathing
For Active/Active multipath load balancing and failover, install Veritas Storage Foundation and
High Availability Software, following the instructions provided in the Veritas Storage Foundation
installation and administrator guides, available on the following website:
Symantec
NOTE: Veritas Cluster V6.0.1 is supported on RHEL 6.x with HP 3PAR OS 3.1.1 or later.
If you are using QLogic HBAs, the QLogic non-failover driver should be installed for Veritas DMP
support.
Device-mapper (DM) or multipath modules should not be configured when Veritas DMP is used for
multipathing.
Check the configuration of the Device-mapper module with chkconfig --list multipathd
and turn it off with chkconfig multipathd off.
It is required to have the Veritas Array Support Library (ASL) for the HP 3PAR StoreServ Storage
installed on the RHEL host if you are using a Veritas Storage Foundation version prior to 5.0mp3.
As of HP 3PAR OS 3.1.2, the virtual volume (VV) WWN increased from 8 bytes to 16 bytes. The
increase in WWN length may cause the Symantec ASL to incorrectly identify the array volume
identification (AVID) number, subsequently resulting in use of a different naming convention for
DMP disk devices.
NOTE: This issue does not occur with Storage Foundation 6.1, which is compatible with both
8-byte and 16-byte WWNs.
The standard naming convention is as follows:
<enclosure_name><enclosure_number>_<AVID>
For example:
3pardata4_5876
3pardata4_5877
3pardata4_5878
54 Configuring a Host with Fibre Channel