HiCommand Dynamic Link Manager User's Guide (for Windows(R))

[Contents][Glossary][Index][Back][Next]

3.5.3 Performing a new installation of HDLM

Organization of this subsection
(1) In a Non-Cluster Environment
(2) When MSCS is used
(3) When VCS is used
(4) When Oracle RAC is used

(1) In a Non-Cluster Environment

Before installing HDLM, prepare a license key.

If you want to perform an unattended installation, prepare the installation-information settings file in which information required for the installation has already been defined.

To install HDLM on a host that does not currently contain HDLM:

  1. Log on to the Windows system as a member of the Administrators group.

  2. Store the license key file directly under the Windows installation-destination drive. You can also specify a license key directly without using the license key file.

    installation-drive:\hdlm_license

    The license key file will be deleted when the installation finishes.

  3. Perform the installation.
    • If you do not want to perform an unattended installation, insert the CD-ROM into the drive, and then start the installation program setup.exe.
      The program checks whether HDLM has already been installed. If HDLM 5.4 or earlier has been installed, the KAPL09129-E message appears. In this case, carry out the procedure shown in 3.5.5 Migrating from HDLM 5.4 or earlier to HDLM 5.5 or later. If HDLM 5.5 or later has been installed, the KAPL09173-W message appears. In this case, carry out the procedure shown in 3.5.4 Upgrade installation or re-installation of HDLM. If no message appears, go to step 4.
    • If you want to perform an unattended installation, insert the CD-ROM into the drive, and start the installation program installhdlm.exe.
      At the command prompt, execute the following command:
      drive-to-which-the-installation-CD-ROM-is-inserted:\DLMTools\installhdlm.exe -f installation-information-settings-file (installhdlm.ini)
      This command checks whether HDLM has already been installed. If HDLM 5.4 or earlier has been installed, the KAPL09129-E message appears. In this case, carry out the procedure shown in 3.5.5 Migrating from HDLM 5.4 or earlier to HDLM 5.5 or later. If HDLM 5.5 or later has been installed, an upgrade installation is performed, and then the KAPL09183-I message appears.
      If you have specified n (do not restart) for the restart key in the installation-information settings file, go to step 12.
      If you have specified y (restart) for the restart key in the installation-information settings file, go to step 17.

  4. The program checks the version of the MPIO driver, and then installs the MPIO driver. If a message appears, asking you whether you want to install MPIO driver, follow the procedure below:
    • The KAPL09127-W message appears if MPIO driver has already been installed and its version does not match the version of MPIO driver to be installed.
      - Click the Next button to install MPIO driver.
      - Click the Cancel button to cancel the installation.
    • If no message appears, go to the next step.

  5. Follow the instructions shown in the messages that appear on the window.
    If a license key file was stored in step 2, specify that license key file.
    If a license key file is not used, specify the license key directly.

  6. Enter user information in accordance with the instructions shown in the messages that appear on the window.

  7. Specify the installation folder in accordance with the instructions shown in the messages that appear on the window.

  8. The utility for registering HDLM persistent reservation keys (dlmprsvkey) is automatically executed to create a PRSV key. The PRSV key is required for the HDLM functions to operate normally. Also, the value of the PRSV key must be unique among hosts. Creation of the PRSV key may be unsuccessful if, for example, an NIC does not exist. Do one of the following in accordance with the result of the execution of the dlmprsvkey utility:
    • If the key creation is successful, the created PRSV key appears in the dialog box. If you do not need to change the value, click the Next button. If you must change the value because another host already has the same PRSV key, change the value and then click the Next button. If you want to undo the change, click the Back button and then start over from step 7.
    • If the key creation is unsuccessful, a dialog box appears that prompts you for the PRSV key. Enter the PRSV key, and then click the OK button.
    For the values you can specify for the PRSV key, follow the instructions shown in the installation program window.

  9. The program checks the PRSV key. If the KAPL09128-W message appears, follow the procedure below:
    • You are prompted to re-enter the PRSV key. Enter an appropriate PRSV key. The program then checks the PRSV key again.
    • If no message appears, go to the next step.

  10. Select an HDLM management-target device only when the OS is one of the following:
    • Windows Server 2003 (IA32) SP1 or later
    • Windows Server 2003 (IPF) SP1 or later
    The Hitachi USP V, TagmaStore, Lightning, Thunder Series and HP StorageWorks XP Series option is always selected. To select the EMC DMX series and CX series as the HDLM management-target device, select EMC Symmetrix DMX Series, CLARiiON CX Series. To select the HP EVA series as the HDLM management-target device, select HP StorageWorks EVA Series.

  11. Follow the instructions shown in the messages that appear on the window.
    • If a dialog box that begins with the following sentence appears during installation, and the Storport Miniport driver is used as the HBA driver, stop the HDLM installation. Then, install QFE838894 or a later version of the Microsoft Storport driver, or install Windows Server 2003 SP1 or later.
      Notes on using a Storport Miniport driver
      Read these notes before using a Storport Miniport driver as an HBA driver.
      The file version of the Storport.sys of this system (Microsoft(R) Storport driver) is n.n.nnnn.n.
      When using a Storport Miniport driver as an HBA driver:
      Please update the Storport Miniport driver to a Storport.sys with a file version n.n.nnnn.n or later.
    • The PRSV key is registered before the installation finishes. If the KAPL09131-W message appears, follow the procedure described in step 13.

  12. Check the results of the installation.
    If you performed an unattended installation, check the installation results in the command prompt.

  13. When the installation finishes, execute the dlmprsvkey utility with the -v parameter specified.
    Make sure that the PRSV key displayed by the dlmprsvkey utility is unique among those of any other hosts in the SAN. If the PRSV key is not unique or is not registered, or if the KAPL09131-W message appears, execute the dlmprsvkey utility with the -r parameter specified to re-register the PRSV key. If the PRSV key is not registered, the HDLM functions may not operate normally. For details about the dlmprsvkey utility, see 8.4 dlmprsvkey (utility for registering a HDLM persistent reservation key).
    If you used the license key file, it will be deleted when the installation finishes. The KAPL09115-W message appears if deletion of this file fails. In this case, delete the file manually, such as by using Explorer.

  14. Shut down the host.
    Leave the host in a single-path configuration until you check (in step 21) whether HDLM has been successfully installed.

  15. Modify the settings in the storage subsystem.
    Modify the settings in the storage subsystem according to the procedure described in the Hardware Notes provided with HDLM.

  16. Start the host.

  17. Log on to the Windows system again as a member of the Administrators group.

  18. Check the log file and PRSV key.
    If you installed HDLM by using an unattended installation and specified y (restart) for the restart key in the installation-information settings file, make sure that the KAPL09181-I message is output to installhdlm.log. For details about this log file, see (3) Log file in 3.5.2 Preparations for installing HDLM by performing an unattended installation or (4) Notes on installation in 3.5.2 Preparations for installing HDLM by performing an unattended installation.
    Make sure that the PRSV key displayed by the dlmprsvkey utility is unique among the hosts in the SAN. If the PRSV key is not unique or is not registered, or if the KAPL09131-W message appears, execute the dlmprsvkey utility with the -r parameter specified to re-register the PRSV key. If the PRSV key is not registered, HDLM functions might not operate normally. For details about the dlmprsvkey utility, see 8.4 dlmprsvkey (utility for registering a HDLM persistent reservation key). If you used the license key file, it will be deleted when the installation finishes. The KAPL09115-W message appears if deletion of this file fails. In this case, delete the file manually, such as by using Explorer.

  19. Execute the dlnkmgr command's view operation to display the status of each program.
    An example of executing the dlnkmgr command's view operation is as follows:

    >dlnkmgr view -sys
