For DM-Multipath to function properly, you must edit the /etc/multipath.conf configuration file.
You should exclude all of the devices that do not correspond to LUNs configured on the storage system that are mapped to your Linux host. That is, you should exclude the devices that are not displayed by the sanlun lun show command.
To obtain the WWID on systems running other Linux operating systems, enter scsi_id -gus /block/sda.
In both cases, the output looks similar to the following:
SIBM-ESXSMAW3073NC_FDAR9P66067WTo exclude that device, enter SIBM-ESXSMAW3073NC_FDAR9P66067W in the blacklist section of the configuration file:
blacklist { wwid IBM-ESXSMAW3073NC_FDAR9P66067W devnode "^hd[a-z]" devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*" devnode "^cciss.*" }
devnode_blacklist { devnode "^hd[a-z]" devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*" devnode ^cciss.*" wwid SIBM-ESXSMAW3073NC_FDAR9P66067WJ }
If you are running... | Without ALUA, use the value | Without ALUA, use the value |
---|---|---|
SUSE Linux Enterprise Server 10 SP2 and later, SUSE Linux Enterprise Server 11, 12, and later, or Red Hat Enterprise Linux 6.0 and later | Set prio to: “alua” | Set prio to: “ontap” |
Any other Red Hat Enterprise Linux operating system | Set prio_callout to: /sbin/mpath_prio_alua | Set prio_callout to: /sbin/mpath_prio_ontap |
SUSE Linux Enterprise Server 10 SP1 and SP2 | ~ | Set prio_callout to: /sbin/mpath_prio_ontap |
All supported Linux operating systems that support ALUA | Set hardware_handler to: "1 alua" | Set hardware_handler to: "0" |