Hitachi Dynamic Link Manager Software Users Guide for Linux

¢
If you have an HDLM device name as the output, change the UUID to
the HDLM device name in the /etc/crypttab file's second field.
¢
If you have got a SCSI device name as the output, check the output
of step 1 to confirm the HDLM device name corresponding to the SCSI
device name, and change the UUID to the HDLM device name in
the /etc/crypttab file's second field.
The following shows an example of changing the setting in the /etc/
crypttab file's second field.
Before:
luks-volume1 UUID="050f9901-3ab8-4556-a091-9c6e4a404f09" /etc/
cryptpassword1
After:
luks-volume1 /dev/sddlmaa /etc/cryptpassword1
4. Unmap the SCSI device from the device used by the device mapper.
The following shows an example of unmapping the SCSI device from
the /dev/mapper/luks-volume1 device.
# cryptsetup luksClose luks-volume1
#
5. Map the device used by device mapper to the HDLM device.
The following shows an example of mapping /dev/mapper/luks-volume1
(that was unmapped at step 4) to the HDLM device when using a key file
(/etc/cryptpassword1).
# cryptsetup -d /etc/cryptpassword1 luksOpen /dev/sddlmaa luks-
volume1
key slot 0 unlocked.
Command successful.
#
6. Change the single-path configuration to a multi-path configuration.
Settings for md Devices
This section explains the procedures that the user must perform when using
md devices.
Notes on Setting Up md Devices
The following are notes on using md devices:
• Because HDLM is multi-path software, it cannot be used with the
MULTIPATH function for md devices.
• If you are using the MULTIPATH function for md devices before you install
HDLM, change it to the LINEAR function after installing HDLM.
Creating an HDLM Environment
3-159
Hitachi Dynamic Link Manager (for Linux®) User Guide