HP Hitachi Dynamic Link Manager Software Licenses - Manual (Page 378)

Table 4-5 Example: Allocation of New HDLM Devices
Allocation before
restarting the host
Allocation after restarting the host
none /dev/sddlmaa #
/dev/sddlmaa /dev/sddlmaa
/dev/sddlmab
#
/dev/sddlmaa
/dev/sddlmab /dev/sddlmaa
/dev/sddlmab
/dev/sddlmac
#
/dev/sddlmaa
/dev/sddlmac /dev/sddlmaa
/dev/sddlmab
#
/dev/sddlmac
/dev/sddlmab
/dev/sddlmac /dev/sddlmaa #
/dev/sddlmab
/dev/sddlmac
/dev/sddlmaa
:
/dev/sddlmpp /dev/sddlmaa
:
/dev/sddlmpp
/dev/sddlmaaa
#
/dev/sddlmaa
:
/dev/sddlmaap /dev/sddlmaa
:
/dev/sddlmaap
/dev/sddlmbaa
#
#
The newly allocated logical device file name of the HDLM device
If the error message KAPL10357-E is displayed, HDLM does not add an HDLM
device even though a new LU was recognized. In this case, you must execute
the HDLM-configuration definition utility (dlmcfgmgr -u) to delete the HDLM
device(s) not in use (or, represented with a hyphen (-)) to release the
available name(s) to create an HDLM device file for the new LU.
Even if you add a path to an HDLM device that is not managed by HDLM and
restart the host, the HDLM device will not be managed by HDLM.
An AutoPATH_ID is allocated sequentially as the HDLM recognizes a SCSI
device during start up of the host. Therefore, an AutoPATH_ID for the same
path may change whenever the host starts.
If a different LU is allocated to the same path name, a new HDLM device will
be allocated to the newly allocated LU after restarting the host restarts. In
such case, the previous HDLM device is unregistered automatically.
4-74
HDLM Operation
Hitachi Dynamic Link Manager (for Linux®) User Guide