HiCommand® Dynamic Link Manager (HDLM) for Windows Systems User’s Guide MK-92DLM129-13
© 2007 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED Notice: 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 Data Systems Corporation. Hitachi Data Systems reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use.
Veritas, and Veritas Storage Foundation are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Windows Server is a registered trademark of Microsoft Corp. in the U.S. and other countries. This product includes software developed by the JDOM Project (http://www.jdom.org/) and the Apache Software Foundation (http://www.apache.org/).
Preface The HiCommand Dynamic Link Manager (HDLM) for Windows Systems User’s Guide describes and provides instructions for installing the HDLM software on a Windows system and using HDLM with the TagmaStore USP, TagmaStore AMS/WMS Series, Hitachi Lightning 9900 V Series, Lightning 9900, and/or Thunder 9200, 5800, or 5700E disk array systems.
Convention for Storage Capacity Values This document uses the following convention for storage capacity values: 1 KB = 1,000 bytes 1 MB = 1,0002 bytes 1 GB = 1,0003 bytes 1 TB = 1,0004 bytes Referenced Documents Hitachi Lightning 9900 V Series User and Reference Guide, MK-92RD100 Hitachi Lightning 9900 V Series Windows NT Configuration Guide, MK-92RD120 Hitachi Lightning 9900 V Series Windows 2000 Configuration Guide, MK-92RD121 Hitachi Lightning 9900 User and Reference Guide, MK-90RD008
Contents Chapter 1 Overview of HDLM..................................................................................................................1 1.1 1.2 1.3 Chapter 2 What is HDLM?..................................................................................... 2 HDLM Features .................................................................................... 4 HDLM GUI Overview .............................................................................. 5 1.3.
2.11 Error Management...............................................................................43 2.11.1 Collected Logs ..........................................................................44 2.11.2 Filtering of Error Information ........................................................46 2.11.3 Collecting Error Information Using the DLMgetras Utility........................47 2.12 Cluster Support ..................................................................................
3.5.3 3.6 3.7 3.8 3.9 Chapter 4 Applying the Settings and Closing the Windows ...................................80 3.5.3.1 Closing the Options Window When Using HDLM GUI ...................80 3.5.3.2 Checking New Settings Using the dlnkmgr Command .................80 Installing HDLM ..................................................................................81 3.6.1 Preparations for a New Installation of HDLM ......................................81 3.6.
4.2.4 4.3 4.4 4.5 4.6 Chapter 5 Troubleshooting .................................................................................................................161 5.1 5.2 5.3 x Exporting Path Information to a CSV File......................................... 130 4.2.4.1 Notes on Exporting Path Information to a CSV File from the Host 130 4.2.4.2 Exporting Path Information to a CSV File ............................. 131 4.2.5 Setting Path Statistics to Initial Value ..................................
5.3.2 5.4 5.5 Chapter 6 GUI Reference.....................................................................................................................177 6.1 6.2 6.3 Chapter 7 Using the dlnkmgr Command to Handle a Path Error........................... 169 5.3.2.1 Examine the Messages .................................................... 169 5.3.2.2 Obtain Path Information ................................................. 169 5.3.2.3 Identify the Error Path ........................................
7.7.1 7.7.2 Chapter 8 Utility Reference .................................................................................................................269 8.1 8.2 8.3 8.4 8.5 Chapter 9 Overview of the Utilities ..................................................................... 270 The DLMgetras Utility for Collecting HDLM Error Information.......................... 271 8.2.1 Format ................................................................................. 271 8.2.1.
9.15 Messages from the dlmchkpath Utility for Checking HDLM Paths...................... 366 9.16 Return Codes for the HDLM Remote Access Interface ................................... 368 Appendix A Functionality Differences Between HDLM Versions........................................................373 A.1 A.2 A.3 A.2 A.3 A.4 A.5 Functionality differences between version 5.9.1 and versions earlier than 5.9.1 .. 373 Functionality differences between version 5.9 and versions earlier than 5.9 .......
List of Figures Figure 1.1 Figure 1.2 Figure 1.3 Connections Between Hosts and Storage Systems .................................... 2 Path Management Window................................................................ 5 Options Window ............................................................................ 7 Figure 2.1 Figure 2.2 Figure 2.3 Figure 2.4 Figure 2.5 Figure 2.6 Figure 2.7 Figure 2.8 Figure 2.9 Figure 2.10 Figure 2.11 Figure 2.12 Figure 2.13 Figure 2.14 Figure 2.15 Figure 2.
List of Tables Table 2.1 Table 2.2 Table 2.3 Table 2.4 Table 2.5 Table 2.6 Table 2.7 Table 2.8 Table 2.9 HDLM System Components Using FC-SAN ..............................................12 HDLM System Components that use IP-SAN ...........................................14 Components Recognized by Host .......................................................16 HDLM Program Functionality ............................................................18 Algorithms for Load Balancing ............................
Table 7.3 Table 7.4 Table 7.5 Table 7.15 Error Log Collection Level Values..................................................... 226 Trace Level Values ...................................................................... 227 Relationship Between Setting Status for Automatic Failback and Intermittent Error Monitoring and Executable Operations ....................................... 231 License Key Types.......................................................................
Chapter 1 Overview of HDLM This chapter provides an overview of HDLM and describes its features. The overview is broken down into the following sections: What is HDLM? (see section 1.1) HDLM features (see section 1.2) HDLM GUI Overview (see section 1.
1.1 What is HDLM? The widespread use of data warehousing and increasing use of multimedia data have increased the need for high-speed processing of large volumes of data on networks. To satisfy this need, networks dedicated to data transfer, such as a SAN, are now being used to provide access to storage systems. The HDLM software manages access paths to storage systems.
EMC CX series HP EVA series HiCommand® Dynamic Link Manager (HDLM) for Windows® Systems User’s Guide 3
1.2 HDLM Features HDLM provides the following features: Distributes the load across paths (load balancing) When multiple paths connect a host and storage system, HDLM distributes the load across the paths. This prevents a heavily loaded path from affecting processing speed. For details on load balancing, see section 2.6.
1.3 HDLM GUI Overview HDLM GUI has the following windows: 1.3.1 Path Management window Options window Help window About the Path Management Window Use the Path Management window to view path information and change path status. Figure 1.2 shows the Path Management window. Figure 1.
The Path Management window consists of three frames shown in Figure 1.2: Common frame Displays the title, logo, and buttons that are used throughout the HDLM GUI. Tree frame Displays in tree format the storage systems and LUs that are managed by the host. View frame Displays the path configuration view or path list view.
1.3.2 About the Options Window Use the Options window to view or change an HDLM operating environment. Figure 1.3 shows the Options window. Figure 1.3 1.3.3 Options Window About the Help Window Use the Help window to view the HTML version of this manual.
8 Chapter 1 Overview of HDLM
Chapter 2 HDLM Functions This chapter describes HDLM functionality including HDLM management targets, system configuration, basic terms and functionality including load distribution across paths and path switching. HDLM functionality is discussed in the following sections: Devices managed by HDLM (see section 2.1) System configuration (see section 2.2) LU configuration (see section 2.3) Program configuration (see section 2.4) HDLM and MPIO driver position (see section 2.
2.1 Devices Managed by HDLM Devices that can and cannot be managed by HDLM are shown below. The devices that can be managed by HDLM are called HDLM management-target devices.
2.2 System Configuration HDLM is available in two SAN environment types: FC-SAN and IP-SAN. However, a single host can connect to either the FC-SAN or IP-SAN. Note that the EMC DMX series, EMC CX series, and HP EVA series is available only in an FC-SAN environment. 2.2.1 System Configuration Using an FC-SAN In an FC-SAN, fiber cables connect hosts and storage systems. The cable port on the host is a host bus adapter (HBA). The cable port on the storage system is a port (P) on a channel adapter (CHA).
Table 2.1 2.2.2 HDLM System Components Using 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 data transfer between hosts and storage systems. CHA A channel adapter. P A port on a channel adapter. This serves as a cable port on a storage system. LU A logical unit with which the host can perform input or output operations. This unit can be accessed from the network.
Figure 2.2 IP-SAN System Configuration Using iSCSI HBA Figure 2.3 IP-SAN System Configuration Using iSCSI Software and NIC Table 2.2 lists the HDLM system components that use the IP-SAN.
Table 2.2 HDLM System Components that use IP-SAN Components Description iSCSI software The driver software that has the iSCSI initiator function. iSCSI HBA A host bus adapter that has the iSCSI initiator function. This serves as a cable port on the host. The iSCSI HBA is referred to as the HBA in HDLM commands and HDLM GUI. It is sometimes called an HBA in this manual. 2.2.2.1 NIC A network interface card that serves as a cable port on a host.
2.3 LU Configuration When you install HDLM, the LU configuration recognized by the host changes as follows: Before installing HDLM: In the disk management window of the host, a SCSI device is displayed for each path. This means a single LU in the storage system is recognized as the number of LUs that correspond to the number of paths. After installing HDLM: The MPIO driver integrates the LUs that are recognized for each path.
Table 2.3 lists the components recognized by the host. Table 2.3 16 Components Recognized by Host Components Description HLU An LU that the host recognizes via the HDLM driver. It is called a host LU. Regardless of how many paths exist, only one host LU is recognized for the LU in the storage system. HDev A Dev in an LU that the host recognizes via the HDLM driver. It is called a host device.
2.4 Program Configuration HDLM runs as a combination of programs. Because these programs correspond to the HDLM operations, you need to understand the name, position, and role of each program. Figure 2.5 shows the HDLM program configuration. Figure 2.
Table 2.4 lists and describes the functionality of these programs. Table 2.
2.5 HDLM and MPIO Driver Position The HDLM and MPIO drivers are positioned above the SCSI driver. Applications on a host access LUs in storage systems through the HDLM and MPIO drivers. Figure 2.6 shows the positions of the HDLM and MPIO drivers. Figure 2.
2.6 Load Distribution using Load Balancing When the system contains multiple paths to an LU, HDLM can distribute the load across the paths by using multiple paths for I/O. This functionality is called load balancing, and it prevents a heavily loaded path from affecting the performance of the entire system. Note that some I/O operations managed by HDLM can be distributed to each path, while others cannot.
Figure 2.7 I/O Flow When Load Balancing is Not Used When the load balancing function is not being used, I/O operations converge on one path (A). The load on the path (A) will cause a bottleneck, which might cause deterioration of the whole system's performance.
Figure 2.8 I/O Flow When Load Balancing is Used When the load balancing function is being used, I/O operations are distributed via paths (A), (B), (C), and (D). This prevents deterioration of the whole system's performance from a bottleneck on one path.
2.6.1 Paths to Which Load Balancing is Applied This section explains the mechanism of load balancing. The explanation uses the example shown in Figure 2.9. Figure 2.9 Overview of Load Balancing This subsection describes, for each storage system, the paths to which the load balancing function is applied.
2.6.1.1 Using TagmaStore AMS/WMS Series, Thunder 9500V Series, or Thunder 9200 Series HDLM performs load balancing between owner paths or between non-owner paths. An owner path is a path that passes through the channel adapter. This path is set on the owner controller of the storage system LU. When you set an LU, you determine the owner controller and non-owner controller for the LU. Since the owner controller varies depending on the LU, the owner path also varies depending on the LU.
Table 2.5 Algorithms for Load Balancing Algorithm For Sequential Access For Random Access Round robin After an I/O operation is issued to a path once or a certain number of times, the path is switched to the next path. The storage system cache might not be fully usable. When multiple applications that request sequential access are run concurrently, we recommend that you use the round robin algorithm to distribute I/Os across multiple paths.
You can specify the load balancing function from the Options window of the HDLM GUI or by the dlnkmgr command's set operation. For details on how to use the window components, see section 4.2.8 or 6.3. For details on the set operation, see section 7.6. Note: Some I/O operations managed by HDLM can be distributed across all paths, and some cannot. Thus, you should be aware that even when you use the load balancing function, I/O operations cannot always be allocated uniformly across all paths.
2.7 Failover and Failback Using Path Switching When the system contains multiple paths to an LU and an error occurs in the path being used, HDLM can switch to another normal path to allow the system to continue to operate. This functionality is called failover. When the path in which an error occurred recovers from the error, HDLM can switch the paths so that the recovered path is used. This functionality is called failback.
When TagmaStore AMS/WMS series, Thunder 9500V Series, or Thunder 9200 are being used, HDLM selects the switching destination from the paths that access the same LU, in the order of owner paths and non-owner paths. For example, in Figure 2.10, the owner controller of LU is CHA0, and access to the LU is made only via the path (A). After the access path is placed offline, the first candidate for the switching destination is the path (B) and the second candidate is the path (C) or (D).
2.7.1.2 Automatic Failback After a path recovers from an error, HDLM can automatically place the recovered path online. This functionality is called automatic failback. When using this function, HDLM monitors error recovery on a regular basis. When using the TagmaStore AMS/WMS series, Thunder 9500V Series, or Thunder 9200, HDLM selects the path to use from online owner paths, and then from online non-owner paths.
2.7.2 Manual Path Switching You can switch a path by manually placing a path online or offline. Manually switching a path temporarily is useful for maintenance of the system. You can manually place a path online or offline in the following ways: Use the Path Management window of the HDLM GUI. Execute the dlnkmgr command's online or offline operation. For details on the online operation, see section 7.5. For details on the offline operation, see section 7.4.
2.7.3 Path Status Transition This section explains the online and offline path statuses described in section 2.7. There are four types of online status, and three types of offline status. A description of each type of status is provided below. In the descriptions, an offline operation refers to performing an offline operation using the Path Management window in HDLM GUI or by executing the dlnkmgr command's offline operation. For details on the offline operation, see section 7.4. 2.7.3.
The Offline(P) path changes to Online(EP). If the reserve processing finishes after the path has changed from Online(EP) to Offline(P), the offline operation ends successfully and the path changes to Offline(C). If the reserve processing finishes while the path is Online(EP), the offline operation fails and the path changes to Online(E). 2.7.3.2 The Offline Path Status The offline path statuses are as follow: – Offline(C) The path is offline because an offline operation was performed.
2.7.3.3 Status Transitions of a Path Figure 2.11 shows the status transitions of a path. 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 reservation processing for an LU, the Online status is temporarily changed to Online(P).
#4: When the following conditions are 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 reservation processing for an LU, the Offline(E) status is temporarily changed to Offline(P).
Note: If there is a path failure immediately after a path is made offline by using an HDLM command or HDLM GUI, Offline(C) might change to Offline(E). If an offline operation was performed, wait for a fixed period of time (about 2 minutes), check the path status by using an HDLM command or HDLM GUI, and make sure that the status has changed to Offline(C). If it is Offline(E), retry the offline operation.
2.8 Monitoring Intermittent Errors An intermittent error means an error that occurs irregularly because of some reason such as a loose cable connection. I/O performance might decrease when an intermittent error occurs while automatic failback is used, because automatic failback is performed repeatedly. To prevent this phenomenon, HDLM can automatically remove the path where an intermittent error is occurring from those paths subject to automatic failback.
2.8.3.1 When an intermittent error occurs. When an intermittent error does not occurs. When the conditions for the intermittent error are changed during error monitoring. When an Intermittent Error Occurs When an error occurs in a path the specified number of times within the specified interval, the error monitoring finishes, the path is determined to have an intermittent error, and then the path is removed from those items subject to automatic failback.
Figure 2.13 shows the action for intermittent error monitoring when an intermittent error does not occur. In this example, the path is determined to have an intermittent error if the error occurs three or more times in 30 minutes. The event occurring in one path is described on the time arrow. Figure 2.13 Action When an Intermittent Error does not Occur in the Path The number of times that the error is to occur is counted when an error occurs. As shown in Figure 2.
Figure 2.14 Action Conditions for Intermittent Error Change during Error Monitoring 2.8.
User Operation Number of Errors and Time Passed since Error Monitoring Started Information about Paths not Subject to Automatic Failback Changing the setting for intermittent error monitoring to outside the intermittent error monitoring. (Not applicable) (Not counted.
2.9 Detecting Errors Using Path Health Checking HDLM can check the status of paths at regular intervals, and detect errors. This functionality is called path health checking. Without path health checking, an error is not detected unless I/O is performed because the system only checks the path status when I/O is performed. With path health checking, however, the system checks the status of online paths at regular intervals regardless of whether I/O is performed.
2.10 Dynamic Reconfiguration Using the Windows plug-and-play functionality, you can add an LU and a path when the host installing HDLM is running, which is called dynamic reconfiguration functionality. For details on the dynamic reconfiguration, see section 4.6.1. 2.10.1 Adding an LU Dynamically The LU dynamic addition functionality enables you to add an LU and a path when the host installing HDLM is running. For details on the LU dynamic addition functionality, see section 4.6.1. 2.10.
2.11 Error Management For troubleshooting, HDLM collects information into log files. The error information can be filtered according to the error level, and collected into the log files. Figure 2.15 shows the data flow when collecting error information. Figure 2.15 Data Flow when Collecting Error Information Logs might be collected in layers lower than HDLM, such as for the SCSI driver. For details on the logs, see the Windows documentation.
2.11.1 Collected Logs HDLM collects information on the detected error and trace information in 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. The information about the Windows system-down is output to a system memory dump file. A system memory dump file is a file to which the system memory data is output when Windows system-down occurs.
Log Name Description Output Destination 2The underlined part indicates the folder specified during installation. When obtaining these files, make sure that you copy them to other files. For details on error levels, see section 2.11.2. Note: To collect logs, HDLM uses the Hitachi Network Objectplaza Trace Library service. If this service is not active, start it as follows: In Control Panel, choose Administrative Tools and then Services to open the Services window.
2.11.2 Filtering of Error Information Errors that HDLM detects are classified into error levels. Table 2.8 lists the error levels, in order of adverse effect on the system. Table 2.8 Error Levels Error Level Meaning Level Shown in Event Viewer Critical Fatal errors that may stop the system. Error Error Errors that crucially affect the system. This type of error can be avoided by using failover or other countermeasures.
2.11.3 Collecting Error Information Using the DLMgetras Utility HDLM has a utility for collecting HDLM error information (DLMgetras). By executing this utility, you can simultaneously collect all the information required for analyzing errors: information such as error logs, integrated trace files, trace files, definition files, and the operation system. You can use the collected information when you contact your HDLM vendor or maintenance company (if there is a maintenance contract for HDLM).
2.12 Cluster Support HDLM is also available for cluster configurations. Table 2.9 lists the cluster software supported by HDLM. Table 2.9 Cluster Software Supported by HDLM Operating System Cluster Software Thunder 9200/9500V Series, Lightning 9900/9900V Series, TagmaStore, and Universal Storage Platform V EMC DMX Series EMC CX Series* HP EVA Series* Windows 2000 MSCS X -- -- -- Oracle 9i RAC version 9.2.0.1.0 X -- -- -- Oracle RAC 10g version 10.1.0.2.
Figure 2.16 Path Switching in a Cluster Configuration Note When you use HDLM in a cluster configuration, you must install the same version of HDLM on all the nodes that comprise the cluster. If different versions of HDLM are installed, the cluster system may not operate correctly.
50 Chapter 2 HDLM Functions
Chapter 3 Creating an HDLM Environment This chapter explains the procedure for setting up an HDLM environment and canceling environment settings. The chapter is comprised of the following sections: System requirements (see section 3.1) Flow for creating an HDLM environment (see section 3.2) HDLM installation types (see section 3.3) Notes on creating an HDLM environment (see section 3.4) Setting up HDLM (see section 3.5) Installing HDLM (see section 3.
3.1 System Requirements Check the following before installing HDLM: 3.1.1 3.1.1.1 Applicable Models Applicable Hosts You can install HDLM on a host that is running an operating system described in Table 3.1. Table 3.
Table 3.
3.1.2 Microsoft MPIO Drivers Table 3.3 lists and describes versions of the Microsoft MPIO driver bundled with HDLM. Table 3.3 3.1.3 Versions of Microsoft MPIO Driver Bundled with HDLM Driver Description File version mpdev.sys Multipath Scsi Device Filter 1.17.3790.1759 mpio.sys Multipath Support Bus-Driver 1.17.3790.1759 mpspfltr.sys Multipath Scsi Filter 1.17.3790.1759 Related Programs This section describes the programs related to HDLM. 3.1.3.
3.1.3.3 Exchanging Data Using Intermediate Volumes Managed by Hitachi RapidXchange Table 3.5 lists related programs when exchanging data by using intermediate volumes managed by Hitachi RapidXchange. For details about Hitachi RapidXchange, see the manual Reference Manual / File Conversion Utility & File Access Library. Table 3.
3.1.4.2 Disk Requirements This section describes disk space requirements for a host. Table 3.7 lists the disk space requirements for a host. Table 3.7 Disk Space Requirements for a Host Folder Disk Space Requirements HDLM-installation-folder When you do not use the HDLM GUI: 110MB + pMB1 + qMB2 + 1MB When you do use the HDLM GUI: 110MB + 20MB + pMB1 + qMB2 + 1MB 1This size depends on the settings for the log files. The maximum size is 30000MB.
3.2 Flow for Creating an HDLM Environment Set up the environment to use HDLM as follows. Figure 3.
3.3 HDLM Installation Types This subsection describes the following types of HDLM installation: new installation, upgrade installation, and re-installation. New installation of HDLM: Installing HDLM in a server on which HDLM has not been installed is called a new installation of HDLM. Upgrade installation of HDLM: Installing a newer version than the existing version without uninstalling the existing version is called an upgrade installation of HDLM. You can perform upgrade installation only for HDLM 5.
3.4 Notes on Creating an HDLM Environment When you are building an HDLM environment, note the points listed below. 3.4.1 Notes on HBAs and HBA Drivers When using the Storport Miniport driver as an HBA driver in Windows Server 2003, install QFE 838894 or later for the Microsoft Storport driver install or Windows Server 2003 SP1 or later, before installing HDLM.
3.4.3 For a configuration in which the host and the storage system are connected by using a Fibre Channel switch, select Point To Point as the connection type. If you select FC-AL (Fibre Channel Arbitrated Loop) as the connection type, an unexpected path error may be detected. Windows can recognize LUNs from 0 to 255. Therefore, set LUNs in the range from 0 to 255 in the storage system management software. Notes on HDLM Versions If HDLM 5.
Before installing or upgrading HDLM 5.5 or later, make sure that no other application is using an HDLM management-target LU. When HDLM 5.5 or later is installed for the first time, the event described below occurs and is output to the event log. However, it does not affect the system or HDLM operations. Description Event provider attempted to register query "select * from WMIEvent" whose target class "WMIEvent" does not exist. The query will be ignored.
HDLM-installation-folder\lib For Windows Server 2003 SP1 and Windows Server 2003 R2 (no service pack), if you do not want to use one of the above methods, you can use a Microsoft hotfix to start HDLM Manager.For details about how to obtain and use the hotfix and how it affects the system, contact Microsoft. Before installing HDLM, enable the setting for automatically shortening file and folder names (8.3 format).
In Windows Server 2003 (x64), do not create the data stored in the GUID Partition Table (GPT). When installing HDLM, The name of the HDLM installation folder and the names of all its parent folders must fulfill all of the following conditions: – The name must not be a reserved name specified in the operating system. Reserved names specified in the operating system include, for example, CON, AUX, COM1 to COM9, LPT1 to LPT9, PRN, and NUL.
In the above configuration, we recommend that you change MISSCOUNT, which is the I/O timeout threshold value for a voting disk, to the following value: (greatest-numberof-paths-connected-to-the-voting-disk x 60 seconds). If an I/O timeout occurs between a host and a voting disk in the above conditions, Oracle RAC 10g might regard it as the I/O timeout before the HDLM failover function checks all the paths.
– When HDLM for another operating system has not been installed: a. Perform the installation again according to the following procedure: In Explorer, in the Tools menu choose Folder Options. The Folder Options window is displayed. b. Click the View tab, and in the Advanced settings field, under Hidden files and folders, select Show hidden files and folders. c.
3.5 Setting up HDLM HDLM has load balancing, automatic failback, error logging, and other functions. You can set up these functions by using the Options window of the HDLM GUI or by using the dlnkmgr command's set operation. The following subsections describe these setup methods. 3.5.
Figure 3.
3.5.1.2 Checking Current Settings Using the dlnkmgr Command Check the current settings by executing the following command to set the HDLM functionality by using the dlnkmgr command's set operation.
3.5.2 Setting HDLM Functionality The recommended and default values for the HDLM functionalities are shown below in Table 3.10. Table 3.10 Recommended and Default Values for Each Function Functionality Default Value Recommended Value Load-balancing ON ON Algorithm is round robin The recommended algorithm depends on the operating environment. Path health checking ON ON 30-minute check interval The recommended checking interval depends on the operating environment.
3.5.2.1 Setting Load Balancing You can select whether to enable load balancing. In a cluster environment, the load balancing function is only available for TagmaStore, Thunder 9200/9500V Series, and Lightning 9900/9900V Series, TagmaStore, and Universal Storage Platform V. In a non-cluster environment, the load balancing function is available for TagmaStore, Thunder 9200/9500V Series, Lightning 9900/9900V Series, Universal Storage Platform V, and the EMC DMX series.
3.5.2.3 Setting Automatic Failback You can select whether to enable automatic failback.
3.5.2.4 Settings for Intermittent Error Monitoring Intermittent error monitoring is specifiable only when automatic failback is enabled. To prevent an intermittent error from reducing I/O performance, we recommend that you monitor intermittent errors when automatic failback is enabled. When intermittent error monitoring is enabled, you can specify intermittent error conditions (the conditions used by the system to determine whether an intermittent error is occurring).
3.5.2.5 Setting the Reservation Level You cannot set the reservation level (reservation control method for the LU). 3.5.2.6 Setting the LU Deletion Functionality You can select whether to enable the LU dynamic removal function. For details on the LU deletion functionality, see section 4.6.2. Table 3.11 shows the values for the LU deletion functionality. Table 3.
3.5.2.7 Setting Error Log Collection Level The error log collection level can be set. 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). Table 3.12 lists and describes values for the error log collection level setting. Table 3.12 Error Log Collection Level Setting Values Value* Description 0: Do not collect an error log No error logs are collected.
3.5.2.8 Setting the Trace Level The trace output level can be set. A trace file in which a trace level can be set is hdlmtrn.log (n indicates a file number from 1 to 64). Table 3.13 lists and describes values for the trace level setting. Table 3.13 Trace Level Setting Values Value* Description 0: Do not output any trace No trace is output. 1: Error information only Only error information is output. 2: Summary of program operation Program operation summaries are output.
3.5.2.9 Setting 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, the valid range of a file size is from 100 to 9900. If you specify a value of 9901 or more, 9900 is applied. The specified value is applied for HDLM manager logs.
3.5.2.10 Setting the Number of Error Log Files The number of the error log files can be set. 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). The error logs you can set in the Options window and the set operation are limited to the HDLM manager logs file dlmmgrn.log (n indicates a file number from 1 to 16). The number of files for the HDLM GUI log file dlmguin.
3.5.2.11 Setting the Trace File Size The trace file size can be set. Trace files for which a trace file size can be set are hdlmtrn.log (n indicates a file number from 1 to 64). The length of a trace file is fixed. Thus, even if the amount of written trace information is less than the set file size, the file size of each output trace file is always fixed. For the trace file size, you can specify a value (in kilobytes) from 100 to 16000.
3.5.2.12 Setting the Number of Trace Files You can set the number of trace files. Trace files for which the number of files can be set are hdlmtrn.log (n indicates a file number from 1 to 64). For the number of trace files, you can specify a value from 2 to 64. If you specify a value smaller than the setting value, the message (KAPL02080-W for the Options window and KAPL01097-W for the set operation) is displayed to confirm execution, and the trace file is temporarily deleted.
3.5.3 Applying the Settings and Closing the Windows This section describes steps involved in closing the Options window of the HDLM GUI and how to check the new settings by using the dlnkmgr command's set operation after the new settings are applied. 3.5.3.1 Closing the Options Window When Using HDLM GUI When using the HDLM GUI, follow these steps to close the Options window: 1. Click the OK button. The settings are applied and then the Options window is closed. 2.
3.6 Installing HDLM Before installing, check whether HDLM has been installed on the installation-target host. When HDLM has been installed on the host, you can upgrade HDLM by performing an update installation as described in section 3.6.4 or 3.6.5. When you install HDLM, Hitachi Network Objectplaza Trace Library will also be installed.
2. To set up the storage system, assign an LU to each port. Change the settings of the storage system according to the hardware notes supplied with HDLM. 3. Install the HBAs onto the host. In a cluster configuration, make sure that the manufacturer and model of the HBA is the same for all the hosts that make up the cluster. Also make sure that the versions of the HBA micro-programs are the same. 4. Set up the switches. For details on how to set up a switch, see the documentation for the switch.
3.6.2 Preparations for installing HDLM by performing an unattended installation An unattended installation allows a user to install HDLM without needing to enter information into dialog boxes. Instead, the user defines the required dialog box information in an installation-information settings file prior to installation. The unattended installation procedure is as follows: 1. Define the information required for the installation in the installation-information settings file. 2. Execute installhdlm.
Table 3.14 Keys in an installation-information settings file (installhdml.ini) Key name Description Necessity of definition New installation Upgrade installation Maximum character length#1 workdir Specify an absolute path to an output folder. Installation logs and processing files are output to this folder.#2, #3 If this key is omitted, the installer uses the folder path that has been specified for the environment variable TMP or TEMP.
Not required: Specification is unnecessary. If a value is specified for the key, the installer ignores the specified value. #1 If the length of the value exceeds the maximum length, an error will occur. #2 If the value is not of an allowable type, an error will occur. #3 The value to be specified does not have to be enclosed within double quotation marks ("), even if the value includes space characters.
3.6.2.4 Notes on installation 3.6.3 3.6.3.1 Do not forcibly stop the execution of installhdlm.exe during an unattended installation of HDLM. If you forcibly stop the execution of installhdlm.exe (for example, if you press Ctrl + C), HDLM installation will not be stopped. If you have specified y for the restart key in the installation-information settings file, the computer will restart when the installation finishes successfully.
If you have specified n (do not restart) for the restart key in the installationinformation settings file, go to step 12. If you have specified y (restart) for the restart key in the installation-information settings file, go to step 17. 4. The program checks the version of the MPIO driver, and then installs the MPIO driver.
8. The utility for registering HDLM persistent reservation keys (dlmprsvkey) is automatically executed to create a PRSV key. The PRSV key is required for the HDLM functions to operate normally. Also, the value of the PRSV key must be unique among hosts. Creation of the PRSV key may be unsuccessful if, for example, an NIC does not exist.
12. Check the results of the installation. If you performed an unattended installation, check the installation results in the command prompt. 13. When the installation finishes, execute the dlmprsvkey utility with the -v parameter specified. Make sure that the PRSV key displayed by the dlmprsvkey utility is unique among those of any other hosts in the SAN.
Trace Level : 0 Trace File Size(KB) : 1000 Number Of Trace Files : 4 Path Health Checking : on(30) Auto Failback : off Remove LU : off Intermittent Error Monitor : off HDLM Manager Ver WakeupTime Alive xx-xx yyyy/mm/dd hh:mm:ss HDLM Alert Driver Ver WakeupTime Alive xx-xx HDLM Driver Ver Alive xx-xx ElogMem Size yyyy/mm/dd hh:mm:ss 128 WakeupTime yyyy/mm/dd hh:mm:ss License Type Expiration Permanent KAPL01001-I The HDLM command completed normally.
3.6.3.2 Performing a New Installation Using MSCS The following provides separate explanations of the procedures for when installing MSCS after HDLM installation, and for when installing HDLM after MSCS installation. Installing MSCS After HDLM Installation 1. Shut down all the hosts. 2. Make sure that all the hosts comprising the cluster system have been fully shut down. 3. Start the hosts individually in the single path configuration. 4. Log on to Windows as a member of the administrators group. 5.
– – Click the Cancel button to cancel the installation. If no message appears, go to the next step. 8. Specify a license key file or enter a license key in accordance with the instructions shown in the messages that appear on the window. If a license key file was stored in step 5, specify that license key file. If a license key file is not used, specify the license key directly. 9. Enter user information in accordance with the instructions shown in the messages that appear on the window. 10.
– If a dialog box that begins with the following sentence appears during installation, and the Storport Miniport driver is used as the HBA driver, stop the HDLM installation. Then, install QFE838894 or a later version of the Microsoft Storport driver, or install Windows Server 2003 SP1or 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 Storport driver) is n.n.nnnn.n.
Number Of Trace Files : 4 Path Health Checking : on(30) Auto Failback : off Remove LU : off Intermittent Error Monitor : off HDLM Manager Ver WakeupTime Alive xx-xx yyyy/mm/dd hh:mm:ss HDLM Alert Driver Ver WakeupTime ElogMem Size Alive xx-xx yyyy/mm/dd hh:mm:ss 128 HDLM Driver Ver WakeupTime Alive xx-xx yyyy/mm/dd hh:mm:ss License Type Expiration Permanent KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss 23.
Trace File Size(KB) : 1000 Number Of Trace Files : 4 Path Health Checking : on(30) Auto Failback : off Remove LU : off Intermittent Error Monitor : off HDLM Manager Ver WakeupTime Alive xx-xx yyyy/mm/dd hh:mm:ss HDLM Alert Driver Ver WakeupTime ElogMem Size Alive xx-xx yyyy/mm/dd hh:mm:ss 128 HDLM Driver Ver WakeupTime Alive xx-xx yyyy/mm/dd hh:mm:ss License Type Expiration Permanent KAPL01001-I The HDLM command completed normally.
6. The program checks the version of the MPIO driver, and then installs the MPIO driver. If a message appears asking you whether you want to install MPIO driver, follow the procedure below: – – The KAPL09127-W message appears if MPIO driver has already been installed and its version does not match the version of MPIO driver to be installed: – Click the Next button to install MPIO driver. – Click the Cancel button to cancel the installation. If no message appears, go to the next step. 7.
13. Follow the instructions shown in the messages that appear in the window. – If a dialog box that begins with the following sentence appears during installation, and the Storport Miniport driver is used as the HBA driver, stop the HDLM installation. Then, install QFE838894 or a later version of the Microsoft Storport driver, or install Windows Server 2003 SP1. Notes on using a Storport Miniport driver: Read these notes before using a Storport Miniport driver as an HBA driver.
22. Make sure that the program is working normally, by examining the results of the command's view operation. Make sure that on MSCS is displayed in Support Cluster.
3.6.3.3 Performing a New Installation Using VCS 1. Start the hosts individually in the single path configuration. 2. Use the VCS Configuration Wizard to configure Cluster Components. 3. Restart the host. 4. Log on to the Windows system as a member of the administrators group. 5. Stop VCS. 6. Store the license key file directly under the Windows installation-destination drive. You can also specify the license key directly without using the license key file.
9. Specify a license key file or enter a license key in accordance with the instructions shown in the messages that appear on the window. If a license key file was stored in step 6, specify that license key file. If a license key file is not used, specify the license key directly. 10. Enter user information in accordance with the instructions shown in the messages that appear on the window. 11.
Please update the Storport Miniport driver to a Storport.sys with a file version n.n.nnnn.n or later. – The PRSV key is registered before the installation finishes. If the KAPL09131-W message appears, follow the procedure described in step 17. 16. Check the results of the installation. If you performed an unattended installation, check the installation results in the command prompt. 17. When the installation finishes, execute the dlmprsvkey utility with the -v parameter specified.
An example of executing the dlnkmgr command's view operation is as follows: >dlnkmgr view -sys HDLM Version : xx-xx Service Pack Version : Load Balance : on(rr) Support Cluster : off Elog Level : 3 Elog File Size (KB) : 9900 Number Of Elog Files : 2 Trace Level : 0 Trace File Size(KB) : 1000 Number Of Trace Files : 4 Path Health Checking : on(30) Auto Failback : off Remove LU : off Intermittent Error Monitor : off HDLM Manager Ver WakeupTime Alive xx-xx yyyy/mm/dd hh:mm:ss HDLM Alert Driver Ver WakeupTime E
3.6.3.4 Performing a New Installation Using Oracle RAC 1. Shut down all the hosts. 2. Make sure that all the hosts comprising the cluster system have been fully shut down. 3. Start the host individually in the single path configuration. 4. Log on to Windows as a member of the administrators group. 5. Store the license key file directly under the Windows installation-destination drive. You can also specify the license key directly without using the license key file.
8. Specify a license key file or enter a license key in accordance with the instructions shown in the messages that appear on the window. If a license key file was stored in step 5, specify that license key file. If a license key file is not used, specify the license key directly. 9. Enter user information in accordance with the instructions shown in the messages that appear on the window. 10.
When using a Storport Miniport driver as an HBA driver: Please update the Storport Miniport driver to a Storport.sys with a file version n.n.nnnn.n or later. – The PRSV key is registered before the installation finishes. If the KAPL09131-W message appears, follow the procedure described in step 16. 15. Check the results of the installation. If you performed an unattended installation, check the installation results in the command prompt. 16.
22. Execute the dlnkmgr command's view operation to display the status of each program.
31. Make sure that the program is working normally, by examining the results of the dlnkmgr command's view operation.
This step is omitted. Creating and checking the PRSV key. This step is omitted if an appropriate PRSV key exists. In such a case, it is also unnecessary to check for duplicate PRSV keys after the installation finishes. Upgrade installation or re-installation from HDLM 5.7 or later – Selecting an HDLM management-target device The default of the HDLM management-target device is the same as that before the upgrade installation or re-installation.
3.6.6 Installing JRE To start HDLM GUI, an HDLM uses the JRE that is bundled with the HDLM product (JRE 1.3.1 provided by Sun Microsystems, Inc.). For HDLM version 5.8 or later, a JRE whose version differs from the one bundled with HDLM can be used to start HDLM GUI. (You can use JRE 1.4.2_13 (32 bit), JRE 5.0_05 (32 bit), or JRE 5.0_10 (32 bit), all provided by Sun Microsystems, Inc.
3.7 Checking the Path Configuration HDLM functionality such as load balancing and failover is only available for HDLM management-target devices that have more than one active path. After you install HDLM or change the hardware configuration, check the structure and statuses of these paths. To check the path information, use the dlnkmgr command's view operation or use the Path List view in the Path Management window of the HDLM GUI. The following subsection shows how to check the path information.
3.8 Setting Up Integrated Traces When HDLM is used, dlnkmgr commands and GUI operation logs are output to the integrated trace information files of Hitachi Network Objectplaza Trace Library (HNTRLib2) (installation-destination-drive:\Program Files\HITACHI\HNTRLib2\ spool\Hntr2n.log files (n indicates a file number)). In Windows Server 2003 (IPF and x64), replace Files with Program Files (x86).
To change the integrated trace file settings: 1. In Explorer, double-click the following file: program-installation-destination-drive:\Program Files\HITACHI\HNTRLib2\bin\hntr2utl2.exe The Hitachi Network Objectplaza Trace Utility 2 Release 2.0 dialog box shown in Figure 3.5 appears. 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.
6. In Lookout Span(KB), enter a value to specify the interval for monitoring the number of messages to be output to the integrated trace file. The default is 0 (seconds). You can specify a value from 0 to 3600. If you specify 0, you cannot adjust the number of messages to be output because the system ignores the setting of Max Messages/Span. 7.
3.9 Uninstalling HDLM This section explains how to return the operating environment to the way it was before HDLM was installed. 3.9.1 HDLM Uninstall Preparation Back up the data on the host where HDLM is installed, onto storage media such as tape. Also, if necessary, back up the data on the management target device onto storage media such as tape. 3.9.2 Notes on Uninstalling HDLM Note the following when uninstalling HDLM: Depending on the environment, uninstalling HDLM might take some time.
1. Use the registry editor to determine whether Intel 32 is included in the UninstallString value that is used when uninstalling HDLM. If Intel 32 is included, shortened names are not generated in the Intel 32 folder.
The default installation folder for HDLM is C:\Program Files\HITACHI\DynamicLinkManager. The following subsections describe how to uninstall HDLM in different environments. 3.9.3.1 Uninstallation Procedure for a Non-Cluster Environment To uninstall HDLM in a non-cluster environment: 1. Log on to Windows as a member of the administrators group. 2. Stop all the processes and services that use the HDLM management-target paths.
6. Follow the instructions shown in the messages that appear on the window. If the KAPL09005-E message appears, stop the HDLM manager according to the procedure in section 4.5.2. After stopping the HDLM manager, restart the uninstallation program. 7. When uninstallation finishes, shut down the host. 8. Restart the host. 9. When uninstallation finishes, a dialog box appears prompting you to restart the host. Click the OK button to restart the host. 3.9.3.
Figure 3.7 Single Path and Multi-Path Configurations 5. Start the uninstallation program. In Control Panel, choose Add/Remove Programs, and then Change or Remove Programs. From the list of programs, select Dynamic Link Manager, and click the Change/Remove button. 6. The dlmchkpath utility is automatically executed. If a warning dialog box appears, follow this procedure: – Cancel the uninstallation. Reconfigure the system into a single-path configuration, and then perform the uninstallation again.
3. If a host and a storage system connect via multiple paths, reconfigure it so that one path connects one host to the storage system (single-path configuration). Uninstalling HDLM in a multi-path configuration, which uses more than one path to connect the host to the storage system, may cause disk contents to be incorrect when the host restarts. Make sure that you uninstall HDLM in the single path configuration. Figure 3.7 shows a single path configuration and a multi-path configuration. 4.
3.9.4 Uninstalling Hitachi Network Objectplaza Trace Library (HNTRLib2) When you uninstall HDLM, if the KAPL09019-E or KAPL09020-E message is output, follow these steps below to uninstall HNTRLib2. 1. Log on to Windows as a member of the administrators group. 2. Start the uninstallation program. In Control Panel, choose Add/Remove Programs, and then Change or Remove Programs. From the list of programs, select Hitachi Network Objectplaza Trace Library 2, and click the Change/Remove button. 3.
3.9.5 Uninstalling Hitachi Network Objectplaza Trace Library (HNTRLib) After you uninstall HDLM version 4.0 or earlier, if no applications other than HDLM are using HNTRLib, uninstall it using this procedure: 1. Check that no applications other than HDLM are using HNTRLib. See the manuals and documentation for each program to check whether the program is using Hitachi Network Objectplaza Trace Library. 2. Log on to Windows as a member of the administrators group. 3. Start the uninstallation program.
122 Chapter 3 Creating an HDLM Environment
Chapter 4 HDLM Operation This chapter describes operating procedures for HDLM, including how to operate HDLM and the HDLM manager, and how to change the configuration of the operating environment. Operating procedures are broken down into the following sections: Notes on Using HDLM (see section 4.1) HDLM operations using the HDLM GUI (see section 4.2) Using Commands for HDLM Operations (see section 4.3) Using the Windows Administrative Tool to Check Path Information (see section 4.
4.1 Notes on Using HDLM This section provides notes on HDLM operation. 4.1.1 Using a Storage Management Program You must not change the vendor and product IDs of the storage system. If you change them, HDLM cannot recognize the storage system. 4.1.2 Upgrading Windows Before upgrading the OS from Windows 2000 Server to Windows Server 2003 or re-installing the OS during system recovery, always uninstall HDLM. After upgrading the OS, install the appropriate HDLM version for the upgraded OS. 4.1.3 4.1.3.
4.1.4 Using the EMC DMX series, EMC CX Series, and HP EVA series Only HDLM version 5.7 or later can manage the EMC DMX series or EMC CX series. For HDLM versions earlier than 5.7, see section 3.6.4 and then perform an update installation. Only HDLM version 5.9.1 or later can manage the HP EVA series. For HDLM versions earlier than 5.9.1, see section 3.6.4 and then perform an update installation.
4.2 HDLM Operations Using the HDLM GUI This chapter explains the procedures for operating HDLM GUI window components. For details on the components of each window, see section 6.1. 4.2.1 Notes on Operating HDLM GUI Windows This section provides important notes for operating HDLM GUI windows. The HDLM GUI cannot start when all of the following conditions exist: The operating system of the host is Windows Server 2003 with SP1 or later applied.
– The JRE that is bundled with the HDLM product (JRE 1.3.1 provided by Sun Microsystems, Inc.) will be used to start the HDLM GUI, even if you install a JRE whose version differs from the one bundled with HDLM. When the HDLM GUI ends abnormally, the message below is output to the Windows application event log. Note that the value for fault address might differ from 0x0004d87d. Reporting queued error: faulting application java.exe, version 0.0.0.0, faulting module jvm.dll, version 0.0.0.
If the I/O load on the dynamic disk is heavy, it might take a long time to redisplay the HDLM GUI. When an operation to close a window is performed in the window frame of the path management window, the HDLM GUI will terminate even if the Option window remains open. If the HDLM GUI screen size is reduced, in some cases, buttons such as the Online and Offline buttons may become hidden. In such cases, please adjust the screen size appropriately, so that the buttons are visible.
4.2.3 Viewing Path Information This section explains how to view path information. Path information can be displayed in the following two formats: Configuration-diagram format. This format uses a diagram to display the configuration of the host, host bus adapters, paths, channel adapters, LUs, and storage system. List format. This format displays path information in a list. You can switch the display format for the path information by clicking the Configuration tab or the Path List tab.
4.2.3.2 Viewing Path Information in List Format To view path information in the list format: 1. Display the Path Management window. The Path List view of the Path Management window is displayed. (For details on displaying the Path Management window, see section 4.2.2.1.) 2. In the tree frame, select the host, storage system, or LU connected to the path whose information you want to view. If a host is selected, information on all the paths connected to the host is displayed in a list in the view frame.
4.2.4.2 Exporting Path Information to a CSV File To export path information to a CSV file: 1. Display the Path Management window. The Path List view of the Path Management window is displayed. (For details on displaying the Path Management window, see section 4.2.2.1.) 2. By performing operations in the tree frame, make sure that the Path List view displays the path whose information is to be exported to a CSV file. (For details on the tree frame, see section 6.2.2.
4.2.5 Setting Path Statistics to Initial Value This section explains how to set the values of the path statistics (I/O count and I/O errors) to the initial value (0) for all the paths that HDLM manages. This operation is useful when you want to find out how many I/Os or I/O errors occur during a specific period, from the time when the values for I/O count and I/O errors are set to the initial value (0). To set the path statistics to zero: 1. Display the Path Management window.
4.2.6 Changing the Path Status The procedure for changing the path status differs depending on the display format of the path information. Path information can be displayed in the following two formats: Configuration-diagram format. This format uses a diagram to display the configuration of the host, host bus adapters, paths, channel adapters, LUs, and storage system. List format. This format displays path information in a list.
If you attempt to change the status of multiple paths but the status of one of those paths cannot be changed, the KAPL02022-W or KAPL02023-W message appears. To ignore the path whose status cannot be changed and to continue processing, click the OK button. To stop processing, click the Cancel button. 4.2.6.2 Changing the Path Status from the List Format To change the path status when path information is displayed in list format: 1. Display the Path Management window.
5. Click the OK button. The status of the selected path changes to online or offline. Also, the icons displayed in the Status column change to (Online status) or (Offline(C) status). In a cluster configuration, if a user uses the Path Management window or uses the dlnkmgr command's offline operation to perform offline operations during reserve processing, the offline processing waits until the reserve processing finishes.
4.2.9 Viewing the HTML Manual To view the HTML version of this manual (HiCommand Dynamic Link Manager User's Guide (for Windows(R)): 1. Display the Path Management window. The Path List view of the Path Management window is displayed. For details on displaying the Path Management window, see sections 4.2.2.1. 2. Click the Help button. Your default Web browser starts and opens the Help window for the HTML version of this manual. 4.2.
4.3 Using Commands for HDLM Operations The following subsections explain how to use the HDLM commands to utilize HDLM functions. 4.3.1 4.3.2 Notes on Using Commands Execute the command as a member of the administrators group. To specify a value containing a space in a parameter, enclose the entire value in double quotation marks ("). If the I/O load on the dynamic disk is heavy, it might take a long time to execute the view operation.
4.3.3 Changing the Status of Paths This subsection explains how to change the status of paths. 4.3.3.1 Changing the Status of a Path to Online To change the status of a path to online: 1. Check the current status of the path. To change the status of the path for each HBA port, channel adapter port, or path to online, check the path name or AutoPATH_ID. The following example shows how to execute the command: >dlnkmgr view -path 2.
4.3.3.2 Changing the Status of a Path to Offline(C) To change the status of a path to Offline(C): 1. Check the current status of the path. To change the status of the path for each HBA port, channel adapter port, or path to Offline(C), check the path name or AutoPATH_ID. The following example shows how to execute the command: >dlnkmgr view -path 2. To change the status of the path to Offline(C), execute the dlnkmgr command's offline operation.
4.3.4 Viewing LU Information Using an HDLM Command To display LU information, execute the dlnkmgr command's view operation with the -lu parameter specified.
4.3.5 Initializing Statistical Information for Paths This subsection explains how to initialize statistical information (I/O counts and I/O errors) for all paths managed by HDLM. This procedure is useful when you wish to check the number of I/O hits and I/O errors that have occurred since the last time the I/O counts and I/O errors were initialized to the value 0. To initialize statistical information for paths: 1. Check the current status of the path.
4.3.6 Viewing and Setting Up the Operating Environment The following subsections explain how to display and set up the HDLM operating environment. 4.3.6.1 Viewing the Operating Environment To display the operating environment, execute the dlnkmgr command's view operation with the -sys and -sfunc parameters specified.
4.3.6.2 Setting Up the Operating Environment To set up the HDLM operating environment, execute the dlnkmgr command's set operation.
4.3.7 Viewing License Information To display license information, execute the dlnkmgr command's view operation with the sys and -lic parameters specified. The following shows an example in which the command is executed. >dlnkmgr view -sys -lic License Type Expiration Permanent KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss > For details on the displayed items and their descriptions, see section 7.7. 4.3.
4.3.9 Viewing HDLM Version Information To display HDLM version information, execute the dlnkmgr command's view operation with the -sys parameter specified.
4.3.10 Viewing HDLM Component Information To display HDLM component information, execute the dlnkmgr command's view operation with the -sys parameter specified.
4.4 Using the Windows Administrative Tool to Check Path Information In the Windows administrative tool, you can use Performance to check path information. The following shows the procedure for adding a counter that HDLM provides. Note: In Windows Server 2003 (IPF and x64) environment, the function of Using the Windows administrative tool to check path information is not supported. To add a counter: 1. Choose Start, Settings, and then Control Panel. Double click Administrative Tools.
Table 4.3 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. The following items are displayed for each path (sorted in ascending order of pathid): The path management PATH_ID is indicated by pathid.
4.5 Starting and Stopping the HDLM Manager If an error occurs in the system, such as in an HDLM program, you may need to manually stop or start HDLM to recover from the error. The following subsections describe these processes. 4.5.1 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 also starts automatically.
4.5.2 Stopping the HDLM Manager When you uninstall HDLM or install an HDLM upgrade or re-installation, the HDLM manager automatically stops. If, for some reason, the HDLM manager does not automatically stop, stop it using the following procedure: 1. Log on to Windows as a member of the administrators group. 2. In Control Panel, choose Administrative Tools and then Services. From the list of services, double-click DLMManager, and then click the Stop button. 3.
4.6 Reconfiguring the HDLM operating environment This section describes the procedures for changing an LU and a path configuration. Using the Windows plug-and-play functionality, which is called a dynamic reconfiguration functionality, you can add an LU and a path when the host installing HDLM is running. 4.6.1 Setting Up an Added LU and Path as an HDLM Management-Target This subsection explains the procedure for setting up an added LU and path as an HDLM management-target.
Figure 4.1 Using the dlnkmgr view -path Command to Confirm LU Addition Figure 4.2 shows an example of using the HDLM GUI to confirm that an LU has been added.
Figure 4.2 Using the HDLM GUI to Confirm LU Addition 5. For the new LU, write a signature, create partitions, and perform formatting. Note: A PathID is added to a minimum available number in ascending order. Once you delete a path, a different PathID might be assigned when you add a path again. Note that the previous number might not be assigned.
When MSCS is used: 1. Add an LU. 2. Stop node B. 3. In node A, perform the steps shown in When MSCS is not used. 4. Stop node A, and then start node B. 5. In node B, perform the steps shown in When MSCS is not used. 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 start node A. 7. In node A, register the new LU in MSCS, and set it up. 8. Start node B.
4.6.1.2 Checking an Added Path You can add a path by inserting a cable into an existing LU when the host installing HDLM is running. When you add only a path and do not add an LU, the display of the disk management is not changed. Figure 4.3 shows an example of using the dlnkmgr view -path command to confirm that a path has been added. Figure 4.3 Using the dlnkmgr view -path Command to Confirm Path Addition Figure 4.4 shows the example of using the HDLM GUI to confirm that a path has been added.
Figure 4.4 Using the HDLM GUI to Confirm That a Path Has Been Added Notes: A PathID is added to a minimum available number in ascending order. Once you delete path, a different PathID might be assigned when you add a path again. Note that the previous number might not be assigned. When a path is added to an LU, the following messages might appear: – KAPL08019-E and KAPL08022-E – KAPL05301-E These messages are output by Windows activities, and not by an error.
4.6.2 Deleting an LU Dynamically The LU deletion functionality automatically removes an LU from HDLM management when all the paths to that LU are disconnected. You can set the LU deletion functionality by specifying the dlnkmgr command's set operation together with the -rmlu on parameter in the HDLM command. You can also set this functionality in the Options window of the HDLM GUI. For details on the Options window, or set operation, see section 3.5.2. 4.6.2.
Figure 4.5 Displaying the KAPL05301-E Message In the event viewer, the information about the deleted path is displayed in the format: PathID PathName DskName iLU ChaPort. Figure 4.6 shows an example of outputting data to the KAPL05301-E message.
Figure 4.6 Outputting Data to the KAPL05301-E Message Table 4.4 shows the items and descriptions for the path information, displayed in the KAPL05301-E message. Table 4.4 Items and Descriptions for Path Information Displayed in KAPL05301-E Message Item Description PathID An AutoPATH_ID. Host port number Elements of a PathName.
4.6.2.3 Recovering the Deleted LU or Path To restore the deleted LU, recover it from physical failure and then perform the operations below. For a path error, remove the cause of the path error and then perform the following. Note that sometimes they are automatically recovered without performing the following operations. 160 In the Device Manager window of Windows, select Disk drives and then click Scan for hardware changes. In the Disk Management window of Windows, click Rescan Disks.
Chapter 5 Troubleshooting This chapter describes how to check HDLM error information, and how to take action if an error occurs in HDLM. The actions you should take are described separately for path errors, for HDLM program errors, and for other types of errors. Troubleshooting information is broken down into the following sections: Information collected by the DLMgetras utility for collecting HDLM error information (see section 5.1) Checking error information in messages (see section 5.
5.1 Information Collected by the DLMgetras Utility for Collecting HDLM Error Information Immediately after an error occurs, execute the error information collection utility, DLMgetras, since restarting the machine may delete information collected. For details about the DLMgetras utility and the error information it collects, see section 8.2.
5.2 Checking Error Information in Messages You can check path errors by referring to the KAPL08xxx messages output to event log. To obtain detailed information about a path, check the following windows according to the type of message”. For the HDLM GUI, check the Path List view in the Path Management window. For a command, check the execution results of the view operation.
Each message contains several elements. These elements are explained below. ErrorCode The error number generated when Windows detected the path error. PathID The ID assigned to a path. This ID is called the AutoPATH_ID. AutoPATH_IDs are reassigned every time the host is restarted. This path ID is the same as the path ID displayed in the Path List view in the Path Management window. The path ID is also the same as PathID displayed by the command's view operation.
5.3 Actions for a Path Error When a path error is detected by HDLM, you must immediately resolve the error and restore the path. A check for path errors is performed whenever an I/O is issued, or the Windows Plug and Play function detects that the paths are disconnected. If there are any paths through which I/O is not normally issued, such as a non-owner path, you should enable path health checking in order to detect errors regardless of I/O issuance. For details about path health checking, see section 2.
Figure 5.
5.3.1 Using the HDLM GUI to Handle a Path Error The following shows the procedure for handling a path error using the HDLM GUI. 5.3.1.1 Examine the Messages Examine the message that is output to the event log in the host for monitoring messages. If the KAPL08022-E message is output, view that message to check the path in which the error occurs. For details on the message, see section 5.2.
5.3.1.5 Identify the Error Location and Correct Hardware Errors Use the Windows and hardware management tools to identify the error location, and then take appropriate, corrective action. If an error occurs in the path, HDLM outputs an error message to the event log of the host. Information about the path in which the error occurred is also output to the event log. For hardware maintenance, contact your hardware vendor or maintenance company if there is a maintenance contract. 5.3.1.
5.3.2 Using the dlnkmgr Command to Handle a Path Error The following subsections show the procedure for using the HDLM command (dlnkmgr) to handle a path error. 5.3.2.1 Examine the Messages Examine the message that is output to the event log in the host for monitoring messages. If the KAPL08022-E message is output, view the message to check the path in which the error occurs. For details on each item displayed in the message, see section 5.2.
5.3.2.5 Identify the Error Location and Correct Hardware Errors Use the Windows and hardware management tools to identify the error location, and then take appropriate, corrective action. If an error occurs in the path, HDLM outputs an error message to the event log of the host. Information about the path in which the error occurred is also output to the event log. For hardware maintenance, contact your hardware vendor or maintenance company if there is a maintenance contract. 5.3.2.
5.4 Actions for Program Errors The following describes the troubleshooting procedure for handling errors that occur in an HDLM program. Figure 5.3 shows the troubleshooting procedure. Figure 5.3 Troubleshooting a Program Error The following subsections describe the troubleshooting procedures for handling a program error. The first subsection explains the procedure when using the GUI, and the second subsection explains the procedure when using the HDLM command (dlnkmgr).
5.4.1 Using the HDLM GUI to Handle a Program Error The following shows the procedure for handling a program error by using the HDLM GUI. 5.4.1.1 Examine the Messages Examine the message that is output to the event log in the host. If an error occurs in an HDLM program, a message other than KAPL08xxx is output to the event log. Check the output message. Messages with error level E (Error) or higher require corrective action. 5.4.1.
5.4.1.3 Take Action for the Program Error Take the action recommended for the program error message as described in Chapter 9. If the error occurs again after you take the corrective action, use the Options window to check the status of the HDLM program, and then take the appropriate corrective action. To check the status of an HDLM program: 1. Display the Path Management window. The Path List view appears in the Path Management window. 2. Click the Options button. The Options window appears. 3.
Use the DLMgetras utility for collecting HDLM error information to collect the error information. For details on the DLMgetras utility and the information it collects, see section 8.2. Some of the information collected by the DLMgetras utility might be cleared when the system is restarted. When an error occurs, as soon as possible execute the DLMgetras utility. When an error occurs in the HDLM GUI, collect the screenshot at the time the error occurred. 5.4.2.
5.5 Actions Taken for Other Errors When the cause of an error may be related to HDLM but is neither a path error nor an HDLM program error, execute the DLMgetras utility for collecting HDLM error information, and then report the collected information to the HDLM vendor or maintenance company if there is a maintenance contract for HDLM. For details about the DLMgetras utility and the information it collects, see section 8.2.
176 Chapter 5 Troubleshooting
Chapter 6 GUI Reference This chapter explains the items displayed in the HDLM GUI windows. Reference information is included in the following sections: HDLM GUI windows (see section 6.1) Path Management window (see section 6.2) Options window (see section 6.
6.1 HDLM GUI Windows This section explains the windows that make up the HDLM GUI and the window transitions (that is, how the user moves from one window to another). You can use the HDLM windows to perform the same operations as you would perform using the HDLM command. You can also use HDLM windows, together with HDLM commands, to operate HDLM. For example, when you execute a command, the result of the command will be reflected in an HDLM window.
6.1.2 Window Transitions Figure 6.1 shows the transitions among HDLM windows.ss Figure 6.1 Window Transitions When you display the Options window or Help window from the Path Management window, the Options or Help windows are displayed as separate windows. Note, however, that while the Options window is displayed, you cannot perform any operations in the Path Management window.
6.2 Path Management Window This section explains the Path Management window. In this window, you can do the following: View path information. For details, see section 4.2.3. Export path information to a CSV file. For details, see section 4.2.4. In the path information, set the I/O count and the I/O error count to 0. For details, see section 4.2.5. Change the path status. For details, see section 4.2.6. Refresh the display of path information. For details, see section 4.2.7.
Figure 6.2 Path Management Window As shown in Figure 6.2, the Path Management window is composed of the following three frames: Common frame Displays the title, logo, and buttons that are used throughout the HDLM GUI. Tree frame Displays, in tree format, the storage systems and LUs that are managed by the host. View frame Displays the path configuration view or path list view.
6.2.1 Common Frame The buttons in the common frame are: 6.2.2 Refresh button: Reflects the most recent path information in the Path Management window. Options button: Displays the Options window, which reflects the most recent operating environment. Help button: Displays the HTML version of this manual. Exit button: Closes the Path Management window. Tree Frame You use the tree frame to specify the range of path information to be displayed in the view frame. Figure 6.
The following describes the window components in the tree frame: Host. The tree frame displays an icon that indicates the host and the character string host. In the tree frame of the Configuration view, an unselectable host icon is always displayed. In the tree frame of the Path List view, selectable host icons are always displayed. When you select a host, the view frame of the Path List view displays the path information of all paths connected to the selected host. Table 6.1 explains the host icons.
Model ID Model Name of Storage System USP_V Hitachi Universal Storage Platform V XP128 XP128 XP1024 XP1024 XP10000 XP10000 XP12000 XP12000 XP24000 XP24000 When you select a storage system, the view frame displays all of the paths connected to all of the LUs that can be accessed from that selected storage system. When the Path Management window starts, a plus sign (+) is displayed on the left side of the system icons.
Table 6.4 Icon LU Icons in Tree Frame of the Path Management Window Icon Name Explanation LU (all paths are online) Indicates an LU in which all paths are operating normally. Indicates an LU all of whose paths are in the Online status. LU (some paths are offline) Indicates an LU in which some paths are operating normally. Indicates an LU that has a path in the Online status and also has a path in the Offline(C) or Offline(E) status.
6.2.3 Configuration View in the Vview Frame The view frame of the Path Management window displays one of the following two views: Configuration view Path List view This subsection explains the window components in the Configuration view. If the content displayed for each storage system differs, this subsection explains the displayed contents individually. The following figures show the Configuration view for each storage system. Figure 6.
Figure 6.5 Configuration View (When Using the TagmaStore AMS 1000 or Thunder 9580V) Figure 6.
188 Figure 6.7 Configuration View: Lightning 9900V Series Figure 6.
When using the TagmaStore USP, the display format for the following items is different from that for other storage systems: A channel adapter number is assigned to each channel adapter. In Figure 6.8, these numbers are CHA-1E, CHA-1F, and so on. The port numbers for each channel adapter can be displayed in the minimized, or expanded modes.
The Type specification has priority over the Status specification. For example, if you clear the Owner path check box in Type, the Configuration view will not display those paths even if their statuses are selected in the Status check boxes. Note that the Type settings of the Configuration view remain in effect even when you click the Path List tab and switch to the Path List view. Owner Path check box Select Owner path to display owner paths. Clear Owner path to hide all paths.
When no path is displayed in the Configuration view, or no path is selected, the Offline button is displayed as inactive. If you attempt to change the status of multiple paths to Offline(C) but one of those paths cannot be changed, the message KAPL02023-W appears. To ignore the path whose status cannot be changed and to continue processing, click the OK button. To stop processing, click the Cancel button. Host: host is displayed.
Line Style Path Status If the intermittent error monitoring functionality is enabled, the line that indicates the error path flashes when an intermittent error occurs in the path (The line lights for 3 seconds and then goes out for 0.2 seconds, repeatedly). Placing the mouse pointer over a path displays a tool tip giving the path status (Online, Offline(C), Offline(E), Offline(E) (intermittent error), Online(E), or Online(E) (intermittent error)) and whether the path is an owner path or non-owner path.
Placing the mouse pointer over these buttons displays a tool tip containing the channel adapter port number. For the Lightning 9900V Series, the tool tips for the buttons a to r of CL1 may display 3a to 3r, and the tool tips for the buttons a to r of CL2 may display 4a to 4r. – When using TagmaStore USP This button displays the CHA port number. The CHA port button is displayed in the minimized or the expanded mode for each CHA.
CHA button: This button indicates a channel adapter. – When using the TagmaStore AMS/WMS series, Thunder 9500V Series, or Thunder 9200 There are two buttons: CHA0 and CHA1. If one or more of the channel adapter ports belonging to a CHA are displayed as active, the corresponding CHA button is displayed as active. If you selected an LU in the tree frame, HDLM displays whether the paths connected to the CHA are owner paths or non-owner paths based on the information of the paths connected to the LU.
Vendor ID: The name of the storage system vendor (for example, HITACHI). Model ID: Indicates the model name of the storage system (for example, 9200 indicates the Thunder 9200). Serial number: The serial number of the storage system (for example, 0123). Table 6.6 shows the model IDs displayed in the Configuration view, and the model names of corresponding storage systems supported by HDLM. Table 6.
6.2.4 Path List View in the View Frame The view frame area of the Path Management window displays one of the following two views: Configuration view Path List view This subsection explains the window components in the Path List view. The Path List view of the Path Management window displays the configuration, status, and utilization of paths. Figure 6.9 shows the Path List view. Figure 6.
Status: You use the following four check boxes to select the status of the paths to be displayed. By default, all check boxes are selected. When you clear a Status check box, the Path List view narrows down the items displayed. Online path check box: When you select this check box, the Path List view displays the paths that have the Online or Online(P) status. Offline path check box: When you select this check box, the Path List view displays the paths that have the Offline(C) status.
Export CSV button: This button exports, to a CSV file, the information for the paths displayed in the Path List view. The default name for the CSV file is homedirectory/pathlist.csv. When no path is displayed in the Path List view, the Export CSV button is displayed as inactive. Column headers: The column header for each column is a button. When you click the button, the path information is sorted using the information in the clicked header's column as the sorting key.
Path Name: The path name, which indicates a path. When you modify the system configuration or replace a hardware item, you should check the path names to identify the paths that will be affected by the change. A path name consists 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) Table 6.
Table 6.
CLPR: This column displays the CLPR number to which the CHA belongs. A decimal value from 0 to 31 is displayed. Note that a hyphen (-) is displayed if the following items are subject to display: CHA ports in the storage system that do not support cache logical partition functionality Paths connected to the Snapshot Image of the Copy-on-write Snapshot of the TagmaStore AMS/WMS series Type: This column displays the attributes of paths.
6.3 Options Window In the Options window, you can do the following: View the HDLM operating environment. Set the HDLM operating environment. For details on how to view or set up the HDLM operating environment, see section 4.2.8. Figure 6.10 shows the Options window. Figure 6.10 Options Window Table 6.9 describes the default value and recommended value for each item displayed in the Options window.
Table 6.9 Default and Recommended Values for Items Displayed in the Options Window Displayed Item Default Value Recommended Value Load balancing ON ON Algorithm is Round robin The recommended setting for the algorithm depends on the operating environment. ON ON The checking interval is 30 minutes. The recommended checking interval depends on the operating environment.
Table 6.10 lists and describes the items displayed in the HDLM Component Information dialog box. Table 6.10 Items Displayed in the HDLM Component Information Dialog Box Item Description Component HDLM component Version number Version number of the component Status Status of the component: Alive: Normal Dead: Stopped Wakeup time Time the component was started Clicking the OK button closes the HDLM Component Information dialog box.
Auto failback Specify whether or not the auto failback function is to be used. To use the function, select ON; otherwise, select OFF. When ON is selected, you can specify the interval (in minutes) at which the path status is checked. Specify a value from 1 to 1440 minutes. The default, which is also the recommended value, is 1. Set the value depending on system operations.
Specify whether or not intermittent error monitoring is to be used. To use this function, select ON; otherwise, select OFF. When you use automatic failback, we recommend that you set intermittent error monitoring to ON to prevent an intermittent error from reducing I/O performance. When you set Intermittent Error Monitor to ON, you can specify the error monitoring interval and the number of times that an error is to occur.
When Intermittent Error Monitor is set to ON and automatic failback is set to OFF, intermittent error monitoring is disabled. If you return the automatic failback to ON, intermittent error monitoring is enabled. Available operations for automatic failback and intermittent error monitoring depend on the function settings. Table 6.12 shows the relation between the settings and available operations for automatic failback and intermittent error monitoring. Table 6.
OFF OFF ON#3 OFF The error count, elapsed monitoring time, and information about paths not subject to automatic failback are completely cleared. Set AFB to ON. The operations of AFB and IEM do not change. Change the AFB setting. AFB operates using new settings. Set AFB to OFF. AFB is disabled. Set IEM to ON. IEM is enabled.#2 Set AFB to ON. AFB and IEM are enabled.#2 Set AFB to OFF. The operations of AFB and IEM do not change. Set AFB to ON. AFB is enabled. Set AFB to OFF.
Table 6.13 LU Deletion Function Values Value Description OFF The LU is not removed from HDLM management even if an error occurs in all the paths to the LU, all the paths to the LU are disconnected, or the LU is deleted. The status of the paths is Offline(E) and Online(E). This operation is the same as the operation in HDLM 5.1 or earlier. The off option is recommended when you want to use the same functionality as you use in HDLM 5.1 or earlier, without using the LU deletion functionality.
From the pull-down list box, select the desired trace output level. In the event of an error, you may need to set the trace level to 1 or higher and collect the log information again. – 0: Do not output any trace – 1: Error information only – 2: Summary of program operation – 3: Details of program operation – 4: All information The amount of log information to be output increases as the value of the setting increases.
If you set a smaller value than the current one, an execution confirmation message KAPL02080-W is output and then the trace file is deleted. You can set the file size for the trace file hdlmtrn.log (n indicates a file number from 1 to 64). The trace files are fixed in length. Thus, even if the amount of written trace information is less than the setting file size, the size of each output trace file is always fixed.
212 Chapter 6 GUI Reference
Chapter 7 Command Reference This chapter describes the HDLM command (dlnkmgr) and its operations. Subsections include: Overview of the HDLM command (see section 7.1) The clear operation (see section 7.2) The help operation (see section 7.3) The offline operation (see section 7.4) The online operation (see section 7.5) The set operation (see section 7.6) The view operation (see section 7.
7.1 Overview of the HDLM Command (dlnkmgr) This section describes how to specify the HDLM command dlnkmgr and its subcommands (called operations in HDLM). Note that messages might refer to this command and the operations as the HDLM command. Command format Enter the command using the following format: dlnkmgr operation-name [parameter [parameter-value]] Command values include the following: The command name is dlnkmgr. The type of operation entered after dlnkmgr is operation-name.
7.2 The Clear Operation The dlnkmgr command's clear operation clears the statistics (I/O count and I/O errors) of all paths that are managed by HDLM to the initial value. 7.2.1 Format To set the path statistics to 0, use this command: dlnkmgr clear -pdst [-s] To display the format of the clear operation, use this command: dlnkmgr clear -help 7.2.2 Parameters To set the path statistics to 0, -pdst clears statistics (I/O count and I/O errors) of all paths managed by HDLM to the initial value (0).
7.3 The Help Operation The dlnkmgr command's help operation displays the list of operations available for the HDLM command, or the format of individual operations. 7.3.1 Format The help operation’s format is: dlnkmgr help [operation-name] [operation-name] ... 7.3.2 Parameters operation-name Specify the name of the HDLM command operation whose format you want to know.
Example 2: The following example shows how to display the formats of multiple operations. >dlnkmgr help online offline help online: Format dlnkmgr online [-path] -hba HBAPortNumber.BusNumber [-s] dlnkmgr online [-path] -cha -pathid AutoPATH_ID [-s] dlnkmgr online [-path] [-pathid AutoPATH_ID] [-s] Valid value AutoPATH_ID { 000000 – 999999 }(Decimal) offline: Format dlnkmgr offline [-path] -hba HBAPortNumber.
7.4 The Offline Operation The dlnkmgr command's offline operation places online paths offline. Specify the paths you want to place offline by specifying a HBA port or channel adapter port to which the target paths are connected, or by specifying a single path. The last path accessing each LU cannot be placed offline. Placing too many paths offline may prevent path switching if an error occurs. Before placing a path offline, use the view operation to check how many online paths remain.
>dlnkmgr offline -hba 1.1 KAPL01055-I All the paths which pass the specified HBA will be changed to the Offline(C) status. Is this OK? [y/n]:y KAPL01056-I If you are sure that there would be no problem when all the paths which pass the specified HBA are placed in the Offline(C) status, enter y. Otherwise, enter n. [y/n]:y KAPL01061-I 3 path(s) were successfully placed offline(C). 0 path(s) could not be placed offline(C).
To display the format of the offline operation, use -help. The following example shows how to display the format of the offline operation: >dlnkmgr offline -help offline: Format dlnkmgr offline [-path] -hba HBAPortNumber.BusNumber [-s] dlnkmgr offline [-path] -cha -pathid AutoPATH_ID [-s] dlnkmgr offline [-path] -pathid AutoPATH_ID [-s] Valid value AutoPATH_ID { 000000 – 999999 }(Decimal) KAPL01001-I The HDLM command completed normally.
7.5 The Online Operation The dlnkmgr command's online operation places offline paths online. You can specify the paths you want to place online by specifying a HBA port or channel adapter port to which the target paths are connected, or by specifying a single path. 7.5.1 Format To place the path online: dlnkmgr online [-path] [-hba host-port-number.bus-number |-cha -pathid AutoPATH_ID |-pathid AutoPATH_ID] [-s] To display the format of the online operation: dlnkmgr online -help 7.5.
To place online, at one time, all paths that pass through a specific channel adapter port, use -cha -pathid AutoPATH_ID. The command will place online all paths that pass through the channel adapter port to which the path with the specified AutoPATH_ID is connected.
KAPL01001-I The HDLM command completed normally. Operation name = online, completion time = yyyy/mm/dd hh:mm:ss > 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 section 7.7.
7.6 The Set Operation The dlnkmgr command's set operation sets the HDLM operating environment. 7.6.
Error log file size 9900 (KB) 9900 (KB) Number of error log files 2 2 Trace level 0: Do not output any trace. 0: Do not output any trace. Trace file size 1000 (KB) 1000 (KB) Number of trace files 4 4 Path health checking on on The recommended checking interval depends on the operating environment. Automatic failback off Off Intermittent Error Monitor off Off Remove LU off The recommended value depends on the operating environment.
Table 7.3 shows the values of the error log collection level. If an error occurs, you may have to set the error log collection level to 1 or higher to collect log information. Table 7.3 Error Log Collection Level Values 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.
Table 7.4 Trace Level Values Value Description 0 Does not output any trace. 1 Only outputs error information. 2 Outputs a summary of program operation. 3 Outputs details of program operation. 4 Outputs all information. The larger the trace level value, the larger the amount of log information that is output. As the amount of log information that is output increases, the amount of time before existing information is overwritten becomes shorter.
The explanation for the following sub-parameter describes how to specify the checking interval. To specify the checking interval between path health checks (in minutes), use -intvl checking-interval. Specify a value from 1 to 1440 minutes depending on the user environment. When you change the checking interval, the new setting takes effect immediately.
To specify the interval between path status checks (in minutes), use -intvl checkinginterval. Specify a value from 1 to 1440 minutes as appropriate for your operation environment.
If you omit the intermittent error monitoring interval or the number of times that the error is to occur, each setting is specified as follows: When the intermittent error monitoring interval or the number of times that the error is to occur has not been specified before, the intermittent error monitoring interval is set to 30 minutes, and the number of times that the error is to occur is set to 3.
Outside the duration of intermittent error monitoring, if you change the number of times that the error is to occur in order for the system to determine that an intermittent error has occurred, from the next time automatic failback finishes normally, the changed values takes effect. Outside the duration of intermittent error monitoring, the number of errors that determine an intermittent error is not counted and this value is not changed.
Setting Automatic Failback Available Operation Result of Operation Set intermittent error monitoring to on. When a path is being monitored (in the period of conditional intermittent error monitoring), the value of the error count and the elapsed monitoring time are reset to 0, and then intermittent error monitoring restarts. When a path is not being monitored (outside the period of conditional intermittent error monitoring), nothing changes.
Setting Automatic Failback Available Operation Result of Operation Intermittent Error Monitoring 2Since automatic failback is off, intermittent error monitoring is disabled. The following example shows how to enable monitoring of intermittent errors: >dlnkmgr set -iem on -intvl 20 -iemnum 2 KAPL01049-I Would you like to execute the operation? Operation name = set [y/n]: y KAPL01001-I The HDLM command completed normally.
Table 7.6 lists the license key types. Table 7.6 License Key Types Type Description Permanent license key Permanent licenses are valid for using HDLM in an ongoing basis. Temporary license key* The temporary license key is used temporarily, for example, when a user performs product evaluations. Temporary licenses are valid for only 120 days after installation. You cannot reuse a temporary license key.
Table 7.7 shows the values of the LU dynamic deletion functionality. Table 7.7 Values for LU Dynamic Deletion Functionality Value Description off The LU is not removed from HDLM-management even if the error occurs in all the paths to the LU, all the paths to the LU are disconnected, or the LU is deleted. The status of the paths is Offline(E) and Online(E). This operation is as equal as the operation in HDLM 5.1 or earlier.
The following example shows how to display the format of the set operation.
7.7 The View Operation 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 long time to execute the view operation. 7.7.
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]|all ] [-hdev host-device-name|-pathid AutoPATH_ID] [-exlu] [-t] To display a summary of LU information : dlnkmgr view -lu -c [-exlu] [-t] To display a summary of LU information (by adding items to be displayed): dlnkmgr view -lu -c -item [slpr] [-exlu] [-t] To displa
7.7.2 Parameters This section describes the parameters for the view operation. 7.7.2.1 Parameters Used for Displaying Program Information To displays the HDLM program information, use -sys [-sfunc|-msrv|-adrv|-pdrv|lic]. Use one of the subsequent parameters (following -sys) to specify the program information that you want to display. If you do not specify a subsequent parameter, the command displays all program information. Table 7.
Parameter and Program Information -sfunc Information about the HDLM function settings Item Description Trace Level Trace output level 0: Does not output any trace 1: Only outputs error information 2: Outputs a summary of program operation 3: Outputs details of program operation 4: Outputs all information Trace File Size(KB) Trace file size in kilobytes Number Of Trace Files Number of trace files Path Health Checking Setting for path health checking on: Enabled off: Disabled
Parameter and Program Information -adrv Item Description WakeupTime Startup time of the HDLM manager HDLM Alert Driver Status of the HDLM alert driver Information about the HDLM alert driver -pdrv Alive: Normal Dead: Stopped Ver Version number of the HDLM alert driver WakeupTime Startup time of the HDLM alert driver ElogMem Size Size of error log memory for the HDLM alert driver in kilobytes HDLM Driver Status of the HDLM driver Information about the HDLM driver -lic Alive: No
The following example shows how to display information about the HDLM function settings: >dlnkmgr view -sys -sfunc HDLM Version : xx-xx Service Pack Version : Load Balance : on(rr) Support Cluster : off Elog Level : 3 Elog File Size(KB) : 9900 Number Of Elog Files : 2 Trace Level : 0 Trace File Size(KB) : 1000 Number Of Trace Files : 4 Path Health Checking : on(30) Auto Failback : off Remove LU : on Intermittent Error Monitor : off KAPL01001-I The HDLM command completed normally.
7.7.2.2 Parameters Used for Displaying HDLM Management-Target Device Information Use the –stinfo parameter to display information about a HDLM management-target device (except the Thunder 9200/9500V Series, Lightning 9900/9900V Series, TagmaStore, and Universal Storage Platform V) that was set when HDLM was installed. Table 7.9 describes the displayed items. Table 7.
7.7.2.3 Parameters Used for Displaying Path Information When displaying path information, if the -item parameter or the -c parameter is specified at the same time as 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.
-exlu: When an HDLM management-target device contains the EMC DMX series, EMC CX series, or HP EVA series. If this parameter is specified, the entire 32 digits of the iLU are displayed without truncating it to 13 digits. If this parameter is not specified, the iLU of the EMC DMX series, EMC CX series, and HP EVA series is displayed as 16 digits with the 14th to 16th digits displayed as periods (...).
When the -exlu parameter is specified: 246 Chapter 7 Command Reference
Parameters for Displaying Path Information by Selecting a Display 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. Table 7.10 shows the items that can be selected by using the -item parameter and the parameter values that can be specified after the -item parameter. Table 7.
-stname: Use this parameter for the Thunder 9200/9500V Series, Lightning 9900/9900V Series, TagmaStore, or Universal Storage Platform V to display the model ID of the storage system in the product ID element of the DskName field. When this parameter is omitted, the command displays the product ID or emulation type of the storage system instead. When you use this parameter, DskName is displayed by default. Therefore, it is not necessary to specify dn for the -item parameter.
HiCommand® Dynamic Link Manager (HDLM) for Windows® Systems User’s Guide 249
Parameters for Displaying a Summary of Path Information If the -c parameter is specified at the same time as the -path parameter, only PathID, DskName, iLU, CP, Status, and Type are displayed from the path information managed by HDLM. The displayed contents are shortened so that each instance of path information 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 in each item, see Table 7.11.
The following example shows how to display a summary of the path information in the order of the iLUs: HiCommand® Dynamic Link Manager (HDLM) for Windows® Systems User’s Guide 251
Displayed Path Information Table 7.11 describes the displayed path information. Table 7.11 Displayed Path Information Displayed Item No Summary Displayed1 Description Summary Displayed2 Paths Total number of displayed paths, indicated by a decimal number. OnlinePaths Number of available paths in the displayed paths, indicated by a decimal number. When the value of Paths equals the value of OnlinePaths, all paths are online.
Displayed Item Description No Summary Displayed1 Summary Displayed2 DskName3 DskName The storage system name, which identifies the storage system that is accessed by a path. A storage system name consists of the following three elements, separated by periods: Vendor ID: The name of the storage system vendor (for example, HITACHI). Product ID: Indicates the storage system product ID, emulation type, or model ID (for example, DF600F). For more details, see Table 7.13.
Displayed Item No Summary Displayed1 Description Summary Displayed2 Status of the path Status Online: Online Offline(C): Placed offline using the Path Management window of the HDLM GUI or by a command Offline(E): Offline due to an error Online(E): Failure has occurred (If none of the paths accessing one LU have an Online status, one of those paths is changed to the Online(E) status.
Displayed Item Description No Summary Displayed1 Summary Displayed2 IEP Not displayed Information about the intermittent error. This item is displayed only when you specify iem with the -path parameter. One of the following values is displayed for each path: - indicates that intermittent error monitoring is disabled or the monitoring time for an intermittent error is out of range (the path status is Online(E) or Offline(E)).
Table 7.13 shows the product ID displayed by the -path Operation View. Table 7.
7.7.2.4 Parameters Used for 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.
The –t parameter does not display the title for each information item. For example, when the -exlu parameter is not specified: >dlnkmgr view -lu Product : 9500V SerialNumber : 0329 LUs : 2 iLU HDevName PathID 0000 P 000006 000014 0001 Q 000007 000015 Status Online Online Online Online Product : DGC SerialNumber : LUs : 2 iLU HDevName PathID 6006016099C50... F 000004 000008 6006016099C50...
iLU HDevName PathID 6006048000018781000153594D423031 L 000000 000010 6006048000018781000153594D423032 M 000001 000011 6006048000018781000153594D423033 N 000002 000012 6006048000018781000153594D423034 O 000003 000013 KAPL01001-I The HDLM command completed normally.
Parameters for Displaying LU Information by Adding Items to be Displayed In the -lu –item parameter, the items specified with the -item option are added to the items to be displayed by the -lu option and displayed. If no value or all is specified for the -item parameter, all the items that can be added are displayed. Table 7.14 shows the items that can be added by using the -item parameter and the parameters that can be specified after the -item parameter. Table 7.
-exlu: When an HDLM management-target device is the EMC DMX series, EMC CX series, or HP EVA series. If this parameter is specified when a device managed by HDLM is the EMC DMX series, EMC CX series, and HP EVA series, the entire 32 digits of the iLU are displayed without truncating it to 13 digits. If this parameter is not specified, the iLU of the EMC DMX series, EMC CX series, and HP EVA series is displayed as 16 digits with the 14th to 16th digits displayed as periods (...).
In the –exlu parameter, when an HDLM management-target device contains the EMC DMX series, EMC CX series, or HP EVA series. If this parameter is specified, the entire 32 digits of the iLU are displayed without truncating it to 13 digits. If this parameter is not specified, the iLU of the EMC DMX series, EMC CX series, and HP EVA series is displayed as 16 digits with the 14th to 16th digits displayed as periods (...).
Parameters for Displaying a Summary of LU Information by Adding Items to be Displayed In the -lu -c –item parameter, the items specified with the -item option are added to the items to be displayed by the -lu -c option and displayed. If no value is specified for the -item parameter, all the items that can be added are displayed. See Table 7.15 for the contents of each displayed item.
Displayed LU Information Table 7.15 describes the displayed LU information. The following explains the table headings. Table 7.
Displayed Item Description No Summary Displayed1 Summary Displayed2 PathID Not displayed AutoPATH_ID indicated by a decimal number. AutoPATH_ID is assigned when the host is restarted. PathName3 Not displayed The path name, which indicates a path. When you modify the system configuration or replace a hardware item, you should check the path names to identify the path that will be affected by the change.
Displayed Item Description No Summary Displayed1 Summary Displayed2 Type3 Not displayed For the Thunder 9200/9500V Series, Lightning 9900/9900V Series TagmaStore, and Universal Storage Platform V: Attribute of the path Own: Owner path Non: Non-owner path When connected to the Lightning 9900 Series, Lightning 9900V Series, TagmaStore USP, or Universal Storage Platform V, all paths are owner paths. For the EMC DMX series, EMC CX series, and HP EVA series: A hyphen (-) is displayed.
Displayed Item No Summary Displayed1 3This Description Summary Displayed2 information is displayed when one of the following conditions exist: The user selected the item to be displayed by using the -lu -item parameter. all was specified. No value was specified for the parameter. 4This information is displayed when one of the following conditions exist: The user selected the item to be displayed by using the -lu -c -item parameter. No value was specified for the parameter.
268 Chapter 7 Command Reference
Chapter 8 Utility Reference This chapter explains the utilities used by HDLM. Utilities are discussed in the following sections: Overview of utilities (see section 8.1) The DLMgetras utility (see section 8.2) The dlmpr utility (see section 8.3) The dlmprsvkey utility (see section 8.4) The dlmchkpath utility (see section 8.
8.1 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 information to be submitted to your HDLM vendor or maintenance company. For details about the DLMgetras utility, see section 8.2. The utility for clearing HDLM persistent reservation (dlmpr). This utility cancels remaining persistent reservations after an un-installation.
8.2 The DLMgetras Utility for Collecting HDLM Error Information This utility collects information that is needed to analyze HDLM errors that have occurred: information such as error logs, integrated trace files, trace files, definition files, and operating system information. The collected information is archived in a file and saved to the directory that you specified. When the system is restarted, a part of the information that was collected by the DLMgetras utility will be cleared.
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. You cannot use this parameter together with the -eventlogsize log-size parameter. -h Displays the format of the DLMgetras utility.
8.2.3 List of Collected Error Information Table 8.1 lists the types of error information collected by the DLMgetras utility for collecting error information in the folder to which error information is output. Table 8.1 List of Error Information Collected by DLMgetras Utility Collected Files1 Folder Files Explanation Just under the folder to which collected information is output getrasn.log The log file generated when DLMgetras is executed.
Collected Files1 Folder Files Explanation folder-to-which-collectedinformation-is-output\VxVMinstallation-destinationdrive-name_Program Files\Veritas\Volume Manager M.N\logs4 All files under logs VxVM log folder-to-which-collectedinformation-is-output\VCSinstallation-destinationdrive-name_Program Files\Veritas\Cluster Server\log All files under log VCS log Integrated-trace-file-output-folderspecified-in-the-Hitachi-NetworkObjectplaza-Trace-Library-utility hntrn.
Collected Files1 Folder Files Explanation 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 Result of the dlnkmgr view -sys command evApplication.evt Event log for applications evApplication.log evSecurity.evt Event log for security evSecurity.log evSystem.evt Event log for the system evSystem.log folder-to-which-collectedinformation-isoutput\hbsainfo HBA-reg.
Manually Obtainable Error Information Files and How to Obtain Them When the DLMgetras utility finishes normally, the KAPL10022-I message is displayed. Error information is not obtained in the following cases: When the KAPL10048-E message is displayed after execution of the DLMgetras utility finishes When the KAPL10022-I and KAPL10048-E messages are not displayed after execution of the DLMgetras utility finishes.
Error Information File How to Obtain Files1 Registry information application-list.txt Use a registry editor to output the registry information into a file. The following lists the registry keys for each file. dlm-reg.txt HBA-reg.txt When obtaining the HBA-reg.txt file, the registry keys below might not exist, depending on the environment you use. Only output existing registry keys into a file. For application-list.txt: HKEY_LOCAL_MACHINE\SOFTWARE For dlm-reg.
Error Information File How to Obtain Files1 MSCS information cluster-sys.txt At the command prompt, execute all of the cluster commands listed below to output the results into the cluster-sys.txt file: iSCSI information dlm_iscsims.txt4 cluster /ver > cluster-sys.txt cluster /QUORUM >> cluster-sys.txt cluster /List >> cluster-sys.txt cluster node >> cluster-sys.txt cluster node /prop >> cluster-sys.txt cluster node /priv >> cluster-sys.txt cluster group >> cluster-sys.
Error Information File How to Obtain Files1 hdlmdsm-status.txt dlmmemorytrace.txt dlmmgr-lic.txt dlmmgr-lu.txt dlmmgr-lu-all.txt dlmmgr-path.txt dlmmgr-path-iem.txt dlmmgr-sys.txt hdlmdsm-status.txt viewfile.txt At the command prompt, execute the following commands to output the results into each file: hdlmdsm-status.txt HDLM-installation-drive:\Program Files\HITACHI \DynamicLinkManager\DLMTools\hsptpdrv.exe aa > hdlmdsm-status.txt dlmmemorytrace.
Error Information File How to Obtain Files1 MPIO information mpio-list.txt At the command prompt, execute the mpiolist command listed below to output the results into the mpio-list.txt file: Windows system information winmsd.txt All the folders and the list of files in the Windows installation destination folder dirSystemRoot.txt 1The HDLM-installation-drive:\Program Files\HITACHI\DynamicLinkManager\DLMTools \mpiolist 0 > mpio-list.
8.3 The dlmpr Utility for Clearing HDLM Persistent Reservation The dlmpr utility clears the persistent reservation left in the LU after HDLM is uninstalled. However, the persistent reservation is not left in the LU when you uninstall HDLM as instructed by the procedure in the manual. This utility is located in: drive-whereinstallation-CD-ROM-is-being-inserted\DLMTools\dlmpr.exe Note: This utility can be executed when the following conditions are satisfied: 8.3.1 HDLM has been uninstalled.
8.3.2.1 Clearing the Persistent Reservation in an MSCS Environment To clear the persistent reservation in an environment in which MSCS is used: 1. Start a host from the hosts that make up the MSCS system. 2. Choose Start, Settings, Control Panel, double-click Administrative Tool, and then double click Computer Management. The Computer Management window is displayed. 3. Choose Services and Applications and then double-click Services. A list of services is displayed.
7. Choose Start, Settings, Control Panel, double-click Administrative Tool, and then double-click Computer Management. The Computer Management window is displayed. 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. Select Automatic from the Startup type combo box in the General tab, and then click OK button. 9. In the Computer Management window, choose Device Manager.
8.4 The dlmprsvkey Utility for Registering an HDLM Persistent Reservation Key This utility registers and displays a persistent reservation key on the HDLM host. A persistent reservation key is required to operate HDLM functions normally. This utility is executed automatically at installation of HDLM. A registered persistent reservation key becomes valid after the host is rebooted. This utility is located in the following: HDLM-installation-folder\bin\dlmprsvkey.exe 8.4.
KAPL12106-I An attempt to register the PRSV key was successful. (PRSV key = 0123456789abcdef) Specify the –s parameter to display no confirmation message on execution of the dlmprsvkey utility. Specify the –v parameter to display the registered persistent reservation key. Example: >dlmprsvkey -v KAPL12116-I The registered PRSV key will now be displayed. (PRSV key = 0123456789abcdef) Specify the –h parameter to display the help for this utility.
8.5 The dlmchkpath Utility for Checking HDLM Paths If you install or uninstall HDLM in a multi-path configuration, the disk contents might no longer be correct. Use the dlmchkpath utility for checking HDLM paths to make sure that the system is in a single-path configuration. During upgrade installation or re-installation of HDLM, the dlmchkpath utility is executed automatically.
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 section 7.7. >dlnkmgr view -path -c Paths:000006 OnlinePaths:000006 PathStatus IO-Count IO-Errors Online 152579 30 PathID DskName 000000 HITACHI .DF600F .5455 000001 HITACHI .DF600F .5455 000002 HITACHI .DF600F .5455 000003 HITACHI .DF600F .5455 000004 HITACHI .DF600F .5455 000005 HITACHI .DF600F .
288 Chapter 8 Utility Reference
Chapter 9 Messages This chapter describes the format and meaning of message IDs, terms used in messages and in message explanations, HDLM messages, and appropriate actions to take in response to the messages. Section 9.16 describes the meanings and actions to be taken of return codes output by HDLM when the HDLM remote access interface sends a request to HDLM. Before viewing the list of messages (see section 9.1) HDLM command messages (see section 9.2) HDLM GUI messages (see section 9.
9.1 Before Viewing the List of Messages This section explains the following information that is needed to locate messages and understand the message explanations in the sections from 9.2. 9.1.1 Format and meaning of message IDs Terms used in messages and message explanations Message language Format and Meaning of Message IDs Each message has a message ID. Table 9.1 shows the format and meaning of message IDs. Table 9.
9.1.2 Terms Used in Messages and Message Explanations Table 9.2 shows the terms that may appear in messages and message explanations. Table 9.2 Terms Used in Messages and Message Explanations Terms Meaning aa...aa Variable (If a message contains two or more variables, they are displayed as bb...bb, cc...cc, and so on.) FO Failover Operation name Type of the operation that is entered after dlnkmgr in the command.
9.2 HDLM Command (dlnkmgr and Operations) Messages Message ID Message Details and Actions KAPL01001-I The HDLM command completed normally. Operation name = aa...aa, completion time = Details bb...bb The HDLM command completed successfully. aa...aa: clear, help, offline, online, set, view bb...bb: the year of grace/month/day hour:minute:second Action None. KAPL01002-I The HDLM command started. Operation name = aa...aa Details The HDLM command was executed. aa...
Message ID Message Details and Actions KAPL01007-W A duplicate parameter is specified. Operation name = aa...aa, parameter = bb...bb Details aa...aa: clear, offline, online, set, view bb...bb: Duplicate parameter Action Delete the duplicate parameter, and then retry. KAPL01008-W A necessary parameter value is not specified. Operation name = aa...aa, parameter = bb...bb Details aa...aa: offline, online, set, view bb...bb: Parameter name Action Specify the parameter value, and then retry.
Message ID Message Details and Actions KAPL01014-W No authority to execute the HDLM command. Operation name = aa...aa Details You are not authorized to execute the HDLM command as the administrator. aa...aa: clear, offline, online, set, view Action Execute the command as a user with administrators group privileges. KAPL01015-W The target HBA was not found. Operation name = aa...aa Details The path having the port number and path number specified in the -hba parameter could not be found. aa...
Message ID Message Details and Actions KAPL01019-W The target path was not found. Operation name = aa...aa Details aa...aa: offline, online, view offline/online operation view operation The specified path does not exist. The paths have not been configured because creation of the HDLM environment or configuration changes to the HDLM operating environment have not finished.
Message ID Message Details and Actions 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. Action The load balancing function is not supported in an environment with MSCS installed. If you want to use the load balancing function, uninstall MSCS. KAPL01036-E The Offline path cannot be placed online. PathID = aa...aa Details The path could not be recovered. aa...
Message ID Message Details and Actions KAPL01045-W Too many parameter values are specified. Operation name = aa...aa, parameters = bb...bb, parameter value = cc...cc Details aa...aa: offline, online, set, view bb...bb: Parameter name cc...cc: Parameter value Action Execute help operation-name of the HDLM command (dlnkmgr) to check the parameter value, and then retry. For details on the help operation, see section 7.3. KAPL01046-I An offline request was registered in a batch job. PathID = aa...
Message ID Message Details and Actions KAPL01050-I The currently selected paths will be changed to the Online status. Is this OK? [y/n]: Details The online operation will be started. To continue the online operation, enter y. To cancel the operation, enter n. Action If you want to execute the online processing, enter y. If you want to terminate the processing, enter n. For details on the online operation, see section 7.5.
Message ID Message Details and Actions KAPL01055-I All the paths which pass the specified aa...aa will be changed to the Offline(C) status. Is this OK? [y/n]: Details Multiple paths will be collectively placed Offline(C) because the -hba or -cha parameter was specified. To collectively place multiple paths Offline(C), enter y. To not collectively place them Offline(C), enter n. aa...
Message ID Message Details and Actions KAPL01059-W Cannot specify the parameter aa...aa at the same time if you specify parameter bb...bb and parameter value cc...cc. Operation name = dd...dd Details A parameter value conflicts with the specification of another parameter. bb...bb: Parameter name cc...cc: Parameter value aa...aa: Parameter name dd...dd: view, set Action Execute help operation-name of the HDLM command (dlnkmgr) to check the parameter and parameter value, and then retry.
Message ID Message Details and Actions KAPL01062-I aa...aa path(s) were successfully placed Offline(C). The offline request of bb...bb path(s) were registered; cc...cc path(s) were not. Operation name = dd...dd Details This message indicates the number of paths that were processing when the offline request was registered during Reserve processing. aa...aa: Number of paths where offline is successful (decimal number) bb...bb: Number of paths for which offline was reserved (decimal number) cc...
Message ID Message Details and Actions KAPL01065-E The configuration does not support the simultaneous use of the load balancing and cluster support functions. Details If a storage system for which persistent reserve is not supported exists among the HDLMmanaged storage systems, the load balancing function cannot be used in the cluster environment. Action Make sure that all HDLM-managed storage systems support persistent reserve.
Message ID Message Details and Actions KAPL01074-E The emergency license expired. Details The emergency license expired. Register a permanent license. Action Register a permanent license. KAPL01075-E A fatal error occurred in HDLM. The system environment is invalid. Details A part of the HDLM configuration file is missing. Action Re-install HDLM. KAPL01076-I The permanent license has been installed.
Message ID Message Details and Actions KAPL01082-E There is no installable license key in the license key file. File name = aa...aa Details There is no HDLM-installable license key in the license key file. aa...aa: Windows-installationdestination-drivename\hdlm_license Action Make sure that the license key file is correct, and then re-execute. KAPL01083-I There is no license key file. File name = aa...aa Details There is no license key file in the designated directory: aa...
Message ID Message Details and Actions KAPL01089-E One of the following was executed at the same time as an HDLM command set -lic operation: another set -lic operation, or an update of the license for an update installation. Action Check the license by using the HDLM command's view -sys -lic operation. Then, if necessary, re-execute the HDLM command's set -lic operation. If the same error message is output, contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Message ID Message Details and Actions KAPL01098-W The storage system (aa...aa, bb...bb) cannot perform the cc...cc operation in units of CHA ports. Details Processing to place all paths Offline or Online via a specific CHA port cannot be performed on the EMC DMX series, the EMC CX series, and the HP EVA series. aa...aa: Vendor ID bb...bb: Product ID cc...cc: online/offline Action Execute, in units of paths, on a path that goes through the CHA port of the specified storage system. KAPL01100-I aa...
9.3 HDLM GUI Messages Message ID Message Details and Actions KAPL02001-I HDLM GUI has started normally. Action None. KAPL02002-I HDLM GUI has terminated. Action None. KAPL02003-E You lack permission to start HDLM GUI. Action Execute the command as a user with administrators group privileges. KAPL02004-E An error occurred during internal processing of HDLM GUI. HDLM GUI cannot start. Details = Details During GUI startup, an error that might not be caused by a user operation occurred. aa...
Message ID Message Details and Actions KAPL02007-E The HDLM manager could not be connected. The aa...aa operation has been stopped. Details During the Option window startup or Set Option Information operation, the system could not access the HDLM manager. aa...aa: Get Option Information or Set Option Information Action Execute the view operation of the HDLM command (dlnkmgr) to check whether the HDLM manager has started.
Message ID Message Details and Actions KAPL02014-W No data has been input in aa...aa. Details No value has been entered in the input field of the Option window. aa...aa: Input item 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. See section 6.
Message ID Message Details and Actions KAPL02016-W A value which is outside of the valid range has been input in aa...aa. Details The value entered in the input field of the Option window is not within the valid range. aa...
Message ID Message Details and Actions 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 confirmation to determine whether you want to change the selected path(s) to Offline(C) status. If you want to continue, click OK. If you do not want to proceed, click Cancel. Action If you want to execute the offline processing, click OK. To cancel the offline processing, click Cancel.
Message ID Message Details and Actions KAPL02026-W The target path of the aa...aa operation could not be found. Details The target path of the operation could not be found. aa...aa: Operation Online Clear Data CSV Output Get Path Information Refresh Action Click Refresh to update the view contents, check the path status, and then retry. KAPL02027-E The last Online path or Online(E) path to the LU cannot be placed in the Offline(C) status. PathID = aa...
Message ID Message Details and Actions KAPL02029-E An error occurred during internal processing of the HDLM GUI. The aa...aa operation has been stopped. Details = bb...bb Details During the GUI processing, an error which might not be caused by a user operation occurred. aa...
Message ID Message Details and Actions KAPL02032-E The aa...aa operation cannot be executed because the amount of memory is insufficient. Details There was not sufficient memory available for the HDLM GUI processing. aa...
Message ID Message Details and Actions KAPL02041-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. Action The load balancing function is not supported in an environment where MSCS is installed. If you want to use the load balancing function, uninstall MSCS. KAPL02042-E An unexpected error occurred. The HDLM GUI cannot start.
Message ID Message Details and Actions KAPL02054-I aa...aa path(s) were successfully placed Offline(C). The Offline request of bb...bb path(s) were registered. cc...cc path(s) could not be placed Offline(C). Details Indicates the number of the processed paths when the offline request was registered during the Reserve processing. aa...aa: The number of paths that succeeded in the offline processing (decimal number) bb...
Message ID Message Details and Actions KAPL02063-W The version number cannot be displayed. Details The version number couldn't be acquired because it failed in reading of a parameter file to start HDLM GUI. Action The version number cannot be displayed, but the operation of HDLM GUI can execute. If you want to display the version number, install the HDLM again.
Message ID Message Details and Actions KAPL02080-W All the current trace files will be deleted. Is this OK? [OK/Cancel] Details If you set a value less than the current value of the trace file size or number of trace files, all the current trace files will be deleted. To continue the operation, click OK. To cancel the operation, click Cancel. Action If you want to execute the operation, click OK. To cancel the operation, click Cancel. KAPL02083-I HDLM GUI is started by the user-specified JRE. aa...
9.4 HDLM API Messages Message ID Message Details and Actions KAPL03001-I HDLM API information - aa...aa Details This information is required for determining the cause of the problem (if any). aa...aa: Trace information Action None. KAPL03002-W HDLM API Warning - aa...aa Details This information is required for determining the cause of the problem (if any). aa...aa: API trace information Action Refer to the contents of the warning. KAPL03003-E HDLM API Error information - aa...
Message ID Message Details and Actions KAPL03007-E An error occurred during communication with the HDLM manager. (aa...aa) Details This information is required for determining the cause of the problem (if any). 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. For details on the DLMgetras utility, see section 8.2.
9.5 HDLM Manager Messages Message ID Message Details and Actions KAPL04001-I HDLM manager started. Action None. KAPL04002-E Could not start the HDLM manager. Details HDLM manager failed to start because the environment is incorrect for the manager to run properly. 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 section 8.2.
Message ID Message Details and Actions KAPL04008-E Cannot open the option definition file (aa...aa). Details HDLM manager cannot start normally (unable to open the option definition file). aa...aa: Option definition file name Action Check whether another program is using the file (or has opened the file with Notepad), or whether the file has been deleted inadvertently. KAPL04009-E The option definition is invalid.
Message ID Message Details and Actions KAPL04013-E Input is impossible via the communication pipe. RC = aa...aa Details Data could not be read from the pipe file during the communication with the HDLM command. aa...aa: operating system error code (decimal number) 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 section 8.2.
Message ID Message Details and Actions KAPL04023-E HDLM manager error information - aa...aa Details This information is required for determining the cause of the problem (if any). aa...aa: HDLM manager 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. For details on the DLMgetras utility, see section 8.2.
Message ID Message Details and Actions KAPL04031-E The emergency license has already expired. Action Install the permanent license. KAPL04032-C A fatal error occurred in HDLM. The system environment is invalid Details A part of the HDLM configuration file is missing. Action Re-install HDLM. KAPL04033-W The option definition file was re-created. Details An option definition file was re-created using the default values. The specified values are set when some of the options have been read.
Message ID KAPL04045-I Message Details and Actions HDLM SNMP TRAP was sent. Trap ID = Details aa...aa, IP Address = bb...bb, Port Number= cc...cc, Community = dd...dd, Trap Data = ee..ee aa...aa: Trap ID 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: Send data Action None.
9.6 HDLM Driver (Filter Component) Messages Message ID Message Details and Actions KAPL05001-I DriverEntry() started. Details The initialization function was executed (started). 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).
Message ID Message Details and Actions KAPL05010-E Could not initialize the HDLM driver (filter component). (aa...aa:bb...bb) Details The HDLM driver (filter component) could not be initialized for each device object. aa...aa and bb...bb: Device object address (aa...aa and bb...bb: Fixed to 0) Action Check whether the HDLM driver has started normally.
Message ID Message Details and Actions KAPL05014-I The device object (aa...aa) was registered as the path (bb...bb). Details 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 in the core logic. Action None. KAPL05018-W The FO processing in the path (aa...aa) failed. (bb...bb:cc...cc) Details There is no path where FO processing is to be performed. Path (aa...
Message ID Message Details and Actions KAPL05033-W The path health checking for the path (aa...aa) failed.(bb...bb,cc...cc,dd...dd) Details aa...aa: Path ID (hexadecimal number) bb...bb: Disk sequence number (decimal number) cc...cc: Degree of progress in health checking (hexadecimal number) dd...dd: Execution result of health checking (hexadecimal number) Action Check the path for which the path health checking failed.
Message ID Message Details and Actions KAPL05301-E A path has been removed. Details When the LU deletion functionality is available, the path information is output to the event log. The removed path information is displayed in the event viewer with the following format: PathID PathName DskName iLU ChaPort When a path is added to an LU, this message might appear. Note that this message is output by Windows activities, and not by an error.
9.7 HDLM Driver (Core Logic Component) Messages Message ID KAPL07819-I Message Details and Actions Data for maintenance: aa...aa bb...bb Details cc...cc dd...dd. This message is generated by the core logic for maintenance. aa...aa: Detailed information 1 (decimal number) bb...bb: Internal function number of the core logic (decimal number) cc...cc: Detailed information 2 (decimal number) dd...dd: Detailed information 3 (decimal number) Action None.
Message ID Message Details and Actions KAPL07823-W An LU connected to PathID (aa...aa) can also use the load balancing function in a cluster configuration. Details An LU connected to the PathID shown as aa...aa is an LU of a storage system that can use the persistent reservation. In a cluster configuration, the load balancing function can also be used for this LU. aa...aa: Path ID (same as PathID of view -path) Action None.
9.8 HDLM Management Target Messages Message ID Message Details and Actions KAPL08019-E The path (aa...aa) detected an error (bb...bb). (cc...cc) Details An error occurred in the path because of a condition such as a disconnection. aa...aa: Path identifier (hexadecimal number) bb...bb: Error code (hexadecimal number) When a path error was detected by path health checking or an online operation 0x000F0000(Fixed) is displayed.
Message ID Message Details and Actions KAPL08023-I A path was recovered. PathID = aa...aa, PathName = bb...bb.cc...cc.dd...dd.ee...ee, DNum = ff...ff, HDevName = gg...gg Details The path was recovered from the error. aa...aa: Path ID (same as PathID of view path) (decimal number) bb...bb: Host port number (same as PathName of view -path) (hexadecimal number) cc...cc: Bus number (same as PathName of view -path) (hexadecimal number) dd...
Message ID Message Details and Actions KAPL08026-E An error occurred on all the paths of the LU. PathID = aa...aa Details An error occurred in the last path of one LU because of a condition such as a disconnection. aa...aa: Path ID (same as PathID of view path) (decimal number) Action Find the KAPL05301-E message in the event log to identify the storage sub system the error was detected and recover from the error. KAPL08027-E A path was excluded from the items subject to automatic failback.
9.9 HDLM Installation Program Messages Message ID Message Details and Actions KAPL09001-E There is no system management permission. Details The current user does not have the administrator permission to install HDLM. Action Execute the program as a member of the Administrators group. KAPL09002-E KAPL09003-E The disk does not have sufficient free space. Action Cannot install in this system.
Message ID Message Details and Actions KAPL09001-E There is no system management permission. Details The current user does not have the administrator permission to install HDLM. Action Execute the program as a member of the Administrators group. KAPL09009-E The license code is invalid. The HDLM installation program will now terminate. Details The HDLM installation program is terminating because multiple attempts to enter the license code failed.
Message ID Message Details and Actions KAPL09001-E There is no system management permission. Details The current user does not have the administrator permission to install HDLM. Action Execute the program as a member of the Administrators group. KAPL09021-E An attempt to register the bundle PP name of Hitachi Network Objectplaza Trace Library 2 failed. Details An attempt to register the PP name of HNTRLib 2 has failed.
Message ID Message Details and Actions KAPL09001-E There is no system management permission. Details The current user does not have the administrator permission to install HDLM. Action Execute the program as a member of the Administrators group. KAPL09079-I The permanent license has been installed. Action None. KAPL09080-I The temporary license has been installed. The license expires on aa...aa. Details aa...
Message ID Message Details and Actions KAPL09001-E There is no system management permission. Details The current user does not have the administrator permission to install HDLM. Action Execute the program as a member of the Administrators group. KAPL09089-W License information cannot be acquired. Details License information cannot be acquired from the already installed HDLM environment. Action When the message that prompts you to install the license is displayed, install the license.
Message ID Message Details and Actions KAPL09001-E There is no system management permission. Details The current user does not have the administrator permission to install HDLM. Action Execute the program as a member of the Administrators group. KAPL09114-I There is no license key file. File name = aa...aa Details There is no license key file in the designated directory. aa...
Message ID Message Details and Actions KAPL09001-E There is no system management permission. Details The current user does not have the administrator permission to install HDLM. Action Execute the program as a member of the Administrators group. KAPL09127-W The MPIO driver has already been installed in this system. Driver aa...aa has already been installed. The file version is bb...bb. Driver aa...aa has already been installed. The file version could not be acquired. If installation continues, dd...
Message ID Message Details and Actions KAPL09001-E There is no system management permission. Details The current user does not have the administrator permission to install HDLM. Action Execute the program as a member of the Administrators group. KAPL09131-W An attempt to register the PRSV key has failed. Details An attempt to register the PRSV key has failed.
Message ID Message Details and Actions KAPL09001-E There is no system management permission. Details The current user does not have the administrator permission to install HDLM. Action Execute the program as a member of the Administrators group. KAPL09134-E The HDLM path cannot be added to the Path environment variable. Details The HDLM path could not be added to the Path environment variable.
Message ID Message Details and Actions KAPL09001-E There is no system management permission. Details The current user does not have the administrator permission to install HDLM. Action Execute the program as a member of the Administrators group. KAPL09135-E One of the following was executed at the same time as an HDLM command set -lic operation: another set -lic operation, or an update of the license for an update installation.
Message ID Message Details and Actions KAPL09001-E There is no system management permission. Details The current user does not have the administrator permission to install HDLM. Action Execute the program as a member of the Administrators group. KAPL09174-E HDLM cannot be installed because automatic name generation for files and folders (NTFS 8.3) is disabled. Details HDLM cannot be installed if "8.3-format short names" is not created for "%CommonProgramFiles%\InstallShield\Engine\6\I ntel 32".
Message ID Message Details and Actions KAPL09001-E There is no system management permission. Details The current user does not have the administrator permission to install HDLM. Action Execute the program as a member of the Administrators group. KAPL09183-I HDLM version aa...aa is installed. This version will now be overwritten with version bb...bb. Details aa...aa: Version number of the installed HDLM (character string). bb...bb: Version number of the HDLM you tried to install (character string).
Message ID Message Details and Actions KAPL09001-E There is no system management permission. Details The current user does not have the administrator permission to install HDLM. Action Execute the program as a member of the Administrators group. KAPL09189-W The parameter contains an incorrect value. (Value = aa...aa) Details Either -f or -h must be specified as the first parameter of installhdlm.exe. aa...aa: Invalid parameter (character string) Action Make sure that the parameters for installhdlm.
Message ID Message Details and Actions KAPL09001-E There is no system management permission. Details The current user does not have the administrator permission to install HDLM. Action Execute the program as a member of the Administrators group. KAPL09194-W A folder or file specified in the installation information settings file does not exist. (aa...aa = bb...bb) Details The folder or file specified for a key does not exist aa...
Message ID Message Details and Actions KAPL09001-E There is no system management permission. Details The current user does not have the administrator permission to install HDLM. Action Execute the program as a member of the Administrators group. KAPL09501-E HDLM is not installed on this system. Details The SP cannot be applied because HDLM is not installed in this system. Action Check whether HDLM has been correctly installed.
9.10 Messages from the DLMgetras Utility for Collecting HDLM Error Information Message ID Message Details and Actions KAPL10001-W No parameter has been specified. Details No parameter (folder to which collected information is output) has been specified. Action Check the parameters of the DLMgetras utility for collecting HDLM error information, and then retry. For details on the DLMgetras utility, see section 8.2. KAPL10002-W Too many parameters have been specified.
Message ID Message Details and Actions KAPL10012-W The specified file or directory does not exist. Line = aa...aa, Value = bb...bb Details The specified file or folder does not exist in the file for defining the information to be collected. aa...aa: Line number of the file for defining information to be collected (decimal number) bb...
Message ID Message Details and Actions KAPL10032-W The entered value is invalid. The utility for collecting HDLM error information stops. Details Processing of the DLMgetras utility for collecting HDLM error information will terminate because an invalid response was sent three times to a request. Action Re-execute the DLMgetras utility. For details on the DLMgetras utility, see section 8.2. KAPL10033-W The file does not exist. Filename = aa...aa Details The file subject to collection does not exist.
Message ID Message Details and Actions KAPL10045-W A parameter is invalid. Details The specified parameter is invalid. Action Make sure that the parameters for the DLMgetras utility for collecting HDLM error information are appropriate, and then try again. KAPL10046-W A parameter value is invalid. Details The specified parameter is invalid. Action Make sure that the parameters for the DLMgetras utility for collecting HDLM error information are appropriate, and then try again.
9.11 Messages from the dlmpr Utility for Canceling the HDLM Persistent Reserve Message ID Message Details and Actions KAPL10640-I The dlmpr utility completed normally. Details The dlmpr utility for canceling the HDLM persistent reserve finished normally. Action None. For details on the dlmpr utility, see section 8.3. KAPL10644-W The specified parameters cannot be specified at the same time. parameter = aa...aa Details aa...
Message ID Message Details and Actions KAPL10656-I The persistent reservation information of PathID = aa...aa will be cleared. Is this OK? [y/n]: Details We recommend that you report the path ID of the LU for which you want to clear persistent reservation information to the user for confirmation. aa...aa: The path ID Action Enter y to execute clearing, or n to cancel. KAPL10657-I If you continue this process, the reservation of the LU you specified will be cleared.
Message ID Message Details and Actions KAPL10664-E An attempt to acquire Inquiry data failed. PortNo = aa...aa, Error Code = bb...bb Details An error occurred in the issuing of IOCTL_SCSI_GET_INQUIRY_DATA for a SCSI controller. Port No is the number of the port of the SCSI controller to which IOCTL_SCSI_GET_INQUIRY_DATA is issued. aa...aa: PortNo (hexadecimal number) bb...
9.12 Messages from the HDLM Remote Access Interface Message ID Message Details and Actions KAPL11901-I aa...aa has started. Details The operation has started on the host. aa...aa: Operation (character string) Get Path Information Get Option Information Set Option Information Clear Data Get HDLM Manager Status Get HDLM Driver Status Get HDLM Alert Driver Status Action None. KAPL11902-I aa...aa has started. PathID = bb...bb Details The operation has started on the host. aa..
Message ID Message Details and Actions KAPL11904-E aa...aa has completed abnormally. Error status = bb...bb Details Operation has completed abnormally on the host. aa...aa: Operation (character string) Get Path Information Get Option Information Set Option Information Clear Data Get HDLM Driver Status Get HDLM Manager Status Get HDLM Alert Driver Status Online Offline Get SNMP Trap Information Set SNMP Trap Information Set LU Load Balance bb...
Message ID Message Details and Actions KAPL11908-I XML transmission - aa...aa Details This information is required for determining the cause of the problem (if any). aa...aa: XML information (character string) Action None. 9.13 Messages from the dlmprsvkey Utility for Registration of the HDLM Persistent Reserve Message ID Message Details and Actions KAPL12101-W A parameter has not been specified.
Message ID Message Details and Actions KAPL12105-W The user does not have permission to execute the utility for registering HDLM persistent reservation key. Details The dlmprsvkey utility for registering HDLM persistent reservation key must be executed by a user with administrator privileges. Action Try again as a user with administrator privileges. For details on the dlmprsvkey utility, see section 8.4. KAPL12106-I An attempt to register the PRSV key was successful. (PRSV key = aa...aa) Details aa.
Message ID Message Details and Actions KAPL12112-E An error occurred during internal processing of the utility for registering the HDLM persistent reservation key . Details = aa...aa, bb...bb Details An error, probably not caused by the user, occurred during processing of the dlmprsvkey utility for registering HDLM persistent reservation key. aa...aa: Error detail bb...
Message ID Message Details and Actions KAPL12117-I Trace data for maintenance: registered PRSV key = aa...aa Details Output when PRSV key registration is successful. aa...aa contains the PRSV key (hexadecimal number). Message for trace logs. Action None. KAPL12118-E Trace data for maintenance: aa...aa bb...bb cc...cc dd...
9.14 Messages from the HDLM Performance Monitor Message ID Message Details and Actions KAPL12150-E An error occurred during internal processing of HDLM Performance Monitor. HDLM Performance Monitor cannot start. Details = Details aa...aa An attempt to start HDLM Performance Monitor has failed. aa...aa: Error details (character string) Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
9.15 Messages from the dlmchkpath Utility for Checking HDLM Paths Message ID Message Details and Actions KAPL12401-I All LUs managed by HDLM are in a single path configuration. Details 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]... Details The LU of the LU number in the message is not in a single path configuration. aa...aa: LU number bb...bb,cc...
Message ID Message Details and Actions 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. If it has, contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
9.16 Return Codes for the HDLM Remote Access Interface The HDLM remote access interface is an interface used by other HiCommand products to access hosts. HDLM outputs a return code when the operation that the HDLM remote access interface requested to HDLM terminates abnormally, or when there is a warning while the operation terminates normally. Return Code Details and Actions 1002 Details There is no path on which the operation can be performed.
Return Code Details and Actions 1018 Details The load balancing function is not supported because MSCS is installed. Action The load balancing function is not supported in an environment with MSCS installed. If you want to use the load balancing function, uninstall MSCS from the host. 1019 Details An error occurred during HDLM internal processing.
Return Code Details and Actions 1026 Details The getting Path Information has been stopped because the configuration of paths was changed during the processing of the getting Path Information. Action Refresh the host information, check the path status, and then perform the operation again. 1027 Details The error monitoring interval and the number of times that the error is to occur conflict with the automatic failback checking interval.
Return Code Details and Actions 1038 Details A storage system that cannot use the load balancing function is connected. Action Please check a system configuration. One or more connected storage system(s) cannot use the load balancing function. The load balancing function does not operate on the LUs of that storage system. 1041 Details An attempt to communicate with the HDLM Manager has failed. Action Check whether the HDLM Manager is running on the host. If it is not running, start the HDLM Manager.
372 Chapter 9 Messages
Appendix A A.1 Functionality differences between version 5.9.1 and versions earlier than 5.9.1 A.2 A.3 A.1.1 Functionality Differences Between HDLM Versions In HDLM 5.9.1, the initial window of the Path Management window of the HDLM GUI has been changed from the Configuration view to the Path List view. Functionality differences between version 5.9 and versions earlier than 5.9 In HDLM 5.
– SCSI devices are connected and all Offline(E) paths are subject to automatic failback. – SCSI devices are connected to the Offline(C) paths. Offline(E) Paths, where intermittent errors are thought to have occurred When the following conditions are satisfied, the connected Offline(E) paths are automatically placed Online: 374 – All the online paths are Online(E) and SCSI devices connected to the Online(E) paths have been deleted. – The SCSI devices are connected to the Offline(E) paths.
Offline(E) Paths, where intermittent errors are not thought to have occurred If one of the following conditions exists, Online(E) paths will automatically change to Online.
A.2 Differences in LU Dynamic Removal Functionality Depending on the HDLM version, LU dynamic removal functionality differs as follows: In HDLM 5.2 or 5.4 – When Remove the LU even if there are Offline(C) paths is not specified (or when the following HDLM command is executed: dlnkmgr set -rmlu on) If none of the paths connected to the LU is Online or Offline(C), the LU will be removed from being an HDLM management-target.
A.4 Differences in Default Values Depending on the HDLM version, default values for the HDLM functionality differ as follows: A.5 Default value for path health checking – In HDLM 4.0 or earlier: OFF – In HDLM 5.0 or later: ON. The checking interval is 30 minutes. Default value for error log file size – In HDLM 5.4 or earlier: 1000 KB. Note that this item name in HDLM 5.4 or earlier is Log file size. – In HDLM 5.
378 Appendix A Functionality Differences Between HDLM Versions
Acronyms and Abbreviations AL API arbitrated loop application programming interface BIOS basic input/output system CA CCI CHA CL CLPR CS CSV CU channel adapter command control interface channel adapter cluster cache logical partition cluster support comma separated value control unit DEV device EMC CX series EMC DMX series EMC CLARiiON CX series EMC Symmetrix DMX series HDLM HDLM GUI HLU HiCommand Dynamic Link Manager Windows application GUI host logical unit I/O IA32 IP IPF iSCSI input/output
MVS Microsoft Windows Storage Server 2003 Enterprise x64 Edition multiple virtual storage NIC network interface card OS operating system P PRSV port persistent reserve SAN SCSI SLPR SNMP SVS storage-area network small computer system interface storage logical partition simple network management protocol HP StorageWorks 200 Storage Virtualization System TID target ID VSFW VxVM Veritas Storage Foundation for Windows Veritas volume manager Windows 2000 Server A generic term for Microsoft Windows
Windows Server 2003 R2 XP128 XP1024 XP10000 XP12000 Enterprise x64 Edition, Microsoft Windows Server 2003 R2, Standard x64 Edition, Microsoft Windows Server 2003 Standard x64 Edition, Microsoft Windows Storage Server 2003 R2, Enterprise x64 Edition, Microsoft Windows Storage Server 2003 R2, Express x64 Edition, Microsoft Windows Storage Server 2003 R2, Standard x64 Edition, Microsoft Windows Storage Server 2003 R2, Workgroup x64 Edition, Microsoft Windows Storage Server 2003 Enterprise x64 Edition, or Mic
382 Acronyms and Abbreviations
Glossary automatic failback Functionality for checking the status of paths at regular intervals and automatically placing the status of a path recovered from an error into Online status. If a path with Offline(E) or Online(E) status recovers from an error, automatic failback places the path Online.
384 dynamic reconfiguration Dynamic reconfiguration enables HDLM to recognize devices whose configuration has been changed without restarting the host using Windows plug and play functionality. emulation type An LU type accessible from a host. Since an HDLM host is an open-system host such as a PC or a UNIX machine, the HDLM host can access only LUs with open-system emulation types. For details on emulation types supported by a storage system, see the maintenance manual for that storage system.
host device name A logical area within a host LU. host LU An LU that the host recognizes. The actual HDev entity is a dev in the storage system. Each host LU has a host LU number. host LU number A number assigned to a host LU. The host LU number is part of a path name. IP-SAN (Internet protocol - storage area network) A data transfer network that connects hosts and storage systems using the iSCSI standard.
Universal Storage Platform V, all controllers are owner controllers. 386 owner path A path that provides the fastest access to an LU, using an owner controller. When using the Thunder 9200, or Thunder 9500V Series, the access speed to the LU varies depending on the path. A path that provides slower LU accesses than the owner path is called a nonowner path.
target host when an LU is deleted or all paths connected to the LU are placed in Offline(E) status. reservation The reservation functionality enables a host to declare that it has exclusive use of an LU, thus preventing other hosts from accessing that LU. Access permission for a reserved LU is given only to the host that issued the reservation, so the LU cannot be accessed from multiple paths simultaneously. As a result, load balancing is not possible.
388 Glossary
Index A active host ..........................................48 Algorithms for Load Balancing ...................24 Apply button in Options window............................ 211 automatic failback.......................... 29, 228 automatic failover .................................27 automatic path switching ........................27 B Basic function settings in Options window............................ 204 buffer size ........................................ 111 bus number ...........................
cluster software ................................48 EMC DMX series cluster software ................................48 EMC DMX series and CX series dlnkmgr view -lu.............................. 258 EMC DMX series and EMC CX series select the HDLM management-target device .................................................88 EMC DMX series EMC CX series, and HP EVA series available SAN environment ...................11 EMC DMX series, CX series, and HP EVA series notes.........................................
HDLM GUI Overview ................................ 5 HDLM installation program messages ....................................... 337 HDLM installation type new installation of HDLM......................58 re-installation of HDLM ........................58 upgrade installation of HDLM .................58 HDLM management target messages ....................................... 334 HDLM management-target devices .............10 HDLM manager .....................................18 messages .......................
LU configuration recognized by the host.......15 LUN........................................... 199, 255 in Path Management window (Path List view) ............................................... 200 M manual path switching ............................30 message examining...................................... 167 examining...................................... 172 examining...................................... 173 message level .................................... 290 messages from HDLM API ..............
in Path Management window (Path List view) ............................................... 196 P P 12, 14 path ............................................. 11, 12 checking the configuration.................. 110 path error handling ........................................ 165 path health checking .................... 4, 41, 227 Path ID in Path Management window (Path List view) ............................................... 198 path information exporting to CSV file .........................
system configuration ......................... 11, 12 T TagmaStore USP Path Management window (Configuration view) ........................................ 188 taking actions for hardware error................................ 168 program error ..................... 171, 173, 174 Target Id .................................... 199, 255 the DLMgetras utility for collecting HDLM error information messages ....................................... 352 trace file ............................................
HiCommand® Dynamic Link Manager (HDLM) for Windows® Systems User’s Guide 395
