Hitachi Command Suite Dynamic Link Manager (for Windows®) User Guide Document Organization Product Version Getting Help Contents MK-92DLM129-29
© 2014 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd. Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use.
Contents Preface.................................................................................................. xi Intended audience....................................................................................................xii Product version........................................................................................................ xii Release notes...........................................................................................................xii Document revision level.
Automatic Failovers............................................................................... 2-17 Automatic Failbacks............................................................................... 2-19 Manual Path Switching.................................................................................... 2-19 Path Status Transition..................................................................................... 2-20 The Online Path Statuses........................................................
Disk Requirements.................................................................................3-13 Number of LUs and Paths That Are Supported in HDLM..................................... 3-14 Flow for Creating an HDLM Environment.................................................................3-14 HDLM Installation Types........................................................................................3-14 Notes on Creating an HDLM Environment........................................................
Notes on Removing HDLM............................................................................... 3-84 Removing HDLM............................................................................................. 3-86 Removal Procedures - in a Non-Cluster Environment................................ 3-86 Removal Procedures - MSCS or VCS Environment.................................... 3-88 Removal Procedures - Oracle RAC Environment.......................................
5 Troubleshooting....................................................................................5-1 Information Collected by the DLMgetras Utility for Collecting HDLM Error Information. 5-2 Checking Error Information in Messages................................................................... 5-2 What To Do for a Path Error.................................................................................... 5-4 Examining the Messages....................................................................
To Display Program Information............................................................. 6-33 To Display HDLM Management-target Device Information........................ 6-33 To Display Path Information...................................................................6-33 To Display LU Information......................................................................6-34 To Display the Format of the view Operation........................................... 6-34 Parameters................................
8 Messages............................................................................................. 8-1 Before Viewing the List of Messages.........................................................................8-3 Format and Meaning of Message IDs................................................................. 8-3 Terms Used in Messages and Message Explanations............................................8-3 KAPL01001 to KAPL02000.......................................................................
x Hitachi Dynamic Link Manager (for Windows®) User Guide
Preface This document describes how to use the Hitachi Dynamic Link Manager.
Intended audience This document is intended for storage administrators who use Hitachi Dynamic Link Manager (HDLM) to operate and manage storage systems, and assumes that readers have: • Knowledge of Windows and its management functionality • Knowledge of Storage system management functionality • Knowledge of Cluster software functionality • Knowledge of Volume management software functionality Product version This document revision applies to HDLM for Windows version 8.0.0 or later.
Document organization The following table provides an overview of the contents and organization of this document. Click the chapter title in the left column to go to that chapter. The first page of each chapter provides links to the sections in that chapter. Chapter/Appendix Description Chapter 1, Overview of HDLM on Describes an overview of HDLM, and its features. page 1-1 Chapter 2, HDLM Functions on page 2-1 Describes the system configuration of HDLM, and the basic terms and functions for HDLM.
• Hitachi USP Series User's Guide • Hitachi Workgroup Modular Storage Series User's Guide • Thunder9580V Series Disk Array Subsystem User's Guide • Reference Manual / File Conversion Utility & File Access Library • Universal Storage Platform V User's Guide • Universal Storage Platform VM User's Guide • Virtual Storage Platform User's Guide Document conventions This document uses the following typographic conventions: Convention Description Bold Indicates text on a window, other than the win
Physical capacity unit Value 1 kilobyte (KB) 1,000 (103) bytes 1 megabyte (MB) 1,000 KB or 1,0002 bytes 1 gigabyte (GB) 1,000 MB or 1,0003 bytes 1 terabyte (TB) 1,000 GB or 1,0004 bytes 1 petabyte (PB) 1,000 TB or 1,0005 bytes 1 exabyte (EB) 1,000 PB or 1,0006 bytes Logical storage capacity values (for example, logical device capacity) are calculated based on the following values: Logical capacity unit Value 1 block 512 bytes 1 KB 1,024 (210) bytes 1 MB 1,024 KB or 1,0242 bytes 1 GB 1
our existing Support Portal and support services by providing an area where you can get answers to non-critical issues and questions. Join the conversation today! Go to community.hds.com, register, and complete your profile. Comments Please send us your comments on this document: doc.comments@hds.com. Include the document title and number, including the revision level (for example, -07), and refer to specific sections and paragraphs whenever possible.
1 Overview of HDLM HDLM is a software package that manages paths between a host and a storage system. HDLM is designed to distribute loads across multiple paths and will switch a given load to another path if there is a failure in the path that is currently being used, thus improving system reliability. This chapter gives an overview of HDLM and describes its features.
What is HDLM? With the widespread use of data warehousing and increasing use of multimedia data, the need for high-speed processing of large volumes of data on networks has rapidly grown. To satisfy this need, networks dedicated to the transfer of data, such as SANs, are now being used to provide access to storage systems. HDLM manages the access paths to these storage systems.
The ability to continue running operations between a host and storage system, even if there is a failure. This is also known as performing a failover. When a host is connected to a storage system via multiple paths, HDLM can automatically switch to another path if there is some sort of failure in the path that is currently being used. This allows operations to continue between a host and a storage system.
1-4 Overview of HDLM Hitachi Dynamic Link Manager (for Windows®) User Guide
2 HDLM Functions This chapter describes the various functions that are built into HDLM. Before the function specifications are explained though, this chapter will go into detail about the HDLM management targets, system configuration, and basic terms that are necessary to know to effectively operate HDLM. After that, the rest of the chapter focuses on describing all the HDLM functions, including the main ones: load distribution across paths and path switching.
□ Collecting Audit Log Data □ Integrated HDLM management using Global Link Manager □ Cluster Support 2-2 HDLM Functions Hitachi Dynamic Link Manager (for Windows®) User Guide
Devices Managed by HDLM Below is a list of devices that can or cannot be managed by HDLM. The devices that can be managed by HDLM are called HDLM management-target devices.
HDLM assigns a unique ID to each management-target path. This ID is called AutoPATH_ID. Sometimes, the path is also just simply called a management target. The following figure shows the configuration of an HDLM system using an FCSAN. Figure 2-1 Configuration of an HDLM System When Using an FC-SAN The following table lists the HDLM system components when using an FCSAN. Table 2-1 HDLM System Components When Using an FC-SAN Components 2-4 Description HBA A host bus adapter.
System Configuration Using an IP-SAN In an IP-SAN, LAN cables are used to connect hosts to storage systems. The cable port on the host is called an iSCSI host bus adapter (iSCSI HBA) or a network interface card (NIC). In order to use an NIC, the iSCSI software 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.
Figure 2-3 Configuration of an IP-SAN System When Using iSCSI Software and an NIC The following table lists the HDLM system components when using an IP-SAN. Table 2-2 HDLM System Components When Using an IP-SAN Components Description iSCSI software The driver software that contains the iSCSI initiator function iSCSI HBA A host bus adapter that contains the iSCSI initiator function. This serves as a cable port on a host. The iSCSI HBA is referred to as the HBA in HDLM commands and the HDLM GUI.
Setting Range of the iSCSI Software and iSCSI HBA The following describes the ranges that can be used for the iSCSI software and iSCSI HBA settings. For notes on how to set these values, see the corresponding documentation for your particular iSCSI software and iSCSI HBA. • IP addresses Use the same network address for both an HBA and a CHA port connected via a common path. • Other settings ¢ An IP-SAN can be used for multiple hosts. ¢ A single HBA can connect to multiple CHA ports.
After the installation of HDLM, an LU recognized by a host is called a host LU (HLU). The areas in a host LU that correspond to the Devs in a storage system LU are called host devices (HDev). On a system using HDLM, in order to access a target LU, a drive letter is first assigned to the disk that has been integrated by the MPIO driver. Such disks are displayed in the Windows' Disk Management window. The following figure shows the LU configuration recognized by the host, after the installation of HDLM.
Program Configuration HDLM is actually a combination of several programs. Because each program corresponds to a specific HDLM operation, it is important to understand the name and purpose of each program, along with how they are all interrelated. The following figure shows the configuration of the HDLM programs. Figure 2-5 Configuration of the HDLM Programs The following table lists and describes the functions of these programs.
Program name HDLM manager Functions • Clear persistent reservations • Register persistent reservation keys • Check the configuration of the paths • Check the installation information • Perform unattended installations of HDLM • Perform unattended removals of HDLM Provides the HDLM manager, which enables you to: • Configure the operating environment • Request path health checks and automatic failbacks to be performed • Collect error log data HDLM alert driver Reports the log information
Figure 2-6 Driver Levels of the HDLM and MPIO Drivers Distributing a Load Using Load Balancing When the system contains multiple paths to a single LU, HDLM can distribute the load across the paths by using multiple paths to transfer the I/O data. This function is called load balancing, and it prevents a single, heavily loaded path from affecting the performance of the entire system. Note that some I/O operations managed by HDLM can be distributed across all, available paths, and some cannot.
Platform V/VM series, and Virtual Storage Platform series. In a non-cluster environment, the load balancing function is available for the Thunder 9500V series, Lightning 9900V series, Hitachi AMS2000/AMS/WMS/SMS series, Hitachi USP series, Universal Storage Platform V/VM series, Virtual Storage Platform series, and EMC DMX series. For details on the various cluster software that HDLM supports, see Cluster Support on page 2-46.
Figure 2-8 Flow of I/O Data When the Load Balancing Function Is Used When the load balancing function is used, I/O operations are distributed via multiple paths (A, B, C, and D). This helps to prevent problems with system performance and helps prevent bottlenecks from occurring. Paths to Which Load Balancing Is Applied This subsection describes, for each type of storage system, the paths to which the load balancing function is applied.
load balancing will be performed among the remaining, usable owner paths. It is only when absolutely no owner paths are available, that load balancing is then performed among the non-owner paths. For the example in Figure 2-9 Overview of Load Balancing on page 2-14, suppose that in the owner controller of LU0 is CHA0. When the LU is accessed, the load is balanced between the two paths A and B, which are both owner paths.
¢ VSP G1000 series ¢ Hitachi AMS2000 series# ¢ Hitachi SMS series# ¢ HUS100 series# HUS VM #: This storage system applies when the dynamic I/O path control function is disabled.
If the data is not sequential, these algorithms select the path to be used each time an I/O request is issued. ¢ ¢ ¢ Extended Round Robin The paths are simply selected in order from among all the connected paths. Extended Least I/Os The path that has the least number of I/Os being processed is selected from among all the connected paths. Extended Least Blocks The path that has the least number of I/O blocks being processed is selected from among all the connected paths.
Performing Failovers and Failbacks Using Path Switching When the system contains multiple paths to an LU and an error occurs on the path that is currently being used, HDLM can switch to another functional path, so that the system can continue operating. This is called a failover. If a path in which an error has occurred recovers from the error, HDLM can then switch back to that path. This is called a failback.
If the Thunder 9500V series, or Hitachi AMS/WMS series is being used, HDLM will select the path to be used next from among the various paths that access the same LU, starting with owner paths, and then non-owner paths. For example, in Figure 2-10 Path Switching on page 2-18, the owner controller of an LU is CHA0, and access to the LU is made via only one path (A). After that access path (A) is placed offline, the first choice for the switching destination is the other path connected to CHA0 (B).
Automatic Failbacks When a path recovers from an error, HDLM can automatically place the recovered path back online. This function is called the automatic failback function. In order to use the automatic failback function, HDLM must already be monitoring error recovery on a regular basis. When using the Thunder 9500V series, or Hitachi AMS/WMS series, HDLM will select the next path to be used first from among the online owner paths, and then from the online non-owner paths.
You can manually place a path online or offline by doing the following: • Use the HDLM GUI Path Management window. • Execute the dlnkmgr command's online or offline operation. For details on the online operation, see online (Places Paths Online) on page 6-11. For details on the offline operation, see offline (Places Paths Offline) on page 6-6. However, if there is only one online path for a particular LU, that path cannot be manually switched offline.
The Online Path Statuses The online path statuses are as follows: • Online I/Os can be issued normally. • Online(P) A state in which a path in the Online status is in the waiting-to-execute status to be taken offline. This status occurs in a cluster configuration only. The Online(P) status indicates that the user has requested an Online path to be taken offline, for a path that is connected to an LU that is currently performing reserve processing.
The paths to the primary volume (P-VOL) in the HAM environment have recovered from an error, but I/O to the P-VOL is suppressed. • Online(D)# The paths to the primary volume (P-VOL) in an HAM environment have recovered from an error, but I/O to the P-VOL is suppressed. If an error occurs in all the paths to a secondary volume (S-VOL), the status of the P-VOL paths will be automatically changed to the Online status.
Figure 2-11 Path Status Transitions Legend: Online operation: Online operation performed in the Path Management window or by executing the dlnkmgr command's online operation. Offline operation: Offline operation performed in the Path Management window or by executing the dlnkmgr command's offline operation. #1 During reserve processing for an LU, the Online status is temporarily changed to Online(P). When the reservation processing finishes, the Online(P) status is changed to Offline(C).
When the following conditions are all satisfied, a path that has been determined to have an intermittent error also becomes subject to automatic failback: ¢ ¢ ¢ All the paths connected to an LU are Online(E), Offline(E), or Offline(C). All the paths connected to an LU have been determined to have an intermittent error. The processing of continuous I/O operations issued to an LU is successful. #5 During reserve processing for an LU, the Offline(E) status is temporarily changed to Offline(P).
Online operation: Online operation performed by executing the dlnkmgr command's online operation. Offline operation: Offline operation performed by executing the dlnkmgr command's offline operation. #1 Also when an error occurs in all the paths to an S-VOL in the Online(D) status. #2 When I/O operations are processed on an S-VOL. If there is only one available online path for an LU, it cannot be placed offline by using the Path Management window or by executing the offline operation.
HDLM command or the HDLM GUI, and then make sure that the status has changed to Offline(C). If it is still Offline(E), retry the offline operation. Monitoring Intermittent Errors (Functionality When Automatic Failback Is Used) An intermittent error refers to an error that occurs irregularly because of something like a loose cable. In such a case, I/O performance might decrease while an automatic failback is being performed to repair an intermittent error.
monitoring depend on the values specified for automatic failbacks. For details on how to specify the settings, see set (Sets Up the Operating Environment) on page 6-16 or the HDLM GUI Help. Intermittent Error Monitoring Actions Intermittent error monitoring is performed on each path, and it automatically starts as soon as a path is recovered from an error by using the automatic failback function.
When an Intermittent Error Does Not Occur If an error does not occur on a path a specified number of times within a specified interval, an intermittent error will not occur. In such a case, the error monitoring will finish when the specified error-monitoring interval finishes, upon which the number of errors is reset to 0. If an error occurs on the path again at a later time, error monitoring will resume when the path is recovered from the error via an automatic failback.
since the error monitoring started are both reset to 0. As such, the error monitoring will not finish, and it will start over by using the new conditions. If the conditions are changed while error monitoring is not being performed, error monitoring will start up again and use the updated conditions after any given path is recovered from an error by performing an automatic failback.
Table 2-6 When Effects of a User Changing the Intermittent Error Information User operation Changing the intermittent error monitoring settings Turning off Number of errors and time passed since error monitoring started Information about paths not subject to automatic failback Reset Reset#1 Changing the conditions for Reset#2 an intermittent error while intermittent error monitoring is being performed Inherited Turning intermittent error monitoring on by executing the set operation, (but not chang
User operation Restarting the host Number of errors and time passed since error monitoring started Information about paths not subject to automatic failback Reset Reset #1 When you turn the intermittent error monitoring function off, information about paths not subject to automatic failback will be reset. If you do not want to reset the information about paths not subject to automatic failback when you turn the intermittent error monitoring function off, change the target paths to Offline(C).
For example, in a normal state, I/O operations are not performed on the paths coming from the standby host in the cluster configuration or on nonowner paths (that is, some of the paths that access a Thunder 9500V series, or Hitachi AMS/WMS series storage system). Because of this, for the standby host or for a host connected to non-owner paths, we recommend that you use path health checking to detect errors.
The dynamic I/O path control function can be enabled or disabled based on each host, connected storage system, or LU. The dynamic I/O path control function can be specified by using the HDLM command's set operation. For details about the set operation, see set (Sets Up the Operating Environment) on page 6-16. Dynamic Re-configuration Utilizing the Windows plug-and-play functionality, you can add or delete an LU or a path while the host (on which HDLM is installed) is still running.
Figure 2-16 Flow of Data When Collecting Error Information Logs might be collected in layers below HDLM, such as for the SCSI driver. For more details, see the Windows documentation. Types of Collected Logs HDLM collects information on detected errors and trace information and stores it into the integrated trace file, trace file, error logs and event logs. You can use the error information to examine the status of an error and analyze the cause of the error.
A system memory dump file is a file to which the system memory data is output when a Windows system is down. Specify the following procedure to output the system memory dump file. Click Control Panel, System, Startup/Shutdown, Write Debugging Information is chosen with Recovery, and then choose Kernel Memory Dump or Complete Memory Dump. The following table lists and describes the error information that can be collected in logs.
For Windows Server 2003 (excluding the x86 edition) , Windows Server 2008 (excluding the x86 edition), and Windows Server 2012 Program Files is Program Files (x86). #2 The underlined part indicates the folder specified during the installation. After obtaining these files, be sure to also copy them to a backup location. For details on error levels, see Filtering of Error Information on page 2-36. Note To collect logs, HDLM uses the Hitachi Network Objectplaza Trace Library service.
¢ ¢ ¢ Collects error information from the Warning level and higher. Collects error information from the Information level and higher (information from all the levels is collected). Collects error information from the Information level and higher (including maintenance information).
Category Explanation • 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-38 Startup and termination of software running on storage systems, software running on SVPs (service processors), and Hitachi Command Suite products Link up or link down An event indicating
Category AnomalyEvent Explanation An event indicating an abnormal state such as exceeding a threshold, including: • Exceeding a network traffic threshold • Exceeding a CPU load threshold • Reporting that the temporary audit log data saved internally is close to its maximum size limit or that the audit log files have wrapped back around to the beginning An event indicating an occurrence of abnormal communication, including: • A SYN flood attack or protocol violation for a normally used port • Acces
Category Authentication ConfigurationAccess 2-40 Explanation Audit event Severity #1 Message ID Startup of the HDLM GUI was successful. 6 KAPL15201-I Startup of the HDLM GUI failed. 4 KAPL15204-W Termination of the HDLM GUI was successful. 6 KAPL15202-I Administrator or Permission has end-user not been granted authentication to execute the HDLM command. 4 KAPL15111-W Permission has not been granted to execute HDLM utilities.
Category Explanation Audit event An attempt to display program information was successful. Severity #1 6 Message ID KAPL15107-I An attempt to 4 display program information failed. KAPL15108-W An attempt to 6 display HDLM managementtarget information was successful. KAPL15109-I An attempt to 4 display HDLM managementtarget information failed. KAPL15110-W An attempt to place a path online by using the HDLM GUI was successful.
Category Explanation Audit event Severity #1 Message ID An attempt to perform an operation by using the HDLM GUI failed. 4 KAPL15206-W Processing of the dlmprsvkey -r command was successful. 6 KAPL15030-I Processing of the dlmprsvkey -r command failed. 4 KAPL15031-W Processing of the dlmprsvkey -v command was successful. 6 KAPL15032-I Processing of the dlmprsvkey -v command failed. 4 KAPL15033-W Processing of the dlmchkpath singleconnect command was successful.
Requirements for Outputting Audit Log Data HDLM can output audit log data when all of the following conditions are satisfied: • The Event Log service is running. • The output of audit log data has been enabled by using the HDLM command's set operation. However, audit log data might still be output regardless of the above conditions if, for example, an HDLM utility is executed from external media.
¢ StartStop ¢ Authentication ¢ ConfigurationAccess ¢ All of the above For details on how to specify audit log settings, see Setting Up the HDLM Functions on page 3-72. Audit Log Data Formats The following describes the format of audit log data: The following is the format of audit log data.
Item# Explanation Audit event result Event result Subject ID for audit event result Depending on the event, an account ID, process ID, or IP address is output.
For large-scale system configurations using many hosts running HDLM, the operational load for managing paths on individual hosts increases with the size of the configuration. By linking HDLM and Global Link Manager, you can centrally manage path information for multiple instances of HDLM and reduce operational load. In addition, you can switch the operational status of paths to perform system-wide load balancing, and centrally manage the system by collecting HDLM failure information in Global Link Manager.
For details about the cluster software supported by HDLM, see Table 3-5 Supported Cluster Software on page 3-8 in Cluster Software Supported by HDLM on page 3-7. When load balancing is used by cluster software supported by HDLM, HDLM uses an active host path to access an LU.
2-48 HDLM Functions Hitachi Dynamic Link Manager (for Windows®) User Guide
3 Creating an HDLM Environment This chapter explains how to set up an HDLM environment and also how to erase environment settings. Make sure that you have already installed HDLM and configured the function settings.
HDLM System Requirements Check the following before installing HDLM: For the requirements for using HDLM in an HAM environment, see the release notes of HDLM. OSs Supported by HDLM This subsection describes the OSs, Microsoft MPIO drivers, and Web browsers supported by HDLM. Supported OSs You can install HDLM on any of the OSs described in the following table.
OS Service pack Windows Server 2012 (x64) No service pack Windows Server 2012 R2(x64) No service pack Note: In this manual, Windows running on a 32-bit processor is referred to as x86. # To use the Storport Miniport driver for the HBA driver in an environment where SP1 or later has not been installed, QFE update program QFE 838894 or later provided by Microsoft is required. Microsoft MPIO Drivers The following table lists the versions of the Microsoft MPIO driver that are bundled with HDLM.
settings required for using HDLM, see the maintenance documentation for storage systems.
OS Supported storage systems#1 • Interface Windows Windows Server Server 2003, 2008, Windows Windows Server Server 2003 R2 2008 R2 Windows Server 2012, Windows Server 2012 R2 XP24000 Lightning 9900V series • SVS • XP10000 • XP12000 Thunder 9500V series FC I/F Y Y -- iSCSI I/F Y -- -- FC I/F Y Y -- FC I/F Y Y -- Legend: Y: Usable --: Not usable FC I/F: FC Interface iSCSI I/F: iSCSI Interface #1 Dual controller configuration is required.
#6 Not supported for Windows Server 2003 (x64) or Windows Server 2003 R2 (x64). #7 Supported only for Windows Server 2008. #8 Supported only for EVA6400 storage systems running Windows Server 2008 R2 (x64). HBAs For details about the supported HBAs, see the HDLM Release Notes. When Using Intermediate Volumes Managed by Hitachi RapidXchange to Exchange Data The following table lists the related programs for when intermediate volumes managed by Hitachi RapidXchange are used to exchange data.
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 3-8 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 Thunder 9500V series, Lightning 9900V series, Hitachi USP series, Hitachi AMS2000/AMS /WMS/SMS series, Universal Storage Platform V/VM series, Virtual Storage Platform series, and HUS VM EMC DMX series EMC CX series HP EVA series Oracle RAC 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 9900V series, Hitachi USP series, Hitachi AMS2000/AMS /WMS/SMS series, Universal Storage Platform V/VM series, Virtual Storage Platform series, and HUS VM EMC DMX series EMC CX series HP EVA series MSCS Y Y Y Y VCS 4.3, 5.0 Y -- -- -- Oracle RAC 10g#1 Y -- -- -- Oracle RAC 11g#1 Y -- -- -- MSCS Y Y Y Y VCS 4.3, 5.0, 5.
OS Thunder 9500V series, Lightning 9900V series, Hitachi USP series, Hitachi AMS2000/AMS /WMS/SMS series, Universal Storage Platform V/VM series, Virtual Storage Platform series, and HUS VM EMC DMX series EMC CX series HP EVA series MSCS Y -- Y -- Oracle RAC 11g#1 Y -- -- -- MSCS Y -- Y -- VCS 5.
--: Not usable #1 For details about Oracle RAC versions, see the HDLM Release Notes. #2 The following operating systems can manage the EMC DMX series, EMC CX series, and HP EVA series: - Windows Server 2003 (x86) SP1 or later - Windows Server 2003 (IPF) SP1 or later - 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.
• Logical partitioning feature available on Hitachi Compute Blade blade servers • Windows Server 2008 Hyper-V • Windows Server 2012 Hyper-V Memory and Disk Capacity Requirements This section describes memory and disk capacity requirements. Memory Requirements The following table lists the memory requirements for a host.
q = (t x n) / 1024 MB (rounded-up to the nearest integer) Number of LUs and Paths That Are Supported in HDLM The following table lists the number of LUs and 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.
Migration of HDLM: Installing HDLM 5.5 or later after removing 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 removing that version is called a re-installation of HDLM.
Notes on HDLM Versions • If HDLM 5.4 or earlier has been installed, remove HDLM first and then proceed with a new installation of HDLM by following the procedure described in Migrating from HDLM 5.4 or Earlier to HDLM 5.5 or Later on page 3-66. • 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.
• Before installing or upgrading HDLM 5.5 or later, make sure that no other application is using an HDLM management-target LU. • When HDLM 5.5 or later is installed for the first time, the event described below will occur and is output to the event log. However, it does not affect the system or HDLM operations. Description Event provider attempted to register query "select * from WMIEvent" whose target class "WMIEvent" does not exist. The query will be ignored.
For Windows Server 2003 (excluding the x86 edition) , Windows Server 2008 (excluding the x86 edition) , or Windows Server 2012: Windows-installation-drive:\Program Files (x86)\Common Files \Hitachi Windows-installation-drive:\Program Files (x86)\HDVM\HBaseAgent \bin Windows-installation-drive:\Program Files (x86)\HDVM\HBaseAgent \util\bin HDLM-installation-folder\bin HDLM-installation-folder\lib For other versions of Windows: Windows-installation-drive:\Program Files\Common Files\Hitachi Windows-installatio
• If you install HDLM when either of the following conditions exists, an error might be displayed for the mirror disk in the Disk Management window of Windows. ¢ A mirror disk volume that uses a Windows dynamic disk exists among the HDLM management-target devices An application that uses the dmaadmin service is being executed. This error does not affect the data on the HDLM management-target devices.
Problem What to do when the DLMgetras utility for collecting HDLM error information was executed. • When installing HDLM in Windows Server 2008 or Windows Server 2012, perform the following operation before the installation to make sure applications cannot access the HDLM management-target disks. ¢ ¢ • If the disk is not used as a cluster resource: In the Windows' Disk Management windows, offline the disk. If the disk is used as a cluster resource: Stop Cluster Service.
• HDLM uses the following MPIO drivers according to the host OS: ¢ ¢ In Windows Server 2003 HDLM uses the MPIO driver on the HDLM DVD that is installed during HDLM installation. The MPIO driver consists of the following files: mpio.sys, mpspfltr.sys, mpdev.sys. In Windows Server 2008 , or Windows Server 2012 HDLM uses the MPIO driver already installed with the OS, not the MPIO driver on the HDLM installation DVD.
d. Delete the setup information files from the following folder: Windows-installation-folder\inf If there are any files whose names are the same as the setup information files but have the extension pnf, you also need to delete these files. Note that we strongly recommend that, before deleting any setup information files, you first back up the files and store the backup files in a different folder.
is different for each type of storage system. Use the following table to determine a value, and then change the current value to a value equal to or greater than the value you have determined. Table 3-12 Formula for Calculating DISKTIMEOUT Storage system type Number of paths connecte d to the voting disk • Lightning 9900V series 3 or less • Hitachi USP series You do not need to change the value of DISKTIMEOUT.
Installation of HDLM on Windows Server 2008 and Windows Server 2012 on page 3-52, the contents of the disk might become corrupted.Note that you can upgrade or re-install HDLM in a multipath configuration in Windows Server 2003 SP1 or later , in Windows Server 2008 and in Windows Server 2012. • HDLM does not support multiple-path configurations in which both an FCSAN and IP-SAN exist on the same LU.
For Windows Server 2003 (excluding the x86 edition) , Windows Server 2008 (excluding the x86 edition) or Windows Server 2012, Program Files is Program Files (x86). d. Restore the setting for Show hidden files and folders that you changed in step b. e. Rerun the HDLM installation program. • When installing HDLM on a host where a Device Manager agent 5.
Restore the disk number managed by Windows to the number that was in use prior to the migration installation or upgrade installation. For details about how to do this, contact Microsoft. Installing HDLM First, check whether HDLM has been installed on the host. When HDLM has already been installed on the host: You can upgrade HDLM by performing an update installation as described in Upgrade Installation or Re-installation of HDLM on page 3-64 or Migrating from HDLM 5.4 or Earlier to HDLM 5.
Figure 3-2 Single Path Configuration and Multi-path Configuration 2. Set up the storage system. Assign an LU to each port. To change the settings of a storage system, follow the maintenance documentation for that particular storage system. 3. Install the HBAs onto the host. Install as many HBAs as you want to use. In a cluster configuration, make sure that the manufacturer and model of the HBA is the same for all the hosts that make up the cluster.
10. Restart the host. 11. Confirm that the host is operating normally. Preparations for Installing HDLM by Performing an Unattended Installation An unattended installation allows a user to install HDLM without having to enter information into dialog boxes or specify HDLM functions. Instead, the user defines the required information for the dialog boxes in an installationinformation settings file prior to running the installation. The procedure for an unattended installation is as follows: 1.
2. Use a text editor to edit the sample file that was copied in step 1, in order to create an installation-information settings file for your particular configuration. Items that need to be defined in the installation-information settings file are described in Contents of an Installation-Information Settings File on page 7-18 below. Notes on an Unattended Installation • Do not forcibly stop the execution of the installhdlm utility during an unattended installation of HDLM.
The license key file will be deleted after the installation finishes. 3. 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. If no window is displayed, manually run the installer (setup.exe). The program checks whether HDLM has already been installed. If HDLM 5.4 or earlier has been installed, the KAPL09129-E message will appear.
6. Specify the installation folder by following the instructions shown in the messages that appear in the window. The utility for registering HDLM persistent reservation keys (dlmprsvkey) will be automatically executed. However, creation of the PRSV key might be unsuccessful if, for example, an NIC does not exist. If the PRSV key is created with time information only, or if key creation fails, a dialog box will prompt you to enter a PRSV key.
¢ In the last installation window, the following message might be output: When you manage a host by using Global Link Manager and Windows firewall is enabled on that host, execute the firewall_setup command to allow a firewall exception. If Global Link Manager will not be used to manage HDLM, you do not need to take any action. To manage HDLM with Global Link Manager, register Firewall exceptions. For details, see Firewall Settings for Managing HDLM by Using Global Link Manager on page 3-68. 11.
Unattended Installation on page 3-28 or About the Log File on page 7-27 in The installhdlm Utility for Installing HDLM on page 7-17. 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 not registered, HDLM functions might not properly operate.
21. Check the path information as described in Checking the Path Configuration on page 3-70, and make sure that you have successfully installed HDLM in a single-path configuration. 22. Connect cables to all the HBAs to change the configuration to a multi-path configuration. The following figure shows a single path configuration and a multi-path configuration. Figure 3-3 Single Path Configuration and Multi-path Configuration 23.
6. 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. If no window is displayed, manually run the installer (setup.exe). The program checks whether HDLM has already been installed. If HDLM 5.4 or earlier has been installed, the KAPL09129-E message will appear. If this happens, carry out the procedure shown in Migrating from HDLM 5.
¢ 9. If no message appears, go to the next step. Specify a license key file or enter a license key by following the instructions shown in the messages that appear in the window. ¢ If a license key file was saved in step 5, specify that license key file. ¢ If a license key file is not being used, specify the license key directly. 10. Specify the installation folder by following the instructions shown in the messages that appear in the window.
Please update the Storport Miniport driver to a Storport.sys with a file version n.n.nnnn.n or later. ¢ ¢ ¢ The PRSV key will be registered before the installation finishes. If the KAPL09131-W message appears, follow the procedure described in step 15. Although a message prompting you to restart the host appears after the installation has finished, a restart is not necessary.
An example of executing the dlnkmgr command's view operation is as follows: PROMPT>dlnkmgr view -sys 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 : off Intermittent Error Monitor : off Dynamic I/O Path Control : off(10) HDLM Manager Ver WakeupTime Alive x.x.
33. Restart each host. 34. Log on to Windows again as a member of the Administrators group. 35. Make sure that the program is working normally running properly, by examining the results of the dlnkmgr command's view operation. Make sure that on MSCS is displayed in Support Cluster. An example of executing the dlnkmgr command's view operation is as follows: PROMPT>dlnkmgr view -sys HDLM Version : x.x.
¢ If you are not performing an unattended installation, insert the DVD into the drive. In the displayed window, click the Install button next to for Windows of Hitachi Dynamic Link Manager. If no window is displayed, manually run the installer (setup.exe). The program checks whether HDLM has already been installed. If HDLM 5.4 or earlier has been installed, the KAPL09129-E message will appear. If this happens, carry out the procedure shown in Migrating from HDLM 5.4 or Earlier to HDLM 5.
The utility for registering HDLM persistent reservation keys (dlmprsvkey) will be automatically executed. However, creation of the PRSV key might be unsuccessful if, for example, an NIC does not exist. If the PRSV key is created with time information only, or if key creation fails, a dialog box will prompt you to enter the PRSV key. If this dialog box appears, go to step 9; otherwise, go to step 11. 9. Enter the PRSV key by following the instructions shown in the dialog box.
When you manage a host by using Global Link Manager and Windows firewall is enabled on that host, execute the firewall_setup command to allow a firewall exception. If Global Link Manager will not be used to manage HDLM, you do not need to take any action. To manage HDLM with Global Link Manager, register Firewall exceptions. For details, see Firewall Settings for Managing HDLM by Using Global Link Manager on page 3-68. 13. Check the results of the installation.
Load Balance : on(extended lio) Support Cluster : on MSCS Elog Level : 3 Elog File Size (KB) : 9900 Number Of Elog Files : 2 Trace Level : 0 Trace File Size(KB) : 1000 Number Of Trace Files : 4 Path Health Checking : on(30) Auto Failback : on(1) Remove LU : off Intermittent Error Monitor : off Dynamic I/O Path Control : off(10) HDLM Manager Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.
6. Save the license key file directly under the Windows installationdestination drive. Also, instead of using the license key file, you can directly specify the license key during the installation of HDLM. installation-drive:\hdlm_license The license key file will be deleted after the installation finishes. 7. Perform the installation. ¢ If you are not performing an unattended installation, insert the DVD.
9. Specify a license key file or enter a license key by following the instructions shown in the messages that appear in the window. If a license key file was saved in step 6, specify that license key file. If a license key file is not being used, specify the license key directly. 10. Specify the installation folder by following the instructions shown in the messages that appear in the window. The utility for registering HDLM persistent reservation keys (dlmprsvkey) is automatically executed.
When you manage a host by using Global Link Manager and Windows firewall is enabled on that host, execute the firewall_setup command to allow a firewall exception. If Global Link Manager will not be used to manage HDLM, you do not need to take any action. To manage HDLM with Global Link Manager, register Firewall exceptions. For details, see Firewall Settings for Managing HDLM by Using Global Link Manager on page 3-68. 15. Check the results of the installation.
Trace Level : 0 Trace File Size(KB) : 1000 Number Of Trace Files : 4 Path Health Checking : on(30) Auto Failback : on(1) Remove LU : off Intermittent Error Monitor : off Dynamic I/O Path Control : off(10) HDLM Manager Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.x-xx yyyy/mm/dd hh:mm:ss 128 HDLM Driver Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss License Type Expiration Permanent KAPL01001-I The HDLM command completed normally.
5. Save the license key file directly under the Windows installationdestination drive. Also, instead of using the license key, you can directly specify the license key during the installation of HDLM. installation-drive:\hdlm_license The license key file will be deleted after the installation finishes. 6. Perform the installation. ¢ If you are not performing an unattended installation, insert the DVD into the drive.
8. Specify a license key file or enter a license key by following the instructions shown in the messages that appear in the window. If a license key file was saved in step 5, specify that license key file. If a license key file is not being used, specify the license key directly. 9. Specify the installation folder by following the instructions shown in the messages that appear in the window. The utility for registering HDLM persistent reservation keys (dlmprsvkey) will be automatically executed.
When you manage a host by using Global Link Manager and Windows firewall is enabled on that host, execute the firewall_setup command to allow a firewall exception. If Global Link Manager will not be used to manage HDLM, you do not need to take any action. To manage HDLM with Global Link Manager, register Firewall exceptions. For details, see Firewall Settings for Managing HDLM by Using Global Link Manager on page 3-68. 14. Check the results of the installation.
Trace Level : 0 Trace File Size(KB) : 1000 Number Of Trace Files : 4 Path Health Checking : on(30) Auto Failback : on(1) Remove LU : off Intermittent Error Monitor : off Dynamic I/O Path Control : off(10) HDLM Manager Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.x-xx yyyy/mm/dd hh:mm:ss 128 HDLM Driver Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss License Type Expiration Permanent KAPL01001-I The HDLM command completed normally.
PROMPT>dlnkmgr view -sys 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 : off Intermittent Error Monitor : off Dynamic I/O Path Control : off(10) HDLM Manager Ver WakeupTime Alive x.x.
3. 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. 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-64.
¢ ¢ 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.
14. Click the OK button to close the MPIO Properties dialog box. 15. Shut down the host. Leave the host in a single-path configuration until you check (in step 23) whether HDLM has been successfully installed. 16. Modify the storage system settings. Modify the storage system settings by following the procedure described in the maintenance documentation for that particular storage system. 17. Start the host. 18. Log on to Windows again as a member of the Administrators group. 19.
HDLM Manager Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.x-xx yyyy/mm/dd hh:mm:ss 128 HDLM Driver Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss License Type Expiration Permanent KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss PROMPT> 21. Use the results of the view operation to check the version of the installed HDLM. If x.x.
Installing MSCS after an HDLM installation To install HDLM and then MSCS: 1. Shut down all the hosts. 2. Make sure that all the hosts that make up the cluster system have been fully shut down. 3. Restart each host. Restart them all in the single path configuration. 4. Log on to Windows as a member of the Administrators group. 5. Save the license key file directly under the Windows installationdestination drive.
The utility for registering HDLM persistent reservation keys (dlmprsvkey) will be automatically executed. However, creation of the PRSV key might be unsuccessful if, for example, an NIC does not exist. If the PRSV key is created with time information only, or if key creation fails, a dialog box will prompt you to register the PRSV key. If this dialog box appears, go to step 9; otherwise, go to step 10. 9. Enter the PRSV key by following the instructions shown in the dialog box.
appear if deletion of this file fails. If this happens, delete the file manually. 13. If you want to select an EMC CX series or an HP EVA series LU as the HDLM management-target device, perform the following steps to register it. Otherwise, go to step 18. 14. From Control Panel, choose MPIO. The MPIO Properties dialog box opens. 15. On the MPIO-ed Devices page, click the Add button. The Add MPIO Support dialog box opens. 16. Enter the Device hardware ID, and then click the OK button.
HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.x-xx yyyy/mm/dd hh:mm:ss 128 HDLM Driver Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss License Type Expiration Permanent KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss PROMPT> 24. Use the results of the view operation to check the version of the installed HDLM. If x.x.x-xx is displayed in HDLM Version, the correct version of HDLM has been installed. 25.
Auto Failback : on(1) Remove LU : off Intermittent Error Monitor : off Dynamic I/O Path Control : off(10) HDLM Manager Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.x-xx yyyy/mm/dd hh:mm:ss 128 HDLM Driver Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss License Type Expiration Permanent KAPL01001-I The HDLM command completed normally.
This command checks whether HDLM has already been installed. If the KAPL09183-I message will appear, the re-installation is performed. After the installation is complete, go to step 10. 6. Specify a license key file or enter the license key by following the instructions shown in the messages that appear in the window. ¢ If a license key file was saved in step 4, specify that license key file. ¢ If a license key file is not being used, specify the license key directly. 7.
HDLM-installation-folder\bin\dlmprsvkey -v Make sure that the PRSV key displayed by the dlmprsvkey utility is unique among all the other hosts in the SAN. If the PRSV key is not unique or 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, the HDLM functions might not properly operate.
HDLM Version : x.x.x-xx Service Pack Version : Load Balance : on(extended lio) Support Cluster : on MSCS Elog Level : 3 Elog File Size (KB) : 9900 Number Of Elog Files : 2 Trace Level : 0 Trace File Size(KB) : 1000 Number Of Trace Files : 4 Path Health Checking : on(30) Auto Failback : on(1) Remove LU : off Intermittent Error Monitor : off Dynamic I/O Path Control : off(10) HDLM Manager Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.
The dlmchkpath utility is executed automatically when the installation program (setup.exe) starts. The dlmchkpath utility checks whether the system is in a single-path or multi-path configuration. If a warning dialog box appears in a Windows Server 2003 environment in which no service packs are installed, return everything to a single-path configuration, and then upgrade or reinstall HDLM.
Migrating from HDLM 5.4 or Earlier to HDLM 5.5 or Later To upgrade from HDLM 5.4 or earlier: 1. Copy the following files to any location other than the HDLM installation folder. dlmmgr.xml is a file that specifies information needed to run HDLM managers. dlmwebagent.properties is a file that specifies information needed for linkage with Global Link Manager. dlmwebagent.properties only exists in HDLM 05-02 or later. If you migrate to HDLM 5.9.1 or later, you do not need to copy the dlmwebagent.
DLMAlertDriver by using the procedure below. Note, however, that leaving DLMAlertDriver on the window will not affect HDLM operations: a. From the Device Manager window, in the View menu, choose Show hidden devices. b. From the View menu, choose Devices by connection. c. Select Non-Plug and Play Drivers to display DLMAlertDriver. d. Delete DLMAlertDriver. e. Restart the system. Installing JRE HDLM starts the HDLM GUI by using JRE (JRE 1.6.
\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 When using JRE 7.0_01: jre7 For example, if the HDLM installation folder is C:\Program Files \HITACHI\DynamicLinkManager and you are using JRE 6.0_04, after copying the configuration files, the folder configuration will become the following: C:\Program Files\HITACHI\DynamicLinkManager\jre_user \jre1.6.
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 location, depending on whether the Device Manager agent is installed. • Device Manager agent is installed: program-installation-destination-drive:\Program Files#\Hitachi \HDVM\HBaseAgent\bin\firewall_setup.
In Windows, the folder in which the Hitachi Command Suite Common Agent Component commands are installed is automatically added to the environment variable Path. When you execute a command, you do not need to change the current folder to the folder that contains commands. 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.
Setting Up HDLM HDLM includes functions like the load balancing function, the automatic failback function, the error logging function, the audit logging function, etc. You can set up these functions by using the dlnkmgr command's set 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.
KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss PROMPT> Setting Up the HDLM Functions The table below summarizes the functions that can be set in HDLM. For details about each function, see Setting Up Load Balancing on page 3-73 and subsequent sections. Each function has a default value and a recommended value.
Function Collection of audit log data Default value off Recommended value The recommended value depends on the operating environment. Set on, if you want to collect audit log data. # This function is applied only when Hitachi AMS2000 series, Hitachi SMS series, or HUS100 series storage is used.
Setting Up Path Health Checking You can choose whether you want to use path health checking. • Set up path health checking by using the set operation The following is an example of how to set up path health checking by using a command: dlnkmgr set -pchk on -intvl 10 When path health checking is enabled by specifying on for the -pchk parameter, you can also specify the -intvl parameter, in order to specify the checking interval.
Setting Up Intermittent Error Monitoring Intermittent error monitoring is specifiable only when the automatic failback function is enabled. To prevent an intermittent error from reducing I/O performance, we recommend that you monitor intermittent errors when automatic failback is enabled. When intermittent error monitoring is enabled, you can specify intermittent error conditions. The default value for the intermittent error-monitoring interval is 30.
dlnkmgr set -dpc on -pathid 000001 -lu dlnkmgr set -dpcintvl 10 Specify "on" to enable the dynamic I/O path control function, or "off" to disable the function. For the -pathid parameter, specify an LU, or the ID of a path connected to the storage system. For the -dpcintvl parameter, specify the checking interval (in minutes) for reviewing the information about the switching of controllers performed by the storage system.
Setting the Error Log Collection Level There are two error logs: the HDLM manager log file dlmmgrn.log (n indicates a file number from 1 to 16) and the HDLM GUI log file dlmguin.log (n indicates a file number of 1 or 2). The table below lists and describes the values for the audit log collection level setting. Table 3-16 Values for the Error Log Collection Level Setting Value Description 0 No error logs are collected. 1 All information for errors of the "Error" level or higher is collected.
Value Description 2 Program operation summaries are output. 3 Program operation details are output. 4 All information is output. If an error occurs, you might have to set the trace level to 1 or higher to collect any trace information. The higher this value is set, the more information that will be output. As the amount of trace information to be output increases, it will take less time to overwrite the old trace information with the new information.
Setting the Number of Error Log Files There are two error logs: the HDLM manager log file dlmmgrn.log (n indicates a file number from 1 to 16) and the HDLM GUI log file dlmguin.log (n indicates a file number of 1 or 2). You can set the number of files only for the HDLM manager logs in the Options window and by the set operation. The number of HDLM GUI log files is set to 2. You can specify a value from 2 to 16 for the number of HDLM manager log files.
KAPL01097-W message will be displayed to confirm the execution, and the trace file will be temporarily deleted. By specifying both the trace file size and the number of trace files, you can collect up to 1024000KB of trace data. • Setting up the number of trace files by using the set operation The following is an example of setting up the number of trace files by using a command: dlnkmgr set -systfn 10 Specify the number of trace files by using numbers.
dlnkmgr set -audlog on -audlv 6 -category all Specify on if you want to collect audit log data, and off if you do not want to collect audit log data. If you specify on, you can use the -audlv parameter to specify the collection level for audit log data and the -category parameter to specify the audit log categories. Checking the Updated Settings This chapter describes how to check the updated settings by using the dlnkmgr command's set operation after settings have been changed.
Files#\HITACHI\HNTRLib2\spool\Hntr2n.log files (n indicates a file number)). # For Windows Server 2003 (excluding the x86 edition) , Windows Server 2008 (excluding the x86 edition), or Windows Server 2012, Program Files is Program Files (x86). If a lot of integrated trace information is output, the older information might end up getting deleted in a very short amount of time.
# For Windows Server 2003 (excluding the x86 edition), Windows Server 2008 (excluding the x86 edition), or Windows Server 2012, Program Files is Program Files (x86). The dialog box shown in Figure 3-5 Hitachi Network Objectplaza Trace Utility 2 Release 2.0 Dialog Box. on page 3-83 appears. Figure 3-5 Hitachi Network Objectplaza Trace Utility 2 Release 2.0 Dialog Box. 2. In Number of Files, change the number of integrated trace files. The default is 4. You can specify a value from 1 to 16.
The default is 0 (seconds). You can specify a value from 0 to 3600. If you specify 0, you cannot adjust the number of messages to be output because the system ignores the setting of Max Messages / Span. 7. In Max Messages / Span, enter a value to specify the maximum number of messages to be output to the integrated trace file at the monitoring interval specified in Lookout Span(Sec). The default is 0. You can specify a value from 0 to 500.
• Depending on the environment, removing HDLM might take some time. Do not terminate the removal process while a progress bar for removal is displayed. The following is an approximate calculation of the time required for an removal: (1 x number-of-connected-paths) seconds # # To remove HDLM, you must reconfigure the system to a single-path configuration. The time for doing this does not affect the time required for an removal.
the folder specified in the TMP or TEMP environment variable, if the -w parameter was not specified). Removing HDLM After HDLM is removed, sometimes the files below will not be deleted. The following files will be deleted when you restart the host: HDLM-installation-folder\DLMTools\perfhdlm\provhdlm.dll HDLM-installation-folder\lib\libdlm.dll HDLM-installation-folder\lib\hdlmhcc60.dll The default installation folder for HDLM is Windows-installation-drive: \Program Files#\HITACHI\DynamicLinkManager.
Figure 3-6 Single Path Configuration and Multi-path Configuration If you have selected an EMC CX series or an HP EVA 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 the hardware ID, and then click the Delete button. ¢ ¢ For an EMC CX series: The hardware ID is DGC RAID. For an HP EVA series: The hardware ID is HP HSV. 6.
From the Command Prompt window, execute the removehdlm utility for removing HDLM. For details about the removehdlm utility, see The removehdlm Utility for Removing HDLM on page 7-28. 8. The dlmchkpath utility is automatically executed. If a warning dialog box appears, follow the procedure below: ¢ ¢ 9. Cancel the removal. Reconfigure the system into a single-path configuration, and then perform the removal again.
Figure 3-7 Single Path Configuration and Multi-path Configuration In Windows Server 2008, if you have selected an EMC CX series or an HP EVA 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 the hardware ID, and then click the Delete button. ¢ ¢ For an EMC CX series: The hardware ID is DGC RAID.
Server Core environment: From the Command Prompt window, execute the removehdlm utility for removing HDLM. For details about the removehdlm utility, see The removehdlm Utility for Removing HDLM on page 7-28. 9. The dlmchkpath utility is automatically executed. If a warning dialog box appears, follow the procedure below: ¢ ¢ Cancel the removal. Reconfigure the system into a single-path configuration, and then perform the removal again.
¢ For an HP EVA series: The hardware ID is HP HSV. 6. Click the OK button to close the MPIO Properties dialog box. 7. Start the removal program. From Control Panel, choose Add or Remove Programs, and then Change or Remove Programs. From the list of programs, select Dynamic Link Manager, and click the Change/Remove button. 8. The dlmchkpath utility is automatically executed. If a warning dialog box appears, follow the procedure below: ¢ ¢ 9. Cancel the removal.
3. Execute the following command#1 to check if any program is using HNTRLib2: "C:\Program Files#2\HITACHI\HNTRLib2\bin\hntr2getname.exe" If the name of a program using HNTRLib2 is displayed, a program other than HDLM is using HNTRLib2. If this happens, do not delete HNTRLib2. No further steps are required. If no names of programs using HNTRLib2 are displayed, go to the next step. 4. Execute the following command#1 to remove HNTRLib2: "C:\Program Files#2\HITACHI\HNTRLib2\unsetup\unsetup.exe" 5.
c. Check that the hntr2t.dll file exists and the hntr2sys.dll and hntr2tj.dll files do not exist in the folder, and then delete the hntr2t.dll file. Clearing the Persistent Reservation If the persistent reservation remains in an LU after HDLM is removed, use the utility for clearing HDLM persistent reservations (dlmpr) to clear the persistent reservation. However, if you follow the removal procedure in this manual, the persistent reservation will not remain and will not need to be deleted manually.
3-94 Creating an HDLM Environment Hitachi Dynamic Link Manager (for Windows®) User Guide
4 HDLM Operation This chapter describes the operating procedures for HDLM, including how to operate HDLM and the HDLM manager, and how to change the configuration of the operating environment.
Notes on Using HDLM This section contains notes that are important for running HDLM operations. Using a Storage Management Program You must not change the vendor ID and product ID of a storage system. If you change these IDs, HDLM will not be able to recognize the storage system. Upgrading Windows Always remove HDLM before upgrading or re-installing Windows, or before installing a Windows Server 2003 service pack.
EMC DMX series and EMC CX series: HDLM 5.7 or later HP EVA series: HDLM 5.9.1 or later ¢ If the OS is Windows Server 2008: EMC CX series: HDLM 6.4 or later • You can display and use the HDLM GUI windows for the Thunder 9500V series, Lightning 9900V series, Hitachi USP series, Hitachi AMS2000/AMS/WMS/SMS series, Universal Storage Platform V/VM series, and Virtual Storage Platform series.
If you attempt to perform an HDLM operation by any other method, a dialog box will appear, requesting confirmation that you have administrator permissions. HDLM Operations Using the HDLM GUI This chapter explains the procedures for operating the HDLM GUI window components. For details on the components of each window, see the HDLM GUI Help. Notes on Using the HDLM GUI This subsection provides notes on using the HDLM GUI window. Be sure to read this section.
¢ Execute the HDLM command using the Administrator account. To execute an HDLM command with a non-administrator account, use the Administrator: Command Prompt window. If you attempt to execute an HDLM command by any other method, you might be asked whether you have administrator permissions. ¢ • To specify a parameter value containing one or more spaces, enclose the entire value in double quotation marks (").
Changing the Status of Paths to Online To change the status of paths to online: 1. Check the current status of the paths. To place paths online by specifying an HBA port, CHA port, single path, or HBA port WWN, check the path name or PATH_ID used to manage the path. The following example shows how to execute the command: dlnkmgr view -path 2. To change the status of paths to online, execute the dlnkmgr command's online operation.
The paths to be placed offline can be specified by using an HBA port, CHA port, single path, or HBA port WWN. For details on how to specify paths, see offline (Places Paths Offline) on page 6-6. For example, if you want to place all the paths that pass through a specific HBA port offline, execute the dlnkmgr command's offline operation with the -hba parameter specified. The following shows an example of executing this command: PROMPT>dlnkmgr offline -hba 1.
000009 Online KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss PROMPT> For details on the displayed items and their descriptions, see view (Displays Information) on page 6-33. Initializing Statistical Information for Paths This section explains how to initialize statistical information (I/O counts and I/O errors) for all the paths managed by HDLM.
The following shows an example in which the command is executed: PROMPT>dlnkmgr view -sys -sfunc HDLM Version : x.x.
• Trace file size • The number of trace files • Number of times the same path can be used for load balancing • Number of times the same path can be used for extended load balancing For details on how to set up each function, see set (Sets Up the Operating Environment) on page 6-16. For example, to set up the error log collection level, execute the dlnkmgr command's set operation with the -ellv parameter specified.
Note: When you are executing the dlnkmgr command's set operation with the lic parameter to install the license, you can only execute it once at a time. If you attempt to execute more than one dlnkmgr command containing the set operation with the -lic parameter, the following message might appear and HDLM might terminate abnormally: KAPL01075-E A fatal error occurred in HDLM. The system environment is invalid.
PROMPT> The value displayed in HDLM version indicates the HDLM version. Viewing HDLM Component Information This section explains how to display HDLM component information. To display HDLM component information, execute the dlnkmgr command's view operation with the -sys parameter specified. The following shows an example in which the command is executed: PROMPT>dlnkmgr view -sys HDLM Version : x.x.
Using the Windows Administrative Tool (Performance) to Check Path Information The HDLM Performance Monitor uses the Windows administrative tool Performance to display path information. Note: ¢ ¢ The function for checking path information using the Windows administrative tool is not supported in a non-x86 edition of Windows Server 2003, Windows Server 2008, or Windows Server 2012. If an error occurs in the HDLM performance monitor, performance information is not collected after the error.
Counter name Description Disk Read Bytes/Sec The amount of data transferred per second from the disk during read operations. Disk Write Bytes/Sec The amount of data transferred per second to the disk during write operations. Table 4-2 Selectable Items for Instances Selectable items# Description _Total Selecting this item displays the total value of each instance. pathid disk-number drive-letter Selecting this item displays the instance of the selected path.
Starting the HDLM Manager During installation, the HDLM manager is registered as a Windows service and the startup type is set to Automatic. This means that when Windows starts, the HDLM manager will also start automatically. If, for some reason, the HDLM manager does not automatically start, do the following: Log on to Windows as a member of the Administrators group. From Control Panel, choose Administrative Tools, and then Services.
HDLM Resident Processes The table below lists and describes the resident processes in HDLM. To monitor these processes, use the names below. Table 4-3 HDLM resident processes Process Service Description dlmmgr.exe DLMManager HDLM manager process hbsa_service.exe HBsA Service Hitachi Command Suite Common Agent Component# process hntr2mon.exe Hitachi Network Objectplaza Trace Monitor 2 Hitachi Network Objectplaza Trace Library (HNTRLib2) process hntr2srv.
3. If the LU is not displayed in the Disk Management window, perform the following operations to add the LU as an HDLM management-target. ¢ ¢ 4. From the Device Manager window of Windows, select Disk drives, and then click Scan for hardware changes. From the Disk Management window of Windows, click Rescan Disks. Use the dlnkmgr view -path command or the HDLM GUI to confirm that the PathID has been added. The figure below shows an example of how to use the command to confirm that an LU has been added.
When you create a partition, assign the same drive letter as the one assigned for node A in step 3. 6. Stop node B, and then restart node A. 7. On node A, register the new LU in MSCS, and set it up. 8. Restart node B. Checking an Added Path You can add a path, by inserting a cable into an existing LU, even while the host (on which HDLM is installed) is running. When you add a path without adding an LU, what is displayed in the disk management window does not changed.
- KAPL05301-E Note that these messages are output by Windows activities, and not by an error in HDLM. Deleting an LU Dynamically The LU deletion function automatically removes an LU from HDLM management when all the paths to that particular LU are disconnected. You can set up the LU deletion function by specifying the dlnkmgr command's set operation together with the -rmlu on parameter. You can also set up this function in the Options window of the HDLM GUI.
When an LU is deleted from the HDLM management target by using the LU deletion function, the KAPL08022-E message might not be output to the event log. In this case, refer to the KAPL05301-E message to check the path information. The figure below shows an example display of the KAPL05301-E message. Figure 4-3 An example display of the KAPL05301-E message In the event viewer, deleted path information is displayed in the following format: PathID PathName DskName iLU ChaPort.
The following table shows the items and descriptions for the path information, which are displayed in the KAPL05301-E message. Table 4-4 Items and Descriptions for the Path Information Displayed in the KAPL05301-E Message Item Description PathID An AutoPATH_ID. Host port number Elements of a PathName.
4-22 HDLM Operation Hitachi Dynamic Link Manager (for Windows®) User Guide
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 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-33. What To Do for a Path Error When a path error is detected by HDLM, you must immediately resolve the error and restore the path.
Figure 5-2 Troubleshooting Procedure When a Path Error Occurs The following shows the procedure for using the HDLM command (dlnkmgr) to handle a path error. Examining the Messages Examine the messages that are output to the host event log. If the KAPL08022-E message is output, view the message to check the path in which the error has occurred. For details on each item displayed in messages, see Checking Error Information in Messages on page 5-2.
Identifying the Error Path Check the obtained path information to find the path with the error. In the Status column, the error path has the status Offline(E) or Online(E). Narrowing Down the Hardware That Might Have Caused the Error Check the DskName, iLU, ChaPort, and HBAPortWWN columns of the path with the error to narrow down the hardware that may be the cause of the error.
Figure 5-3 Troubleshooting Procedure When a Program Error Occurs The following shows the procedure for handling a program error by using the HDLM command (dlnkmgr). Examining the Messages Examine the messages that are output to the host event log. If an error occurs in an HDLM program, a message other than KAPL08xxx is output to the event log. Examine the content of the message. Messages with error level E (Error) or higher require corrective action.
problem. For details on the view operation, see view (Displays Information) on page 6-33. Execute the following command: Example: dlnkmgr view -sys If the KAPL01012-E message appears as a result of executing the command The following shows the KAPL01012-E message: KAPL01012-E Could not connect the HDLM manager. Operation name = view Start the HDLM manager. For details about how to start the HDLM manager, see Starting the HDLM Manager on page 4-15.
6 Command Reference This chapter describes the HDLM command (dlnkmgr) and its operations.
Overview of the HDLM Command dlnkmgr This section describes how to specify the HDLM command dlnkmgr and its subcommands (called operations in HDLM). Command format Enter the command using the following format: dlnkmgr operation [parameter [parameter-value]] dlnkmgr The command name. operation The type of operation entered after dlnkmgr. parameter A value required for an operation. parameter-value A value required for an operation parameter.
¢ ¢ If you are using Windows Server 2003 , execute HDLM commands as a member of the Administrators group. If you are executing HDLM commands in Windows Server 2008 or Windows Server 2012, see Using Windows Server 2008 or Windows Server 2012 on page 4-3. To specify a value that contains a space in its parameter, enclose the entire value in double quotes (").
PROMPT>dlnkmgr clear -pdst -s KAPL01001-I The HDLM command completed normally. Operation name = clear, completion time = yyyy/mm/dd hh:mm:ss PROMPT> To Display the Format of the clear Operation -help Displays the format of the clear operation. Example PROMPT>dlnkmgr clear -help clear: Format dlnkmgr clear -pdst [-s] KAPL01001-I The HDLM command completed normally.
Examples Example 1 The following example shows how to display all the operations available in the HDLM command. PROMPT>dlnkmgr help dlnkmgr: Format dlnkmgr { clear | help | offline | online | set | view | delete} KAPL01001-I The HDLM command completed normally. Operation name = help, completion time = yyyy/mm/dd hh:mm:ss PROMPT> Example 2 The following example shows how to display the formats of multiple operations.
help: Format dlnkmgr help { clear | offline | online | set | view | delete} KAPL01001-I The HDLM command completed normally. Operation name = help, completion time = yyyy/mm/dd hh:mm:ss PROMPT> offline (Places Paths Offline) The dlnkmgr command's offline operation places online paths offline. Specify the paths to be placed offline by specifying an HBA port, CHA port, single path, or HBA port WWN. There must always be at least one online path accessing each LU.
This parameter is optional because offline is always used for paths, so it is assumed. Make sure that you specify the paths to be taken offline by using the hba, -cha, -pathid, or -hbaportwwn parameter. -hba host-port-number.bus-number Use this parameter to place offline, at one time, all the paths that pass through a specific HBA port. The command will place offline all the paths connected to the HBA port that has the specified host port number and bus number.
AutoPATH_IDs are re-assigned every time the host is restarted. Always make sure that you use the view operation to find the current AutoPATH_ID of the target path, before executing the offline operation. Example The following example shows how to place offline all the paths connected to the channel adapter port 0A.
For details on how to execute the view operation and display the HBA port WWN and path name, see Parameters Used When Displaying Path Information on page 6-43 in Parameters on page 6-35. Example The following shows an example of placing offline the paths for which the HBA port WWN is 10000000C93213BA, target ID is 0000000000000001, and host LU number is 0000 while confirming command operation.
Valid value AutoPATH_ID { 000000 - 999999 }(Decimal) Host_LUN { 0000 - FFFF }(Hexadecimal) KAPL01001-I The HDLM command completed normally. Operation name = offline, completion time = yyyy/mm/dd hh:mm:ss PROMPT> Reference Using the view operation together with Windows commands enables you to filter the path information listed for a specific HBA port or channel adapter port. For details about the view operation, see view (Displays Information) on page 6-33.
online (Places Paths Online) The dlnkmgr command's online operation places offline paths online. To specify the paths to be placed online, specify an HBA port, CHA port, single path, or HBA port WWN. Format To Place Paths Online dlnkmgr online [-path] [-hba host-port-number.
operation. Enter a period between these two parameter values. For details about the view operation, see view (Displays Information) on page 6-33. Leading zeros of each parameter value can be omitted; however, when the host port number or bus number of the target HBA port is 0000, enter 0000 or 0 for the corresponding parameter value. Example The following example shows how to place online all paths connected to an HBA port whose host port number is 0001 and bus number is 0001: PROMPT>dlnkmgr online -hba 1.
Use this parameter to place a single path online. Specify the current AutoPATH_ID of the target path, which is displayed by using the view operation. For details about the view operation, see view (Displays Information) on page 6-33 Leading zeros can be omitted (000001 and 1 indicate the same AutoPATH_ID); however, when the target AutoPATH_ID is 000000, enter 000000 or 0 for the parameter value. AutoPATH_IDs are re-assigned every time the host is restarted.
of all the paths in the Online(S) and Online(D) statuses, specify only hapath. -dfha Use this parameter to change the paths to the primary volume (P-VOL) in an HAM environment to Online(D). The Online(S) status changes to the Online(D) status. When you do not specify this parameter, the status of the P-VOL paths in the HAM environment will be changed to the Online(S) status.
dlnkmgr online [-path] -cha -pathid AutoPATH_ID [-s] dlnkmgr online [-path] [-pathid AutoPATH_ID] [-s] dlnkmgr online [-path] [-hbaportwwn HBA_Port_WWN [-tid Target_ID -hlun Host_LUN]] [-s] dlnkmgr online [-path] -hapath [-lu -pathid AutoPATH_ID] [-s] s] dlnkmgr online [-path] -dfha [-lu -pathid AutoPATH_ID] [- Valid value AutoPATH_ID { 000000 - 999999 }(Decimal) Host_LUN { 0000 - FFFF }(Hexadecimal) KAPL01001-I The HDLM command completed normally.
status of, has been deleted, and then resolve the path error. For details, see Deleting an LU Dynamically on page 4-19. set (Sets Up the Operating Environment) The dlnkmgr command's set operation sets the HDLM operating environment.
Table 6-2 Default and Recommended Values Item name Load balancing Default value Recommended value on on The Extended Least I/Os algorithm is used. The recommended algorithm depends on the operating environment. 3 3 Collect error information for the Information level and higher. Collect error information for the Information level and higher. Error log file size 9900 (KB) 9900 (KB) Number of error log files 2 2 Trace level 0 0 Do not output any trace. Do not output any trace.
Item name Default value Recommended value you want to display the physical storage system information. # This item is applied only when Hitachi AMS2000 series, Hitachi SMS series, or HUS100 series storage is used. -lb {on [-lbtype {rr|exrr|lio|exlio|lbk|exlbk}]|off} Enables or disables load balancing.
HDLM GUI logs: dlmguin.log (n indicates a file number of 1 or 2) Table 6-3 Values of the Error Log Collection Level on page 6-19 shows the values of the error log collection level. If an error occurs, you may have to set the error log collection level to 1 or higher to collect log information. Table 6-3 Values of the Error Log Collection Level Value Description 0 Collects no error log. 1 Collects error information for the Error or higher level.
When combined with the specification for the error log file size, the maximum total size of error log files that can be collected is 32000000KB (approximately 30GB). Only the number of files for HDLM manager logs (dlmmgrn.log (n indicates a file number from 1 to 16)) can be set. For HDLM GUI logs (dlmguin.log (n indicates a file number of 1 or 2)), the number of log files is set at 2. -systflv trace-level Specify the trace output level. The trace files for which trace levels can be set are hdlmtrn.
When combined with the specification for the trace file size, the maximum total size of the trace files that can be collected is 1024000KB. If the value is changed to something smaller than the value that is currently set, the execution confirmation message KAPL01097-W will be displayed and the trace file will be deleted temporarily. The trace files for which the number of files can be set are hdlmtrn.log (n indicates a file number from 1 to 64).
Enabling automatic failbacks might automatically place paths online that were intentionally placed offline (for example, paths placed offline for maintenance work). If you want to prevent such paths from automatically being placed online, disable this function. When intermittent errors occur in paths or storage systems, statuses of paths alternates between the online and offline status frequently, thus decreasing I/O performance.
When you set the number of times that the error is to occur to 1, the above condition does not need to be satisfied. When you change the error monitor interval while intermittent error monitoring is running, the new settings will take effect immediately. When the checking interval is shortened and the checking interval time after the change has already elapsed during the current checking interval, the path status check will start over.
When a value of 2 or more is specified for the number of times, the following condition must be satisfied: error-monitoring-interval >= checking-interval-for-automaticfailback x number-of-times-error-is-to-occur-during-intermittenterror-monitoring If this condition is not satisfied, the KAPL01080-W message will be output and an error will occur.
completes. When intermittent error monitoring is not being performed, the number of errors that determine that an intermittent error has occurred is not counted and this value is not changed. The number of times that the error is to occur is stored in the system, even when -iem off is specified and intermittent error monitoring is disabled.
Setting AFB IEM Available operation Change the IEM settings. Set IEM to off. off off on#2 off Result of operation • While a path is being monitored, the value of the error count and the elapsed monitoring time are reset to 0, and then intermittent error monitoring will restart.#1 • When a path is not being monitored, the IEM settings will take effect again when the path is recovered from the error status by performing an automatic failback. • IEM is disabled.
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 PROMPT> -lic Specify this option for when a license is updated. The HDLM license is provided via a license key or license key file. A license key file is a file that stores the HDLM license key.
KAPL01049-I Would you like to execute the operation? Operation name = set [y/n]: y KAPL01071-I A permanent license was installed. PROMPT> Example 2 The following example shows how to update the license key when the license key file does not exist: PROMPT>dlnkmgr set -lic KAPL01049-I Would you like to execute the operation? Operation name = set [y/n]: y KAPL01083-I There is no license key file.
Value Description on -force The LU is removed from HDLM-management when all the paths to the LU are disconnected, even when an Offline(C) path is included. The removed LU is restored after it is recovered from the physical failure and the disk is re-scanned. -audlog {on [-audlv audit-log-data-collection-level] [-category [[ss][a][ca]|all]]|off} Specifies whether to collect audit log data. on: Audit log data is collected. off: Audit log data is not collected.
Value Explanation Audit log events of the StartStop, Authentication, and ConfigurationAccess categories are collected. all -lbpathusetimes number-of-path-use-times Specifies the number of times the same path can be used for I/O operations when the Round Robin (rr), Least I/Os (lio), or Least Blocks (lbk) algorithm is used for load balancing. You can specify a decimal (base 10) value from 0 to 999999. The default is 1. If you specify 0, operation is the same as when load balancing is disabled.
on: Enabled off: Disabled If the display of the physical storage system information is enabled, information about the physical storage system is displayed. If the display of the physical storage system information is disabled, information about the storage system recognized by the operating system is displayed. For a virtualized storage system, virtual information is displayed, and for a non-virtualized storage system, physical information is displayed.
| | | | | | | | | | | | | | storage } ] | | | | -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 ] -audlog off -lbpathusetimes Number-Of-PathUseTimes -expathusetimes Number-Of-ExPathUseTimes -dpc { on
view (Displays Information) The dlnkmgr command's view operation displays HDLM program information, HDLM management-target device information, path information, and LU information. If the I/O load on the dynamic disk is heavy, it might take a while to execute the view operation.
To display a summary of path information dlnkmgr view -path -c [-pstv|-vstv] [-stname] [-srt {lu|cp}] [-t] To Display LU Information To display LU information dlnkmgr view -lu [-pstv|-vstv] [-hdev host-device-name|-pathid AutoPATH_ID] [-exlu] [-t] To display LU information (by adding items to be displayed) dlnkmgr view -lu -item [ [slpr] [pn] [cp] [clpr] [type] [ic] [ie] [dnu] [iep] [dpc] [phys] [virt] [vid] [ha] [hastat] |all ] [-pstv|-vstv] [-hdev host-device-name|-pathid AutoPATH_ID] [-exlu] [-t] To d
Parameters This section describes the parameters for the view operation, in the following order: Parameters Used When Displaying Program Information on page 6-35 Parameters Used When Displaying HDLM Management-target Device Information on page 6-42 Parameters Used When Displaying Path Information on page 6-43 Parameters Used When Displaying LU Information on page 6-60 Parameter Used When Displaying the Format of the view Operation on page 6-76 Parameters Used When Displaying Program Information -sys [-sfun
Parameter and program information to be displayed Item Description When the setting status of load balancing is on, one of the following types of algorithms is used for load balancing is displayed in the parentheses following on.
Parameter and program information to be displayed Item Description Number Of Trace Number of trace files Files Path Health Checking • Settings for path health checking: on: Enabled off: Disabled • Checking interval: When the setting of the path health checking is on, the checking interval of path health checking is displayed within the parentheses following on. The time is in minutes.
Parameter and program information to be displayed Item Description • Checking interval The parentheses following the setting status shows the checking interval for reviewing information about the switching of controllers performed by the storage system. "Minute" is used as the unit. If different settings have been specified for each storage system or LU, an asterisk (*) is added after the parentheses in which the checking interval is displayed.
Parameter and program information to be displayed Item Description For example, when there are 100 days left until the license period (2006/08/21) expires, the following appears: 2006/08/21(100days after) -audlog Audit Log Settings for audit log data collection: • Information about audit log data collection settings Whether collection is enabled: on: Enabled off: Disabled • Audit log data collection level: When audit log data collection is on, the collection level that has been set is displayed wit
Parameter and program information to be displayed storage-systeminformation setting Item Description off: Disabled # When the HDLM manager starts, HDLM cluster servers are automatically recognized. Examples Example 1 The following example shows how to display information about the HDLM function settings: PROMPT>dlnkmgr view -sys -sfunc HDLM Version : x.x.
HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.x-xx yyyy/mm/dd hh:mm:ss 128 KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss PROMPT> Example 4 The following example shows how to display information about the HDLM driver: PROMPT>dlnkmgr view -sys -pdrv HDLM Driver Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss KAPL01001-I The HDLM command completed normally.
= view, completion time = yyyy/mm/dd hh:mm:ss PROMPT> Example 9 The following example shows how to display the value of the display-ofthe-physical-storage-system-information setting: PROMPT>dlnkmgr view -sys -pstv Physical Storage View : off KAPL01001-I The HDLM command completed normally.
Item Description 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 PROMPT>dlnkmgr view -stinfo EMC Symmetrix DMX Series, CLARiiON CX Series : on HP StorageWorks EVA Series : on KAPL01001-I The HDLM command completed normally.
system is displayed. If neither parameter is specified, information is displayed according to the value specified in the -pstv parameter of set operations. For information about the items that are displayed differently depending on the specified -pstv and -vstv parameters, see Table 6-10 Display items for which the display results of the view operation differ depending on the -pstv parameter specification on page 6-31 in Parameters on page 6-16.
• When an HDLM management-target device is the EMC DMX series, EMC CX series, or HP EVA series: If this parameter is specified, all 32 digits of the iLU are displayed instead of truncating the iLU to 13 digits. If this parameter is not specified, any characters after the 13th digit of the iLU of the EMC DMX series, EMC CX series, and HP EVA series will not be displayed. Ellipsis (...) will be displayed instead.
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 Status# None Type type IO-Count ic IO-Errors ie DNum dnu HDevName hd IEP iep HBAPortWWN hbaportwwn Physical-LDEV phys Virtual-LDEV virt Physical-DskName vid Physical-iLU vid Physical-ChaPort vid Org-DskName ha Org-iLU ha # 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).
Specify a drive letter to indicate the desired host device. You cannot specify the host device unless a drive letter has been assigned. The host-device-name string is case sensitive. When you specify this parameter, HDevName is displayed by default. It is not necessary to specify hd for the -item parameter. If the command ends with the KAPL01064-W or KAPL01013-E message, follow the recommended action in the message.
DMX series, EMC CX series, and HP EVA series will not be displayed. Ellipsis (...) will be displayed instead. • When an HDLM management-target device is configured for only the Thunder 9500V series, Lightning 9900V series, Hitachi USP series, Hitachi AMS2000/AMS/WMS/SMS series, HUS100 series, Universal Storage Platform V/VM series, or Virtual Storage Platform series: 16 digits are displayed for the iLU even if this parameter is specified. -t Omits the title for each information item.
path information. The displayed contents are also shortened, so that each path information item is displayed on a single line. The items that are displayed are PathID, DskName, iLU, CP, Status, and Type. For details on what is displayed for each item, see Table 6-14 Displayed Path Information on page 6-51. When you use the -c parameter, the number of characters that can be displayed in the product ID element of the DskName field is limited to 10.
-t Omits the title for each information item. Example The following example shows how to display a summary of the path information in order of iLUs. Displayed path information Table 6-14 Displayed Path Information on page 6-51describes 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.
Displayed Item No summary displayed Description Summary displayed check the status of individual paths and resolve the problem for any paths that have an error status. Status of the displayed paths. The displayed status indicates the following: PathStatus • Online: All paths are available. • Reduced: Some paths are not available.
Displayed Item No summary displayed Description Summary displayed Storage Platform V/VM series, and Virtual Storage Platform series the serial number of the storage system. For example, 0051. For the EMC DMX series, EMC CX series, and HP EVA series, a hyphen (-) is displayed.
Displayed Item No summary displayed Description Summary displayed The ID that differs from the LU number in the storage system and that identifies the LU is indicated by a hexadecimal number. iLU consists of 32 digits. The first 13 digits of iLU are displayed, and the rest of the digits are displayed as an ellipsis (...). When the -exlu parameter is specified, the entire value of iLU is displayed.
Displayed Item No summary displayed Description Summary displayed Own: Owner path Non: Non-owner path When connecting to the Lightning 9900V series, Hitachi USP series, Universal Storage Platform V/VM series, Virtual Storage Platform series, VSP G1000 series, Hitachi AMS2000 series#3, Hitachi SMS series#3, HUS100 series#3, or HUS VM, all paths are owner paths. • For the EMC DMX series, EMC CX series, and HP EVA series: A hyphen (-) is displayed.
Displayed Item No summary displayed Description Summary displayed 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). • * Indicates that an intermittent error occurred (automatic failbacks do not check the path) (the path status is Online, Online(E), or Offline(E)).
Displayed Item No summary displayed Description Summary displayed • For HUS VM indicated by a hexadecimal number. The first two characters of iLU are the CU number, and the last two characters are the internal LU number within the CU. • For Hitachi Virtual Storage Platform, indicated by a hexadecimal number. The first two characters of iLU are the number of the logical DKC (Disk Controller), the middle two numbers are the CU number, and the last two characters are the internal LU number within the CU.
In a cluster configuration, an offline operation requested during reserve processing is put into the waiting-to-execute state, and does not execute until the reserve processing finishes. #3 This storage system applies when the dynamic I/O path control function is disabled. #4 The drive letter assigned to a dynamic disk volume is not displayed.
Product ID Model names of storage systems With the -stname parameter (Displays the following for the model ID) Without the -stname parameter Hitachi SMS series SMS Hitachi WMS series WMS HUS100 series HUS100 Lightning 9900V series SVS Emulation type# 9970/9980 SVS • Hitachi Universal Storage Platform 100 • Hitachi Universal Storage Platform 600 • Hitachi Universal Storage Platform 1100 • Hitachi NSC55 • Hitachi Universal Storage Platform V • Hitachi Universal Storage Platform VM USP
characters after the 9th character are not displayed, and ellipsis (...) are displayed instead. ¢ For command devices, -CM is added to the end of the emulation type of the storage system (for example, DF600F-CM). Parameters Used When Displaying LU Information When displaying LU information, if the -item parameter, -c parameter, or the -c -item parameter is specified at the same time as the -lu parameter, you can add and display items and display a summary of LU information.
Displays information only for the paths accessing the specified host device, if the -hdev parameter is specified. Specify a drive letter to indicate the desired host device. You cannot specify the host device unless a drive letter has been assigned.If the command ends with the KAPL01064-W or KAPL01013-E message, follow the recommended action in the message. If the -pathid parameter is specified, only information about the LU connected to the path with the specified AutoPATH_ID is displayed.
000010 Online 000001 Online 000011 Online 6006048000018... N 000002 Online 000012 Online 6006048000018... O 000003 Online 000013 Online KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss PROMPT> 6006048000018...
The items specified with the -item option are displayed among with those displayed by the -lu option. If all is specified for the -item parameter, all items that can be added are displayed except for DPC, Physical-LDEV, Virtual-LDEV, PhysicalProduct, Physical-SerialNumber, Physical-iLU, Physical-ChaPort, Org-Product, Org-SerialNumber, and Org-iLU.
If the -pstv parameter is specified, information about the physical storage system is displayed. If the -vstv parameter is specified, information about the storage system recognized by the operating system is displayed. If neither parameter is specified, information is displayed according to the value specified in the -pstv parameter of set operations.
Example 2: When using Hitachi AMS2000 series, Hitachi SMS series , or HUS100 series storage and displaying LU information with DPC added to the display items: PROMPT>dlnkmgr view -lu -item dpc Product : HUS100 SerialNumber : 9203008 LUs : 3 Dynamic I/O Path Control : on* iLU HDevName DPC PathID Status 000006 E on 000000 Online 000003 Online 000007 F off 000001 Online 000004 Online 000008 G on 000002 Online 000005 Online KAPL01001-I The HDLM command completed normally.
¢ 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. You cannot specify the -c parameter together with the -hdev or -pathid parameter. For details on the contents of each display item, see Table 6-19 Displayed LU Information on page 6-69. The sub-parameters are as follows: ¢ -pstv|-vstv If the -pstv parameter is specified, information about the physical storage system is displayed.
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. If no value is specified for the -item parameter, all the items that can be added are displayed. See Table 6-19 Displayed LU Information on page 6-69for the contents of each displayed item.
For information about the items that are displayed differently depending on the specified -pstv and -vstv parameters, see Table 6-10 Display items for which the display results of the view operation differ depending on the -pstv parameter specification on page 6-31 in Parameters on page 6-16. -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-19 Displayed LU Information Displayed item No summary displayed Description Summary displayed • Product For the Thunder 9500V series, Lightning 9900V series, Hitachi USP series, Hitachi AMS2000/AMS/WMS/SMS series, HUS100 series, Universal Storage Platform V/VM series, and Virtual Storage Platform series: 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, Li
Displayed item No summary displayed Description Summary displayed This number combined with the storage system name (shown in DskName) identifies the LU that is accessed by a path. • For the Lightning 9900V series, Hitachi Universal Storage Platform 100, Hitachi Universal Storage Platform 600, Hitachi Universal Storage Platform1100,HUS VM, and Hitachi NSC55, the first two characters of iLU are the CU (Control Unit) number, and the last two characters are the internal LU number within the CU.
Displayed item No summary displayed Description Summary displayed HDevName#1# - Host device name. 3 A drive letter is displayed. If no drive letter has been assigned, a hyphen (-) is displayed. The drive letter is displayed in the HDevName field even if the value of the DNum field is 0. Note, however, that the displayed drive letter is the drive letter for one of the Devs included in the LU. - DPC The setting information about the dynamic I/O path control function is displayed for each LU.
Displayed item No summary displayed CLPR#1 Status Description Summary displayed - - The number of the CLPR to which the CHA port belongs, indicated by a number from 0 to 31. Note that a hyphen (-) is displayed if the following items are subject to display: • CHA ports in the storage system that do not support the cache logical partition function • Paths connected to the Snapshot Image of the Copy-on-write Snapshot of the Hitachi AMS2000/AMS/WMS/SMS series.
Displayed item No summary displayed Description Summary displayed When connected to the Lightning 9900V series, Hitachi USP series, Universal Storage Platform V/VM series, Virtual Storage Platform series, VSP G1000 series, Hitachi AMS2000 series#5, Hitachi SMS series#5, HUS100 series#5, or HUS VM, all paths are owner paths. • For the EMC DMX series, EMC CX series, and HP EVA series: A hyphen (-) is displayed. IO-Count#1 - Total I/O count for a path.
Displayed item No summary displayed PhysicalLDEV Description Summary displayed - The model ID, serial number, and iLU number of a physical volume are separated by periods and displayed. You can identify the physical volume from this information. If the volume is not virtualized, a hyphen (-) is displayed. VirtualLDEV - Displays the model ID, serial number, and iLU number of a virtual volume, separated by periods. You can identify the virtual volume from this information.
Displayed item No summary displayed - Description Summary displayed OnlinePaths Org-Product - Number of online paths among the paths recognized by HDLM for the LU. When the value of Paths is equal to the value of OnlinePaths, all paths are online. If the value of OnlinePaths is less than that of Paths, some paths may have an error status, in which case you should check the status of individual paths and take resolve the problem for any paths that have an error status.
- The user selected the item to be displayed by using the -lu -c -item parameter. - No value was specified for the parameter. #3 The drive letter assigned to a dynamic disk volume is not displayed. #4 In a cluster configuration, an offline operation requested during reserve processing is put into the waiting-to-execute state, and does not execute until the reserve processing finishes. #5 This storage system applies when the dynamic I/O path control function is disabled.
PROMPT> delete (Deletes a Path Dynamically) The dlnkmgr command's delete operation batch-deletes disconnected paths whose statuses are Offline(C) from the HDLM-management targets. You can execute this command dynamically without any effects on existing paths. Format To Delete a Path Dynamically dlnkmgr delete -path [-s] To Display the Format of the delete Operation dlnkmgr delete -help Parameters To Delete a Path Dynamically -path Indicates that the target of the operation is a path managed by HDLM.
Note: Any paths excluded from the HDLM-management targets must be deleted from the OS before executing this command. To Display the Format of the delete Operation -help Use this parameter to display the delete operation format. Example PROMPT>dlnkmgr delete -help delete: Format dlnkmgr delete -path [-s] KAPL01001-I The HDLM command completed normally.
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 dlmstnn.log Log file of the function for setting storage system names. hcmdslicense2.log Log when updating the license hdlmtrn.log Trace file hs_err_pidnnnn.log Java execution log (nnnn indicates a process ID) dlmguin.log HDLM GUI log dlmgui_launcher.log dlmwebgui_setup.log folder-to-whichcollected-information-isoutput\folder-to-whichWindows-is-introduced (%SystemRoot%)#3 dlmwebagent[1N].
Folder that stores collected files#1 Files Explanation installation-destinationdrive-name_\Program Files \VERITAS\Volume Manager M.N\logs#6 folder-to-whichcollected-information-isoutput\VCS-installationdestination-drive-name_ \Program Files\VERITAS \Cluster Server\log All files under log VCS log Integrated trace file output folder specified in the Hitachi Network Objectplaza Trace Library utility hntrn.log#8 Integrated trace file (HNTRLib2) hntr[1-16].
Folder that stores collected files#1 Files Explanation dlmmgr-lu.txt Result of the dlnkmgr view lu -item pn cp type ic ie dnu slpr clpr dpc vid 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 Explanation hyper-v.txt WMI class instance related to Hyper-V hyperv-haadm.txt Windows event log related to Hyper-V hyperv-itegadm.txt Windows event log related to Hyper-V hyperv-synfcadm.txt Windows event log related to Hyper-V hyperv-synnicadm.txt Windows event log related to Hyper-V hyperv-synstoradm.txt Windows event log related to Hyper-V hyperv-synstorope.txt Windows event log related to Hyper-V hyperv-vmmsadm.
Folder that stores collected files#1 Files Explanation wevFCOper.txt Contents of Windows event log wevFCMgrA.txt Contents of Windows event log win_dep.log DEP setting information winmsd.txt Windows system information folder-to-whichcollected-information-isoutput\hbsainfo All files under hbsainfo#11 Error information of a Hitachi Command Suite product other than HDLM folder-to-whichcollected-information-isoutput\%SystemDrive% hdlminst.
For Windows Server 2003 (excluding the x86 edition), Windows Server 2008 (excluding the x86 edition), or Windows Server 2012, Program Files is Program Files (x86). #8 File names are created by using the value in the Hitachi Network Objectplaza Trace Library utility's Output (directory and prefix), adding 2 onto the end, and then adding a file number onto the end of that. The default file names range from hntr21.log to hntr216.log.
-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. Start a host from among the hosts that make up the MSCS system. 2. Choose Start, Settings, Control Panel, double-click Administrative Tool, and then double click Computer Management. 3.
ExclusiveAccessRegistrantOnly 000001 0001.0000.0000000000000000.0001 1 200000E08B1059EC ExclusiveAccessRegistrantOnly KAPL10655-I Specify the PathID of the LU for which you want to clear persistent reservation information. (To cancel, press the x key):0 KAPL10656-I The persistent reservation information of PathID = 0 will be cleared. Is this OK? [y/n]:y KAPL10657-I If you continue this process, the reservation of the LU you specified will be cleared.
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. A registered PRSV key becomes valid after the host is rebooted.
successful. (PRSV key = 0123456789abcdef) PROMPT> -s Specify this parameter to avoid displaying a confirmation message upon execution of the dlmprsvkey utility. -v Specify this parameter to display the registered PRSV key. Example PROMPT>dlmprsvkey -v KAPL12116-I The registered PRSV key will now be displayed. (PRSV key = 0123456789abcdef) PROMPT> -h Displays the format of the dlmprsvkey utility. If you do not specify any parameters, a warning message will appear.
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: PROMPT>dlmchkpath -singleconnect KAPL12401-I All LUs managed by HDLM are in a single path configuration.
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.
"version","x.x.x-xx" KAPL13801-I The dlmhostinfo utility for confirming HDLM installation information completed normally. PROMPT> The following table refers to the items that make up the output installation information.
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. For details about the installation-information settings file, see Contents of an Installation-Information Settings File on page 7-18. -c Checks the contents of the installation-information settings file, the license, and other necessary information, but does not perform an installation.
Table 7-3 Keys That Can Be Defined in the [INSTALLATION_SETTINGS] Section Necessity of definition Key name Description installfile_locat ion Specify the absolute path name of the drive in which the installation DVD is inserted. If this key is omitted, the installer uses the following folder: Maximu Upgrad m e charact New installat er installat ion or length# ion Re1 installat ion Optional Optional 100 workdir Specify an absolute path to an Optional output folder.
Necessity of definition Key name Description Maximu Upgrad m e charact New installat er installat ion or length# ion Re1 installat ion If this key is omitted ¢ ¢ storage_eva In Windows Server 2003, the two series are not included as management targets. In Windows Server 2008, the two series are included as management targets. Specify whether to include the HP EVA series as possible management targets of HDLM.
Necessity of definition Key name Description Maximu Upgrad m e charact New installat er installat ion or length# ion Re1 installat ion n: Do not restart (default). In a cluster environment, do not specify y. Legend: Optional: If no key or setting value is specified, the installer uses the default value. Not required: The specification of any key or setting value is unnecessary. If a key or setting value is specified for the key, the installer ignores the specified value.
[ENVIRONMENT_SETTINGS] section This section defines HDLM operational and function information. HDLM operational and function information is optional, however, if omitted, the installer will use the following values: • For a new installation, the installer uses the default values of the keys that are listed in the following Table 7-4 Keys That Can Be Defined in the [ENVIRONMENT_SETTINGS] Section on page 7-22. • For an upgrade installation or re-installation, the installer uses the old HDLM setting values.
Necessity of definition Key name#1 Description#2 Maximu m Upgrade charact installat New er ion or installat length# Reion 3 installat ion (rr), Least I/Os (lio), or Least Blocks (lbk) algorithm is used for load balancing. You can specify a value from 0 to 999999. The default is 1. Specify 0 to disable load balancing.
Necessity of definition Key name#1 trace_file_numbe r Description#2 Specify the maximum number of trace files (hdlmtr[1-64].log). Maximu m Upgrade charact installat New er ion or installat length# Reion 3 installat ion Optional Optional 2 Optional Optional 3 Specify, in minutes, the interval at Optional which the path health check will be performed. Optional 4 Optional 3 Optional 4 Optional Optional 3 Optional Optional 4 You can specify a value from 2 to 64. The default is 4.
Necessity of definition Key name#1 Description#2 Maximu m Upgrade charact installat New er ion or installat length# Reion 3 installat ion You can specify a value from 1 to 1440. The default is 30. intermittent_err or_monitor_numbe r#5 Specify how many times an error needs to occur to cause HDLM to assume an intermittent error. Optional Optional 2 Specify whether to enable or Optional disable the dynamic I/O path control function by using the values below.
Legend: Optional: ¢ ¢ For a new installation: If no key or setting value is specified, the installer uses the default values. For an upgrade installation or re-installation: If no key or setting value is specified, the installer uses the old HDLM setting values. #1 Keys that are not specified for an upgrade installation or re-installation inherit the current key settings. #2 Specifying an invalid value results in an error.
load_balance_type=exlio load_balance_same_path_use_times=1 lbex_usetimes_limit=100 error_log_level=3 error_log_size=9900 error_log_number=2 trace_level=0 trace_file_size=1000 trace_file_number=4 path_health_check=on path_health_check_interval=30 auto_failback=on auto_failback_interval=1 intermittent_error_monitor=off #intermittent_error_monitor_interval=30 #intermittent_error_monitor_number=3 dynamic_io_path_control=off dynamic_io_path_control_interval=10 remove_lu=off remove_lu_force=off Note: ¢ ¢ If a
The removehdlm Utility for Removing HDLM The removehdlm utility removes HDLM. If you execute the removehdlm utility with the -s parameter specified, no dialog boxes will be displayed during an unattended removal. Format removehdlm [-s [-r] [-w work-folder] | -h] Parameters -s [-r] [-w work-folder] Executes an unattended removal. -r Restarts the host after a removal. -w work-folder Specifies the folder to which removehdlm.log and work files are output.
8 Messages This chapter describes the format and meaning of the message IDs, and also the terms used in the messages and message explanations. For details on the meaning of the return codes output by HDLM when it receives a request from Global Link Manager and measures to take for them, see Return Codes for Hitachi Command Suite Common Agent Component on page 8-112.
□ 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 (for Windows®) User Guide
Before Viewing the List of Messages This section explains the following information that is needed to locate messages and understand the explanations in the sections from KAPL01001 to KAPL02000 on page 8-4. • Format and meaning of the message IDs • Terms used in the messages and message explanations This information is explained below. Format and Meaning of Message IDs Each message has a message ID. The following table shows the format and meaning of message IDs.
KAPL01001 to KAPL02000 Message ID KAPL01001-I Message Text The HDLM command completed normally. Operation name = aa...aa, completion time = bb...bb Explanation Details The HDLM command completed successfully. When the view -path, or view lu operation is executed, view(pstv) is displayed if the Physical Storage View is disabled, and view(-vstv) is displayed if the Physical Storage View is disabled. aa...aa: Specified operation name bb...bb: Year/month/day hour:minute:second Action None.
Message ID Message Text KAPL01006-W A necessary parameter is not specified. Operation name = aa...aa Explanation Details The specified operation does not contain the necessary parameter. aa...aa: Specified operation name 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.
Message ID Message Text Explanation then retry the HDLM command. For details on the view operation, see view (Displays Information) on page 6-33. 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: Specified operation name bb...
Message ID Message Text KAPL01016-W The target CHA port was not found. Operation name = aa...aa Explanation 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 ¢ view operation Refer to Chapter 3, Creating an HDLM Environment on page 3-1. Creating an HDLM Environment or Reconfiguring the HDLM Operating Environment on page 4-16, and then configure any paths that exist. If the same message appears again, execute the DLMgetras utility for collecting HDLM error information, acquire the error information, and then contact your HDLM vendor or the company for which you have a service contract.
Message ID Message Text Explanation 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. Action The load balancing function is not supported in an environment where MSCS is installed. If you want to use the load balancing function, remove MSCS.
Message ID KAPL01041-E Message Text Explanation 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...aa, parameter = bb...bb, parameter value = cc...
Message ID Message Text KAPL01047-W Only one offline request can be registered in a batch job. Explanation 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 see online (Places Paths Online) on page 6-11. KAPL01051-I Because no path has been selected among the currently displayed paths, the paths in the Offline(C), Offline(E), and Online(E) statuses will be changed to the Online status. Is this OK? [y/n]: Details All the paths will be placed Online because the path selection parameter is not specified for the online operation. To place all the paths Online, enter y. To cancel the operation, enter n.
Message ID Message Text command, a path that cannot be placed in the Offline(C) status was detected. PathID = aa...aa Would you like to continue the processing of the offline operation? [y/n]: Explanation A path that cannot be set to Offline(C) was detected during multi-path offline processing. To ignore this path and perform offline processing for the next path, enter y. To cancel offline processing, enter n. aa...
Message ID Message Text Explanation 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...bb, in a parameter that does not need parameter value = cc...cc a parameter value. aa...
Message ID Message Text Explanation None. KAPL01061-I aa...aa path(s) were successfully placed bb...bb; cc...cc path(s) were not. Operation name = dd...dd Details This message indicates the number of the paths processed in an online/offline operation. aa...aa: Number of paths where the online/offline operation was successful (decimal (base-10) number) bb...bb: Online, Online(S), Online(D) or Offline(C) cc...
Message ID Message Text Explanation As a result of a previous online/ offline operation, the specified path has already been set to Online/Online(S)/Online(D)/ Offline(C). aa...aa: Online, Online(S), Online(D) or Offline(C) Action Use the view operation of the HDLM command (dlnkmgr) to check the status of the path. For details on the view operation, see view (Displays Information) on page 6-33. For details on the online operation, see online (Places Paths Online) on page 6-11.
Message ID Message Text Explanation operation without specifying the host device name. KAPL01065-E The configuration does not support the simultaneous use of the load balancing and cluster support functions. Details If a storage system for which persistent reservations are not supported exists among the HDLM-managed storage systems, the load balancing function cannot be used in the cluster environment. Action Make sure that all HDLM-managed storage systems support persistent reservations.
Message ID Message Text Explanation Action Install a permanent license by the expiration day. KAPL01073-E The temporary license expired. Details The temporary license has expired. Register a permanent license. Action Register a permanent license. KAPL01074-E The emergency license expired. Details The emergency license has expired. Register a permanent license. Action Register a permanent license. KAPL01075-E A fatal error occurred in HDLM. The system environment is invalid.
Message ID Message Text Explanation (automatic-failback-checkinginterval x number-of-times-erroris-to-occur-for-intermittent-errormonitoring). KAPL01081-E The license key file is invalid. File name = aa...aa Details The format of the license key file is invalid. aa...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.
Message ID Message Text parameter = bb...bb, parameter values = cc...cc Explanation bb...bb: Parameter name cc...cc: Parameter values that cannot be specified at the same time Action Execute help operation-name of the HDLM command (dlnkmgr) to check which parameter can be specified, and then retry. For details on the help operation, see help (Displays the Operation Format) on page 6-4.
Message ID Message Text Explanation the DLMgetras utility for collecting HDLM error information, acquire the error information, and then contact your HDLM vendor or the company for which you have a service contract. KAPL01097-W All the current trace files will be deleted. Is this OK? [y/n] 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.
Message ID Message Text Explanation target HBA port WWN. After that, specify the appropriate HBA port WWN, and then retry. KAPL01102-I All the paths which pass the specified aa...aa port will be changed to the Offline(C) status. Is this OK? [y/n]: 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...
Message ID KAPL01107-I KAPL01112-E Message Text Explanation The load balancing type specified for individual LUs will become invalid when this operation is executed. Do you want to execute the operation anyway? Operation name = set [y/n]: Action An attempt to connect to the HDLM driver has failed. Operation name = aa...aa Details If you want to change the load balancing algorithm for the system, enter y. If you want to terminate processing, enter n.
Message ID Message Text Explanation specify the desired setting by using the dlnkmgr set -audlog command. KAPL01117-W An error occurred during processing to read the audit log configuration file. 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.
Message ID Message Text Explanation bb...bb: Online or Online(S) cc...cc: The number of paths which changed to the Online(S) or Online(D) status dd...dd: Online(S), Online(D) or Online(S)/Online(D) ee...ee: The number of paths which failed to change to either the Online, Online(S) or Online(D) status ff...ff: online Action None. KAPL01134-I The target paths are already Online or Online(S). Details The specified paths are already in the Online or Online(S) status as a result of an online operation.
Message ID KAPL01156-I Message Text The dynamic I/O path control function was set to aa...aa for storage. Explanation Details aa...aa: "on" or "off" Action Use the view operation of the HDLM command (dlnkmgr) to check the setting for storage and LUs. For details on the view operation, see view (Displays Information) on page 6-33. KAPL01157-I The dynamic I/O path control function was set to aa...aa for the system. Details aa...
Message ID Message Text Explanation Enter y to change the path configuration, or enter n to cancel the operation. KAPL01163-E The path configuration change failed. (details = aa...aa) Details This message indicates that a delete operation failed. aa...aa: code indicating the content of the error Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or, if you have a maintenance contract for HDLM, the maintenance company.
Message ID Message Text Explanation Action If you want to change the number of times that the same path can be used for the system, enter y. To cancel the operation, enter n. KAPL01167-I All paths will be set to Online or Details Online(D). Is this OK? [y/n]: All paths will be set to Online or Online(D) because no path is specified. To continue, enter y. To cancel the operation, enter n. Action To set all paths to Online or Online(D), enter y. To cancel the operation, enter n.
Message ID Message Text LU that has the specified path ID will be set to Online. Is this OK? [y/n]: Explanation specified LU will be set to Online. To continue, enter y. To cancel the operation, enter n. Action To set to online the all Online(S) or Online(D) paths that are connected to the specified LU with path ID, enter y. To cancel the operation, enter n. KAPL01171-I The target paths are already aa...aa or bb...bb.
Message ID Message Text Explanation Specify a physical CHA port by using the -cha -pathid parameter, and then re-execute the offline or online operation. KAPL01174-W If the Physical Storage View is disabled, the parameter value aa...aa cannot be specified for the -item parameter. Details If the Physical Storage View is disabled, the parameter value shown cannot be specified. aa...aa: virt Action When specifying virtual storage information as a display item, enable the Physical Storage View.
Message ID Message Text Explanation ¢ JHSPGetDriverStatus ¢ JHSPGetADriverStatus ¢ JHSPVerifyAuthorization 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. KAPL02005-E An attempt to start HDLM GUI has failed due to insufficient memory.
Message ID Message Text Explanation This is a confirmation for execution. If you want to execute the operation, click OK. To cancel the operation, click Cancel. aa...aa: Clear Data Action If you want to execute the operation, click OK. To cancel the operation, click Cancel. KAPL02012-I aa...aa has started. Details aa...aa: Operation (character string) ¢ Export CSV ¢ Set Option Information ¢ Refresh ¢ Online ¢ Offline ¢ Clear Data Action None. KAPL02013-I aa...aa has completed successfully.
Message ID Message Text Explanation Action Data has not been input for the specified item. See the HDLM GUI Help to specify a number within the valid range. KAPL02015-W A value which is not a number has been input in aa...aa. Details A character other than a numeric character has been entered in the input field of the Option window. aa...
Message ID Message Text Explanation If you do not want to proceed, click Cancel. Action If you want to execute online processing, click OK. To cancel online processing, click Cancel. KAPL02018-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? [OK/Cancel] Details Among the currently displayed paths, the paths that are not online will be changed to the Online status.
Message ID Message Text Explanation For the path ID of a path for which online/offline processing failed, see the operation log. KAPL02022-W A path that cannot be placed in Details the Online status has been While online processing was being detected. PathID = aa...aa performed for multiple paths, at Would you like to continue the least one path that could not be Online processing? [OK/Cancel]: changed to Online was detected. If you want to ignore the path and continue, click OK.
Message ID Message Text Explanation aa...aa: Operation (character string) ¢ Online ¢ Clear Data ¢ Export CSV ¢ Get Path Information ¢ Refresh Action Click Refresh to update the contents of the view operation, check the path status, and then retry. KAPL02027-E The last Online path or Online(E) path to the LU cannot be placed in the Offline(C) status. PathID = aa...
Message ID Message Text Explanation ¢ Clear Data ¢ Get HDLM Manager Status ¢ Get HDLM Driver Status ¢ Get HDLM Alert Driver Status bb...
Message ID Message Text Explanation Terminate unnecessary applications to increase the amount of free memory, or restart the host. KAPL02033-E An unexpected error occurred, and the aa...aa operation has been stopped. Details An exception occurred during HDLM GUI processing. aa...
Message ID Message Text Explanation want to use the load balancing function, remove MSCS. KAPL02042-E An unexpected error occurred. The HDLM GUI cannot start. Details An exception occurred when starting up the HDLM GUI. 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 operation, see view (Displays Information) on page 6-33. KAPL02053-I KAPL02054-I Would you like to terminate the HDLM GUI? [OK/Cancel] Action aa...aa path(s) were successfully placed Offline(C). The Offline request of bb...bb path(s) were registered. cc...cc path(s) could not be placed Offline(C). Details If you want to terminate the HDLM GUI, click OK. If you do not want to terminate the HDLM GUI, click Cancel.
Message ID Message Text Explanation maintenance company to check whether the storage systems you are using support persistent reservations. KAPL02061-W The getting PathInformation has Details been stopped because the path The path information could not be configuration was changed acquired because the path during HDLM GUI startup configuration was changed when processing. the HDLM GUI was started. Action After confirming that the paths are not currently being reconfigured, click the Refresh button.
Message ID Message Text Explanation is-to-occur-for-intermittent-errormonitoring). KAPL02065-W The getting PathInformation has Details been stopped because the Updated path information could configuration of paths was not be acquired because the path changed during the processing configuration was changed after of the getting PathInformation. an Offline, Online, or Clear Data operation was performed. Action After confirming that the paths are not currently being reconfigured, click the Refresh button.
Message ID KAPL02083-I Message Text HDLM GUI is started by the user-specified JRE. aa...aa, bb...bb Explanation Details aa...aa: The user-specified JRE version (character string) bb...bb: Vendor who provided the user-specified JRE (character string) Action None. KAPL02084-E An error occurred in HDLM GUI startup processing. HDLM GUI cannot start. Details = aa...aa bb...bb cc...cc Details During the GUI startup, an error occurred that was probably not a result of a user operation. aa...
Message ID KAPL02200-I Message Text GUI information - aa...aa Explanation Details This information is required for resolving problems. aa...aa: Trace information Action None. KAPL03001 to KAPL04000 Message ID KAPL03001-I Message Text HDLM API information - aa...aa Explanation Details This information is required for resolving problems. aa...aa: Trace information Action None. KAPL03002-W HDLM API Warning - aa...aa Details This information is required for resolving problems. 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. KAPL03006-E An access to the HDLM driver causes an error. (aa...aa) Details This information is required for resolving problems. aa...
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. KAPL03999-E An unexpected error occurred. Details Conflicting versions of HDLM modules are being used.
Message ID Message Text Explanation The HDLM manager internal parameter is invalid. 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. KAPL04004-I KAPL04005-E HDLM manager will now terminate. Action Cannot connect the service control manager. Details None.
Message ID Message Text Explanation aa...aa: Option definition file name Action Check whether another program is currently using this file (for example, the file is being opened in a text editor), or whether the file has been inadvertently deleted. KAPL04009-E The option definition is invalid. Details HDLM manager could not start normally because some of the definitions in the option definition file were invalid.
Message ID KAPL04012-E Message Text Could not create a communication pipe. RC = aa...aa Explanation Details HDLM manager could not start normally because it was unable to create a pipe file, which is used in communication with HDLM commands. aa...aa: OS error code (decimal (base-10) number) Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Message ID Message Text Explanation HDLM Error Information on page 7-2. KAPL04019-E Could not collect the error information. RC = aa...aa Details An attempt to read the log information from the alert driver failed. aa...aa: API return code (decimal (base-10) number) Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
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. KAPL04024-C A critical error occurred in the HDLM manager. (aa...aa) Details This information is required for resolving problems. aa...
Message ID Message Text Explanation Install a permanent license by the expiration day. KAPL04028-E The temporary license expired. Action Install a permanent license. KAPL04029-E The emergency license expired. Action Install a permanent license. KAPL04030-E KAPL04031-E KAPL04032-C The temporary license has already expired. Action The emergency license has already expired. Action A fatal error occurred in HDLM. The system environment is invalid Details Install a permanent license.
Message ID KAPL04036-I Message Text Explanation The path health check for the Details path aa...aa was executed. aa...aa: Number of paths targeted Number of error paths = bb...bb for path health checking. bb...bb: Number of paths determined to have an error by path health checking. Action None. KAPL04037-I The path health check completed normally. Path ID = aa...aa Details All the paths that path health checking examined are fine. aa...aa: Path ID for the path examined by path health checking.
Message ID KAPL04054-I Message Text Explanation The owner controller will now be Details revised. (number of LUs = aa...aa: number of targeted LUs aa...aa) Action None. KAPL04055-I The owner controller was revised. (number of changed LUs = aa...aa) Details aa...aa: number of changed LUs Action None. KAPL04056-W The owner controller cannot be Details revised because no paths are in aa...aa: ID (serial number + iLUN) the Online status. (LU = aa...
Message ID KAPL05004-I Message Text The filtering function (aa...aa) for the HDLM driver (filter component) was initialized successfully. Explanation Details The HDLM driver (filter component) was successfully initialized for each device object. aa...aa: Device object address (hexadecimal number) Action None. KAPL05005-I The control function (aa...aa) for the HDLM driver (filter component) was initialized successfully.
Message ID Message Text Explanation Action Check whether the HDLM driver has started normally. If it has not started or contains an error, contact your HDLM vendor or the maintenance company, if there is a maintenance contract for HDLM, and report the error and detail code. KAPL05012-I The device (aa...aa) for Disk (bb...bb), Partition (cc...cc) is selected for a mounted drive. Details The device object corresponding to the disk (bb...bb: Disk sequence number (decimal (base-10) number)), partition (cc.
Message ID KAPL05032-I Message Text Explanation The path health checking for the Details path (aa...aa) completed aa...aa: Path ID (hexadecimal normally. (bb...bb,cc...cc) number) bb...bb: Disk sequence number (decimal (base-10) number) cc...cc: Degree of progress in health checking (hexadecimal number) Action None. KAPL05033-W The path health checking for the Details path (aa...aa) failed. aa...aa: Path ID (hexadecimal (bb...bb,cc...cc,dd...dd) number) bb...
Message ID Message Text maintenance company. Refer to the HDLM User's Guide for instructions how to execute the DLMgetras utility. Explanation PathID PathName DskName iLU ChaPort When a path is added to an LU, this message might appear. Note that this message is output by Windows activities, and not as a result of an error. Action Make sure that the path is correctly connected to the LU, and then recover the path.
Message ID Message Text Explanation None. KAPL07820-E The configuration does not support the simultaneous use of the load balancing and cluster support functions. Details Because this storage system does not support persistent reservations, the load balancing function cannot be used in a cluster environment. Action Update all the HDLM target storage systems to a version that supports persistent reservations.
Message ID Message Text Explanation function can also be used for this kind of LU. aa...aa: Path ID (same as PathID of view -path) (decimal (base-10) number) Action None. KAPL07824-I The owner controller of the LU connected to the path (aa...aa) was changed to (bb...bb). Details The owner controller of the LU connected to the path with the ID shown in the message was changed. aa...aa: Path ID of the changed LU. (same as PathID of view path) (Decimal number) bb...
Message ID Message Text Explanation ¢ When the Windows plug-andplay functionality deletes the SCSI device from Windows 0x00000000 is displayed. ¢ When a path error is detected by path health checking or an online operation 0x000F0000 is displayed. ¢ When a path error is detected through an I/O error The OS error code is displayed. cc...cc: Address of the filter driver in which the error occurred(character string) Action Check the path in which the error was detected.
Message ID Message Text Explanation 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. For details on what to do, see What To Do for a Path Error on page 5-4, and then switch the path shown in the message to Online. KAPL08023-I A path was recovered. PathID = aa...aa, PathName = bb...bb.cc...cc.dd...dd.ee...
Message ID Message Text Explanation 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...aa: Path ID (same as PathID of view -path) (decimal (base-10) number) Action Find the KAPL05301-E message in the event log to identify the storage system that the error was detected on and resolve the problem.
Message ID Message Text Explanation Action To return a path to the Online(D) status, resolve the path failure, and then execute the "dlnkmgr online -dfha" command. 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 remove HDLM. aa...
Message ID KAPL09005-E Message Text Explanation Could not stop the HDLM Details manager. Stop it manually, and An attempt to stop the HDLM then try the installation program manager service has failed. or the remove program again. Action Stop the HDLM manager manually, and then try the installation program or the remove program again. KAPL09006-E Could not install HDLM. Action If the installation was interrupted, incomplete files and folders might remain. Manually delete all these files and folders.
Message ID Message Text Explanation Action Remove the HDLM that has been installed on another OS on the same drive, and then restart the installation program. KAPL09019-E KAPL09020-E An attempt to cancel the registration of the bundle PP name of Hitachi Network Objectplaza Trace Library 2 failed. Remove Hitachi Network Objectplaza Trace Library 2 by referring to HDLM User's Guide section "Removing Hitachi Network Objectplaza Trace Library (HNTRLib2)".
Message ID Message Text Contact your HDLM vendor or the maintenance company if there is a maintenance contract of HDLM. Explanation During installation of HDLM, an error occurred that was probably not a result of a user operation. aa...aa: Error number (decimal (base-10) number) bb...bb: Detailed information (decimal (base-10) number) Action When Code = 13 1633: At least one SCSI disk managed by Windows does not have a hardware ID.
Message ID KAPL09080-I Message Text The temporary license has been installed. The license expires on aa...aa. Explanation Details aa...aa: Year (4 digits)/month (01-12)/day (01-31) Action Install a permanent license by the expiration day. KAPL09081-I The emergency license has been Details installed. The license expires on aa...aa: Year (4 digits)/month aa...aa. (01-12)/day (01-31) Action Install a permanent license by the expiration day. KAPL09082-W The temporary license expired.
Message ID Message Text Explanation Because the license information cannot be acquired, a license needs to be installed. Action Enter a license key when prompted by a message to do so. KAPL09090-W This operation will now be continued without updating the license. Details This operation will continue without updating the license. Action Install a permanent license at a later time. KAPL09091-E KAPL09093-I A fatal error occurred in HDLM. The system environment is invalid.
Message ID Message Text Explanation \hdlm_license or the-filethat-the-user-specified Action If a license key file exists, delete it. KAPL09118-W The license key file is invalid. File name = aa...aa Details The format of the license key file is invalid. aa...aa: Windows-installationdestination-drive-name \hdlm_license or the-filethat-the-user-specified Action Store a correct license key file in the designated directory, and then re-execute the installation program.
Message ID Message Text Explanation The file version is bb...bb is not displayed. aa...aa: File name (mpio.sys, mpspfltr.sys, or mpdev.sys) bb...bb: Version of the installed file (mpio.sys, mpspfltr.sys, or mpdev.sys) cc...cc: Version of the file (mpio.sys, mpspfltr.sys, or mpdev.sys) to be installed dd...dd: File name (mpio.sys, mpspfltr.sys, or mpdev.sys) Action To continue processing, click Next. To cancel processing, click Cancel. KAPL09128-W The entered PRSV key is invalid.
Message ID KAPL09134-E Message Text Explanation The HDLM path cannot be added Details to the Path environment The HDLM path could not be variable. added to the Path environment Refer to the Messages section of variable. the HDLM User's Guide for Action instructions to correct this Edit the Path environment problem. variable so that it stays within the following length after adding the HDLM paths.
Message ID Message Text Explanation ¢ ¢ ¢ ¢ ¢ C:\Program Files (x86)\HDVM\HBaseAgent\bin C:\Program Files (x86)\HDVM\HBaseAgent \util\bin C:\Program Files (x86)\HITACHI \DynamicLinkManager\bin C:\Program Files (x86)\HITACHI \DynamicLinkManager\lib C:\Program Files (x86)\Common Files \Hitachi However, if Hntrlib2 has already been installed, the following file paths are not added: Windows Server 2003 (x86) and Windows Server 2008 (x86) C:\Program Files\Common Files \Hitachi For Windows Server 2003 (e
Message ID Message Text Explanation while updating a license for an upgrade or re-installation of HDLM KAPL09142-E HDLM aa...aa cannot be performed. Wait a while, and then perform aa...aa again. Error Code = bb...bb Details HDLM could not be installed or removed because Hitachi Command Suite Common Agent Component is being used. aa...aa : "installation" or "remove" bb...bb : Internal code (decimal (base-10) number) Action When linkage is performed with Global Link Manager, cancel remote access.
Message ID Message Text Explanation aa...aa: installation or remove bb...bb: Version number of the installed or removed HDLM Action None. KAPL09182-W An attempt to aa...aa HDLM version bb...bb has failed. See the previous messages to resolve the problems. Details The unattended installation or remove of HDLM failed. aa...aa: install or remove bb...bb: Version number of HDLM you attempted to install or remove Action See the previous warning and error messages to resolve the problems.
Message ID Message Text Explanation ¢ In removehdlm utility for removing HDLM: None. KAPL09186-I The computer will now restart. Details ¢ In installhdlm utility for installing HDLM: After HDLM is installed, the computer will automatically restart because the restart option was specified in installhdlm.ini. ¢ In removehdlm utility for removing HDLM: After HDLM is removed, the computer will automatically restart because the -r parameter was specified.
Message ID Message Text Explanation installhdlm utility, see The installhdlm Utility for Installing HDLM on page 7-17. For details on the removehdlm utility, see The removehdlm Utility for Removing HDLM on page 7-28. KAPL09189-W The parameter contains an incorrect value. (Value = aa...aa) Details Either -f or -h must be specified as the first parameter for the installhdlm utility for installing HDLM. -s, -r, -w or -h must be specified as parameters for the removehdlm utility for removing HDLM. aa...
Message ID Message Text product version is specified. (hdlmversion = aa...aa) Explanation The specified installationinformation settings file is not supported by this version of HDLM. aa...aa: The HDLM version in which the specified installationinformation settings file was provided Action Specify the installationinformation settings file for the current version or an earlier version of HDLM, and then try again. KAPL09193-W A definition in the installation information settings file is invalid. (aa...
Message ID Message Text KAPL09196-W Some of the LUs managed by HDLM are not in a single path configuration. Explanation Details Before performing an upgrade installation or remove, reconfigure the system into a single-path configuration. Action Reconfigure the system into a single-path configuration, and then try again. KAPL09197-W The user terminated aa...aa, but Details HDLM bb...bb will continue. installhdlm.exe or removehdlm.exe was forcibly stopped by an action such as pressing Ctrl + C.
Message ID Message Text Explanation Action None. KAPL09212-E aa...aa ended abnormally. Details aa...aa: dlnkmgr Action Check the error message that was output just before this message, and then perform the action indicated in that error message. KAPL09213-W An error occurred during aa...aa Details processing. Although the aa...aa processing has ended, an error occurred during the processing. aa...
Message ID Message Text Explanation Make sure that there is enough unused capacity for the folder specified by the -w parameter. If there is not, allocate the required amount of capacity, and then retry the operation. For details about how to determine the amount of capacity that is required, see Notes on Removing HDLM on page 3-84. KAPL09222-E HDLM could not be removed. Details HDLM could not be removed.
Message ID Message Text Explanation Action Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM. KAPL09226-I An update (QFE) for MPIO has been installed. Driver version = aa...aa Only the HDLM driver will be installed, without overwriting the MPIO driver. Details If an update (QFE) for MPIO from Microsoft has been installed, the MPIO driver bundled with HDLM will not be installed. aa...aa: Version number of the installed MPIO driver Action None.
Message ID Message Text Add the search paths that were specified during the installation of Windows, and then re-install HDLM. Explanation The search paths that were specified during the installation of Windows are required for the installation of HDLM. Action Add all of the search paths that were specified during the installation of Windows into the Path system environment variable, and then install HDLM.
Message ID KAPL09259-I Message Text The HDLM aa...aa installation check has completed successfully. Explanation Details The HDLM installation check has completed successfully. aa...aa: Version of HDLM that will be installed Action None. KAPL09260-W Errors were detected during the HDLM aa...aa installation check. See the previous messages to resolve the problems. Details Errors were detected during the HDLM installation check. aa...
Message ID Message Text Explanation aa...aa: Year (4 digits)/Month (01-12)/Day (01-31) Action None. KAPL09281-I HDLM 6.3.0 or later has been installed. Only the HDLM driver will be installed, without overwriting the MPIO driver. 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.
Message ID Message Text Explanation Check whether HDLM has been correctly installed. KAPL09504-E The language environments of HDLM and the Service Pack are different. Details The Japanese SP was applied to the English edition of HDLM, or vice versa. Action Acquire the SP that has the same language as the installed HDLM, and then try again. KAPL09505-E aa...aa cannot be applied to the installed bb...bb. Details aa...aa: the version of HDLM or SP currently being installed bb...
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. KAPL10017-W You lack privileges for executing Details the utility for collecting HDLM The DLMgetras utility for error information. collecting HDLM error information must be executed by a user who is a member of the Administrators group.
Message ID Message Text KAPL10031-W The entered value is invalid. Continue operation ? [y/n]: Explanation Details A value other than y or n has been entered for a [y/n] request. Enter y or n. Action Enter y or n. KAPL10032-W The entered value is invalid. The Details utility for collecting HDLM error Processing of the DLMgetras information stops. utility for collecting HDLM error information will terminate because an invalid response was sent three times in a row to a request.
Message ID KAPL10043-I Message Text Error information is being collected. (aa...aa%) Explanation Details aa...aa: What percentage of all the information to be collected is log information Action None. KAPL10044-W There is insufficient disk space. Details The DLMgetras utility for collecting HDLM error information execution will now stop because the available disk capacity has decreased to less than 50 MB. Action Re-execute in an environment that has at least 50 MB of free disk capacity.
Message ID Message Text Explanation Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL10080-I Data for maintenance: aa...aa bb...bb cc...cc dd...dd Details aa...aa: Maintenance information bb...bb: Error number of the Windows API (hexadecimal number) cc...cc and dd...dd: Fixed to 0 (hexadecimal number) Action None KAPL10081-I Data for maintenance: aa...aa bb...bb cc...cc dd...dd Details aa...aa: Maintenance information bb...
Message ID Message Text Explanation aa...aa: Specified parameter (character string) Action Execute the dlmpr utility for clearing HDLM persistent reservation with the -h parameter to check the parameters that can be specified, and then retry. For details on the dlmpr utility, see The dlmpr Utility for Clearing HDLM Persistent Reservations on page 7-10. KAPL10648-E An internal error occurred in the Details dlmpr utility. Error Code = aa...aa: Error number (character aa...
Message ID Message Text Explanation aa...aa: The path ID (decimal (base-10) number) Action Enter y to execute clearing, or n to cancel. KAPL10657-I If you continue this process, the Details reservation of the LU you We recommend that you report specified will be cleared. Please the effects of using the utility to confirm that no other servers the user for confirmation. are accessing this LU. Action To clear the LU reservation, enter y. Enter n to cancel.
Message ID Message Text Explanation Terminate unnecessary applications, and then retry. If the problem persists, restart the host, and then retry. Alternatively, in dlmpr.exe, specify only the connected LUs for which you want to clear the persistent reservation information. KAPL10663-W The input value is invalid. Specify the PathID of the LU for you want to clear persistent reservation information. (To cancel: press the x key): Action KAPL10664-E Details An attempt to acquire Inquiry data failed.
Message ID Message Text Explanation - The cluster system service and the driver are running. KAPL10668-E An attempt to open a device failed. DeviceName = aa...aa Details aa...aa: Device name Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL10669-W The utility for clearing HDLM persistent reservation (dlmpr) cannot be executed because HDLM is installed.
Message ID Message Text Explanation None. KAPL11902-I aa...aa has started. PathID = bb...bb Details The operation has started on the host. aa...aa: Operation (character string) ¢ Online ¢ Offline bb...bb: The Path ID of the target path (decimal number) Action None. KAPL11903-I aa...aa has completed normally. Details The operation has completed normally on the host. aa...
Message ID Message Text Explanation aa...aa: Operation (character string) ¢ Get Path Information ¢ Get Option Information ¢ Set Option Information ¢ Clear Data ¢ Get HDLM Driver Status ¢ Get HDLM Manager Status ¢ Get HDLM Alert Driver Status ¢ Online ¢ Offline ¢ Get SNMP Trap Information ¢ Set SNMP Trap Information ¢ Set LU Load Balance ¢ Get Path Status Log Information ¢ Add Path Information ¢ Delete Path Information ¢ Set Storage Identification Information bb...
Message ID Message Text Explanation for Collecting HDLM Error Information on page 7-2. KAPL11906-I GUI information - aa...aa Details This information is required for resolving problems. aa...aa: Trace information (character string) Action None. KAPL11907-I XML reception - aa...aa Details This information is required for resolving problems. aa...aa: XML information (character string) Action None. KAPL11908-I XML transmission - aa...aa Details This information is required for resolving problems.
Message ID Message Text Explanation an HDLM Persistent Reservation Key on page 7-13. KAPL12103-W The parameter value is invalid. (value = aa...aa) Details The first parameter must be -r, v, or -h. When the -r parameter is specified, the second parameter must be the -s parameter or must have 16 digits and be hexadecimal. When the -h parameter is specified, values other than the -h parameter cannot be entered for the parameter. aa...
Message ID KAPL12106-I Message Text An attempt to register the PRSV key was successful. (PRSV key = aa...aa) Explanation 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...aa: Registered PRSV key (character string) 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 contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL12112-E An error occurred during internal processing of the utility for registering the HDLM persistent reservation key. Details = aa...aa, bb...bb Details During processing of the dlmprsvkey utility for registering an HDLM persistent reservation key, an error occurred that was probably not a result of a user operation. aa...aa: Error detail bb...
Message ID Message Text Explanation \HDLMdsm\Parameters \PRSVKeyString. Action Execute the dlmprsvkey utility for registering an HDLM persistent reservation key to register a valid PRSV key. KAPL12115-E KAPL12116-I An attempt to generate the PRSV key has failed. Action The registered PRSV key will now be displayed. (PRSV key = aa...aa) Details Specify the -r parameter for the PRSV key, and then try again.
Message ID Message Text Explanation Action None. KAPL12119-E Trace data for maintenance: aa...aa bb...bb cc...cc dd...dd ee...ee Details This is the trace message when the -r parameter is specified and an error occurs before the PRSV key is generated, or when the -v parameter is specified and an error occurs before the PRSV key can be acquired. aa...aa: Maintenance information 1 (hexadecimal number) bb...bb: Maintenance information 2 (hexadecimal number) cc...
Message ID Message Text Explanation The Windows Management Instrumentation service might not be working. This message might also be output when the WMI repository is corrupted. aa...aa: API name (character string) bb...bb: Error code (decimal (base-10) number) Action Check whether the Windows Management Instrumentation service is working. If not, start it.
Message ID Message Text Explanation Action None. KAPL12402-W iLU (aa...aa) is in a multi-path configuration. PathID = bb...bb[,cc...cc]... Details The LU for the LU number in the message is not in a single path configuration. aa...aa: LU number bb...bb,cc...cc: Path ID of the path connected to the LU Action Before performing remove, upgrade installation, or reinstallation, change all the LUs to a single path configuration. KAPL12403-W A necessary parameter has not been specified.
Message ID Message Text Explanation ¢ Error code: 22 Check whether HDLM has been installed correctly. If it has, contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. ¢ Error code: Others Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL13001 to KAPL14000 Message ID Message Text Explanation KAPL13601-W The audit log configuration file Details does not exist.
Message ID Message Text KAPL13604-W An error occurred during processing to read the audit log configuration file. Explanation Details An internal error occurred during processing to read the audit log configuration file. Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL13605-W An error occurred during processing to output the audit log configuration file. Details An internal parameter error occurred during output of the audit log data.
Message ID Message Text KAPL13804-W Too many parameters have been specified. Explanation Details Three or more parameters have been specified. Action Check the parameters for the dlmhostinfo utility for confirming HDLM installation information, and then re-execute the utility. KAPL13805-W At least one parameter is invalid. Details At least one of the specified parameters is invalid.
Message ID Message Text Explanation Action Make sure that the installation information file does not meet any of the above conditions. KAPL13809-E An internal error occurred in the Details dlmhostinfo utility for confirming An error, which does not seem to HDLM installation information. be a result of a user action, Code = aa...aa, bb...bb occurred during processing of the dlmhostinfo utility. aa...aa: Error code (decimal number) bb...
Message ID Message Text Explanation displayed. Command Line = aa...aa KAPL15035-W An attempt to display the status Details that indicates whether paths are aa...aa: Name of the utility that in an individual or multiple path the user executed configuration has failed. Command Line = aa...aa KAPL15060-I KAPL15061-I KAPL15101-I DLMgetras was invoked. Command Line = aa...aa Details DLMgetras successfully executed. Command Line = aa...aa Details Clear operation was completed successfully.
Message ID KAPL15109-I Message Text Information about HDLMmanagement targets was successfully displayed. Command Line = aa...aa Explanation Details aa...aa: Command that the user executed KAPL15110-W An attempt to display information about HDLMmanagement targets has failed. Command Line = aa...aa Details KAPL15111-W The HDLM command was started or stopped by the user who does not have the authority. Command Line = aa...aa Details KAPL15116-I Details bb...bb path(s) were successfully placed aa...aa.
Message ID Message Text Explanation KAPL15206-W aa...aa has failed. Details aa...aa: Refresh, Clear Data, Export CSV, Get Option Information, or Set Option Information KAPL15207-I aa...aa path(s) were successfully placed bb...bb. cc...cc path(s) could not be placed bb...bb. Details 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..
Return Code Explanation Check whether a path between the host and the storage system is connected. If a path is connected, check whether HDLM is configured correctly. 1004 Details Memory required for HDLM internal processing could not be allocated. Action 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.
Return Code Explanation 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. 1021 Details MSCS is not installed on the host.
Return Code Explanation Refresh the host information, check the path status, and then perform the operation again. 1027 Details The error monitoring interval and the number of times that the error needs to occur are conflicting with the automatic failback-checking interval. Action 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).
Return Code Explanation see The DLMgetras Utility for Collecting HDLM Error Information on page 7-2. 1037 Details A parameter is invalid. Action Refresh the host information, and then perform the operation again. If the same error occurs again, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or maintenance company if you have a maintenance contract for HDLM.
Return Code 1046 Explanation Details A parameter is invalid. Action Refresh the host information, and then perform the operation again. If the same error occurs again, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or maintenance company if 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.
Message ID Type Source Category Event ID User KAPL04027-I Information DLMManager None 16411 N/A KAPL04028-E Error DLMManager None 16412 N/A KAPL04029-E Error DLMManager None 16413 N/A KAPL04030-E Error DLMManager None 16414 N/A KAPL04031-E Error DLMManager None 16415 N/A KAPL04032-C Error DLMManager None 16416 N/A KAPL04033-W Warning DLMManager None 16417 N/A KAPL04034-E Error DLMManager None 16418 N/A KAPL05008-E Error DLMManager None 20488 N/A KA
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 (for Windows®) User Guide
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 (for Windows®) User Guide U V W X Y Z
GUI Graphical User Interface GUID Globally Unique Identifier H HBA Host Bus Adapter HDev Host Device HLU Host Logical Unit HTTP Hypertext Transfer Protocol I I/O Input/Output IP Internet Protocol iSCSI Internet Small Computer System Interface L LAN Local Area Network LDAP Lightweight Directory Access Protocol LDEV Logical Device # A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Acronyms-3 Hitachi Dynamic Link Manager (for Windows®) User Guide
LU Logical Unit LUN Logical Unit Number M MPIO Multipath I/O MVS Multiple Virtual Storage N NIC Network Interface Card NTP Network Time Protocol O OS Operating System P P Port PRSV Persistent Reserve Q QFE Quick Fix Engineering # A B C D E F G H I J K L M N O P Q R S T Acronyms-4 Hitachi Dynamic Link Manager (for Windows®) User Guide U V W X Y Z
R RADIUS Remote Authentication Dial in User Service S SAN Storage Area Network SCSI Small Computer System Interface SLPR Storage Logical Partition SMTP Simple Mail Transfer Protocol SNMP Simple Network Management Protocol SP Service Pack SSL Secure Sockets Layer SVP Service Processor W WMI Windows Management Instrumentation WWN World Wide Name # A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Acronyms-5 Hitachi Dynamic Link Manager (for Windows®) User Guide
# 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 (for Windows®) User Guide U V W X Y Z
Glossary This glossary explains the terms used in this manual. A automatic failback A function for checking the status of paths at regular intervals, and automatically placing the status of a path recovered from an error into the Online status. If a path with an Offline(E) or Online(E) status recovers from an error, an automatic failback will place the path Online.
cluster A system of connecting multiple hosts with the same OS or platform (essentially, an environment in which the same application can run) and treating them as one system. D Dev A logical division of an LU that HDLM controls and operates. A Dev is equivalent to a partition in Windows. In Windows, each LU has only one Dev. Each Dev has a Dev number. (See also: Dev number) Dev number A Dev number (the DNum column) in the configuration list in HDLM. 0 is displayed as the number indicating the entire LU.
FC-SAN (Fibre Channel - Storage Area Network) A SAN using Fibre Channel. H HAM environment An environment in which volume pairs that are synchronized between two storage systems are created by HAM (High Availability Manager), and hosts are configured to recognize these volumes as one volume. An HAM environment consists of the primary volume (P-VOL) in the primary site and the secondary volume (S-VOL) in the secondary site.
host LU number A number assigned to a host LU. The host LU number is part of a path name. (See also: host LU, path name) I intermittent error An error that occurs irregularly due to, for example, a loose cable connection. IP-SAN (Internet Protocol - Storage Area Network) A data transfer network that connects hosts and storage systems by using the iSCSI standard. L LDEV (Logical Device) A combination of the storage system's product name, serial number, and an internal LU.
Non-owner controllers exist only in the Thunder 9500V series, or Hitachi AMS/WMS series. (See also: owner controller, non-owner path) non-owner path A path that passes through a non-owner controller. Non-owner paths exist only in the Thunder 9500V series, or Hitachi AMS/WMS series. (See also: owner path, non-owner controller) O owner controller A controller that has been set as an owner controller for an LU. Owner controllers are only in the Thunder 9500V series, or Hitachi AMS/WMS series.
path name The path name consisting of the following four elements, separated by periods: - Host port number (hexadecimal number) - Bus number (hexadecimal number) - Target ID (hexadecimal number) - Host LU number (hexadecimal number) A path name is used to identify a path. (See also: host LU number) persistent reservation Similar to reservations, persistent reservations enable a server to declare that it has exclusive rights to use an LU, and prevents other servers from accessing that LU.
SLPR (Storage Logical Partition) A function supported by Hitachi USP series, Universal Storage Platform V/VM series, Virtual Storage Platform series, and VSP G1000 series, for logically splitting up a storage system. This function splits up the resources, such as ports, CLPR, and volumes, in the storage system, so that the user can manage each resource independently.
# A B C D E F G H I J K L M N O P Q R S T Glossary-8 Hitachi Dynamic Link Manager (for Windows®) User Guide U V W X Y Z
Index A buffer size 3-82 bus number 6-58 command format 6-2 overview 6-2 command device 2-3, 6-60 HDLM command (dlnkmgr) delete 6-77 command of HDLM (dlnkmgr) clear 6-3 help 6-4 offline 6-6 online 6-11 set 6-16 view 6-33 configuration of HDLM system configuration of HDLM system using FC-SAN 2-4 core logic component 2-10 Critical 2-36 C D CHA 2-4, 2-6 CHA (Channel Adapter) Glossary-1 channel adapter 2-3, 2-5 checking path information using Windows administrative tool (Performance) 4-13 clear 6-3 CLPR(Ca
summary of path information 6-34 Distributing a Load Using Load Balancing dlmchkpath 7-14 DLMgetras 5-7, 5-8, 7-2 dlmhostinfo 7-16 dlmpr 7-10 dlmprsvkey 7-13 dlnkmgr 6-1 DNum 5-3 2-11 driver level HDLM and MPIO drivers 2-10 dynamic I/O path control 3-75 dynamic reconfiguration Glossary-2 E EMC CX series cluster software 3-8 EMC DMX series cluster software 3-8 dlnkmgr view -lu -c 6-66 EMC DMX series and CX series dlnkmgr view -lu 6-61 dlnkmgr view -path -c 6-51 EMC DMX series, CX series, and HP EVA series
narrowing down 5-6 HBA 2-4 notes on HBA and HBA drivers 3-15 HBA (Host Bus Adapter) Glossary-3 HDev 2-8 HDevName 5-3 HDLM features 1-2 functions 2-1 installing 3-26 new installation (on Windows Server 2003) 3-29 new installation (on Windows Server 2008 and Windows Server 2012) 3-52 notes on versions 3-16 overview 1-1 program information 6-35 removal 3-84 setup 3-71 HDLM alert driver 2-10, Glossary-3 HDLM command 2-9 HDLM Core components 2-10 HDLM driver 2-10, Glossary-3 driver level 2-10 HDLM environment cr
log collection level values 6-19 logical unit 2-3, 2-5 logical unit ID 6-58 logs HDLM output to Windows event logs LU 2-4, 2-6, 4-16 configuration 2-7 LU (Logical Unit) Glossary-4 LU configuration recognized by the host LUN 6-58 8-117 2-8 M manual path switching 2-19 message examining 5-7 format and meaning of ID 8-3 terms that appear 8-3 terms used for explanation 8-3 message element DNum 5-3 ErrorCode 5-3 PathID 5-3 PathName 5-3 Message level 8-3 Messages 8-1 migrating from HDLM 5.
P P 2-4, 2-6 path 2-3, 2-5, Glossary-5 checking the configuration 3-70 deleting dynamically 6-77 path error handling 5-4 Path Health Checking 2-31 path health checking 1-3, 2-31, 6-21, Glossary-5 path information obtaining 5-5 path name Glossary-6 path status transition 2-20 path status transitions 2-23 path switching automatically 2-17 manually 2-19 PathID 5-3 PathName 5-3 paths to which load balancing is applied 2-13 Performance 4-13 Performance Monitor 4-13 Performing Failovers and Failbacks Using Path S
using Windows administrative tool (Performance) checking path information 4-13 utilities for checking HDLM installation information 7-16 for checking HDLM paths 7-14 for clearing HDLM persistent reservation 7-10 for collecting HDLM error information 7-2 for registering a HDLM persistent reservation key 7-13 for removing HDLM 7-28 installing HDLM 7-17 overview 7-2 utility for removing HDLM 7-28 V VCS 3-8, 3-9, 3-10, 3-88 vendor ID 6-52, 6-56, 6-57 view 6-33 viewing GUI Help 4-4 W Warning 2-36 what is HDLM?
Hitachi Dynamic Link Manager (for Windows®) User Guide
Hitachi Data Systems Corporate Headquarters 2845 Lafayette Street Santa Clara, California 95050-2639 U.S.A. www.hds.com Regional Contact Information Americas +1 408 970 1000 info@hds.com Europe, Middle East, and Africa +44 (0)1753 618000 info.emea@hds.com Asia Pacific +852 3189 7900 hds.marketing.apac@hds.
