Page 1 Hitachi Command Suite Dynamic Link Manager Software User Guide (for Windows(R)) Document Organization Product Version Getting Help Contents MK-92DLM129-21...
Page 2 © 2011 Hitachi, Ltd., Hitachi Data Systems Corporation. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd.
Page 3: Table Of Contents
Contents Preface....................xi Intended audience....................xii Product version......................xii Release notes......................xii Document revision level....................xii Document organization.....................xii Referenced documents.....................xiii Document conventions.....................xiii Convention for storage capacity values..............xv Getting help......................xvi Comments......................xvi 1 Overview of HDLM................1-1 What is HDLM?.......................1-2 HDLM Features.......................1-3 2 HDLM Functions...................2-1 Devices Managed by HDLM..................2-3 System Configuration....................2-3 System Configuration Using an FC-SAN..............2-3 System Configuration Using an IP-SAN...............2-4...
Page 4 Automatic Failovers................2-17 Automatic Failbacks................2-18 Manual Path Switching..................2-19 Path Status Transition..................2-20 The Online Path Statuses...............2-20 The Offline Path Statuses...............2-21 Status Transitions of a Path..............2-21 Monitoring Intermittent Errors (Functionality When Automatic Failback Is Used)..2-24 Checking Intermittent Errors................2-24 Setting Up Intermittent Error Monitoring............2-25 Intermittent Error Monitoring Actions...............2-25 When an Intermittent Error Occurs............2-25 When an Intermittent Error Does Not Occur..........2-26...
Page 5 HDLM Installation Types..................3-13 Notes on Creating an HDLM Environment...............3-14 Notes on HBAs and HBA Drivers...............3-14 Notes on Storage systems................3-14 Notes on HDLM Versions.................3-14 Notes on Windows..................3-16 Notes on Related Software................3-19 Notes on New Installations and Upgrade Installations........3-22 Notes on Migration or Upgrade Installation............3-24 Installing HDLM....................3-24 Preparations for a New Installation of HDLM.............3-25 Preparations for Installing HDLM by Performing an Unattended Installation..3-26...
Page 6 Uninstalling Hitachi Network Objectplaza Trace Library (HNTRLib2)....3-89 Clearing the Persistent Reservation..............3-90 4 HDLM Operation................... 4-1 Notes on Using HDLM..................... 4-2 Using a Storage Management Program...............4-2 Upgrading Windows..................4-2 Using MSCS......................4-2 When the Number of Displayed Paths Is Less than the Actual Number of Paths ......................4-2 When a System Event Occurs in an MSCS Environment......4-2 Using the EMC DMX series, EMC CX series, and HP EVA series......
Page 7 Examining the Messages................... 5-5 Obtaining Path Information................5-5 Identifying the Error Path..................5-6 Narrowing Down the Hardware That Might Have Caused the Error.......5-6 Identifying the Error Location and Correcting any Hardware Errors.......5-6 Placing the Path Online..................5-6 What To Do for a Program Error................5-7 Examining the Messages...................5-7 Obtaining Program Information.................5-7 What To Do for the Program Error..............5-7...
Page 8 To Display the Format of the view Operation...........6-31 Parameters.....................6-31 Parameters Used When Displaying Program Information......6-31 Parameters Used When Displaying HDLM Management-target Device Information...................6-37 Parameters Used When Displaying Path Information........6-38 Parameters Used When Displaying LU Information........6-52 Parameter Used When Displaying the Format of the view Operation..6-65 7 Utility Reference...................7-1 Overview of the Utilities..................7-2 The DLMgetras Utility for Collecting HDLM Error Information........7-2...
Page 9 KAPL09001 to KAPL10000..................8-57 KAPL10001 to KAPL11000..................8-80 KAPL11001 to KAPL12000..................8-89 KAPL12001 to KAPL13000..................8-91 KAPL13001 to KAPL14000..................8-99 KAPL15001 to KAPL16000..................8-102 Return Codes for Hitachi Command Suite Common Agent Component.....8-105 Events Output to Windows Event Logs by HDLM............8-110 A Functional Differences Between Versions of HDLM........A-1 Functional Differences Between Version 6.6 or Later and Versions Earlier Than 6.6..A-3 Functional Differences Between Version 6.2 or Later and Versions Earlier Than 6.2..A-3 Functional Differences Between Version 6.0.1 or Later and Versions Earlier Than 6.0.1...
Page 10 Hitachi Dynamic Link Manager User Guide (for Windows(R))
Page 11: Preface
Preface This document describes how to use the Hitachi Dynamic Link Manager. □ Intended audience □ Product version □ Release notes □ Document revision level □ Document organization □ Referenced documents □ Document conventions □ Convention for storage capacity values □...
Page 12: Intended Audience
Intended audience This manual is intended for system administrators who use Hitachi Dynamic Link Manager (HDLM) to operate and manage storage systems. The readers of this manual must have a basic knowledge of the following areas: • Windows and its management functionality •...
Page 13: Referenced Documents
Chapter Description configure an environment to properly operate HDLM, such as changing the HDLM management-target devices that connect paths or replacing the hardware that makes up a path. Chapter 4 also describes how to check path information by using the Windows management tool.
Page 14 These conventions are described below. General font conventions The following table lists the general font conventions: Font Convention Bold Bold type indicates text on a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels.
Page 15: Convention For Storage Capacity Values
Example font or Convention symbol Bold code-font characters indicate the abbreviation for a command. Underlined characters indicate the default value. perm Square brackets enclose an item or set of items whose specification is optional. An item that is underlined is specified when other items are omitted.
Page 16: Getting Help
Logical capacity unit Value 1 TB 1,024 GB or 1,024 bytes 1 PB 1,024 TB or 1,024 bytes 1 EB 1,024 PB or 1,024 bytes Getting help The Hitachi Data Systems customer support staff is available 24 hours a day, seven days a week.
Page 17: Overview Of Hdlm
Overview of HDLM HDLM is a software package that manages paths between a host and a storage system. HDLM is designed to distribute loads across multiple paths and will switch a given load to another path if there is a failure in the path that is currently being used, thus improving system reliability.
Page 18: What Is Hdlm
What is HDLM? With the widespread use of data warehousing and increasing use of multimedia data, the need for high-speed processing of large volumes of data on networks has rapidly grown. To satisfy this need, networks dedicated to the transfer of data, such as SANs, are now being used to provide access to storage systems.
Page 19: Hdlm Features
HDLM Features HDLM features include the following: The ability to distribute a load across multiple paths. This is also known as load balancing. When a host is connected to a storage system via multiple paths, HDLM can distribute the load across all the paths. This prevents one, loaded down path from affecting the processing speed of the entire system.
Page 20 Overview of HDLM Hitachi Dynamic Link Manager User Guide (for Windows(R))
Page 21: Hdlm Functions
HDLM Functions This chapter describes the various functions that are built into HDLM. Before the function specifications are explained though, this chapter will go into detail about the HDLM management targets, system configuration, and basic terms that are necessary to know to effectively operate HDLM. After that, the rest of the chapter focuses on describing all the HDLM functions, including the main ones: load distribution across paths and path switching.
Page 22 □ Integrated HDLM management using Global Link Manager □ Cluster Support HDLM Functions Hitachi Dynamic Link Manager User Guide (for Windows(R))
Page 23: Devices Managed By Hdlm
Devices Managed by HDLM Below is a list of devices that can or cannot be managed by HDLM. The devices that can be managed by HDLM are called HDLM management-target devices. HDLM management-target devices: The following devices are from the storage systems listed in Section What is HDLM? on page 1-2:...
Page 24: System Configuration Using An Ip-San
Figure 2-1 Configuration of an HDLM System When Using an FC-SAN on page shows the configuration of an HDLM system using an FC-SAN. Figure 2-1 Configuration of an HDLM System When Using an FC-SAN Table 2-1 HDLM System Components When Using an FC-SAN on page 2-4 lists the HDLM system components when using an FC-SAN.
Page 25 must be installed ahead of time on the host. The cable port on the storage system is called a port (P) on a channel adapter (CHA) used for iSCSI connections. A logical unit (LU), which lies in a storage system, is either an input target or an output target to or from a host.
Page 26 Figure 2-3 Configuration of an IP-SAN System When Using iSCSI Software and an NIC Table 2-2 HDLM System Components When Using an IP-SAN on page 2-6 lists the HDLM system components when using an IP-SAN. Table 2-2 HDLM System Components When Using an IP-SAN Components Description iSCSI software...
Page 27: Setting Range Of The Iscsi Software And Iscsi Hba
Components Description Path A route that connects a host to a Dev in an LU Setting Range of the iSCSI Software and iSCSI HBA The following describes the ranges that can be used for the iSCSI software and iSCSI HBA settings. For notes on how to set these values, see the corresponding documentation for your particular iSCSI software and iSCSI HBA.
Page 28 This means that each LU in the storage system is always recognized as only one LU, regardless of the number of paths that are connected to SCSI devices. You can display all the various SCSI devices from the Windows' Device Manager window.
Page 29: Program Configuration
Components Description HDev A Dev in an LU that the host recognizes via the HDLM driver. This type of Dev is called a host device. Program Configuration HDLM is actually a combination of several programs. Because each program corresponds to a specific HDLM operation, it is important to understand the name and purpose of each program, along with how they are all interrelated.
Page 30: Driver Levels Of The Hdlm And Mpio Drivers
Program name Functions • Set up the HDLM operating environment HDLM command Provides the dlnkmgr command, which enables you to: • Manage paths • Display error information • Set up the HDLM operating environment HDLM utility Provides the HDLM utility, which enables you to: •...
Page 31: Distributing A Load Using Load Balancing
Figure 2-6 Driver Levels of the HDLM and MPIO Drivers Distributing a Load Using Load Balancing When the system contains multiple paths to a single LU, HDLM can distribute the load across the paths by using multiple paths to transfer the I/O data. This function is called load balancing, and it prevents a single, heavily loaded path from affecting the performance of the entire system.
Page 32 VM, and Virtual Storage Platform. In a non-cluster environment, the load balancing function is available for the Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi AMS2000/AMS/WMS/SMS series, Hitachi USP, Universal Storage Platform V/VM, Virtual Storage Platform, and EMC DMX series. For details on the various cluster software that HDLM supports, see Cluster Support on page 2-44.
Page 33: Paths To Which Load Balancing Is Applied
Figure 2-8 Flow of I/O Data When the Load Balancing Function Is Used When the load balancing function is used, I/O operations are distributed via multiple paths (A, B, C, and D). This helps to prevent problems with system performance and helps prevent bottlenecks from occurring. Paths to Which Load Balancing Is Applied This subsection describes, for each type of storage system, the paths to which the load balancing function is applied.
Page 34: When Using The Lightning 9900 Series, Lightning 9900V Series, Hitachi Usp, Universal Storage Platform V/Vm, Virtual Storage Platform, Hitachi Ams2000 Series, Or Hitachi Sms
load balancing will be performed among the remaining, usable owner paths. It is only when absolutely no owner paths are available, that load balancing is then performed among the non-owner paths. For the example in Figure 2-9 Overview of Load Balancing on page 2-14, suppose that in the owner controller of LU0 is CHA0.
Page 35 • The Extended Round Robin algorithm • The Least I/Os algorithm • The Extended Least I/Os algorithm • The Least Blocks algorithm • The Extended Least Blocks algorithm The above algorithms are divided into two categories, which differ in their processing method.
Page 36: Performing Failovers And Failbacks Using Path Switching
Table 2-5 Features of the Load Balancing Algorithms Algorithm type Algorithm features • These types of algorithms are most effective when a lot of Round Robin discontinuous, non-sequential I/Os are issued. • Least I/Os • Least Blocks • Extended Round If the I/O data is from something like a read request and is Robin generally sequential with the previous I/Os, an improvement...
Page 37: Automatic Path Switching
means that the path cannot receive I/Os. A path will go into the offline status for the following reasons: • An error occurred on the path. • A user intentionally placed the path offline by using the Path Management window in the HDLM GUI. •...
Page 38: Automatic Failbacks
is placed offline, the switching destination can come from any of the other three paths (B, C, or D). Figure 2-10 Path Switching Automatic Failbacks When a path recovers from an error, HDLM can automatically place the recovered path back online. This function is called the automatic failback function.
Page 39: Manual Path Switching
HDLM automatically places the recovered path online, the path that is currently being used will continue to be used (as opposed to switching over to the path that was just recovered). When intermittent errors occur on paths and you are using the automatic failback function, the path status might frequently alternate between the online and offline statuses.
Page 40: Path Status Transition
6-10. After a path status is changed to online, the path can be selected as a useable path by HDLM in the same manner as automatic path switching. When using the Thunder 9500V series, or Hitachi AMS/WMS series, HDLM selects the path to use from online owner paths, and then from online non- owner paths.
Page 41: The Offline Path Statuses
The (E) means error, which indicates that an error has occurred on the path from some previous operation. • Online(EP) The status of an Offline(P) path changes to Online(EP) when the path goes through the following process during reserve processing in a cluster configuration: When exactly two paths are connected to an LU and the user performs an offline operation on the Offline(E) path to change it to...
Page 42 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. During reserve processing for an LU, the Online status is temporarily changed to Online(P).
Page 43 When the following conditions are all satisfied, a path that has been determined to have an intermittent error also becomes subject to automatic failback: All the paths connected to an LU are Online(E), Offline(E), or ¢ Offline(C). All the paths connected to an LU have been determined to have an ¢...
Page 44: Monitoring Intermittent Errors (Functionality When Automatic Failback Is Used)
hardware is then re-installed, HDLM will automatically place the path back online. However, this is the case only when there is no other cause or reason for the path being placed offline. In this case, because HDLM will automatically place the path back online without using the automatic failback function, you do not need to manually place the path online.
Page 45: Setting Up Intermittent Error Monitoring
Setting Up Intermittent Error Monitoring When you enable the intermittent error monitoring function, specify the following monitoring conditions: the error monitoring interval, and the number of times that the error needs to occur. If an error occurs on a particular path the specified number of times within the specified error- monitoring interval, then an intermittent error will occur on the path.
Page 46: When An Intermittent Error Does Not Occur
Figure 2-12 Action What Will Happen When an Intermittent Error Occurs on a Path When an Intermittent Error Does Not Occur If an error does not occur on a path a specified number of times within a specified interval, an intermittent error will not occur. In such a case, the error monitoring will finish when the specified error-monitoring interval finishes, upon which the number of errors is reset to 0.
Page 47: When The Conditions For An Intermittent Error Are Changed During Error Monitoring
As shown in Figure 2-13 What Will Happen When an Intermittent Error Does Not Occur on a Path on page 2-26, normally, the count for the number of times that an error occurs is started after the path is first recovered from an error by using the automatic failback function.
Page 48: When A User Changes The Intermittent Error Information
When a User Changes the Intermittent Error Information The following might be reset when a user changes any of the values set for the intermittent error or the path status: the number of errors that have already been counted during error monitoring, the amount of time that has passed since error monitoring has started, and the information about whether an intermittent error has occurred.
Page 49 Number of Information errors and time about paths passed since User operation not subject to error automatic monitoring failback started Changing the path Taking the path Offline(C) Reset Reset status Placing the path Online (Not applicable) Reset (Not counted.) while intermittent error monitoring is not being performed Placing the path Online...
Page 50: Detecting Errors By Using Path Health Checking
The number of errors and the time passed since error monitoring had started are both reset to 0, and then monitoring restarts from the time the HDLM manager starts. Detecting Errors by Using Path Health Checking HDLM can check the status of paths for which I/O operations are not being performed at regular intervals.
Page 51: Deleting An Lu Dynamically
Deleting an LU Dynamically The dynamic LU deletion function automatically removes an LU from under HDLM control when all the paths to that LU have been disconnected. You can use the dynamic LU deletion function by specifying the dlnkmgr command's set operation together with the -rmlu on parameter. You can also use this function from the Options window of the HDLM GUI.
Page 52: Types Of Collected Logs
Figure 2-15 Flow of Data When Collecting Error Information Logs might be collected in layers below HDLM, such as for the SCSI driver. For more details, see the Windows documentation. Types of Collected Logs HDLM collects information on detected errors and trace information and stores it into the integrated trace file, trace file, error logs and event logs.
Page 53 A system memory dump file is a file to which the system memory data is output when a Windows system is down. Specify the following procedure to output the system memory dump file. Click Control Panel, System, Startup/Shutdown, Write Debugging Information is chosen with Recovery, and then choose Kernel Memory Dump or Complete Memory Dump.
Page 54: Filtering Of Error Information
For Windows Server 2003 (excluding the x86 edition) and Windows Server 2008 (excluding the x86 edition), Program Files is Program Files (x86). The underlined part indicates the folder specified during the installation. After obtaining these files, be sure to also copy them to a backup location.
Page 55: Collecting Error Information Using The Utility For Collecting Hdlm Error Information (Dlmgetras)
Collects error information from the Error level and higher. ¢ Collects error information from the Warning level and higher. ¢ Collects error information from the Information level and higher ¢ (information from all the levels is collected). Collects error information from the Information level and higher ¢...
Page 56 Category Explanation • Startup and termination of software running on storage systems, software running on SVPs (service processors), and Hitachi Command Suite products An abnormal hardware or software event, including: Failure • Hardware errors • Software errors (such as memory errors) An event indicating the linkage status between devices: LinkStatus •...
Page 57: Categories And Audit Events That Hdlm Can Output To The Audit Log
Category Explanation An event indicating an abnormal state such as exceeding a AnomalyEvent threshold, including: • Exceeding a network traffic threshold • Exceeding a CPU load threshold • Reporting that the temporary audit log data saved internally is close to its maximum size limit or that the audit log files have wrapped back around to the beginning An event indicating an occurrence of abnormal...
Page 58 Severity Category Explanation Audit event Message ID Startup of the KAPL15201-I HDLM GUI was successful. Startup of the KAPL15204-W HDLM GUI failed. Termination of KAPL15202-I the HDLM GUI was successful. Administrator or Permission has KAPL15111-W Authentication end-user not been granted authentication to execute the HDLM command.
Page 59 Severity Category Explanation Audit event Message ID An attempt to KAPL15107-I display program information was successful. An attempt to KAPL15108-W display program information failed. An attempt to KAPL15109-I display HDLM management- target information was successful. An attempt to KAPL15110-W display HDLM management- target information failed.
Page 60: Requirements For Outputting Audit Log Data
Severity Category Explanation Audit event Message ID An attempt to KAPL15206-W perform an operation by using the HDLM GUI failed. Processing of the KAPL15030-I dlmprsvkey -r command was successful. Processing of the KAPL15031-W dlmprsvkey -r command failed. Processing of the KAPL15032-I dlmprsvkey -v command was...
Page 61: Destination And Filtering Of Audit Log Data
However, audit log data might still be output regardless of the above conditions if, for example, an HDLM utility is executed from external media. The following audit log data is output: Categories: StartStop, Authentication, and ConfigurationAccess ¢ Severity: 6 (Error, Warning, or Information) ¢...
Page 62: Audit Log Data Formats
Audit Log Data Formats The following describes the format of audit log data: The following is the format of audit log data. This data can be viewed in the Description box of the Event Properties dialog box, which is opened when an event is double-clicked in the Application Log list of the Event Viewer administrative tool: program-name [process-ID]: message-section...
Page 63: Integrated Hdlm Management Using Global Link Manager
Explanation Item Location identification Location identification information information FQDN Fully qualified domain name Redundancy Redundancy identification information identification information Agent information Agent information Host sending request Name of the host sending a request Port number sending Number of the port sending a request request Host receiving request Name of the host receiving a request...
Page 64: Cluster Support
Global Link Manager collects and manages information about paths from instances of HDLM installed on multiple hosts. Even if multiple users manage these hosts, they can control and view this centralized information from client computers. For an example of a system configuration using HDLM and Global Link Manager, see Figure 2-16 Example System Configuration Using HDLM and Global Link Manager on page...
Page 65 For example, in Figure 2-17 Path Switching in a Cluster Configuration on page 2-45, when HDLM uses a path (A) from the active host to access a device within the LU, if the path is placed offline, HDLM switches to another path (B) to continue processing.
Page 66 2-46 HDLM Functions Hitachi Dynamic Link Manager User Guide (for Windows(R))
Page 67: Creating An Hdlm Environment
Creating an HDLM Environment This chapter explains how to set up an HDLM environment and also how to erase environment settings. Make sure that you have already installed HDLM and configured the function settings. □ HDLM System Requirements □ Flow for Creating an HDLM Environment □...
Page 68: Hdlm System Requirements
HDLM System Requirements Check the following before installing HDLM: OSs Supported by HDLM This subsection describes the OSs, Microsoft MPIO drivers, and Web browsers supported by HDLM. Supported OSs You can install HDLM on any OS described in Table 3-1 Supported OSs on page 3-2.
Page 69: Microsoft Mpio Drivers
In this manual, Windows running on a 32-bit processor is referred to as x86. To use the Storport Miniport driver for the HBA driver in an environment where SP1 or later has not been installed, QFE update program QFE 838894 or later provided by Microsoft is required. Microsoft MPIO Drivers Table 3-2 Versions of the Microsoft MPIO Driver Bundled with HDLM on page lists the versions of the Microsoft MPIO driver bundled with HDLM.
Page 70 Table 3-3 Supported Storage systems Supported storage Interfa Windows Server 2003 Windows Server 2008 systems FC I/F EMC DMX series FC I/F EMC CX series • Hitachi AMS FC I/F • Hitachi WMS iSCSI I/ Hitachi AMS2000 series FC/IF Hitachi SMS FC I/F iSCSI I/ •...
Page 71: Hbas
Legend: Y: Usable --: Not usable FC I/F: FC Interface iSCSI I/F: iSCSI Interface Dual controller configuration is required. The evaluation of EMC DMX3000 has been completed. Response to inquiries for other systems of the EMC DMX series must be the same as that of the EMC DMX3000.
Page 72: Cluster Software Supported By Hdlm
Table 3-4 Related Programs When Intermediate Volumes Managed by Hitachi RapidXchange Are Used to Exchange Data Related programs Windows Server 2003 R2 File Access Library and File Conversion Utility (FAL/FCU) (x64) SP2 01-05-66/25 or later Windows Server 2003 File Access Library and File Conversion Utility (FAL/FCU) (x86) 01-03-64/21 or later 01-04-64/20 or later...
Page 73 Table 3-5 Supported Cluster Software Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP, Cluster Hitachi software AMS2000/ name AMS/WMS/ series series series SMS series, Universal Storage Platform V/VM, and Virtual Storage Platform Windows Server MSCS service 2003 (IPF) pack MSCS VCS 5.0...
Page 74 Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP, Cluster Hitachi software AMS2000/ name AMS/WMS/ series series series SMS series, Universal Storage Platform V/VM, and Virtual Storage Platform Oracle RAC MSCS VCS 4.3, 5.0 Oracle RAC Oracle RAC Windows Server MSCS service...
Page 75 Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP, Cluster Hitachi software AMS2000/ name AMS/WMS/ series series series SMS series, Universal Storage Platform V/VM, and Virtual Storage Platform Windows Server MSCS service 2003 R2 (x86) VCS 4.3, 5.0 pack Oracle RAC Oracle RAC...
Page 76 Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP, Cluster Hitachi software AMS2000/ name AMS/WMS/ series series series SMS series, Universal Storage Platform V/VM, and Virtual Storage Platform MSCS Oracle RAC Windows Server MSCS 2008 R2(x64) service VCS 5.1 pack Oracle RAC Oracle RAC...
Page 77: Volume Managers Supported By Hdlm
- Windows Server 2003 (x64) Notes: When you use HDLM in a cluster configuration, you must install the ¢ same version of HDLM on all the nodes that make up the cluster. If different versions of HDLM are installed, the cluster system might not operate correctly.
Page 78: Memory And Disk Capacity Requirements
Memory and Disk Capacity Requirements This section describes memory and disk capacity requirements. Memory Requirements Table 3-7 Memory Requirements for a Host on page 3-12 lists the memory requirements for a host. Table 3-7 Memory Requirements for a Host HDLM GUI Required memory Not used Windows...
Page 79: Number Of Paths Supported In Hdlm
Number of Paths Supported in HDLM Table 3-9 Number of LUs and Paths Supported in HDLM on page 3-13 lists the number of LUs, the number of paths for an individual LU, and the total number of paths supported in HDLM. Table 3-9 Number of LUs and Paths Supported in HDLM Item Number supported...
Page 80: Notes On Creating An Hdlm Environment
Installing HDLM 5.5 or later after uninstalling HDLM 5.4 or earlier is called a migration of HDLM. By doing this, you can keep the settings from the previous version. Re-installation of HDLM: Installing the same version of HDLM, in order to restore the existing version, without first uninstalling that version is called a re-installation of HDLM.
Page 81 described in Migrating from HDLM 5.4 or Earlier to HDLM 5.5 or Later on page 3-64. • For HDLM 5.6 or later, the trace files for HDLM versions earlier than 5.6 are divided into integrated trace files and trace files. The logs for the HDLM commands and HDLM GUI operations are output to integrated trace files.
Page 82: Notes On Windows
• When you use HDLM in a cluster configuration, you must install the same version of HDLM on all the nodes that make up the cluster. If different versions of HDLM are installed, the cluster system might not operate correctly. If the HDLM Version and Service Pack Version, which are displayed by executing the following command, are the same, then the versions of HDLM will also be the same: >dlnkmgr view -sys -sfunc...
Page 83 Windows-installation-drive:\Program Files (x86)\HDVM\HBaseAgent \util\bin HDLM-installation-folder\bin HDLM-installation-folder\lib For other versions of Windows: Windows-installation-drive:\Program Files\Common Files\Hitachi Windows-installation-drive:\Program Files\HDVM\HBaseAgent\bin Windows-installation-drive:\Program Files\HDVM\HBaseAgent\util \bin HDLM-installation-folder\bin HDLM-installation-folder\lib For Windows Server 2003 SP1 and Windows Server 2003 R2 (with no service pack), if you do not want to use one of the above methods, you can use a Microsoft hotfix to start the HDLM manager.
Page 84 An application that uses the dmaadmin service is being executed. ¢ This error does not affect the data on the HDLM management-target devices. If you restart the host and then activate the disk in the Disk Management window of Windows, this error will not appear. To prevent this error from occurring, perform the following before installing HDLM: When a mirror disk volume that uses a dynamic disk exists among the ¢...
Page 85: Notes On Related Software
If the disk is not used as a cluster resource: ¢ In the Windows' Disk Management windows, offline the disk. If the disk is used as a cluster resource: ¢ Stop Cluster Service. • Windows Server 2008 supports user account control (UAC). If you are logged on with a non-administrator account, use the Administrator: Command Prompt window when executing any of the following programs to install or uninstall HDLM:...
Page 86 • If you attempt to install HDLM on a Windows Server 2003 host on which an MPIO driver has already been installed, and the MPIO driver version differs from that of the driver bundled with HDLM, the KAPL09127-W message is output. This message asks whether it is OK to overwrite the existing MPIO driver.
Page 87 If you are installing HDLM on Windows Server 2008, do not delete the ¢ multi-path I/O feature from the Server Manager. • When a host is connected to an Oracle RAC voting disk via multiple paths, if an I/O timeout occurs for any one of these paths, HDLM will perform a failover.
Page 88: Notes On New Installations And Upgrade Installations
Number of paths connecte Formula for obtaining the value Storage system type d to the of DISKTIMEOUT voting disk • Hitachi USP 4 or more number-of-paths-connected-to-the- • Universal Storage voting-disk x 60 seconds Platform V/VM • Virtual Storage Platform • Hitachi AMS2000/AMS/ 6 or less You do not need to change the value...
Page 89 specified in the license key file or the input license key type. For information on license key types and the set operation, see set (Sets Up the Operating Environment) on page 6-15 • Installing HDLM requires 70 MB of unused capacity on the system drive. •...
Page 90: Notes On Migration Or Upgrade Installation
unattended installation, see The installhdlm Utility for Installing HDLM on page 7-16. • After all HDLM components have been installed on a host, if you want to create a configuration that uses only the HDLM Core components, you cannot do so by performing an upgrade installation or re-installation. To re-configure HDLM with only the HDLM Core components, first uninstall HDLM, and then perform an unattended new installation of HDLM.
Page 91: Preparations For A New Installation Of Hdlm
When you install HDLM, Hitachi Network Objectplaza Trace Library will also be installed. The file path of the Hitachi Network Objectplaza Trace Library integrated trace information file is installation-destination-drive:\Program \HITACHI\HNTRLib2\spool\Hntr2n.log, where n is the number of the Files integrated trace information file. For Windows Server 2003 (excluding the x86 edition) or Windows Server 2008 (excluding the x86 edition), Program Files is Program Files (x86).
Page 92: Preparations For Installing Hdlm By Performing An Unattended Installation
Install the HBAs onto the host. Install as many HBAs as you want to use. 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.
Page 93: How To Create An Installation-Information Settings File
This section describes the following aspects of an unattended installation: • How to create an installation-information settings file • Notes on installation For details on the installhdlm utility, see The installhdlm Utility for Installing HDLM on page 7-16. For details about performing an unattended installation, see Performing a New Installation of HDLM on Windows Server 2003 on page 3-28 Performing a New Installation of HDLM on Windows Server 2008 on page...
Page 94: Performing A New Installation Of Hdlm On Windows Server 2003
A folder specified in the workdir key (if the workdir key has not been specified, a folder specified in the TMP or TEMP environment variable) must have at least 20 KB of free disk capacity. • Information for the HDLM operation can also be specified by using the HDLM command's set operation.
Page 95 drive-to-which-the-installation-DVD-is-inserted:\HDLM_Windows \DLMTools\installhdlm -f installation-information-settings- file This command checks whether HDLM has already been installed. If HDLM 5.4 or earlier has been installed, the KAPL09129-E message will appear. If this happens, carry out the procedure shown in Migrating from HDLM 5.4 or Earlier to HDLM 5.5 or Later on page 3-64.
Page 96 Windows Server 2003 (x64) ¢ This OS cannot be used with the EMC DMX series. The Hitachi storage systems and HP StorageWorks XP Series option is always selected. To select an EMC DMX series or EMC CX series LU as the HDLM management-target device, select EMC Symmetrix DMX Series, CLARiiON CX Series.
Page 97 Make sure that the PRSV key displayed by the dlmprsvkey utility is unique among all the other hosts in the SAN. If the PRSV key is not unique or is not registered, or if the KAPL09131-W message appears, execute the dlmprsvkey utility with the -r parameter specified to re- register the PRSV key.
Page 98 Support Cluster : off Elog Level Elog File Size (KB) : 9900 Number Of Elog Files Trace Level Trace File Size(KB) : 1000 Number Of Trace Files Path Health Checking : on(30) Auto Failback : on(1) Remove LU : off Intermittent Error Monitor : off HDLM Manager Ver...
Page 99: When Mscs Is Used
Figure 3-3 Single Path Configuration and Multi-path Configuration Check the path information as described in Checking the Path Configuration on page 3-68 to make sure that you have successfully assembled a multi-path configuration. When MSCS Is Used The following provides explanations of how to install MSCS before and after an HDLM installation.
Page 100 The program checks whether HDLM has already been installed. If HDLM 5.4 or earlier has been installed, the KAPL09129-E message will appear. If this happens, carry out the procedure shown in Migrating from HDLM 5.4 or Earlier to HDLM 5.5 or Later on page 3-64.
Page 101 Specify the installation folder by following the instructions shown in the messages that appear in the window. The utility for registering HDLM persistent reservation keys (dlmprsvkey) will be automatically executed. However, creation of the PRSV key might be unsuccessful if, for example, an NIC does not exist. If the PRSV key is created with time information only, or if key creation fails, a dialog box will prompt you to enter the PRSV key.
Page 102 In the last installation window, the following message might be ¢ output: When you manage a host by using Global Link Manager and Windows firewall is enabled on that host, execute the firewall_setup command to allow a firewall exception. If Global Link Manager will not be used to manage HDLM, you do not need to take any action.
Page 103 Elog Level Elog File Size (KB) : 9900 Number Of Elog Files Trace Level Trace File Size(KB) : 1000 Number Of Trace Files Path Health Checking : on(30) Auto Failback : on(1) Remove LU : off Intermittent Error Monitor : off HDLM Manager Ver WakeupTime Alive...
Page 104 >dlnkmgr view -sys HDLM Version : x.x.x-xx Service Pack Version Load Balance : on(extended lio) Support Cluster : on MSCS Elog Level Elog File Size (KB) : 9900 Number Of Elog Files Trace Level Trace File Size(KB) : 1000 Number Of Trace Files Path Health Checking : on(30) Auto Failback...
Page 105 HDLM 5.5 or later has been installed, the KAPL09173-W message will appear. If this happens, carry out the procedure shown in Upgrade Installation or Re-installation of HDLM on page 3-63. If no message appears, go to step 6. If you are planning to perform an unattended installation, execute the ¢...
Page 106 If the KAPL09128-W message appears, you will need to re-enter the correct PRSV key. If a message does not appear, go to the next step. Select an HDLM management-target device only when the OS is one of the following: Windows Server 2003 (x86) SP1 or later ¢...
Page 107 Check the results of the installation. If you have performed an unattended installation, check the installation results from the command prompt. After the installation finishes, execute the dlmprsvkey utility with the -v parameter specified. Execute the following command: HDLM-installation-folder\bin\dlmprsvkey -v Make sure that the PRSV key displayed by the dlmprsvkey utility is unique among all the other hosts in the SAN.
Page 108: When Vcs Is Used
HDLM Manager Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.x-xx yyyy/mm/dd hh:mm:ss 128 HDLM Driver Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss License Type Expiration Permanent KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss Use the results of the view operation to check the version of the installed HDLM.
Page 109 In the displayed window, click the Install button next to for Windows of Hitachi Dynamic Link Manager Software. If no window is displayed, manually run the installer (setup.exe). The program checks whether HDLM has already been installed. If HDLM 5.4 or earlier has been installed, the KAPL09129-E message will appear.
Page 110 created with time information only, or if key creation fails, a dialog box will prompt you to enter the PRSV key. If this dialog box appears, go to step 11; otherwise, go to step 13. Enter the PRSV key by following the instructions shown in the dialog box. The PRSV key is required for the HDLM functions to properly operate.
Page 111 Check the results of the installation. If you have performed an unattended installation, check the installation results from the command prompt. After the installation finishes, execute the dlmprsvkey utility with the -v parameter specified. Execute the following command: HDLM-installation-folder\bin\dlmprsvkey -v Make sure that the PRSV key displayed by the dlmprsvkey utility is unique among all the other hosts in the SAN.
Page 112: When Oracle Rac Is Used
HDLM Driver Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss License Type Expiration Permanent KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss Even if you are using VCS, off appears for Support Cluster. Even if this is the case, the cluster support function will run properly.
Page 113 If no window is displayed, manually run the installer (setup.exe). The program checks whether HDLM has already been installed. If HDLM 5.4 or earlier has been installed, the KAPL09129-E message will appear. If this happens, carry out the procedure shown in Migrating from HDLM 5.4 or Earlier to HDLM 5.5 or Later on page 3-64.
Page 114 Enter the PRSV key by following the instructions shown in the dialog box. The PRSV key is required for the HDLM functions to properly operate. Also, the value of the PRSV key must be unique for each host. If the KAPL09128-W message appears, you will need to re-enter the correct PRSV key.
Page 115 After the installation finishes, execute the dlmprsvkey utility with the -v parameter specified. Execute the following command: HDLM-installation-folder\bin\dlmprsvkey -v Make sure that the PRSV key displayed by the dlmprsvkey utility is unique among all the other hosts in the SAN. If the PRSV key is not unique or is not registered, or if the KAPL09131-W message appears, execute the dlmprsvkey utility with the -r parameter specified to re- register the PRSV key.
Page 116 KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss Use the results of the dlnkmgr command's view operation to check the version of the installed HDLM. If x.x.x-xx is displayed in HDLM Version, the correct version of HDLM has been installed.
Page 117: Performing A New Installation Of Hdlm On Windows Server 2008
HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.x-xx yyyy/mm/dd hh:mm:ss 128 HDLM Driver Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss License Type Expiration Permanent KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss Even if you are using Oracle RAC, off appears for Support Cluster. Even if this is the case, the cluster support function will run normally.
Page 118 file This command checks whether HDLM has already been installed. If the KAPL09183-I message appears, a re-installation will be performed. If you specified n for the restart key in the installation-information settings file, go to step 8. If you specified y for the restart key in the installation-information settings file, go to step 18.
Page 119 If you have performed an unattended installation, check the installation results from the command prompt. After the installation finishes, execute the dlmprsvkey utility with the -v parameter specified. Execute the following command: HDLM-installation-folder\bin\dlmprsvkey -v Make sure that the PRSV key displayed by the dlmprsvkey utility is unique among all the hosts in the SAN.
Page 120 Make sure that the PRSV key displayed by the dlmprsvkey utility is unique among all the other hosts in the SAN. If the PRSV key is not unique or is not registered, or if the KAPL09131-W message appears, execute the dlmprsvkey utility with the -r parameter specified to re- register the PRSV key.
Page 121: When Mscs Is Used
Connect cables to all the HBAs to change the configuration to a multi-path configuration. Figure 3-4 Single Path Configuration and Multi-path Configuration on page 3-55 shows a single path configuration and a multi-path configuration. Figure 3-4 Single Path Configuration and Multi-path Configuration Check the path information as described in Checking the Path Configuration on page 3-68...
Page 122 If you are not performing an unattended installation, insert the DVD ¢ into the drive. In the displayed window, click the Install button next to for Windows of Hitachi Dynamic Link Manager Software. If no window is displayed, manually run the installer (setup.exe). The program checks whether HDLM has already been installed.
Page 123 Although a message prompting you to restart the host appears after ¢ the installation has finished, a restart is not necessary. In the last installation window, the following message might be ¢ output: When you manage a host by using Global Link Manager and Windows firewall is enabled on that host, execute the firewall_setup command to allow a firewall exception.
Page 124 Make sure that all the hosts in the cluster system have completely shut down. Restart each host. Log on to Windows again as a member of the Administrators group. Execute the dlnkmgr command's view operation to display the status of each program.
Page 125 Shut down the host. Perform steps 21 to 29 on all the hosts that make up the cluster system. Restart each host. Install MSCS on each host. Shut down all the hosts. Restart each host again. Log on to Windows as a member of the Administrators group. Execute the dlnkmgr command's view operation to display the status of each program.
Page 126 The license key file will be deleted after the installation finishes. Perform the installation. If you are not performing an unattended installation, insert the DVD ¢ into the drive. In the displayed window, click the Install button next to for Windows of Hitachi Dynamic Link Manager Software.
Page 127 Although a message prompting you to restart the host appears after ¢ the installation has finished, a restart is not necessary. In the last installation window, the following message might be ¢ output: When you manage a host by using Global Link Manager and Windows firewall is enabled on that host, execute the firewall_setup command to allow a firewall exception.
Page 128 Perform steps 1 to 17 on all the hosts that make up the cluster system. Make sure that all the hosts that make up the cluster system have completely shut down. Modify the storage system settings. Modify the storage system settings by following the procedure described in the maintenance documentation for that particular storage system.
Page 129: Upgrade Installation Or Re-Installation Of Hdlm
Connect cables to all the HBAs to change the configuration to a multi-path configuration. Check the path information as described in Checking the Path Configuration on page 3-68 to make sure that you have successfully assembled a multi-path configuration. Upgrade Installation or Re-installation of HDLM You can perform an upgrade installation for only HDLM 5.5 or later.
Page 130: Migrating From Hdlm 5.4 Or Earlier To Hdlm 5.5 Or Later
Note: If you want to install all HDLM components on a host on which the HDLM Core components have been installed, use an unattended installation. When you install HDLM without using the unattended installation option, only the HDLM Core components, which were already installed in the previous environment, will be installed.
Page 131: Installing Jre
\HDLM-installation-folder\config\dlmmgr.xml \HDLM-installation-folder\config\dlmwebagent.properties Delete the files copied in step 1. Restart the host. Note: When you install HDLM 5.5 or later in an environment where HDLM 5.4 or earlier was installed, DLMAlertDriver is displayed in the Non-Plug and Play Drivers area of the Device Manager window. You can delete DLMAlertDriver by using the procedure below.
Page 132: Firewall Settings For Managing Hdlm By Using Global Link Manager
HDLM-installation-folder\jre_user If you use JRE 6.0_04, the folder configuration is as follows: HDLM-installation-folder\jre_user \jre1.6.0_04 \bin \lib The folder name depends on the JRE version that will be used: When using JRE 1.4.2_13: j2re1.4.2_13 When using JRE 5.0_10: jre1.5_10 When using JRE 6.0_17: jre6 For example, if the HDLM installation folder is C:\Program Files \HITACHI\DynamicLinkManager and you are using JRE 6.0_04, after copying the configuration files, the folder configuration will become the...
Page 133: Firewall_Setup Command Syntax
Execute the firewall_setup command. Check the displayed message to make sure that the command was executed successfully. The command ended successfully. firewall_setup command syntax If the host OS is Windows, the firewall_setup command is used to register the ports used by the Hitachi Command Suite Common Agent Component as firewall exceptions.
Page 134: Checking The Path Configuration
Checking the Path Configuration HDLM functions, such as load balancing and failover, are 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 the 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.
Page 135: Checking The Current Settings
operation or by using the Options window of the HDLM GUI. The following subsections describe how to set up HDLM functions by using the HDLM command’s set operation. For details about the Options window, see the HDLM GUI Help. Notes: •...
Page 136: Setting Up The Hdlm Functions
Setting Up the HDLM Functions The recommended and default values for each HDLM function is shown below Table 3-14 The Recommended and Default Values for Each Function on page 3-70. Table 3-14 The Recommended and Default Values for Each Function Function Default value Recommended value...
Page 137: Setting Up Path Health Checking
these conditions are applied regardless of whether or not the load balancing function is enabled in those series. For example, in a cluster environment, the load balancing function is disabled even if you try to enable it for the EMC DMX series.
Page 138: Setting Up The Automatic Failback Function
Setting Up the Automatic Failback Function When intermittent error monitoring is enabled and the number of error occurrences is 2 or more, the following condition must be satisfied. error-monitoring-interval >= checking-interval-for-automatic- failbacks x number-of-times-an-error-is-to-occur-during-intermittent- error-monitoring If this condition is not satisfied, an error will occur and the warning message KAPL01080-W will be output.
Page 139: Setting Up The Lu Deletion Function
When a value of 2 or more is specified for the number of times an error needs to occur, make sure that the condition shown in Setting Up the Automatic Failback Function on page 3-72 is satisfied. To determine whether a path is invalid for an automatic failback, you can use the results of the dlnkmgr command's view operation.
Page 140: Setting The Error Log Collection Level
Values in the set Description operation The removed LU is restored after it is recovered from the physical failure and the disk is re-scanned. • Setting up LU deletion by using the set operation The following is an example of setting up LU deletion by using a command: >dlnkmgr set -rmlu on -force To enable the LU deletion function, specify on.
Page 141: Setting The Trace Level
>dlnkmgr set -ellv 2 Specify the error log collection level as a number. Setting the Trace Level You can set up the trace level for a trace file hdlmtrn.log (n indicates a file number from 1 to 64). Table 3-17 Values for the Trace Level Setting on page 3-75 lists and describes the possible values for the trace level setting.
Page 142: Setting The Number Of Error Log Files
a value over 9901, 9900 will be used. For HDLM manager logs, the specified value will be applied as it is without being limited by the above. When an error log file reaches its maximum size, the information in the oldest error log file will be overwritten with new information.
Page 143: Setting The Number Of Trace Files
• Setting up the trace file size by using the set operation The following is an example of setting up the trace file size by using a command: >dlnkmgr set -systfs 2000 Specify the size of the trace file in kilobytes. Setting 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).
Page 144: Checking The Updated Settings
Value (severity) Explanation Table 3-19 Values Indicating Audit Log Data Categories on page 3-78 describes the values that indicate audit log data categories. The default is all. Table 3-19 Values Indicating Audit Log Data Categories Value Explanation Audit log events of the StartStop category are collected. Audit log events of the Authentication category are collected.
Page 145: Setting Up Integrated Traces
KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss > After you have set up the collection of audit log data, use the following command to make sure that the setting has been specified correctly: >dlnkmgr view -sys -audlog Audit Log : on(6)
Page 146 Recommended Setting Default value value Buffer size per 64 (KB) 256 (KB) monitoring interval Number of Monitoring cycle 0 (seconds) 0 (seconds) messages to be Number of messages output per to be output monitoring interval If Hitachi Network Objectplaza Trace Library (HNTRLib2) is already installed, the existing settings will be inherited.
Page 147 Figure 3-5 Hitachi Network Objectplaza Trace Utility 2 Release 2.0 Dialog Box. In Number of Files, change the number of integrated trace files. The default is 4. You can specify a value from 1 to 16. The value you specify here will apply to n in program-installation- destination-drive:\Program Files\HITACHI\HNTRLib2\spool \Hntr2n.log (n indicates a file number).
Page 148: Uninstalling Hdlm
The default is 0. You can specify a value from 0 to 500. If you specify 0, you cannot adjust the number of messages to be output. If you specify 0 for Lookout Span(Sec), you cannot adjust the number of messages to be output because the system ignores the Max Messages / Span setting.
Page 149 To uninstall HDLM, you must reconfigure the system to a single-path configuration. The time for doing this does not affect the time required for an uninstallation. Since the uninstallation time depends on the value of the maximum number of paths that can be configured in your environment, use this value for an approximate calculation.
Page 150: Uninstalling Hdlm
Uninstalling HDLM After HDLM is uninstalled, sometimes the files below will not be deleted. The following files will be deleted when you restart the host: HDLM-installation-folder\DLMTools\perfhdlm\provhdlm.dll HDLM-installation-folder\lib\libdlm.dll HDLM-installation-folder\lib\hdlmhcc60.dll The default installation folder for HDLM is Windows-installation-drive: \Program Files \HITACHI\DynamicLinkManager. For Windows Server 2003 (excluding the x86 edition) or Windows Server 2008 (excluding the x86 edition), Program Files is Program Files (x86).
Page 151 Figure 3-6 Single Path Configuration and Multi-path Configuration In Windows Server 2008, if you have selected an EMC CX series LU as the HDLM management-target device, perform the following steps to unregister it. Otherwise, go to step 7. From Control Panel, choose MPIO. The MPIO Properties dialog box opens.
Page 152: Uninstallation Procedures - Mscs Or Vcs Environment
If a warning dialog box is not displayed, go to the next step. ¢ Follow the instructions shown in the messages that appear in the window. If the KAPL09005-E message appears, stop the HDLM manager according to the procedure in Stopping the HDLM Manager on page 4-15.
Page 153 Figure 3-7 Single Path Configuration and Multi-path Configuration In Windows Server 2008, if you have selected an EMC CX series LU as the HDLM management-target device, perform the following steps to unregister it. Otherwise, go to step 8. From Control Panel, choose MPIO. The MPIO Properties dialog box opens.
Page 154: Uninstallation Procedures - Oracle Rac Environment
about the dlmchkpath utility, see The dlmchkpath Utility for Checking HDLM Paths on page 7-13. If a warning dialog box is not displayed, go to the next step. ¢ Follow the instructions shown in the messages that appear in the window. Uninstall HDLM from all the hosts that make up the cluster.
Page 155: Uninstalling Hitachi Network Objectplaza Trace Library (Hntrlib2)
If a warning dialog box is not displayed, go to the next step. ¢ Follow the instructions shown in the messages that appear in the window. If the KAPL09005-E message appears, stop the HDLM manager according to the procedure in Stopping the HDLM Manager on page 4-15.
Page 156: Clearing The Persistent Reservation
For Windows Server 2003 (excluding the x86 edition) or Windows Server 2008 (excluding the x86 edition), Program Files is Program Files (x86). Notes: If HNTRLib2 is being used by another program, the KAPL09026-I ¢ message will appear and HNTRLib2 will not be uninstalled. If you are unable to complete uninstallation even though no programs other than HDLM are using HNTRLib2, contact your HDLM vendor or, if you have a maintenance contract for HDLM, contact maintenance...
Page 157 If HDLM is uninstalled in one of the following situations, the persistent ¢ reservation in the LU will remain: - When MSCS or VCS is running - When a cable is not connected to the host To uninstall HDLM, follow the procedure in Uninstallation Procedures - MSCS or VCS Environment on page 3-86 Uninstalling HDLM on page...
Page 158 3-92 Creating an HDLM Environment Hitachi Dynamic Link Manager User Guide (for Windows(R))
Page 159: Hdlm Operation
HDLM Operation This chapter describes the operating procedures for HDLM, including how to operate HDLM and the HDLM manager, and how to change the configuration of the operating environment. □ Notes on Using HDLM □ HDLM Operations Using the HDLM GUI □...
Page 160: Notes On Using Hdlm
Notes on Using HDLM This section contains notes that are important for running HDLM operations. Using a Storage Management Program You must not change the vendor ID and product ID of a storage system. If you change these IDs, HDLM will not be able to recognize the storage system.
Page 161: Using Symantec Backup Exec For Windows And The Veritas Netbackup Intelligent Disaster Recovery Function
• You can display and use the HDLM GUI windows for the Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP, Hitachi AMS2000/AMS/WMS/SMS series, Universal Storage Platform V/VM, and Virtual Storage Platform. If you specify the EMC DMX series, EMC CX series, or HP EVA series as an HDLM management-target device, use HDLM commands to display information and set the operating environment.
Page 162: Hdlm Operations Using The Hdlm Gui
HDLM Operations Using the HDLM GUI This chapter explains the procedures for operating the HDLM GUI window components. For details on the components of each window, see the HDLM GUI Help. Notes on Using the HDLM GUI This subsection provides notes on using the HDLM GUI window. Be sure to read this section.
Page 163: Viewing Path Information
• To specify a parameter value containing one or more spaces, 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. Viewing Path Information This section explains how to display path information by using an HDLM command.
Page 164: Changing The Status Of Paths To Offline(C)
To place paths online by specifying an HBA port, CHA port, single path, or HBA port WWN, check the path name or PATH_ID used to manage the path. The following example shows how to execute the command: >dlnkmgr view -path To change the status of paths to online, execute the dlnkmgr command's online operation.
Page 165: Viewing Lu Information
operation with the -hba parameter specified. The following shows an example of executing this command: >dlnkmgr offline -hba 1.1 KAPL01055-I All the paths which pass the specified HBA port 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.
Page 166: Initializing Statistical Information For Paths
For details on the displayed items and their descriptions, see view (Displays Information) on page 6-29. Initializing Statistical Information for Paths This section explains how to initialize statistical information (I/O counts and I/ O errors) for all the paths managed by HDLM. This procedure is useful when you want to check the number of I/O operations and I/O errors that have occurred since the last time the I/O counts and I/O errors were initialized to 0.
Page 167: Setting Up The Operating Environment
Load Balance : on(extended lio) Support Cluster : off Elog Level Elog File Size(KB) : 9900 Number Of Elog Files Trace Level Trace File Size(KB) : 1000 Number Of Trace Files Path Health Checking : on(30) Auto Failback : on(1) Remove LU : on Intermittent Error Monitor...
Page 168: Viewing License Information
For example, to set up the error log collection level, execute the dlnkmgr command's set operation with the -ellv parameter specified. When the confirmation message is displayed, enter y to execute, or n to cancel the command. The following shows an example in which the command is executed: >dlnkmgr set -ellv 1 KAPL01049-I Would you like to execute the operation? Operation name = set [y/n]: y...
Page 169: Viewing Hdlm Version Information
environment is invalid. If this message appears, execute the dlnkmgr command's view operation with the -sys -lic parameter to make sure that the license is installed correctly. The following shows an example in which the command is executed: >dlnkmgr set -lic KAPL01049-I Would you like to execute the operation? Operation name = set [y/n]: y KAPL01071-I A permanent license was installed.
Page 170: Using The Windows Administrative Tool (Performance) To Check Path Information
To display HDLM component information, execute the dlnkmgr command's view operation with the -sys parameter specified. The following shows an example in which the command is executed: >dlnkmgr view -sys HDLM Version : x.x.x-xx Service Pack Version Load Balance : on(extended lio) Support Cluster : off Elog Level...
Page 171 If an error occurs in the HDLM performance monitor, performance ¢ information is not collected after the error. To restart the acquisition of performance information, restart the host. To add a counter that HDLM provides: Click Start, Settings, and then Control Panel. Double click Administrative Tools., and then double click Performance.
Page 172: Starting And Stopping The Hdlm Manager
Description Selectable items 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): • pathid Displays AutoPATH_ID. This is the same value as when PathID is displayed by executing the dlnkmgr command's view operation with the -path parameter.
Page 173: Stopping The Hdlm Manager
>dlnkmgr view -sys -msrv HDLM Manager Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss > When the HDLM Manager column shows Alive, the HDLM manager is active. Stopping the HDLM Manager When you uninstall, upgrade, or re-install HDLM, the HDLM manager will automatically stop.
Page 174: Reconfiguring The Hdlm Operating Environment
Process Service Description Hitachi Network Objectplaza Trace hntr2mon.exe Hitachi Network Library (HNTRLib2) process Objectplaza Trace hntr2srv.exe Monitor 2 You only need to monitor this process when HDLM is linked to Global Link Manager. This process does not exist if you install only the HDLM Core components. Reconfiguring the HDLM Operating Environment You can add or delete LUs and paths while the host installing HDLM is running by utilizing the Windows plug-and-play functionality.
Page 175 Figure 4-1 Using the command to confirm that an LU has been added on page 4-17 shows an example of using the command to confirm that an LU has been added. For details about the HDLM GUI, see the HDLM GUI Help.
Page 176: Checking An Added Path
Checking an Added Path You can add a path, by inserting a cable into an existing LU, even while the host (on which HDLM is installed) is running. When you add a path without adding an LU, what is displayed in the disk management window does not changed.
Page 177: Deleting An Lu Dynamically
Deleting an LU Dynamically The LU deletion function automatically removes an LU from HDLM management when all the paths to that particular LU are disconnected. You can set up the LU deletion function by specifying the dlnkmgr command's set operation together with the -rmlu on parameter. You can also set up this function in the Options window of the HDLM GUI.
Page 178 Figure 4-3 An example of displaying the KAPL05301-E message In the event viewer, deleted path information is displayed in the following format: PathID PathName DskName iLU ChaPort. The following is an example of output data to the KAPL05301-E message. 4-20 HDLM Operation Hitachi Dynamic Link Manager User Guide (for Windows(R))
Page 179: Recovering A Deleted Lu Or Path
Table 4-4 Items and Descriptions for the Path Information Displayed in the KAPL05301-E Message on page 4-21 shows the items and descriptions for the path information, displayed in the KAPL05301-E message. Table 4-4 Items and Descriptions for the Path Information Displayed in the KAPL05301-E Message Item Description...
Page 180 4-22 HDLM Operation Hitachi Dynamic Link Manager User Guide (for Windows(R))
Page 181: Troubleshooting
Troubleshooting This chapter describes how to properly use HDLM error information, and then how to resolve the problem, if an error occurs in HDLM. The resolutions for path errors, HDLM program errors, and other types of errors are all described separately.
Page 182: Information Collected By The Dlmgetras Utility For Collecting Hdlm Error Information
Information Collected by the DLMgetras Utility for Collecting HDLM Error Information Immediately after an error occurs, execute the DLMgetras utility for collecting HDLM error information, since restarting the machine might delete error information before the information is collected by DLMgetras. For details about the DLMgetras utility and the error information it collects, see DLMgetras Utility for Collecting HDLM Error Information on page 7-2.
Page 183 output to the event log. If this happens, refer to the KAPL05301-E message to check the path information. The message elements are explained below: For details about the KAPL05301-E message, see When an LU or path is automatically deleted due to all the paths being disconnected in Checking that the LU or Path Has Been Dynamically Deleted on page 4-19 Deleting...
Page 184: What To Do For A Path Error
The name of the host device. A drive letter is used. If no drive letter has been assigned, a hyphen (-) will be displayed. This is the same as the HDevName that is displayed by the view operation. For details on the view operation, see view (Displays Information) on page 6-29.
Page 185: Examining The Messages
Figure 5-2 Troubleshooting Procedure When a Path Error Occurs The following shows the procedure for using the HDLM command (dlnkmgr) to handle a path error. Examining the Messages Examine the messages that are output to the host event log. If the KAPL08022-E message is output, view the message to check the path in which the error has occurred.
Page 186: Identifying The Error Path
Identifying the Error Path Check the obtained path information to find the path with the error. In the Status column, the error path has the status Offline(E) or Online(E). Narrowing Down the Hardware That Might Have Caused the Error Check the DskName, iLU, ChaPort, and HBAPortWWN columns of the path with the error to narrow down the hardware that may be the cause of the error.
Page 187: What To Do For A Program Error
What To Do for a Program Error The following describes what to do to handle errors that occur in an HDLM program. Figure 5-3 Troubleshooting Procedure When a Program Error Occurs on page 5-7 shows the troubleshooting procedure. Figure 5-3 Troubleshooting Procedure When a Program Error Occurs The following shows the procedure for handling a program error by using the HDLM command (dlnkmgr).
Page 188: Contacting Your Hdlm Vendor Or Maintenance Company
If the error occurs again after you thought that you had resolved the problem, use the dlnkmgr command's view operation to check the status of the HDLM program, and then do whatever is necessary to resolve the problem. For details on the view operation, see view (Displays Information) on page 6-29.
Page 189: Command Reference
Command Reference This chapter describes the HDLM command (dlnkmgr) and its operations. □ Overview of the HDLM Command dlnkmgr □ clear (Returns the Path Statistics to the Initial Value) □ help (Displays the Operation Format) □ offline (Places Paths Offline) □...
Page 190: Overview Of The Hdlm Command Dlnkmgr
Overview of the HDLM Command dlnkmgr This section describes how to specify the HDLM command dlnkmgr and its subcommands (called operations in HDLM). Command format Enter the command using the following format: dlnkmgr operation [parameter [parameter-value]] dlnkmgr The command name. operation The type of operation entered after dlnkmgr.
Page 191: Clear (Returns The Path Statistics To The Initial Value)
If you are executing HDLM commands in Windows Server 2008, see Using Windows Server 2008 on page 4-3. To specify a value that contains a space in its parameter, enclose the ¢ entire value in double quotes ("). clear (Returns the Path Statistics to the Initial Value) The dlnkmgr command's clear operation clears the statistics (I/O count and I/O errors) of all paths that are managed by HDLM, and returns them to their initial value.
Page 192: To Display The Format Of The Clear Operation
> To Display the Format of the clear Operation -help Displays the format of the clear operation. Example >dlnkmgr clear -help clear: Format dlnkmgr clear -pdst [-s] KAPL01001-I The HDLM command completed normally. Operation name = clear, completion time = yyyy/mm/dd hh:mm:ss >...
Page 193 >dlnkmgr help dlnkmgr: Format dlnkmgr { clear | help | offline | online | set | view } KAPL01001-I The HDLM command completed normally. Operation name = help, completion time = yyyy/mm/dd hh:mm:ss > Example 2 The following example shows how to display the formats of multiple operations.
Page 194: Offline (Places Paths Offline)
offline (Places Paths Offline) The dlnkmgr command's offline operation places online paths offline. Specify the paths to be placed offline by specifying an HBA port, CHA port, single path, or HBA port WWN. There must always be at least one online path accessing each LU. Placing too many paths offline might prevent paths from being able to switch if an error occurs.
Page 195 Specify the host port number and bus number of the target HBA port: the numbers are found in the PathName field displayed using the view operation. Enter a period between these two parameter values. For details about the view operation, see view (Displays Information) on page 6-29.
Page 196 when all the paths which pass the specified CHA port are placed in the Offline(C) status, enter y. Otherwise, enter n. [y/n]: y KAPL01061-I 2 path(s) were successfully placed Offline(C); 0 path(s) were not. Operation name = offline > -pathid AutoPATH_ID Use this parameter to place a single path offline.
Page 197: To Display The Format Of The Offline Operation
when the path is placed in the Offline(C) status, enter y. Otherwise, enter n. [y/n]: y KAPL01061-I 1 path(s) were successfully placed Offline(C); 0 path(s) were not. Operation name = offline Executes the command without displaying the message asking for confirmation of command execution from the user.
Page 198: Online (Places Paths Online)
We recommend that you use the following command and verify the information on the target paths before you execute the offline operation to place offline all the paths connected to a specific HBA port or channel adapter port. Example 1 The following example shows how to filter and display the information on all paths that pass through the HBA port whose host port number is 0004 and bus number is 0001:...
Page 199: To Place Paths Online
|-hbaportwwn HBA-port-WWN [-tid target-ID -hlun host-LU- number]] [-s] To Display the Format of the Online Operation dlnkmgr online -help Parameters To Place Paths Online -path Indicates that the target of the operation is a path managed by HDLM. This parameter is optional because the online is always used for paths, so it is assumed.
Page 200 Use this parameter to place online, at one time, all the paths that pass through a specific channel adapter port. The command will place online all the paths that pass through the channel adapter port to which the path with the specified AutoPATH_ID is connected. You can specify this parameter only when the HDLM management-target device is the Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP, Hitachi AMS2000/AMS/WMS/SMS series, Universal Storage...
Page 201: To Display The Format Of The Online Operation
For target-ID, specify the target ID portion of PathName. Leading zeroes can be omitted from the target ID (0000000000000001 and 1 are the same value). The parameter is not case sensitive. For host-LU-number, specify the host LU number portion of PathName. Leading zeroes can be omitted from the host LU number (0001 and 1 are the same value).
Page 202 online: Format dlnkmgr online [-path] [-s] dlnkmgr online [-path] -hba HBAPortNumber.BusNumber [-s] dlnkmgr online [-path] -cha -pathid AutoPATH_ID [-s] dlnkmgr online [-path] [-pathid AutoPATH_ID] [-s] dlnkmgr online [-path] [-hbaportwwn HBA_Port_WWN [-tid Target_ID -hlun Host_LUN]] [-s] Valid value AutoPATH_ID { 000000 - 999999 }(Decimal) Host_LUN { 0000 - FFFF }(Hexadecimal) KAPL01001-I The HDLM command completed normally.
Page 203: Set (Sets Up The Operating Environment)
status of, has been deleted, and then resolve the path error. For details, see Deleting an LU Dynamically on page 4-19. set (Sets Up the Operating Environment) The dlnkmgr command's set operation sets the HDLM operating environment. Format To Set Up the HDLM Operating Environment dlnkmgr set {-lb {on [-lbtype {rr|exrr|lio|exlio|lbk|exlbk}]|off} |-ellv error-log-collection-level |-elfs error-log-file-size...
Page 204 Item name Default value Recommended value The Extended Least I/Os The recommended algorithm algorithm is used. depends on the operating environment. Error log collection level Collect error information for the Collect error information for the Information level and higher. Information level and higher. Error log file size 9900 (KB) 9900 (KB)
Page 205 -lbtype {rr|exrr|lio|exlio|lbk|exlbk} Specify the algorithm to be used for load balancing. rr: The Round Robin algorithm exrr: The Extended Round Robin algorithm lio: The Least I/Os algorithm exlio: The Extended Least I/Os algorithm lbk: The Least Blocks algorithm exlbk: The Extended Least Blocks algorithm The type of algorithm specified by the -lbtype parameter remains stored in the system, even when you disable the load balancing function by specifying -lb off.
Page 206 KAPL01049-I Would you like to execute the operation? Operation name = set [y/n]: y KAPL01001-I The HDLM command completed normally. Operation name = set, completion time = yyyy/mm/dd hh:mm:ss > -elfs error-log-file-size Specify a value from 100 to 2000000 (KB) for the size of the error log files.
Page 207 The higher the error log collection level value, the more log information will be output. As the amount of log information that is output increases, the amount of time before existing information will be overwritten becomes shorter. -systfs trace-file-size Specify the size of the trace file in kilobytes. Specify a value from 100 to 16000.
Page 208 The explanation for the following sub-parameter describes how to specify the checking interval. -intvl checking-interval Specify the checking interval between path health checks. 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.
Page 209 The previously used interval The explanation for the following sub-parameter describes how to specify the interval between path status checks. -intvl checking-interval Specify the interval between path status checks. Specify a value from 1 to 1440 minutes. Specify an interval appropriate for your operating environment.
Page 210 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. If on is specified, be sure to also specify the intermittent error monitoring interval and the number of times that the error is to occur. The system assumes that an intermittent error is occurring if the specified number of times that the error is to occur is reached during the monitoring interval.
Page 211 while intermittent errors are not being monitored, the values will not change. The monitoring interval specified in this parameter is stored even though specifying -iem off disables intermittent error monitoring. Therefore, when you re-enable intermittent error monitoring and a monitoring interval is not specified, error monitoring will be performed by using the stored monitoring interval.
Page 212 Table 6-5 Relationship Between the Setting for the Automatic Failback Function and Intermittent Error Monitoring and the Executable Operations Setting Available operation Result of operation Set AFB to on. The operations of AFB and IEM do not change. Change the AFB setting. AFB is performed under the new settings.
Page 213 Setting Available operation Result of operation Set AFB to on. AFB is enabled. Set AFB to off. The operations of AFB and IEM do not change. Legend: AFB: Automatic failback IEM: Intermittent error monitoring When this condition is not satisfied, the KAPL01080-W message is output and an error occurs.
Page 214 key file. For a temporary license key or emergency license key, the expiration period is also displayed (KAPL01071-I, KAPL01072-I). Table 6-6 License Key Types on page 6-26 lists the license key types. Table 6-6 License Key Types Type Description Permanent license key Permanent license keys are valid for using HDLM permanently.
Page 215 The following sub-parameter can be used to specify how the LU dynamic deletion function operates. -force The LU is removed from under HDLM-management when all the paths to the LU are disconnected, even when an Offline(C) path is included in the paths connected to the LU. For details on the LU dynamic deletion function, see Deleting an LU Dynamically on page...
Page 216: To Display The Format Of The Set Operation
Value (severity) Explanation Error-level and Warning-level audit log data is collected. Error-level, Warning-level, and Information-level audit log data is collected. -category [[ss][a][ca]|all] Specifies the categories of audit log data to be collected. Table 6-9 Values Indicating Audit Log Data Categories on page 6-28 lists the values that indicate categories of audit log data.
Page 217: View (Displays Information)
dlnkmgr set { -lb on [ -lbtype { rr | exrr | lio | exlio | lbk | exlbk } ] | -lb off | -ellv ElogLevel | -elfs ElogFileSize | -elfn Number-Of-ElogFiles | -systflv TraceLevel | -systfs TraceFileSize | -systfn Number-Of-TraceFiles | -pchk on [ -intvl Interval-Time ] | -pchk off | -afb...
Page 218: Format
Format To Display Program Information dlnkmgr view -sys [-sfunc|-msrv|-adrv|-pdrv|-lic|-audlog] [-t] To Display HDLM Management-target Device Information dlnkmgr view -stinfo [-t] To Display Path Information To display path information dlnkmgr view -path [-hdev host-device-name] [-stname] [-iem] [-srt {pn|lu|cp}] [-exlu] [-hbaportwwn] [-t] To display path information (by selecting a display item) dlnkmgr view -path -item [pn] [dn] [lu] [cp] [type] [ic] [ie] [dnu] [hd] [iep]...
Page 219: To Display The Format Of The View Operation
[-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]...
Page 220 Use one of the sub-parameters (following -sys) to specify the program information that you want to display. If you do not specify a sub- parameter, the command displays all of the program information. Table 6-10 Displayed Program Information on page 6-32 describes the specifiable parameters, displayed information, displayed items, and a corresponding description.
Page 221 Parameter and program Item Description information to be displayed • 2: Collects error information at the Warning level or higher. • 3: Collects error information at the Information level or higher. • 4: Collects error information at the Information level or higher (including maintenance information).
Page 222 Parameter and program Item Description information to be displayed • Setting for intermittent error monitoring: Intermittent Error Monitor on: Enabled off: Disabled When automatic failback is off, intermittent error monitoring is disabled although Intermittent Error Monitor will be shown as on. When the automatic failback function is on, intermittent error monitoring will be enabled.
Page 223 Parameter and program Item Description information to be displayed License expiration: Expiration • When using a permanent license: - • When using a temporary license or emergency license: The license expiration period is displayed in the format: yyyy/mm/ dd(ndays after). When the view -sys - lic operation is executed, (ndays after) appears if there are n days left until the license period expires.
Page 224 >dlnkmgr view -sys -sfunc HDLM Version : x.x.x-xx Service Pack Version Load Balance : on(extended lio) Support Cluster : off Elog Level Elog File Size(KB) : 9900 Number Of Elog Files Trace Level Trace File Size(KB) : 1000 Number Of Trace Files Path Health Checking : on(30) Auto Failback...
Page 225: Parameters Used When Displaying Hdlm Management-Target Device Information
>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 > Example 6 The following example shows how to display information about the audit log settings: >dlnkmgr view -sys -audlog Audit Log : off Audit Log Category...
Page 226: Parameters Used When Displaying Path Information
Item Description • Windows Server 2003 (IPF) SP1 or later • Windows Server 2003 (x64) • Windows Server 2008 If the OS is Windows Server 2008, this item always displays The EMC DMX series cannot be managed. The EMC DMX series and the HP EVA series cannot be managed. Does not display the title for each information item.
Page 227 -hdev host-device-name Displays information only for the paths accessing the specified host device. Specify a drive letter to indicate the desired host device. You cannot specify the host device unless a drive letter has been assigned. The host-device-name string is case sensitive. If the command ends with the KAPL01064-W or KAPL01013-E message, follow the recommended action in the message.
Page 228 • When the only HDLM management-target devices are the Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP, Hitachi AMS2000/AMS/WMS/SMS series, Universal Storage Platform V/VM, or Virtual Storage Platform: 16 digits will be displayed for the iLU, even if this parameter is specified.
Page 229 Parameters to display path information, by selecting a display item: -path -item When you specify the -path parameter together with the -item parameter, the command only displays the items specified by the value of the -item parameter. If you specify no value for the -item parameter, only the PathID and the Status fields are displayed.
Page 230 Selectable items Sub-parameters ChaPort None Status Type type IO-Count IO-Errors DNum HDevName Because both PathID and Status are always displayed, you do not have to specify any parameters. In the sub-parameters following -path -item, you can list the paths (- hdev) and sort the list (-srt).
Page 231 Use this parameter to sort the path information in ascending order, according to the specified sorting key. The sorting keys are as follows: the first sorting key is the name of the storage system (DskName), the second sorting key is the value specified by the -srt parameter, and the third sorting key is AutoPATH_ID.
Page 232 Parameters to display a summary of path information: -path -c If the -c parameter is specified at the same time as the -path parameter, only PathID, DskName, iLU, CP, Status, and Type are displayed for the path information. The displayed contents are also shortened, so that each path information item is displayed on a single line.
Page 233 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. For details about the information about product IDs, see Table 6-15 Product ID Displayed by the View -path Operation on page 6-51.
Page 234 Displayed path information Table 6-13 Displayed Path Information on page 6-46describes the displayed path information. The following explains the table headings: • No summary displayed: The user specifies only the -path parameter or the -path -item parameter. • Summary displayed: The user specifies the -path -c parameter. Table 6-13 Displayed Path Information Displayed Item Description...
Page 235 Displayed Item Description Summary summary displayed displayed • Host LU number (hexadecimal number) For details about each element of the path name and its representation in Windows, see Table 6-14 Elements of a Path Name on page 6-50. The storage system name, which identifies the storage system DskName DskName that is accessed by a path.
Page 236 Displayed Item Description Summary summary displayed displayed storage system. You can identify an actual LU by referencing iLU from the storage system management program. Indicated by a decimal number. For Universal Storage Platform V/VM, and Hitachi Virtual Storage Platform, iLU is indicated by a hexadecimal number. The first two characters of iLU are the number of the logical DKC (Disk Controller), the middle two numbers are the CU (Control Unit) number, and the last two characters are the...
Page 237 Displayed Item Description Summary summary displayed displayed • For the Thunder 9500V series, Lightning 9900 series, Type Type Lightning 9900V series, Hitachi USP, Hitachi AMS2000/ AMS/WMS/SMS series, Universal Storage Platform V/VM, and Virtual Storage Platform: Attribute of the path Own: Owner path Non: Non-owner path When connecting to the Lightning 9900 series, Lightning 9900V series, Hitachi USP, Universal Storage Platform V/...
Page 238 Displayed Item Description Summary summary displayed displayed 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), Offline(C) or Offline(E)).
Page 239 Element Windows representation Target ID (example: 0000000000000000, Target Id 000000000000007A) Host LU number (example: 0001) Logical Unit ID or LUN The path name corresponds to the following information: Information shown in the Computer Management window ¢ The information in the following registry: ¢...
Page 240: Parameters Used When Displaying Lu Information
Product ID With the -stname Model names of parameter storage systems Without the -stname parameter (Displays the following for the model ID) • Hitachi NSC55 • Hitachi Universal USP_V Storage Platform V • Hitachi Universal Storage Platform Hitachi Virtual Storage Platform P9500 P9500...
Page 241 Note that: For the Thunder 9500V series, Lightning 9900 series, Lightning 9900V ¢ series, Hitachi USP, Hitachi AMS2000/AMS/WMS/SMS series, Universal Storage Platform V/VM, and Virtual Storage Platform LU information is displayed for each storage system. For the EMC DMX series and EMC CX series, LU information is ¢...
Page 242 >dlnkmgr view -lu Product : 9500V SerialNumber : 0329 HDevName PathID Status 0000 P 000006 Online 000014 Online 0001 Q 000007 Online 000015 Online Product : DGC SerialNumber HDevName PathID Status 6006016099C50... F 000004 Online 000008 Online 6006016099C50... G 000005 Online 000009 Online Product : EMC...
Page 243 SerialNumber HDevName PathID Status 6006048000018781000153594D423031 L 000000 Online 000010 Online 6006048000018781000153594D423032 M 000001 Online 000011 Online 6006048000018781000153594D423033 N 000002 Online 000012 Online 6006048000018781000153594D423034 O 000003 Online 000013 Online KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss >...
Page 244 In the sub-parameters, -hdev or -pathid, you can filter the LU information to be displayed. If you omit both parameters, the command displays the information about all the LUs recognized by HDLM. For details on the contents of each displayed item, see Table 6-18 Displayed LU Information on page 6-60.
Page 245 Parameters to display a summary of LU information: -lu -c When the -c parameter is specified with the -lu parameter, a summary of LU configuration information is displayed on one line. The total number of paths recognized by HDLM and the number of online paths are displayed for each LU.
Page 246 Hitachi USP, Hitachi AMS2000/AMS/WMS/SMS series, Universal Storage Platform V/VM, or Virtual Storage Platform: 16 digits are displayed for the iLU even if this parameter is specified. Omits the title for each information item. Example When the -exlu parameter is not specified: When the -exlu parameter is specified: Parameters to display a summary of LU information by adding items to be displayed:...
Page 247 Table 6-17 Items That Can Be Added by Using the -lu -c -item Parameter and Sub-parameters Item that can be added Sub-parameter SLPR slpr The sub-parameter is: -exlu • When an HDLM management-target device is the EMC DMX series, EMC CX series, or HP EVA series: If this parameter is specified, all 32 digits of the iLU are displayed instead of truncating the iLU to 13 digits.
Page 248 Table 6-18 Displayed LU Information Displayed item Description Summary summary displayed displayed • For the Thunder 9500V series, Lightning 9900 Product series, Lightning 9900V series, Hitachi USP, Hitachi AMS2000/AMS/WMS/SMS series, Universal Storage Platform V/VM, and Virtual Storage Platform: Model name of the storage system •...
Page 249 Displayed item Description Summary summary displayed displayed 9500V series, and Hitachi AMS2000/AMS/WMS/ SMS series, the entire value of iLU is the internal LU number within the storage system. You can identify an actual LU by referencing iLU from the storage system management program. For Universal Storage Platform V/VM, and Hitachi Virtual Storage Platform, iLU is indicated by a hexadecimal number.
Page 250 Displayed item Description Summary summary displayed displayed For details about each element of the path name and its representation in Windows, see Table 6-14 Elements of a Path Name on page 6-50 • For the Thunder 9500V series, Lightning 9900 ChaPort series, Lightning 9900V series, Hitachi USP, Hitachi AMS2000/AMS/WMS/SMS series,...
Page 251 Displayed item Description Summary summary displayed displayed determined by referring to What To Do for a Path Error on page 5-4 • For the Thunder 9500V series, Lightning 9900 Type series, Lightning 9900V series, Hitachi USP, Hitachi AMS2000/AMS/WMS/SMS series, and Universal Storage Platform V/VM, and Virtual Storage Platform: Attribute of the path...
Page 252 Displayed item Description Summary summary displayed displayed • -: Indicates that intermittent error monitoring is disabled or the monitoring time for an intermittent error is out of range. • A value of at least 0: Indicates the number of errors that occurred during intermittent error monitoring.
Page 253: Parameter Used When Displaying The Format Of The View Operation
Parameter Used When Displaying the Format of the view Operation -help Use this parameter to display the view operation format. Example >dlnkmgr view -help view: Format dlnkmgr view -sys [ -sfunc | -msrv | -adrv | -pdrv | -lic| - audlog ] [-t] dlnkmgr view -stinfo [-t] dlnkmgr view -path [ -hdev HostDeviceName ] [-stname] [-iem]...
Page 254 6-66 Command Reference Hitachi Dynamic Link Manager User Guide (for Windows(R))
Page 255: Utility Reference
Utility Reference This chapter explains the utilities used by HDLM. □ Overview of the Utilities □ The DLMgetras Utility for Collecting HDLM Error Information □ The dlmpr Utility for Clearing HDLM Persistent Reservations □ The dlmprsvkey Utility for Registering an HDLM Persistent Reservation □...
Page 256: Overview Of The Utilities
Overview of the Utilities HDLM provides the following utilities: • The DLMgetras utility for collecting HDLM error information When an error occurs, this utility collects the files that contain the information that you need to submit to your HDLM vendor or maintenance company.
Page 257: Format
files, definition files, and OS information. The collected information is archived in a file and saved to a folder of your choosing. Whenever the host is restarted, some of the information that is collected by the DLMgetras utility will be cleared. As a result, whenever an error occurs, immediately execute this utility to avoid losing any valuable information.
Page 258: List Of Collected Error Information
The utility obtains logs from each application, system, and security event log. The logs obtained are those output after 00:00 on the date yyyy/ mm/dd. Specify the date in the yyyy/mm/dd format. -eventlogsize {all | maximum-file-length} Logs from all applications, systems, and security event logs are obtained.
Page 259 Folder that stores collected Files Explanation files HDLM manager log (including folder-to-which- dlmmgrn.log the driver log) collected-information-is- output\HDLM-installation- Log when updating the license hcmdslicense2.log destination-drive-name_ \Program Files\HITACHI Trace file hdlmtrn.log \DynamicLinkManager\log Java execution log (nnnn hs_err_pidnnnn.log indicates a process ID) Windows log folder-to-which- setupact.log...
Page 260 Folder that stores collected Files Explanation files All files under logs Volume Manager log folder-to-which- collected-information-is- output\Volume-Manager- installation-destination- drive-name_\Program Files \VERITAS\Volume Manager M.N\logs All files under log VCS log folder-to-which- collected-information-is- output\VCS-installation- destination-drive-name_ \Program Files\VERITAS \Cluster Server\log Integrated trace file output Integrated trace file hntrn.log folder specified in the Hitachi...
Page 261 Folder that stores collected Files Explanation files Result of the dlnkmgr view - dlmmgr-lic.txt sys -lic command Result of the dlnkmgr view - dlmmgr-lu.txt lu -item pn cp type ic ie dnu slpr clpr -exlu command Result of the dlnkmgr view - dlmmgr-lu-all.txt lu -item all -exlu command...
Page 262 Folder that stores collected Files Explanation files iSCSI registry information iscsi-reg.txt MSCS log Localhost_Cluster.log MPIO information mpio-list.txt MPIO registry information mpio-reg.txt Environment variable Path path_environ.log information Version information, sysdllexe.txt timestamps for PE format files, last modification dates, and file size information for executable files installed in the HDLM directory, HNTRLib2 directory, Hitachi common...
Page 263: The Dlmpr Utility For Clearing Hdlm Persistent Reservations
The value N depends on the setting in the dlmwebagent.properties file. The default value is 2. M.N indicates the version of VxVM, or of Veritas Storage Foundation for Windows including the VxVM. For example, 5.0 indicates Veritas Storage Foundation for Windows 5.0. For Windows Server 2003 (excluding the x86 edition) or Windows Server 2008 (excluding the x86 edition), Program Files is Program Files (x86).
Page 264: Format
Format dlmpr {-c| -d| -h} Parameters Displays a list of the paths for LUs managed by HDLM and persistent reservation information. When you specify the path ID, the persistent reservation for the path is cleared. Displays a list of the paths for LUs managed by HDLM and persistent reservation information.
Page 265: Procedure For Executing The Dlmpr Utility In Vcs Environments
Execute dlmpr -c. From the displayed list, enter the path ID where KeyCount is not 0. A confirmation message is displayed twice. Check the message and enter y. The persistent reservation is cleared. Repeat the procedure until KeyCount for all the paths is changed to 0. The following shows what happens when executing this utility.
Page 266: The Dlmprsvkey Utility For Registering An Hdlm Persistent Reservation Key
The persistent reservation is cleared. Repeat the procedure until KeyCount for all the paths is changed to 0. Restart the VCS. Restart all the other hosts from among the hosts that make up the VCS system. The dlmprsvkey Utility for Registering an HDLM Persistent Reservation Key This utility registers and displays a PRSV key on an HDLM host.
Page 267: The Dlmchkpath Utility For Checking Hdlm Paths
KAPL12106-I An attempt to register the PRSV key was successful. (PRSV key = 0123456789abcdef) In the following example, the utility registers the PRSV key by specifying it on the host: >dlmprsvkey -r 0123456789ABCDEF KAPL12104-I The operation for PRSV key registration will now start.
Page 268: Format
Format dlmchkpath {-singleconnect | -h} Parameters -singleconnect Checks whether a single path configuration is being used to connect the HDLM management-target LU to the host. Examples In the following example, the utility determines that the system is in a single-path configuration: >dlmchkpath -singleconnect KAPL12401-I All LUs managed by HDLM are in a single path configuration.
Page 269: The Dlmhostinfo Utility For Checking Hdlm Installation Information
name = view, completion time = yyyy/mm/dd hh:mm:ss Displays the format of the dlmchkpath utility. If you do not specify any parameters, a warning message will appear. The dlmhostinfo Utility for Checking HDLM Installation Information This utility either displays HDLM installation information from the command prompt or outputs the information to a file.
Page 270: The Installhdlm Utility For Installing Hdlm
No parameters Displays installation information. Example: Without specifying the -output parameter: >dlmhostinfo "installDirectory","C:\Program Files\Hitachi \DynamicLinkManager" "version","x.x.x-xx" KAPL13801-I The dlmhostinfo utility for confirming HDLM installation information completed normally. Table 7-2 Installation Information on page 7-16 refers to the items that make up the output installation information, as shown below. Table 7-2 Installation Information Item name Value...
Page 271: Format
For details about the procedure for performing an unattended installation, see Performing a New Installation of HDLM on Windows Server 2003 on page 3-28 Performing a New Installation of HDLM on Windows Server 2008 on page 3-51. Format installhdlm {-f installation-information-settings-file-name [- c ]| -v| -h} Parameters -f installation-information-settings-file-name...
Page 272 Table 7-3 Keys That Can Be Defined in the [INSTALLATION_SETTINGS] Section on page 7-18lists and explains the keys that can be defined in the [INSTALLATION_SETTINGS] section. Table 7-3 Keys That Can Be Defined in the [INSTALLATION_SETTINGS] Section Necessity of definition Maximu Upgrad charact...
Page 273 Necessity of definition Maximu Upgrad charact Key name Description installat installat ion or length installat y: Include them as management targets. n: Do not include them as management targets. If this key is omitted In Windows Server 2003, ¢ the two series are not included as management targets.
Page 274 Necessity of definition Maximu Upgrad charact Key name Description installat installat ion or length installat Specify whether to restart the host Optional Optional restart after installation. Specify either of the following values: y: Restart. n: Do not restart (default). In a cluster environment, do not specify y.
Page 275 components have already been installed. If you want to do this, first uninstall HDLM, and then perform a new installation. If you want to install all the HDLM components on a host on which ¢ only the HDLM Core components have been installed, specify n for the HDLM_core key.
Page 276 Necessity of definition Maximu Upgrade charact installat Key name Description ion or installat length installat exlio: The Extended Least I/Os algorithm (default) lbk: The Least Blocks algorithm exlbk: The Extended Least Blocks algorithm Specify the level of the error Optional Optional error_log_level information to be collected as error...
Page 277 Necessity of definition Maximu Upgrade charact installat Key name Description ion or installat length installat Specify, in minutes, the interval at Optional Optional path_health_chec which the path health check will be k_interval performed. You can specify a value from 1 to 1440.
Page 278 Necessity of definition Maximu Upgrade charact installat Key name Description ion or installat length installat on: Enable the LU dynamic removal function. off: Disable the LU dynamic removal function (default). Using either of the following Optional Optional remove_lu_force values, specify whether to remove an LU from the HDLM management target list when all paths to the LU are disconnected,...
Page 279: About The Log File
When on is specified for the auto_failback key in the installation- information settings file For an upgrade installation or re-installation: ¢ When on is specified for the auto_failback key in the installation- information settings file, or when automatic failbacks are enabled in the installation pre-settings.
Page 280: The Uninstallhdlm Utility For Uninstalling Hdlm
• The installhdlm.log file is created in the folder specified by the workdir key in the installation-information settings file. • If the installhdlm.log file already exists, log data will be appended to the file. For details about the capacity of the log output folder, see Preparations for Installing HDLM by Performing an Unattended Installation on page 3-26.
Page 281 After the uninstallhdlm utility has been executed and the host ¢ restarted, the utility is automatically deleted. After executing the uninstallhdlm utility, check the messages output ¢ to the command prompt and the uninstallhdlm.log file to make sure that HDLM has been uninstalled. The uninstallhdlm.log file is output to the folder defined in the TMP or TEMP environment variable or the folder specified in the -w parameter.
Page 282 7-28 Utility Reference Hitachi Dynamic Link Manager User Guide (for Windows(R))
Page 283: Messages
Messages This chapter describes the format and meaning of the message IDs, and also the terms used in the messages and message explanations. For details on the meaning of the return codes output by HDLM when it receives a request from Global Link Manager and measures to take for them, see Return Codes for Hitachi Command Suite Common Agent Component on page...
Page 284 □ KAPL15001 to KAPL16000 □ Return Codes for Hitachi Command Suite Common Agent Component □ Events Output to Windows Event Logs by HDLM Messages Hitachi Dynamic Link Manager User Guide (for Windows(R))
Page 285: Before Viewing The List Of Messages
Before Viewing the List of Messages This section explains the following information that is needed to locate messages and understand the explanations in the sections from KAPL01001 to KAPL02000 on page 8-4. • Format and meaning of the message IDs •...
Page 286: Kapl01001 To Kapl02000
KAPL01001 to KAPL02000 Message ID Message Text Explanation KAPL01001-I The HDLM command completed Details normally. Operation name = The HDLM command completed aa...aa, completion time = successfully. bb...bb aa...aa: clear, help, offline, online, set, or view bb...bb: Year/month/day hour:minute:second Action None.
Page 287 Message ID Message Text Explanation aa...aa: clear, set, offline, or view Action Execute help operation-name of the HDLM command (dlnkmgr) to check the parameter. Specify the correct parameter, and then retry. For details on the help operation, help (Displays the Operation Format) on page 6-4.
Page 288 Message ID Message Text Explanation then retry the HDLM command. For details on the view operation, view (Displays Information) on page 6-29. KAPL01013-E An error occurred in internal Details processing of the HDLM An error unrelated to a user command. Operation name = operation occurred during aa...aa details = bb...bb command processing.
Page 289 Message ID Message Text Explanation operation, see view (Displays Information) on page 6-29. KAPL01016-W The target CHA port was not Details found. Operation name = The path ID indicated by -pathid aa...aa and required by the -cha parameter is not an object of HDLM management.
Page 290 Message ID Message Text Explanation check the settings, and then retry. For details on the view operation, see view (Displays Information) on page 6-29. view operation ¢ Refer to 3 Creating an HDLM Environment on page 3-1. Creating an HDLM Environment or Reconfiguring the HDLM Operating...
Page 291 Message ID Message Text Explanation bb...bb: Parameters that cannot be specified at the same time Action Execute help operation of the HDLM command (dlnkmgr) to check which parameters can be specified at the same time, and then retry. For details on the help operation, see help (Displays the Operation Format) on page...
Page 292 Message ID Message Text Explanation A value other than y and n was entered. Enter y or n. Action Enter y or n. KAPL01041-E The entered value is invalid. The Details operation stops. Operation Command processing will be name = aa...aa aborted because an incorrect value was entered three times in a row for a request.
Page 293 Message ID Message Text Explanation Action None. KAPL01047-W Only one offline request can be Details registered in a batch job. The offline command cannot be executed because offline processing is already being performed. Action Wait until the offline request registered in the batch job finishes, and then retry.
Page 294 Message ID Message Text Explanation details on the online operation, online (Places Paths Online) on page 6-10. KAPL01051-I Because no path has been Details selected among the currently All the paths will be placed Online displayed paths, the paths in because the path selection the Offline(C), Offline(E), and parameter is not specified for the...
Page 295 Message ID Message Text Explanation KAPL01054-W During the offline operation Details processing of the HDLM A path that cannot be set to command, a path that cannot be Offline(C) was detected during placed in the Offline(C) status multi-path offline processing. To was detected.
Page 296 Message ID Message Text Explanation to the Online status. Is this OK? or -cha parameter has been [y/n]: specified. To continue processing, enter y. To cancel processing, enter n. aa...aa: CHA port or HBA Action If you want to execute online processing for the paths that meet the specified requirements, enter y.
Page 297 Message ID Message Text Explanation aa...aa: online, offline, set, or clear Action None. KAPL01061-I aa...aa path(s) were Details successfully placed bb...bb; This message indicates the cc...cc path(s) were not. number of the paths processed in Operation name = dd...dd an online/offline operation. aa...aa: Number of paths where the online/offline operation was successful (decimal (base-10)
Page 298 Message ID Message Text Explanation KAPL01063-I The target path(s) are already Details aa...aa. As a result of a previous online/ offline operation, the specified path has already been set to Online/Offline(C). aa...aa: Online or Offline(C) Action Use the view operation of the HDLM command (dlnkmgr) to check the status of the path.
Page 299 Message ID Message Text Explanation be used in the cluster environment. Action Make sure that all HDLM-managed storage systems support persistent reservations. Contact your storage system vendor or maintenance company to check whether the storage systems you are using support persistent reservations.
Page 300 Message ID Message Text Explanation Action Register a permanent license. KAPL01074-E The emergency license expired. Details The emergency license has expired. Register a permanent license. Action Register a permanent license. KAPL01075-E A fatal error occurred in HDLM. Details The system environment is The license information file is invalid.
Page 301 Message ID Message Text Explanation aa...aa: Windows-installation- destination-drive-name: \hdlm_license Action Store the license key file directly under the Windows installation- destination drive. KAPL01082-E There is no installable license Details key in the license key file. File There is no useable license key for name = aa...aa HDLM in the license key file.
Page 302 Message ID Message Text Explanation Execute help operation-name of the HDLM command (dlnkmgr) to check which parameter can be specified, and then retry. For details on the help operation, see help (Displays the Operation Format) on page 6-4. KAPL01089-E One of the following was Action executed at the same time as Check the license by using the...
Page 303 Message ID Message Text Explanation KAPL01097-W All the current trace files will be Details deleted. Is this OK? [y/n] If you set a value that is less than the current value of the trace file size or number of trace files, all the current trace files will be deleted.
Page 304 Message ID Message Text Explanation KAPL01102-I All the paths which pass the Details specified aa...aa port will be Multiple paths will be collectively changed to the Offline(C) placed Offline(C) because the - status. Is this OK? [y/n]: hbaportwwn parameter was specified.
Page 305 Message ID Message Text Explanation operation is executed. Do you system, enter y. If you want to want to execute the operation terminate processing, enter n. anyway? Operation name = set [y/n]: KAPL01112-E An attempt to connect to the Details HDLM driver has failed.
Page 306 Message ID Message Text Explanation using the dlnkmgr set -audlog command. KAPL01117-W An error occurred during Details processing to read the audit log An internal error occurred while configuration file. reading the audit log configuration file. Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Page 307: Kapl02001 To Kapl03000
KAPL02001 to KAPL03000 Message ID Message Text Explanation KAPL02001-I HDLM GUI has started normally. Details java.version = aa...aa aa...aa: Version Action None. KAPL02002-I HDLM GUI has terminated. Action None. KAPL02003-E You lack permission to start Action HDLM GUI. Execute the command as a user with Administrators group permissions or as an Administrator.
Page 308 Message ID Message Text Explanation Set up a path between the host and storage system, and then restart the host. KAPL02007-E The HDLM manager could not be Details connected. The aa...aa The system could not access the operation has been stopped. HDLM manager when the Option window was started up or the Set Option Information operation was...
Page 309 Message ID Message Text Explanation Refresh ¢ Clear Data ¢ Action None. KAPL02014-W No data has been input in Details aa...aa. Nothing has been entered into the input field of the Option window. aa...aa: Input item (character string) Path Health Checking ¢...
Page 310 Message ID Message Text Explanation The entered value for the input field of the Option window is not within the valid range. aa...aa: Input item (character string) Path Health Checking ¢ Interval Auto Failback Checking ¢ Interval Error Log File Size ¢...
Page 311 Message ID Message Text Explanation If you want to execute offline processing, click OK. To cancel offline processing, click Cancel. KAPL02020-I If you are sure that there would Details be no problem when the path is This is a confirmation to check placed in the Offline(C) status, whether you really want to change click OK.
Page 312 Message ID Message Text Explanation changed to Offline(C) was detected. If you want to ignore the path and continue, click OK. To cancel the operation, click Cancel. aa...aa: Path ID (decimal (base-10) number) Action If you want to continue offline processing, click OK.
Page 313 Message ID Message Text Explanation check the path status, and then retry. KAPL02028-W You lack write permission for Details the aa...aa. You do not have write permission for the specified CSV file. aa...aa: Output CSV file name Action Check whether you have access permission for the specified file and whether the specified file name is correct.
Page 314 Message ID Message Text Explanation vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-2. KAPL02032-E The aa...aa operation cannot be Details executed because the amount of There was not enough memory to...
Page 315 Message ID Message Text Explanation Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-2.
Page 316 Message ID Message Text Explanation Click Refresh to update the contents of the view operation, check the path status, and then retry. KAPL02044-W aa...aa exists already. Do you Details want to overwrite it? [OK/ The existing file will be Cancel] overwritten.
Page 317 Message ID Message Text Explanation For the Path IDs of any failed paths, see the operation log. Click Refresh to view any paths that were registered together as a batch job. KAPL02055-I The target path(s) are already Details aa...aa. The specified paths are already Online/Offline(C), as a result of the online/offline operation that was just executed.
Page 318 Message ID Message Text Explanation reconfigured, click the Refresh button. KAPL02063-W The version number cannot be Details displayed. The version number could not be acquired because an attempt to read a parameter file, which starts up the HDLM GUI, failed. Action The version number cannot be displayed, but HDLM GUI...
Page 319 Message ID Message Text Explanation contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. KAPL02077-W An attempt to acquire the Details Service Pack version information aa...aa: Code showing the reason failed. Details = aa...aa for the error Action Re-execute the command.
Page 320: Kapl03001 To Kapl04000
Message ID Message Text Explanation HDLM error information, and then contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. KAPL02087-I "Configuration View" is not Details supported for this storage "Configuration View" cannot be system model. displayed for the selected storage Please use the "Path List View"...
Page 321 Message ID Message Text Explanation Action Refer to the contents of the warning. KAPL03003-E HDLM API Error information - Details aa...aa This information is required for resolving problems. aa...aa: API trace error information Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance...
Page 322 Message ID Message Text Explanation HDLM Error Information on page 7-2. KAPL03007-E An error occurred during Details communication with the HDLM This information is required for manager. (aa...aa) resolving problems. aa...aa: API trace error information Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance...
Page 323: Kapl04001 To Kapl05000
KAPL04001 to KAPL05000 Message ID Message Text Explanation KAPL04001-I HDLM manager started. Action None. KAPL04002-E Could not start the HDLM Details manager. The HDLM manager failed to start because the current environment is unsuitable for the HDLM manager to run in. Action Execute the DLMgetras utility for collecting HDLM error information,...
Page 324 Message ID Message Text Explanation KAPL04006-E Cannot register the service Details control handler function. Return HDLM manager could not start value = aa...aa normally because it was unable to register the service control handler function. aa...aa: OS error code Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Page 325 Message ID Message Text Explanation If the same error occurs, re-install HDLM. For details on the view operation, see view (Displays Information) on page 6-29. For details on the set operation, see set (Sets Up the Operating Environment) on page 6-15.
Page 326 Message ID Message Text Explanation Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-2.
Page 327 Message ID Message Text Explanation None. KAPL04022-W HDLM manager warning Details information - aa...aa This information is required for resolving problems. aa...aa: HDLM manager trace warning information Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Page 328 Message ID Message Text Explanation KAPL04025-C A memory shortage occurred in Details the HDLM manager. There was not enough memory to run the HDLM manager processes. Action To increase the amount of free memory, terminate unnecessary applications or restart the host. KAPL04026-I The temporary license is valid.
Page 329 Message ID Message Text Explanation remaining values, the default values will be used. Action For any non-default options, use the dlnkmgr set operation to set the options again. For details on the set operation, see set (Sets Up the Operating Environment) on page 6-15.
Page 330: Kapl05001 To Kapl06000
Message ID Message Text Explanation bb...bb, Port Number= cc...cc, bb...bb: Destination IP address of Community = dd...dd, Trap the trap Data = ee..ee cc...cc: Destination port number of the trap dd...dd: Community name given to the trap ee...ee: Transmission data Action None.
Page 331 Message ID Message Text Explanation component) was initialized The HDLM driver (filter successfully. component) was successfully initialized for each device object. aa...aa: Device object address (hexadecimal number) Action None. KAPL05008-E Could not allocate memory. Details (aa...aa:bb...bb) Execute the An attempt to execute the OS DLMgetras utility to collect error memory allocation function or the information, and then contact...
Page 332 Message ID Message Text Explanation (base-10) number)), partition (cc...cc: Partition sequence number (decimal (base-10) number)), and device object address (aa...aa: Device object address (hexadecimal number)) is the first path for the LU (including the non-HDLM target device). Action None. KAPL05013-I The device (aa...aa) for Disk Details (bb...bb), Partition (cc...cc) was...
Page 333 Message ID Message Text Explanation bb...bb: Disk sequence number (decimal (base-10) number) cc...cc: Degree of progress in disk recognition processing (hexadecimal number) dd...dd: Execution result of health checking (hexadecimal number) Action Check the path for which path health checking failed. If this message is displayed for an unexpected path, contact your HDLM vendor or the maintenance...
Page 334: Kapl07001 To Kapl08000
Message ID Message Text Explanation KAPL05819-I Data for maintenance: aa...aa Details bb...bb cc...cc dd...dd. The filter driver outputs this message for maintenance. aa...aa: HDLM Device minor number (decimal (base-10) number) bb...bb: Message output location information (decimal (base-10) number) cc...cc: Detailed information 1 (decimal (base-10) number) dd...dd: Detailed information 2 (decimal (base-10) number)
Page 335 Message ID Message Text Explanation for HDLM, your maintenance company, to confirm whether your storage systems support persistent reservations. KAPL07821-I An LU that cannot use the load Details balancing function in a cluster The host is connected to an LU of configuration is connected.
Page 336: Kapl08001 To Kapl09000
KAPL08001 to KAPL09000 Message ID Message Text Explanation KAPL08019-E The path (aa...aa) detected an Details error (bb...bb). (cc...cc) An error occurred in the path. The error is most likely due to a disconnected cable. aa...aa: Path identifier (hexadecimal number) bb...bb: Error code (hexadecimal number) When the Windows plug-and- ¢...
Page 337 Message ID Message Text Explanation cc...cc: Host port number (same as PathName of view -path) (hexadecimal number) dd...dd: Bus number (same as PathName of view -path) (hexadecimal number) ee...ee: Target ID (same as PathName of view -path) (hexadecimal number) ff...ff: HLU number (same as PathName of view -path) (hexadecimal number) gg...gg: Dev number (same as...
Page 338 Message ID Message Text Explanation The auto recover function recovered a path. This message is output if an error occurs in all the paths to an LU and one of the paths is recovered. aa...aa: Path ID(same as PathID of view -path) (decimal (base-10) number) Action None.
Page 339: Kapl09001 To Kapl10000
KAPL09001 to KAPL10000 Message ID Message Text Explanation KAPL09001-E There is no system management Details permission. Login with The current user does not have administrator permission and the necessary administrator aa...aa HDLM. permission to install or uninstall HDLM. aa...aa: re-install or re- uninstall Action Re-install or re-uninstall HDLM as...
Page 340 Message ID Message Text Explanation KAPL09006-E Could not install HDLM. Action If the installation was interrupted, incomplete files and folders might remain. Manually delete all these files and folders. KAPL09007-W HDLM version aa...aa is Details installed. Do you want to Confirm whether you want to overwrite it? overwrite the existing installation.
Page 341 Message ID Message Text Explanation Objectplaza Trace Library 2 An attempt to cancel the failed. Uninstall Hitachi Network registration of the PP name of Objectplaza Trace Library 2 by HNTRLib2 has failed. referring to HDLM User's Guide Action section "Uninstalling Hitachi Manually cancel the PP name Network Objectplaza Trace registration, and then uninstall...
Page 342 Message ID Message Text Explanation Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM. KAPL09071-E The specified installation folder Details is read-only. Specify a different Since the install folder you folder. specified is read-only, you cannot install.
Page 343 Message ID Message Text Explanation Install a permanent license. KAPL09084-W The temporary license cannot be Details installed. The temporary license cannot be reused. Action Install a permanent license. KAPL09085-W The emergency license cannot Details be installed. An emergency license cannot be updated with another emergency license.
Page 344 Message ID Message Text Explanation Contact your HDLM vendor or the maintenance company if there is a maintenance contract of HDLM. KAPL09093-I aa...aa will be installed. Is this Details aa...aa: SP version that will be installed. Action To execute the installation, select OK.
Page 345 Message ID Message Text Explanation KAPL09119-W There is no installable license Details key in the license key file. File There is no HDLM-installable name = aa...aa license key in the license key file. aa...aa: Windows-installation- destination-drive-name \hdlm_license or the-file- that-the-user-specified Action Make sure that the correct license key file has been specified, and...
Page 346 Message ID Message Text Explanation An invalid PRSV key has been entered. Action Enter a valid PRSV key. KAPL09129-E The version upgrade from Details aa...aa to bb...bb cannot be If a version earlier than HDLM 5.5 executed. has already been installed, version HDLM 5.5 or later cannot be installed.
Page 347 Message ID Message Text Explanation service pack), if the Path environment variable was rounded down to 1,024 bytes, but the Microsoft patch program to solve this problem has not been applied: 1,023 bytes When the HDLM default path is specified, the following three file paths are added to the environment variable: Windows Server 2003 (x86) and...
Page 348 Message ID Message Text Explanation \Hitachi For Windows Server 2003 (excluding the x86 edition) or Windows Server 2008 (excluding the x86 edition), Program Files is Program Files (x86) C:\Program Files (x86)\Common Files\Hitachi Do not remove the search paths that were specified during the installation of Windows from the Path system environment variable because these paths are required to install HDLM.
Page 349 Message ID Message Text Explanation KAPL09173-W HDLM version aa...aa is Details installed. Do you want to aa...aa: Installed version number overwrite it with version of HDLM (character string) bb...bb? bb...bb: Version number of HDLM to be installed (character string) Action Click the OK button to upgrade or re-install HDLM.
Page 350 Message ID Message Text Explanation KAPL09183-I HDLM version aa...aa is Details installed. This version will now aa...aa: Installed version number be overwritten with version of HDLM bb...bb. bb...bb: Version number of HDLM you attempted to install Action None. KAPL09184-I The PRSV key was registered. Details (PRSV key = aa...aa) aa...aa: PRSV key (16-digits...
Page 351 Message ID Message Text Explanation Action In installhdlm utility for ¢ installing HDLM: After the computer restarts, make sure that HDLM is running correctly. In uninstallhdlm utility for ¢ uninstalling HDLM: None. KAPL09187-W No parameter is specified. Details No installation-information settings file has been specified in the installhdlm utility for installing HDLM.
Page 352 Message ID Message Text Explanation aa...aa: Invalid parameter (character string) Action Make sure that the parameters for the installhdlm or uninstallhdlm utility are appropriate, and then try again. For details on the installhdlm utility, see The installhdlm Utility for Installing HDLM on page 7-16.
Page 353 Message ID Message Text Explanation KAPL09193-W A definition in the installation Details information settings file is An invalid value has been invalid. (aa...aa = bb...bb) specified for a key. aa...aa: The key where the invalid value was specified bb...bb: The invalid key value Action Correct the definition in the installation-information settings...
Page 354 Message ID Message Text Explanation pressing Ctrl + C. The installhdlm.exe or uninstallhdlm.exe processing has ended, but the HDLM installation or uninstallation will continue. aa...aa: installhdlm.exe or uninstallhdlm.exe bb...bb: installation or uninstallation Action Refer to installhdlm.log or uninstallhdlm.log and make sure that the installation or uninstallation completed normally.
Page 355 Message ID Message Text Explanation KAPL09213-W An error occurred during aa...aa Details processing. Although the aa...aa processing has ended, an error occurred during the processing. aa...aa: dlnkmgr Action Check the error message that was output just before this message, and then perform the action indicated in that error message.
Page 356 Message ID Message Text Explanation Uninstalling HDLM on page 3-82. KAPL09222-E HDLM could not be uninstalled. Details HDLM could not be uninstalled. Action Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM. KAPL09223-E A feature could not be installed.
Page 357 Message ID Message Text Explanation will be installed, without MPIO driver bundled with HDLM overwriting the MPIO driver. will not be installed. aa...aa: Version number of the installed MPIO driver Action None. If you want to install the MPIO driver bundled with HDLM, uninstall the update (QFE) for MPIO, and then install HDLM.
Page 358 Message ID Message Text Explanation Add all of the search paths that were specified during the installation of Windows into the Path system environment variable, and then install HDLM. If you are not sure which search paths were specified during the installation of Windows, contact Microsoft.
Page 359 Message ID Message Text Explanation Action None. KAPL09260-W Errors were detected during the Details HDLM aa...aa installation check. Errors were detected during the See the previous messages to HDLM installation check. resolve the problems. aa...aa: Version of HDLM that will be installed Action See the previous warning and...
Page 360 Message ID Message Text Explanation KAPL09281-I HDLM 6.3.0 or later has been Details installed. Only the HDLM driver The MPIO driver will not be will be installed, without installed because the version of overwriting the MPIO driver. the installed MPIO driver is the same as the one bundled with HDLM.
Page 361 Message ID Message Text Explanation The Japanese SP was applied to the English edition of HDLM, or vice versa. Action Acquire the SP that has the same language as the installed HDLM, and then try again. KAPL09505-E aa...aa cannot be applied to the Details installed bb...bb.
Page 362: Kapl10001 To Kapl11000
KAPL10001 to KAPL11000 Message ID Message Text Explanation KAPL10002-W Too many parameters have Details been specified. Four or more parameters have 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 DLMgetras Utility for Collecting HDLM Error Information on page...
Page 363 Message ID Message Text Explanation utility for collecting HDLM error information, without executing it. For details on the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2. KAPL10012-W The specified file or directory Details does not exist. Line = aa...aa, The specified file or folder does Value = bb...bb not exist in the file for defining the...
Page 364 Message ID Message Text Explanation aa...aa: Collected file name bb...bb: Year/month/day hour:minute:second Action None. KAPL10022-I The utility for collecting HDLM Details error information completed Error information has been normally. collected. Action None. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-2.
Page 365 Message ID Message Text Explanation aa...aa: Information collection file Action None. KAPL10034-E The file could not be copied. Details Filename = aa...aa, Details = Execution of the cp command bb...bb failed. aa...aa: File name you tried to copy bb...bb: cp command output message Action An error occurred while the...
Page 366 Message ID Message Text Explanation 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.
Page 367 Message ID Message Text Explanation ee...ee: The command that could not be executed and the registry key that could not be obtained. Action None KAPL10640-I The dlmpr utility completed Details normally. The dlmpr utility for canceling the HDLM persistent reserve finished normally.
Page 368 Message ID Message Text Explanation HDLM Persistent Reservations on page 7-9. KAPL10651-I The user terminated the Action operation. None. KAPL10652-E The entered value is invalid. The Details operation stops An invalid response to a request was entered three times in a row. Action Re-execute the dlmpr utility.
Page 369 Message ID Message Text Explanation KAPL10659-I There is no LU for which Action persistent reservation None. information exists. KAPL10660-I There is no LU managed by Action HDLM. None. KAPL10661-E The SCSI command failed. SCSI Details Code = aa...aa, Service Action aa...aa: SCSI Code (hexadecimal = bb...bb, Status Code = number)
Page 370 Message ID Message Text Explanation aa...aa: Port number (hexadecimal number) bb...bb: Error code (hexadecimal number) Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL10665-I The dlmpr utility completed. Action None. For details on the dlmpr utility, see The dlmpr Utility for Clearing HDLM Persistent...
Page 371: Kapl11001 To Kapl12000
KAPL11001 to KAPL12000 Message ID Message Text Explanation 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 ¢...
Page 372 Message ID Message Text Explanation Get HDLM Alert Driver ¢ Status Online ¢ Offline ¢ Get SNMP Trap Information ¢ Set SNMP Trap Information ¢ Set LU Load Balance ¢ Get Path Status Log ¢ Information Get Local Time ¢ Action None.
Page 373: Kapl12001 To Kapl13000
Message ID Message Text Explanation An exception occurred during processing on the host. Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if you have a maintenance contract for HDLM. For details on the DLMgetras utility, see The DLMgetras Utility...
Page 374 Message ID Message Text Explanation an HDLM Persistent Reservation Key on page 7-12. KAPL12102-W There are too many parameters Action Make sure that the parameters for the dlmprsvkey utility for registering an HDLM persistent reservation key are appropriate, and then try again. For details on the dlmprsvkey utility, see dlmprsvkey Utility for Registering an HDLM Persistent Reservation...
Page 375 Message ID Message Text Explanation Action Try again as a user who is a member of the Administrators group. For details on the dlmprsvkey utility, see dlmprsvkey Utility for Registering an HDLM Persistent Reservation Key on page 7-12. KAPL12106-I An attempt to register the PRSV Details key was successful.
Page 376 Message ID Message Text Explanation KAPL12111-E The registry key for the Details registration destination does not The registry key exist. HKEY_LOCAL_MACHINE\SYSTEM \CurrentControlSet\Services \HDLMdsm\Parameters \PRSVKeyString does not exist. Action Check whether HDLM has been installed correctly. If it has, contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Page 377 Message ID Message Text Explanation company if there is a maintenance contract for HDLM. For details on the dlmprsvkey utility, see dlmprsvkey Utility for Registering an HDLM Persistent Reservation Key on page 7-12. KAPL12114-E An invalid PRSV key has been Details registered.
Page 378 Message ID Message Text Explanation error occurs before the PRSV key can be acquired. aa...aa: Maintenance information 1 (hexadecimal number) bb...bb: Maintenance information 2 (hexadecimal number) cc...cc: Maintenance information 3 (hexadecimal number) dd...dd: Maintenance information 4 (hexadecimal number) Action None. KAPL12119-E Trace data for maintenance: Details...
Page 379 Message ID Message Text Explanation vendor or the maintenance company if there is a maintenance contract for HDLM. If the WMI repository is corrupted, consider rebuilding the repository. KAPL12151-W A Windows Management Details Instrumentation service access A Windows Management error occurred. Details = Instrumentation service access aa...aa, bb...bb error occurred.
Page 380 Message ID Message Text Explanation vendor or the maintenance company if there is a maintenance contract for HDLM. If the WMI repository is corrupted, consider rebuilding the repository. KAPL12401-I All LUs managed by HDLM are in Details a single path configuration. This message is displayed when the number of LUs managed by HDLM is 0.
Page 381: Kapl13001 To Kapl14000
Message ID Message Text Explanation Terminate unnecessary applications to increase the amount of free memory. Alternatively, restart the host. KAPL12406-E An error occurred in internal Details processing of the utility for aa...aa: Error code checking HDLM paths. Error bb...bb: Details code code = aa...aa, details code = bb...bb Action...
Page 382 Message ID Message Text Explanation KAPL13603-W The audit log configuration file is Details invalid. Execute the "dlnkmgr The audit log configuration file is view -sys -audlog" command invalid. and check the setting. Action Restart the HDLM manager, execute the dlnkmgr view -sys -audlog command, and then specify any desired settings by using the dlnkmgr set -audlog.
Page 383 Message ID Message Text Explanation KAPL13803-W The user does not have the Details privileges required to execute The dlmhostinfo utility must be the dlmhostinfo utility for executed by a user with confirming HDLM installation Administrator group privileges. information. Action Re-execute the dlmhostinfo utility as a user with Administrator group privileges.
Page 384: Kapl15001 To Kapl16000
Message ID Message Text Explanation The installation information ¢ file already exists. A folder with the same name ¢ as the installation information file exists. The parent folder does not ¢ exist. The user does not have write ¢ permission for the parent folder.
Page 385 Message ID Message Text Explanation KAPL15032-I An HDLM persistent reservation Details key was successfully displayed. aa...aa: Name of the utility that Command Line = aa...aa the user executed KAPL15033-W An attempt to display an HDLM Details persistent reservation key has aa...aa: Name of the utility that failed.
Page 386 Message ID Message Text Explanation KAPL15105-I Setting up the operating Details environment succeeded. aa...aa: Command that the user Command Line = aa...aa executed KAPL15106-W Setting up the operating Details environment failed. Command aa...aa: Command that the user Line = aa...aa executed KAPL15107-I Program information was...
Page 387: Return Codes For Hitachi Command Suite Common Agent Component
Message ID Message Text Explanation cc...cc path(s) could not be aa...aa: Number of paths that placed bb...bb. were successfully placed online or offline bb...bb: Online or Offline cc...cc: Number of paths that failed to be placed online or offline KAPL15208-W aa...aa path(s) were failed to Details place bb...bb.
Page 388 Message ID Explanation Terminate unnecessary applications to increase free memory, or restart the host. 1006 Details An Offline path cannot be placed Online. Action Remove the error in the path, and then retry. 1007 Details The target path of the offline operation is the last, remaining path connected to the device and therefore, cannot be placed in the offline status.
Page 389 Message ID Explanation Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if you have a maintenance contract for HDLM. For details on the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2.
Page 390 Message ID Explanation Set the intermittent error-monitoring interval to a value that is equal to or greater than (automatic-failback-checking-interval x number-of- times-error-is-to-occur-for-intermittent-error-monitoring). 1033 Details An attempt to acquire the HDLM version information failed. Action Re-execute the command. If the same error occurs again, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM.
Page 391 Message ID Explanation vendor or maintenance company if you have a maintenance contract for HDLM. For details on the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2. 1038 Details A storage system that cannot use the load balancing function is connected.
Page 392: Events Output To Windows Event Logs By Hdlm
Events Output to Windows Event Logs by HDLM The following table lists Table 8-3 Events Output to the Windows Application Log on page 8-110 Table 8-4 Events Output to the Windows System Log on page 8-111 events output by HDLM to Windows event logs. Table 8-3 Events Output to the Windows Application Log Message ID Type...
Page 393 Message ID Type Source Category Event ID User KAPL05011-E Error DLMManager None 20491 KAPL07820-E Error DLMManager None 29492 KAPL08019-E Error DLMManager None 32787 KAPL08022-E Error DLMManager None 32790 KAPL08023-I Information DLMManager None 32791 KAPL08025-I Information DLMManager None 32793 KAPL08026-E Error DLMManager None 32794...
Page 394 8-112 Messages Hitachi Dynamic Link Manager User Guide (for Windows(R))
Page 395: Functional Differences Between Version 6.0.1 Or Later And Versions Earlier Than 6
Functional Differences Between Versions of HDLM This section explains the functional differences between newer and older versions of HDLM. □ Functional Differences Between Version 6.6 or Later and Versions Earlier Than 6.6 □ Functional Differences Between Version 6.2 or Later and Versions Earlier Than 6.2 □...
Page 396: A Functional Differences Between Versions Of Hdlm
□ Differences in Default Values □ Differences in the Load Balancing Function in an MSCS Environment Functional Differences Between Versions of HDLM Hitachi Dynamic Link Manager User Guide (for Windows(R))
Page 397: Functional Differences Between Version 6.6 Or Later And Versions Earlier Than 6.6
Functional Differences Between Version 6.6 or Later and Versions Earlier Than 6.6 • The type of the messages listed below that are output to the event log has been changed from Error to Warning in HDLM version 6.6. Also, the level of the message IDs has been changed from E to W.
Page 398: Functional Differences Between Version 5.9.1 Or Later And Versions Earlier Than
Functional Differences Between Version 5.9.4 or Later and Versions Earlier Than 5.9.4 • The following operations have been changed to reduce the number of responses required during an installation: Entry of user information has been deleted. ¢ When the dlmprsvkey utility for registering an HDLM persistent ¢...
Page 399: Automatic Switching Of Paths That Have The Online(E), Offline(C), Or Offline(E) Status
• An LU has been removed from being an HDLM management-target Automatic Switching of Paths That Have the Online(E), Offline(C), or Offline(E) Status In HDLM 5.5 or later, if one of the following conditions is satisfied, the status of Online(E), Offline(C), or Offline(E) paths will automatically change to Online.
Page 400: Differences In The Lu Dynamic Removal Function
Differences in the LU Dynamic Removal Function Depending on the HDLM version, the LU dynamic removal function differs as follows: • In HDLM 05-02, and 5.4 When Remove the LU even if there are Offline(C) paths is not ¢ specified or when the HDLM command dlnkmgr set -rmlu on is executed If none of the paths connected to an LU are Online or Offline(C), the LU will be removed from being an HDLM management-target.
Page 401: Differences In The Drive Letters Displayed In Windows
Differences in the Drive Letters Displayed in Windows Depending on the HDLM version, the Windows' drive letters that are displayed when all paths connected to the LU have an error status differ as follows: • When the LU dynamic removal function is not used in HDLM 5.4 Drive letters are displayed for the disks that are displayed in My Computer.
Page 402 MSCS environment, even if you set the load balancing function to on, it will automatically change to off. Functional Differences Between Versions of HDLM Hitachi Dynamic Link Manager User Guide (for Windows(R))
Page 403: Acronyms And Abbreviations
Acronyms and abbreviations The following acronyms and abbreviations might be used in this guide. Arbitrated Loop Application Programming Interface Automatic Storage Management BIOS Basic Input / Output System Channel Adapter CLPR Cache Logical Partition Central Processing Unit Acronyms-1 Hitachi Dynamic Link Manager User Guide (for Windows(R))
Page 404 Comma Separated Value Control Unit DBMS Database Management System Data Execution Prevention Device Domain Name Server Fibre Channel FC-SP Fibre Channel Security Protocol Failover FQDN Fully Qualified Domain Name Greenwich Mean Time GUID Partition Table Acronyms-2 Hitachi Dynamic Link Manager User Guide (for Windows(R))
Page 405 Graphical User Interface GUID Globally Unique Identifier Host Bus Adapter HDev Host Device Host Logical Unit HTTP Hypertext Transfer Protocol Input/Output Internet Protocol Itanium(R) Processor Family iSCSI Internet Small Computer System Interface Local Area Network LDAP Lightweight Directory Access Protocol Acronyms-3 Hitachi Dynamic Link Manager User Guide (for Windows(R))
Page 406 LDEV Logical Device Logical Unit Logical Unit Number MPIO Multipath I/O Multiple Virtual Storage Network Interface Card Network Time Protocol Operating System Port PRSV Persistent Reserve Acronyms-4 Hitachi Dynamic Link Manager User Guide (for Windows(R))
Page 407 Quick Fix Engineering RADIUS Remote Authentication Dial in User Service Storage Area Network SCSI Small Computer System Interface SLPR Storage Logical Partition SMTP Simple Mail Transfer Protocol SNMP Simple Network Management Protocol Service Pack Secure Sockets Layer Service Processor Windows Management Instrumentation Acronyms-5 Hitachi Dynamic Link Manager User Guide (for Windows(R))
Page 408 World Wide Name Acronyms-6 Hitachi Dynamic Link Manager User Guide (for Windows(R))
Page 409: Glossary
Glossary This glossary explains the terms used in this manual. automatic failback A function for checking the status of paths at regular intervals, and automatically placing the status of a path recovered from an error into the Online status. If a path with an Offline(E) or Online(E) status recovers from an error, an automatic failback will place the path Online.
Page 410 cluster A system of connecting multiple hosts with the same OS or platform (essentially, an environment in which the same application can run) and treating them as one system. A logical division of an LU that HDLM controls and operates. A Dev is equivalent to a partition in Windows.
Page 411 FC-SAN (Fibre Channel - Storage Area Network) A SAN using Fibre Channel. HBA (Host Bus Adapter) A device that is an interface between hosts and external devices. In this manual, the term HBA indicates an interface card that is mounted on a host from which the host connects to a storage system via a SCSI or FC connection.
Page 412: Load Balancing
intermittent error An error that occurs irregularly due to, for example, a loose cable connection. IP-SAN (Internet Protocol - Storage Area Network) A data transfer network that connects hosts and storage systems by using the iSCSI standard. LDEV (Logical Device) A combination of the storage system's product name, serial number, and an internal LU.
Page 413 non-owner path A path that passes through a non-owner controller. Non-owner paths exist only in the Thunder 9500V series, or Hitachi AMS/WMS series. (See also: owner path, non-owner controller) owner controller A controller that has been set as an owner controller for an LU. Owner controllers are only in the Thunder 9500V series, or Hitachi AMS/WMS series.
Page 414 A path name is used to identify a path. (See also: host LU number) persistent reservation Similar to reservations, persistent reservations enable a server to declare that it has exclusive rights to use an LU, and prevents other servers from accessing that LU. Note, however, that while reservations allows a server to have exclusive use of only one path to the LU, persistent reservations allow a server to have exclusive rights to use multiple paths.
Page 415: Index
Index command format active host 2-44 overview audit log command device 2-3, 6-52 categories and audit events that HDLM can command of HDLM (dlnkmgr) output 2-37 clear collecting data 2-35 help data format 2-42 offline automatic failback 2-18, 6-20, Glossary-1 online 6-10 automatic failover...
Page 416 dlmhostinfo 7-15 Events Output to Windows Event Logs by HDLM dlmpr 8-110 dlmprsvkey 7-12 examining dlnkmgr message DNum driver level HDLM and MPIO drivers 2-10 dynamic reconfiguration Glossary-2 failback 1-3, 2-16, Glossary-2 failover 1-3, 2-16, Glossary-2 FC-SAN 2-3, 2-4, Glossary-3 features of HDLM EMC CX series filter...
Page 417 features functions installing 3-24 count new installation (on Windows Server 2003) 3-28 errors new installation (on Windows Server 2008) 3-51 identifying notes on versions 3-14 error path overview Information 2-34 program information 6-31 HDLM management-target device 6-37 setup 3-68 installation 3-24 uninstalling 3-82...
Page 418 LU configuration recognized by the host on unattended installations 3-27 6-51 on Windows 3-16 storage systems 3-14 number of error log files 6-18 number of trace files 6-19 manual path switching 2-19 message examining message element obtaining DNum path information ErrorCode program information PathID...
Page 419 path switching starting automatically 2-17 HDLM manager 4-14 manually 2-19 statistics PathID clearing to the initial value PathName stopping paths to which load balancing is applied 2-13 HDLM manager 4-15 Performance 4-12 storage systems Performance Monitor 4-12 notes 3-14 Performing Failovers and Failbacks Using Path syntax conventions Switching 2-16...
Page 420 3-7, 3-8, 3-9, 3-86 vendor ID 6-47 view 6-29 viewing GUI Help Warning 2-34 what is HDLM? what to do for program error Windows notes on 3-16 Index-6 Hitachi Dynamic Link Manager User Guide (for Windows(R))
Page 421 Hitachi Dynamic Link Manager User Guide (for Windows(R))
Page 422 Hitachi Data Systems Corporate Headquarters 750 Central Expressway Santa Clara, California 95050-2627 U.S.A. Phone: 1 408 970 1000 www.hds.com [email protected] Asia Pacific and Americas 750 Central Expressway Santa Clara, California 95050-2627 U.S.A. Phone: 1 408 970 1000 [email protected] Europe Headquarters Sefton Park Stoke Poges Buckinghamshire SL2 4HD...

This manual is also suitable for:

Dynamic link manager

Hitachi XP P9500 User Manual

1 Overview of HDLM

2 HDLM Functions

3 Creating an HDLM Environment

4 HDLM Operation

5 Troubleshooting

6 Command Reference

7 Utility Reference

8 Messages

A Functional Differences between Versions of HDLM

Quick Links

Related Manuals for Hitachi XP P9500

Summary of Contents for Hitachi XP P9500