HDLM Version                 : xx-xx
Service Pack Version         : 
Load Balance                 : on(rr)
Support Cluster              : off
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                : off
Remove LU                    : off
Intermittent Error Monitor   : off
HDLM Manager Ver      WakeupTime
Alive        xx-xx    yyyy/mm/dd hh:mm:ss
HDLM Alert Driver Ver      WakeupTime          ElogMem Size
Alive             xx-xx    yyyy/mm/dd hh:mm:ss 128
HDLM Driver Ver      WakeupTime
Alive       xx-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

  20. Use the results of the view operation to check the version of the installed HDLM.
    When 05-91 is displayed in HDLM Version, the correct version of HDLM has been installed.

  21. Use the results of the view operation to check that the programs are running properly.
    If HDLM Manager, HDLM Alert Driver, and HDLM Driver are all Alive, all programs are running correctly.

  22. Check the path information as described in 3.6 Checking the path configuration, and make sure that you have successfully installed HDLM in a single-path configuration.

  23. Connect cables to all HBAs (multi-path configuration).
    Figure 3-3 Single path configuration and multi-path configuration shows a single path configuration and a multi-path configuration.

    Figure 3-3 Single path configuration and multi-path configuration

    [Figure]

  24. Check the path information as described in 3.6 Checking the path configuration to make sure that you have successfully built a multi-path configuration.

(2) When MSCS is used

The following provides separate explanations of the procedures for when installing MSCS after HDLM installation, and for when installing HDLM after MSCS installation.

