Hitachi Command Suite Dynamic Link Manager Software User Guide (for Windows(R)) Document Organization Product Version Getting Help Contents MK-92DLM129-21
© 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. (hereinafter referred to as "Hitachi") and Hitachi Data Systems Corporation (hereinafter referred to as "Hitachi Data Systems").
Contents Preface..................................................................................................xi Intended audience....................................................................................................xii Product version........................................................................................................xii Release notes...........................................................................................................xii Document revision level...
Automatic Failovers...............................................................................2-17 Automatic Failbacks...............................................................................2-18 Manual Path Switching....................................................................................2-19 Path Status Transition.....................................................................................2-20 The Online Path Statuses............................................................
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........................................................
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...........................................................
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.......................
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......
KAPL09001 to KAPL10000......................................................................................8-57 KAPL10001 to KAPL11000......................................................................................8-80 KAPL11001 to KAPL12000......................................................................................8-89 KAPL12001 to KAPL13000......................................................................................8-91 KAPL13001 to KAPL14000......................................
x Hitachi Dynamic Link Manager User Guide (for Windows(R))
Preface This document describes how to use the Hitachi Dynamic Link Manager.
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 • Storage system management functionality • Cluster software functionality • Volume management software functionality Product version This document revision applies to HDLM for Windows version 7.2 or later.
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. 5 Troubleshooting on page 5-1 Describes how to troubleshoot a path error, HDLM failure, or any other problems that you might encounter. 6 Command Reference on page 6-1 Describes all the HDLM commands.
These conventions are described below. General font conventions The following table lists the general font conventions: Font Bold Italics Convention 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. For example, bold is used in sentences such as the following: • From the File menu, choose Open. • Click the Cancel button. • In the Enter name entry box, type your name.
Example font or symbol SD Convention Bold code-font characters indicate the abbreviation for a command. perm Underlined characters indicate the default value. [ ] 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. { } One of the options enclosed in { } must be specified. | Only one of the options separated by a vertical bar can be specified at the same time. ... An ellipsis (...
Logical capacity unit Value 1 TB 1,024 GB or 1,0244 bytes 1 PB 1,024 TB or 1,0245 bytes 1 EB 1,024 PB or 1,0246 bytes Getting help The Hitachi Data Systems customer support staff is available 24 hours a day, seven days a week. If you need technical support, log on to the Hitachi Data Systems Portal for contact information: https://hdssupport.hds.com Comments Please send us your comments on this document: doc.comments@hds.com.
1 Overview of HDLM HDLM is a software package that manages paths between a host and a storage system. HDLM is designed to distribute loads across multiple paths and will switch a given load to another path if there is a failure in the path that is currently being used, thus improving system reliability. This chapter gives an overview of HDLM and describes its features.
What is HDLM? With the widespread use of data warehousing and increasing use of multimedia data, the need for high-speed processing of large volumes of data on networks has rapidly grown. To satisfy this need, networks dedicated to the transfer of data, such as SANs, are now being used to provide access to storage systems. HDLM manages the access paths to these storage systems.
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. For details on load balancing, see Distributing a Load Using Load Balancing on page 2-11.
1-4 Overview of HDLM Hitachi Dynamic Link Manager User Guide (for Windows(R))
2 HDLM Functions This chapter describes the various functions that are built into HDLM. Before the function specifications are explained though, this chapter will go into detail about the HDLM management targets, system configuration, and basic terms that are necessary to know to effectively operate HDLM. After that, the rest of the chapter focuses on describing all the HDLM functions, including the main ones: load distribution across paths and path switching.
□ Integrated HDLM management using Global Link Manager □ Cluster Support 2-2 HDLM Functions Hitachi Dynamic Link Manager User Guide (for Windows(R))
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.
Figure 2-1 Configuration of an HDLM System When Using an FC-SAN on page 2-4 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. Table 2-1 HDLM System Components When Using an FC-SAN Components Description HBA A host bus adapter. This serves as a cable port on the host.
must be installed ahead of time on the host. The cable port on the storage system is called a port (P) on a channel adapter (CHA) used for iSCSI connections. A logical unit (LU), which lies in a storage system, is either an input target or an output target to or from a host. The areas within an LU are called Devs. A route that connects a host to a Dev in an LU is called a path. HDLM assigns a unique ID to each management-target path. This ID is called AutoPATH_ID.
Figure 2-3 Configuration of an IP-SAN System When Using iSCSI Software and an NIC 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 The driver software that contains the iSCSI initiator function iSCSI HBA A host bus adapter that contains the iSCSI initiator function. This serves as a cable port on a host.
Components Path Description 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. • IP addresses Use the same network address for both an HBA and a CHA port connected via a common path.
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. After the installation of HDLM, an LU recognized by a host is called a host LU (HLU). The areas in a host LU that correspond to the Devs in a storage system LU are called host devices (HDev).
Components HDev Description 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. Figure 2-5 Configuration of the HDLM Programs on page 2-9 shows the configuration of the HDLM programs.
Program name Functions • HDLM command HDLM utility HDLM manager Set up the HDLM operating environment Provides the dlnkmgr command, which enables you to: • Manage paths • Display error information • Set up the HDLM operating environment Provides the HDLM utility, which enables you to: • Collect error information • Clear persistent reservations • Register persistent reservation keys • Check the configuration of the paths • Check the installation information • Perform unattended install
Figure 2-6 Driver Levels of the HDLM and MPIO Drivers Distributing a Load Using Load Balancing When the system contains multiple paths to a single LU, HDLM can distribute the load across the paths by using multiple paths to transfer the I/O data. This function is called load balancing, and it prevents a single, heavily loaded path from affecting the performance of the entire system. Note that some I/O operations managed by HDLM can be distributed across all, available paths, and some cannot.
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.
Figure 2-8 Flow of I/O Data When the Load Balancing Function Is Used When the load balancing function is used, I/O operations are distributed via multiple paths (A, B, C, and D). This helps to prevent problems with system performance and helps prevent bottlenecks from occurring. Paths to Which Load Balancing Is Applied This subsection describes, for each type of storage system, the paths to which the load balancing function is applied.
load balancing will be performed among the remaining, usable owner paths. It is only when absolutely no owner paths are available, that load balancing is then performed among the non-owner paths. For the example in Figure 2-9 Overview of Load Balancing on page 2-14, suppose that in the owner controller of LU0 is CHA0. When the LU is accessed, the load is balanced between the two paths A and B, which are both owner paths.
• 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. The following describes both of these processing methods: The Round Robin, Least I/Os, and Least Blocks algorithms These algorithms select which path to use every time an I/O is issued.
Table 2-5 Features of the Load Balancing Algorithms Algorithm type • Round Robin# • Least I/Os • Least Blocks • Extended Round Robin • Extended Least I/Os • Extended Least Blocks Algorithm features These types of algorithms are most effective when a lot of discontinuous, non-sequential I/Os are issued.
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. • A user executed the HDLM command's offline operation. For details on the offline operation, see offline (Places Paths Offline) on page 6-6. • Hardware, such as cables or HBAs, has been removed.
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. In order to use the automatic failback function, HDLM must already be monitoring error recovery on a regular basis.
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.
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 nonowner paths.
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: a. 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 Offline(P) and the other path is Online(E). b.
Figure 2-11 Path Status Transitions Legend: Online operation: Online operation performed in the Path Management window or by executing the dlnkmgr command's online operation. Offline operation: Offline operation performed in the Path Management window or by executing the dlnkmgr command's offline operation. #1 During reserve processing for an LU, the Online status is temporarily changed to Online(P). When the reservation processing finishes, the Online(P) status is changed to Offline(C).
When the following conditions are all satisfied, a path that has been determined to have an intermittent error also becomes subject to automatic failback: ¢ ¢ ¢ All the paths connected to an LU are Online(E), Offline(E), or Offline(C). All the paths connected to an LU have been determined to have an intermittent error. The processing of continuous I/O operations issued to an LU is successful. #5 During reserve processing for an LU, the Offline(E) status is temporarily changed to Offline(P).
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. When you use the LU dynamic deletion function, the Online(E) path will be deleted. Therefore, that path is not displayed in the Path Management window.
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 errormonitoring interval, then an intermittent error will occur on the path.
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.
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.
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.
Number of errors and time passed since error monitoring started Information about paths not subject to automatic failback Taking the path Offline(C) Reset Reset Placing the path Online while intermittent error monitoring is not being performed (Not applicable) (Not counted.
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. This function is called path health checking.
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. For details on the set operation, see set (Sets Up the Operating Environment) on page 6-15.
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. You can use the error information to examine the status of an error and analyze the cause of the error.
A system memory dump file is a file to which the system memory data is output when a Windows system is down. Specify the following procedure to output the system memory dump file. Click Control Panel, System, Startup/Shutdown, Write Debugging Information is chosen with Recovery, and then choose Kernel Memory Dump or Complete Memory Dump. Table 2-7 Types of Error Information on page 2-33 describes the types of error information.
#1 For Windows Server 2003 (excluding the x86 edition) and Windows Server 2008 (excluding the x86 edition), Program Files is Program Files (x86). #2 The underlined part indicates the folder specified during the installation. After obtaining these files, be sure to also copy them to a backup location. For details on error levels, see Filtering of Error Information on page 2-34. Note To collect logs, HDLM uses the Hitachi Network Objectplaza Trace Library service.
¢ 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 (including maintenance information).
Category Explanation • Failure LinkStatus An abnormal hardware or software event, including: • Hardware errors • Software errors (such as memory errors) An event indicating the linkage status between devices: • ExternalService Authentication AccessControl ContentAccess ConfigurationAccess Maintenance 2-36 Startup and termination of software running on storage systems, software running on SVPs (service processors), and Hitachi Command Suite products Link up or link down An event indicating
Category AnomalyEvent Explanation An event indicating an abnormal state such as exceeding a threshold, including: • Exceeding a network traffic threshold • Exceeding a CPU load threshold • Reporting that the temporary audit log data saved internally is close to its maximum size limit or that the audit log files have wrapped back around to the beginning An event indicating an occurrence of abnormal communication, including: • A SYN flood attack or protocol violation for a normally used port • Acces
Category Authentication ConfigurationAccess 2-38 Explanation Audit event Severity #1 Message ID Startup of the HDLM GUI was successful. 6 KAPL15201-I Startup of the HDLM GUI failed. 4 KAPL15204-W Termination of the HDLM GUI was successful. 6 KAPL15202-I Administrator or Permission has end-user not been granted authentication to execute the HDLM command. 4 KAPL15111-W Permission has not been granted to execute HDLM utilities.
Category Explanation Audit event An attempt to display program information was successful. Severity #1 6 Message ID KAPL15107-I An attempt to 4 display program information failed. KAPL15108-W An attempt to 6 display HDLM managementtarget information was successful. KAPL15109-I An attempt to 4 display HDLM managementtarget information failed. KAPL15110-W An attempt to place a path online by using the HDLM GUI was successful.
Category Explanation Audit event Severity #1 Message ID An attempt to perform an operation by using the HDLM GUI failed. 4 KAPL15206-W Processing of the dlmprsvkey -r command was successful. 6 KAPL15030-I Processing of the dlmprsvkey -r command failed. 4 KAPL15031-W Processing of the dlmprsvkey -v command was successful. 6 KAPL15032-I Processing of the dlmprsvkey -v command failed. 4 KAPL15033-W Processing of the dlmchkpath singleconnect command was successful.
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) Note: ¢ You might need to perform operations such as changing the log size and backing up and saving collected log data, because the amount of audit log data might be quite large.
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 The following shows the format of message-section and explains its contents.
Item# Explanation Location identification information Location identification information FQDN Fully qualified domain name Redundancy identification information Redundancy identification information Agent information Agent information Host sending request Name of the host sending a request Port number sending request Number of the port sending a request Host receiving request Name of the host receiving a request Port number receiving request Number of the port receiving a request Common op
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 2-44.
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. The trigger for switching nodes is dependent on the cluster software.
2-46 HDLM Functions Hitachi Dynamic Link Manager User Guide (for Windows(R))
3 Creating an HDLM Environment This chapter explains how to set up an HDLM environment and also how to erase environment settings. Make sure that you have already installed HDLM and configured the function settings.
HDLM System Requirements Check the following before installing HDLM: 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.
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 3-3 lists the versions of the Microsoft MPIO driver bundled with HDLM.
Table 3-3 Supported Storage systems Supported storage systems#1 EMC DMX series#2 FC I/F Y#3 Y#3 -- -- -- -- EMC CX series#4 FC I/F Y#3 Y#3 Y Y Y Y • Hitachi AMS FC I/F Y Y Y Y Y Y • Hitachi WMS iSCSI I/ F Y Y Y Y Y Y Hitachi AMS2000 series FC/IF Y Y Y Y Y Y Hitachi SMS FC I/F Y Y Y Y Y Y iSCSI I/ F Y Y Y Y Y Y FC I/F Y Y Y Y Y Y iSCSI I/ F Y Y Y -- -- -- FC I/F Y Y Y Y Y Y • Hitachi Virtual Storage FC I/F Platform Y Y Y Y Y
Legend: Y: Usable --: Not usable FC I/F: FC Interface iSCSI I/F: iSCSI Interface #1 Dual controller configuration is required. #2 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. When using systems of the EMC DMX series other than the EMC DMX3000, evaluate the connection in advance. #3 SP1 or later must be installed. #4 The evaluation of EMC CX700 has been completed.
Table 3-4 Related Programs When Intermediate Volumes Managed by Hitachi RapidXchange Are Used to Exchange Data OS Related programs Windows Server 2003 R2 (x64) SP2#1 File Access Library and File Conversion Utility (FAL/FCU) Windows Server 2003 (x86)#1 File Access Library and File Conversion Utility (FAL/FCU) 01-05-66/25 or later#2 01-03-64/21 or later#3 01-04-64/20 or later#4 #1 For details, see Supported OSs on page 3-2 in OSs Supported by HDLM on page 3-2.
Table 3-5 Supported Cluster Software OS Windows Server 2003 (IPF)#2 SP EMC CX series HP EVA series MSCS Y Y Y Y SP1 MSCS Y Y Y Y VCS 5.0 Y -- -- -- Oracle RAC 10g#1 Y -- -- -- MSCS Y Y Y Y VCS 5.0 Y -- -- -- Oracle RAC 10g#1 Y -- -- -- MSCS Y -- Y Y VCS 4.3 Y -- -- -- Oracle RAC 10g#1 Y -- -- -- MSCS Y -- Y Y VCS 4.3 Y -- -- -- Oracle RAC 10g#1 Y -- -- -- Oracle RAC 11g#1 Y -- -- -- MSCS Y -- Y Y VCS 4.3, 5.
OS SP SP2 Windows Server 2003 (x86)#2 No service pack SP1 SP2 3-8 Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP, Hitachi AMS2000/ AMS/WMS/ SMS series, Universal Storage Platform V/VM, and Virtual Storage Platform EMC DMX series EMC CX series HP EVA series Oracle RAC 11g#1 Y -- -- -- MSCS Y -- Y Y VCS 4.3, 5.0 Y -- -- -- Oracle RAC 10g#1 Y -- -- -- Oracle RAC 11g#1 Y -- -- -- MSCS Y Y Y Y VCS 4.1, 4.2, 4.
OS Windows Server 2003 R2 (x86)#2 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 EMC DMX series EMC CX series HP EVA series MSCS Y Y Y Y VCS 4.3, 5.0 Y -- -- -- Oracle RAC 10g#1 Y -- -- -- Oracle RAC 11g#1 Y -- -- -- MSCS Y Y Y Y VCS 4.3, 5.0, 5.
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 EMC DMX series EMC CX series HP EVA series MSCS Y -- Y -- Oracle RAC 11g#1 Y -- -- -- MSCS Y -- Y -- VCS 5.
- 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. 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 ¢ The DiskReservation agent of the VCS is not supported.
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 OS Required memory Not used Windows 40MB Used Windows 65MB Disk Requirements This section describes the disk capacity requirements for a host.
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 Number of LUs 1 to 256 Number of paths per LU 1 to 12 Total number of paths 1 to 3060 Flow for Creating an HDLM Environment Set up the environment to use HDLM as follows.
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.
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. Trace information for the HDLM manager is output to trace files.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
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 reregister the PRSV key. If the PRSV key is unregistered, HDLM functions might not properly operate. For details about the dlmprsvkey utility, see The dlmprsvkey Utility for Registering an HDLM Persistent Reservation Key on page 7-12.
24. 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 25. 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.
¢ If you are not performing an unattended installation, insert the DVD into the drive. In the displayed window, click the Install button next to for Windows of Hitachi Dynamic Link Manager Software. If no window is displayed, manually run the installer (setup.exe). The program checks whether HDLM has already been installed. If the KAPL09173-W message appears, perform the procedure shown in Upgrade Installation or Re-installation of HDLM on page 3-63. If a message does not appear, go to the next step.
¢ ¢ 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. If Global Link Manager will not be used to manage HDLM, you do not need to take any action.
20. Make sure that all the hosts in the cluster system have completely shut down. 21. Restart each host. 22. Log on to Windows again as a member of the Administrators group. 23. Execute the dlnkmgr command's view operation to display the status of each program. An example of executing the dlnkmgr command's view operation is as follows: >dlnkmgr view -sys HDLM Version : x.x.
29. Shut down the host. 30. Perform steps 21 to 29 on all the hosts that make up the cluster system. 31. Restart each host. 32. Install MSCS on each host. 33. Shut down all the hosts. 34. Restart each host again. 35. Log on to Windows as a member of the Administrators group. 36. Execute the dlnkmgr command's view operation to display the status of each program. Make sure that on MSCS is displayed in Support Cluster.
The license key file will be deleted after the installation finishes. 5. 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. If no window is displayed, manually run the installer (setup.exe). The program checks whether HDLM has already been installed.
¢ ¢ 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. If Global Link Manager will not be used to manage HDLM, you do not need to take any action.
18. Perform steps 1 to 17 on all the hosts that make up the cluster system. 19. Make sure that all the hosts that make up the cluster system have completely shut down. 20. Modify the storage system settings. Modify the storage system settings by following the procedure described in the maintenance documentation for that particular storage system. 21. Restart each host. 22. Log on to Windows again as a member of the Administrators group. 23.
27. Connect cables to all the HBAs to change the configuration to a multi-path configuration. 28. Check the path information as described in Checking the Path Configuration on page 3-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. To migrate HDLM 5.4 or earlier to version 5.5 or later, see Migrating from HDLM 5.4 or Earlier to HDLM 5.5 or Later on page 3-64.
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. For details about unattended installations, see The installhdlm Utility for Installing HDLM on page 7-16. Migrating from HDLM 5.4 or Earlier to HDLM 5.5 or Later To upgrade from HDLM 5.
\HDLM-installation-folder\config\dlmmgr.xml \HDLM-installation-folder\config\dlmwebagent.properties 6. Delete the files copied in step 1. 7. Restart the host. Note: When you install HDLM 5.5 or later in an environment where HDLM 5.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. Note, however, that leaving DLMAlertDriver on the window will not affect HDLM operations: a.
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.
2. Execute the firewall_setup command. 3. 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. The firewall_setup command is stored in the following locations: installation-folder-for-Hitachi-Command-Suite-Common-agent-Component \bin\firewall_setup.
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. For details about the Path List view, see the HDLM GUI Help.
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: • Windows Server 2008 supports user account control (UAC). As a result, to execute an HDLM command, perform one of the following: ¢ ¢ • Use the Administrator account to perform an operation.
Setting Up the HDLM Functions The recommended and default values for each HDLM function is shown below in 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 Load-balancing Default value Recommended value on on The Extended Least I/Os algorithm is used. The recommended algorithm depends on the operating environment.
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. For details on the cluster software supported by HDLM, see Cluster Support on page 2-44.
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-automaticfailbacks x number-of-times-an-error-is-to-occur-during-intermittenterror-monitoring If this condition is not satisfied, an error will occur and the warning message KAPL01080-W will be output.
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.
Values in the set operation Description 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. To disable the LU deletion function, specify off. If you specify on, you can set the conditions for the -force parameter.
>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. Table 3-17 Values for the Trace Level Setting Value Description 0 No trace is output. 1 Only error information is output. 2 Program operation summaries are output.
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. By specifying both the log file size and the number of log files, you can collect up to 32000000KB (approximately 30GB) of error log information.
• 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). For the number of trace files, you can specify a value from 2 to 64.
Value (severity) Explanation 7 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 ss Audit log events of the StartStop category are collected. c Audit log events of the Authentication category are collected. ca Audit log events of the ConfigurationAccess category are collected.
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) Audit Log Category : a11 KAPL01001-I The HDLM command completed normally.
Setting Number of messages to be output per monitoring interval Recommended value Default value Buffer size per monitoring interval 64 (KB) 256 (KB) Monitoring cycle 0 (seconds) 0 (seconds) Number of messages to be output 0 0 If Hitachi Network Objectplaza Trace Library (HNTRLib2) is already installed, the existing settings will be inherited. If you change these settings, keep in mind that programs other than HDLM also use them.
Figure 3-5 Hitachi Network Objectplaza Trace Utility 2 Release 2.0 Dialog Box. 2. In Number of Files, change the number of integrated trace files. The default is 4. You can specify a value from 1 to 16. The value you specify here will apply to n in program-installationdestination-drive:\Program Files\HITACHI\HNTRLib2\spool \Hntr2n.log (n indicates a file number). 3. In File Size(KB), change the size of an integrated trace file. The default is 256 (kilobytes). You can specify a value from 8 to 8192.
The default is 0. You can specify a value from 0 to 500. If you specify 0, you cannot adjust the number of messages to be output. If you specify 0 for Lookout Span(Sec), you cannot adjust the number of messages to be output because the system ignores the Max Messages / Span setting. 8. After you finish changing the settings, click the OK button. The dialog box closes. 9. Close all of the Hitachi program products that are using Hitachi Network Objectplaza Trace Library, or restart the host.
# To 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. • Before uninstalling HDLM 5.5 or later, make sure that no other application is using an HDLM management-target LU.
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.
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. 4. From Control Panel, choose MPIO. The MPIO Properties dialog box opens. 5. On the MPIO-ed Devices page, select Device Hardware ID DGC RAID, and then click the Delete button. 6. Click the OK button to close the MPIO Properties dialog box. 7.
¢ 9. 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. After stopping the HDLM manager, restart the uninstallation program. 10. When uninstallation finishes, a dialog box appears, prompting you to restart the host. Click the OK button to restart the host.
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. 5. From Control Panel, choose MPIO. The MPIO Properties dialog box opens. 6. On the MPIO-ed Devices page, select Device Hardware ID DGC RAID, and then click the Delete button. 7. Click the OK button to close the MPIO Properties dialog box. 8.
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. 10. Follow the instructions shown in the messages that appear in the window. Uninstall HDLM from all the hosts that make up the cluster. If the KAPL09005-E message appears, stop the HDLM manager according to the procedure in Stopping the HDLM Manager on page 4-15. After stopping the HDLM manager, restart the uninstallation program. 11.
¢ 9. 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. After stopping the HDLM manager, restart the uninstallation program. 10. After uninstallation finishes, restart the host. 11. Start the Oracle RAC instance of the host. 12.
#2 For Windows Server 2003 (excluding the x86 edition) or Windows Server 2008 (excluding the x86 edition), Program Files is Program Files (x86). Notes: ¢ ¢ ¢ a. 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 company.
¢ ¢ 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 in Uninstalling HDLM on page 3-84. You can execute this utility if the following conditions are satisfied: - HDLM has been uninstalled. - The services and drivers in the cluster system are not running.
3-92 Creating an HDLM Environment Hitachi Dynamic Link Manager User Guide (for Windows(R))
4 HDLM Operation This chapter describes the operating procedures for HDLM, including how to operate HDLM and the HDLM manager, and how to change the configuration of the operating environment.
Notes on Using HDLM This section contains notes that are important for running HDLM operations. Using a Storage Management Program You must not change the vendor ID and product ID of a storage system. If you change these IDs, HDLM will not be able to recognize the storage system. Upgrading Windows Always uninstall HDLM before upgrading Windows, re-installing Windows during a system recovery, or installing a Windows SP.
• 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. For details about the various command operations, see 6 Command Reference on page 6-1.
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. • The HDLM GUI is unavailable in the Server Core environment of Windows Server 2008. • You cannot use an HDLM GUI shortcut that was copied from a version of HDLM earlier than 5.8.
• 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. To display path information, execute the dlnkmgr command's view operation with the -path parameter specified.
To place paths online by specifying an HBA port, CHA port, single path, or HBA port WWN, check the path name or PATH_ID used to manage the path. The following example shows how to execute the command: >dlnkmgr view -path 2. To change the status of paths to online, execute the dlnkmgr command's online operation. The paths to be placed online can be specified by using an HBA port, CHA port, single path, or HBA port WWN. For details on how to specify paths, see online (Places Paths Online) on page 6-10.
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. Otherwise, enter n. [y/n]:y KAPL01061-I 3 path(s) were successfully placed Offline(C); 0 path(s) were not.
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.
Load Balance : on(extended lio) Support Cluster : off Elog Level : 3 Elog File Size(KB) : 9900 Number Of Elog Files : 2 Trace Level : 0 Trace File Size(KB) : 1000 Number Of Trace Files : 4 Path Health Checking : on(30) Auto Failback : on(1) Remove LU : on Intermittent Error Monitor : off KAPL01001-I The HDLM command completed normally.
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 KAPL01001-I The HDLM command completed normally.
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. > Viewing HDLM Version Information This section explains how to display HDLM version 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.
¢ 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: 1. Click Start, Settings, and then Control Panel. Double click Administrative Tools., and then double click Performance. The Performance window appears. 2. Right-click the window showing the system monitor details, and then choose Add Counters. The Add Counters window appears. 3.
Selectable items# pathid disk-number drive-letter Description 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. • disk-number Displays the disk number of disks displayed in the Disk Management window of Windows.
>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.
Process hntr2mon.exe hntr2srv.exe Service Hitachi Network Objectplaza Trace Monitor 2 Description Hitachi Network Objectplaza Trace Library (HNTRLib2) process # 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.
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. Figure 4-1 Using the command to confirm that an LU has been added 5. For the new LU, write a signature, create partitions, and then format it. Note: The PathID is determined by the system choosing the smallest, available number that is not already in use for another 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. You can confirm that a path has been added by using the HDLM command view operation, or the HDLM GUI. Figure 4-2 Using the command to confirm that a path has been added on page 4-18 shows an example of using the command to confirm that a path has been added.
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. For details on the set operation, see Setting Up the HDLM Functions on page 3-70. For details on the Options window, see the HDLM GUI Help.
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.
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 PathID An AutoPATH_ID. Host port number Elements of a PathName.
4-22 HDLM Operation Hitachi Dynamic Link Manager User Guide (for Windows(R))
5 Troubleshooting This chapter describes how to properly use HDLM error information, and then how to resolve the problem, if an error occurs in HDLM. The resolutions for path errors, HDLM program errors, and other types of errors are all described separately. This chapter describes how to use the HDLM commands to use HDLM error information and utilize various workarounds. For details about how to use the HDLM GUI, see the Hitachi Dynamic Link Manager Software GUI Help.
Information Collected by the DLMgetras Utility for Collecting HDLM Error Information Immediately after an error occurs, execute the DLMgetras utility for collecting HDLM error information, since restarting the machine might delete error information before the information is collected by DLMgetras. For details about the DLMgetras utility and the error information it collects, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2.
output to the event log. If this happens, refer to the KAPL05301-E message to check the path information. The message elements are explained below: For details about the KAPL05301-E message, see When an LU or path is automatically deleted due to all the paths being disconnected in Checking that the LU or Path Has Been Dynamically Deleted on page 4-19 in Deleting an LU Dynamically on page 4-19. ErrorCode The error number generated when Windows detects a path error.
The name of the host device. A drive letter is used. If no drive letter has been assigned, a hyphen (-) will be displayed. This is the same as the HDevName that is displayed by the view operation. For details on the view operation, see view (Displays Information) on page 6-29. What To Do for a Path Error When a path error is detected by HDLM, you must immediately resolve the error and restore the path.
Figure 5-2 Troubleshooting Procedure When a Path Error Occurs The following shows the procedure for using the HDLM command (dlnkmgr) to handle a path error. Examining the Messages Examine the messages that are output to the host event log. If the KAPL08022-E message is output, view the message to check the path in which the error has occurred. For details on each item displayed in messages, see Checking Error Information in Messages on page 5-2.
Identifying the Error Path Check the obtained path information to find the path with the error. In the Status column, the error path has the status Offline(E) or Online(E). Narrowing Down the Hardware That Might Have Caused the Error Check the DskName, iLU, ChaPort, and HBAPortWWN columns of the path with the error to narrow down the hardware that may be the cause of the error.
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). Examining the Messages Examine the messages that are output to the host event log.
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.
6 Command Reference This chapter describes the HDLM command (dlnkmgr) and its operations.
Overview of the HDLM Command dlnkmgr This section describes how to specify the HDLM command dlnkmgr and its subcommands (called operations in HDLM). Command format Enter the command using the following format: dlnkmgr operation [parameter [parameter-value]] dlnkmgr The command name. operation The type of operation entered after dlnkmgr. parameter A value required for an operation. parameter-value A value required for an operation parameter.
If you are 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.
> 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 > help (Displays the Operation Format) The dlnkmgr command's help operation displays the list of operations available for the HDLM command, or the format of individual operations. Format dlnkmgr help [operation] [operation] ...
>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. >dlnkmgr help online offline help online: Format dlnkmgr online [-path] [-s] dlnkmgr online [-path] -hba HBAPortNumber.
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. Before placing a path offline, use the view operation to check how many online paths remain.
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. Leading zeros of each parameter value can be omitted; however, when the host port number or bus number of the target HBA port is 0000, enter 0000 or 0 for the corresponding parameter value.
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. Specify the current AutoPATH_ID of the target path, which is displayed by using the view operation. For details about the view operation, see view (Displays Information) on page 6-29.
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 -s Executes the command without displaying the message asking for confirmation of command execution from the user. Specify this parameter if you want to skip the response to the confirmation message: for example, when you want to execute the command in a shell script or batch file.
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: >dlnkmgr view -path | find "0004.
|-hbaportwwn HBA-port-WWN [-tid target-ID -hlun host-LUnumber]] [-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. Specify the paths to be taken online by using the -hba, -cha, -pathid, or -hbaportwwn parameter.
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.
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).
online: Format dlnkmgr dlnkmgr dlnkmgr dlnkmgr dlnkmgr online online online online online [-path] [-s] [-path] -hba HBAPortNumber.BusNumber [-s] [-path] -cha -pathid AutoPATH_ID [-s] [-path] [-pathid AutoPATH_ID] [-s] [-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.
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.
Item name Default value Recommended value The Extended Least I/Os algorithm is used. The recommended algorithm depends on the operating environment. Error log collection level 3 3 Collect error information for the Information level and higher. Collect error information for the Information level and higher. Error log file size 9900 (KB) 9900 (KB) Number of error log files 2 2 Trace level 0 0 Do not output any trace. Do not output any trace.
-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.
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. The target log files for which a file size can be set are HDLM manager logs (dlmmgrn.log (n indicates a file number from 1 to 16)) and HDLM GUI logs (dlmguin.log (n indicates a file number of 1 or 2)).
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. When combined with the specification for the number of trace files, the maximum size of the trace files that can be collected is 1024000KB.
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.
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.
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.
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. -iemnum number-of-times-error-is-to-occur Specify the number of times the error is to occur.
Table 6-5 Relationship Between the Setting for the Automatic Failback Function and Intermittent Error Monitoring and the Executable Operations Setting AFB on IEM on Available 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.#1 Set AFB to off. • AFB and IEM are disabled. • The error count, elapsed monitoring time, and information about paths not subject to automatic failback are cleared.
Setting AFB IEM off 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 #1 When this condition is not satisfied, the KAPL01080-W message is output and an error occurs. The status of intermittent error monitoring does not change. #2 Because automatic failback is off, intermittent error monitoring is disabled.
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. Temporary license key# Temporary license keys are used temporarily, for example, when a user needs to perform product evaluations.
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 4-19. Table 6-7 Values for the LU Dynamic Deletion Function on page 6-27 shows the values of the LU dynamic deletion function.
Value (severity) Explanation 1 2 3 Error-level and Warning-level audit log data is collected. 4 5 Error-level, Warning-level, and Information-level audit log data is collected. 6 7 -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. The default is all.
dlnkmgr set { exlbk } ] | | | | | | | | | | | | | | | | | -lb on [ -lbtype { rr | exrr | lio | exlio | lbk | -lb off -ellv ElogLevel -elfs ElogFileSize -elfn Number-Of-ElogFiles -systflv TraceLevel -systfs TraceFileSize -systfn Number-Of-TraceFiles -pchk on [ -intvl Interval-Time ] -pchk off -afb on [ -intvl Interval-Time ] -afb off -iem on [ -intvl Error-Monitor-Interval ] [ -iemnum Number-Of-Times ] -iem off -lic -rmlu on [ -force ] -rmlu off -audlog on [ -audlv AudlogLevel ] [ -category Category-Value ]
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] [hbaportwwn] [-hdev host-devic
[-hdev host-device-name|-pathid AutoPATH_ID] [-exlu] [-t] To display LU information (by adding items to be displayed) dlnkmgr view -lu -item [ [slpr] [pn] [cp] [clpr] [type] [ic] [ie] [dnu] [iep]|all ] [-hdev host-device-name|-pathid AutoPATH_ID] [-exlu] [-t] To display a summary of LU information dlnkmgr view -lu -c [-exlu] [-t] To display a summary of LU information (by adding items to be displayed) dlnkmgr view -lu -c -item [slpr] [-exlu] [-t] To Display the Format of the view Operation dlnkmgr view
Use one of the sub-parameters (following -sys) to specify the program information that you want to display. If you do not specify a subparameter, 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. -t Does not display the title for each information item.
Parameter and program information to be displayed Item Description • 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). Elog File Size (KB) Size of the error log file in kilobytes Number Of Elog Files Number of error log files Trace Level Trace output level: Trace File Size(KB) • 0: Does not output any trace.
Parameter and program information to be displayed Item Intermittent Error Monitor Description • Setting for intermittent error monitoring: 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.
Parameter and program information to be displayed Item Expiration Description License 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.
>dlnkmgr view -sys -sfunc HDLM Version : x.x.x-xx Service Pack Version : Load Balance : on(extended lio) Support Cluster : off Elog Level : 3 Elog File Size(KB) : 9900 Number Of Elog Files : 2 Trace Level : 0 Trace File Size(KB) : 1000 Number Of Trace Files : 4 Path Health Checking : on(30) Auto Failback : on(1) Remove LU : on Intermittent Error Monitor : off KAPL01001-I The HDLM command completed normally.
>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 : KAPL01001-I The HDLM command completed normally.
Item Description • Windows Server 2003 (IPF) SP1 or later • Windows Server 2003 (x64)#1 • Windows Server 2008#2 If the OS is Windows Server 2008, this item always displays on. #1 The EMC DMX series cannot be managed. #2 The EMC DMX series and the HP EVA series cannot be managed. -t Does not display the title for each information item. Example >dlnkmgr view -stinfo EMC Symmetrix DMX Series, CLARiiON CX Series : on HP StorageWorks EVA Series : on KAPL01001-I The HDLM command completed normally.
-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.
• 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. -hbaportwwn Displays port WWN information for the HBAs connected to the storage system. -t Omits the title for each information item.
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.
Selectable items Sub-parameters iLU lu ChaPort cp Status# None Type type IO-Count ic IO-Errors ie DNum dnu HDevName hd IEP iep # 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). If you omit both parameters, the command displays information for all the paths in ascending order of AutoPATH_IDs.
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.
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. The items that are displayed are PathID, DskName, iLU, CP, Status, and Type.
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. -srt {lu|cp} Use this parameter to sort the path information in ascending order, according to the specified sorting key.
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 No summary displayed Description Summary displayed Paths Total number of displayed paths, indicated by a decimal number.
Displayed Item No summary displayed Description Summary displayed • 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. DskName#1 DskName The storage system name, which identifies the storage system that is accessed by a path.
Displayed Item No summary displayed Description Summary 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.
Displayed Item No summary displayed Type#1 Description Summary displayed Type • 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: 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/ VM, Virtual Storage Platform, Hitachi AMS2000 series, or Hitachi SM
Displayed Item No summary displayed Description Summary 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)). • A value of at least 0 Indicates the number of errors that occurred during intermittent error monitoring (the path status is Online(E), Offline(E), or Online).
Element Windows representation Target ID (example: 0000000000000000, 000000000000007A) Target Id 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: HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi Note: When an FC connection is used, the target ID of a SCSI device is determined by the HBA configuration.
Product ID Model names of storage systems • Hitachi NSC55 • Hitachi Universal Storage Platform V • Hitachi Universal Storage Platform VM With the -stname parameter (Displays the following for the model ID) Without the -stname parameter USP_V Hitachi Virtual Storage Platform VSP P9500 P9500 HP XP128 XP128 HP XP1024 XP1024 HP XP10000 XP10000 HP XP12000 XP12000 HP XP20000 XP20000 HP XP24000 XP24000 # ¢ ¢ When a summary is displayed by specifying the -path -c parameter and there are
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 displayed for each vendor ID. For the HP EVA series, LU information is displayed for each vendor_ID_product_ID.
>dlnkmgr view Product SerialNumber LUs iLU HDevName 0000 P -lu : 9500V : 0329 : 2 PathID Status 000006 Online 000014 Online 0001 Q 000007 Online 000015 Online Product : DGC SerialNumber : LUs : 2 iLU HDevName PathID Status 6006016099C50... F 000004 Online 000008 Online 6006016099C50... G 000005 Online 000009 Online Product : EMC SerialNumber : LUs : 4 iLU HDevName PathID Status 6006048000018... L 000000 Online 000010 Online 6006048000018... M 000001 Online 000011 Online 6006048000018...
SerialNumber LUs : : 4 iLU 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.
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. The sub-parameters are: -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.
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.
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. -t Omits the title for each information item. Example When the -exlu parameter is not specified: When the -exlu parameter is specified: Parameters to display a summary of LU information by adding items to be displayed: -lu -c -item The items displayed when the -item option is added to the -lu -c options.
Table 6-17 Items That Can Be Added by Using the -lu -c -item Parameter and Sub-parameters Item that can be added SLPR Sub-parameter slpr The sub-parameter is: -exlu • When an HDLM management-target device is the EMC DMX series, EMC CX series, or HP EVA series: If this parameter is specified, all 32 digits of the iLU are displayed instead of truncating the iLU to 13 digits.
Table 6-18 Displayed LU Information Displayed item No summary displayed Description Summary displayed • Product 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: Model name of the storage system • For the EMC DMX and series, EMC CX series: Vendor ID • For the HP EVA series: Vendor-ID_Product-ID Serial Number S/N • For the Thunder 9500V series, Lightning 9900
Displayed item No summary displayed Description Summary 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.
Displayed item No summary displayed Description Summary 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 ChaPort#1 - • 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: Port number of the channel adapter, which identifies the CHA port that is mounted on the storage syste
Displayed item No summary displayed Description Summary displayed determined by referring to What To Do for a Path Error on page 5-4 Type#1 - • For the Thunder 9500V series, Lightning 9900 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 Own: Owner path Non: Non-owner path When connected to the Lightning 9900 series, Lightning 9900V series, Hitachi USP, Universal Storage Platform V/
Displayed item No summary displayed Description Summary 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. • *: Indicates that an intermittent error occurred (automatic failback does not check the path). - Paths Total number of the paths recognized by HDLM for the LU to be displayed.
Parameter Used When Displaying the Format of the view Operation -help Use this parameter to display the view operation format.
6-66 Command Reference Hitachi Dynamic Link Manager User Guide (for Windows(R))
7 Utility Reference This chapter explains the utilities used by HDLM.
Overview of the Utilities HDLM provides the following utilities: • The DLMgetras utility for collecting HDLM error information When an error occurs, this utility collects the files that contain the information that you need to submit to your HDLM vendor or maintenance company. For details about the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2.
files, definition files, and OS information. The collected information is archived in a file and saved to a folder of your choosing. Whenever the host is restarted, some of the information that is collected by the DLMgetras utility will be cleared. As a result, whenever an error occurs, immediately execute this utility to avoid losing any valuable information.
The utility obtains logs from each application, system, and security event log. The logs obtained are those output after 00:00 on the date yyyy/ mm/dd. Specify the date in the yyyy/mm/dd format. -eventlogsize {all | maximum-file-length} all Logs from all applications, systems, and security event logs are obtained. maximum-file-length The utility obtains logs from each application, system, and security event log.
Folder that stores collected files#1 Files Explanation folder-to-whichcollected-information-isoutput\HDLM-installationdestination-drive-name_ \Program Files\HITACHI \DynamicLinkManager\log#2 dlmmgrn.log HDLM manager log (including the driver log) hcmdslicense2.log Log when updating the license hdlmtrn.log Trace file hs_err_pidnnnn.log Java execution log (nnnn indicates a process ID) folder-to-whichcollected-information-isoutput\folder-to-whichWindows-is-introduced (%SystemRoot%)#3 setupact.
Folder that stores collected files#1 Files Explanation folder-to-whichcollected-information-isoutput\Volume-Managerinstallation-destinationdrive-name_\Program Files \VERITAS\Volume Manager M.
Folder that stores collected files#1 Files Explanation dlmmgr-lic.txt Result of the dlnkmgr view sys -lic command dlmmgr-lu.txt Result of the dlnkmgr view lu -item pn cp type ic ie dnu slpr clpr -exlu command dlmmgr-lu-all.txt Result of the dlnkmgr view lu -item all -exlu command dlmmgr-path.txt Result of the dlnkmgr view path -exlu command dlmmgr-path-iem.txt Result of the dlnkmgr view path -iem command dlmmgr-sys.txt System information, and driver information for each SCSI port driverquery.
Folder that stores collected files#1 Files iscsi-reg.txt Explanation iSCSI registry information Localhost_Cluster.log MSCS log #4 mpio-list.txt MPIO information mpio-reg.txt MPIO registry information path_environ.log Environment variable Path information sysdllexe.txt Version information, timestamps for PE format files, last modification dates, and file size information for executable files installed in the HDLM directory, HNTRLib2 directory, Hitachi common directory, and system directory.
#5 The value N depends on the setting in the dlmwebagent.properties file. The default value is 2. #6 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. #7 For Windows Server 2003 (excluding the x86 edition) or Windows Server 2008 (excluding the x86 edition), Program Files is Program Files (x86).
Format dlmpr {-c| -d| -h} Parameters -c 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. -d Displays a list of the paths for LUs managed by HDLM and persistent reservation information. -h Displays the format of the dlmpr utility. No parameters Displays an overview of this utility. Procedure for Executing the dlmpr Utility in MSCS Environments: 1.
6. 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. >dlmpr -c PathID PathName KeyCount ReservedKey Type 000000 0001.0000.0000000000000000.0000 1 200000E08B1059EC ExclusiveAccessRegistrantOnly 000001 0001.0000.0000000000000000.
The persistent reservation is cleared. Repeat the procedure until KeyCount for all the paths is changed to 0. 6. Restart the VCS. 7. 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. A PRSV key is required to operate HDLM functions. This utility is executed automatically during an installation of HDLM.
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. Is this OK? [y/n]: y KAPL12106-I An attempt to register the PRSV key was successful. (PRSV key = 0123456789abcdef) -s Specify this parameter to avoid displaying a confirmation message upon execution of the dlmprsvkey utility.
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.
name = view, completion time = yyyy/mm/dd hh:mm:ss -h 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. Installation information refers to the installation directory and the version. If HDLM has not been installed, no installation information is output.
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.
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 or 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 Sets the information required to perform an installation.
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 Key name Description installfile_locat ion Specify the absolute path name of the drive in which the installation DVD is inserted.
Necessity of definition Key name Description Maximu Upgrad m e charact New installat er installat ion or length# ion Re1 installat ion y: Include them as management targets. n: Do not include them as management targets. If this key is omitted ¢ ¢ storage_eva In Windows Server 2003, the two series are not included as management targets. In Windows Server 2008, the two series are included as management targets. Specify whether to include the HP EVA series as possible management targets of HDLM.
Necessity of definition Key name restart Description Maximu Upgrad m e charact New installat er installat ion or length# ion Re1 installat ion Specify whether to restart the host Optional after installation. Specify either of the following values:#2 Optional 1 y: Restart. n: Do not restart (default). In a cluster environment, do not specify y. Legend: Optional: If no key or setting value is specified, the installer uses the default value.
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. [ENVIRONMENT_SETTINGS] section This section defines HDLM operational and function information.
Necessity of definition Key name#1 Description#2 Maximu m Upgrade charact installat New er ion or installat length# Reion 3 installat ion exlio: The Extended Least I/Os algorithm (default) lbk: The Least Blocks algorithm exlbk: The Extended Least Blocks algorithm error_log_level Specify the level of the error Optional information to be collected as error log data.
Necessity of definition Key name#1 path_health_chec k_interval Description#2 Maximu m Upgrade charact installat New er ion or installat length# Reion 3 installat ion Specify, in minutes, the interval at Optional which the path health check will be performed. Optional 4 Optional 3 Optional 4 Optional Optional 3 Optional Optional 4 Optional Optional 2 Optional Optional 3 You can specify a value from 1 to 1440. The default is 30.
Necessity of definition Key name#1 Description#2 Maximu m Upgrade charact installat New er ion or installat length# Reion 3 installat ion on: Enable the LU dynamic removal function. off: Disable the LU dynamic removal function (default). remove_lu_force Using either of the following values, specify whether to remove an LU from the HDLM management target list when all paths to the LU are disconnected, even when there are Offline(C) paths:#2 Optional Optional 3 on: Remove the LU.
When on is specified for the auto_failback key in the installationinformation settings file ¢ For an upgrade installation or re-installation: When on is specified for the auto_failback key in the installationinformation settings file, or when automatic failbacks are enabled in the installation pre-settings. #5 If you want to enable intermittent error monitoring, specify this key after specifying the auto_failback and auto_failback_interval keys.
• 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. Notes: • The installhdlm.log file is not deleted when HDLM is uninstalled. If the file is no longer necessary, delete it manually.
¢ ¢ ¢ 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.
7-28 Utility Reference Hitachi Dynamic Link Manager User Guide (for Windows(R))
8 Messages This chapter describes the format and meaning of the message IDs, and also the terms used in the messages and message explanations. For details on the meaning of the return codes output by HDLM when it receives a request from Global Link Manager and measures to take for them, see Return Codes for Hitachi Command Suite Common Agent Component on page 8-105.
□ KAPL15001 to KAPL16000 □ Return Codes for Hitachi Command Suite Common Agent Component □ Events Output to Windows Event Logs by HDLM 8-2 Messages Hitachi Dynamic Link Manager User Guide (for Windows(R))
Before Viewing the List of Messages This section explains the following information that is needed to locate messages and understand the explanations in the sections from KAPL01001 to KAPL02000 on page 8-4. • Format and meaning of the message IDs • Terms used in the messages and message explanations This information is explained below. Format and Meaning of Message IDs Each message has a message ID.
KAPL01001 to KAPL02000 Message ID KAPL01001-I Message Text The HDLM command completed normally. Operation name = aa...aa, completion time = bb...bb Explanation Details The HDLM command completed successfully. aa...aa: clear, help, offline, online, set, or view bb...bb: Year/month/day hour:minute:second Action None. KAPL01002-I The HDLM command started. Operation name = aa...aa Details The HDLM command was executed. aa...aa: clear, offline, online, set, or view Action None.
Message ID Message Text Explanation aa...aa: clear, set, offline, or view Action Execute help operation-name of the HDLM command (dlnkmgr) to check the parameter. Specify the correct parameter, and then retry. For details on the help operation, see help (Displays the Operation Format) on page 6-4. KAPL01007-W A duplicate parameter is specified. Operation name = aa...aa, parameter = bb...bb Details aa...aa: clear, offline, online, set, or view bb...
Message ID Message Text Explanation then retry the HDLM command. For details on the view operation, see view (Displays Information) on page 6-29. KAPL01013-E An error occurred in internal processing of the HDLM command. Operation name = aa...aa details = bb...bb Details An error unrelated to a user operation occurred during command processing. aa...aa: clear, offline, online, set, or view bb...
Message ID Message Text Explanation operation, see view (Displays Information) on page 6-29. KAPL01016-W The target CHA port was not found. Operation name = aa...aa Details The path ID indicated by -pathid and required by the -cha parameter is not an object of HDLM management. aa...aa: offline or online Action Execute the view operation of the HDLM command (dlnkmgr view path), and then check the value displayed in ChaPort. Specify an AutoPath_ID that passes through the relevant CHA port, and then retry.
Message ID Message Text Explanation check the settings, and then retry. For details on the view operation, see view (Displays Information) on page 6-29. ¢ view operation Refer to 3 Creating an HDLM Environment on page 3-1. Creating an HDLM Environment or Reconfiguring the HDLM Operating Environment on page 4-16, and then configure any paths that exist.
Message ID Message Text Explanation bb...bb: Parameters that cannot be specified at the same time Action Execute help operation of the HDLM command (dlnkmgr) to check which parameters can be specified at the same time, and then retry. For details on the help operation, see help (Displays the Operation Format) on page 6-4. KAPL01035-W The cluster support function is active, so the load balancing function is not supported. Details The load balancing function cannot be enabled because MSCS is installed.
Message ID Message Text Explanation A value other than y and n was entered. Enter y or n. Action Enter y or n. KAPL01041-E The entered value is invalid. The Details operation stops. Operation Command processing will be name = aa...aa aborted because an incorrect value was entered three times in a row for a request. aa...aa: clear, offline, online, or set Action Check the correct value, and then re-execute the HDLM command. KAPL01044-W A duplicate parameter value is specified. Operation name = aa...
Message ID Message Text Explanation Action None. KAPL01047-W Only one offline request can be registered in a batch job. Details The offline command cannot be executed because offline processing is already being performed. Action Wait until the offline request registered in the batch job finishes, and then retry. KAPL01048-W Help information cannot be found. Operation name = aa...aa. Details The specified operation is not an operation of the HDLM command. aa...
Message ID Message Text Explanation details on the online operation, see online (Places Paths Online) on page 6-10. KAPL01051-I Because no path has been selected among the currently displayed paths, the paths in the Offline(C), Offline(E), and Online(E) statuses will be changed to the Online status. Is this OK? [y/n]: Details All the paths will be placed Online because the path selection parameter is not specified for the online operation. To place all the paths Online, enter y.
Message ID Message Text Explanation KAPL01054-W During the offline operation Details processing of the HDLM A path that cannot be set to command, a path that cannot be Offline(C) was detected during placed in the Offline(C) status multi-path offline processing. To was detected. PathID = aa...aa ignore this path and perform Would you like to continue the offline processing for the next processing of the offline path, enter y. To cancel offline operation? [y/n]: processing, enter n. aa...
Message ID Message Text to the Online status. Is this OK? [y/n]: Explanation or -cha parameter has been specified. To continue processing, enter y. To cancel processing, enter n. aa...aa: CHA port or HBA Action If you want to execute online processing for the paths that meet the specified requirements, enter y. If you want to terminate processing, enter n. KAPL01058-W The specified parameter value is Details not needed. Operation name = A parameter value was specified aa...aa, parameter = bb...
Message ID Message Text Explanation aa...aa: online, offline, set, or clear Action None. KAPL01061-I aa...aa path(s) were successfully placed bb...bb; cc...cc path(s) were not. Operation name = dd...dd Details This message indicates the number of the paths processed in an online/offline operation. aa...aa: Number of paths where the online/offline operation was successful (decimal (base-10) number) bb...bb: Online or Offline(C) cc...
Message ID KAPL01063-I Message Text The target path(s) are already aa...aa. Explanation Details 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. For details on the view operation, see view (Displays Information) on page 6-29. For details on the online operation, see online (Places Paths Online) on page 6-10.
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. KAPL01068-I Enter a license key: Details The license key will now be renewed. Enter a license key. Action None. KAPL01069-W The entered license key is invalid. Details The entered license key is invalid.
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. The system environment is invalid. Details The license information file is missing. Action Re-install HDLM. KAPL01076-I The permanent license has been Details installed.
Message ID Message Text Explanation aa...aa: Windows-installationdestination-drive-name: \hdlm_license Action Store the license key file directly under the Windows installationdestination drive. KAPL01082-E There is no installable license key in the license key file. File name = aa...aa Details There is no useable license key for HDLM in the license key file. aa...aa: Windows-installationdestination-drive-name \hdlm_license Action Make sure that the license key file is correct, and then re-execute.
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 executed at the same time as an HDLM command set -lic operation: another set -lic operation, or an update of the license for an update installation. Action Check the license by using the HDLM command's view -sys -lic operation.
Message ID Message Text KAPL01097-W All the current trace files will be deleted. Is this OK? [y/n] Explanation Details 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. To continue the operation, enter y. To cancel the operation, enter n. Action If you want to execute the operation of the HDLM command, enter y. If you want to terminate processing, enter n. KAPL01098-W The storage system (aa...aa, bb...
Message ID KAPL01102-I Message Text All the paths which pass the specified aa...aa port will be changed to the Offline(C) status. Is this OK? [y/n]: Explanation Details Multiple paths will be collectively placed Offline(C) because the hbaportwwn parameter was specified. To collectively place multiple paths Offline(C), enter y. To not collectively place them Offline(C), enter n. aa...aa: HBA Action If you want to execute the offline processing for the paths which pass the specified target, enter y.
Message ID Message Text operation is executed. Do you want to execute the operation anyway? Operation name = set [y/n]: KAPL01112-E An attempt to connect to the HDLM driver has failed. Operation name = aa...aa Explanation system, enter y. If you want to terminate processing, enter n. Details HDLM driver information must be collected to execute the given HDLM command, but the HDLM driver cannot be accessed. aa...
Message ID Message Text Explanation using the dlnkmgr set -audlog command. KAPL01117-W An error occurred during processing to read the audit log configuration file. Details An internal error occurred while reading the audit log configuration file. Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL01118-W An error occurred during processing to output the audit log configuration file.
KAPL02001 to KAPL03000 Message ID KAPL02001-I Message Text Explanation HDLM GUI has started normally. Details java.version = aa...aa aa...aa: Version Action None. KAPL02002-I HDLM GUI has terminated. Action None. KAPL02003-E KAPL02004-E You lack permission to start HDLM GUI. Action An error occurred during internal processing of HDLM GUI. HDLM GUI cannot start. Details = aa...aa Details Execute the command as a user with Administrators group permissions or as an Administrator.
Message ID Message Text Explanation Set up a path between the host and storage system, and then restart the host. KAPL02007-E The HDLM manager could not be Details connected. The aa...aa The system could not access the operation has been stopped. HDLM manager when the Option window was started up or the Set Option Information operation was executed. aa...
Message ID Message Text Explanation ¢ Refresh ¢ Clear Data Action None. KAPL02014-W No data has been input in aa...aa. Details Nothing has been entered into the input field of the Option window. aa...aa: Input item (character string) ¢ ¢ Path Health Checking Interval Auto Failback Checking Interval ¢ Error Log File Size ¢ Monitoring Interval ¢ Number of times ¢ Error Log Number of Files ¢ Trace File Size ¢ Trace Number of Files Action Data has not been input for the specified item.
Message ID Message Text Explanation The entered value for the input field of the Option window is not within the valid range. aa...aa: Input item (character string) ¢ ¢ Path Health Checking Interval Auto Failback Checking Interval ¢ Error Log File Size ¢ Monitoring Interval ¢ Number of times ¢ Error Log Number of Files ¢ Trace File Size ¢ Trace Number of Files Action See the HDLM GUI Help to specify a number within the valid range.
Message ID Message Text Explanation If you want to execute offline processing, click OK. To cancel offline processing, click Cancel. KAPL02020-I If you are sure that there would be no problem when the path is placed in the Offline(C) status, click OK. Otherwise, click Cancel. [OK/Cancel] Details This is a confirmation to check whether you really want to change the selected path(s) to the Offline(C) status. If you want to continue, click OK. If you do not want to proceed, click Cancel.
Message ID Message Text Explanation changed to Offline(C) was detected. If you want to ignore the path and continue, click OK. To cancel the operation, click Cancel. aa...aa: Path ID (decimal (base-10) number) Action If you want to continue offline processing, click OK. To cancel offline processing, click Cancel.
Message ID Message Text Explanation check the path status, and then retry. KAPL02028-W You lack write permission for the aa...aa. Details You do not have write permission for the specified CSV file. aa...aa: Output CSV file name Action Check whether you have access permission for the specified file and whether the specified file name is correct. KAPL02029-E An error occurred during internal processing of the HDLM GUI. The aa...aa operation has been stopped. Details = bb...
Message ID Message Text Explanation vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2. KAPL02032-E The aa...aa operation cannot be Details executed because the amount of There was not enough memory to memory is insufficient. use the HDLM GUI. aa...
Message ID Message Text Explanation Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2. KAPL02040-E The Offline(C) path cannot be placed Online. PathID = aa...aa Details aa...
Message ID Message Text Explanation Click Refresh to update the contents of the view operation, check the path status, and then retry. KAPL02044-W aa...aa exists already. Do you want to overwrite it? [OK/ Cancel] Details The existing file will be overwritten. To continue, click OK. Otherwise, click Cancel. aa...aa: File name Action To overwrite the existing file, click OK. Otherwise, click Cancel. KAPL02052-W The HDLM manager could not be Details connected.
Message ID Message Text Explanation For the Path IDs of any failed paths, see the operation log. Click Refresh to view any paths that were registered together as a batch job. KAPL02055-I The target path(s) are already aa...aa. Details The specified paths are already Online/Offline(C), as a result of the online/offline operation that was just executed. aa...aa: Online or Offline(C) Action Click Refresh to check the status of the path.
Message ID Message Text Explanation reconfigured, click the Refresh button. KAPL02063-W The version number cannot be displayed. Details The version number could not be acquired because an attempt to read a parameter file, which starts up the HDLM GUI, failed. Action The version number cannot be displayed, but HDLM GUI operations can be executed. If you want to display the version number, reinstall HDLM.
Message ID Message Text Explanation contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. KAPL02077-W An attempt to acquire the Details Service Pack version information aa...aa: Code showing the reason failed. Details = aa...aa for the error Action Re-execute the command.
Message ID Message Text Explanation HDLM error information, and then contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. KAPL02087-I "Configuration View" is not supported for this storage system model. Please use the "Path List View" instead. Storage = aa...aa Details "Configuration View" cannot be displayed for the selected storage system because "Configuration View" cannot be displayed in the HDLM GUI. aa...
Message ID Message Text Explanation Action Refer to the contents of the warning. KAPL03003-E HDLM API Error information aa...aa Details This information is required for resolving problems. aa...aa: API trace error information Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Message ID Message Text Explanation HDLM Error Information on page 7-2. KAPL03007-E An error occurred during communication with the HDLM manager. (aa...aa) Details This information is required for resolving problems. aa...aa: API trace error information Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
KAPL04001 to KAPL05000 Message ID KAPL04001-I Message Text HDLM manager started. Explanation Action None. KAPL04002-E Could not start the HDLM manager. Details The HDLM manager failed to start because the current environment is unsuitable for the HDLM manager to run in. Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Message ID KAPL04006-E Message Text Cannot register the service control handler function. Return value = aa...aa Explanation Details HDLM manager could not start normally because it was unable to register the service control handler function. aa...aa: OS error code Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL04007-E Cannot register the service status. Return value = aa...
Message ID Message Text Explanation If the same error occurs, re-install HDLM. For details on the view operation, see view (Displays Information) on page 6-29. For details on the set operation, see set (Sets Up the Operating Environment) on page 6-15. KAPL04010-E Could not open the error log file. Details HDLM manager could not start normally because it was unable to open the error log file.
Message ID Message Text Explanation Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2. KAPL04014-E Output is impossible via the communication pipe. RC = aa...aa Details Data could not be written to the pipe file while communicating with an HDLM command. aa...
Message ID Message Text Explanation None. KAPL04022-W HDLM manager warning information - aa...aa Details This information is required for resolving problems. aa...aa: HDLM manager trace warning information Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2.
Message ID KAPL04025-C Message Text A memory shortage occurred in the HDLM manager. Explanation Details There was not enough memory to run the HDLM manager processes. Action To increase the amount of free memory, terminate unnecessary applications or restart the host. KAPL04026-I The temporary license is valid. The license expires in aa...aa days on (bb...bb). Details aa...aa: Number of days remaining bb...
Message ID Message Text Explanation remaining values, the default values will be used. Action For any non-default options, use the dlnkmgr set operation to set the options again. For details on the set operation, see set (Sets Up the Operating Environment) on page 6-15. KAPL04034-E An attempt to create the option definition file has failed. Details An attempt to re-create an option definition file using the default values has failed.
Message ID Message Text bb...bb, Port Number= cc...cc, Community = dd...dd, Trap Data = ee..ee Explanation bb...bb: Destination IP address of the trap cc...cc: Destination port number of the trap dd...dd: Community name given to the trap ee...ee: Transmission data Action None. KAPL05001 to KAPL06000 Message ID KAPL05001-I Message Text DriverEntry() started. 0 Explanation Details The initialization function was executed. Action None. KAPL05002-I DriverEntry() completed normally.
Message ID Message Text component) was initialized successfully. Explanation The HDLM driver (filter component) was successfully initialized for each device object. aa...aa: Device object address (hexadecimal number) Action None. KAPL05008-E Could not allocate memory. (aa...aa:bb...bb) Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company. Refer to the HDLM User's Guide for instructions how to execute the DLMgetras utility.
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 (bb...bb), Partition (cc...cc) was removed from the mounted drive. Details The device object corresponding to the disk (bb...
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 company if there is a maintenance contract for HDLM. KAPL05034-I Disk(aa...
Message ID KAPL05819-I Message Text Data for maintenance: aa...aa bb...bb cc...cc dd...dd. Explanation Details 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) Action None.
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 balancing function in a cluster configuration is connected. Details The host is connected to an LU of a storage system that cannot use persistent reservations. In a cluster configuration, the load balancing function cannot be used for an LU of a storage system that cannot use persistent reservations.
KAPL08001 to KAPL09000 Message ID KAPL08019-E Message Text The path (aa...aa) detected an error (bb...bb). (cc...cc) Explanation Details An error occurred in the path. The error is most likely due to a disconnected cable. aa...aa: Path identifier (hexadecimal number) bb...bb: Error code (hexadecimal number) ¢ When the Windows plug-andplay functionality deletes the SCSI device from Windows 0x00000000 is displayed.
Message ID Message Text Explanation cc...cc: Host port number (same as PathName of view -path) (hexadecimal number) dd...dd: Bus number (same as PathName of view -path) (hexadecimal number) ee...ee: Target ID (same as PathName of view -path) (hexadecimal number) ff...ff: HLU number (same as PathName of view -path) (hexadecimal number) gg...gg: Dev number (same as DNum of view -path) (decimal (base-10) number) hh...hh: Host device name (same as HDevName of view -path) Action The path might be damaged.
Message ID Message Text Explanation The auto recover function recovered a path. This message is output if an error occurs in all the paths to an LU and one of the paths is recovered. aa...aa: Path ID(same as PathID of view -path) (decimal (base-10) number) Action None. KAPL08026-E An error occurred on all the paths of the LU. PathID = aa...aa Details An error occurred in the last, remaining path of an LU. (This is most likely as a result of a disconnection.) aa...
KAPL09001 to KAPL10000 Message ID KAPL09001-E Message Text Explanation 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 reuninstall Action Re-install or re-uninstall HDLM as a user who is a member of the Administrators group. KAPL09002-E KAPL09003-E The disk does not have sufficient free space.
Message ID KAPL09006-E Message Text Could not install HDLM. Explanation 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 installed. Do you want to overwrite it? Details Confirm whether you want to overwrite the existing installation. aa...aa: Version number (character string) Action Choose OK to overwrite the older version of HDLM with a newer version.
Message ID KAPL09020-E Message Text Explanation Objectplaza Trace Library 2 failed. Uninstall Hitachi Network Objectplaza Trace Library 2 by referring to HDLM User's Guide section "Uninstalling Hitachi Network Objectplaza Trace Library (HNTRLib2)". An attempt to cancel the registration of the PP name of HNTRLib2 has failed. An attempt to uninstall Hitachi Network Objectplaza Trace Library 2 failed.
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 is read-only. Specify a different folder. Details Since the install folder you specified is read-only, you cannot install. Action Specify an installation folder that is not read-only. KAPL09076-I KAPL09077-I The permanent license was installed. Action The temporary license was installed. The license expires on aa...aa.
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 be installed. Details An emergency license cannot be updated with another emergency license. Action Install a permanent license. KAPL09086-W The entered license key is invalid. KAPL09087-E Action Enter a valid license key.
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 OK? Details aa...aa: SP version that will be installed. Action To execute the installation, select OK. To cancel the installation, select Cancel. KAPL09114-I There is no license key file. File name = aa...aa Details There is no license key file in the designated directory. aa...
Message ID Message Text KAPL09119-W There is no installable license key in the license key file. File name = aa...aa Explanation Details There is no HDLM-installable license key in the license key file. aa...aa: Windows-installationdestination-drive-name \hdlm_license or the-filethat-the-user-specified Action Make sure that the correct license key file has been specified, and then re-execute the installation program. KAPL09127-W The MPIO driver has already been installed in this system. Driver aa...
Message ID Message Text Explanation An invalid PRSV key has been entered. Action Enter a valid PRSV key. KAPL09129-E The version upgrade from aa...aa to bb...bb cannot be executed. Details If a version earlier than HDLM 5.5 has already been installed, version HDLM 5.5 or later cannot be installed. aa...aa: Installed version of HDLM bb...bb: Version of HDLM to be installed Action Refer to the manual Upgrade Installation or Re-installation of HDLM on page 3-63.
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 Windows Server 2008 (x86) (213 bytes including the added ";") ¢ ¢ ¢ ¢ ¢ C:\Program Files\HDVM \HBaseAgent\bin C:\Program Files\HDVM \HBaseAgent\util\bin C:\Pro
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.
Message ID Message Text KAPL09173-W HDLM version aa...aa is installed. Do you want to overwrite it with version bb...bb? Explanation Details aa...aa: Installed version number of HDLM (character string) bb...bb: Version number of HDLM to be installed (character string) Action Click the OK button to upgrade or re-install HDLM. KAPL09179-I Data for maintenance: aa...aa bb...bb Details aa...aa: Message output location information (decimal (base-10) number) bb...
Message ID KAPL09183-I Message Text HDLM version aa...aa is installed. This version will now be overwritten with version bb...bb. Explanation Details aa...aa: Installed version number of HDLM bb...bb: Version number of HDLM you attempted to install Action None. KAPL09184-I The PRSV key was registered. (PRSV key = aa...aa) Details aa...aa: PRSV key (16-digits hexadecimal number) Action None. KAPL09185-I Restart the computer.
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.
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. For details on the uninstallhdlm utility, see The uninstallhdlm Utility for Uninstalling HDLM on page 7-26. KAPL09190-W The installation information settings file is not specified.
Message ID Message Text KAPL09193-W A definition in the installation information settings file is invalid. (aa...aa = bb...bb) Explanation Details An invalid value has been 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 file, and then try again. KAPL09194-W A folder or file specified in the installation information settings file does not exist. (aa...aa = bb...
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. KAPL09198-E An error occurred in I/O of the installation information settings file. Code = aa...aa bb...
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. KAPL09216-E An error occurred during I/O of a file that aa...aa uses. Error Code = bb...bb cc...
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. Details (feature = aa...aa) Contact your You cannot use any features that HDLM vendor or the have not been installed. maintenance company if there is aa...
Message ID Message Text will be installed, without overwriting the MPIO driver. Explanation MPIO driver bundled with HDLM 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. KAPL09253-W y cannot be specified in the HDLM_core key when all HDLM components are installed.
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. KAPL09257-W HDLM cannot be installed on a system where MPIO aa...aa has already been installed. Delete the MPIO aa...aa setup information files (the INF files) from the system, and then continue the installation.
Message ID Message Text Explanation Action None. KAPL09260-W Errors were detected during the HDLM aa...aa installation check. See the previous messages to resolve the problems. Details Errors were detected during the HDLM installation check. aa...aa: Version of HDLM that will be installed Action See the previous warning and error messages to resolve the problems. KAPL09261-I KAPL09262-I A permanent license will be installed. Action A temporary license will be installed. The license expires on aa...
Message ID KAPL09281-I Message Text HDLM 6.3.0 or later has been installed. Only the HDLM driver will be installed, without overwriting the MPIO driver. Explanation Details The MPIO driver will not be installed because the version of the installed MPIO driver is the same as the one bundled with HDLM. Action None. If you want to re-install the MPIO driver bundled with HDLM, select the [Re-install MPIO driver] check box. KAPL09283-W A silent installation cannot be executed by using aa...
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 installed bb...bb. Details aa...aa: the version of HDLM or SP currently being installed bb...bb: the version of HDLM or SP that is already installed Action An upgrade installation or reinstallation cannot be performed on an already installed HDLM or SP.
KAPL10001 to KAPL11000 Message ID Message Text KAPL10002-W Too many parameters have been specified. Explanation Details Four or more parameters have been specified. Action Check the parameters of the DLMgetras utility for collecting HDLM error information, and then retry. For details on the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2. KAPL10003-W The first parameter has not been set to a directory. Value = aa...
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 does not exist. Line = aa...aa, Value = bb...bb Details The specified file or folder does not exist in the file for defining the where information is to be collected. aa...
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 error information completed normally. Details Error information has been collected. Action None. For details on the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2. KAPL10030-I A user terminated the utility for collecting HDLM error information.
Message ID Message Text Explanation aa...aa: Information collection file Action None. KAPL10034-E The file could not be copied. Filename = aa...aa, Details = bb...bb Details Execution of the cp command failed. aa...aa: File name you tried to copy bb...bb: cp command output message Action An error occurred while the information collection file was being copied. The error might be a result of an unstable user environment. Check the system configuration. KAPL10041-I Collection of aa...
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. KAPL10047-W A necessary parameter value has not been specified. (parameter = aa...
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 normally. Details The dlmpr utility for canceling the HDLM persistent reserve finished normally. Action None. For details on the dlmpr utility, see The dlmpr Utility for Clearing HDLM Persistent Reservations on page 7-9. KAPL10644-W The specified parameters cannot Details be specified at the same time. aa...
Message ID Message Text Explanation HDLM Persistent Reservations on page 7-9. KAPL10651-I KAPL10652-E The user terminated the operation. Action None. 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. KAPL10653-W The entered value is invalid. Please Re-enter it [y/n]: Action KAPL10654-W The parameter (aa...aa) cannot be not specified alone.
Message ID KAPL10659-I KAPL10660-I KAPL10661-E Message Text Explanation There is no LU for which persistent reservation information exists. Action There is no LU managed by HDLM. Action None. None. The SCSI command failed. SCSI Details Code = aa...aa, Service Action aa...aa: SCSI Code (hexadecimal = bb...bb, Status Code = number) cc...cc, Error Code = dd...dd, LU bb...bb: Service Action = ee...ee (hexadecimal number) cc...cc: Status Code (hexadecimal number) dd...dd: Error code for Windows ee...
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 Reservations on page 7-9. KAPL10666-I There is no persistent reservation information for the LU of PathID = aa...aa.
KAPL11001 to KAPL12000 Message ID KAPL11901-I Message Text aa...aa has started. Explanation Details The operation has started on the host. aa...aa : Operation (character string) ¢ Get Path Information ¢ Get Option Information ¢ Set Option Information ¢ Clear Data ¢ Get HDLM Manager Status ¢ Get HDLM Driver Status ¢ Get HDLM Alert Driver Status ¢ Get SNMP Trap Information ¢ Set SNMP Trap Information ¢ Set LU Load Balance ¢ ¢ Get Path Status Log Information Get Local Time Action None.
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. KAPL11904-E aa...aa has completed abnormally. Error status = bb...bb Details The operation has completed abnormally on the host. aa...
Message ID Message Text Explanation An exception occurred during processing on the host. Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if you have a maintenance contract for HDLM. For details on the DLMgetras utility, see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2. KAPL11906-I GUI information - aa...aa Details This information is required for resolving problems. aa...
Message ID Message Text Explanation an HDLM Persistent Reservation Key on page 7-12. KAPL12102-W There are too many parameters Action Make sure that the parameters for the dlmprsvkey utility for registering an HDLM persistent reservation key are appropriate, and then try again. For details on the dlmprsvkey utility, see The dlmprsvkey Utility for Registering an HDLM Persistent Reservation Key on page 7-12. KAPL12103-W The parameter value is invalid. (value = aa...
Message ID Message Text Explanation Action Try again as a user who is a member of the Administrators group. For details on the dlmprsvkey utility, see The dlmprsvkey Utility for Registering an HDLM Persistent Reservation Key on page 7-12. KAPL12106-I An attempt to register the PRSV key was successful. (PRSV key = aa...aa) Details aa...aa: Registered PRSV key (character string) Action None. KAPL12107-W An attempt to register the PRSV key has failed. (PRSV key = aa...aa) Details aa...
Message ID KAPL12111-E Message Text Explanation The registry key for the Details registration destination does not The registry key exist. HKEY_LOCAL_MACHINE\SYSTEM \CurrentControlSet\Services \HDLMdsm\Parameters \PRSVKeyString does not exist. Action Check whether HDLM has been installed correctly. If it has, contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Message ID Message Text Explanation company if there is a maintenance contract for HDLM. For details on the dlmprsvkey utility, see The dlmprsvkey Utility for Registering an HDLM Persistent Reservation Key on page 7-12. KAPL12114-E An invalid PRSV key has been registered. Details An invalid PRSV key has been entered in the registry key HKEY_LOCAL_MACHINE\SYSTEM \CurrentControlSet\Services \HDLMdsm\Parameters \PRSVKeyString.
Message ID Message Text Explanation error occurs before the PRSV key can be acquired. aa...aa: Maintenance information 1 (hexadecimal number) bb...bb: Maintenance information 2 (hexadecimal number) cc...cc: Maintenance information 3 (hexadecimal number) dd...dd: Maintenance information 4 (hexadecimal number) Action None. KAPL12119-E Trace data for maintenance: aa...aa bb...bb cc...cc dd...dd ee...
Message ID Message Text Explanation vendor or the maintenance company if there is a maintenance contract for HDLM. If the WMI repository is corrupted, consider rebuilding the repository. KAPL12151-W A Windows Management Instrumentation service access error occurred. Details = aa...aa, bb...bb Details A Windows Management Instrumentation service access error occurred. The Windows Management Instrumentation service might not be working.
Message ID Message Text Explanation vendor or the maintenance company if there is a maintenance contract for HDLM. If the WMI repository is corrupted, consider rebuilding the repository. KAPL12401-I All LUs managed by HDLM are in Details a single path configuration. This message is displayed when the number of LUs managed by HDLM is 0. Action None. KAPL12402-W iLU (aa...aa) is in a multi-path configuration. PathID = bb...bb[,cc...cc]...
Message ID Message Text Explanation Terminate unnecessary applications to increase the amount of free memory. Alternatively, restart the host. KAPL12406-E An error occurred in internal processing of the utility for checking HDLM paths. Error code = aa...aa, details code = bb...bb Details aa...aa: Error code bb...bb: Details code Action ¢ Error code: 22 Check whether HDLM has been installed correctly.
Message ID Message Text Explanation KAPL13603-W The audit log configuration file is Details invalid. Execute the "dlnkmgr The audit log configuration file is view -sys -audlog" command invalid. and check the setting. Action Restart the HDLM manager, execute the dlnkmgr view -sys -audlog command, and then specify any desired settings by using the dlnkmgr set -audlog. KAPL13604-W An error occurred during processing to read the audit log configuration file.
Message ID Message Text KAPL13803-W The user does not have the privileges required to execute the dlmhostinfo utility for confirming HDLM installation information. Explanation Details The dlmhostinfo utility must be executed by a user with Administrator group privileges. Action Re-execute the dlmhostinfo utility as a user with Administrator group privileges. KAPL13804-W Too many parameters have been specified. Details Three or more parameters have been specified.
Message ID Message Text Explanation ¢ ¢ ¢ ¢ The installation information file already exists. A folder with the same name as the installation information file exists. The parent folder does not exist. The user does not have write permission for the parent folder. Action Make sure that the installation information file does not meet any of the above conditions.
Message ID KAPL15032-I Message Text Explanation An HDLM persistent reservation key was successfully displayed. Command Line = aa...aa Details KAPL15033-W An attempt to display an HDLM persistent reservation key has failed. Command Line = aa...aa Details KAPL15034-I Details The status that indicates whether paths are in an individual or multiple path configuration was successfully displayed. Command Line = aa...aa aa...aa: Name of the utility that the user executed aa...
Message ID KAPL15105-I Message Text Setting up the operating environment succeeded. Command Line = aa...aa Explanation Details aa...aa: Command that the user executed KAPL15106-W Setting up the operating environment failed. Command Line = aa...aa Details KAPL15107-I Details Program information was successfully displayed. Command Line = aa...aa aa...aa: Command that the user executed aa...aa: Command that the user executed KAPL15108-W An attempt to display program information has failed.
Message ID Message Text Explanation cc...cc path(s) could not be placed bb...bb. aa...aa: Number of paths that 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 place bb...bb. Details aa...aa: Number of paths that failed to be placed online or offline bb...bb: Online or Offline KAPL15401-I HDLM Manager successfully started.
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. Action Click Refresh to update the host information, check the path status, and then retry the offline operation.
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. 1022 Details Batch registration of Offline processing was performed. Action Refresh the host information, and then check the path status.
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-oftimes-error-is-to-occur-for-intermittent-error-monitoring). 1033 Details An attempt to acquire the HDLM version information failed. Action Re-execute the command.
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. Action Check the system configuration. One or more connected storage systems cannot use the load balancing function. The load balancing function does not operate on the LUs of such storage systems.
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 and Table 8-4 Events Output to the Windows System Log on page 8-111 events output by HDLM to Windows event logs.
Message ID Type Source Category Event ID User KAPL05011-E Error DLMManager None 20491 N/A KAPL07820-E Error DLMManager None 29492 N/A KAPL08019-E Error DLMManager None 32787 N/A KAPL08022-E Error DLMManager None 32790 N/A KAPL08023-I Information DLMManager None 32791 N/A KAPL08025-I Information DLMManager None 32793 N/A KAPL08026-E Error DLMManager None 32794 N/A KAPL08027-E Error DLMManager None 32795 N/A KAPL12150-W Warning PerfHdlm None 60033 N/A
8-112 Messages Hitachi Dynamic Link Manager User Guide (for Windows(R))
A Functional Differences Between Versions of HDLM This section explains the functional differences between newer and older versions of HDLM. □ Functional Differences Between Version 6.6 or Later and Versions Earlier Than 6.6 □ Functional Differences Between Version 6.2 or Later and Versions Earlier Than 6.2 □ Functional Differences Between Version 6.0.1 or Later and Versions Earlier Than 6.0.1 □ Functional Differences Between Version 6.0 or Later and Versions Earlier Than 6.
□ Differences in Default Values □ Differences in the Load Balancing Function in an MSCS Environment A-2 Functional Differences Between Versions of HDLM Hitachi Dynamic Link Manager User Guide (for Windows(R))
Functional Differences Between Version 6.6 or Later and Versions Earlier Than 6.6 • The type of the messages listed below that are output to the event log has been changed from Error to Warning in HDLM version 6.6. Also, the level of the message IDs has been changed from E to W. ¢ KAPL12150, KAPL12151, and KAPL12152 • Drive and Disk Number can be displayed in the Path List view of the HDLM GUI in HDLM version 6.6.
Functional Differences Between Version 5.9.4 or Later and Versions Earlier Than 5.9.4 • The following operations have been changed to reduce the number of responses required during an installation: ¢ ¢ ¢ • Entry of user information has been deleted. When the dlmprsvkey utility for registering an HDLM persistent reservation key is automatically executed and a PRSV key is successfully created, the PRSV key dialog box that prompts the user for a response is no longer displayed.
• An LU has been removed from being an HDLM management-target Automatic Switching of Paths That Have the Online(E), Offline(C), or Offline(E) Status In HDLM 5.5 or later, if one of the following conditions is satisfied, the status of Online(E), Offline(C), or Offline(E) paths will automatically change to Online. In HDLM 5.
Differences in the LU Dynamic Removal Function Depending on the HDLM version, the LU dynamic removal function differs as follows: • In HDLM 05-02, and 5.4 ¢ ¢ When Remove the LU even if there are Offline(C) paths is not specified or when the HDLM command dlnkmgr set -rmlu on is executed If none of the paths connected to an LU are Online or Offline(C), the LU will be removed from being an HDLM management-target.
Differences in the Drive Letters Displayed in Windows Depending on the HDLM version, the Windows' drive letters that are displayed when all paths connected to the LU have an error status differ as follows: • When the LU dynamic removal function is not used in HDLM 5.4 Drive letters are displayed for the disks that are displayed in My Computer. • When the LU dynamic removal function is used in HDLM 5.4, or 5.5 or later, or when the function is not used in HDLM 5.
MSCS environment, even if you set the load balancing function to on, it will automatically change to off.
Acronyms and abbreviations The following acronyms and abbreviations might be used in this guide.
CSV Comma Separated Value CU Control Unit D DBMS Database Management System DEP Data Execution Prevention Dev Device DNS Domain Name Server F FC Fibre Channel FC-SP Fibre Channel Security Protocol FO Failover FQDN Fully Qualified Domain Name G GMT Greenwich Mean Time GPT GUID Partition Table # A B C D E F G H I J K L M N O P Q R S T Acronyms-2 Hitachi Dynamic Link Manager User Guide (for Windows(R)) U V W X Y Z
GUI Graphical User Interface GUID Globally Unique Identifier H HBA Host Bus Adapter HDev Host Device HLU Host Logical Unit HTTP Hypertext Transfer Protocol I I/O Input/Output IP Internet Protocol IPF Itanium(R) Processor Family iSCSI Internet Small Computer System Interface L LAN Local Area Network LDAP Lightweight Directory Access Protocol # A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Acronyms-3 Hitachi Dynamic Link Manager User Guide (for Windows(R))
LDEV Logical Device LU Logical Unit LUN Logical Unit Number M MPIO Multipath I/O MVS Multiple Virtual Storage N NIC Network Interface Card NTP Network Time Protocol O OS Operating System P P Port PRSV Persistent Reserve # A B C D E F G H I J K L M N O P Q R S T Acronyms-4 Hitachi Dynamic Link Manager User Guide (for Windows(R)) U V W X Y Z
Q QFE Quick Fix Engineering R RADIUS Remote Authentication Dial in User Service S SAN Storage Area Network SCSI Small Computer System Interface SLPR Storage Logical Partition SMTP Simple Mail Transfer Protocol SNMP Simple Network Management Protocol SP Service Pack SSL Secure Sockets Layer SVP Service Processor W WMI Windows Management Instrumentation # A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Acronyms-5 Hitachi Dynamic Link Manager User Guide (for Windows(R))
WWN World Wide Name # A B C D E F G H I J K L M N O P Q R S T Acronyms-6 Hitachi Dynamic Link Manager User Guide (for Windows(R)) U V W X Y Z
Glossary This glossary explains the terms used in this manual. A automatic failback A function for checking the status of paths at regular intervals, and automatically placing the status of a path recovered from an error into the Online status. If a path with an Offline(E) or Online(E) status recovers from an error, an automatic failback will place the path Online.
cluster A system of connecting multiple hosts with the same OS or platform (essentially, an environment in which the same application can run) and treating them as one system. D Dev A logical division of an LU that HDLM controls and operates. A Dev is equivalent to a partition in Windows. In Windows, each LU has only one Dev. Each Dev has a Dev number. (See also: Dev number) Dev number A Dev number (the DNum column) in the configuration list in HDLM. 0 is displayed as the number indicating the entire LU.
FC-SAN (Fibre Channel - Storage Area Network) A SAN using Fibre Channel. H 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. HDLM alert driver A program that receives information about an error detected by the HDLM driver, and then reports the error information to the HDLM manager.
I intermittent error An error that occurs irregularly due to, for example, a loose cable connection. IP-SAN (Internet Protocol - Storage Area Network) A data transfer network that connects hosts and storage systems by using the iSCSI standard. L LDEV (Logical Device) A combination of the storage system's product name, serial number, and an internal LU. HDLM uses this value to identify a particular LU.
non-owner path A path that passes through a non-owner controller. Non-owner paths exist only in the Thunder 9500V series, or Hitachi AMS/WMS series. (See also: owner path, non-owner controller) O owner controller A controller that has been set as an owner controller for an LU. Owner controllers are only in the Thunder 9500V series, or Hitachi AMS/WMS series. A controller other than an owner controller is called a non-owner controller.
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.
Index A B command format 6-2 overview 6-2 command device 2-3, 6-52 command of HDLM (dlnkmgr) clear 6-3 help 6-4 offline 6-6 online 6-10 set 6-15 view 6-29 configuration of an HDLM system core logic component 2-10 Critical 2-34 buffer size 3-79 bus number 6-50 D active host 2-44 audit log categories and audit events that HDLM can output 2-37 collecting data 2-35 data format 2-42 automatic failback 2-18, 6-20, Glossary-1 automatic failover 2-17 automatic path switching 2-17 AutoPATH_ID 2-3, 2-5, Glossary
dlmhostinfo 7-15 dlmpr 7-9 dlmprsvkey 7-12 dlnkmgr 6-1 DNum 5-3 driver level HDLM and MPIO drivers 2-10 dynamic reconfiguration Glossary-2 E EMC CX series cluster software 3-7 EMC DMX series cluster software 3-7 dlnkmgr view -lu -c 6-58 EMC DMX series and CX series dlnkmgr view -lu 6-53 dlnkmgr view -path -c 6-45 EMC DMX series, CX series, and HP EVA series available SAN environment 2-3 notes 4-2 EMC DMX series, EMC CX series, or HP EVA series -exlu parameter 6-39 emulation type Glossary-2 Error 2-34 error
features 1-3 functions 2-1 installing 3-24 new installation (on Windows Server 2003) 3-28 new installation (on Windows Server 2008) 3-51 notes on versions 3-14 overview 1-1 program information 6-31 setup 3-68 uninstalling 3-82 HDLM alert driver 2-10, Glossary-3 HDLM command 2-10 HDLM Core components 2-10 HDLM driver 2-10, Glossary-3 driver level 2-10 HDLM environment creating 3-1 HDLM GUI 2-9 HDLM installation types 3-13 HDLM installation type migration of HDLM 3-13 new installation of HDLM 3-13 re-installa
LU configuration recognized by the host LUN 6-51 2-8 M manual path switching 2-19 message examining 5-7 message element DNum 5-3 ErrorCode 5-3 PathID 5-3 PathName 5-3 message explanation 8-3 message ID format and meaning 8-3 Message level 8-3 Messages 8-1, 8-3 migrating from HDLM 5.4 or earlier to HDLM 5.
path switching automatically 2-17 manually 2-19 PathID 5-3 PathName 5-3 paths to which load balancing is applied 2-13 Performance 4-12 Performance Monitor 4-12 Performing Failovers and Failbacks Using Path starting HDLM manager 4-14 statistics 6-3 clearing to the initial value stopping HDLM manager 4-15 storage systems 1-2 notes 3-14 syntax conventions xiv Switching 2-16 persistent reservation Glossary-6 clearing 3-90 placing a path or paths offline 6-6 placing a path or paths online 6-10 Placing the Path
V VCS 3-7, 3-8, 3-9, 3-86 vendor ID 6-47 view 6-29 viewing GUI Help 4-4 W Warning 2-34 what is HDLM? 1-2 what to do for program error 5-7 Windows notes on 3-16 Index-6 Hitachi Dynamic Link Manager User Guide (for Windows(R))
Hitachi Dynamic Link Manager User Guide (for Windows(R))
Hitachi Data Systems Corporate Headquarters 750 Central Expressway Santa Clara, California 95050-2627 U.S.A. Phone: 1 408 970 1000 www.hds.com info@hds.com Asia Pacific and Americas 750 Central Expressway Santa Clara, California 95050-2627 U.S.A. Phone: 1 408 970 1000 info@hds.com Europe Headquarters Sefton Park Stoke Poges Buckinghamshire SL2 4HD United Kingdom Phone: + 44 (0)1753 618000 info.eu@hds.
