HP Hitachi Dynamic Link Manager Software - Manual (Page 309)

4. HDLM Operation
287
dlmfdrv.conf
).
3. Execute the
dlmsetconf
utility for creating the HDLM driver configuration
definition file.
Edit the HDLM driver unconfiguration definition file (
/opt/
DynamicLinkManager/config/dlmfdrv.unconf
) as required, and then
execute the
dlmsetconf
utility.
For details on how to edit the HDLM driver unconfiguration definition file (
/
opt/DynamicLinkManager/config/dlmfdrv.unconf
), see 3.5.5 Using
the HDLM Device Unconfiguration Function When Performing a New
Installation of HDLM.
4. Depending on the changes you have made to the HDLM system configuration,
restart the host with the reconfiguration option specified, or execute the
dlmcfgmgr
utility for managing the HDLM configuration.
(2) When the Path Configuration Is Changed
When the path configuration of an LU is changed and any of the following operations
occur, logical device files of HDLM devices might be re-created with a different name:
„ The
-r
parameter was specified when executing the
dlmsetconf
utility for
creating the HDLM driver configuration definition file.
„ One of the following changes was made to the construction of the path used by
HDLM to determine the logical device file name of the HDLM device:
• A path was deleted.
• The target ID was changed. Alternatively, when Sun HBA had been used
with fabric connection (using Sun StorageTek (TM) SAN Foundation
Software), the connection destination was changed to a different storage
port.
• A LUN was changed.
• The HBA model was changed.
• The HBA mounting slot was changed.
• The contents of the
/etc/path_to_inst
file were altered to change the
instance number of the HBA driver.
• The FCode was installed on an HBA where the FCode had not been
previously installed. Alternatively, the FCode was uninstalled from an HBA.
If the HDLM logical device file has been re-created by specifying the different file
name, perform the following procedures:
„ Change the disk settings being used by the application programs.