Installing MSCS after HDLM Installation

  1. Shut down all the hosts.

  2. Make sure that all the hosts comprising the cluster system have been fully shut down.

  3. Start the host individually.
    Start them in the single path configuration.

  4. Log on to Windows as a member of the Administrators group.

  5. Store the license key file directly under the Windows installation-destination drive. You can also specify the license key directly without using the license key file.

    installation-drive:\hdlm_license

    The license key file will be deleted when the installation finishes.

  6. Perform the installation.
    • If you do not want to perform an unattended installation, insert the CD-ROM into the drive, and start the installation program setup.exe.
      The program checks whether HDLM has already been installed. If HDLM 5.4 or earlier has been installed, the KAPL09129-E message appears. In this case, carry out the procedure shown in 3.5.5 Migrating from HDLM 5.4 or earlier to HDLM 5.5 or later. If HDLM 5.5 or later has been installed, the KAPL09173-W message appears. In this case, carry out the procedure shown in 3.5.4 Upgrade installation or re-installation of HDLM. If no message appears, go to step 7.
    • If you want to perform an unattended installation, insert the CD-ROM into the drive, and start the installation program installhdlm.exe.
      At the command prompt, execute the following command:
      drive-to-which-the-installation-CD-ROM-is-inserted:\DLMTools\installhdlm.exe -f installation-information-settings-file (installhdlm.ini)
      Specify n (do not restart) for the restart key in the installation-information settings file.
      This command checks whether HDLM has already been installed. If HDLM 5.4 or earlier has been installed, the KAPL09129-E message appears. In this case, carry out the procedure shown in 3.5.5 Migrating from HDLM 5.4 or earlier to HDLM 5.5 or later. If HDLM 5.5 or later has been installed, an upgrade installation is performed, and then the KAPL09183-I message appears.
      After the installation is complete, go to step 15.

  7. The program checks the version of the MPIO driver, and then installs the MPIO driver. If a message appears asking you whether you want to install MPIO driver, follow the procedure below:
    • The KAPL09127-W message appears if MPIO driver has already been installed and its version does not match the version of MPIO driver to be installed.
      - Click the Next button to install MPIO driver.
      - Click the Cancel button to cancel the installation.
    • If no message appears, go to the next step.

  8. Specify a license key file or enter a license key in accordance with the instructions shown in the messages that appear on the window.
    If a license key file was stored in step 5, specify that license key file.
    If a license key file is not used, specify the license key directly.

  9. Enter user information in accordance with the instructions shown in the messages that appear on the window.

  10. Specify the installation folder in accordance with the instructions shown in the messages that appear on the window.

  11. The utility for registering HDLM persistent reservation keys (dlmprsvkey) is automatically executed to create a PRSV key. The PRSV key is required for the HDLM functions to operate normally. Also, the value of the PRSV key must be unique among hosts. Creation of the PRSV key may be unsuccessful if, for example, an NIC does not exist. Do one of the following in accordance with the result of the execution of the dlmprsvkey utility:
    • If the key creation is successful, the created PRSV key appears in the dialog box. If you do not need to change the value, click the Next button. If you must change the value because another host already has the same PRSV key, change the value, and then click the Next button. If you want to undo the change, click the Back button and then start over from step 10.
    • If the creation is unsuccessful, a dialog box appears that prompts you for the PRSV key. Enter the PRSV key, and then click the OK button.
    For the values you can specify for the PRSV key, follow the instructions shown in the installation program window.

  12. The program checks the PRSV key. If the KAPL09128-W message appears, follow the procedure below:
    • You are prompted to re-enter the PRSV key. Enter an appropriate PRSV key. The program then checks the PRSV key again.
    • If no message appears, go to the next step.

  13. Select an HDLM management-target device only when the OS is one of the following:
    • Windows Server 2003 (IA32) SP1 or later
    • Windows Server 2003 (IPF) SP1 or later
    The Hitachi USP V, TagmaStore, Lightning, Thunder Series and HP StorageWorks XP Series option is always selected. To select the EMC DMX series and CX series as the HDLM management-target device, select EMC Symmetrix DMX Series, CLARiiON CX Series. To select the HP EVA series as the HDLM management-target device, select HP StorageWorks EVA Series.

  14. Follow the instructions shown in the messages that appear on the window.
    • If a dialog box that begins with the following sentence appears during installation, and the Storport Miniport driver is used as the HBA driver, stop the HDLM installation. Then, install QFE838894 or a later version of the Microsoft Storport driver, or install Windows Server 2003 SP1 or later.
      Notes on using a Storport Miniport driver
      Read these notes before using a Storport Miniport driver as an HBA driver.
      The file version of the Storport.sys of this system (Microsoft(R) Storport driver) is n.n.nnnn.n.
      When using a Storport Miniport driver as an HBA driver:
      Please update the Storport Miniport driver to a Storport.sys with a file version n.n.nnnn.n or later.
    • The PRSV key is registered before the installation finishes. If the KAPL09131-W message appears, follow the procedure described in step 16.

  15. Check the results of the installation.
    If you performed an unattended installation, check the installation results in the command prompt.

  16. When the installation finishes, execute the dlmprsvkey utility with the -v parameter specified.
    Make sure that the PRSV key displayed by the dlmprsvkey utility is unique among those of any other hosts in the SAN. If the PRSV key is not unique or is not registered, or if the KAPL09131-W message appears, execute the dlmprsvkey utility with the -r parameter specified to re-register the PRSV key. If the PRSV key is not registered, the HDLM functions may not operate normally. For details about the dlmprsvkey utility, see 8.4 dlmprsvkey (utility for registering a HDLM persistent reservation key).
    If you used the license key file, it will be deleted when the installation finishes. The KAPL09115-W message appears if deletion of this file fails. In this case, delete the file manually, such as by using Explorer.

  17. Shut down the host.
    Leave the host in a single-path configuration until you check (in step 25) whether HDLM has been successfully installed.

  18. On all the hosts comprising the cluster system, perform steps 3 through 17.

  19. Make sure that all the hosts comprising cluster system have been completely shut down.

  20. Start the host individually.

  21. Log on to the Windows system again as a member of the Administrators group.

  22. Execute the dlnkmgr command's view operation to display the status of each program:
    An example of executing the dlnkmgr command's view operation is as follows:

    >dlnkmgr view -sys
