Hitachi Command Suite Dynamic Link Manager Software User Guide for Windows® Document Organization Product Version Getting Help Contents MK-92DLM129-28
© 2011-2013 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd. Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use.
Contents Preface..................................................................................................xi Intended audience....................................................................................................xii Product version........................................................................................................xii Release notes...........................................................................................................xii Document revision level...
Automatic Failovers...............................................................................2-17 Automatic Failbacks...............................................................................2-19 Manual Path Switching....................................................................................2-19 Path Status Transition.....................................................................................2-20 The Online Path Statuses............................................................
Disk Requirements.................................................................................3-12 Number of LUs and Paths That Are Supported in HDLM.....................................3-13 Flow for Creating an HDLM Environment.................................................................3-13 HDLM Installation Types........................................................................................3-14 Notes on Creating an HDLM Environment.........................................................
Notes on Removing HDLM...............................................................................3-84 Removing HDLM.............................................................................................3-86 Removal Procedures - in a Non-Cluster Environment................................3-86 Removal Procedures - MSCS or VCS Environment....................................3-88 Removal Procedures - Oracle RAC Environment.......................................
5 Troubleshooting....................................................................................5-1 Information Collected by the DLMgetras Utility for Collecting HDLM Error Information. 5-2 Checking Error Information in Messages...................................................................5-2 What To Do for a Path Error....................................................................................5-4 Examining the Messages......................................................................
To Display Program Information.............................................................6-32 To Display HDLM Management-target Device Information........................6-32 To Display Path Information...................................................................6-32 To Display LU Information......................................................................6-33 To Display the Format of the view Operation...........................................6-33 Parameters...................................
8 Messages.............................................................................................8-1 Before Viewing the List of Messages.........................................................................8-3 Format and Meaning of Message IDs................................................................. 8-3 Terms Used in Messages and Message Explanations............................................8-3 KAPL01001 to KAPL02000........................................................................
x Hitachi Dynamic Link Manager User Guide for Windows®
Preface This document describes how to use the Hitachi Dynamic Link Manager.
Intended audience This document is intended for storage administrators who use Hitachi Dynamic Link Manager (HDLM) to operate and manage storage systems, and assumes that readers have: • Knowledge of Windows and its management functionality • Knowledge of Storage system management functionality • Knowledge of Cluster software functionality • Knowledge of Volume management software functionality Product version This document revision applies to HDLM for Windows version 7.6 or later.
Document organization The following table provides an overview of the contents and organization of this document. Click the chapter title in the left column to go to that chapter. The first page of each chapter provides links to the sections in that chapter. Chapter/Appendix Description Chapter 1, Overview of HDLM on Describes an overview of HDLM, and its features. page 1-1 Chapter 2, HDLM Functions on page 2-1 Describes the system configuration of HDLM, and the basic terms and functions for HDLM.
• Hitachi USP Series User's Guide • Hitachi Workgroup Modular Storage Series User's Guide • Thunder9580V Series Disk Array Subsystem User's Guide • Reference Manual / File Conversion Utility & File Access Library • Universal Storage Platform V User's Guide • Universal Storage Platform VM User's Guide • Virtual Storage Platform User's Guide Document conventions This document uses the following typographic conventions: Convention Description Bold Indicates text on a window, other than the win
Physical capacity unit Value 1 kilobyte (KB) 1,000 (103) bytes 1 megabyte (MB) 1,000 KB or 1,0002 bytes 1 gigabyte (GB) 1,000 MB or 1,0003 bytes 1 terabyte (TB) 1,000 GB or 1,0004 bytes 1 petabyte (PB) 1,000 TB or 1,0005 bytes 1 exabyte (EB) 1,000 PB or 1,0006 bytes Logical storage capacity values (for example, logical device capacity) are calculated based on the following values: Logical capacity unit Value 1 block 512 bytes 1 KB 1,024 (210) bytes 1 MB 1,024 KB or 1,0242 bytes 1 GB 1
paragraphs whenever possible. All comments become the property of Hitachi Data Systems Corporation.
1 Overview of HDLM HDLM is a software package that manages paths between a host and a storage system. HDLM is designed to distribute loads across multiple paths and will switch a given load to another path if there is a failure in the path that is currently being used, thus improving system reliability. This chapter gives an overview of HDLM and describes its features.
What is HDLM? With the widespread use of data warehousing and increasing use of multimedia data, the need for high-speed processing of large volumes of data on networks has rapidly grown. To satisfy this need, networks dedicated to the transfer of data, such as SANs, are now being used to provide access to storage systems. HDLM manages the access paths to these storage systems.
The ability to continue running operations between a host and storage system, even if there is a failure. This is also known as performing a failover. When a host is connected to a storage system via multiple paths, HDLM can automatically switch to another path if there is some sort of failure in the path that is currently being used. This allows operations to continue between a host and a storage system.
1-4 Overview of HDLM Hitachi Dynamic Link Manager User Guide for Windows®
2 HDLM Functions This chapter describes the various functions that are built into HDLM. Before the function specifications are explained though, this chapter will go into detail about the HDLM management targets, system configuration, and basic terms that are necessary to know to effectively operate HDLM. After that, the rest of the chapter focuses on describing all the HDLM functions, including the main ones: load distribution across paths and path switching.
□ Collecting Audit Log Data □ Integrated HDLM management using Global Link Manager □ Cluster Support 2-2 HDLM Functions Hitachi Dynamic Link Manager User Guide for Windows®
Devices Managed by HDLM Below is a list of devices that can or cannot be managed by HDLM. The devices that can be managed by HDLM are called HDLM management-target devices.
The following figure shows the configuration of an HDLM system using an FCSAN. Figure 2-1 Configuration of an HDLM System When Using an FC-SAN The following table lists the HDLM system components when using an FCSAN. Table 2-1 HDLM System Components When Using an FC-SAN Components Description HBA A host bus adapter. This serves as a cable port on the host. FC-SAN A dedicated network that is used for the transfer of data between hosts and storage systems CHA A channel adapter P A port on a CHA.
must be installed ahead of time on the host. The cable port on the storage system is called a port (P) on a channel adapter (CHA) used for iSCSI connections. A logical unit (LU), which lies in a storage system, is either an input target or an output target to or from a host. The areas within an LU are called Devs. A route that connects a host to a Dev in an LU is called a path. HDLM assigns a unique ID to each management-target path. This ID is called AutoPATH_ID.
Figure 2-3 Configuration of an IP-SAN System When Using iSCSI Software and an NIC The following table lists the HDLM system components when using an IP-SAN. Table 2-2 HDLM System Components When Using an IP-SAN Components Description iSCSI software The driver software that contains the iSCSI initiator function iSCSI HBA A host bus adapter that contains the iSCSI initiator function. This serves as a cable port on a host. The iSCSI HBA is referred to as the HBA in HDLM commands and the HDLM GUI.
Setting Range of the iSCSI Software and iSCSI HBA The following describes the ranges that can be used for the iSCSI software and iSCSI HBA settings. For notes on how to set these values, see the corresponding documentation for your particular iSCSI software and iSCSI HBA. • IP addresses Use the same network address for both an HBA and a CHA port connected via a common path. • Other settings ¢ An IP-SAN can be used for multiple hosts. ¢ A single HBA can connect to multiple CHA ports.
After the installation of HDLM, an LU recognized by a host is called a host LU (HLU). The areas in a host LU that correspond to the Devs in a storage system LU are called host devices (HDev). On a system using HDLM, in order to access a target LU, a drive letter is first assigned to the disk that has been integrated by the MPIO driver. Such disks are displayed in the Windows' Disk Management window. The following figure shows the LU configuration recognized by the host, after the installation of HDLM.
Program Configuration HDLM is actually a combination of several programs. Because each program corresponds to a specific HDLM operation, it is important to understand the name and purpose of each program, along with how they are all interrelated. The following figure shows the configuration of the HDLM programs. Figure 2-5 Configuration of the HDLM Programs The following table lists and describes the functions of these programs.
Program name HDLM manager Functions • Clear persistent reservations • Register persistent reservation keys • Check the configuration of the paths • Check the installation information • Perform unattended installations of HDLM • Perform unattended removals of HDLM Provides the HDLM manager, which enables you to: • Configure the operating environment • Request path health checks and automatic failbacks to be performed • Collect error log data HDLM alert driver Reports the log information
Figure 2-6 Driver Levels of the HDLM and MPIO Drivers Distributing a Load Using Load Balancing When the system contains multiple paths to a single LU, HDLM can distribute the load across the paths by using multiple paths to transfer the I/O data. This function is called load balancing, and it prevents a single, heavily loaded path from affecting the performance of the entire system. Note that some I/O operations managed by HDLM can be distributed across all, available paths, and some cannot.
Platform V/VM series, and Virtual Storage Platform series. In a non-cluster environment, the load balancing function is available for the Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi AMS2000/AMS/ WMS/SMS series, Hitachi USP series, Universal Storage Platform V/VM series, Virtual Storage Platform series, and EMC DMX series. For details on the various cluster software that HDLM supports, see Cluster Support on page 2-46.
Figure 2-8 Flow of I/O Data When the Load Balancing Function Is Used When the load balancing function is used, I/O operations are distributed via multiple paths (A, B, C, and D). This helps to prevent problems with system performance and helps prevent bottlenecks from occurring. Paths to Which Load Balancing Is Applied This subsection describes, for each type of storage system, the paths to which the load balancing function is applied.
load balancing will be performed among the remaining, usable owner paths. It is only when absolutely no owner paths are available, that load balancing is then performed among the non-owner paths. For the example in Figure 2-9 Overview of Load Balancing on page 2-14, suppose that in the owner controller of LU0 is CHA0. When the LU is accessed, the load is balanced between the two paths A and B, which are both owner paths.
¢ Virtual Storage Platform series ¢ Hitachi AMS2000 series# ¢ Hitachi SMS series# ¢ HUS100 series# HUS VM #: This storage system applies when the dynamic I/O path control function is disabled.
If the data is not sequential, these algorithms select the path to be used each time an I/O request is issued. ¢ ¢ ¢ Extended Round Robin The paths are simply selected in order from among all the connected paths. Extended Least I/Os The path that has the least number of I/Os being processed is selected from among all the connected paths. Extended Least Blocks The path that has the least number of I/O blocks being processed is selected from among all the connected paths.
Performing Failovers and Failbacks Using Path Switching When the system contains multiple paths to an LU and an error occurs on the path that is currently being used, HDLM can switch to another functional path, so that the system can continue operating. This is called a failover. If a path in which an error has occurred recovers from the error, HDLM can then switch back to that path. This is called a failback.
If the Thunder 9500V series, or Hitachi AMS/WMS series is being used, HDLM will select the path to be used next from among the various paths that access the same LU, starting with owner paths, and then non-owner paths. For example, in Figure 2-10 Path Switching on page 2-18, the owner controller of an LU is CHA0, and access to the LU is made via only one path (A). After that access path (A) is placed offline, the first choice for the switching destination is the other path connected to CHA0 (B).
Automatic Failbacks When a path recovers from an error, HDLM can automatically place the recovered path back online. This function is called the automatic failback function. In order to use the automatic failback function, HDLM must already be monitoring error recovery on a regular basis. When using the Thunder 9500V series, or Hitachi AMS/WMS series, HDLM will select the next path to be used first from among the online owner paths, and then from the online non-owner paths.
You can manually place a path online or offline by doing the following: • Use the HDLM GUI Path Management window. • Execute the dlnkmgr command's online or offline operation. For details on the online operation, see online (Places Paths Online) on page 6-11. For details on the offline operation, see offline (Places Paths Offline) on page 6-6. However, if there is only one online path for a particular LU, that path cannot be manually switched offline.
The Online Path Statuses The online path statuses are as follows: • Online I/Os can be issued normally. • Online(P) A state in which a path in the Online status is in the waiting-to-execute status to be taken offline. This status occurs in a cluster configuration only. The Online(P) status indicates that the user has requested an Online path to be taken offline, for a path that is connected to an LU that is currently performing reserve processing.
The paths to the primary volume (P-VOL) in the HAM environment have recovered from an error, but I/O to the P-VOL is suppressed. • Online(D)# The paths to the primary volume (P-VOL) in an HAM environment have recovered from an error, but I/O to the P-VOL is suppressed. If an error occurs in all the paths to a secondary volume (S-VOL), the status of the P-VOL paths will be automatically changed to the Online status.
Figure 2-11 Path Status Transitions Legend: Online operation: Online operation performed in the Path Management window or by executing the dlnkmgr command's online operation. Offline operation: Offline operation performed in the Path Management window or by executing the dlnkmgr command's offline operation. #1 During reserve processing for an LU, the Online status is temporarily changed to Online(P). When the reservation processing finishes, the Online(P) status is changed to Offline(C).
When the following conditions are all satisfied, a path that has been determined to have an intermittent error also becomes subject to automatic failback: ¢ ¢ ¢ All the paths connected to an LU are Online(E), Offline(E), or Offline(C). All the paths connected to an LU have been determined to have an intermittent error. The processing of continuous I/O operations issued to an LU is successful. #5 During reserve processing for an LU, the Offline(E) status is temporarily changed to Offline(P).
Online operation: Online operation performed by executing the dlnkmgr command's online operation. Offline operation: Offline operation performed by executing the dlnkmgr command's offline operation. #1 Also when an error occurs in all the paths to an S-VOL in the Online(D) status. #2 When I/O operations are processed on an S-VOL. If there is only one available online path for an LU, it cannot be placed offline by using the Path Management window or by executing the offline operation.
HDLM command or the HDLM GUI, and then make sure that the status has changed to Offline(C). If it is still Offline(E), retry the offline operation. Monitoring Intermittent Errors (Functionality When Automatic Failback Is Used) An intermittent error refers to an error that occurs irregularly because of something like a loose cable. In such a case, I/O performance might decrease while an automatic failback is being performed to repair an intermittent error.
monitoring depend on the values specified for automatic failbacks. For details on how to specify the settings, see set (Sets Up the Operating Environment) on page 6-16 or the HDLM GUI Help. Intermittent Error Monitoring Actions Intermittent error monitoring is performed on each path, and it automatically starts as soon as a path is recovered from an error by using the automatic failback function.
When an Intermittent Error Does Not Occur If an error does not occur on a path a specified number of times within a specified interval, an intermittent error will not occur. In such a case, the error monitoring will finish when the specified error-monitoring interval finishes, upon which the number of errors is reset to 0. If an error occurs on the path again at a later time, error monitoring will resume when the path is recovered from the error via an automatic failback.
since the error monitoring started are both reset to 0. As such, the error monitoring will not finish, and it will start over by using the new conditions. If the conditions are changed while error monitoring is not being performed, error monitoring will start up again and use the updated conditions after any given path is recovered from an error by performing an automatic failback.
Table 2-6 When Effects of a User Changing the Intermittent Error Information User operation Changing the intermittent error monitoring settings Turning off Number of errors and time passed since error monitoring started Information about paths not subject to automatic failback Reset Reset#1 Changing the conditions for Reset#2 an intermittent error while intermittent error monitoring is being performed Inherited Turning intermittent error monitoring on by executing the set operation, (but not chang
User operation Restarting the host Number of errors and time passed since error monitoring started Information about paths not subject to automatic failback Reset Reset #1 When you turn the intermittent error monitoring function off, information about paths not subject to automatic failback will be reset. If you do not want to reset the information about paths not subject to automatic failback when you turn the intermittent error monitoring function off, change the target paths to Offline(C).
For example, in a normal state, I/O operations are not performed on the paths coming from the standby host in the cluster configuration or on nonowner paths (that is, some of the paths that access a Thunder 9500V series, or Hitachi AMS/WMS series storage system). Because of this, for the standby host or for a host connected to non-owner paths, we recommend that you use path health checking to detect errors.
The dynamic I/O path control function can be enabled or disabled based on each host, connected storage system, or LU. The dynamic I/O path control function can be specified by using the HDLM command's set operation. For details about the set operation, see set (Sets Up the Operating Environment) on page 6-16. Dynamic Re-configuration Utilizing the Windows plug-and-play functionality, you can add or delete an LU or a path while the host (on which HDLM is installed) is still running.
Figure 2-16 Flow of Data When Collecting Error Information Logs might be collected in layers below HDLM, such as for the SCSI driver. For more details, see the Windows documentation. Types of Collected Logs HDLM collects information on detected errors and trace information and stores it into the integrated trace file, trace file, error logs and event logs. You can use the error information to examine the status of an error and analyze the cause of the error.
A system memory dump file is a file to which the system memory data is output when a Windows system is down. Specify the following procedure to output the system memory dump file. Click Control Panel, System, Startup/Shutdown, Write Debugging Information is chosen with Recovery, and then choose Kernel Memory Dump or Complete Memory Dump. The following table lists and describes the error information that can be collected in logs.
For Windows Server 2003 (excluding the x86 edition) , Windows Server 2008 (excluding the x86 edition), and Windows Server 2012 Program Files is Program Files (x86). #2 The underlined part indicates the folder specified during the installation. After obtaining these files, be sure to also copy them to a backup location. For details on error levels, see Filtering of Error Information on page 2-36. Note To collect logs, HDLM uses the Hitachi Network Objectplaza Trace Library service.
¢ ¢ ¢ Collects error information from the Warning level and higher. Collects error information from the Information level and higher (information from all the levels is collected). Collects error information from the Information level and higher (including maintenance information).
Category Explanation • An abnormal hardware or software event, including: Failure LinkStatus • Hardware errors • Software errors (such as memory errors) An event indicating the linkage status between devices: • ExternalService Authentication AccessControl ContentAccess ConfigurationAccess Maintenance 2-38 Startup and termination of software running on storage systems, software running on SVPs (service processors), and Hitachi Command Suite products Link up or link down An event indicating
Category AnomalyEvent Explanation An event indicating an abnormal state such as exceeding a threshold, including: • Exceeding a network traffic threshold • Exceeding a CPU load threshold • Reporting that the temporary audit log data saved internally is close to its maximum size limit or that the audit log files have wrapped back around to the beginning An event indicating an occurrence of abnormal communication, including: • A SYN flood attack or protocol violation for a normally used port • Acces
Category Authentication ConfigurationAccess 2-40 Explanation Audit event Severity #1 Message ID Startup of the HDLM GUI was successful. 6 KAPL15201-I Startup of the HDLM GUI failed. 4 KAPL15204-W Termination of the HDLM GUI was successful. 6 KAPL15202-I Administrator or Permission has end-user not been granted authentication to execute the HDLM command. 4 KAPL15111-W Permission has not been granted to execute HDLM utilities.
Category Explanation Audit event An attempt to display program information was successful. Severity #1 6 Message ID KAPL15107-I An attempt to 4 display program information failed. KAPL15108-W An attempt to 6 display HDLM managementtarget information was successful. KAPL15109-I An attempt to 4 display HDLM managementtarget information failed. KAPL15110-W An attempt to place a path online by using the HDLM GUI was successful.
Category Explanation Audit event Severity #1 Message ID An attempt to perform an operation by using the HDLM GUI failed. 4 KAPL15206-W Processing of the dlmprsvkey -r command was successful. 6 KAPL15030-I Processing of the dlmprsvkey -r command failed. 4 KAPL15031-W Processing of the dlmprsvkey -v command was successful. 6 KAPL15032-I Processing of the dlmprsvkey -v command failed. 4 KAPL15033-W Processing of the dlmchkpath singleconnect command was successful.
Requirements for Outputting Audit Log Data HDLM can output audit log data when all of the following conditions are satisfied: • The Event Log service is running. • The output of audit log data has been enabled by using the HDLM command's set operation. However, audit log data might still be output regardless of the above conditions if, for example, an HDLM utility is executed from external media.
¢ StartStop ¢ Authentication ¢ ConfigurationAccess ¢ All of the above For details on how to specify audit log settings, see Setting Up the HDLM Functions on page 3-71. Audit Log Data Formats The following describes the format of audit log data: The following is the format of audit log data.
Item# Explanation Audit event result Event result Subject ID for audit event result Depending on the event, an account ID, process ID, or IP address is output.
For large-scale system configurations using many hosts running HDLM, the operational load for managing paths on individual hosts increases with the size of the configuration. By linking HDLM and Global Link Manager, you can centrally manage path information for multiple instances of HDLM and reduce operational load. In addition, you can switch the operational status of paths to perform system-wide load balancing, and centrally manage the system by collecting HDLM failure information in Global Link Manager.
For details about the cluster software supported by HDLM, see Table 3-5 Supported Cluster Software on page 3-7 in Cluster Software Supported by HDLM on page 3-6. When load balancing is used by cluster software supported by HDLM, HDLM uses an active host path to access an LU.
2-48 HDLM Functions Hitachi Dynamic Link Manager User Guide for Windows®
3 Creating an HDLM Environment This chapter explains how to set up an HDLM environment and also how to erase environment settings. Make sure that you have already installed HDLM and configured the function settings.
HDLM System Requirements Check the following before installing HDLM: For the requirements for using HDLM in an HAM environment, see the release notes of HDLM. OSs Supported by HDLM This subsection describes the OSs, Microsoft MPIO drivers, and Web browsers supported by HDLM. Supported OSs You can install HDLM on any of the OSs described in the following table.
OS Service pack Windows Server 2012 (x64) No service pack Note: In this manual, Windows running on a 32-bit processor is referred to as x86. # To use the Storport Miniport driver for the HBA driver in an environment where SP1 or later has not been installed, QFE update program QFE 838894 or later provided by Microsoft is required. Microsoft MPIO Drivers The following table lists the versions of the Microsoft MPIO driver that are bundled with HDLM.
Table 3-3 Supported Storage systems OS Supported storage systems#1 Windows Server 2003 Windows Server 2008 x86 IPF x64 x86 IPF x64 x64 EMC DMX series#2 FC I/F Y#3 Y#3 -- -- -- -- -- EMC CX series#4 FC I/F Y#3 Y#3 Y Y Y Y -- • Hitachi AMS series FC I/F Y Y Y Y Y Y -- • Hitachi WMS series iSCSI I/F Y Y Y Y Y Y -- FC I/F Y Y Y Y Y Y Y iSCSI I/F Y Y Y Y Y Y Y FC I/F Y Y Y Y Y Y -- iSCSI I/F Y Y Y Y Y Y -- FC I/F Y Y Y Y Y Y -
OS Supported storage systems#1 Interf ace Windows Server 2003 Windows Server 2008 Wind ows Serve r 2012 x86 IPF x64 x86 IPF x64 x64 FC I/F Y Y Y Y Y Y Y Lightning 9900 series FC I/F Y Y Y -- -- -- -- Lightning 9900V series FC I/F Y Y Y Y Y Y -- iSCSI I/F Y Y Y -- -- -- -- FC I/F Y Y Y Y Y Y -- FC I/F Y Y Y Y Y Y -- • XP20000 • XP24000 • SVS • XP10000 • XP12000 Thunder 9500V series Legend: Y: Usable --: Not usable FC I/F: FC Interface i
HP EVA8000. When using HP EVA systems other than the HP EVA8000, evaluate the connection in advance. HBAs For details about the supported HBAs, see the HDLM Release Notes. When Using Intermediate Volumes Managed by Hitachi RapidXchange to Exchange Data The following table lists the related programs for when intermediate volumes managed by Hitachi RapidXchange are used to exchange data.
Table 3-5 Supported Cluster Software OS Windows Server 2003 (IPF)#2 SP EMC CX series HP EVA series MSCS Y Y Y Y SP1 MSCS Y Y Y Y VCS 5.0 Y -- -- -- Oracle RAC 10g#1 Y -- -- -- MSCS Y Y Y Y VCS 5.0 Y -- -- -- Oracle RAC 10g#1 Y -- -- -- MSCS Y -- Y Y VCS 4.3 Y -- -- -- Oracle RAC 10g#1 Y -- -- -- MSCS Y -- Y Y VCS 4.3 Y -- -- -- Oracle RAC 10g#1 Y -- -- -- Oracle RAC 11g#1 Y -- -- -- MSCS Y -- Y Y VCS 4.3, 5.
OS SP SP2 Windows Server 2003 (x86)#2 No service pack SP1 SP2 3-8 Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP series, Hitachi AMS2000/ AMS/WMS/ SMS series, Universal Storage Platform V/VM series, Virtual Storage Platform series, and HUS VM EMC DMX series EMC CX series HP EVA series Oracle RAC 10g#1 Y -- -- -- Oracle RAC 11g#1 Y -- -- -- MSCS Y -- Y Y VCS 4.3, 5.
OS Windows Server 2003 R2 (x86)#2 Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP series, Hitachi AMS2000/ AMS/WMS/ SMS series, Universal Storage Platform V/VM series, Virtual Storage Platform series, and HUS VM EMC DMX series EMC CX series HP EVA series Oracle RAC 10g#1 Y -- -- -- Oracle RAC 11g#1 Y -- -- -- MSCS Y Y Y Y VCS 4.3, 5.0 Y -- -- -- Oracle RAC 10g#1 Y -- -- -- Oracle RAC 11g#1 Y -- -- -- MSCS Y Y Y Y VCS 4.3, 5.0, 5.
OS Windows Server 2008 (x64) Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP series, Hitachi AMS2000/ AMS/WMS/ SMS series, Universal Storage Platform V/VM series, Virtual Storage Platform series, and HUS VM EMC DMX series EMC CX series HP EVA series MSCS Y -- Y -- Oracle RAC 10g#1 Y -- -- -- Oracle RAC 11g#1 Y -- -- -- MSCS Y -- Y -- Oracle RAC 11g#1 Y -- -- -- MSCS Y -- Y -- VCS 5.
OS Windows Server 2012 (x64) SP No service pack Cluster software name Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP series, Hitachi AMS2000/ AMS/WMS/ SMS series, Universal Storage Platform V/VM series, Virtual Storage Platform series, and HUS VM EMC DMX series EMC CX series HP EVA series Y -- -- -- MSCS Legend: Y: Usable --: Not usable #1 For details about Oracle RAC versions, see the HDLM Release Notes.
Volume Managers Supported by HDLM The following table lists and describes the related programs for when a volume manager is used. Table 3-6 Related Programs When a Volume Manager Is Used OS Related programs Windows Server 2003 (IPF)# Veritas Storage Foundation for Windows 5.0 Windows Server 2003 (x64)# Veritas Storage Foundation for Windows 5.0 Windows Server 2003 (x86)# Veritas Storage Foundation for Windows 5.0 Veritas Storage Foundation for Windows 5.
Table 3-8 Disk Space Requirements for a Host Folder Disk capacity requirements HDLM-installation-folder • When you use only the HDLM Core components: 10 MB + p MB#1 + q MB#2 + 1 MB • When you install but do not use the HDLM GUI: 150 MB + p MB#1 + q MB#2 + 1 MB • When you install and use the HDLM GUI: 150 MB + 20 MB + p MB#1 + q MB#2 + 1 MB #1 This size depends on the log files settings. The maximum size is 30000MB.
Figure 3-1 Flow of HDLM Environment Setup HDLM Installation Types This section describes the following types of HDLM installations: new installation, upgrade installation, migration, and re-installation. New installation of HDLM: Installing HDLM on a server, which HDLM has never been installed on, is called a new installation of HDLM. Upgrade installation of HDLM: Installing a newer version of HDLM over the existing version without removing the existing version is called an upgrade installation of HDLM.
Notes on Creating an HDLM Environment This section provides notes on creating an HDLM environment. For details about operating HDLM, see Notes on Using HDLM on page 4-2. Notes on HBAs and HBA Drivers • If you are using the Storport Miniport driver as an HBA driver in Windows Server 2003, install QFE 838894 or later for the Microsoft Storport driver or install Windows Server 2003 SP1 or later, before installing HDLM. • If you are using multiple HBAs, make sure that the models of the HBAs are the same.
- Trace files after migration: drive-for-program-installation:\Program Files\HITACHI \DynamicLinkManager\log\hdlmtrn.log (n indicates a file number) The underlined part indicates the folder specified during installation. ¢ When you migrate from HDLM versions 04-01 to 5.5 to HDLM version 5.6 or later, or when you perform an upgrade installation from HDLM 5.5 or later - Trace files before migration or upgrade: drive-for-program-installation:\Program Files#\HITACHI\HNTRLib \spool\hntrn.
Notes on Windows • We recommend that you install Windows and HDLM on an internal host disk. If you install them on an HDLM management-target disk, the following problems might occur: ¢ ¢ You might not be able to store the OS crash-dump and error information on the disk. After removing HDLM, some files might not be deleted correctly. • When restoring a Windows system disk from a backup, restore the disk to a single-path configuration.
how to obtain and use the hotfix and how it will affect the system, contact Microsoft. • HDLM uses the Windows Installer service. Therefore, when you install HDLM, take the following precautions: a. In the Startup Type setting for the Windows Installer service, specify Manual or Automatic. b. Before installing HDLM, make sure that no other programs are using the Windows Installer service.
• In Windows Server 2003 (excluding x86 versions) , Windows Server 2008 (excluding x86 versions) and Windows Server 2012, we recommend that you install HDLM in a folder other than Program Files. • When installing HDLM, the name of the HDLM installation folder and the names of all its parent folders must satisfy all of the following conditions: ¢ ¢ ¢ The name must not be a reserved name specified in Windows. Reserved names include names like CON, AUX, COM1 to COM9, LPT1 to LPT9, PRN, and NUL.
• If you are using Hyper-V in Windows Server 2008, you cannot use HDLM on a guest OS. Install HDLM on a host OS. If you want to install or remove HDLM on a host OS, first terminate the Hyper-V manager console. If the Hyper-V manager console is running, the installation or removal of HDLM will stop. If this happens, you can continue with the installation or removal of HDLM by first terminating the Hyper-V manager console.
Windows-installation-folder\inf. In addition, two other oemn.pnf files will also be created in this folder. If either the KAPL09257-W or the KAPL09258-E message appears, perform the following procedure to delete the two oemn.inf files and two oemn.pnf files: a. Check the MPIO driver version indicated in the KAPL09257-W or the KAPL09258-E message. In this example, the MPIO driver version is n.nn.nnnn.nnnn (n represents numbers): KAPL09257-W HDLM cannot be installed on a system where MPIO n.nn.nnnn.
current value to a value equal to or greater than the value you have determined.
For details on how to change MISSCOUNT and DISKTIMEOUT, contact the company with which you have an Oracle Support Services contract. Note that when you remove HDLM from the above configuration, you must reset the values of MISSCOUNT and DISKTIMEOUT to their original values. Therefore, make a note of the original values of MISSCOUNT and DISKTIMEOUT before changing them. • Configurations in which Oracle RAC is installed in Oracle Cluster File System are not supported.
(5 x number-of-connected paths) seconds • If installation of HDLM terminates abnormally and the KAPL09016-E message is output, check whether an HDLM version from another OS has been installed on the same drive. ¢ ¢ When an HDLM version from another OS has been installed: Remove the version of HDLM that is already installed, and then rerun the installation program. When HDLM for another OS has not been installed: Perform the installation again by following the procedure below: a.
this happens, execute the dlnkmgr command's online operation to change the path status to Online. Notes on Migration or Upgrade Installation If either of the following conditions is met, the disk numbers managed by Windows might be changed from the state they were in prior to a migration installation or upgrade installation: • The disk numbers managed by Windows are non-consecutive and an HDLM version earlier than 5.4 is migrated to 5.
Preparations for a New Installation of HDLM The following explains what you need to do before performing a new installation of HDLM. For an FC connection, check the topology (Fabric, AL, etc.) and perform an appropriate setup. To prepare for an HDLM installation: 1. Use a single cable to connect the host to the storage system. Using multiple paths to connect a host to a storage system before installing HDLM might result in unstable Windows operations.
6. Install Windows, and any non-HDLM drivers. Install Windows and any non-HDLM drivers by following the documentation for each of the products. 7. Set up the HBAs. See the HBA documentation and manual to complete the required setup. 8. If your configuration uses an IP-SAN, install and set up the iSCSI initiator (iSCSI software or HBA). For details, see the iSCSI initiator documentation, the documentation for the HBA, or the storage system documentation. 9. Prepare the LUs.
How to Create an Installation-Information Settings File For an installation-information settings file, you need to define the license key file name, installation destination folder, and then any other information that is required for the particular installation. HDLM provides a sample file in order to simplify the editing process of an installation-information settings file. The sample file is located on the supplied DVD. To edit the installation-information settings file: 1.
Performing a New Installation of HDLM on Windows Server 2003 In a Non-Cluster Environment Before installing HDLM, have a license key ready. If you want to perform an unattended installation, also be sure to prepare an installation-information settings file. To install HDLM on a host that does not currently have HDLM installed on it: 1. Log on to Windows as a member of the Administrators group. 2. Save the license key file directly under the Windows installationdestination drive.
If you have specified y for the restart key in the installationinformation settings file, go to step 16. 4. The program checks the MPIO driver version, and then installs the MPIO driver. If a message appears, asking you whether you want to install the MPIO driver, make sure that no multi-path management software other than HDLM is installed. ¢ ¢ 5.
HDLM installation. After that, 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.
Leave the host in a single-path configuration until you check (in step 21) whether HDLM has been successfully installed. 14. Modify the storage system settings. Modify the storage system settings by following the procedure described in the maintenance documentation for that particular storage system. 15. Start the host. 16. Log on to Windows again as a member of the Administrators group. 17. Check the log file and PRSV key. This step is unnecessary if you have performed step 12. In this case, go to step 18.
Alive x.x.x-xx yyyy/mm/dd hh:mm:ss 128 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 PROMPT> 19. Use the results of the view operation to check the version of the installed HDLM. If x.x.x-xx is displayed in HDLM Version, the correct version of HDLM has been installed. 20.
Installing MSCS after an HDLM Installation To install HDLM, and then MSCS: 1. Shut down all the hosts. 2. Make sure that all the hosts that make up the cluster system have been fully shut down. 3. Restart each host. Restart them all in the single path configuration. 4. Log on to Windows as a member of the Administrators group. 5. Save the license key file directly under the Windows installationdestination drive.
7. The program checks the MPIO driver version, and then installs the MPIO driver. If a message appears asking you whether you want to install the MPIO driver, make sure that no multi-path management software other than HDLM is installed. ¢ ¢ 8. If no multi-path management software other than HDLM is installed, click the Next button to continue the installation. follow the procedure below: ¢ ¢ 9.
the HDLM management-target device, select EMC Symmetrix DMX Series, CLARiiON CX Series. To select an HP EVA series LU as the HDLM management-target device, select HP StorageWorks EVA Series. 14. Follow the instructions shown in the messages that appear in the window. ¢ ¢ ¢ ¢ If a dialog box with the following text appears during installation, and the Storport Miniport driver is being used as the HBA driver, stop the HDLM installation.
utility, see The dlmprsvkey Utility for Registering an HDLM Persistent Reservation Key on page 7-12. If you used a license key file, it will be deleted after the installation finishes. The KAPL09115-W message will appear if deletion of this file fails. If this happens, delete the file manually. 17. Shut down the host. Leave the host in a single-path configuration until you check (in step 24) whether HDLM has been successfully installed. 18.
If HDLM Manager, HDLM Alert Driver, and HDLM Driver are all Alive, all the programs are running correctly. 25. After the installation finishes, check the path information as described in Checking the Path Configuration on page 3-69, and make sure that you have successfully installed HDLM in a single-path configuration. 26. Connect cables to all the HBAs to change the configuration to a multi-path configuration. 27.
Installing HDLM after an MSCS Installation To install MSCS, and then HDLM on a host that does not currently have HDLM on it: 1. Install MSCS on the host. 2. Restart the host. 3. Log on to Windows as a member of the Administrators group. 4. Save the license key file directly under the Windows installationdestination drive. Also, instead of using the license key file, you can directly specify the license key during the installation of HDLM.
MPIO driver, make sure that no multi-path management software other than HDLM is installed. ¢ ¢ 7. If multi-path management software other than HDLM is installed, click the Cancel button to cancel the installation, remove the multi-path management software, and then install HDLM. If no multi-path management software other than HDLM is installed, click the Next button to continue the installation.
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 will be registered before the installation finishes. If the KAPL09131-W message appears, follow the procedure described in step 14.
17. Confirm that all the hosts that make up the cluster system have been fully shut down. 18. Modify the storage system settings. Modify the storage system settings by following the procedure described in the maintenance documentation for that particular storage system. 19. Restart each host. 20. Log on to Windows again as a member of the Administrators group. 21. Make sure that the program is running properly, by examining the results of the dlnkmgr command's view operation.
25. Connect cables to all the HBAs to change the configuration to a multi-path configuration. 26. Check the path information as described in Checking the Path Configuration on page 3-69 to make sure that you have successfully assembled a multi-path configuration. When VCS Is Used To install HDLM when VCS is used: 1. Start each host. Start them in a single-path configuration. 2. Use the VCS Configuration Wizard to configure the Cluster components. 3. Restart the hosts. 4.
This command checks whether HDLM has already been installed. If HDLM 5.4 or earlier has been installed, the KAPL09129-E message will appear. If this happens, carry out the procedure shown in Migrating from HDLM 5.4 or Earlier to HDLM 5.5 or Later on page 3-65. If HDLM 5.5 or later has been installed, the KAPL09183-E message will appear, and then the upgrade installation or re-installation will be performed. After the installation is complete, go to step 15. 8.
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.
Leave the host in a single-path configuration until you check (in step 24) whether HDLM has been successfully installed. 18. Modify the storage system settings. Modify the storage system settings by following the procedure described in the maintenance documentation for that particular storage system. 19. Restart each host. 20. Log on to Windows again as a member of the Administrators group. 21. Make sure that the program is running properly, by examining the results of the dlnkmgr command's view operation.
24. After the installation finishes, check the path information as described in Checking the Path Configuration on page 3-69, and make sure that you have successfully installed HDLM in a single-path configuration. 25. Connect cables to all the HBAs to change the configuration to a multi-path configuration. 26. Check the path information as described in Checking the Path Configuration on page 3-69 to make sure that you have successfully assembled a multi-path configuration.
Specify n 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 will appear. If this happens, carry out the procedure shown in Migrating from HDLM 5.4 or Earlier to HDLM 5.5 or Later on page 3-65. If HDLM 5.5 or later has been installed, the KAPL09183-E message will appear, and then the upgrade installation or re-installation will be performed.
¢ ¢ ¢ ¢ If a dialog box with the following text appears during installation, and the Storport Miniport driver is being used as the HBA driver, stop the HDLM installation. After that, 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.
16. Shut down the host. Leave the host in a single-path configuration until you check (in step 24) whether HDLM has been successfully installed. 17. On all the hosts that make up the cluster system, perform steps 3 to 16. 18. Make sure that all the hosts that make up the cluster system have been completely shut down. 19. Restart each host. 20. Log on to Windows again as a member of the Administrators group. 21.
25. Connect cables to all the HBAs to change the configuration to a multi-path configuration. 26. Check the path information as described in Checking the Path Configuration on page 3-69 to make sure that you have successfully assembled a multi-path configuration. 27. Shut down the host. 28. On all the hosts that make up the cluster system, perform steps 19 to 27. 29. Install and configure Oracle RAC.
Performing a New Installation of HDLM on Windows Server 2008 and Windows Server 2012 Note: If you are running a Server Core environment in Windows Server 2008 or Windows Server 2012, perform an unattended installation to install HDLM. In a Non-Cluster Environment Before installing HDLM, have a license key ready. If you want to perform an unattended installation, also be sure to prepare an installation-information settings file. To install HDLM in a non-cluster environment: 1.
4. Specify a license key file or enter the license key by following the instructions shown in the messages that appear in the window. ¢ If a license key file was saved in step 2, specify that license key file. ¢ If a license key file is not being used, specify the license key directly. 5. Specify the installation folder by following the instructions shown in the messages that appear in the window.
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 unregistered, HDLM functions might not properly operate. For details about the dlmprsvkey utility, see The dlmprsvkey Utility for Registering an HDLM Persistent Reservation Key on page 7-12. If you used a license key file, it will be deleted after the installation finishes. The KAPL09115-W message will appear if deletion of this file fails.
20. 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: PROMPT>dlnkmgr view -sys HDLM Version : x.x.
Figure 3-4 Single Path Configuration and Multi-path Configuration 25. Check the path information as described in Checking the Path Configuration on page 3-69 to make sure that you have successfully assembled a multi-path configuration. When MSCS Is Used The following provides explanations of how to install MSCS before and after an HDLM installation. Installing MSCS after an HDLM installation To install HDLM and then MSCS: 1. Shut down all the hosts. 2.
The program checks whether HDLM has already been installed. If the KAPL09173-W message appears, perform the procedure shown in Upgrade Installation or Re-installation of HDLM on page 3-64. If a message does not appear, go to the next step. ¢ If you are performing an unattended installation, execute the installhdlm utility.
Windows firewall is enabled on that host, execute the firewall_setup command to allow a firewall exception. If Global Link Manager will not be used to manage HDLM, you do not need to take any action. To manage HDLM with Global Link Manager, register Firewall exceptions. For details, see Firewall Settings for Managing HDLM by Using Global Link Manager on page 3-67. 11. Check the results of the installation.
23. 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: PROMPT>dlnkmgr view -sys HDLM Version : x.x.
32. Install MSCS on each host. 33. Shut down all the hosts. 34. Restart each host again. 35. Log on to Windows as a member of the Administrators group. 36. Execute the dlnkmgr command's view operation to display the status of each program. Make sure that on MSCS is displayed in Support Cluster. An example of executing the dlnkmgr command's view operation is as follows: PROMPT>dlnkmgr view -sys HDLM Version : x.x.
¢ If you are not performing an unattended installation, insert the DVD into the drive. In the displayed window, click the Install button next to for Windows of Hitachi Dynamic Link Manager Software. If no window is displayed, manually run the installer (setup.exe). The program checks whether HDLM has already been installed. If the KAPL09173-W message will appear, perform the procedure shown in Upgrade Installation or Re-installation of HDLM on page 3-64. If a message does not appear, go to the next step.
¢ In the last installation window, the following message might be output: When you manage a host by using Global Link Manager and Windows firewall is enabled on that host, execute the firewall_setup command to allow a firewall exception. If Global Link Manager will not be used to manage HDLM, you do not need to take any action. To manage HDLM with Global Link Manager, register Firewall exceptions. For details, see Firewall Settings for Managing HDLM by Using Global Link Manager on page 3-67. 10.
19. Make sure that all the hosts that make up the cluster system have completely shut down. 20. Modify the storage system settings. Modify the storage system settings by following the procedure described in the maintenance documentation for that particular storage system. 21. Restart each host. 22. Log on to Windows again as a member of the Administrators group. 23. Execute the dlnkmgr command's view operation to display the status of each program. Make sure that on MSCS is displayed in Support Cluster.
27. Connect cables to all the HBAs to change the configuration to a multi-path configuration. 28. Check the path information as described in Checking the Path Configuration on page 3-69 to make sure that you have successfully assembled a multi-path configuration. Upgrade Installation or Re-installation of HDLM You can perform an upgrade installation for only HDLM 5.5 or later. To migrate HDLM 5.4 or earlier to version 5.5 or later, see Migrating from HDLM 5.4 or Earlier to HDLM 5.5 or Later on page 3-65.
you select EMC Symmetrix DMX Series, CLARiiON CX Series when you installed HDLM for the first time, EMC Symmetrix DMX Series, CLARiiON CX Series will already be selected when it appears in the dialog box. Note: If you want to install all HDLM components on a host on which the HDLM Core components have been installed, use an unattended installation.
4. Perform a new HDLM installation by following the procedure in Installing HDLM on page 3-25. 5. Copy the files copied in step 1 to the following location, and then overwrite the existing files: \HDLM-installation-folder\config\dlmmgr.xml \HDLM-installation-folder\config\dlmwebagent.properties 6. Delete the files copied in step 1. 7. Restart the host. Note: When you install HDLM 5.5 or later in an environment where HDLM 5.
Do not install the JRE directly into HDLM-installation-folder\jre_user. If you do this, remove the JRE, and then reinstall it into another folder. When you install JRE 6.0_04, the C:\Program Files\Java\jre1.6.0_04. folder is created by default. 3. Copy all the configuration files, including the JRE installation folder, into the following folder: HDLM-installation-folder\jre_user If you use JRE 6.0_04, the folder configuration is as follows: HDLM-installation-folder\jre_user \jre1.6.
• Port set for the server.http.localPort property (default: 24043/tcp) For details about the ports used by the Hitachi Command Suite Common Agent Component, see the manual Hitachi Command Suite Global Link Manager Installation and Configuration Guide. To add the ports to the exceptions list: 1. Log on as a member of the Administrators group. 2. Execute the firewall_setup command. 3. Check the displayed message to make sure that the command was executed successfully. The command ended successfully.
Item Details • Port set for the server.http.localPort property (default: 24043/tcp) This operation requires Administrators group privileges. If the OS is Windows Server 2008 or Windows Server 2012, the command must be executed from a command prompt started as an Administrator. Options -set Adds firewall exceptions. -unset Removes firewall exceptions.
and the HBA port (the host port number and bus number displayed in the PathName column) is different. The number to the left of PathName is the host port number. The numbers displayed between the period to the right of the host port number and the following period is the bus number. ¢ Make sure that there are different host port numbers and bus numbers for each physical HBA port. If the system cannot be configured in a multi-path configuration, perform the following operations: 1.
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) Remove LU : off Intermittent Error Monitor : off Dynamic I/O Path Control : off(10) KAPL01001-I The HDLM command completed normally.
Function Default value Recommended value The recommended checking interval depends on the operating environment.
dlnkmgr set -lb on -lbtype exlio When load balancing is enabled by specifying on for the -lb parameter, specify one of the following algorithm values after the -lbtype parameter: ¢ rr for the Round Robin algorithm ¢ exrr for the Extended Round Robin algorithm ¢ lio for the Least I/Os algorithm ¢ exlio for the Extended Least I/Os algorithm ¢ lbk for the Least Blocks algorithm ¢ exlbk for the Extended Least Blocks algorithm The type of algorithm specified by the -lbtype parameter remains stored i
If this happens, change any of the following settings: the checking interval for automatic failbacks, the intermittent error-monitoring interval, or the number of times that the error needs to occur. If you set the number of times that the error needs to occur to 1, the above condition does not need to be satisfied.
on specifies that intermittent error monitoring is to be used. To disable intermittent error monitoring, specify off. When you set this parameter to on, you can specify intermittent error conditions by using the -intvl and -iemnum parameters. Specify the monitoring interval for an intermittent error in the -intvl parameter, and the number of times that the error needs to occur in the -iemnum parameter. When these parameters are omitted, the default values of 30 and 3 are used, respectively.
Values in the set operation Description included in the disconnected paths, the LU is not deleted from HDLM-management. The deleted LU is restored when it is recovered from the physical failure and the disk is re-scanned. on -force The LU is removed from HDLM-management when all the paths to the LU are disconnected, even when an Offline(C) path is included. The removed LU is restored after it is recovered from the physical failure and the disk is re-scanned.
The higher this value is set, the more information that will be output. As the amount of log information to be output increases, it will take less time to overwrite the old error log information with the new information. • Setting up the error log collection level by using the set operation The following is an example of setting up the error log collection level by using a command: dlnkmgr set -ellv 2 Specify the error log collection level as a number.
Setting the Error Log File Size There are two error logs: the HDLM manager log file dlmmgrn.log (n indicates a file number from 1 to 16) and the HDLM GUI log file dlmguin.log (n indicates a file number of 1 or 2). You can specify a value (in kilobytes) from 100 to 2000000 for the error log file size. For HDLM GUI logs, file sizes range from 100 to 9900. If you specify a value over 9901, 9900 will be used. For HDLM manager logs, the specified value will be applied as it is without being limited by the above.
W message will be displayed to confirm the execution, and the trace file will be temporarily deleted. When all the trace files become full, the oldest file is overwritten with any new trace data. By specifying both the trace file size and the number of trace files, you can collect up to 1024000KB of trace data.
Value (severity) Explanation 3 4 Error-level and Warning-level audit log data is collected. 5 6 Error-level, Warning-level, and Information-level audit log data is collected. 7 The table below lists and describes the values for the audit log category setting. The default is all. Table 3-19 Values Indicating Audit Log Data Categories Value Explanation ss Audit log events of the StartStop category are collected. c Audit log events of the Authentication category are collected.
Number Of Trace Files : 10 Path Health Checking : on(10) Auto Failback : on(10) Remove LU : on Intermittent Error Monitor : on(2/20) Dynamic I/O Path Control : off(10) KAPL01001-I The HDLM command completed normally.
Setting Recommended value Default value Number of integrated trace files 4 8 Buffer size per monitoring interval Monitoring cycle 10 (seconds) 5 (seconds) Buffer size per monitoring interval 64 (KB) 256 (KB) Number of messages to be output per monitoring interval Monitoring cycle 0 (seconds) 0 (seconds) Number of messages to be output 0 0 If Hitachi Network Objectplaza Trace Library (HNTRLib2) is already installed, the existing settings will be inherited.
Figure 3-5 Hitachi Network Objectplaza Trace Utility 2 Release 2.0 Dialog Box. 2. In Number of Files, change the number of integrated trace files. The default is 4. You can specify a value from 1 to 16. The value you specify here will apply to n in program-installationdestination-drive:\Program Files\HITACHI\HNTRLib2\spool \Hntr2n.log (n indicates a file number). 3. In File Size(KB), change the size of an integrated trace file. The default is 256 (kilobytes). You can specify a value from 8 to 8192.
The default is 0. You can specify a value from 0 to 500. If you specify 0, you cannot adjust the number of messages to be output. If you specify 0 for Lookout Span(Sec), you cannot adjust the number of messages to be output because the system ignores the Max Messages / Span setting. 8. After you finish changing the settings, click the OK button. The dialog box closes. 9. Close all of the Hitachi program products that are using Hitachi Network Objectplaza Trace Library, or restart the host.
# To remove HDLM, you must reconfigure the system to a single-path configuration. The time for doing this does not affect the time required for an removal. Since the removal time depends on the value of the maximum number of paths that can be configured in your environment, use this value for an approximate calculation. • Before removing HDLM 5.5 or later, make sure that no other application is using an HDLM management-target LU.
Removing HDLM After HDLM is removed, sometimes the files below will not be deleted. The following files will be deleted when you restart the host: HDLM-installation-folder\DLMTools\perfhdlm\provhdlm.dll HDLM-installation-folder\lib\libdlm.dll HDLM-installation-folder\lib\hdlmhcc60.dll The default installation folder for HDLM is Windows-installation-drive: \Program Files#\HITACHI\DynamicLinkManager.
In Windows Server 2008, if you have selected an EMC CX series LU as the HDLM management-target device, perform the following steps to unregister it. Otherwise, go to step 7. 4. From Control Panel, choose MPIO. The MPIO Properties dialog box opens. 5. On the MPIO-ed Devices page, select Device Hardware ID DGC RAID, and then click the Delete button. 6. Click the OK button to close the MPIO Properties dialog box. 7. Start the removal program.
Removal Procedures - MSCS or VCS Environment To remove HDLM: 1. Log on to Windows. Log on as a member of the Administrators group. 2. Stop all the processes and services that use the HDLM managementtarget paths. Stop any processes or application services, such as a DBMS, that are using the HDLM management-target paths. 3. Stop MSCS or VCS on all the hosts that make up the cluster. When MSCS is used, follow the procedure described below. Choose Administrative Tools and then Services.
6. On the MPIO-ed Devices page, select Device Hardware ID DGC RAID, and then click the Delete button. 7. Click the OK button to close the MPIO Properties dialog box. 8. Start the removal program. In Windows Server 2003: From Control Panel, choose Add or Remove Programs, and then Change or Remove Programs. From the list of programs, select Dynamic Link Manager, and click the Change/Remove button. In Windows Server 2008 (excluding Windows Server 2008 R2): From Control Panel, choose Programs and Features.
2. Stop the Oracle RAC instance of the host where HDLM is to be removed. 3. If a host and a storage system are connected via multiple paths, reconfigure it so that only one path connects the host to the storage system. Removing HDLM in a multi-path configuration, might cause the disk contents to become corrupted when the host restarts. Make sure that you remove HDLM in a single path configuration only.
Removing Hitachi Network Objectplaza Trace Library (HNTRLib2) When you remove HDLM, if the KAPL09019-E or KAPL09020-E message is output, follow the directions below to remove HNTRLib2: 1. Log on to Windows as a member of the Administrators group. If the KAPL09019-E message appears during the removal of HDLM, go to step 2. If the KAPL09020-E message appears during the removal of HDLM, go to step 3. 2.
undeleted, other applications will not be affected. To delete this file, perform the following procedure: a. Start the registry editor (regedit.exe) and check that the following registry key does not exist: HKEY_LOCAL_MACHINE\SOFTWARE\HITACHI\COMMON_DLL\HNTRLIB2 If this key exists, it means another application is using the hntr2t.dll file. If this is the case, do not delete the hntr2t.dll file. b.
4 HDLM Operation This chapter describes the operating procedures for HDLM, including how to operate HDLM and the HDLM manager, and how to change the configuration of the operating environment.
Notes on Using HDLM This section contains notes that are important for running HDLM operations. Using a Storage Management Program You must not change the vendor ID and product ID of a storage system. If you change these IDs, HDLM will not be able to recognize the storage system. Upgrading Windows Always remove HDLM before upgrading or re-installing Windows, or before installing a Windows Server 2003 service pack.
EMC DMX series and EMC CX series: HDLM 5.7 or later HP EVA series: HDLM 5.9.1 or later ¢ If the OS is Windows Server 2008: EMC CX series: HDLM 6.4 or later • You can display and use the HDLM GUI windows for the Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP series, Hitachi AMS2000/AMS/WMS/SMS series, Universal Storage Platform V/VM series, and Virtual Storage Platform series.
If you attempt to perform an HDLM operation by any other method, a dialog box will appear, requesting confirmation that you have administrator permissions. HDLM Operations Using the HDLM GUI This chapter explains the procedures for operating the HDLM GUI window components. For details on the components of each window, see the HDLM GUI Help. Notes on Using the HDLM GUI This subsection provides notes on using the HDLM GUI window. Be sure to read this section.
¢ Execute the HDLM command using the Administrator account. To execute an HDLM command with a non-administrator account, use the Administrator: Command Prompt window. If you attempt to execute an HDLM command by any other method, you might be asked whether you have administrator permissions. ¢ • To specify a parameter value containing one or more spaces, enclose the entire value in double quotation marks (").
Changing the Status of Paths to Online To change the status of paths to online: 1. Check the current status of the paths. To place paths online by specifying an HBA port, CHA port, single path, or HBA port WWN, check the path name or PATH_ID used to manage the path. The following example shows how to execute the command: dlnkmgr view -path 2. To change the status of paths to online, execute the dlnkmgr command's online operation.
The paths to be placed offline can be specified by using an HBA port, CHA port, single path, or HBA port WWN. For details on how to specify paths, see offline (Places Paths Offline) on page 6-6. For example, if you want to place all the paths that pass through a specific HBA port offline, execute the dlnkmgr command's offline operation with the -hba parameter specified. The following shows an example of executing this command: PROMPT>dlnkmgr offline -hba 1.
000009 Online KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss PROMPT> For details on the displayed items and their descriptions, see view (Displays Information) on page 6-32. Initializing Statistical Information for Paths This section explains how to initialize statistical information (I/O counts and I/ O errors) for all the paths managed by HDLM.
The following shows an example in which the command is executed: PROMPT>dlnkmgr view -sys -sfunc HDLM Version : x.x.
• The number of trace files • Number of times the same path can be used for load balancing • Number of times the same path can be used for extended load balancing For details on how to set up each function, see set (Sets Up the Operating Environment) on page 6-16. For example, to set up the error log collection level, execute the dlnkmgr command's set operation with the -ellv parameter specified. When the confirmation message is displayed, enter y to execute, or n to cancel the command.
When you are executing the dlnkmgr command's set operation with the lic parameter to install the license, you can only execute it once at a time. If you attempt to execute more than one dlnkmgr command containing the set operation with the -lic parameter, the following message might appear and HDLM might terminate abnormally: KAPL01075-E A fatal error occurred in HDLM. The system environment is invalid.
PROMPT> The value displayed in HDLM version indicates the HDLM version. Viewing HDLM Component Information This section explains how to display HDLM component information. To display HDLM component information, execute the dlnkmgr command's view operation with the -sys parameter specified. The following shows an example in which the command is executed: PROMPT>dlnkmgr view -sys HDLM Version : x.x.
Using the Windows Administrative Tool (Performance) to Check Path Information The HDLM Performance Monitor uses the Windows administrative tool Performance to display path information. Note: ¢ ¢ The function for checking path information using the Windows administrative tool is not supported in a non-x86 edition of Windows Server 2003, Windows Server 2008, or Windows Server 2012. If an error occurs in the HDLM performance monitor, performance information is not collected after the error.
Counter name Description Disk Read Bytes/ Sec The amount of data transferred per second from the disk during read operations. Disk Write Bytes/ Sec The amount of data transferred per second to the disk during write operations. Table 4-2 Selectable Items for Instances Selectable items# Description _Total Selecting this item displays the total value of each instance. pathid disk-number drive-letter Selecting this item displays the instance of the selected path.
Starting the HDLM Manager During installation, the HDLM manager is registered as a Windows service and the startup type is set to Automatic. This means that when Windows starts, the HDLM manager will also start automatically. If, for some reason, the HDLM manager does not automatically start, do the following: Log on to Windows as a member of the Administrators group. From Control Panel, choose Administrative Tools, and then Services.
HDLM Resident Processes The table below lists and describes the resident processes in HDLM. To monitor these processes, use the names below. Table 4-3 HDLM resident processes Process Service Description dlmmgr.exe DLMManager HDLM manager process hbsa_service.exe HBsA Service Hitachi Command Suite Common Agent Component# process hntr2mon.exe Hitachi Network Objectplaza Trace Monitor 2 Hitachi Network Objectplaza Trace Library (HNTRLib2) process hntr2srv.
3. If the LU is not displayed in the Disk Management window, perform the following operations to add the LU as an HDLM management-target. ¢ ¢ 4. From the Device Manager window of Windows, select Disk drives, and then click Scan for hardware changes. From the Disk Management window of Windows, click Rescan Disks. Use the dlnkmgr view -path command or the HDLM GUI to confirm that the PathID has been added. The figure below shows an example of how to use the command to confirm that an LU has been added.
When you create a partition, assign the same drive letter as the one assigned for node A in step 3. 6. Stop node B, and then restart node A. 7. On node A, register the new LU in MSCS, and set it up. 8. Restart node B. Checking an Added Path You can add a path, by inserting a cable into an existing LU, even while the host (on which HDLM is installed) is running. When you add a path without adding an LU, what is displayed in the disk management window does not changed.
- KAPL05301-E Note that these messages are output by Windows activities, and not by an error in HDLM. Deleting an LU Dynamically The LU deletion function automatically removes an LU from HDLM management when all the paths to that particular LU are disconnected. You can set up the LU deletion function by specifying the dlnkmgr command's set operation together with the -rmlu on parameter. You can also set up this function in the Options window of the HDLM GUI.
When an LU is deleted from the HDLM management target by using the LU deletion function, the KAPL08022-E message might not be output to the event log. In this case, refer to the KAPL05301-E message to check the path information. The figure below shows an example display of the KAPL05301-E message. Figure 4-3 An example display of the KAPL05301-E message In the event viewer, deleted path information is displayed in the following format: PathID PathName DskName iLU ChaPort.
The following table shows the items and descriptions for the path information, which are displayed in the KAPL05301-E message. Table 4-4 Items and Descriptions for the Path Information Displayed in the KAPL05301-E Message Item Description PathID An AutoPATH_ID. Host port number Elements of a PathName.
4-22 HDLM Operation Hitachi Dynamic Link Manager User Guide for Windows®
5 Troubleshooting This chapter describes how to properly use HDLM error information, and then how to resolve the problem, if an error occurs in HDLM. The resolutions for path errors, HDLM program errors, and other types of errors are all described separately. This chapter describes how to use the HDLM commands to use HDLM error information and utilize various workarounds. For details about how to use the HDLM GUI, see the Hitachi Dynamic Link Manager Software GUI Help.
Information Collected by the DLMgetras Utility for Collecting HDLM Error Information Immediately after an error occurs, execute the DLMgetras utility for collecting HDLM error information, since restarting the machine might delete error information before the information is collected by DLMgetras. For details about the DLMgetras utility and the error information it collects, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2.
output to the event log. If this happens, refer to the KAPL05301-E message to check the path information. The message elements are explained below: For details about the KAPL05301-E message, see When an LU or path is automatically deleted due to all the paths being disconnected in Checking that the LU or Path Has Been Dynamically Deleted on page 4-19 in Deleting an LU Dynamically on page 4-19. ErrorCode The error number generated when Windows detects a path error.
The name of the host device. A drive letter is used. If no drive letter has been assigned, a hyphen (-) will be displayed. This is the same as the HDevName that is displayed by the view operation. For details on the view operation, see view (Displays Information) on page 6-32. What To Do for a Path Error When a path error is detected by HDLM, you must immediately resolve the error and restore the path.
Figure 5-2 Troubleshooting Procedure When a Path Error Occurs The following shows the procedure for using the HDLM command (dlnkmgr) to handle a path error. Examining the Messages Examine the messages that are output to the host event log. If the KAPL08022-E message is output, view the message to check the path in which the error has occurred. For details on each item displayed in messages, see Checking Error Information in Messages on page 5-2.
Identifying the Error Path Check the obtained path information to find the path with the error. In the Status column, the error path has the status Offline(E) or Online(E). Narrowing Down the Hardware That Might Have Caused the Error Check the DskName, iLU, ChaPort, and HBAPortWWN columns of the path with the error to narrow down the hardware that may be the cause of the error.
Figure 5-3 Troubleshooting Procedure When a Program Error Occurs The following shows the procedure for handling a program error by using the HDLM command (dlnkmgr). Examining the Messages Examine the messages that are output to the host event log. If an error occurs in an HDLM program, a message other than KAPL08xxx is output to the event log. Examine the content of the message. Messages with error level E (Error) or higher require corrective action.
problem. For details on the view operation, see view (Displays Information) on page 6-32. Execute the following command: Example: dlnkmgr view -sys If the KAPL01012-E message appears as a result of executing the command The following shows the KAPL01012-E message: KAPL01012-E Could not connect the HDLM manager. Operation name = view Start the HDLM manager. For details about how to start the HDLM manager, see Starting the HDLM Manager on page 4-15.
6 Command Reference This chapter describes the HDLM command (dlnkmgr) and its operations.
Overview of the HDLM Command dlnkmgr This section describes how to specify the HDLM command dlnkmgr and its subcommands (called operations in HDLM). Command format Enter the command using the following format: dlnkmgr operation [parameter [parameter-value]] dlnkmgr The command name. operation The type of operation entered after dlnkmgr. parameter A value required for an operation. parameter-value A value required for an operation parameter.
¢ ¢ If you are using Windows Server 2003 , execute HDLM commands as a member of the Administrators group. If you are executing HDLM commands in Windows Server 2008 or Windows Server 2012, see Using Windows Server 2008 or Windows Server 2012 on page 4-3. To specify a value that contains a space in its parameter, enclose the entire value in double quotes (").
PROMPT>dlnkmgr clear -pdst -s KAPL01001-I The HDLM command completed normally. Operation name = clear, completion time = yyyy/mm/dd hh:mm:ss PROMPT> To Display the Format of the clear Operation -help Displays the format of the clear operation. Example PROMPT>dlnkmgr clear -help clear: Format dlnkmgr clear -pdst [-s] KAPL01001-I The HDLM command completed normally.
Examples Example 1 The following example shows how to display all the operations available in the HDLM command. PROMPT>dlnkmgr help dlnkmgr: Format dlnkmgr { clear | help | offline | online | set | view | delete} KAPL01001-I The HDLM command completed normally. Operation name = help, completion time = yyyy/mm/dd hh:mm:ss PROMPT> Example 2 The following example shows how to display the formats of multiple operations.
help: Format dlnkmgr help { clear | offline | online | set | view | delete} KAPL01001-I The HDLM command completed normally. Operation name = help, completion time = yyyy/mm/dd hh:mm:ss PROMPT> offline (Places Paths Offline) The dlnkmgr command's offline operation places online paths offline. Specify the paths to be placed offline by specifying an HBA port, CHA port, single path, or HBA port WWN. There must always be at least one online path accessing each LU.
This parameter is optional because offline is always used for paths, so it is assumed. Make sure that you specify the paths to be taken offline by using the hba, -cha, -pathid, or -hbaportwwn parameter. -hba host-port-number.bus-number Use this parameter to place offline, at one time, all the paths that pass through a specific HBA port. The command will place offline all the paths connected to the HBA port that has the specified host port number and bus number.
AutoPATH_IDs are re-assigned every time the host is restarted. Always make sure that you use the view operation to find the current AutoPATH_ID of the target path, before executing the offline operation. Example The following example shows how to place offline all the paths connected to the channel adapter port 0A.
For details on how to execute the view operation and display the HBA port WWN and path name, see Parameters Used When Displaying Path Information on page 6-42 in Parameters on page 6-34. Example The following shows an example of placing offline the paths for which the HBA port WWN is 10000000C93213BA, target ID is 0000000000000001, and host LU number is 0000 while confirming command operation.
Valid value AutoPATH_ID { 000000 - 999999 }(Decimal) Host_LUN { 0000 - FFFF }(Hexadecimal) KAPL01001-I The HDLM command completed normally. Operation name = offline, completion time = yyyy/mm/dd hh:mm:ss PROMPT> Reference Using the view operation together with Windows commands enables you to filter the path information listed for a specific HBA port or channel adapter port. For details about the view operation, see view (Displays Information) on page 6-32.
online (Places Paths Online) The dlnkmgr command's online operation places offline paths online. To specify the paths to be placed online, specify an HBA port, CHA port, single path, or HBA port WWN. Format To Place Paths Online dlnkmgr online [-path] [-hba host-port-number.
operation. Enter a period between these two parameter values. For details about the view operation, see view (Displays Information) on page 6-32. Leading zeros of each parameter value can be omitted; however, when the host port number or bus number of the target HBA port is 0000, enter 0000 or 0 for the corresponding parameter value. Example The following example shows how to place online all paths connected to an HBA port whose host port number is 0001 and bus number is 0001: PROMPT>dlnkmgr online -hba 1.
Use this parameter to place a single path online. Specify the current AutoPATH_ID of the target path, which is displayed by using the view operation. For details about the view operation, see view (Displays Information) on page 6-32 Leading zeros can be omitted (000001 and 1 indicate the same AutoPATH_ID); however, when the target AutoPATH_ID is 000000, enter 000000 or 0 for the parameter value. AutoPATH_IDs are re-assigned every time the host is restarted.
of all the paths in the Online(S) and Online(D) statuses, specify only hapath. -dfha Use this parameter to change the paths to the primary volume (P-VOL) in an HAM environment to Online(D). The Online(S) status changes to the Online(D) status. When you do not specify this parameter, the status of the P-VOL paths in the HAM environment will be changed to the Online(S) status.
dlnkmgr online [-path] -cha -pathid AutoPATH_ID [-s] dlnkmgr online [-path] [-pathid AutoPATH_ID] [-s] dlnkmgr online [-path] [-hbaportwwn HBA_Port_WWN [-tid Target_ID -hlun Host_LUN]] [-s] dlnkmgr online [-path] -hapath [-lu -pathid AutoPATH_ID] [-s] s] dlnkmgr online [-path] -dfha [-lu -pathid AutoPATH_ID] [- Valid value AutoPATH_ID { 000000 - 999999 }(Decimal) Host_LUN { 0000 - FFFF }(Hexadecimal) KAPL01001-I The HDLM command completed normally.
status of, has been deleted, and then resolve the path error. For details, see Deleting an LU Dynamically on page 4-19. set (Sets Up the Operating Environment) The dlnkmgr command's set operation sets the HDLM operating environment.
Table 6-2 Default and Recommended Values Item name Default value Load balancing Recommended value on on The Extended Least I/Os algorithm is used. The recommended algorithm depends on the operating environment. 3 3 Collect error information for the Information level and higher. Collect error information for the Information level and higher. Error log file size 9900 (KB) 9900 (KB) Number of error log files 2 2 Trace level 0 0 Do not output any trace. Do not output any trace.
This item is applied only when Hitachi AMS2000 series, Hitachi SMS series, or HUS100 series storage is used. -lb {on [-lbtype {rr|exrr|lio|exlio|lbk|exlbk}]|off} Enables or disables load balancing.
you may have to set the error log collection level to 1 or higher to collect log information. Table 6-3 Values of the Error Log Collection Level Value Description 0 Collects no error log. 1 Collects error information for the Error or higher level. 2 Collects error information for the Warning or higher level. 3 Collects error information for the Information or higher level. 4 Collects error information for the Information or higher level (including maintenance information).
(dlmguin.log (n indicates a file number of 1 or 2)), the number of log files is set at 2. -systflv trace-level Specify the trace output level. The trace files for which trace levels can be set are hdlmtrn.log (n indicates a file number from 1 to 64). Table 6-4 Trace Level Values on page 6-20 shows the values of the trace level. The default is 0. If an error occurs, set the trace level to 1 or higher to collect the log information.
The trace files for which the number of files can be set are hdlmtrn.log (n indicates a file number from 1 to 64). -pchk {on [-intvl checking-interval]|off} Enables or disables path health checking. on: Enabled off: Disabled Path health checking checks all online paths. For a standby host, or a host connected to the Thunder 9500V series, or Hitachi AMS/WMS series storage system, we recommend that you activate path health checking so that you can detect errors in paths where I/Os operations do not occur.
Automatic failbacks are performed on the following types of paths: ¢ Paths where an error occurred and for which the KAPL08022-E message was displayed. Path where an error occurred during the startup of the HDLM manager. To prevent intermittent errors from deteriorating I/O performance, we recommend that you also enable intermittent error monitoring when the automatic failback function is enabled. Intermittent error monitoring is specifiable only when automatic failbacks are enabled.
This setting remains stored in the system, even if you disable the function by changing the setting of automatic failbacks to off. Therefore, if you re-enable automatic failbacks and do not change the interval, path status checks will be executed at the interval already stored in the system.
If this condition is not satisfied, the KAPL01080-W message will be output and an error will occur. If this happens, change any of the following settings: the checking interval for automatic failback, intermittent error monitoring interval, or the number of times that the error is to occur. When you set the number of times that the error is to occur to 1, the above condition does not need to be satisfied.
without specifying the number of times, the error monitoring will be executed using the value stored in the system. When the set -iem on operation is executed during error monitoring, even if you do not change the conditions for intermittent error monitoring, the number of errors and the time that has passed since the error monitoring has started are reset to 0. Intermittent error monitoring will then resume with the changed settings.
Setting AFB IEM Available operation Set IEM to off. off off on#2 off Result of operation • When a path is not being monitored, the IEM settings will take effect again when the path is recovered from the error status by performing an automatic failback. • IEM is disabled. • The error count, elapsed monitoring time, and information about paths not subject to automatic failbacks are cleared. Set AFB to on. The operations of AFB and IEM do not change. Change the AFB setting.
-lic Specify this option for when a license is updated. The HDLM license is provided via a license key or license key file. A license key file is a file that stores the HDLM license key. If you use a license key file: Store the license key file named hdlm_license directly under the Windows installation drive, and then execute the set -lic operation. A message confirming that the license key has been registered is displayed, depending on the license key type defined in the license key file.
The following example shows how to update the license key when the license key file does not exist: PROMPT>dlnkmgr set -lic KAPL01049-I Would you like to execute the operation? Operation name = set [y/n]: y KAPL01083-I There is no license key file. File name =Windowsinstallation-destination-drive-name\hdlm_license KAPL01068-I Enter a license key:************* KAPL01071-I A permanent license was installed. PROMPT> -rmlu { on [ -force ] | off } Enables or disables the LU dynamic deletion function.
-audlog {on [-audlv audit-log-data-collection-level] [-category [[ss][a][ca]|all]]|off} Specifies whether to collect audit log data. on: Audit log data is collected. off: Audit log data is not collected. -audlv audit-log-data-collection-level Specifies the severity level that determines the selection of audit log data to be collected. The table below lists and describes the values used for this setting. The default is 6.
You can specify a decimal (base 10) value from 0 to 999999. The default is 1. If you specify 0, operation is the same as when load balancing is disabled. -expathusetimes number-of-path-use-times Specifies the number of times the same path can be used for sequential I/ O operations when the extended Round Robin (exrr), Least I/Os (exlio), or Least Blocks (exlbk) algorithm is used for load balancing. You an specify a decimal (base 10) value from 0 to 999999. The default is 100.
The following example shows how to display the format of the set operation: PROMPT>dlnkmgr set -help set: Format dlnkmgr set { -lb on [ -lbtype { rr | exrr | lio | exlio | lbk | exlbk } ] | -lb off | -ellv ElogLevel | -elfs ElogFileSize | -elfn Number-Of-ElogFiles | -systflv TraceLevel | -systfs TraceFileSize | -systfn Number-Of-TraceFiles | -pchk on [ -intvl Interval-Time ] | -pchk off | -afb on [ -intvl Interval-Time ] | -afb off | -iem on [ -intvl Error-Monitor-Interval ] [ -iemnum Number-Of-Times ] | -i
100) AutoPATH_ID { 000000 - 999999 }(Decimal) Dpc-Interval { 1 - 1440 }(Minute) (Default Value 10) KAPL01001-I The HDLM command completed normally. Operation name = set, completion time = yyyy/mm/dd hh:mm:ss PROMPT> view (Displays Information) The dlnkmgr command's view operation displays HDLM program information, HDLM management-target device information, path information, and LU information. If the I/O load on the dynamic disk is heavy, it might take a while to execute the view operation.
[-srt {pn|lu|cp}] [-exlu] [-t] To display a summary of path information dlnkmgr view -path -c [-stname] [-srt {lu|cp}] [-t] To Display LU Information To display LU information dlnkmgr view -lu [-hdev host-device-name|-pathid AutoPATH_ID] [-exlu] [-t] To display LU information (by adding items to be displayed) dlnkmgr view -lu -item [ [slpr] [pn] [cp] [clpr] [type] [ic] [ie] [dnu] [iep] [dpc] [vid] [ha] [hastat] |all ] [-hdev host-device-name|-pathid AutoPATH_ID] [-exlu] [-t] To display a summary of LU i
Parameters This section describes the parameters for the view operation, in the following order: Parameters Used When Displaying Program Information on page 6-34 Parameters Used When Displaying HDLM Management-target Device Information on page 6-40 Parameters Used When Displaying Path Information on page 6-42 Parameters Used When Displaying LU Information on page 6-57 Parameter Used When Displaying the Format of the view Operation on page 6-71 Parameters Used When Displaying Program Information -sys [-sfun
Parameter and program information to be displayed Item Description When the setting status of load balancing is on, one of the following types of algorithms is used for load balancing is displayed in the parentheses following on.
Parameter and program information to be displayed Item Description Number Of Trace Number of trace files Files Path Health Checking • Settings for path health checking: on: Enabled off: Disabled • Checking interval: When the setting of the path health checking is on, the checking interval of path health checking is displayed within the parentheses following on. The time is in minutes.
Parameter and program information to be displayed Item Description • Checking interval The parentheses following the setting status shows the checking interval for reviewing information about the switching of controllers performed by the storage system. "Minute" is used as the unit. If different settings have been specified for each storage system or LU, an asterisk (*) is added after the parentheses in which the checking interval is displayed.
Parameter and program information to be displayed Item Description For example, when there are 100 days left until the license period (2006/08/21) expires, the following appears: 2006/08/21(100days after) -audlog Audit Log Settings for audit log data collection: • Information about audit log data collection settings Whether collection is enabled: on: Enabled off: Disabled • Audit log data collection level: When audit log data collection is on, the collection level that has been set is displayed wit
When the HDLM manager starts, HDLM cluster servers are automatically recognized. Examples Example 1 The following example shows how to display information about the HDLM function settings: PROMPT>dlnkmgr view -sys -sfunc HDLM Version : x.x.
PROMPT>dlnkmgr view -sys -pdrv HDLM Driver Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss PROMPT> Example 5 The following example shows how to display information about the HDLM license: PROMPT>dlnkmgr view -sys -lic License Type Expiration Permanent KAPL01001-I The HDLM command completed normally.
Use this parameter to display information about an HDLM managementtarget device (except the Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP series, Hitachi AMS2000/AMS/WMS/ SMS series, HUS100 series, Universal Storage Platform V/VM series, and Virtual Storage Platform series) that was specified when HDLM was installed. Table 6-11 HDLM Management-target Device Information on page 6-41 describes the displayed items.
KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss PROMPT> Parameters Used When Displaying Path Information When displaying path information, if you specify either the -item or -c parameter and also specify the -path parameter, you can select the items to display and display a summary of path information. This section describes each parameter, path information and displayed items.
-iem Use this parameter to add IEP to path information and display information about intermittent errors. -srt {pn|lu|cp} Use this parameter to sort the path information in ascending order, according to the specified sorting keys. The sorting keys are as follows: the first sorting key is the name of the storage system (DskName), the second sorting key is the value specified by the -srt parameter, and the third sorting key is AutoPATH_ID.
When the -exlu parameter is specified: 6-44 Command Reference Hitachi Dynamic Link Manager User Guide for Windows®
Parameters to display path information, by selecting a display item: -path -item When you specify the -path parameter together with the -item parameter, the command only displays the items specified by the value of the -item parameter. If you specify no value for the -item parameter, only the PathID and the Status fields are displayed.
-hdev host-device-name Displays information only for the paths accessing the specified host device. Specify a drive letter to indicate the desired host device. You cannot specify the host device unless a drive letter has been assigned. The host-device-name string is case sensitive. When you specify this parameter, HDevName is displayed by default. It is not necessary to specify hd for the -item parameter.
If this parameter is specified, all 32 digits of the iLU are displayed instead of truncating the iLU to 13 digits. If this parameter is not specified, any characters after the 13th digit of the iLU of the EMC DMX series, EMC CX series, and HP EVA series will not be displayed. Ellipsis (...) will be displayed instead.
If the -c parameter is specified at the same time as the -path parameter, only PathID, DskName, iLU, CP, Status, and Type are displayed for the path information. The displayed contents are also shortened, so that each path information item is displayed on a single line. The items that are displayed are PathID, DskName, iLU, CP, Status, and Type. For details on what is displayed for each item, see Table 6-13 Displayed Path Information on page 6-49.
Displayed path information Table 6-13 Displayed Path Information on page 6-49describes the displayed path information. The following explains the table headings: • No summary displayed: The user specifies only the -path parameter or the -path -item parameter. • Summary displayed: The user specifies the -path -c parameter. Table 6-13 Displayed Path Information Displayed Item No summary displayed Description Summary displayed Paths Total number of displayed paths, indicated by a decimal number.
Displayed Item No summary displayed Description Summary displayed Reduced means that some paths might have an error status, in which case you should check the status of individual paths and resolve the problem for any paths that have an error status. IO-Count Total I/O count for all the displayed paths, indicated by a decimal number. The maximum value that can be displayed is 232 - 1 (4294967295). If the total I/O count reaches the maximum value, it will re-start from 0.
Displayed Item No summary displayed Description Summary displayed SMS series, HUS100 series, Universal Storage Platform V/VM series, and Virtual Storage Platform series you can identify an actual storage system by referencing the above information from the storage system management program.
Displayed Item No summary displayed Description Summary displayed The port number of the channel adapter, which identifies the CHA port that is mounted on the storage system. You can identify an actual CHA port by referencing this number from the storage system management program. • For the EMC DMX series, EMC CX series, and HP EVA series: A hyphen (-) is displayed.
Displayed Item No summary displayed Description Summary displayed (4294967295). If the total I/O count reaches the maximum value, it will re-start from 0. To reset the IO-Count value to 0, execute the dlnkmgr command's clear operation. Executing the clear operation also resets the number of I/O errors (IO-Errors) to 0. For details about the clear operation, see clear (Returns the Path Statistics to the Initial Value) on page 6-3.
Displayed Item No summary displayed Description Summary displayed parameter or when you specify hbaportwwn for the -item parameter. Note that a hyphen (-) is displayed in the following cases: PhysicalDskName - • When using the EMC DMX, EMC CX, or HP EVA series • When using iSCSI interfaces When a path is migrated using a virtual ID, displays the name of the storage system that is connected by the migrationdestination path.
In a cluster configuration, an offline operation requested during reserve processing is put into the waiting-to-execute state, and does not execute until the reserve processing finishes. #3 This storage system applies when the dynamic I/O path control function is disabled. #4 The drive letter assigned to a dynamic disk volume is not displayed.
Product ID Model names of storage systems Without the -stname parameter With the -stname parameter (Displays the following for the model ID) Hitachi SMS series SMS Hitachi WMS series WMS HUS100 series HUS100 Lightning 9900 series Emulation type# 9910/9960 Lightning 9900V series 9970/9980 SVS SVS • Hitachi Universal Storage Platform 100 • Hitachi Universal Storage Platform 600 • Hitachi Universal Storage Platform 1100 • Hitachi NSC55 • Hitachi Universal Storage Platform V • Hitachi
¢ For command devices, -CM is added to the end of the emulation type of the storage system (for example, DF600F-CM). Parameters Used When Displaying LU Information When displaying LU information, if the -item parameter, -c parameter, or the -c -item parameter is specified at the same time as the -lu parameter, you can add and display items and display a summary of LU information. This section describes each parameter and the LU information and displayed items.
• When an HDLM management-target device is the EMC DMX series, EMC CX series, or HP EVA series: If this parameter is specified, all 32 digits of the iLU are displayed instead of truncating the iLU to 13 digits. If this parameter is not specified, any characters after the 13th digit of the iLU of the EMC DMX series, EMC CX series, and HP EVA series will not be displayed. Ellipsis (...) will be displayed instead.
When the -exlu parameter is specified: PROMPT>dlnkmgr view -lu -exlu Product : 9500V SerialNumber : 0329 LUs : 2 iLU HDevName PathID 0000 P 000006 000014 0001 Q 000007 000015 Product SerialNumber LUs Status Online Online Online Online : DGC : : 2 iLU HDevName PathID 6006016099C50E0028CB54C558CDD911 F 000004 000008 6006016099C50E008C70FDB358CDD911 G 000005 000009 Product SerialNumber LUs Status Online Online Online Online : EMC : : 4 iLU HDevName PathID Status 6006048000018781000153594D423031 L 000000
Table 6-16 Items That Can Be Added by Using the -lu -item Parameter and Sub-parameters Item that can be added Sub-parameter SLPR slpr PathName pn ChaPort cp CLPR clpr Type type IO-Count ic IO-Errors ie DNum dnu IEP iep DPC dpc Physical-Product vid Physical-SerialNumber vid Physical-iLU vid Physical-ChaPort vid Org-Product ha Org-SerialNumber ha Org-iLU ha HaStat hastat All items are displayed all In the sub-parameters, -hdev or -pathid, you can filter the LU informati
Use this parameter to display only the information about the LU that is connected to the path with that specified AutoPATH_ID. -exlu • When an HDLM management-target device is the EMC DMX series, EMC CX series, or HP EVA series: If this parameter is specified, all 32 digits of the iLU are displayed instead of truncating the iLU to 13 digits. If this parameter is not specified, any characters after the 13th digit of the iLU of the EMC DMX series, EMC CX series, and HP EVA series will not be displayed.
SerialNumber : 9203008 LUs : 3 Dynamic I/O Path Control : on* iLU HDevName DPC PathID Status 000006 E on 000000 Online 000003 Online 000007 F off 000001 Online 000004 Online 000008 G on 000002 Online 000005 Online KAPL01001-I The HDLM command completed normally.
HUS100 series, Universal Storage Platform V/VM series, or Virtual Storage Platform series: 16 digits are displayed for the iLU even if this parameter is specified. -t Omits the title for each information item. Example When the -exlu parameter is not specified: When the -exlu parameter is specified: Parameters to display a summary of LU information by adding items to be displayed: -lu -c -item The items displayed when the -item option is added to the -lu -c options.
Table 6-17 Items That Can Be Added by Using the -lu -c -item Parameter and Sub-parameters Item that can be added SLPR Sub-parameter slpr The sub-parameter is: -exlu • When an HDLM management-target device is the EMC DMX series, EMC CX series, or HP EVA series: If this parameter is specified, all 32 digits of the iLU are displayed instead of truncating the iLU to 13 digits.
• Summary displayed: The user specifies the -lu -c parameter or -lu -c item parameter.
Displayed item No summary displayed Description Summary displayed This number combined with the storage system name (shown in DskName) identifies the LU that is accessed by a path.
Displayed item No summary displayed Description Summary displayed however, that the displayed drive letter is the drive letter for one of the Devs included in the LU. - DPC The setting information about the dynamic I/O path control function is displayed for each LU. on: The dynamic I/O path control function is enabled. off: The dynamic I/O path control function is disabled. -: The dynamic I/O path control function is not supported. PathID - The AutoPATH_ID.
Displayed item No summary displayed Status Description Summary displayed - • CHA ports in the storage system that do not support the cache logical partition function • Paths connected to the Snapshot Image of the Copy-on-write Snapshot of the Hitachi AMS2000/AMS/WMS/SMS series.
Displayed item No summary displayed IO-Count#1 Description Summary displayed - Total I/O count for a path. The maximum value that can be displayed is 232 - 1 (4294967295). If the total I/O count reaches the maximum value, it is reset, and the count is re-started from 0. To reset the IO-Count value to 0, execute the dlnkmgr command's clear operation. Executing the clear operation also resets the number of I/O errors (IO-Errors) to 0.
Displayed item No summary displayed Description Summary displayed When a virtual ID is not used, a hyphen (-) is displayed. PhysicaliLU - When a path is migrated using a virtual ID, displays LU number in the storage system that is connected by the migration-destination path. • For HUS VM indicated by a hexadecimal number. The first two characters of iLU are the CU number, and the last two characters are the internal LU number within the CU.
- The user selected the item to be displayed by using the -lu -c -item parameter. - No value was specified for the parameter. #3 The drive letter assigned to a dynamic disk volume is not displayed. #4 In a cluster configuration, an offline operation requested during reserve processing is put into the waiting-to-execute state, and does not execute until the reserve processing finishes. #5 This storage system applies when the dynamic I/O path control function is disabled.
delete (Deletes a Path Dynamically) The dlnkmgr command's delete operation batch-deletes disconnected paths whose statuses are Offline(C) from the HDLM-management targets. You can execute this command dynamically without any effects on existing paths. Format To Delete a Path Dynamically dlnkmgr delete -path [-s] To Display the Format of the delete Operation dlnkmgr delete -help Parameters To Delete a Path Dynamically -path Indicates that the target of the operation is a path managed by HDLM.
To Display the Format of the delete Operation -help Use this parameter to display the delete operation format. Example PROMPT>dlnkmgr delete -help delete: Format dlnkmgr delete -path [-s] KAPL01001-I The HDLM command completed normally.
6-74 Command Reference Hitachi Dynamic Link Manager User Guide for Windows®
7 Utility Reference This chapter explains the utilities used by HDLM.
Overview of the Utilities HDLM provides the following utilities: • The DLMgetras utility for collecting HDLM error information When an error occurs, this utility collects the files that contain the information that you need to submit to your HDLM vendor or maintenance company. For details about the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2.
files, definition files, and OS information. The collected information is archived in a file and saved to a folder of your choosing. Whenever the host is restarted, some of the information that is collected by the DLMgetras utility will be cleared. As a result, whenever an error occurs, immediately execute this utility to avoid losing any valuable information.
The utility obtains logs from each application, system, and security event log. The logs obtained are those output after 00:00 on the date yyyy/ mm/dd. Specify the date in the yyyy/mm/dd format. -eventlogsize {all | maximum-file-length} all Logs from all applications, systems, and security event logs are obtained. maximum-file-length The utility obtains logs from each application, system, and security event log.
Folder that stores collected files#1 folder-to-whichcollected-information-isoutput\folder-to-whichWindows-is-introduced (%SystemRoot%)#3 Files Explanation hdlmtrn.log Trace file hs_err_pidnnnn.log Java execution log (nnnn indicates a process ID) setupact.log Windows log setupapi.log setuperr.log setupapi.app.log#4 setupapi.dev.log#4 setupapi.offline.log# 4 folder-to-which-collectedhdlmtr.
Folder that stores collected files#1 Files Explanation folder-to-whichcollected-information-isoutput\VCS-installationdestination-drive-name_ \Program Files\VERITAS \Cluster Server\log All files under log VCS log Integrated trace file output folder specified in the Hitachi Network Objectplaza Trace Library utility hntrn.log#8 Integrated trace file (HNTRLib2) hntr[1-16].log Integrated trace file (HNTRLib) output when HDLM version 04-00 or earlier was being used application-list.
Folder that stores collected files#1 Files Explanation dlmmgr-lu-all.txt Result of the dlnkmgr view lu -item all -exlu command dlmmgr-path.txt Result of the dlnkmgr view path -exlu command dlmmgr-path-iem.txt Result of the dlnkmgr view path -iem command dlmmgr-sys.txt System information, and driver information for each SCSI port driverquery.txt List of detailed driver information and digital signature information for drivers evApplication.evt#10 Event log for applications evApplication.
Folder that stores collected files#1 Files Explanation hyperv-synfcadm.txt Windows event log related to Hyper-V hyperv-synnicadm.txt Windows event log related to Hyper-V hyperv-synstoradm.txt Windows event log related to Hyper-V hyperv-synstorope.txt Windows event log related to Hyper-V hyperv-vmmsadm.txt Windows event log related to Hyper-V hyperv-vmmsnet.txt Windows event log related to Hyper-V hyperv-vmmsope.txt Windows event log related to Hyper-V hyperv-vmmsstor.
Folder that stores collected files#1 Files Explanation folder-to-whichcollected-information-isoutput\hbsainfo All files under hbsainfo#11 Error information of a Hitachi Command Suite product other than HDLM folder-to-whichcollected-information-isoutput\%SystemDrive% hdlminst.log HDLM installation log #1 The target error information collection folder is created in the folder to which collected information is output.
Note that 2 is part of the integrated trace file name and does not represent part of the file number. #9 You can obtain dlm_iscsims.txt only when the iSCSI software is installed. #10 You can obtain these files only in Windows Server 2003. #11 You can obtain all files under hbsainfo only when a Hitachi Command Suite product other than HDLM from which error information is to be collected is being used.
Procedure for Executing the dlmpr Utility in MSCS Environments: 1. Start a host from among the hosts that make up the MSCS system. 2. Choose Start, Settings, Control Panel, double-click Administrative Tool, and then double click Computer Management. 3. Choose Services and Applications, and then double-click Services. A list of services is displayed. From the list, right-click Cluster Service, and choose Properties.
KAPL10658-I The persistent reservation information of PathID = 0 was cleared. KAPL10640-I The dlmpr utility completed normally. PROMPT> 7. Choose Start, Settings, Control Panel, double-click Administrative Tool, and then double-click Computer Management. 8. Choose Services and Applications, and then double-click Services. A list of services is displayed. From the list, right-click Cluster Service, and then choose Properties.
Parameter -r [PRSV-key-to-be-specified-by-user][-s] Specify this parameter when you register a PRSV key. PRSV-key-to-be-specified-by-user A maximum of 16 hexadecimal digits can be specified. • If this parameter is omitted, or the dlmprsvkey utility is automatically executed during HDLM installation: The dlmprsvkey utility for registering an HDLM persistent reservation key creates a PRSV key by using the MAC address of the NIC and the execution time of the utility.
-h Displays the format of the dlmprsvkey utility. If you do not specify any parameters, a warning message will appear. The dlmchkpath Utility for Checking HDLM Paths If you install or remove HDLM in a multi-path configuration, the disk might become corrupted. Use the dlmchkpath utility to check HDLM paths and to make sure that the system is in a single-path configuration. During an upgrade installation, a re-installation, or removal of HDLM, the dlmchkpath utility is executed automatically.
KAPL12402-W iLU(0100) is in a multi-path configuration. PathID = 0,3 KAPL12402-W iLU(0101) is in a multi-path configuration. PathID = 1,4 KAPL12402-W iLU(0102) is in a multi-path configuration. PathID = 5,2 PROMPT> In the following example, the view operation is performed when the utility determines that the system is in a multi-path configuration. For details about the view operation, see view (Displays Information) on page 6-32.
drive-where-the-installation-DVD-has-been-inserted:\HDLM_Windows \DLMTools# # Use this utility only in an environment where the version of the installed HDLM and the version on the DVD are the same. Format dlmhostinfo [-output installation-information-file | -h] Parameters -output installation-information-file Outputs the installation information to the specified file. If the specified file already exists, the installation information will not be output.
Item name version Value Version of the installed HDLM# # The version that is output is the same as what is output for HDLM Version when the HDLM command is executed with -sys specified for the view operation. Note that when a service pack has been installed, the version in Service Pack Version is output instead. Each item and value is enclosed in double quotation marks (") and is output in CSV format.
-c Checks the contents of the installation-information settings file, the license, and other necessary information, but does not perform an installation. -v Displays the information that was set during installation. If the installation was performed without using the unattended installation functionality, the information specified in a dialog box is displayed.
Table 7-3 Keys That Can Be Defined in the [INSTALLATION_SETTINGS] Section Necessity of definition Key name Description installfile_locat ion Specify the absolute path name of the drive in which the installation DVD is inserted. If this key is omitted, the installer uses the following folder: Maximu Upgrad m e charact New installat er installat ion or length# ion Re1 installat ion Optional Optional 100 workdir Specify an absolute path to an Optional output folder.
Necessity of definition Key name Description Maximu Upgrad m e charact New installat er installat ion or length# ion Re1 installat ion If this key is omitted ¢ ¢ storage_eva In Windows Server 2003, the two series are not included as management targets. In Windows Server 2008, the two series are included as management targets. Specify whether to include the HP EVA series as possible management targets of HDLM.
Necessity of definition Key name Description Maximu Upgrad m e charact New installat er installat ion or length# ion Re1 installat ion n: Do not restart (default). In a cluster environment, do not specify y. Legend: Optional: If no key or setting value is specified, the installer uses the default value. Not required: The specification of any key or setting value is unnecessary. If a key or setting value is specified for the key, the installer ignores the specified value.
[ENVIRONMENT_SETTINGS] section This section defines HDLM operational and function information. HDLM operational and function information is optional, however, if omitted, the installer will use the following values: • For a new installation, the installer uses the default values of the keys that are listed in the following Table 7-4 Keys That Can Be Defined in the [ENVIRONMENT_SETTINGS] Section on page 7-22. • For an upgrade installation or re-installation, the installer uses the old HDLM setting values.
Necessity of definition Key name#1 Description#2 Maximu m Upgrade charact installat New er ion or installat length# Reion 3 installat ion (rr), Least I/Os (lio), or Least Blocks (lbk) algorithm is used for load balancing. You can specify a value from 0 to 999999. The default is 1. Specify 0 to disable load balancing.
Necessity of definition Key name#1 trace_file_numbe r Description#2 Specify the maximum number of trace files (hdlmtr[1-64].log). Maximu m Upgrade charact installat New er ion or installat length# Reion 3 installat ion Optional Optional 2 Optional Optional 3 Specify, in minutes, the interval at Optional which the path health check will be performed. Optional 4 Optional 3 Optional 4 Optional Optional 3 Optional Optional 4 You can specify a value from 2 to 64. The default is 4.
Necessity of definition Key name#1 Description#2 Maximu m Upgrade charact installat New er ion or installat length# Reion 3 installat ion You can specify a value from 1 to 1440. The default is 30. intermittent_err or_monitor_numbe r#5 Specify how many times an error needs to occur to cause HDLM to assume an intermittent error. Optional Optional 2 Specify whether to enable or Optional disable the dynamic I/O path control function by using the values below.
Legend: Optional: ¢ ¢ For a new installation: If no key or setting value is specified, the installer uses the default values. For an upgrade installation or re-installation: If no key or setting value is specified, the installer uses the old HDLM setting values. #1 Keys that are not specified for an upgrade installation or re-installation inherit the current key settings. #2 Specifying an invalid value results in an error.
load_balance_type=exlio load_balance_same_path_use_times=1 lbex_usetimes_limit=100 error_log_level=3 error_log_size=9900 error_log_number=2 trace_level=0 trace_file_size=1000 trace_file_number=4 path_health_check=on path_health_check_interval=30 auto_failback=on auto_failback_interval=1 intermittent_error_monitor=off #intermittent_error_monitor_interval=30 #intermittent_error_monitor_number=3 dynamic_io_path_control=off dynamic_io_path_control_interval=10 remove_lu=off remove_lu_force=off Note: ¢ ¢ If a
The removehdlm Utility for Removing HDLM The removehdlm utility removes HDLM. If you execute the removehdlm utility with the -s parameter specified, no dialog boxes will be displayed during an unattended removal. Format removehdlm [-s [-r] [-w work-folder] | -h] Parameters -s [-r] [-w work-folder] Executes an unattended removal. -r Restarts the host after a removal. -w work-folder Specifies the folder to which removehdlm.log and work files are output.
8 Messages This chapter describes the format and meaning of the message IDs, and also the terms used in the messages and message explanations. For details on the meaning of the return codes output by HDLM when it receives a request from Global Link Manager and measures to take for them, see Return Codes for Hitachi Command Suite Common Agent Component on page 8-111.
□ KAPL15001 to KAPL16000 □ Return Codes for Hitachi Command Suite Common Agent Component □ Events Output to Windows Event Logs by HDLM 8-2 Messages Hitachi Dynamic Link Manager User Guide for Windows®
Before Viewing the List of Messages This section explains the following information that is needed to locate messages and understand the explanations in the sections from KAPL01001 to KAPL02000 on page 8-4. • Format and meaning of the message IDs • Terms used in the messages and message explanations This information is explained below. Format and Meaning of Message IDs Each message has a message ID. The following table shows the format and meaning of message IDs.
KAPL01001 to KAPL02000 Message ID KAPL01001-I Message Text The HDLM command completed normally. Operation name = aa...aa, completion time = bb...bb Explanation Details The HDLM command completed successfully. aa...aa: clear, help, offline, online, set, or view bb...bb: Year/month/day hour:minute:second Action None. KAPL01002-I The HDLM command started. Operation name = aa...aa Details The HDLM command was executed. aa...aa: clear, offline, online, set, or view Action None.
Message ID Message Text Explanation aa...aa: clear, set, offline, or view Action Execute help operation-name of the HDLM command (dlnkmgr) to check the parameter. Specify the correct parameter, and then retry. For details on the help operation, see help (Displays the Operation Format) on page 6-4. KAPL01007-W A duplicate parameter is specified. Operation name = aa...aa, parameter = bb...bb Details aa...aa: clear, offline, online, set, or view bb...
Message ID Message Text Explanation then retry the HDLM command. For details on the view operation, see view (Displays Information) on page 6-32. KAPL01013-E An error occurred in internal processing of the HDLM command. Operation name = aa...aa details = bb...bb Details An error unrelated to a user operation occurred during command processing. aa...aa: clear, offline, online, set, or view bb...
Message ID Message Text Explanation operation, see view (Displays Information) on page 6-32. KAPL01016-W The target CHA port was not found. Operation name = aa...aa Details The path ID indicated by -pathid and required by the -cha parameter is not an object of HDLM management. aa...aa: offline or online Action Execute the view operation of the HDLM command (dlnkmgr view path), and then check the value displayed in ChaPort. Specify an AutoPath_ID that passes through the relevant CHA port, and then retry.
Message ID Message Text Explanation check the settings, and then retry. For details on the view operation, see view (Displays Information) on page 6-32. ¢ view operation Refer to Chapter 3, Creating an HDLM Environment on page 3-1. Creating an HDLM Environment or Reconfiguring the HDLM Operating Environment on page 4-16, and then configure any paths that exist.
Message ID Message Text Explanation bb...bb: Parameters that cannot be specified at the same time Action Execute help operation of the HDLM command (dlnkmgr) to check which parameters can be specified at the same time, and then retry. For details on the help operation, see help (Displays the Operation Format) on page 6-4. KAPL01035-W The cluster support function is active, so the load balancing function is not supported. Details The load balancing function cannot be enabled because MSCS is installed.
Message ID Message Text Explanation A value other than y and n was entered. Enter y or n. Action Enter y or n. KAPL01041-E The entered value is invalid. The Details operation stops. Operation Command processing will be name = aa...aa aborted because an incorrect value was entered three times in a row for a request. aa...aa: clear, offline, online, or set Action Check the correct value, and then re-execute the HDLM command. KAPL01044-W A duplicate parameter value is specified. Operation name = aa...
Message ID Message Text Explanation Action None. KAPL01047-W Only one offline request can be registered in a batch job. Details The offline command cannot be executed because offline processing is already being performed. Action Wait until the offline request registered in the batch job finishes, and then retry. KAPL01048-W Help information cannot be found. Operation name = aa...aa. Details The specified operation is not an operation of the HDLM command. aa...
Message ID Message Text Explanation details on the online operation, see online (Places Paths Online) on page 6-11. KAPL01051-I Because no path has been selected among the currently displayed paths, the paths in the Offline(C), Offline(E), and Online(E) statuses will be changed to the Online status. Is this OK? [y/n]: Details All the paths will be placed Online because the path selection parameter is not specified for the online operation. To place all the paths Online, enter y.
Message ID Message Text Explanation KAPL01054-W During the offline operation Details processing of the HDLM A path that cannot be set to command, a path that cannot be Offline(C) was detected during placed in the Offline(C) status multi-path offline processing. To was detected. PathID = aa...aa ignore this path and perform Would you like to continue the offline processing for the next processing of the offline path, enter y. To cancel offline operation? [y/n]: processing, enter n. aa...
Message ID Message Text to the Online status. Is this OK? [y/n]: Explanation or -cha parameter has been specified. To continue processing, enter y. To cancel processing, enter n. aa...aa: CHA port or HBA Action If you want to execute online processing for the paths that meet the specified requirements, enter y. If you want to terminate processing, enter n. KAPL01058-W The specified parameter value is Details not needed. Operation name = A parameter value was specified aa...aa, parameter = bb...
Message ID Message Text Explanation aa...aa: online, offline, set, or clear Action None. KAPL01061-I aa...aa path(s) were successfully placed bb...bb; cc...cc path(s) were not. Operation name = dd...dd Details This message indicates the number of the paths processed in an online/offline operation. aa...aa: Number of paths where the online/offline operation was successful (decimal (base-10) number) bb...bb: Online, Online(S), Online(D) or Offline(C) cc...
Message ID Message Text Explanation For details on the view operation, see view (Displays Information) on page 6-32. KAPL01063-I The target path(s) are already aa...aa. Details As a result of a previous online/ offline operation, the specified path has already been set to Online/Online(S)/Online(D)/ Offline(C). aa...aa: Online, Online(S), Online(D) or Offline(C) Action Use the view operation of the HDLM command (dlnkmgr) to check the status of the path.
Message ID Message Text Explanation cannot view the path information by specifying the host device name. Re-execute the dlnkmgr command's view operation without specifying the host device name. KAPL01065-E The configuration does not support the simultaneous use of the load balancing and cluster support functions.
Message ID Message Text Explanation A license was renewed and is registered as an emergency license. aa...aa: Year (4 digits)/month (01-12)/day (01-31) Action Install a permanent license by the expiration day. KAPL01073-E The temporary license expired. Details The temporary license has expired. Register a permanent license. Action Register a permanent license. KAPL01074-E The emergency license expired. Details The emergency license has expired. Register a permanent license.
Message ID Message Text Explanation Action Set the intermittent errormonitoring interval to a value that is equal to or greater than (automatic-failback-checkinginterval x number-of-times-erroris-to-occur-for-intermittent-errormonitoring). KAPL01081-E The license key file is invalid. File name = aa...aa Details The format of the license key file is invalid. aa...
Message ID Message Text Explanation If a license key file exists, delete it. KAPL01088-W The specified parameter values Details cannot be specified at the same aa...aa: view time. Operation name = aa...aa, bb...bb: Parameter name parameter = bb...bb, parameter values = cc...cc cc...cc: Parameter values that cannot be specified at the same time Action Execute help operation-name of the HDLM command (dlnkmgr) to check which parameter can be specified, and then retry.
Message ID KAPL01096-E Message Text Explanation An attempt to acquire the Details Service Pack version information aa...aa: Code showing the reason has failed. details = aa...aa for the error Action Re-execute the command. If the same error occurs again, execute the DLMgetras utility for collecting HDLM error information, acquire the error information, and then contact your HDLM vendor or the company for which you have a service contract. KAPL01097-W All the current trace files will be deleted.
Message ID Message Text Explanation hbaportwwn parameter could not be found. aa...aa: offline or online Action Use the view operation of the HDLM command (dlnkmgr view path -hbaportwwn) to check the target HBA port WWN. After that, specify the appropriate HBA port WWN, and then retry. KAPL01102-I All the paths which pass the specified aa...aa port will be changed to the Offline(C) status.
Message ID Message Text Explanation If you want to execute the online processing for the paths which pass the specified target, enter y. If you want to terminate the processing, enter n. KAPL01106-W One or more connected storage system cannot use the load balancing function. Action KAPL01107-I The load balancing type specified for individual LUs will become invalid when this operation is executed.
Message ID Message Text Explanation company if there is a maintenance contract for HDLM. KAPL01116-W The audit log configuration file is Details invalid. Execute the "dlnkmgr The audit log configuration file is view -sys -audlog" command invalid. and check the setting. Action Execute the dlnkmgr view -sys -audlog command, and then specify the desired setting by using the dlnkmgr set -audlog command. KAPL01117-W An error occurred during processing to read the audit log configuration file.
Message ID Message Text Explanation HDLM Error Information on page 7-2. KAPL01133-I aa...aa path(s) were Details successfully placed bb...bb; The number of paths processed by cc...cc path(s) were successfully an online operation is shown. placed dd...dd; ee...ee path(s) aa...aa: The number of paths were not. Operation name = which changed to the Online ff...ff status bb...bb: Online or Online(S) cc...cc: The number of paths which changed to the Online(S) or Online(D) status dd...
Message ID Message Text Explanation KAPL01155-W The dynamic I/O path control Details function is already set to aa...aa aa...aa: "on" or "off" for storage. Action Use the view operation of the HDLM command (dlnkmgr) to check the setting for storage. For details on the view operation, see view (Displays Information) on page 6-32. KAPL01156-I The dynamic I/O path control function was set to aa...aa for storage. Details aa...
Message ID Message Text Explanation already been deleted from HDLM. KAPL01161-I This operation will change the path configuration. Do you want to continue? [y/n]: Details This message confirms whether to perform a path configuration change by using a delete operation. Action Enter y to change the path configuration, or enter n to cancel the operation. KAPL01163-E The path configuration change failed. (details = aa...aa) Details This message indicates that a delete operation failed. aa...
Message ID Message Text Explanation Use the view operation of the HDLM command (dlnkmgr) to verify that the paths were deleted. KAPL01166-I If you execute this operation, the specified number of times that the same path can be used for individual LUs will become invalid. Do you want to execute the operation anyway? Operation name = set [y/n]: Details The specified number of times that the same path can be used for individual LUs will become invalid. To continue the operation, enter y.
Message ID Message Text Explanation To execute online processing, enter y. To cancel the operation, enter n. Before you execute the processing, you must check the path status by executing the view operation of the HDLM command dlnkmgr. KAPL01170-I All Online(S) or Online(D) paths that are connected to the LU that has the specified path ID will be set to Online. Is this OK? [y/n]: Details All paths in the Online(S) or Online(D) status for each specified LU will be set to Online. To continue, enter y.
KAPL02001 to KAPL03000 Message ID KAPL02001-I Message Text Explanation HDLM GUI has started normally. Details java.version = aa...aa aa...aa: Version Action None. KAPL02002-I HDLM GUI has terminated. Action None. KAPL02003-E KAPL02004-E You lack permission to start HDLM GUI. Action An error occurred during internal processing of HDLM GUI. HDLM GUI cannot start. Details = aa...aa Details Execute the command as a user with Administrators group permissions or as an Administrator.
Message ID Message Text Explanation Set up a path between the host and storage system, and then restart the host. KAPL02007-E The HDLM manager could not be Details connected. The aa...aa The system could not access the operation has been stopped. HDLM manager when the Option window was started up or the Set Option Information operation was executed. aa...
Message ID Message Text Explanation ¢ Refresh ¢ Clear Data Action None. KAPL02014-W No data has been input in aa...aa. Details Nothing has been entered into the input field of the Option window. aa...aa: Input item (character string) ¢ ¢ Path Health Checking Interval Auto Failback Checking Interval ¢ Error Log File Size ¢ Monitoring Interval ¢ Number of times ¢ Error Log Number of Files ¢ Trace File Size ¢ Trace Number of Files Action Data has not been input for the specified item.
Message ID Message Text Explanation The entered value for the input field of the Option window is not within the valid range. aa...aa: Input item (character string) ¢ ¢ Path Health Checking Interval Auto Failback Checking Interval ¢ Error Log File Size ¢ Monitoring Interval ¢ Number of times ¢ Error Log Number of Files ¢ Trace File Size ¢ Trace Number of Files Action See the HDLM GUI Help to specify a number within the valid range.
Message ID Message Text Explanation If you want to execute offline processing, click OK. To cancel offline processing, click Cancel. KAPL02020-I If you are sure that there would be no problem when the path is placed in the Offline(C) status, click OK. Otherwise, click Cancel. [OK/Cancel] Details This is a confirmation to check whether you really want to change the selected path(s) to the Offline(C) status. If you want to continue, click OK. If you do not want to proceed, click Cancel.
Message ID Message Text Explanation changed to Offline(C) was detected. If you want to ignore the path and continue, click OK. To cancel the operation, click Cancel. aa...aa: Path ID (decimal (base-10) number) Action If you want to continue offline processing, click OK. To cancel offline processing, click Cancel.
Message ID Message Text Explanation check the path status, and then retry. KAPL02028-W You lack write permission for the aa...aa. Details You do not have write permission for the specified CSV file. aa...aa: Output CSV file name Action Check whether you have access permission for the specified file and whether the specified file name is correct. KAPL02029-E An error occurred during internal processing of the HDLM GUI. The aa...aa operation has been stopped. Details = bb...
Message ID Message Text Explanation vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2. KAPL02032-E The aa...aa operation cannot be Details executed because the amount of There was not enough memory to memory is insufficient. use the HDLM GUI. aa...
Message ID Message Text Explanation Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2. KAPL02040-E The Offline(C) path cannot be placed Online. PathID = aa...aa Details aa...
Message ID Message Text Explanation Click Refresh to update the contents of the view operation, check the path status, and then retry. KAPL02044-W aa...aa exists already. Do you want to overwrite it? [OK/ Cancel] Details The existing file will be overwritten. To continue, click OK. Otherwise, click Cancel. aa...aa: File name Action To overwrite the existing file, click OK. Otherwise, click Cancel. KAPL02052-W The HDLM manager could not be Details connected.
Message ID Message Text Explanation For the Path IDs of any failed paths, see the operation log. Click Refresh to view any paths that were registered together as a batch job. KAPL02055-I The target path(s) are already aa...aa. Details The specified paths are already Online/Offline(C), as a result of the online/offline operation that was just executed. aa...aa: Online or Offline(C) Action Click Refresh to check the status of the path.
Message ID Message Text Explanation reconfigured, click the Refresh button. KAPL02063-W The version number cannot be displayed. Details The version number could not be acquired because an attempt to read a parameter file, which starts up the HDLM GUI, failed. Action The version number cannot be displayed, but HDLM GUI operations can be executed. If you want to display the version number, reinstall HDLM.
Message ID Message Text Explanation contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. KAPL02077-W An attempt to acquire the Details Service Pack version information aa...aa: Code showing the reason failed. Details = aa...aa for the error Action Re-execute the command.
Message ID Message Text Explanation HDLM error information, and then contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. KAPL02087-I "Configuration View" is not supported for this storage system model. Please use the "Path List View" instead. Storage = aa...aa Details "Configuration View" cannot be displayed for the selected storage system because "Configuration View" cannot be displayed in the HDLM GUI. aa...
Message ID Message Text Explanation Action Refer to the contents of the warning. KAPL03003-E HDLM API Error information aa...aa Details This information is required for resolving problems. aa...aa: API trace error information Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Message ID Message Text Explanation HDLM Error Information on page 7-2. KAPL03007-E An error occurred during communication with the HDLM manager. (aa...aa) Details This information is required for resolving problems. aa...aa: API trace error information Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
KAPL04001 to KAPL05000 Message ID KAPL04001-I Message Text HDLM manager started. Explanation Action None. KAPL04002-E Could not start the HDLM manager. Details The HDLM manager failed to start because the current environment is unsuitable for the HDLM manager to run in. Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Message ID KAPL04006-E Message Text Cannot register the service control handler function. Return value = aa...aa Explanation Details HDLM manager could not start normally because it was unable to register the service control handler function. aa...aa: OS error code Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL04007-E Cannot register the service status. Return value = aa...
Message ID Message Text Explanation If the same error occurs, re-install HDLM. For details on the view operation, see view (Displays Information) on page 6-32. For details on the set operation, see set (Sets Up the Operating Environment) on page 6-16. KAPL04010-E Could not open the error log file. Details HDLM manager could not start normally because it was unable to open the error log file.
Message ID Message Text Explanation Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2. KAPL04014-E Output is impossible via the communication pipe. RC = aa...aa Details Data could not be written to the pipe file while communicating with an HDLM command. aa...
Message ID Message Text Explanation None. KAPL04022-W HDLM manager warning information - aa...aa Details This information is required for resolving problems. aa...aa: HDLM manager trace warning information Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2.
Message ID KAPL04025-C Message Text A memory shortage occurred in the HDLM manager. Explanation Details There was not enough memory to run the HDLM manager processes. Action To increase the amount of free memory, terminate unnecessary applications or restart the host. KAPL04026-I The temporary license is valid. The license expires in aa...aa days on (bb...bb). Details aa...aa: Number of days remaining bb...
Message ID Message Text Explanation remaining values, the default values will be used. Action For any non-default options, use the dlnkmgr set operation to set the options again. For details on the set operation, see set (Sets Up the Operating Environment) on page 6-16. KAPL04034-E An attempt to create the option definition file has failed. Details An attempt to re-create an option definition file using the default values has failed.
Message ID Message Text bb...bb, Port Number= cc...cc, Community = dd...dd, Trap Data = ee..ee Explanation bb...bb: Destination IP address of the trap cc...cc: Destination port number of the trap dd...dd: Community name given to the trap ee...ee: Transmission data Action None. KAPL04053-W The option definition file was recovered from a work file. KAPL04054-I Action Execute the dlnkmgr view -sys command to check whether the settings are recovered.
Message ID Message Text Explanation Action None. KAPL05002-I DriverEntry() completed normally. Details The initialization function completed successfully. Action None. KAPL05003-I The HDLM driver (filter component) was successfully attached to Disk (aa...aa), Partition (bb...bb). Details aa...aa: Disk sequence number (decimal (base-10) number) bb...bb: Partition sequence number (always 0) A HDLM driver (filter component) device object was added to the disk device stack and partition. Action None.
Message ID Message Text Explanation started or contains an error, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2. KAPL05010-E Could not initialize the HDLM driver (filter component). (aa...aa:bb...
Message ID Message Text Explanation address (hexadecimal number)) is the second or a subsequent path for the LU. Action This is normal. If the target drive cannot be referenced, check the disk configuration. KAPL05014-I The device object (aa...aa) was Details registered as the path (bb...bb). The path (bb...bb: Core logic path identifier (hexadecimal number)) of the device object (aa...aa: Filter driver management table address (hexadecimal number)) was successfully registered into the core logic.
Message ID Message Text Explanation aa...aa: Disk sequence number (decimal (base-10) number) bb...bb: Degree of progress in disk recognition processing (hexadecimal number) cc...cc: Execution result of the disk confirmation command (hexadecimal number) Action None. KAPL05301-E A path has been removed. Make Details sure that the path is correctly When the LU deletion function is connected to the LU, and then enabled, path information is recover the path. If the path output to the event log.
KAPL07001 to KAPL08000 Message ID KAPL07819-I Message Text Data for maintenance: aa...aa bb...bb cc...cc dd...dd. Explanation Details This message is generated by the core logic for maintenance. aa...aa: Detailed information 1 (decimal (base-10) number) bb...bb: Internal function number of the core logic (decimal (base-10) number) cc...cc: Detailed information 2 (decimal (base-10) number) dd...dd: Detailed information 3 (decimal (base-10) number) Action None.
Message ID Message Text balancing function in a cluster configuration. Explanation that cannot use persistent reservations. In a cluster configuration, the load balancing function cannot be used for this kind of LU. aa...aa: Path ID (same as PathID of view -path) (decimal (base-10) number) Action None. KAPL07823-W An LU connected to PathID (aa...aa) can also use the load balancing function in a cluster configuration. Details The LU connected to the PathID aa...
KAPL08001 to KAPL09000 Message ID KAPL08019-E Message Text The path (aa...aa) detected an error (bb...bb). (cc...cc) Explanation Details An error occurred in the path. The error is most likely due to a disconnected cable. aa...aa: Path identifier (hexadecimal number) bb...bb: Error code (hexadecimal number) ¢ When the Windows plug-andplay functionality deletes the SCSI device from Windows 0x00000000 is displayed.
Message ID Message Text Explanation cc...cc: Host port number (same as PathName of view -path) (hexadecimal number) dd...dd: Bus number (same as PathName of view -path) (hexadecimal number) ee...ee: Target ID (same as PathName of view -path) (hexadecimal number) ff...ff: HLU number (same as PathName of view -path) (hexadecimal number) gg...gg: Dev number (same as DNum of view -path) (decimal (base-10) number) hh...hh: Host device name (same as HDevName of view -path) Action The path might be damaged.
Message ID Message Text Explanation The auto recover function recovered a path. This message is output if an error occurs in all the paths to an LU and one of the paths is recovered. aa...aa: Path ID(same as PathID of view -path) (decimal (base-10) number) Action None. KAPL08026-E An error occurred on all the paths of the LU. PathID = aa...aa Details An error occurred in the last, remaining path of an LU. (This is most likely as a result of a disconnection.) aa...
Message ID KAPL08033-E Message Text No path connected to the LU that connects to Path ID (aa...aa) is in the Online(D) status. Explanation Details Due to path failure, path deletion, or offline operation, no path connected to the LU that connects to Path ID (aa...aa) is in the Online(D) status. aa...aa: Path ID (same as PathID of view -path) (decimal (base-10) number) Action To return a path to the Online(D) status, resolve the path failure, and then execute the "dlnkmgr online -dfha" command.
Message ID Message Text Explanation Action To immediately restart the system, select the Yes. I want to restart my computer now check box. If you do not want to immediately restart the system, select the No. I will restart my computer later check box. KAPL09005-E Could not stop the HDLM Details manager. Stop it manually, and An attempt to stop the HDLM then try the installation program manager service has failed. or the remove program again.
Message ID KAPL09014-E KAPL09015-E KAPL09016-E Message Text Explanation The OS must be restarted before you install HDLM. Action HDLM cannot be installed. A newer version of HDLM is already installed. Action Because HDLM has been installed in another system, HDLM cannot be installed in this system. Details Restart the OS before HDLM is installed. Remove HDLM, and then restart the installation program. HDLM cannot be installed on this system because it has already been installed on another system.
Message ID Message Text Explanation Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM. KAPL09026-I Hitachi Network Objectplaza Trace Library 2 wasn't removed because it was being used for other products. Details HNTRLib2 was not removed because it was still being used for another PP. Action None. KAPL09034-E An Internal error occurred in the Details HDLM Installer. Code = aa...aa During installation of HDLM, an bb...
Message ID KAPL09078-I Message Text The emergency license was installed. The license expires on aa...aa. Explanation Details An emergency license was installed. aa...aa: Year (4 digits)/month (01-12)/day (01-31) Action Install a permanent license by the expiration day. KAPL09079-I The permanent license has been Action installed. None. KAPL09080-I The temporary license has been installed. The license expires on aa...aa. Details aa...
Message ID Message Text license key, and then re-install HDLM. Explanation license key was entered three times in a row. Action Obtain a valid license key, and then re-install HDLM. KAPL09088-E The entered license key is invalid. The HDLM installation will now terminate. Obtain a valid license key, and then reinstall HDLM. KAPL09089-W License information cannot be acquired. Action Obtain a valid license key, and then re-install HDLM.
Message ID Message Text Explanation Alternatively, cancel the installation, save the correct license key file in the designated folder, and then re-execute the installation. KAPL09115-W An attempt to delete the license key file has failed. File name = aa...aa Details An attempt to delete the license key file has failed. aa...aa: Windows-installationdestination-drive-name \hdlm_license or the-filethat-the-user-specified Action If a license key file exists, delete it.
Message ID Message Text If installation continues, dd...dd of file version cc...cc will be overwritten. Explanation aa...aa has already been installed. The file version could not be acquired. If the file version could not be obtained, the following message is displayed: Driver aa...aa has already been installed. The file version could not be acquired. In this case, the following message is not displayed: Driver aa...aa has already been installed. The file version is bb...bb is not displayed. aa...
Message ID Message Text Explanation After the installation finishes, without rebooting, execute the dlmprsvkey utility for registering an HDLM persistent reservation key to register the PRSV key. For details on the dlmprsvkey utility, see The dlmprsvkey Utility for Registering an HDLM Persistent Reservation Key on page 7-12. KAPL09134-E The HDLM path cannot be added Details to the Path environment The HDLM path could not be variable.
Message ID Message Text Explanation ¢ C:\Program Files\Common Files\Hitachi For Windows Server 2003 (excluding the x86 edition), Windows Server 2008 (excluding the x86 edition), or Windows Server 2012, Program Files is Program Files (x86) (243 bytes including the added ";") ¢ ¢ ¢ ¢ ¢ C:\Program Files (x86)\HDVM\HBaseAgent\bin C:\Program Files (x86)\HDVM\HBaseAgent \util\bin C:\Program Files (x86)\HITACHI \DynamicLinkManager\bin C:\Program Files (x86)\HITACHI \DynamicLinkManager\lib C:\Program Files
Message ID Message Text license for an update installation. Explanation after the installation. If the same error message is output, contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. Do not perform the following operation: Execute the HDLM command's set -lic operation while updating a license for an upgrade or re-installation of HDLM KAPL09142-E HDLM aa...aa cannot be performed. Wait a while, and then perform aa...aa again. Error Code = bb...
Message ID Message Text Explanation Action None. KAPL09181-I The aa...aa of HDLM version bb...bb completed successfully. Details The unattended installation or remove of HDLM has completed normally. aa...aa: installation or remove bb...bb: Version number of the installed or removed HDLM Action None. KAPL09182-W An attempt to aa...aa HDLM version bb...bb has failed. See the previous messages to resolve the problems. Details The unattended installation or remove of HDLM failed. aa...
Message ID Message Text Explanation Action ¢ In installhdlm utility for installing HDLM: Restart the computer and make sure that HDLM is running correctly. ¢ In removehdlm utility for removing HDLM: None. KAPL09186-I The computer will now restart. Details ¢ In installhdlm utility for installing HDLM: After HDLM is installed, the computer will automatically restart because the restart option was specified in installhdlm.ini.
Message ID Message Text Explanation More than four parameters have been specified for the removehdlm utility for removing HDLM. Action Make sure that the parameters for the installhdlm or removehdlm utilities are appropriate, and then try again. For details on the installhdlm utility, see The installhdlm Utility for Installing HDLM on page 7-17. For details on the removehdlm utility, see The removehdlm Utility for Removing HDLM on page 7-28. KAPL09189-W The parameter contains an incorrect value.
Message ID Message Text Explanation Action Make sure that the path name of the installation-information settings file is appropriate, and then try again. KAPL09192-W An installation information settings file of an unsupported product version is specified. (hdlmversion = aa...aa) Details The specified installationinformation settings file is not supported by this version of HDLM. aa...
Message ID Message Text Explanation Specify drive-in-which-theinstallation-DVD-is-inserted: \HDLM_Windows\ in the installfile_location key of the installation-information settings file. KAPL09196-W Some of the LUs managed by HDLM are not in a single path configuration. Details Before performing an upgrade installation or remove, reconfigure the system into a single-path configuration. Action Reconfigure the system into a single-path configuration, and then try again. KAPL09197-W The user terminated aa.
Message ID Message Text Explanation Action None. KAPL09211-I aa...aa completed successfully. Details aa...aa: dlnkmgr Action None. KAPL09212-E aa...aa ended abnormally. Details aa...aa: dlnkmgr Action Check the error message that was output just before this message, and then perform the action indicated in that error message. KAPL09213-W An error occurred during aa...aa Details processing. Although the aa...aa processing has ended, an error occurred during the processing. aa...
Message ID Message Text Explanation required, see Preparations for Installing HDLM by Performing an Unattended Installation on page 3-27. ¢ In removehdlm utility: Make sure that there is enough unused capacity for the folder specified by the -w parameter. If there is not, allocate the required amount of capacity, and then retry the operation. For details about how to determine the amount of capacity that is required, see Notes on Removing HDLM on page 3-84. KAPL09222-E HDLM could not be removed.
Message ID Message Text Explanation A feature for Hitachi Command Suite Common Agent Component could not be removed. HDLM cannot be managed from Global Link Manager. aa...aa: Feature that could not be removed Action Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM. KAPL09226-I An update (QFE) for MPIO has been installed. Driver version = aa...aa Only the HDLM driver will be installed, without overwriting the MPIO driver.
Message ID Message Text Explanation Action None. KAPL09256-E No search paths have been specified for the Path system environment variable. Add the search paths that were specified during the installation of Windows, and then re-install HDLM. Details No search paths have been specified for the Path system environment variable. The search paths that were specified during the installation of Windows are required for the installation of HDLM.
Message ID Message Text Explanation Delete the MPIO setup information files (the INF files) from the system, and then re-execute the HDLM installation by starting Setup.exe. For details on how to delete them, see Notes on Related Software on page 3-20. KAPL09259-I The HDLM aa...aa installation check has completed successfully. Details The HDLM installation check has completed successfully. aa...aa: Version of HDLM that will be installed Action None. KAPL09260-W Errors were detected during the HDLM aa.
Message ID Message Text Explanation aa...aa: Year (4 digits)/Month (01-12)/Day (01-31) Action None. KAPL09266-I A emergency license (excluding HDLM Light) will be installed. The license expires on aa...aa. Details A emergency license (excluding HDLM Light) will be installed. aa...aa: Year (4 digits)/Month (01-12)/Day (01-31) Action None. KAPL09281-I HDLM 6.3.0 or later has been installed. Only the HDLM driver will be installed, without overwriting the MPIO driver.
Message ID Message Text Explanation None. KAPL09501-E HDLM is not installed on this system. Details An SP cannot be applied because HDLM is not installed on the system. Action Check whether HDLM has been correctly installed. KAPL09504-E The language environments of HDLM and the Service Pack are different. Details The Japanese SP was applied to the English edition of HDLM, or vice versa. Action Acquire the SP that has the same language as the installed HDLM, and then try again. KAPL09505-E aa...
Message ID Message Text Explanation aa...aa: The version of the SP to be installed bb...bb: The HDLM or SP version that has already been installed Action You do not have to install the SP. Keep using HDLM as is. KAPL10001 to KAPL11000 Message ID Message Text KAPL10002-W Too many parameters have been specified. Explanation Details Four or more parameters have been specified. Action Check the parameters of the DLMgetras utility for collecting HDLM error information, and then retry.
Message ID Message Text Explanation DLMgetras Utility for Collecting HDLM Error Information on page 7-2. KAPL10009-W The specified directory already Details exists. Do you want to overwrite The specified folder already exists. it? [y/n]: Enter y to overwrite it, or n to cancel. Action The specified folder already exists. Enter y to overwrite the existing file. Enter n or press any other key to terminate the DLMgetras utility for collecting HDLM error information, without executing it.
Message ID KAPL10030-I Message Text A user terminated the utility for collecting HDLM error information. Explanation Details Processing of the DLMgetras utility for collecting HDLM error information has been terminated because the user replied to the confirmation with an n response. Action None. For details on the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2. KAPL10031-W The entered value is invalid.
Message ID Message Text Explanation environment. Check the system configuration. KAPL10041-I Collection of aa...aa information will now start. Details aa...aa: Log information to be collected Action None. KAPL10042-I Collection of aa...aa information will now finish. Details aa...aa: Collected log information Action None. KAPL10043-I Error information is being collected. (aa...aa%) Details aa...aa: What percentage of all the information to be collected is log information Action None.
Message ID Message Text Explanation Action Make sure that the parameters for the DLMgetras utility for collecting HDLM error information are appropriate, and then try again. KAPL10048-E An error occurred in internal processing of the utility for collecting HDLM error information. Details = aa...aa, bb...bb Details aa...aa: Error number (character string) bb...bb: Error number (character string) Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Message ID Message Text Explanation aa...aa: Specified parameter (character string) Action Execute the dlmpr utility for clearing HDLM persistent reservation with the -h parameter to check the parameter, and then retry. For details on the dlmpr utility, see The dlmpr Utility for Clearing HDLM Persistent Reservations on page 7-10. KAPL10646-W A parameter is invalid. parameter = aa...aa Details aa...
Message ID KAPL10655-I KAPL10656-I Message Text Explanation Specify the PathID of the LU for which you want to clear persistent reservation information. (To cancel, press the x key): Action The persistent reservation information of PathID = aa...aa will be cleared. Is this OK? [y/ n]: Details Enter the path ID of the LU for which you want to clear the persistent reservation information, and then press the Enter key or enter n to cancel.
Message ID Message Text Explanation If the following two conditions are satisfied, contact your HDLM vendor or maintenance company if you have a maintenance contract for HDLM: ¢ ¢ KAPL10662-E Free memory is insufficient. The cluster system service and driver are running. An LU was disconnected from the server during execution of a utility. Action Terminate unnecessary applications, and then retry. If the problem persists, restart the host, and then retry. Alternatively, in dlmpr.
Message ID Message Text Explanation None. KAPL10667-C An attempt to the get physical drive number failed. LU = aa...aa Details An LU without a physical drive number existed. aa...aa: LU number Action If the following condition is satisfied, contact your HDLM vendor or maintenance company if you have a maintenance contract for HDLM. - The cluster system service and the driver are running. KAPL10668-E An attempt to open a device failed. DeviceName = aa...aa Details aa...
Message ID Message Text Explanation ¢ ¢ ¢ Set SNMP Trap Information Set LU Load Balance Get Path Status Log Information ¢ Get Local Time ¢ Add Path Information ¢ Delete Path Information ¢ Set Storage Identification Information Action None. KAPL11902-I aa...aa has started. PathID = bb...bb Details The operation has started on the host. aa...aa: Operation (character string) ¢ Online ¢ Offline bb...bb: The Path ID of the target path (decimal number) Action None. KAPL11903-I aa...
Message ID Message Text Explanation ¢ ¢ ¢ Add Path Information Delete Path Information Set Storage Identification Information Action None. KAPL11904-E aa...aa has completed abnormally. Error status = bb...bb Details The operation has completed abnormally on the host. aa...
Message ID Message Text Explanation An exception occurred during processing on the host. Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if you have a maintenance contract for HDLM. For details on the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2. KAPL11906-I GUI information - aa...aa Details This information is required for resolving problems. aa...
Message ID Message Text Explanation an HDLM Persistent Reservation Key on page 7-12. KAPL12102-W There are too many parameters Action Make sure that the parameters for the dlmprsvkey utility for registering an HDLM persistent reservation key are appropriate, and then try again. For details on the dlmprsvkey utility, see The dlmprsvkey Utility for Registering an HDLM Persistent Reservation Key on page 7-12. KAPL12103-W The parameter value is invalid. (value = aa...
Message ID Message Text Explanation Action Try again as a user who is a member of the Administrators group. For details on the dlmprsvkey utility, see The dlmprsvkey Utility for Registering an HDLM Persistent Reservation Key on page 7-12. KAPL12106-I An attempt to register the PRSV key was successful. (PRSV key = aa...aa) Details aa...aa: Registered PRSV key (character string) Action None. KAPL12107-W An attempt to register the PRSV key has failed. (PRSV key = aa...aa) Details aa...
Message ID KAPL12111-E Message Text Explanation The registry key for the Details registration destination does not The registry key exist. HKEY_LOCAL_MACHINE\SYSTEM \CurrentControlSet\Services \HDLMdsm\Parameters \PRSVKeyString does not exist. Action Check whether HDLM has been installed correctly. If it has, contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Message ID Message Text Explanation company if there is a maintenance contract for HDLM. For details on the dlmprsvkey utility, see The dlmprsvkey Utility for Registering an HDLM Persistent Reservation Key on page 7-12. KAPL12114-E An invalid PRSV key has been registered. Details An invalid PRSV key has been entered in the registry key HKEY_LOCAL_MACHINE\SYSTEM \CurrentControlSet\Services \HDLMdsm\Parameters \PRSVKeyString.
Message ID Message Text Explanation error occurs before the PRSV key can be acquired. aa...aa: Maintenance information 1 (hexadecimal number) bb...bb: Maintenance information 2 (hexadecimal number) cc...cc: Maintenance information 3 (hexadecimal number) dd...dd: Maintenance information 4 (hexadecimal number) Action None. KAPL12119-E Trace data for maintenance: aa...aa bb...bb cc...cc dd...dd ee...
Message ID Message Text Explanation vendor or the maintenance company if there is a maintenance contract for HDLM. If the WMI repository is corrupted, consider rebuilding the repository. KAPL12151-W A Windows Management Instrumentation service access error occurred. Details = aa...aa, bb...bb Details A Windows Management Instrumentation service access error occurred. The Windows Management Instrumentation service might not be working.
Message ID Message Text Explanation vendor or the maintenance company if there is a maintenance contract for HDLM. If the WMI repository is corrupted, consider rebuilding the repository. KAPL12401-I All LUs managed by HDLM are in Details a single path configuration. This message is displayed when the number of LUs managed by HDLM is 0. Action None. KAPL12402-W iLU (aa...aa) is in a multi-path configuration. PathID = bb...bb[,cc...cc]...
Message ID Message Text Explanation Terminate unnecessary applications to increase the amount of free memory. Alternatively, restart the host. KAPL12406-E An error occurred in internal processing of the utility for checking HDLM paths. Error code = aa...aa, details code = bb...bb Details aa...aa: Error code bb...bb: Details code Action ¢ Error code: 22 Check whether HDLM has been installed correctly.
Message ID Message Text Explanation KAPL13603-W The audit log configuration file is Details invalid. Execute the "dlnkmgr The audit log configuration file is view -sys -audlog" command invalid. and check the setting. Action Restart the HDLM manager, execute the dlnkmgr view -sys -audlog command, and then specify any desired settings by using the dlnkmgr set -audlog. KAPL13604-W An error occurred during processing to read the audit log configuration file.
Message ID Message Text KAPL13803-W The user does not have the privileges required to execute the dlmhostinfo utility for confirming HDLM installation information. Explanation Details The dlmhostinfo utility must be executed by a user with Administrator group privileges. Action Re-execute the dlmhostinfo utility as a user with Administrator group privileges. KAPL13804-W Too many parameters have been specified. Details Three or more parameters have been specified.
Message ID Message Text Explanation ¢ ¢ ¢ ¢ The installation information file already exists. A folder with the same name as the installation information file exists. The parent folder does not exist. The user does not have write permission for the parent folder. Action Make sure that the installation information file does not meet any of the above conditions.
Message ID KAPL15032-I Message Text Explanation An HDLM persistent reservation key was successfully displayed. Command Line = aa...aa Details KAPL15033-W An attempt to display an HDLM persistent reservation key has failed. Command Line = aa...aa Details KAPL15034-I Details The status that indicates whether paths are in an individual or multiple path configuration was successfully displayed. Command Line = aa...aa aa...aa: Name of the utility that the user executed aa...
Message ID Message Text Explanation KAPL15106-W Setting up the operating environment failed. Command Line = aa...aa Details KAPL15107-I Details Program information was successfully displayed. Command Line = aa...aa aa...aa: Command that the user executed aa...aa: Command that the user executed KAPL15108-W An attempt to display program information has failed. Command Line = aa...aa Details KAPL15109-I Details Information about HDLMmanagement targets was successfully displayed. Command Line = aa.
Message ID Message Text Explanation KAPL15203-W HDLM GUI was executed by the user who does not have the authority. - KAPL15204-W HDLM GUI has not started successfully. - KAPL15205-I aa...aa has completed successfully. KAPL15206-W aa...aa has failed. Details aa...aa: Refresh, Clear Data, Export CSV, Get Option Information, or Set Option Information Details aa...aa: Refresh, Clear Data, Export CSV, Get Option Information, or Set Option Information KAPL15207-I aa...
Return Code 1002 Explanation Details There is no path on which the operation can be performed. Action Refresh the host information, check the path status, and then perform the operation again. 1003 Details No path was detected. Action Check whether a path between the host and the storage system is connected. If a path is connected, check whether HDLM is configured correctly. 1004 Details Memory required for HDLM internal processing could not be allocated.
Return Code Explanation Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if you have a maintenance contract for HDLM. For details on the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2. 1020 Details An unexpected error occurred during HDLM internal processing.
Return Code Explanation vendor or maintenance company if you have a maintenance contract for HDLM. For details on the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2. 1026 Details The acquisition of path information has been aborted, because the path configuration was changed while the system was attempting to acquire the path information. Action Refresh the host information, check the path status, and then perform the operation again.
Return Code 1036 Explanation Details An attempt to acquire information about the HDLM version or SP version has failed. Action Re-execute the command. If the same error occurs again, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2. 1037 Details A parameter is invalid.
Return Code Explanation Action Refresh the host information, and then perform the operation again. If the same error occurs even again, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or maintenance company if you have a maintenance contract for HDLM. For details on the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2. 1046 Details A parameter is invalid.
Message ID Type Source Category Event ID User KAPL04019-E Error DLMManager None 16403 N/A KAPL04023-E Error DLMManager None 16407 N/A KAPL04024-C Error DLMManager None 16408 N/A KAPL04025-C Error DLMManager None 16409 N/A KAPL04026-I Information DLMManager None 16410 N/A KAPL04027-I Information DLMManager None 16411 N/A KAPL04028-E Error DLMManager None 16412 N/A KAPL04029-E Error DLMManager None 16413 N/A KAPL04030-E Error DLMManager None 16414 N/A
8-118 Messages Hitachi Dynamic Link Manager User Guide for Windows®
A Functional Differences Between Versions of HDLM This section explains the functional differences between newer and older versions of HDLM. □ Functional Differences Between Version 6.6 or Later and Versions Earlier Than 6.6 □ Functional Differences Between Version 6.2 or Later and Versions Earlier Than 6.2 □ Functional Differences Between Version 6.0.1 or Later and Versions Earlier Than 6.0.1 □ Functional Differences Between Version 6.0 or Later and Versions Earlier Than 6.
□ Differences in Default Values □ Differences in the Load Balancing Function in an MSCS Environment A-2 Functional Differences Between Versions of HDLM Hitachi Dynamic Link Manager User Guide for Windows®
Functional Differences Between Version 6.6 or Later and Versions Earlier Than 6.6 • The type of the messages listed below that are output to the event log has been changed from Error to Warning in HDLM version 6.6. Also, the level of the message IDs has been changed from E to W. ¢ KAPL12150, KAPL12151, and KAPL12152 • Drive and Disk Number can be displayed in the Path List view of the HDLM GUI in HDLM version 6.6.
Functional Differences Between Version 5.9.4 or Later and Versions Earlier Than 5.9.4 • The following operations have been changed to reduce the number of responses required during an installation: ¢ ¢ ¢ • Entry of user information has been deleted. When the dlmprsvkey utility for registering an HDLM persistent reservation key is automatically executed and a PRSV key is successfully created, the PRSV key dialog box that prompts the user for a response is no longer displayed.
• An LU has been removed from being an HDLM management-target Automatic Switching of Paths That Have the Online(E), Offline(C), or Offline(E) Status In HDLM 5.5 or later, if one of the following conditions is satisfied, the status of Online(E), Offline(C), or Offline(E) paths will automatically change to Online. In HDLM 5.
Differences in the LU Dynamic Removal Function Depending on the HDLM version, the LU dynamic removal function differs as follows: • In HDLM 05-02, and 5.4 ¢ ¢ When Remove the LU even if there are Offline(C) paths is not specified or when the HDLM command dlnkmgr set -rmlu on is executed If none of the paths connected to an LU are Online or Offline(C), the LU will be removed from being an HDLM management-target.
Differences in the Drive Letters Displayed in Windows Depending on the HDLM version, the Windows' drive letters that are displayed when all paths connected to the LU have an error status differ as follows: • When the LU dynamic removal function is not used in HDLM 5.4 Drive letters are displayed for the disks that are displayed in My Computer. • When the LU dynamic removal function is used in HDLM 5.4, or 5.5 or later, or when the function is not used in HDLM 5.
MSCS environment, even if you set the load balancing function to on, it will automatically change to off.
Acronyms and abbreviations The following acronyms and abbreviations might be used in this guide.
CSV Comma Separated Value CU Control Unit D DBMS Database Management System DEP Data Execution Prevention Dev Device DNS Domain Name Server F FC Fibre Channel FC-SP Fibre Channel Security Protocol FO Failover FQDN Fully Qualified Domain Name G GMT Greenwich Mean Time GPT GUID Partition Table # A B C D E F G H I J K L M N O P Q R S T Acronyms-2 Hitachi Dynamic Link Manager User Guide for Windows® U V W X Y Z
GUI Graphical User Interface GUID Globally Unique Identifier H HBA Host Bus Adapter HDev Host Device HLU Host Logical Unit HTTP Hypertext Transfer Protocol I I/O Input/Output IP Internet Protocol iSCSI Internet Small Computer System Interface L LAN Local Area Network LDAP Lightweight Directory Access Protocol LDEV Logical Device # A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Acronyms-3 Hitachi Dynamic Link Manager User Guide for Windows®
LU Logical Unit LUN Logical Unit Number M MPIO Multipath I/O MVS Multiple Virtual Storage N NIC Network Interface Card NTP Network Time Protocol O OS Operating System P P Port PRSV Persistent Reserve Q QFE Quick Fix Engineering # A B C D E F G H I J K L M N O P Q R S T Acronyms-4 Hitachi Dynamic Link Manager User Guide for Windows® U V W X Y Z
R RADIUS Remote Authentication Dial in User Service S SAN Storage Area Network SCSI Small Computer System Interface SLPR Storage Logical Partition SMTP Simple Mail Transfer Protocol SNMP Simple Network Management Protocol SP Service Pack SSL Secure Sockets Layer SVP Service Processor W WMI Windows Management Instrumentation WWN World Wide Name # A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Acronyms-5 Hitachi Dynamic Link Manager User Guide for Windows®
# A B C D E F G H I J K L M N O P Q R S T Acronyms-6 Hitachi Dynamic Link Manager User Guide for Windows® U V W X Y Z
Glossary This glossary explains the terms used in this manual. A automatic failback A function for checking the status of paths at regular intervals, and automatically placing the status of a path recovered from an error into the Online status. If a path with an Offline(E) or Online(E) status recovers from an error, an automatic failback will place the path Online.
cluster A system of connecting multiple hosts with the same OS or platform (essentially, an environment in which the same application can run) and treating them as one system. D Dev A logical division of an LU that HDLM controls and operates. A Dev is equivalent to a partition in Windows. In Windows, each LU has only one Dev. Each Dev has a Dev number. (See also: Dev number) Dev number A Dev number (the DNum column) in the configuration list in HDLM. 0 is displayed as the number indicating the entire LU.
FC-SAN (Fibre Channel - Storage Area Network) A SAN using Fibre Channel. H HAM environment An environment in which volume pairs that are synchronized between two storage systems are created by HAM (High Availability Manager), and hosts are configured to recognize these volumes as one volume. An HAM environment consists of the primary volume (P-VOL) in the primary site and the secondary volume (S-VOL) in the secondary site.
host LU number A number assigned to a host LU. The host LU number is part of a path name. (See also: host LU, path name) I intermittent error An error that occurs irregularly due to, for example, a loose cable connection. IP-SAN (Internet Protocol - Storage Area Network) A data transfer network that connects hosts and storage systems by using the iSCSI standard. L LDEV (Logical Device) A combination of the storage system's product name, serial number, and an internal LU.
Non-owner controllers exist only in the Thunder 9500V series, or Hitachi AMS/WMS series. (See also: owner controller, non-owner path) non-owner path A path that passes through a non-owner controller. Non-owner paths exist only in the Thunder 9500V series, or Hitachi AMS/WMS series. (See also: owner path, non-owner controller) O owner controller A controller that has been set as an owner controller for an LU. Owner controllers are only in the Thunder 9500V series, or Hitachi AMS/WMS series.
path name The path name consisting of the following four elements, separated by periods: - Host port number (hexadecimal number) - Bus number (hexadecimal number) - Target ID (hexadecimal number) - Host LU number (hexadecimal number) A path name is used to identify a path. (See also: host LU number) persistent reservation Similar to reservations, persistent reservations enable a server to declare that it has exclusive rights to use an LU, and prevents other servers from accessing that LU.
SLPR (Storage Logical Partition) A function supported by Hitachi USP series, Universal Storage Platform V/VM series, and Virtual Storage Platform series for logically splitting up a storage system. This function splits up the resources, such as ports, CLPR, and volumes, in the storage system, so that the user can manage each resource independently.
# A B C D E F G H I J K L M N O P Q R S T Glossary-8 Hitachi Dynamic Link Manager User Guide for Windows® U V W X Y Z
Index A buffer size 3-81 bus number 6-55 command format 6-2 overview 6-2 command device 2-3, 6-57 HDLM command (dlnkmgr) delete 6-72 command of HDLM (dlnkmgr) clear 6-3 help 6-4 offline 6-6 online 6-11 set 6-16 view 6-32 configuration of HDLM system configuration of HDLM system using FC-SAN 2-4 core logic component 2-10 Critical 2-36 C D CHA 2-4, 2-6 CHA (Channel Adapter) Glossary-1 channel adapter 2-3, 2-5 checking path information using Windows administrative tool (Performance) 4-13 clear 6-3 CLPR(Ca
summary of path information 6-33 Distributing a Load Using Load Balancing dlmchkpath 7-14 DLMgetras 5-7, 5-8, 7-2 dlmhostinfo 7-15 dlmpr 7-10 dlmprsvkey 7-12 dlnkmgr 6-1 DNum 5-3 2-11 driver level HDLM and MPIO drivers 2-10 dynamic I/O path control 3-75 dynamic reconfiguration Glossary-2 E EMC CX series cluster software 3-7 EMC DMX series cluster software 3-7 dlnkmgr view -lu -c 6-63 EMC DMX series and CX series dlnkmgr view -lu 6-58 dlnkmgr view -path -c 6-48 EMC DMX series, CX series, and HP EVA series
narrowing down 5-6 HBA 2-4 notes on HBA and HBA drivers 3-15 HBA (Host Bus Adapter) Glossary-3 HDev 2-8 HDevName 5-3 HDLM features 1-2 functions 2-1 installing 3-25 new installation (on Windows Server 2003) 3-29 new installation (on Windows Server 2008 and Windows Server 2012) 3-52 notes on versions 3-15 overview 1-1 program information 6-34 removal 3-84 setup 3-70 HDLM alert driver 2-10, Glossary-3 HDLM command 2-9 HDLM Core components 2-10 HDLM driver 2-10, Glossary-3 driver level 2-10 HDLM environment cr
log collection level values 6-19 logical unit 2-3, 2-5 logical unit ID 6-55 logs HDLM output to Windows event logs LU 2-4, 2-6, 4-16 configuration 2-7 LU (Logical Unit) Glossary-4 LU configuration recognized by the host LUN 6-55 8-116 2-8 M manual path switching 2-19 message examining 5-7 format and meaning of ID 8-3 terms that appear 8-3 terms used for explanation 8-3 message element DNum 5-3 ErrorCode 5-3 PathID 5-3 PathName 5-3 Message level 8-3 Messages 8-1 migrating from HDLM 5.
P P 2-4, 2-6 path 2-3, 2-5, Glossary-5 checking the configuration 3-69 deleting dynamically 6-72 path error handling 5-4 Path Health Checking 2-31 path health checking 1-3, 2-31, 6-21, Glossary-5 path information obtaining 5-5 path name Glossary-6 path status transition 2-20 path status transitions 2-23 path switching automatically 2-17 manually 2-19 PathID 5-3 PathName 5-3 paths to which load balancing is applied 2-13 Performance 4-13 Performance Monitor 4-13 Performing Failovers and Failbacks Using Path S
using Windows administrative tool (Performance) checking path information 4-13 utilities for checking HDLM installation information 7-15 for checking HDLM paths 7-14 for clearing HDLM persistent reservation 7-10 for collecting HDLM error information 7-2 for registering a HDLM persistent reservation key 7-12 for removing HDLM 7-28 installing HDLM 7-17 overview 7-2 utility for removing HDLM 7-28 V VCS 3-7, 3-8, 3-9, 3-88 vendor ID 6-50, 6-54 view 6-32 viewing GUI Help 4-4 W Warning 2-36 what is HDLM? 1-2 wh
Hitachi Dynamic Link Manager User Guide for Windows®
Hitachi Data Systems Corporate Headquarters 2845 Lafayette Street Santa Clara, California 95050-2639 U.S.A. www.hds.com Regional Contact Information Americas +1 408 970 1000 info@hds.com Europe, Middle East, and Africa +44 (0)1753 618000 info.emea@hds.com Asia Pacific +852 3189 7900 hds.marketing.apac@hds.
