Linux Config.fm
Draft Document for Review March 28, 2011 12:24 pm
638
IBM System Storage DS3500: Introduction and Implementation Guide
Multipaths: Specifies configuration settings for tuning
Create the /etc/multipath.conf file as shown in Example 20-12.
Example 20-12 Multipath.conf file sample
multipaths {
multipath {
wwid 360080e50001b0c90000007504c6e060a
alias mpath0
path_grouping_policy multibus
path_checker readsector0
path_selector "round-robin 0"
failback "5"
rr_weight priorities
no_path_retry "5"
}
}
devices {
device {
vendor "IBM"
product "1746"
hardware_handler "1 rdac"
path_checker rdac
failback 0
path_grouping_policy multibus
prio_callout "/sbin/mpath_prio_tpc /dev/%n"
}
}
The vendor field must be the same as in the /sys/block/sdb/device/vendor file and the product
field must be the same as in the /sys/block/sdb/device/model file
It is highly recommended to use alias for naming the devices instead of using the uid of the
device. In this case we choose to use the name mpath. To choose the name, consider that the
devices will be created as /dev/mapper/mpath[n]. This name will be created under the
/dev/mapper directory.
Configure Services
Configure the multipathd service to start on boot with the following command:
chkconfig multipathd on
The hal daemon can sometimes cause problems by automatically mounting the underlying
/dev/sd* paths after a failback. To work around this, the hal daemon needs to be disabled in
SLES11 base. This issue is fixed in service pack 1.
If running SLES11 base, disable the haldaemon from starting on boot with the following
commands:
chkconfig network-remotefs off
chkconfig haldaemon off
Note: In this case /dev/sdb is one of the paths to the logical drive
Summary of Contents for DS3500
Page 2: ......
Page 5: ...iii Draft Document for Review March 28 2011 12 24 pm 7914edno fm ...
Page 789: ......