HDLM Version                  : xx-xx
Service Pack Version         : 
Load Balance                  : on(rr)
Support Cluster               : off
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                  : off
Remove LU                       : off
Intermittent Error Monitor   : off
HDLM Manager Ver      WakeupTime
Alive        xx-xx    yyyy/mm/dd hh:mm:ss
HDLM Alert Driver Ver      WakeupTime          ElogMem Size
Alive             xx-xx    yyyy/mm/dd hh:mm:ss 128
HDLM Driver Ver      WakeupTime
Alive       xx-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

  23. Use the results of the dlnkmgr command's view operation to check the version of the installed HDLM.
    When 05-91 is displayed in HDLM Version, the correct version of HDLM has been installed.

  24. Use the results of the dlnkmgr command's view operation to check that the programs are running properly.
    If HDLM Manager, HDLM Alert Driver, and HDLM Driver are all Alive, all programs are running correctly.

  25. After installation finishes, check the path information as described in 3.6 Checking the path configuration, and make sure that you have successfully installed HDLM in a single-path configuration.

  26. Connect cables with all HBAs (multi-path configuration).

  27. Check the path information as described in 3.6 Checking the path configuration to make sure that you have successfully built a multi-path configuration.

  28. Shut down the host.

  29. On all the hosts making up the cluster system, perform the operations from step 20 to step 28.

  30. Start the host individually.

  31. Install MSCS.

  32. Shut down all hosts after completing installation of MSCS in all hosts configured in MSCS.

  33. Start the host individually.

  34. Log on to the Windows system again as a member of the Administrators group.

  35. Make sure that the program is working normally, by examining the results of the dlnkmgr command's view operation.
    Make sure that on MSCS is displayed in Support Cluster. An example of executing the dlnkmgr command's view operation is as follows:

    >dlnkmgr view -sys
HDLM Version                 : xx-xx
Service Pack Version         : 
Load Balance                 : on(rr)
Support Cluster              : on MSCS
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                : off
Remove LU                    : off
Intermittent Error Monitor   : off
HDLM Manager Ver      WakeupTime
Alive        xx-xx    yyyy/mm/dd hh:mm:ss
HDLM Alert Driver Ver      WakeupTime          ElogMem Size
Alive             xx-xx    yyyy/mm/dd hh:mm:ss 128
HDLM Driver Ver      WakeupTime
Alive       xx-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

Installing HDLM after MSCS Installation

To install HDLM on a host that does not currently contain HDLM:

  1. Install MSCS on the host.

  2. Restart the host.

  3. Log on to Windows as a member of the Administrators group.

  4. Store the license key file directly under the Windows installation-destination drive.
    You can also specify the license key directly without using the license key file.
     
