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

dlmfdrv.unconf file exists either in the /opt/DynamicLinkManager/
config directory or in a user-defined directory, the file is renamed
dlmfdrv.unconf.bak and saved as the previous generation of the
definition file.
• Even when the -d parameter is specified, existing definition information
is read from the /kernel/drv/dlmfdrv.conf and /kernel/drv/
dlmndrv.conf files, rather than from the dlmfdrv.conf and
dlmndrv.conf files in the specified directory.
• If the dlmsetconf utility finds an added path, in the HDLM driver
configuration definition file (/kernel/drv/dlmfdrv.conf) the utility adds
an entry (that is, a definition) to the definition of the LU for which the
path has been added. If any path has been deleted, the entry (definition)
is deleted from the definition of the affected LU. Whether a path is added
or deleted, existing instance numbers are inherited unless a new HDLM
driver configuration definition file (/kernel/drv/dlmfdrv.conf) file is
created.
• If the dlmsetconf utility finds any storage systems connected to a newly
added HBA, in the HDLM nexus driver configuration definition file (/
kernel/drv/dlmndrv.conf) the utility adds the entry (definition) for the
new HBA. Even when an HBA, to which one of the Hitachi storage
systems is connected, is deleted, the entry (definition) remains. Unless a
new HDLM nexus driver configuration definition file (/kernel/drv/
dlmndrv.conf) is created, the existing instance numbers are inherited,
and the entry is not deleted.
• If no configuration definition files (/kernel/drv/dlmfdrv.conf and /
kernel/drv/dlmndrv.conf) are found, the configuration definition files (/
kernel/drv/dlmfdrv.conf and /kernel/drv/dlmndrv.conf) are created
regardless of whether or not the -r parameter is specified.
• If an LU is deleted, you must delete the logical device files of the HDLM
devices corresponding to the deleted LU, which are stored in
the /dev/dsk or /dev/rdsk directory, before executing the dlmsetconf
utility. If the dlmsetconf utility is executed before the logical device files
of the HDLM devices corresponding to the deleted LU are deleted, then
the format command might incorrectly display the logical device file
name of an HDLM device corresponding to the deleted LU, for the newly
recognized LU.
• When using SDS or SVM and executing the dlmsetconf utility after
making changes in the path configuration, you must not specify the -r
parameter. If you do so, the metadevices and volumes might be
unavailable.
• Executing the dlmsetconf utility with the -u parameter specified does not
update the unconf property in the HDLM driver configuration definition
file (/kernel/drv/dlmfdrv.conf) if no change is made to the HDLM-
managed devices. After the reconfiguration option is specified to restart
the host, the HDLM driver configuration definition file (/kernel/drv/
dlmfdrv.conf) that was updated takes effect in the system.
7-28
Utility Reference
Hitachi Dynamic Link Manager (for Solaris) User Guide