Notes on installing HDLM

A license key is required to perform a new installation of HDLM.

To update the HDLM license, execute the dlnkmgr command's set -lic operation. The expiration time of the license key is determined by the type of license key specified in the license key file or entered by the user. For information on license key types and the set operation, see COM_MNL_SET_(SETS_UP_THE_OPERATING_ENVIRONMENT)=GUID-D5D49D56-5FD4-47C9-B3EF-F783D00A63D0=3=EN=.html.

For Red Hat Enterprise Linux 9 and Oracle Linux 9, the following RPM package is required for installing HDLM.

• initscripts-RPM package version.rpm

If the RPM package does not exist, the KAPL09320-E message is output and the installation is terminated. Follow the instructions in the message, and then perform the installation again.

For Red Hat Enterprise Linux 8 and 9, Oracle Linux 8 and 9, and Oracle Unbreakable Enterprise Kernel 8, the following RPM package is required for installing HDLM.

• tar-RPM package version.rpm

If the RPM package does not exist, the KAPL09320-E message is output and the installation is terminated. Make sure that the OS you are using meets the prerequisite conditions, and install all required packages. Then, re-install HDLM.

During the installation of HDLM, a check is performed of whether the use of LVM cache files is enabled.

If the use of LVM cache files is enabled, the KAPL12451-E message is output and the installation is terminated. Disable the use of LVM cache files by performing the action corresponding to the message, and then perform installation again.

When performing a backup or restoration by using various features of the OS, storage system, or applications in an environment where HDLM is installed, HDLM might not function correctly in the environment after the backup or restoration. Similarly, if you create a duplicate of an environment where HDLM is installed, HDLM might not function correctly. To avoid these problems, uninstall HDLM before performing a backup or creating a duplicate. After the restoration or environment duplication, reinstall HDLM and then configure the environment.

When the dlmcfgmgr utility is executed to change the HDLM device configuration, memory might become insufficient due to the HAL daemon^#. In this case, the host will not respond.

To avoid this, stop the HAL daemon when executing the dlmcfgmgr utility. The following procedure shows how to stop the HAL daemon.

This does not apply to Red Hat Enterprise Linux 7, 8, or 9, Oracle Unbreakable Enterprise Kernel 7, SUSE LINUX Enterprise Server 12 or 15.

#

The HAL daemon detects hardware configurations changes, for example, when a USB device or CD-ROM is inserted.

To stop the HAL daemon:

1. Check the status of the HAL daemon.

   Execute the /sbin/service command to check the HAL daemon status. If the daemon is running, running will appear.

   # /sbin/service haldaemon status

   If the daemon is not running, stopped will appear.

2. Check the result of step a. If the HAL daemon is running, stop the daemon.

   Execute the /sbin/service command to stop the HAL daemon. Note that it might take a while to stop the daemon completely.

   # /sbin/service haldaemon stop

3. Make sure that the HAL daemon is stopped.

   Execute the /sbin/service command to make sure that the HAL daemon is not running.

   # /sbin/service haldaemon status

4. Execute the dlmcfgmgr utility (dlmcfgmgr -r or dlmcfgmgr -i) to configure the HDLM device.

   # /sbin/dlmcfgmgr -r

   or

   # /sbin/dlmcfgmgr -i

5. Start the HAL daemon.

   Execute the /sbin/service command to start the HAL daemon.

   # /sbin/service haldaemon start

6. Make sure that the HAL daemon is running.

   Execute the /sbin/service command to make sure that the HAL daemon is running.

   # /sbin/service haldaemon status