installation-drive:\hdlm_license
    The license key file will be deleted when the installation finishes.

  5. Perform the installation.
    • If you do not want to perform an unattended installation, insert the CD-ROM into the drive, and start the installation program setup.exe.
      If HDLM has been installed, the KAPL09129-E message appears. In this case, carry out the procedure shown in 3.5.5 Migrating from HDLM 5.4 or earlier to HDLM 5.5 or later. If HDLM 5.5 or later has been installed, the KAPL09173-W message appears. In this case, carry out the procedure shown in 3.5.4 Upgrade installation or re-installation of HDLM. If no message appears, go to step 6.
    • If you want to perform an unattended installation, insert the CD-ROM into the drive, and start the installation program installhdlm.exe.
      At the command prompt, execute the following command:
      drive-to-which-the-installation-CD-ROM-is-inserted:\DLMTools\installhdlm.exe -f installation-information-settings-file (installhdlm.ini)
      Specify n (do not restart) for the restart key in the installation-information settings file.
      This command checks whether HDLM has already been installed. If HDLM 5.4 or earlier has been installed, the KAPL09129-E message appears. In this case, carry out the procedure shown in 3.5.5 Migrating from HDLM 5.4 or earlier to HDLM 5.5 or later. If HDLM 5.5 or later has been installed, an upgrade installation is performed, and then the KAPL09183-I message appears.
      After the installation is complete, go to step 14.

  6. The program checks the version of the MPIO driver, and then installs the MPIO driver. If a message appears asking you whether you want to install MPIO driver, follow the procedure below:
    • The KAPL09127-W message appears if MPIO driver has already been installed and its version does not match the version of MPIO driver to be installed.
      - Click the Next button to install MPIO driver.
      - Click the Cancel button to cancel the installation.
    • If no message appears, go to the next step.

  7. Specify a license key file or enter a license key in accordance with the instructions shown in the messages that appear on the window.
    • If a license key file was stored in step 4, specify that license key file.
    • If a license key file is not used, specify the license key directly.

  8. Enter user information in accordance with the instructions shown in the messages that appear on the window.

  9. Specify the installation folder in accordance with the instructions shown in the messages that appear on the window.

  10. The utility for registering HDLM persistent reservation keys (dlmprsvkey) is automatically executed to create a PRSV key. The PRSV key is required for the HDLM functions to operate normally. Also, the value of the PRSV key must be unique among hosts. Creation of the PRSV key may be unsuccessful if, for example, an NIC does not exist. Do one of the following in accordance with the result of the execution of the dlmprsvkey utility:
    • If the key creation is successful, the created PRSV key appears in the dialog box. If you do not need to change the value, click the Next button. If you must change the value because another host already has the same PRSV key, change the value, and then click the Next button. If you want to undo the change, click the Back button and then start over from step 9.
    • If the creation is unsuccessful, a dialog box appears that prompts you for the PRSV key. Enter the PRSV key, and then click the OK button.
    For the values you can specify for the PRSV key, follow the instructions shown in the installation program window.

  11. The program checks the PRSV key. If the KAPL09128-W message appears, follow the procedure below:
    • You are prompted to re-enter the PRSV key. Enter an appropriate PRSV key. The program then checks the PRSV key again.
    • If no message appears, go to the next step.

  12. Select an HDLM management-target device only when the OS is one of the following:
    • Windows Server 2003 (IA32) SP1 or later
    • Windows Server 2003 (IPF) SP1 or later
    The Hitachi USP V, TagmaStore, Lightning, Thunder Series and HP StorageWorks XP Series option is always selected. To select the EMC DMX series and CX series as the HDLM management-target device, select EMC Symmetrix DMX Series, CLARiiON CX Series. To select the HP EVA series as the HDLM management-target device, select HP StorageWorks EVA Series.

  13. Follow the instructions shown in the messages that appear on the window.
    • If a dialog box that begins with the following sentence appears during installation, and the Storport Miniport driver is used as the HBA driver, stop the HDLM installation. Then, install QFE838894 or a later version of the Microsoft Storport driver, or install Windows Server 2003 SP1 or later.
      Notes on using a Storport Miniport driver
      Read these notes before using a Storport Miniport driver as an HBA driver.
      The file version of the Storport.sys of this system (Microsoft(R) Storport driver) is n.n.nnnn.n.
      When using a Storport Miniport driver as an HBA driver:
      Please update the Storport Miniport driver to a Storport.sys with a file version n.n.nnnn.n or later.
    • The PRSV key is registered before the installation finishes. If the KAPL09131-W message appears, follow the procedure described in step 15.

  14. Check the results of the installation.
    If you performed an unattended installation, check the installation results in the command prompt.

  15. When the installation finishes, execute the dlmprsvkey utility with the -v parameter specified.
    Make sure that the PRSV key displayed by the dlmprsvkey utility is unique among those of any other hosts in the SAN. If the PRSV key is not unique or is not registered, or if the KAPL09131-W message appears, execute the dlmprsvkey utility with the -r parameter specified to re-register the PRSV key. If the PRSV key is not registered, the HDLM functions may not operate normally. For details about the dlmprsvkey utility, see 8.4 dlmprsvkey (utility for registering a HDLM persistent reservation key).
    If you are using the license key file, it will be deleted when the installation finishes. The KAPL09115-W message appears if deletion of this file fails. In this case, delete the file manually, such as by using Explorer.

  16. Shut down the host.
    Leave the host in a single-path configuration until you check (in step 25) whether HDLM has been successfully installed.

  17. On all the hosts making up the cluster system, perform the operations from step 1 to step 16.

  18. Confirm that all the hosts making up the cluster system have been shut down.

  19. Modify the settings in the storage subsystem.
    Modify the settings in the storage subsystem according to the procedure described in the Hardware Notes provided with HDLM.

  20. Start the host individually.

  21. Log on to the Windows system again as a member of the Administrators group.

  22. Make sure that the program is working normally, by examining the results of the dlnkmgr command's view operation.
    Make sure that on MSCS is displayed in Support Cluster. An example of executing the dlnkmgr command's view operation is as follows:

    >dlnkmgr view -sys
HDLM Version                 : xx-xx
Service Pack Version         : 
Load Balance                 : on(rr)
Support Cluster              : on MSCS
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                : off
Remove LU                    : off
Intermittent Error Monitor   : off
HDLM Manager Ver      WakeupTime
Alive        xx-xx    yyyy/mm/dd hh:mm:ss
HDLM Alert Driver Ver      WakeupTime          ElogMem Size
Alive             xx-xx    yyyy/mm/dd hh:mm:ss 128
HDLM Driver Ver      WakeupTime
Alive       xx-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

  23. Use the results of the dlnkmgr command's view operation to check the version of the installed HDLM.
    When 05-91 is displayed in HDLM Version, the correct version of HDLM has been installed.

  24. Use the results of the view operation to check that the programs are running properly.
    If HDLM Manager, HDLM Alert Driver, and HDLM Driver are all Alive, all programs are running correctly.

  25. After installation finishes, check the path information as described in 3.6 Checking the path configuration, and make sure that you have successfully installed HDLM in a single-path configuration.

  26. Connect cables to all HBAs (multi-path configuration).

  27. Check the path information as described in 3.6 Checking the path configuration to make sure that you have successfully built a multi-path configuration.

