HP 3PAR SUSE Linux Enterprise Implementation Guide

2. Edit the device structure to add entries for HP 3PAR array and remove other product entries
that are not needed.
After all of the edits are made, the relevant sections of /etc/multipath.conf should
appear as follows, if the HP 3PAR array that the SLES host is connecting to is running HP 3PAR
OS 3.1.1 or 3.1.2.
NOTE: If the HP 3PAR array is running an HP 3PAR OS version earlier than 3.1.1, then the
polling_interval setting should be set to 5 rather than 10, and the no_path_retry
setting should be set to 12 rather than 18.
defaults {
polling_interval 10
}
devices {
device {
vendor "3PARdata"
product "VV"
no_path_retry 18
features "0"
hardware_handler "0"
path_grouping_policy multibus
path_selector "round-robin 0"
rr_weight uniform
rr_min_io 100
path_checker tur
failback immediate
}
}
NOTE: The example shown above is for host persona 1(Generic).
NOTE: If the HP 3PAR StoreServ Storage array that the SLES server is connecting to is running
an HP 3PAR OS version 3.1.3 or later, you must change the host persona to 2 (generic-ALUA)
and modify the /etc/multipath.conf file.
When changing from HP 3PAR host persona 1 to host persona 2 or vice versa:
• A change from persona 1 to persona 2, or from persona 2 to persona 1, requires that
the array ports affected be taken offline, or that the host for which the persona is being
changed be not connected (not logged in). This is an HP 3PAR OS requirement.
• For existing devices targeted in a persona to be claimed, the host must be rebooted.
Use the following procedure:
1. Stop all host I/O and modify the /etc/multipath.conf file on the SLES host.
2. Shut down the host.
3. Change the host persona on the array.
4. Boot the host.
5. Verify that the target devices have been claimed properly and that the persona setting is
correct.
In addition, a SAN boot configuration requires rebuilding of the ramdisk in order to take
effect.
32 Configuring a Host with Fibre Channel