Multipath Setup
535-0045-00 Rev 02 Violin 6000 Series Memory Array Installation Guide 59
In the above example, support for Violin SAN Array devices was added. When configuring this
file, pay particular attention to the following for a non-ALUA LUN:
• path_grouping_policy should be set to group_by_serial
• getuid_callout should be set
• path_checker should be tur(TEST_UNIT_READY)
• failback should be immediate
• rr_weight should be uniform since weights are not assigned to the individual paths
• no_path_retry should be set faitl to immediately bring path back online
• rr_min_io should be set to 4, but can be subject to change depending on the
environment and workload.
For ALUA LUNs, pay particular attention to the following:
• path_grouping_policy should be set to group_by_prio
• prio should be set to alua
• hardware_handler should be set to 1 alua
2. Save the multipath.conf file and proceed with Configuring the Multipath Daemon on page
59.
Configuring the Multipath Daemon
This section demonstrates how to configure the multipath daemon (multipathd) so that it starts
when the system boots up.
1. Use the chkconfig command to add (-a) to the multipath daemon (multipathd) as a
service.
2. Restart the multipath service, using the service restart command.
3. Verify that the multipath service is running, using the multipath -ll command.
The following example demonstrates these steps for a single ALUA LUN that is accessible
through two Fibre Channel (FC) ports that are multipathed into a single multipath device (/dev/
mapper/mpath1).
# chkconfig -a multipathd
# service multipathd restart
# multipath -ll
mpathav (SVIOLIN_SAN_ARRAY_ALUA_5EA81A7F53121185) dm-11 VIOLIN,SAN
ARRAY ALUA
size=1000G features='0' hwhandler='1 alua' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| `- 5:0:0:9 sds 65:32 active ready running
`-+- policy='round-robin 0' prio=10 status=enabled
`- 7:0:0:9 sdt 65:48 active ready running