(3) When VCS is used

  1. Start the host individually.
    Start them in the single path configuration.

  2. Use the VCS Configuration Wizard to configure Cluster Components.

  3. Restart the host.

  4. Log on to the Windows system as a member of the Administrators group.

  5. Stop VCS.

  6. Store the license key file directly under the Windows installation-destination drive.
    You can also specify the license key directly without using the license key file.

    installation-drive:\hdlm_license

    The license key file will be deleted when the installation finishes.

  7. Perform the installation.
    • If you do not want to perform an unattended installation, insert the CD-ROM into the drive, and start the installation program setup.exe.
      If HDLM has been installed, the KAPL09129-E message appears. In this case, carry out the procedure shown in 3.5.5 Migrating from HDLM 5.4 or earlier to HDLM 5.5 or later. If HDLM 5.5 or later has been installed, the KAPL09173-W message appears. In this case, carry out the procedure shown in 3.5.4 Upgrade installation or re-installation of HDLM. If no message appears, go to step 8.
    • If you want to perform an unattended installation, insert the CD-ROM into the drive, and start the installation program installhdlm.exe.
      At the command prompt, execute the following command:
      drive-to-which-the-installation-CD-ROM-is-inserted:\DLMTools\installhdlm.exe -f installation-information-settings-file (installhdlm.ini)
      Specify n (do not restart) for the restart key in the installation-information settings file.
      This command checks whether HDLM has already been installed. If HDLM 5.4 or earlier has been installed, the KAPL09129-E message appears. In this case, carry out the procedure shown in 3.5.5 Migrating from HDLM 5.4 or earlier to HDLM 5.5 or later. If HDLM 5.5 or later has been installed, an upgrade installation is performed, and then the KAPL09183-I message appears.
      After the installation is complete, go to step 16.

  8. The program checks the version of the MPIO driver, and then installs the MPIO driver. If a message appears asking you whether you want to install MPIO driver, follow the procedure below:
    • The KAPL09127-W message appears if MPIO driver has already been installed and its version does not match the version of MPIO driver to be installed.
      - Click the Next button to install MPIO driver.
      - Click the Cancel button to cancel the installation.
    • If no message appears, go to the next step.

  9. Specify a license key file or enter a license key in accordance with the instructions shown in the messages that appear on the window.
    If a license key file was stored in step 6, specify that license key file.
    If a license key file is not used, specify the license key directly.

  10. Enter user information in accordance with the instructions shown in the messages that appear on the window.

  11. Specify the installation folder in accordance with the instructions shown in the messages that appear on the window.

  12. The utility for registering HDLM persistent reservation keys (dlmprsvkey) is automatically executed to create a PRSV key. The PRSV key is required for the HDLM functions to operate normally. Also, the value of the PRSV key must be unique among hosts. Creation of the PRSV key may be unsuccessful if, for example, an NIC does not exist. Do one of the following in accordance with the result of the execution of the dlmprsvkey utility:
    • If the creation is successful, the created PRSV key appears in the dialog box. If you do not need to change the value, click the Next button. If you must change the value because another host already has the same PRSV key, change the value, and then click the Next button. If you want to undo the change, click the Back button and then start over from step 11.
    • If the creation is unsuccessful, a dialog box appears that prompts you for the PRSV key. Enter the PRSV key, and then click the OK button.
    For the values you can specify for the PRSV key, follow the instructions shown in the installation program window.

  13. The program checks the PRSV key. If the KAPL09128-W message appears, follow the procedure below:
    • You are prompted to re-enter the PRSV key. Enter an appropriate PRSV key. The program then checks the PRSV key again.
    • If no message appears, go to the next step.

  14. The message Select Storage Subsystem to be managed. is displayed: click the Next button.
    In a VCS environment, the EMC DMX series and CX series cannot be set as an HDLM management-target device. Thus, do not select EMC Symmetrix DMX Series, CLARiiON CX Series. Similarly, the HP EVA series cannot be set as an HDLM management-target device. Accordingly, do not select HP StorageWorks EVA Series either.

  15. Follow the instructions shown in the messages that appear on the window.
    • If a dialog box that begins with the following sentence appears during installation, and the Storport Miniport driver is used as the HBA driver, stop the HDLM installation. Then, install QFE838894 or a later version of the Microsoft Storport driver, or install Windows Server 2003 SP1 or later.
      Notes on using a Storport Miniport driver
      Read these notes before using a Storport Miniport driver as an HBA driver.
      The file version of the Storport.sys of this system (Microsoft(R) Storport driver) is n.n.nnnn.n.
      When using a Storport Miniport driver as an HBA driver:
      Please update the Storport Miniport driver to a Storport.sys with a file version n.n.nnnn.n or later.
    • The PRSV key is registered before the installation finishes. If the KAPL09131-W message appears, follow the procedure described in step 17.

  16. Check the results of the installation.
    If you performed an unattended installation, check the installation results in the command prompt.

  17. When the installation finishes, execute the dlmprsvkey utility with the -v parameter specified.
    Make sure that the PRSV key displayed by the dlmprsvkey utility is unique among those of any other hosts in the SAN. If the PRSV key is not unique or is not registered, or if the KAPL09131-W message appears, execute the dlmprsvkey utility with the -r parameter specified to re-register the PRSV key. If the PRSV key is not registered, the HDLM functions may not operate normally. For details about the dlmprsvkey utility, see 8.4 dlmprsvkey (utility for registering a HDLM persistent reservation key).
    If you used the license key file, it will be deleted when the installation finishes. The KAPL09115-W message appears if deletion of this file fails. In this case, delete the file manually, such as by using Explorer.

  18. Shut down the host.
    Leave the host in a single-path configuration until you check (in step 25) whether HDLM has been successfully installed.

  19. Modify the settings in the storage subsystem.
    Modify the settings in the storage subsystem according to the procedure described in the Hardware Notes provided with HDLM.

  20. Start the host individually.

  21. Log on to the Windows system again as a member of the Administrators group.

  22. Make sure that the program is working normally, by examining the results of the dlnkmgr command's view operation.
    An example of executing the dlnkmgr command's view operation is as follows:

    >dlnkmgr view -sys
