vendor
"IBM"
product "3S42"
#DS4200 Product 10
}
device {
vendor
"HP"
product "*"
}
}
2.4. Blacklist Exceptions
You can use the
blacklist_exceptions
section of the configuration file to enable multipathing
on devices that have been blacklisted by default. For example, by default, devices with vendor =
"IBM" and product = "S/390.*" are blacklisted since usually DASD devices are used for local
storage. If you do need to enable multipathing on these devices, uncomment the following lines
in the configuration file:
blacklist_exceptions {
device {
vendor
"IBM"
product "S/390.*"
}
}
When specifying devices in the
blacklist_exceptions
section of the configuration file, you
must specify the exceptions in the same way they were specified in the blacklist. For example, a
WWID exception will not apply to devices specified by a
devnode
blacklist entry, even if the
blacklisted device is associated with that WWID. Similarly,
devnode
exceptions apply only to
devnode
entries, and
device
exceptions apply only to device entries.
3. Configuration File Defaults
The
/etc/multipath.conf
configuration file includes a
defaults
section that sets the
user_friendly_names
parameter to
yes
, as follows.
defaults {
user_friendly_names yes
}
This overwrites the default value of the
user_friendly_names
parameter.
The configuration file includes a template of configuration defaults. This section is commented
out, as follows.
#defaults {
Chapter 4. The DM-Multipath Configuration File
20
Summary of Contents for DEVICE-MAPPER MULTIPATH 5.2
Page 4: ...Using Device Mapper Multipath ...
Page 6: ...vi ...
Page 10: ...x ...
Page 16: ...6 ...
Page 19: ...Multipath Devices in Logical Volumes 9 ...
Page 20: ...10 ...
Page 26: ...16 ...
Page 38: ...28 ...