Performing a new installation of HDLM

Dynamic Link Manager (for Linux®) User Guide

Version
9.0.x
Audience
anonymous
Part Number
MK-92DLM113-64
ft:lastEdition
2025-11-06

To perform a new installation of HDLM:

This subsection describes how to perform a new installation of HDLM. The preparations before newly installing HDLM are required. For details about the preparations before installing HDLM, see Preparations for a new installation of HDLM.

  1. Log on to Linux as the root user.

  2. Prepare the license key.

    Use either of the following methods to store the license key file in the specified directories:

    • Store the license key file (*.plk) in the /var/tmp directory, under the name hdlm_license.

      /var/tmp/hdlm_license
    • Execute the following commands to create the license key file (dlm.lic_key) in the /etc/opt/DynamicLinkManager directory.

      # mkdir /etc/opt/DynamicLinkManager
      # echo "license-key" >
      /etc/opt/DynamicLinkManager/dlm.lic_key
  3. Insert the DVD-ROM and mount it.

    If the DVD-ROM was not automatically mounted, execute the mount command to mount the DVD-ROM to the fixed mount point.

    The following shows an example of command execution when the mount point is /media/cdrom:

    # mount /dev/cdrom /media/cdrom

    The following table lists the fixed mount points for each distribution.

    Table. Mount point for each distribution

    Distribution

    Mount point

    Red Hat Enterprise Linux 7, 8, 9

    /media/cdrom

    SUSE LINUX Enterprise Server

    /media/cdrom

    If the DVD-ROM is automatically mounted:

    /media/ media-volume-id #

    Note 1

    HDLM cannot be installed if the DVD-ROM is mounted to a mount point other than the above.

    Note 2

    To copy the DVD-ROM to a directory, and then install HDLM from that directory, copy the DVD-ROM to a directory with the same name as the mount point noted above. If the file permissions or the directory structure differs, HDLM cannot be installed.

    #

    This refers to the volume name for the CD-ROM or other media, formatted for ISO-9660 file systems. Use the volname command to check media-volume-id.

    The following shows an execution example for when media-volume-id is VOL01234.

    # volname /dev/cdrom
    VOL01234
    #
  4. Check the version of HDLM.

    Execute installux.sh or the HDLM installation utility (installhdlm) stored on the HDLM DVD-ROM to check the version of HDLM that will be installed.

    The following example shows how to execute the command when the mount point for the DVD-ROM is /media/cdrom:

    • When executing installux.sh

      # /media/cdrom/installux.sh -v
    • When executing the installhdlm utility

      # /media/cdrom/HDLM_Linux/installhdlm -v

    A command execution example is described below. x.x.x-xx is the version of HDLM.

    KAPL09177-I HDLM version: x.x.x-xx
  5. Perform the installation.

    Execute installux.sh or the installhdlm utility stored on the HDLM DVD-ROM to start installation.

    The following shows an installation execution example for when the DVD-ROM mount point is /media/cdrom.

    • When executing installux.sh

      # /media/cdrom/installux.sh
    • When executing the installhdlm utility

      # /media/cdrom/HDLM_Linux/installhdlm
  6. The KAPL09093-I message is displayed to confirm that you want to perform a new installation. Check the HDLM version, and if it is correct, enter y.

    The license key file will be deleted when installation finishes.

  7. Make sure that HDLM is installed.

    Execute the following command to display detailed information about the installed package.

    # rpm -qi HDLM
    Name        : HDLM
    Version     : x.x.x.x.xxx
    Release     : xx  
         :

    If HDLM Version is x.x.x.x.xxx, the installed version of HDLM is correct. x.x.x.x.xxx indicates the HDLM version that was installed.

  8. If IP-SAN is used for the connection between the host and the storage system, change iscsi_boot=n, written in the /etc/opt/DynamicLinkManager/hdlm.conf file, to iscsi_boot=y.

    In addition, if the QLogic 8400 Series (FCoE) is used to connect the host and the storage system, in the /etc/opt/DynamicLinkManager/hdlm.conf file, change fcoe_boot=n to fcoe_boot=y.

  9. If you want to set the HDLM driver options, run the dlmsetopt utility.

    For details on this utility, see dlmsetopt utility for setting HDLM driver options.

    If you performed this step, go to step 12.

  10. When you want to install HDLM without restarting the host, go to step 11. When you want to install HDLM with restarting the host, then go to step 12.

  11. Execute the dlmstart utility for starting HDLM.

    For details, see dlmstart utility for starting HDLM.

  12. Add /opt/DynamicLinkManager/bin in the environment variable PATH in the environment setup file for the shell used by the root user.

    Add the following code to the PATH environment variable in the environment settings file for the root user. This makes executing the HDLM commands and HDLM utilities easier.

    When the BourneAgain shell or Korn shell is used:
    PATH=$PATH:/opt/DynamicLinkManager/bin ; export PATH
    When the C shell is used:
    set path= ( $path /opt/DynamicLinkManager/bin )

    If the PATH environment variable is not set, specify an absolute path to execute commands and utilities.

    If you have performed steps 11, go to step 14.

  13. Restart the host.

    Execute the following command to restart the host:

    # shutdown -r now

    A path will be established in the HDLM device and the HDLM manager will start.

  14. If you have edited the /etc/fstab file as described in Operations required for devices to be managed by HDLM, add the line show below to change the setting from a SCSI device specification to an HDLM device specification.

    The Linux functionality that adds LABEL= or UUID= to a SCSI device is not supported in HDLM. Do not use this functionality.

    An example of how to edit the /etc/fstab file is shown in the following figure:

    Add the shaded line shown in the above figure.

  15. Specify the settings required for using the volume management software.

    If the logical volume created with the volume management software is already being used, replace it with a logical volume whose physical volume is an HDLM device.

    For details on setting the volume management software, see Settings for LVM2.

  16. Specify the settings required for using virtual environments.

    When using Xen, set it up to use HDLM devices in domainU. When using KVM, register HDLM devices into the hardware configuration file.

    For details on operating environments for the virtual environments supported by HDLM, see Virtual environments supported by HDLM. For details on how to set up a virtual environment, see Settings for Xen or Settings for KVM.

  17. Specify the settings required for operations in a cluster configuration.

    For a cluster configuration, change the logical device file names of SCSI devices specified in the cluster to logical device file names of HDLM devices.

    For details on setting the cluster software, see Settings for Oracle.

  18. Execute the dlnkmgr command's view operation to check the HDLM settings and status of each program.

    The following is an example of executing the command:

    # /opt/DynamicLinkManager/bin/dlnkmgr view -sys
    HDLM Version                 : x.x.x-xx
    Service Pack Version         :
    Load Balance                 : on(extended lio)
    Support Cluster              :
    Elog Level                   : 3
    Elog File Size (KB)          : 9900
    Number Of Elog Files         : 2
    Trace Level                  : 0
    Trace File Size(KB)          : 1000
    Number Of Trace Files        : 4
    Path Health Checking         : on(30)
    Auto Failback                : on(1)
    Reservation Status           : 
    Intermittent Error Monitor   : off
    HDLM Manager  Ver         WakeupTime
    Alive          x.x.x-xx       yyyy/mm/dd hh:mm:ss
    HDLM Alert Driver  Ver          WakeupTime          ElogMem Size
    Alive                x.x.x-xx        yyyy/mm/dd hh:mm:ss   1000
    HDLM Driver  Ver          WakeupTime
    Alive         x.x.x-xx        yyyy/mm/dd hh:mm:ss
    License Type     Expiration
    Permanent        -
    KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss
    #

    Even when cluster software is being used, Support Cluster is blank. However, the cluster function is operating normally.

  19. Check that the correct version of HDLM is installed.

    If HDLM version x.x.x-xx is displayed, the installed HDLM version is correct. x.x.x-xx is the version of the installed HDLM.

  20. Check that the programs are running properly.

    If HDLM Manager, HDLM Alert Driver, and HDLM Driver are all Alive, all programs are running correctly.

    If the programs are not running properly, see What to do for a program error, and then take actions.

After the installation, check the path configuration according to the procedure indicated in Checking the path configuration.