HDLM Version                 : xx-xx
Service Pack Version         : 
Load Balance                 : on(rr)
Support Cluster              : off
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                : off
Remove LU                    : off
Intermittent Error Monitor   : off
HDLM Manager Ver      WakeupTime
Alive        xx-xx    yyyy/mm/dd hh:mm:ss
HDLM Alert Driver Ver      WakeupTime          ElogMem Size
Alive             xx-xx    yyyy/mm/dd hh:mm:ss 128
HDLM Driver Ver      WakeupTime
Alive       xx-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 if you are using VCS, off appears for Support Cluster. Regardless, the cluster support function runs normally.

  23. Use the results of the view operation to check the version of the installed HDLM.
    When 05-91 is displayed in HDLM Version, the correct version of HDLM has been installed.

  24. Use the results of the view operation to check that the programs are running properly.
    If HDLM Manager, HDLM Alert Driver, and HDLM Driver are all Alive, all programs are running correctly.

  25. After installation finishes, check the path information as described in 3.6 Checking the path configuration, and make sure that you have successfully installed HDLM in a single-path configuration.

  26. Connect cables to all HBAs (multi-path configuration).

  27. Check the path information as described in 3.6 Checking the path configuration to make sure that you have successfully built a multi-path configuration.

(4) When Oracle RAC is used

  1. Shut down all the hosts.

  2. Make sure that all the hosts comprising the cluster system have been fully shut down.

  3. Start the host individually.
    Start them in the single path configuration.

  4. Log on to Windows as a member of the Administrators group.

  5. Store the license key file directly under the Windows installation-destination drive. You can also specify the license key directly without using the license key file.

    installation-drive:\hdlm_license

    The license key file will be deleted when the installation finishes.

  6. Perform the installation.
    • If you do not want to perform an unattended installation, insert the CD-ROM into the drive, and start the installation program setup.exe.
      The program checks whether HDLM has already been installed. If HDLM 5.4 or earlier has been installed, the KAPL09129-E message appears. In this case, carry out the procedure shown in 3.5.5 Migrating from HDLM 5.4 or earlier to HDLM 5.5 or later. If HDLM 5.5 or later has been installed, the KAPL09173-W message appears. In this case, carry out the procedure shown in 3.5.4 Upgrade installation or re-installation of HDLM. If no message appears, go to step 7.
    • If you want to perform an unattended installation, insert the CD-ROM into the drive, and start the installation program installhdlm.exe.
      At the command prompt, execute the following command:
      drive-to-which-the-installation-CD-ROM-is-inserted:\DLMTools\installhdlm.exe -f installation-information-settings-file (installhdlm.ini)
      Specify n (do not restart) for the restart key in the installation-information settings file.
      This command checks whether HDLM has already been installed. If HDLM 5.4 or earlier has been installed, the KAPL09129-E message appears. In this case, carry out the procedure shown in 3.5.5 Migrating from HDLM 5.4 or earlier to HDLM 5.5 or later. If HDLM 5.5 or later has been installed, an upgrade installation is performed, and then the KAPL09183-I message appears.
      After the installation is complete, go to step 15.

  7. The program checks the version of the MPIO driver, and then installs the MPIO driver. If a message appears asking you whether you want to install the MPIO driver, follow the procedure below:
    • The KAPL09127-W message appears if MPIO driver has already been installed and its version does not match the version of MPIO driver to be installed.
      - Click the Next button to install MPIO driver.
      - Click the Cancel button to cancel the installation.
    • If no message appears, go to the next step.

  8. Specify a license key file or enter a license key in accordance with the instructions shown in the messages that appear on the window.
    If a license key file was stored in step 5, specify that license key file.
    If a license key file is not used, specify the license key directly.

  9. Enter user information in accordance with the instructions shown in the messages that appear on the window.

  10. Specify the installation folder in accordance with the instructions shown in the messages that appear on the window.

  11. The utility for registering HDLM persistent reservation keys (dlmprsvkey) is automatically executed to create a PRSV key. The PRSV key is required for the HDLM functions to operate normally. Also, the value of the PRSV key must be unique among hosts. Creation of the PRSV key may be unsuccessful if, for example, an NIC does not exist. Do one of the following in accordance with the result of the execution of the dlmprsvkey utility:
    • If the key creation is successful, the created PRSV key appears in the dialog box. If you do not need to change the value, click the Next button. If you must change the value because another host already has the same PRSV key, change the value, and then click the Next button. If you want to undo the change, click the Back button and then start over from step 10.
    • If the creation is unsuccessful, a dialog box appears that prompts you for the PRSV key. Enter the PRSV key, and then click the OK button.
    For the values you can specify for the PRSV key, follow the instructions shown in the installation program window.

  12. The program checks the PRSV key. If the KAPL09128-W message appears, follow the procedure below:
    • You are prompted to re-enter the PRSV key. Enter an appropriate PRSV key. The program then checks the PRSV key again.
    • If no message appears, go to the next step.

  13. The message Select Storage Subsystem to be managed. is displayed: click the Next button.
    In an Oracle RAC environment, the EMC DMX series and EMC CX series cannot be set as an HDLM management-target device. Thus, do not select EMC Symmetrix DMX Series, CLARiiON CX Series. Similarly, the HP EVA series cannot be set as an HDLM management-target device. Accordingly, do not select HP StorageWorks EVA Series either.

  14. Follow the instructions shown in the messages that appear on the window.
    • If a dialog box that begins with the following sentence appears during installation, and the Storport Miniport driver is used as the HBA driver, stop the HDLM installation. Then, install QFE838894 or a later version of the Microsoft Storport driver, or install Windows Server 2003 SP1 or later.
      Notes on using a Storport Miniport driver
      Read these notes before using a Storport Miniport driver as an HBA driver.
      The file version of the Storport.sys of this system (Microsoft(R) Storport driver) is n.n.nnnn.n.
      When using a Storport Miniport driver as an HBA driver:
      Please update the Storport Miniport driver to a Storport.sys with a file version n.n.nnnn.n or later.
    • The PRSV key is registered before the installation finishes. If the KAPL09131-W message appears, follow the procedure described in step 16.

  15. Check the results of the installation.
    If you performed an unattended installation, check the installation results in the command prompt.

  16. When the installation finishes, execute the dlmprsvkey utility with the -v parameter specified.
    Make sure that the PRSV key displayed by the dlmprsvkey utility is unique among those of any other hosts in the SAN. If the PRSV key is not unique or is not registered, or if the KAPL09131-W message appears, execute the dlmprsvkey utility with the -r parameter specified to re-register the PRSV key. If the PRSV key is not registered, the HDLM functions may not operate normally. For details about the dlmprsvkey utility, see 8.4 dlmprsvkey (utility for registering a HDLM persistent reservation key).
    If you used the license key file, it will be deleted when the installation finishes. The KAPL09115-W message appears if deletion of this file fails. In this case, delete the file manually, such as by using Explorer.

  17. Shut down the host.
    Leave the host in a single-path configuration until you check (in step 25) whether HDLM has been successfully installed.

  18. On all the hosts comprising the cluster system, perform steps 3 through 17.

  19. Make sure that all the hosts comprising cluster system have been completely shut down.

  20. Start the host individually.

  21. Log on to the Windows system again as a member of the Administrators group.

  22. Execute the dlnkmgr command's view operation to display the status of each program:
    An example of executing the dlnkmgr command's view operation is as follows:

    >dlnkmgr view -sys
HDLM Version                 : xx-xx
Service Pack Version         : 
Load Balance                 : on(rr)
Support Cluster              : off
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                : off
Remove LU                    : off
Intermittent Error Monitor   : off
HDLM Manager Ver      WakeupTime
Alive        xx-xx    yyyy/mm/dd hh:mm:ss
HDLM Alert Driver Ver      WakeupTime          ElogMem Size
Alive             xx-xx    yyyy/mm/dd hh:mm:ss 128
HDLM Driver Ver      WakeupTime
Alive       xx-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

  23. Use the results of the dlnkmgr command's view operation to check the version of the installed HDLM.
    When 05-91 is displayed in HDLM Version, the correct version of HDLM has been installed.

  24. Use the results of the dlnkmgr command's view operation to check that the programs are running properly.
    If HDLM Manager, HDLM Alert Driver, and HDLM Driver are all Alive, all programs are running correctly.

  25. After installation finishes, check the path information as described in 3.6 Checking the path configuration, and make sure that you have successfully installed HDLM in a single-path configuration.

  26. Connect cables with all HBAs (multi-path configuration).

  27. Check the path information as described in 3.6 Checking the path configuration to make sure that you have successfully built a multi-path configuration.

  28. Shut down the host.

  29. On all the hosts making up the cluster system, perform the operations from step 18 to step 27.

  30. Install and configure Oracle RAC.
    The following conditions are satisfied, you must change the settings for Oracle RAC 10g after building the environment.
    • Release of 10.1.0.3.0 or later of Oracle RAC 10g is being used.
    • A host and a voting disk are connected by multiple paths (in a multi-path configuration) in an FC-SAN environment.
    For details, see 3.4 Notes on creating an HDLM environment.

  31. Make sure that the program is working normally, by examining the results of the dlnkmgr command's view operation.
    An example of executing the dlnkmgr command's view operation is as follows:

    >dlnkmgr view -sys
HDLM Version                 : xx-xx
Service Pack Version         : 
Load Balance                 : on(rr)
Support Cluster              : off
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                : off
Remove LU                    : off
Intermittent Error Monitor   : off
HDLM Manager Ver      WakeupTime
Alive        xx-xx    yyyy/mm/dd hh:mm:ss
HDLM Alert Driver Ver      WakeupTime          ElogMem Size
Alive             xx-xx    yyyy/mm/dd hh:mm:ss 128
HDLM Driver Ver      WakeupTime
Alive       xx-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 if you are using Oracle RAC, off appears for Support Cluster. Regardless, the cluster support function runs normally.

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2003, 2007, Hitachi, Ltd.