Hitachi Dynamic Link Manager Software User's Guide (for Windows(R)) 3020-3-P35-50(E)
Relevant program products Hitachi Dynamic Link Manager version 6.6 For details about the supported OSs, see the HDLM Release Notes. Trademarks AIX is a trademark of International Business Machines Corporation in the United States, other countries, or both. EMC, Symmetrix, Symmetrix DMX, and CLARiiON are trademarks of EMC Corporation. HP-UX is a product name of Hewlett-Packard Company. HP StorageWorks is a trademark of Hewlett-Packard Company.
Summary of Amendments The following table lists changes in this manual (3020-3-P35-50(E)) and product changes related to this manual. Changes Location in this manual Virtual Storage Platform has been added as a storage system supported by HDLM. 1.1, 2.6, 2.6.1(2), 2.7.1(1), 2.7.1(2), 2.7.2, 3.1.2(1), 3.1.3, 3.4.5, 3.7.2(1), 4.1.4, 4.7.2(2), 6.4.2(1), 6.5.2(1), 6.6.2(1), 6.7.2(2), 6.7.2(3), 6.7.
Preface This manual describes the functions and use of the following program products. • Hitachi Dynamic Link Manager Intended readers This manual is intended for system administrators who use Hitachi Dynamic Link Manager (HDLM) to operate and manage storage systems.
problems that you might encounter. 6. Command Reference Chapter 6 describes all the HDLM commands. 7. Utility Reference Chapter 7 describes the HDLM utilities. 8. Messages Chapter 8 provides information for all the possible messages that could be output by HDLM. The chapter also explains what to do in response to each message. A. Functional Differences Between Versions of HDLM Appendix A explains the differences between HDLM versions. B. Glossary This glossary explains terms used in this manual.
Full name or meaning Abbreviation Device Manager Agent included in Hitachi Device Manager Device Manager Agent EMC CLARiiON CX series EMC CX series EMC Symmetrix DMX series EMC DMX series Hitachi Global Link Manager Global Link Manager Hitachi Dynamic Link Manager HDLM A generic term for: • Hitachi Adaptable Modular Storage 1000 • Hitachi Adaptable Modular Storage 500 • Hitachi Adaptable Modular Storage 200 Hitachi AMS A generic term for: • Hitachi Adaptable Modular Storage 1000 • Hitachi Adap
Full name or meaning Abbreviation HP StorageWorks XP128 Disk Array HP XP128 HP StorageWorks XP1024 Disk Array HP XP1024 HP StorageWorks XP10000 Disk Array HP XP10000 HP StorageWorks XP12000 Disk Array HP XP12000 HP StorageWorks XP20000 Disk Array HP XP20000 HP StorageWorks XP24000 Disk Array HP XP24000 Hitachi Virtualization Manager HVM A generic term for: • Microsoft(R) Internet Explorer(R) • Windows(R) Internet Explorer(R) Internet Explorer JavaTM 2 Runtime Environment, Standard Edition
Full name or meaning Abbreviation A generic term for: • AIX • HP-UX • Linux • Solaris UNIX This abbreviation is used when it is not necessary to distinguish the following products: • Hitachi Universal Storage Platform V • Hitachi Universal Storage Platform V/VM • HP XP20000 • HP XP24000 Universal Storage Platform V/VM A generic term for: • Hitachi Virtual Storage Platform • HP StorageWorks P9500 Disk Array Virtual Storage Platform Veritas Cluster Server VCS Volume Manager, which is included in Ver
Full name or meaning A generic term for: • Microsoft(R) Windows Server(R) 2003, Datacenter x64 Edition • Microsoft(R) Windows Server(R) 2003, Enterprise x64 Edition • Microsoft(R) Windows Server(R) 2003, Standard x64 Edition • Microsoft(R) Windows Server(R) 2003 R2, Datacenter x64 Edition • Microsoft(R) Windows Server(R) 2003 R2, Enterprise x64 Edition • Microsoft(R) Windows Server(R) 2003 R2, Standard x64 Edition • Microsoft(R) Windows(R) Storage Server 2003, Enterprise x64 Edition • Microsoft(R) Windows(R
Full name or meaning A generic term for: • Microsoft(R) Windows Server(R) 2003, Standard Edition • Microsoft(R) Windows Server(R) 2003, Web Edition • Microsoft(R) Windows Server(R) 2003, Datacenter Edition • Microsoft(R) Windows Server(R) 2003, Enterprise Edition • Microsoft(R) Windows Server(R) 2003 R2, Datacenter Edition • Microsoft(R) Windows Server(R) 2003 R2, Enterprise Edition • Microsoft(R) Windows Server(R) 2003 R2, Standard Edition • Microsoft(R) Windows(R) Storage Server 2003 R2, Enterprise Editio
Full name or meaning Abbreviation A generic term for: • Microsoft(R) Windows Server(R) 2003 R2, Datacenter Edition • Microsoft(R) Windows Server(R) 2003 R2, Datacenter x64 Edition • Microsoft(R) Windows Server(R) 2003 R2, Enterprise Edition • Microsoft(R) Windows Server(R) 2003 R2, Enterprise x64 Edition • Microsoft(R) Windows Server(R) 2003 R2, Standard Edition • Microsoft(R) Windows Server(R) 2003 R2, Standard x64 Edition • Microsoft(R) Windows(R) Storage Server 2003 R2, Enterprise Edition • Microsoft(R
Full name or meaning Abbreviation A generic term for: • Microsoft(R) Windows Server(R) 2008 Datacenter • Microsoft(R) Windows Server(R) 2008 Datacenter without Hyper-V(TM) • Microsoft(R) Windows Server(R) 2008 Enterprise • Microsoft(R) Windows Server(R) 2008 Enterprise without Hyper-V(TM) • Microsoft(R) Windows Server(R) 2008 Standard • Microsoft(R) Windows Server(R) 2008 Standard without Hyper-V(TM) Windows Server 2008(x64) A generic term for: • Microsoft(R) Windows Server(R) 2008 Datacenter 32-bit • M
Abbreviation x Full name or meaning CPU Central Processing Unit CSV Comma Separated Value CU Control Unit DBMS Database Management System DEP Data Execution Prevention Dev Device DNS Domain Name Server FC Fibre Channel FC-SP Fibre Channel Security Protocol FO Failover GMT Greenwich Mean Time GPT GUID Partition Table GUI Graphical User Interface GUID Globally Unique Identifier HBA Host Bus Adapter HDev Host Device HLU Host Logical Unit HTTP Hypertext Transfer Protocol I
Abbreviation Full name or meaning MPIO Multipath I/O MVS Multiple Virtual Storage NAS Network Attached Storage NIC Network Interface Card NTP Network Time Protocol OS Operating System P Port PRSV Persistent Reserve QFE Quick Fix Engineering RADIUS Remote Authentication Dial in User Service 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
Conventions: Fonts and symbols Font and symbol conventions are classified as: • General font conventions • Conventions in syntax explanations These conventions are described below. General font conventions The following table lists the general font conventions: Font xii Convention Bold Bold type indicates text on a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels.
Font Convention Code font A code font indicates text that the user enters without change, or text (such as messages) output by the system. For example: • At the prompt, enter dir. • Use the send command to send mail. • The following message is displayed: The password is incorrect. Code examples and messages appear as follows (though there may be some exceptions, such as when the code is part of a diagram): MakeDatabase ... StoreDatabase temp DB32 In examples of coding, an ellipsis (...
Example font or symbol Convention A prompt on a command-execution window. > Conventions: KB, MB, GB, and TB This manual uses the following conventions: • 1 KB (kilobyte) is 1,024 bytes. • 1 MB (megabyte) is 1,0242 bytes. • 1 GB (gigabyte) is 1,0243 bytes. • 1 TB (terabyte) is 1,0244 bytes. Conventions: Using this program in a non-English Windows system This manual uses terms from the English version of Windows.
Contents Preface i Intended readers .........................................................................................................i Organization of this manual .......................................................................................i Related Publications..................................................................................................ii Conventions: Abbreviations ......................................................................................
2.10.2 Deleting an LU Dynamically...................................................................... 42 2.11 Error Management ................................................................................................. 43 2.11.1 Types of Collected Logs ............................................................................. 45 2.11.2 Filtering of Error Information..................................................................... 47 2.11.
3.7 Setting Up HDLM ..................................................................................................142 3.7.1 Checking the Current Settings.....................................................................142 3.7.2 Setting Up the HDLM Functions ................................................................143 3.7.3 Checking the Updated Settings ...................................................................152 3.8 Setting Up Integrated Traces ......................................
5. Troubleshooting 195 5.1 Information Collected by the DLMgetras Utility for Collecting HDLM Error Information ........................................................................................................... 196 5.2 Checking Error Information in Messages .............................................................. 197 5.3 What To Do for a Path Error.................................................................................. 200 5.3.1 Examining the Messages .............................
7.3 7.4 7.5 7.6 7.7 7.8 7.2.2 Parameters ...................................................................................................286 7.2.3 List of Collected Error Information ............................................................287 The dlmpr Utility for Clearing HDLM Persistent Reservations ...........................294 7.3.1 Format .........................................................................................................294 7.3.2 Parameters ..............................
Appendixes 449 A. Functional Differences Between Versions of HDLM ............................................. 450 A.1 Functional Differences Between Version 6.6 or Later and Versions Earlier Than 6.6 ................................................................................................................. 450 A.2 Functional Differences Between Version 6.2 or Later and Versions Earlier Than 6.2 ........................................................................................................
Chapter 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. 1.1 What is HDLM? 1.
1. Overview of HDLM 1.1 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.
1.
1. Overview of HDLM 1.2 HDLM Features HDLM features include the following: The ability to distribute a load across multiple paths. This is also known as load balancing. When a host is connected to a storage system via multiple paths, HDLM can distribute the load across all the paths. This prevents one, loaded down path from affecting the processing speed of the entire system. For details on load balancing, see 2.6 Distributing a Load Using Load Balancing.
1. Overview of HDLM HDLM can utilize both configuration-diagrams and the list format to display information about all the paths that exist between hosts and Hitachi storage systems. You can use the GUI to easily change the status of any given path, and to set up a proper operating environment. For details on the HDLM GUI, see the HDLM GUI Help.
Chapter 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. 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.
2. HDLM Functions 2.1 Devices Managed by HDLM Below is a list of devices that can or cannot be managed by HDLM. The devices that can be managed by HDLM are called HDLM management-target devices. HDLM management-target devices: The following devices are from the storage systems listed in Section 1.
2. HDLM Functions 2.2 System Configuration HDLM is available in two SAN environment types: FC-SAN and IP-SAN. Note that the EMC DMX series, EMC CX series, and HP EVA series can only be used in an FC-SAN environment. 2.2.1 System Configuration Using an FC-SAN In an FC-SAN, fiber cables connect hosts to storage systems. The cable port on the host is called a host bus adapter (HBA). The cable port on the storage system is called a port (P) on a channel adapter (CHA).
2. HDLM Functions Figure 2-1: Configuration of an HDLM System When Using an FC-SAN Table 2-1: HDLM System Components When Using an FC-SAN lists the HDLM system components when using an FC-SAN. Table 2-1: HDLM System Components When Using an FC-SAN Components Description HBA A host bus adapter. This serves as a cable port on the host. FC-SAN A dedicated network that is used for the transfer of data between hosts and storage systems CHA A channel adapter P A port on a CHA.
2. HDLM Functions 2.2.2 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.
2. HDLM Functions Figure 2-3: Configuration of an IP-SAN System When Using iSCSI Software and an NIC Table 2-2: HDLM System Components When Using an IP-SAN 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.
2. HDLM Functions Components Description P A port on a CHA. This serves as a cable port on a storage system. LU A logical unit with which the host can perform I/O operations. This unit can be accessed from the network. Dev A logical area (a partition) in an LU Path A route that connects a host to a Dev in an LU (1) 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.
2. HDLM Functions 2.3 LU Configuration After you have properly installed HDLM, the LU configuration will change as follows: Before the installation of HDLM: In the Windows' Disk Management window of a host, one SCSI device is displayed as multiple LUs, each of which corresponds to one path. In other words, the number of LUs in a storage system appeared to be the same as the number of paths connected to the various SCSI devices.
2. HDLM Functions Figure 2-4: LU Configuration Recognized by the Host After the Installation of HDLM Table 2-3: Components Recognized by the Host lists the components recognized by the host. Table 2-3: Components Recognized by the Host Components Description HLU An LU that the host recognizes via the HDLM driver. This type of LU is called a host LU. Regardless of how many paths are connected to it, only one host LU is recognized for each LU in the storage system.
2. HDLM Functions 2.4 Program Configuration HDLM is actually a combination of several programs. Because each program corresponds to a specific HDLM operation, it is important to understand the name and purpose of each program, along with how they are all interrelated. Figure 2-5: Configuration of the HDLM Programs shows the configuration of the HDLM programs. Figure 2-5: Configuration of the HDLM Programs Table 2-4: Functions of HDLM Programs lists and describes the functions of these programs.
2.
2. HDLM Functions 2.5 Driver Levels of the HDLM and MPIO Drivers The HDLM and MPIO drivers are positioned at a higher driver level than the SCSI drivers. In other words, applications that are accessing LUs in storage systems will first use the HDLM and MPIO drivers, and then use the SCSI drivers, in order to access the LUs. Figure 2-6: Driver Levels of the HDLM and MPIO Drivers shows the driver levels of the HDLM and MPIO drivers.
2. HDLM Functions 2.6 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.
2. HDLM Functions Figure 2-7: Flow of I/O Data When the Load Balancing Function Is Not Used When the load balancing function is not used, I/O operations converge onto a single path (A). The load on that one path (A) will cause a bottleneck, which might cause problems with system performance.
2. HDLM Functions 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. 2.6.1 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.
2. HDLM Functions have different owner controllers, different LUs might also have different owner paths. A non-owner path is a path that passes through a CHA other than the owner controller. This type of CHA is also known as a non-owner controller. An owner path is usually used in preference to a non-owner path. In order to prevent system performance from slowing down, HDLM does not perform load balancing between owner paths and non-owner paths.
2. HDLM Functions (2) When Using the Lightning 9900 Series, Lightning 9900V Series, Hitachi USP, Universal Storage Platform V/VM, Virtual Storage Platform, Hitachi AMS2000 Series, or Hitachi SMS All online paths are owner paths. Therefore, for the example in Figure 2-8: Flow of I/O Data When the Load Balancing Function Is Used, the load is balanced among the four paths A, B, C, and D. If one of the paths were to become unusable, the load would be balanced among the three, remaining paths. 2.6.
2. HDLM Functions If the data is sequential, the path used will be the one to which the data of the I/O that was issued immediately beforehand was distributed. However, if a specified number of I/Os has been issued to a path, processing switches to the next path. 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.
2. HDLM Functions You can specify the load balancing function from the Options window of the HDLM GUI or by using the dlnkmgr command's set operation. For details on how to use the window components, see the HDLM GUI Help. For details on the set operation, see 6.6 set (Sets Up the Operating Environment).
2. HDLM Functions 2.7 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.
2. HDLM Functions Error A high-risk error, which can be avoided by performing a failover or some other countermeasure. For details on error levels, see 2.11.2 Filtering of Error Information. When 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.
2. HDLM Functions Figure 2-10: Path Switching (2) 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.
2. HDLM Functions When the Lightning 9900 series, Lightning 9900V series, Hitachi USP, Universal Storage Platform V/VM, Virtual Storage Platform, Hitachi AMS2000 series, or Hitachi SMS is being used, all the paths are owner paths. As a result, if the path that was previously used recovers from an error, and then HDLM automatically places the recovered path online, the path that is currently being used will continue to be used (as opposed to switching over to the path that was just recovered).
2. HDLM Functions Hitachi USP, Universal Storage Platform V/VM, Virtual Storage Platform, Hitachi AMS2000 series, or Hitachi SMS is being used, all the paths that access the same LU as the path that is currently being used are candidates for the switching destination path. By changing the path status to online in the Path Management window, or by executing the online operation, an offline path can be placed online. For details on the online operation, see 6.5 online (Places Paths Online).
2. HDLM Functions Offline(C). The (P) means pending, which indicates that the operation to take the path offline is in the waiting-to-execute status (i.e. a request has been made). • Online(E) An error has occurred on the path, but none of the other paths that access the same LU are in the Online status. If none of the paths accessing a particular LU are in the Online status, one of the paths is changed to the Online(E) status. This ensures that the LU can be accessed through at least one path.
2. HDLM Functions The status indicating that an I/O could not be issued on a given path, because an error occurred on the path. The (E) means error. • Offline(P) This status occurs in a cluster configuration only. The Offline(P) status indicates that the user has requested an offline operation on an Offline(E) path that is connected to an LU that is currently performing reserve processing.
2. HDLM Functions 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).
2. HDLM Functions the Online(E) paths have been deleted. • The Offline(E) paths are assumed to have had an intermittent error, and are thus excluded from automatic failbacks. • The SCSI devices are connected to the Offline(E) paths. 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. This ensures that the LU can always be accessed by at least one path. For details on the offline operation, see 6.
2. HDLM Functions 2.8 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. This is because the automatic failback operation is being performed repeatedly (because the intermittent error keeps occurring).
2. HDLM Functions 2.8.3 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.
2. HDLM Functions (2) 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.
2. HDLM Functions (3) When the Conditions for an Intermittent Error Are Changed During Error Monitoring When the conditions for an intermittent error are changed during error monitoring, the number of errors and the amount of time that has passed 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.
2. HDLM Functions check the IEP item displayed when the dlnkmgr command's view -path operation is executed with the -iem parameter specified, or the Intermittent Error Path item specified in the Path List view of the HDLM GUI. If 0 or greater is displayed in the Intermittent Error Path item, then intermittent error monitoring is being performed.
2. HDLM Functions User operation Number of errors and time passed since error monitoring started Information about paths not subject to automatic failback Restarting the HDLM manager Reset#4 Inherited Restarting the host Reset Reset #1 When you turn the intermittent error monitoring function off, information about paths not subject to automatic failback will be reset.
2. HDLM Functions 2.9 Detecting Errors by Using Path Health Checking HDLM can check the status of paths for which I/O operations are not being performed at regular intervals. This function is called path health checking. Without path health checking, an error cannot be detected unless an I/O operation is performed, because the system only checks the status of a path when an I/O operation is performed.
2. HDLM Functions 2.10 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. This is called the dynamic re-configuration function. For details on the dynamic re-configuration function, see 4.7.1 Setting Up an Added LU and Path as an HDLM Management-target. 2.10.
2. HDLM Functions 2.11 Error Management For troubleshooting purposes, HDLM collects information and stores it into log files. The error information to be collected can be filtered out by error level, and then stored into the log files. Figure 2-15: Flow of Data When Collecting Error Information shows the flow of data when collecting error information.
2. HDLM Functions Figure 2-15: Flow of Data When Collecting Error Information Logs might be collected in layers below HDLM, such as for the SCSI driver. For more details, see the Windows documentation.
2. HDLM Functions 2.11.1 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. Information regarding a Windows system being down is output to a system memory dump file. A system memory dump file is a file to which the system memory data is output when a Windows system is down.
2. HDLM Functions Log name Description Error log Error information is collected for the user-defined level. By default, HDLM collects all error information. Output destination HDLM Manager logs: \Program Files\HITACHI\DynamicLinkM anager\log\dlmmgr[1-16].lo g#2 HDLM GUI logs: \Program Files\HITACHI\DynamicLinkM anager\log\dlmgui[1-2].log #2 Hitachi Command Suite Common Agent Component logs: \Program Files\HITACHI\DynamicLinkM anager\log\dlmwebagent[1-n ].
2. HDLM Functions 2.11.2 Filtering of Error Information Errors detected by HDLM are classified into various error levels. Table 2-8: Error Levels lists the error levels, in the order of most to least severe. Table 2-8: Error Levels Error level Meaning Level shown in Event Viewer Critical Fatal errors that may stop the system. Error Error Errors that adversely affect the system. This type of error can be avoided by performing a failover or other countermeasures.
2. HDLM Functions • Outputs all trace information For details on how to change the collection level, see 3.7.2 Setting Up the HDLM Functions. 2.11.3 Collecting Error Information Using the Utility for Collecting HDLM Error Information (DLMgetras) HDLM provides the DLMgetras utility for collecting HDLM error information.
2. HDLM Functions 2.12 Collecting Audit Log Data HDLM and other Hitachi storage-related products provide an audit log function so that compliance with regulations, security evaluation standards, and industry-specific standards can be shown to auditors and evaluators. The following table describes the categories of audit log data that Hitachi storage-related products can collect.
2.
2. HDLM Functions Table 2-10: Categories and Audit Events That Can Be Output to the Audit Log Category Explanation Audit event Severity# Message ID 1 StartStop Startup and termination of the software Startup of the HDLM manager was successful. 6 KAPL15401-I Startup of the HDLM manager failed. 4 KAPL15402-W The HDLM manager stopped. 6 KAPL15403-I Startup of the DLMgetras utility 6 KAPL15060-I Termination of the 6 KAPL15061-I Startup of the HDLM GUI was successful.
2. HDLM Functions Category Explanation Audit event Severity# Message ID 1 52 Initialization of path statistics failed. 4 KAPL15102-W An attempt to place a path online or offline was successful. 6 KAPL15103-I An attempt to place a path online or offline failed. 4 KAPL15104-W Setup of the operating environment was successful. 6 KAPL15105-I Setup of the operating environment failed. 4 KAPL15106-W An attempt to display program information was successful.
2. HDLM Functions Category Explanation Audit event Severity# Message ID 1 An attempt to place a path offline by using the HDLM GUI failed. 4 KAPL15208-W An attempt to perform an operation by using the HDLM GUI (output to a CSV file, acquiring option information, specifying option information, refreshing, or clearing data) was successful. 6 KAPL15205-I An attempt to perform an operation by using the HDLM GUI failed.
2. HDLM Functions The severity levels are as follows: 4: Warning, 6: Information #2 If you use Ctrl + C to cancel the DLMgetras utility for collecting HDLM error information, audit log data indicating that the DLMgetras utility has terminated will not be output. 2.12.2 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.
2. HDLM Functions Severity Audit log data to output Correspondence with event log type 2 3 4 Error and Warning Warning Error, Warning, and Information Information 5 6 7 Filtering by category: The following categories can be specified: • StartStop • Authentication • ConfigurationAccess • All of the above For details on how to specify audit log settings, see 3.7.2 Setting Up the HDLM Functions. 2.12.
2. HDLM Functions Up to 950 bytes of text can be displayed for each message-section. Table 2-12: Items Output in the Message Section Explanation Item# Common identifier Fixed to CELFSS Common specification revision number Fixed to 1.1 Serial number Serial number of the audit log message Message ID Message ID in KAPL15nnn-l format Date and time The date and time when the message was output. This item is output in the following format: yyyy-mm-ddThh:mm:ss.
2. HDLM Functions Explanation Item# Log type information Fixed to BasicLog Application identification information Program identification information Reserved area This field is reserved. No data is output here. Message text Data related to the audit event is output. #: The output of this item depends on the audit event. Example of the message section for the audit event An attempt to display HDLM management-target information was successful: CELFSS,1.1,0,KAPL15109-I,2008-04-09T10:18:40.
2. HDLM Functions 2.13 Integrated HDLM management using Global Link Manager By using Global Link Manager, you can perform integrated path management on systems running multiple instances of HDLM. 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.
2.
2. HDLM Functions 2.14 Cluster Support HDLM can also be used in cluster configurations. For details about the cluster software supported by HDLM, see Table 3-5: Supported Cluster Software in 3.1.3 Cluster Software Supported by HDLM. When load balancing is used by cluster software supported by HDLM, HDLM uses an active host path to access an LU.
Chapter 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. 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.
3. Creating an HDLM Environment 3.1 HDLM System Requirements Check the following before installing HDLM: 3.1.1 OSs Supported by HDLM This subsection describes the OSs, Microsoft MPIO drivers, and Web browsers supported by HDLM. (1) Supported OSs You can install HDLM on any OS described in Table 3-1: Supported OSs.
3. Creating an HDLM Environment OS Service pack Windows Server 2008 R2(x64) No service pack SP1 Windows Server 2008(x86) No service pack SP2 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.
3. Creating an HDLM Environment ID for every connected host and storage system. For details about the micro-program versions for using HDLM, see the HDLM Release Notes. For details about storage system settings required for using HDLM, see the maintenance documentation for storage systems.
3.
3. Creating an HDLM Environment #5 The evaluation of HP EVA8000 has been completed. Response to inquiries for other systems of the HP EVA series must be the same as that of the HP EVA8000. When using HP EVA systems other than the HP EVA8000, evaluate the connection in advance. (2) HBAs For details about the supported HBAs, see the HDLM Release Notes.
3. Creating an HDLM Environment #5 Connection mainframe: MVS Connection storage system: Hitachi USP 3.1.3 Cluster Software Supported by HDLM Table 3-5: Supported Cluster Software lists the supported software when you create a cluster software configuration.
3. Creating an HDLM Environment OS Windows Server 2003 (x64)#2 SP No service pack SP2 68 Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP, Hitachi AMS2000/ AMS/WMS/ SMS series, Universal Storage Platform V/VM, and Virtual Storage Platform EMC DMX serie s EMC CX serie s HP EVA serie s MSCS Y -- Y Y VCS 4.3 Y -- -- -- Oracle RAC 10g#1 Y -- -- -- MSCS Y -- Y Y VCS 4.
3. Creating an HDLM Environment OS SP Windows Server 2003 R2 (x64)#2 No service pack SP2 Cluster software name Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP, Hitachi AMS2000/ AMS/WMS/ SMS series, Universal Storage Platform V/VM, and Virtual Storage Platform EMC DMX serie s EMC CX serie s HP EVA serie s MSCS Y -- Y Y VCS 4.3, 5.0 Y -- -- -- Oracle RAC 10g#1 Y -- -- -- Oracle RAC 11g#1 Y -- -- -- MSCS Y -- Y Y VCS 4.3, 5.
3. Creating an HDLM Environment OS Windows Server 2003 (x86)#2 SP No service pack SP1 SP2 70 Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP, Hitachi AMS2000/ AMS/WMS/ SMS series, Universal Storage Platform V/VM, and Virtual Storage Platform EMC DMX serie s EMC CX serie s HP EVA serie s MSCS Y Y Y Y VCS 4.1, 4.2, 4.3 Y -- -- -- Oracle 9i RAC#1 Y -- -- -- Oracle RAC 10g#1 Y -- -- -- MSCS Y Y Y Y VCS 4.3, 5.
3. Creating an HDLM Environment OS SP Windows Server 2003 R2 (x86)#2 No service pack Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP, Hitachi AMS2000/ AMS/WMS/ SMS series, Universal Storage Platform V/VM, and Virtual Storage Platform EMC DMX serie s EMC CX serie s HP EVA serie s 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.
3.
3. Creating an HDLM Environment Legend: Y: Usable --: 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.
3. Creating an HDLM Environment OS Related programs VERITAS Storage Foundation for Windows 4.0 Windows Server 2003 (x86)# VERITAS Storage Foundation for Windows 4.1 VERITAS Storage Foundation for Windows 4.2 VERITAS Storage Foundation for Windows 4.3 Veritas Storage Foundation for Windows 5.0 Veritas Storage Foundation for Windows 5.1 Veritas Storage Foundation for Windows 5.1 Windows Server 2008 R2(x64)# # The EMC DMX Series, EMC CX Series and HP EVA Series do not support volume managers. 3.1.
3. Creating an HDLM Environment Table 3-8: Disk Space Requirements for a Host Folder HDLM-installation-folder Disk capacity requirements • When you use only the HDLM Core components: 10 MB + p MB#1 + q MB#2 + 1 MB • When you install but do not use the HDLM GUI: 150 MB + p MB#1 + q MB#2 + 1 MB • When you install and use the HDLM GUI: 150 MB + 20 MB + p MB#1 + q MB#2 + 1 MB #1 This size depends on the log files settings. The maximum size is 30000MB.
3. Creating an HDLM Environment 3.2 Flow for Creating an HDLM Environment Set up the environment to use HDLM as follows.
3. Creating an HDLM Environment 3.3 HDLM Installation Types This section describes the following types of HDLM installations: new installation, upgrade installation, migration, and re-installation. New installation of HDLM: Installing HDLM on a server, which HDLM has never been installed on, is called a new installation of HDLM. Upgrade installation of HDLM: Installing a newer version of HDLM over the existing version without uninstalling the existing version is called an upgrade installation of HDLM.
3. Creating an HDLM Environment 3.4 Notes on Creating an HDLM Environment This section provides notes on creating an HDLM environment. For details about operating HDLM, see 4.1 Notes on Using HDLM. 3.4.1 Notes on HBAs and HBA Drivers If you are using the Storport Miniport driver as an HBA driver in Windows Server 2003, install QFE 838894 or later for the Microsoft Storport driver or install Windows Server 2003 SP1 or later, before installing HDLM.
3. Creating an HDLM Environment Files#\HITACHI\HNTRLib2\spool\hntr2n.log (n indicates a file number) - Trace files after migration: drive-for-program-installation:\Program Files\HITACHI\DynamicLinkManager\log\hdlmtrn.log (n indicates a file number) The underlined part indicates the folder specified during installation. • When you migrate from HDLM versions 04-01 to 5.5 to HDLM version 5.6 or later, or when you perform an upgrade installation from HDLM 5.
3. Creating an HDLM Environment and Service Pack Version, which are displayed by executing the following command, are the same, then the versions of HDLM will also be the same: >dlnkmgr view -sys -sfunc 3.4.4 Notes on Windows When you upgrade or re-install Windows Server 2003 or install a Windows Server 2003 service pack, be sure to uninstall HDLM beforehand.
3.
3. Creating an HDLM Environment Be aware that even though an upgrade or re-installation of HDLM failed, the Add/Remove Programs window might indicate that HDLM has been installed normally. 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.
3. Creating an HDLM Environment Specifying a Folder That Does Not Satisfy the Conditions for an HDLM Installation might occur. If this happens, reinstall HDLM by following the procedures given below. Table 3-10: Problems and What to Do When Specifying a Folder That Does Not Satisfy the Conditions for an HDLM Installation Problem What to do An internal error occurred and the installation was interrupted. Specify a folder that satisfies the above conditions and re-install the HDLM.
3. Creating an HDLM Environment If you are using Hyper-V in Windows Server 2008 and an HDLM management-target device has been allocated as a physical hard disk to a guest OS, before you perform an HDLM upgrade installation or uninstallation on a host OS, be sure to unallocate the physical hard disk from the guest OS. After the upgrade installation or uninstallation has finished, reallocate the physical hard disk to the guest OS.
3. Creating an HDLM Environment following procedure to delete the two oemn.inf files and two oemn.pnf files: 1. Check the MPIO driver version indicated in the KAPL09257-W or the KAPL09258-E message. In this example, the MPIO driver version is n.nn.nnnn.nnnn (n represents numbers): KAPL09257-W HDLM cannot be installed on a system where MPIO n.nn.nnnn.nnnn has already been installed. 2.
3. Creating an HDLM Environment 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.
3. Creating an HDLM Environment Therefore, make a note of the original values of MISSCOUNT and DISKTIMEOUT before changing them. If you install HDLM while resident software (such as antivirus software) is running, HDLM might not operate correctly. Before installing HDLM, make sure that you have stopped all software programs, including all resident software. 3.4.
3. Creating an HDLM Environment on the same drive. • When an HDLM version from another OS has been installed: Uninstall the version of HDLM that is already installed, and then rerun the installation program. • When HDLM for another OS has not been installed: Perform the installation again by following the procedure below: 1. From Explorer, in the Tools menu, choose Folder Options. The Folder Options window is displayed. 2.
3. Creating an HDLM Environment In Windows Server 2003 SP1 or later, if you change an HDLM management-target device during an upgrade installation and then restart the host, the KAPL08019-E and KAPL08022-E messages might be output, and the path status might change to Offline(E) or Online(E). If this happens, execute the dlnkmgr command's online operation to change the path status to Online. 3.4.
3. Creating an HDLM Environment 3.5 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 3.5.5 Upgrade Installation or Re-installation of HDLM or 3.5.6 Migrating from HDLM 5.4 or Earlier to HDLM 5.5 or Later. When you install HDLM, Hitachi Network Objectplaza Trace Library will also be installed.
3. Creating an HDLM Environment 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.
3. Creating an HDLM Environment See the HBA documentation and manual to complete the required setup. 8. If your configuration uses an IP-SAN, install and set up the iSCSI initiator (iSCSI software or HBA). For details, see the iSCSI initiator documentation, the documentation for the HBA, or the storage system documentation. 9. Prepare the LUs. For each LU that you want to use, be sure to write signatures, create partitions, and then format them.
3. Creating an HDLM Environment (1) How to Create an Installation-Information Settings File For an installation-information settings file, you need to define the license key file name, installation destination folder, and then any other information that is required for the particular installation. HDLM provides a sample file in order to simplify the editing process of an installation-information settings file. The sample file is located on the supplied DVD.
3. Creating an HDLM Environment 3.5.3 Performing a New Installation of HDLM on Windows Server 2003 (1) In a Non-Cluster Environment Before installing HDLM, have a license key ready. If you want to perform an unattended installation, also be sure to prepare an installation-information settings file. To install HDLM on a host that does not currently have HDLM installed on it: 1. Log on to Windows as a member of the Administrators group. 2.
3. Creating an HDLM Environment If you have specified n for the restart key in the installation-information settings file, go to step 11. If you have specified y for the restart key in the installation-information settings file, go to step 16. 4. The program checks the MPIO driver version, and then installs the MPIO driver. If a message appears, asking you whether you want to install the MPIO driver, make sure that no multi-path management software other than HDLM is installed.
3. Creating an HDLM Environment # This OS cannot be used with the EMC DMX series. The Hitachi storage subsystems and HP StorageWorks XP Series option is always selected. To select an EMC DMX series or EMC CX series LU as the HDLM management-target device, select EMC Symmetrix DMX Series, CLARiiON CX Series. To select an HP EVA series LU as the HDLM management-target device, select HP StorageWorks EVA Series. 10. Follow the instructions shown in the messages that appear in the window.
3. Creating an HDLM Environment 12. After the installation finishes, execute the dlmprsvkey utility with the -v parameter specified. Execute the following command: HDLM-installation-folder\bin\dlmprsvkey -v Make sure that the PRSV key displayed by the dlmprsvkey utility is unique among all the other hosts in the SAN. If the PRSV key is not unique or is not registered, or if the KAPL09131-W message appears, execute the dlmprsvkey utility with the -r parameter specified to re-register the PRSV key.
3. Creating an HDLM Environment after the installation finishes. The KAPL09115-W message will appear if deletion of this file fails. If this happens, delete the file manually. 18. Execute the dlnkmgr command's view operation to display the status of each program. An example of executing the dlnkmgr command's view operation is as follows: >dlnkmgr view -sys HDLM Version : x.x.
3. Creating an HDLM Environment configuration. 22. Connect cables to all the HBAs to change the configuration to a multi-path configuration. Figure 3-3: Single Path Configuration and Multi-path Configuration shows a single path configuration and a multi-path configuration. Figure 3-3: Single Path Configuration and Multi-path Configuration 23. Check the path information as described in 3.6 Checking the Path Configuration to make sure that you have successfully assembled a multi-path configuration.
3. Creating an HDLM Environment 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 and run the installation program 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.
3. Creating an HDLM Environment 8. follow the procedure below: • The KAPL09127-W message will appear if the MPIO driver has already been installed and the version does not match the version of the MPIO driver about to be installed. - Click the Next button to install the MPIO driver. - Click the Cancel button to cancel the installation. • If no message appears, go to the next step. 9.
3. Creating an HDLM Environment always selected. To select an EMC DMX series or EMC CX series LU as the HDLM management-target device, select EMC Symmetrix DMX Series, CLARiiON CX Series. To select an HP EVA series LU as the HDLM management-target device, select HP StorageWorks EVA Series. 14. Follow the instructions shown in the messages that appear in the window.
3. Creating an HDLM Environment HDLM-installation-folder\bin\dlmprsvkey -v Make sure that the PRSV key displayed by the dlmprsvkey utility is unique among all the other hosts in the SAN. If the PRSV key is not unique or is not registered, or if the KAPL09131-W message appears, execute the dlmprsvkey utility with the -r parameter specified to re-register the PRSV key. If the PRSV key is not registered, the HDLM functions might not properly operate. For details about the dlmprsvkey utility, see 7.
3. Creating an HDLM Environment 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 23. 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. 24.
3. Creating an HDLM Environment 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 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.
3. Creating an HDLM Environment 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 3.5.6 Migrating from HDLM 5.4 or Earlier to HDLM 5.5 or Later. If HDLM 5.5 or later has been installed, the KAPL09173-W message will appear. If this happens, carry out the procedure shown in 3.5.5 Upgrade Installation or Re-installation of HDLM. If no message appears, go to step 6.
3. Creating an HDLM Environment 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. The PRSV key is required for the HDLM functions to properly operate. Also, the value of the PRSV key must be unique for each host. 10. If the KAPL09128-W message appears, you will need to re-enter the correct PRSV key.
3. Creating an HDLM Environment • The PRSV key will be registered before the installation finishes. If the KAPL09131-W message appears, follow the procedure described in step 14. • Although a message prompting you to restart the host appears after the installation has finished, a restart is not necessary.
3. Creating an HDLM Environment 18. Modify the storage system settings. Modify the storage system settings by following the procedure described in the maintenance documentation for that particular storage system. 19. Restart each host. 20. Log on to Windows again as a member of the Administrators group. 21. Make sure that the program is running properly, by examining the results of the dlnkmgr command's view operation. Make sure that on MSCS is displayed in Support Cluster.
3. Creating an HDLM Environment If HDLM Manager, HDLM Alert Driver, and HDLM Driver are all Alive, all the programs are running correctly. 24. After the installation finishes, check the path information as described in 3.6 Checking the Path Configuration, and make sure that you have successfully installed HDLM in a single-path configuration. 25. Connect cables to all the HBAs to change the configuration to a multi-path configuration. 26. Check the path information as described in 3.
3. Creating an HDLM Environment HDLM. If no message appears, go to step 8. • If you are planning to perform an unattended installation, execute the installhdlm utility. At the command prompt, execute the following command: drive-to-which-the-installation-DVD-is-inserted:\HDLM_Windows\DLMTo ols\installhdlm -f installation-information-settings-file Specify n for the restart key in the installation-information settings file. This command checks whether HDLM has already been installed. If HDLM 5.
3. Creating an HDLM Environment value of the PRSV key must be unique for each host. 12. If the KAPL09128-W message appears, you will need to re-enter the correct PRSV key. If a message does not appear, go to the next step. 13. The message Select Storage system to be managed. is displayed. Click the Next button. In a VCS environment, because an EMC DMX series or EMC CX series LU cannot be set as an HDLM management-target device, do not select EMC Symmetrix DMX Series, CLARiiON CX Series.
3. Creating an HDLM Environment Global Link Manager. 15. Check the results of the installation. If you have performed an unattended installation, check the installation results from the command prompt. 16. After the installation finishes, execute the dlmprsvkey utility with the -v parameter specified. Execute the following command: HDLM-installation-folder\bin\dlmprsvkey -v Make sure that the PRSV key displayed by the dlmprsvkey utility is unique among all the other hosts in the SAN.
3. Creating an HDLM Environment 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 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.
3. Creating an HDLM Environment down. 3. Restart each host. Start them in a 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 installation-destination 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.
3. Creating an HDLM Environment If a message appears asking you whether you want to install the MPIO driver, make sure that no multi-path management software other than HDLM is installed. • If multi-path management software other than HDLM is installed, click the Cancel button to cancel the installation, uninstall the multi-path management software, and then install HDLM. • If no multi-path management software other than HDLM is installed, click the Next button to continue the installation. 8.
3. Creating an HDLM Environment Storport driver, or install Windows Server 2003 SP1 or later. Notes on using a Storport Miniport driver Read these notes before using a Storport Miniport driver as an HBA driver. The file version of the Storport.sys of this system (Microsoft(R) Storport driver) is n.n.nnnn.n. When using a Storport Miniport driver as an HBA driver: Please update the Storport Miniport driver to a Storport.sys with a file version n.n.nnnn.n or later.
3. Creating an HDLM Environment If you used a license key file, it will be deleted after the installation finishes. The KAPL09115-W message will appear if deletion of this file fails. If this happens, delete the file manually. 16. Shut down the host. Leave the host in a single-path configuration until you check (in step 24) whether HDLM has been successfully installed. 17. On all the hosts that make up the cluster system, perform steps 3 to 16. 18.
3. Creating an HDLM Environment 22. Use the results of the dlnkmgr command's view operation to check the version of the installed HDLM. If x.x.x-xx is displayed in HDLM Version, the correct version of HDLM has been installed. 23. Use the results of the dlnkmgr command's view operation to check that the programs are running properly. If HDLM Manager, HDLM Alert Driver, and HDLM Driver are all Alive, all the programs are running correctly. 24.
3. Creating an HDLM Environment 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 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.
3. Creating an HDLM Environment • If you are not performing an unattended installation, insert the DVD into the drive and run the installation program setup.exe. The program checks whether HDLM has already been installed. If the KAPL09173-W message appears, perform the procedure shown in 3.5.5 Upgrade Installation or Re-installation of HDLM. If a message does not appear, go to the next step. • If you are performing an unattended installation, execute the installhdlm utility.
3. Creating an HDLM Environment • The PRSV key will be registered before the installation finishes. If the KAPL09131-W message appears, follow the procedure described in step 9. • Although a message prompting you to restart the host appears after the installation has finished, a restart is not necessary.
3. Creating an HDLM Environment Enter five single-byte spaces between DGC and RAID. 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.
3. Creating an HDLM Environment 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 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.
3. Creating an HDLM Environment Figure 3-4: Single Path Configuration and Multi-path Configuration 25. Check the path information as described in 3.6 Checking the Path Configuration to make sure that you have successfully assembled a multi-path configuration. (2) When MSCS Is Used The following provides explanations of how to install MSCS before and after an HDLM installation. Installing MSCS after an HDLM installation To install HDLM and then MSCS: 1. Shut down all the hosts. 2.
3. Creating an HDLM Environment 6. Perform the installation. • If you are not performing an unattended installation, insert the DVD into the drive and run the installation program setup.exe. The program checks whether HDLM has already been installed. If the KAPL09173-W message appears, perform the procedure shown in 3.5.5 Upgrade Installation or Re-installation of HDLM. If a message does not appear, go to the next step. • If you are performing an unattended installation, execute the installhdlm utility.
3. Creating an HDLM Environment 10. Follow the instructions shown in the messages that appear in the window. • The PRSV key will be registered before the installation finishes. If the KAPL09131-W message appears, follow the procedure described in step 12. • Although a message prompting you to restart the host appears after the installation has finished, a restart is not necessary.
3. Creating an HDLM Environment 16. For Device Hardware ID, enter DGC RAID, and then click the OK button. Enter five single-byte spaces between DGC and RAID. 17. Click the OK button to close the MPIO Properties dialog box. 18. Shut down the host. Leave the host in a single-path configuration until you check (in step 26) whether HDLM has been successfully installed. 19. Perform steps 3 to 18 on all the hosts that make up the cluster system. 20.
3. Creating an HDLM Environment 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. From the results of the view operation, check that the programs are running properly. If HDLM Manager, HDLM Alert Driver, and HDLM Driver are all Alive, all the programs are running correctly. 26. After the installation finishes, check the path information as described in 3.
3. Creating an HDLM Environment Path Health Checking : on(30) Auto Failback : on(1) Remove LU : off Intermittent Error Monitor : off 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.
3. Creating an HDLM Environment Specify n for the restart key in the installation-information settings file. 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.
3. Creating an HDLM Environment 10. Check the results of the installation. If you have performed an unattended installation, check the installation results from the command prompt. 11. After the installation finishes, execute the dlmprsvkey utility with the -v parameter specified. Execute the following command: HDLM-installation-folder\bin\dlmprsvkey -v Make sure that the PRSV key displayed by the dlmprsvkey utility is unique among all the other hosts in the SAN.
3. Creating an HDLM Environment 21. Restart each host. 22. Log on to Windows again as a member of the Administrators group. 23. Execute the dlnkmgr command's view operation to display the status of each program. Make sure that on MSCS is displayed in Support Cluster. An example of executing the dlnkmgr command's view operation is as follows: >dlnkmgr view -sys HDLM Version : x.x.
3. Creating an HDLM Environment 3.6 Checking the Path Configuration, and make sure that you have successfully installed HDLM in a single-path configuration. 27. Connect cables to all the HBAs to change the configuration to a multi-path configuration. 28. Check the path information as described in 3.6 Checking the Path Configuration to make sure that you have successfully assembled a multi-path configuration. 3.5.
3. Creating an HDLM Environment The default of the HDLM management-target device is the same as that before the upgrade installation or re-installation. For example, if you select EMC Symmetrix DMX Series, CLARiiON CX Series when you installed HDLM for the first time, EMC Symmetrix DMX Series, CLARiiON CX Series will already be selected when it appears in the dialog box.
3. Creating an HDLM Environment addition, delete the files that have the same names as the above files, but with the extension pnf (oemn.pnf). If you do not delete the correct files, the host might not run properly. Before deleting a file, make sure that it satisfies all of the above conditions. 4. Perform a new HDLM installation by following the procedure in 3.5 Installing HDLM. 5.
3. Creating an HDLM Environment Sun Microsystems JRE 6.0_04 (32-bit) Sun Microsystems JRE 6.0_17 (32-bit) • In Windows Server 2008: Sun Microsystems JRE 6.0_17 (32-bit) To install JRE: 1. Download the JRE from the Sun Microsystems website. 2. Install the JRE on the host where the HDLM has been installed. Do not install the JRE directly into HDLM-installation-folder\jre_user. If you do this, uninstall the JRE, and then reinstall it into another folder. When you install JRE 6.
3. Creating an HDLM Environment \lib After installing the JRE, check to make sure that the HDLM GUI starts. Note: • If you uninstall HDLM, HDLM-installation-folder\jre_user will be deleted. • If Hitachi Command Suite Common Agent Component is set to use a 32-bit version of Java installed in the system, HDLM uses the specified version of Java to start the HDLM GUI. 3.5.
3. Creating an HDLM Environment command syntax. Table 3-13: firewall_setup command syntax Item Details Synopsis firewall_setup {-set|-unset} Description Registers the following ports used by the Hitachi Command Suite Common Agent Component in a Windows environment as firewall exceptions: • Port set for the server.agent.port property (default: 24041/tcp) • Port set for the server.http.port property (default: 24042/tcp) • Port set for the server.http.
3. Creating an HDLM Environment 3.6 Checking the Path Configuration HDLM functions, such as load balancing and failover, are only available for HDLM management-target devices that have more than one active path. After you install HDLM or change the hardware configuration, check the structure and statuses of the paths. To check the path information, use the dlnkmgr command's view operation or use the Path List view in the Path Management window of the HDLM GUI.
3. Creating an HDLM Environment click Scan for hardware changes. 2. From the Disk Management window of Windows, click Rescan Disks.
3. Creating an HDLM Environment 3.7 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.
3. Creating an HDLM Environment To check the current audit log settings, execute the following command: >dlnkmgr view -sys -audlog Audit Log : off Audit Log Category : KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss > 3.7.2 Setting Up the HDLM Functions The recommended and default values for each HDLM function is shown below in Table 3-14: The Recommended and Default Values for Each Function.
3. Creating an HDLM Environment (1) Setting Up Load Balancing In a cluster environment, the load balancing function is only available for the Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP, Hitachi AMS2000/AMS/WMS/SMS series, Universal Storage Platform V/VM, and Virtual Storage Platform.
3. Creating an HDLM Environment >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. If the checking interval is not specified, then the previously specified value will be automatically applied.
3. Creating an HDLM Environment 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. The default value for the number of error occurrences is 3.
3. Creating an HDLM Environment Table 3-15: LU Deletion Function Values Values in the set operation Description off The LU is not removed from HDLM-management even if the error occurs on all the paths to the LU, all the paths to the LU are disconnected, or the LU is deleted. The status of the paths is either Offline(E) or Online(E). This operation is equal to the operation in HDLM 05-01 or earlier.
3. Creating an HDLM Environment Value Description 2 All information for errors of the "Warning" level or higher is collected. 3 All information for errors of the "Information" level or higher is collected. 4 All information for errors of the "Information" level or higher (including maintenance information) is collected. If an error occurs, you might have to change the collection level to 1 or higher to collect any log information.
3. Creating an HDLM Environment 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. For normal operation, we recommend that you set the trace level to 0.
3. Creating an HDLM Environment is set to 2. You can specify a value from 2 to 16 for the number of HDLM manager log files. By specifying both the log file size and the number of log files, you can collect up to 32000000KB (approximately 30GB) of error logs. • Setting up the number of error log files by using the set operation The following is an example of setting up the number of error log files by using a command: >dlnkmgr set -elfn 5 Specify the number of error log files by using numbers.
3. Creating an HDLM Environment 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.
3. Creating an HDLM Environment Value Explanation ca Audit log events of the ConfigurationAccess category are collected. all Audit log events of the StartStop, Authentication, and ConfigurationAccess categories are all collected. This example shows how to enable the collection of audit log data: >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.
3. Creating an HDLM Environment >dlnkmgr view -sys -audlog Audit Log : on(6) Audit Log Category : a11 KAPL01001-I The HDLM command completed normally.
3. Creating an HDLM Environment 3.8 Setting Up Integrated Traces When HDLM is used, the dlnkmgr command and GUI operation logs are output to the integrated trace information files of Hitachi Network Objectplaza Trace Library (HNTRLib2) (installation-destination-drive:\Program Files#\HITACHI\HNTRLib2\spool\Hntr2n.log files (n indicates a file number)). # For Windows Server 2003 (excluding the x86 edition) or Windows Server 2008 (excluding the x86 edition), Program Files is Program Files (x86).
3. Creating an HDLM Environment To change the integrated trace file settings: 1. In Explorer, double-click the following file: program-installation-destination-drive:\Program Files#\HITACHI\HNTRLib2\bin\hntr2utl2.exe If you are using the Server Core environment of Windows Server 2008, execute hntr2utl2.exe from the Administrator: Command Prompt window. # For Windows Server 2003 (excluding the x86 edition) or Windows Server 2008 (excluding the x86 edition), Program Files is Program Files (x86).
3. Creating an HDLM Environment The value you specify here will apply to n in program-installation-destination-drive:\Program Files\HITACHI\HNTRLib2\spool\Hntr2n.log (n indicates a file number). 3. In File Size(KB), change the size of an integrated trace file. The default is 256 (kilobytes). You can specify a value from 8 to 8192. Specify a value greater than or equal to the setting of Buffer Size(KB). 4. In Buffer Size(KB), change the buffer size. Change the buffer size for the monitoring cycle.
3. Creating an HDLM Environment the Services window. From the list of services, select DLMManager. Then, from the Action menu, choose Restart to restart the service. Next, from the list of services, select Hitachi Network Objectplaza Trace Monitor 2. Then, from the Action menu, choose Restart to restart the service.
3. Creating an HDLM Environment 3.9 Uninstalling HDLM This section explains how to return the operating environment to the way it was before HDLM was installed. 3.9.1 Preparations for HDLM Uninstallation Back up all the data on the host where HDLM is installed. Also, if necessary, back up the data on the management target device. If firewall exceptions have been registered by using the firewall_setup command, remove them.
3. Creating an HDLM Environment • When uninstalling HDLM on a host where a Device Manager Agent 5.0 or later is installed, do not execute any of the following Device Manager Agent commands during uninstallation. Also, do not uninstall HDLM while executing any of the following Device Manager Agent commands: hbsasrv, HiScan, hdvmagt_account, hdvmagt_schedule, hldutil, TIC • If the Data Execute Prevention (DEP) function on the host is enabled, perform the following procedure: 1.
3. Creating an HDLM Environment (1) Uninstallation Procedures - in a Non-Cluster Environment To uninstall HDLM: 1. Log on to Windows. Log on as a member of the Administrators group. 2. Stop all the processes and services that use the HDLM management-target paths. Stop any processes or application services, such as a DBMS, that are using the HDLM management-target paths. In Windows Server 2008, if you are not logged on as an administrator, use the Run as administrator functionality. 3.
3. Creating an HDLM Environment 5. On the MPIO-ed Devices page, select Device Hardware ID DGC and then click the Delete button. 6. Click the OK button to close the MPIO Properties dialog box. 7. Start the uninstallation program. RAID, In Windows Server 2003: From Control Panel, choose Add or Remove Programs, and then Change or Remove Programs. From the list of programs, select Dynamic Link Manager, and click the Change/Remove button.
3. Creating an HDLM Environment Log on as a member of the Administrators group. 2. Stop all the processes and services that use the HDLM management-target paths. Stop any processes or application services, such as a DBMS, that are using the HDLM management-target paths. In Windows Server 2008, if you are not logged on as an administrator, use the Run as administrator functionality. 3. Stop MSCS or VCS on all the hosts that make up the cluster. When MSCS is used, follow the procedure described below.
3. Creating an HDLM Environment Figure 3-7: Single Path Configuration and Multi-path Configuration In Windows Server 2008, if you have selected an EMC CX series LU as the HDLM management-target device, perform the following steps to unregister it. Otherwise, go to step 8. 5. From Control Panel, choose MPIO. The MPIO Properties dialog box opens. 6. On the MPIO-ed Devices page, select Device Hardware ID DGC and then click the Delete button. 7.
3. Creating an HDLM Environment From the Administrator: Command Prompt window, execute the uninstallhdlm utility for uninstalling HDLM. For details about the uninstallhdlm utility, see 7.8 The uninstallhdlm Utility for Uninstalling HDLM. 9. The dlmchkpath utility is automatically executed. If a warning dialog box appears, follow the procedure below: • Cancel the uninstallation. Reconfigure the system into a single-path configuration, and then perform the uninstallation again.
3. Creating an HDLM Environment The MPIO Properties dialog box opens. 5. On the MPIO-ed Devices page, select Device Hardware ID DGC and then click the Delete button. 6. Click the OK button to close the MPIO Properties dialog box. 7. Start the uninstallation program. RAID, 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.
3. Creating an HDLM Environment If the KAPL09020-E message appears during the uninstallation of HDLM, go to step 3. 2. Execute the following command#1 to unregister program products that include HNTRLib2: C:\>"C:\Program Files#2\HITACHI\HNTRLib2\bin\hntr2cancel.exe" Dynamic Link Manager" 3. "Hitachi Execute the following command#1 to check if any program is using HNTRLib2: C:\>"C:\Program Files#2\HITACHI\HNTRLib2\bin\hntr2getname.
3. Creating an HDLM Environment HNTRLib2 common library file hntr2t.dll. Even if this file remains undeleted, other applications will not be affected. To delete this file, perform the following procedure: 1. Start the registry editor (regedit.exe) and check that the following registry key does not exist: HKEY_LOCAL_MACHINE\SOFTWARE\HITACHI\COMMON_DLL\HNTRLIB2 If this key exists, it means another application is using the hntr2t.dll file. If this is the case, do not delete the hntr2t.dll file. 2.
Chapter 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. 4.1 4.2 4.3 4.4 Notes on Using HDLM HDLM Operations Using the HDLM GUI Using Commands for HDLM Operations Using the Windows Administrative Tool (Performance) to Check Path Information 4.5 Starting and Stopping the HDLM Manager 4.6 HDLM Resident Processes 4.
4. HDLM Operation 4.1 Notes on Using HDLM This section contains notes that are important for running HDLM operations. 4.1.1 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. 4.1.2 Upgrading Windows Always uninstall HDLM before upgrading Windows, re-installing Windows during a system recovery, or installing a Windows SP.
4. HDLM Operation • If the OS is Windows Server 2008: EMC CX series: HDLM 6.4 or later • You can display and use the HDLM GUI windows for the Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP, Hitachi AMS2000/ AMS/WMS/SMS series, Universal Storage Platform V/VM, and Virtual Storage Platform. If you specify the EMC DMX series, EMC CX series, or HP EVA series as an HDLM management-target device, use HDLM commands to display information and set the operating environment.
4. HDLM Operation 4.2 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. 4.2.1 Notes on Using the HDLM GUI This subsection provides notes on using the HDLM GUI window. Be sure to read this section. The HDLM GUI is unavailable in the Server Core environment of Windows Server 2008.
4. HDLM Operation 4.3 Using Commands for HDLM Operations This section explains how to use the HDLM command. For details on the various command operations, see 6. Command Reference. 4.3.1 Notes on Using Commands • Execute the HDLM command as a member of the Administrators group. Windows Server 2008 supports user account control (UAC). For this reason, use either of the following procedures to execute HDLM commands: • Execute the HDLM command using the Administrator account.
4. HDLM Operation For details on the displayed items and their descriptions, see 6.7 view (Displays Information). 4.3.3 Changing the Status of Paths This section explains how to change path statuses. (1) 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.
4. HDLM Operation 2. To change the status of paths to online, execute the dlnkmgr command's online operation. The paths to be placed online can be specified by using an HBA port, CHA port, single path, or HBA port WWN. For details on how to specify paths, see 6.5 online (Places Paths Online). For example, if you want to place all the paths that pass through a specific HBA port online, execute the dlnkmgr command's online operation with the -hba parameter specified.
4. HDLM Operation port offline, execute the dlnkmgr command's offline operation with the -hba parameter specified. The following shows an example of executing this command: >dlnkmgr offline -hba 1.1 KAPL01055-I All the paths which pass the specified HBA port will be changed to the Offline(C) status. Is this OK? [y/n]:y KAPL01056-I If you are sure that there would be no problem when all the paths which pass the specified HBA are placed in the Offline(C) status, enter y. Otherwise, enter n.
4. HDLM Operation 000011 Online 000004 Online 000010 Online 058A H 000003 Online 000009 Online KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss > 0585 I For details on the displayed items and their descriptions, see 6.7 view (Displays Information). 4.3.5 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.
4. HDLM Operation 4.3.6 Viewing and Setting Up the Operating Environment This section explains how to display and set up the HDLM operating environment. (1) Viewing the Operating Environment To display the operating environment, execute the dlnkmgr command's view operation with the -sys and -sfunc parameters specified. The following shows an example in which the command is executed: >dlnkmgr view -sys -sfunc HDLM Version : x.x.
4. HDLM Operation • Path health checking • Automatic failback • Intermittent error monitoring • LU dynamic deletion • Error log collection level • Trace level • Error log file size • The number of error log files • Trace file size • The number of trace files • Audit log data collection For details on how to set up each function, see 6.6 set (Sets Up the Operating Environment).
4. HDLM Operation For details on the displayed items and their descriptions, see 6.7 view (Displays Information). 4.3.8 Updating the License This section explains how to update the license. To update the license, execute the dlnkmgr command's set operation with the -lic parameter specified. When the confirmation message is displayed, enter y to execute, or n to cancel the command. If the license key file does not exist, a message asking you to enter the license key appears, so enter the license key.
4. HDLM Operation Trace File Size(KB) : 1000 Number Of Trace Files : 4 Path Health Checking : on(30) Auto Failback : on(1) Remove LU : on Intermittent Error Monitor : off 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.
4. HDLM Operation Permanent KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss > Among the displayed items, HDLM Manager, HDLM Alert Driver, and HDLM Driver indicate the HDLM component information. Also, you can view information for each HDLM component. Execute the dlnkmgr command's view operation with the -sys and subsequent parameter specified.
4. HDLM Operation 4.4 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 or Windows Server 2008. • If an error occurs in the HDLM performance monitor, performance information is not collected after the error.
4. HDLM Operation Counter name Description Avg.Disk Bytes/Read The average number of bytes transferred from the disk during one operation. Avg.Disk Bytes/Write The average number of bytes transferred to the disk during one operation. Disk Bytes/Sec The amount of data transferred per second between disks during read or write operations. Disk Read Bytes/Sec The amount of data transferred per second from the disk during read operations.
4. HDLM Operation 4.5 Starting and Stopping the HDLM Manager If an error occurs in the system, such as in an HDLM program, you might need to manually stop or start HDLM to recover from the error. 4.5.1 Starting the HDLM Manager During installation, the HDLM manager is registered as a Windows service and the startup type is set to Automatic. This means that when Windows starts, the HDLM manager will also start automatically.
4. HDLM Operation >dlnkmgr view -sys -msrv HDLM Manager Ver WakeupTime Dead KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss > When the HDLM Manager column shows Dead, the HDLM manager is inactive.
4. HDLM Operation 4.6 HDLM Resident Processes Table 4-3: HDLM resident processes 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 hntr2srv.
4. HDLM Operation 4.7 Reconfiguring the HDLM Operating Environment You can add or delete LUs and paths while the host installing HDLM is running by utilizing the Windows plug-and-play functionality. This operation is called dynamic reconfiguration. 4.7.1 Setting Up an Added LU and Path as an HDLM Management-target This section explains the procedure for setting up an added LU and path as an HDLM management-target.
4. HDLM Operation Figure 4-1: Using the command to confirm that an LU has been added 5. For the new LU, write a signature, create partitions, and then format it. Note: The PathID is determined by the system choosing the smallest, available number that is not already in use for another path. For example, when a path is deleted and then a new path is added, the PathID for the added path might not be the same number as the deleted PathID. When MSCS is used 1. Add an LU. 2. Stop node B. 3.
4. HDLM Operation 8. Restart node B. (2) Checking an Added Path You can add a path, by inserting a cable into an existing LU, even while the host (on which HDLM is installed) is running. When you add a path without adding an LU, what is displayed in the disk management window does not changed. You can confirm that a path has been added by using the HDLM command view operation, or the HDLM GUI.
4. HDLM Operation - KAPL08019-E and KAPL08022-E - KAPL05301-E Note that these messages are output by Windows activities, and not by an error in HDLM. 4.7.2 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.
4. HDLM Operation 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. Figure 4-3: An example of displaying the KAPL05301-E message shows an example of displaying the KAPL05301-E message.
4. HDLM Operation Table 4-4: Items and Descriptions for the Path Information Displayed in the KAPL05301-E Message shows the items and descriptions for the path information, displayed in the KAPL05301-E message. Table 4-4: Items and Descriptions for the Path Information Displayed in the KAPL05301-E Message Item Description PathID An AutoPATH_ID. Host port number Elements of a PathName.
4. HDLM Operation (3) Recovering a Deleted LU or Path To restore a deleted LU, recover it from the physical failure, and then perform the operations below. Note that sometimes, LUs are automatically recovered, without having to perform the following operations: • 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.
Chapter 5. Troubleshooting This chapter describes how to properly use HDLM error information, and then how to resolve the problem, if an error occurs in HDLM. The resolutions for path errors, HDLM program errors, and other types of errors are all described separately. This chapter describes how to use the HDLM commands to use HDLM error information and utilize various workarounds. For details about how to use the HDLM GUI, see the Hitachi Dynamic Link Manager Software GUI Help. 5.
5. Troubleshooting 5.1 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 7.2 The DLMgetras Utility for Collecting HDLM Error Information.
5. Troubleshooting 5.2 Checking Error Information in Messages You can check path errors by referring to the KAPL08xxx messages that are output to the event log. To obtain detailed information about a path failure, check the execution results of the view operation as indicated by the error message. For details on the view operation, see 6.7 view (Displays Information). The following is an example of a message: • Message that is output when a path error occurs. KAPL08022-E A path error occurred.
5. Troubleshooting LU or Path Has Been Dynamically Deleted in 4.7.2 Deleting an LU Dynamically. ErrorCode The error number generated when Windows detects a path error. When the Windows plug-and-play functionality deletes a SCSI device from Windows, the path of the SCSI device changes to the offline status, and the error number 0x00000000 is used.
5. Troubleshooting displayed. This is the same as the HDevName that is displayed by the view operation. For details on the view operation, see 6.7 view (Displays Information).
5. Troubleshooting 5.3 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. A path error check is performed every time an I/O is issued, or the Windows plug-and-play functionality detects that a path is disconnected. If there are any paths through which I/Os are not normally issued, such as a non-owner path, you should enable path health checking in order to detect any possible errors. For details about path health checking, see 2.
5. Troubleshooting 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. 5.3.1 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 5.2 Checking Error Information in Messages.
5. Troubleshooting pathinfo.txt is the redirection-output file name. Use a file name that matches your environment. 5.3.3 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). 5.3.4 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.
5. Troubleshooting 5.4 What To Do for a Program Error The following describes what to do to handle errors that occur in an HDLM program. Figure 5-3: Troubleshooting Procedure When a Program Error Occurs shows the troubleshooting procedure. Figure 5-3: Troubleshooting Procedure When a Program Error Occurs The following shows the procedure for handling a program error by using the HDLM command (dlnkmgr). 5.4.1 Examining the Messages Examine the messages that are output to the host event log.
5. Troubleshooting When an error occurs in the HDLM GUI, take a screenshot at the time the error occurred. 5.4.3 What To Do for the Program Error Follow the recommended actions for messages in 8. Messages. If the error occurs again after you thought that you had resolved the problem, use the dlnkmgr command's view operation to check the status of the HDLM program, and then do whatever is necessary to resolve the problem. For details on the view operation, see 6.7 view (Displays Information).
5. Troubleshooting 5.5 What To Do for Other Errors When the cause of an error may be related to HDLM but is neither a path error nor an HDLM program error, execute the DLMgetras utility to collect the HDLM error information, and then report the collected information to the HDLM vendor or maintenance company. For details about the DLMgetras utility and the information it collects, see 7.2 The DLMgetras Utility for Collecting HDLM Error Information.
Chapter 6. Command Reference This chapter describes the HDLM command (dlnkmgr) and its operations. 6.1 6.2 6.3 6.4 6.5 6.6 6.
6. Command Reference 6.1 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.
6. Command Reference • 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, see 4.1.6 Using Windows Server 2008. • To specify a value that contains a space in its parameter, enclose the entire value in double quotes (").
6. Command Reference 6.2 clear (Returns the Path Statistics to the Initial Value) The dlnkmgr command's clear operation clears the statistics (I/O count and I/O errors) of all paths that are managed by HDLM, and returns them to their initial value. 6.2.1 Format (1) To Set the Path Statistics to 0 dlnkmgr clear -pdst [-s] (2) To Display the Format of the clear Operation dlnkmgr clear -help 6.2.
6. Command Reference (2) To Display the Format of the clear Operation -help Displays the format of the clear operation. Example >dlnkmgr clear -help clear: Format dlnkmgr clear -pdst [-s] KAPL01001-I The HDLM command completed normally.
6. Command Reference 6.3 help (Displays the Operation Format) The dlnkmgr command's help operation displays the list of operations available for the HDLM command, or the format of individual operations. 6.3.1 Format dlnkmgr help [operation] [operation] ... 6.3.2 Parameter operation Specify the HDLM command operation whose format you want to know.
6. Command Reference online: Format dlnkmgr dlnkmgr dlnkmgr dlnkmgr dlnkmgr online [-path] [-s] online [-path] -hba HBAPortNumber.BusNumber [-s] online [-path] -cha -pathid AutoPATH_ID [-s] online [-path] [-pathid AutoPATH_ID] [-s] online [-path] [-hbaportwwn HBA_Port_WWN [-tid Target_ID -hlun Host_LUN]] [-s] Valid value AutoPATH_ID { 000000 - 999999 }(Decimal) Host_LUN { 0000 - FFFF }(Hexadecimal) offline: Format dlnkmgr offline [-path] -hba HBAPortNumber.
6. Command Reference 6.4 offline (Places Paths Offline) The dlnkmgr command's offline operation places online paths offline. Specify the paths to be placed offline by specifying an HBA port, CHA port, single path, or HBA port WWN. There must always be at least one online path accessing each LU. Placing too many paths offline might prevent paths from being able to switch if an error occurs. Before placing a path offline, use the view operation to check how many online paths remain.
6. Command Reference -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. Specify the host port number and bus number of the target HBA port: the numbers are found in the PathName field displayed using the view operation.
6. Command Reference 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. In this example, a path whose AutoPATH_ID is 000001 is connected to the target channel adapter port: >dlnkmgr offline -cha -pathid 000001 KAPL01055-I All the paths which pass the specified CHA port will be changed to the Offline(C) status.
6. Command Reference For host-LU-number, specify the host LU number portion of PathName. Leading zeroes can be omitted from the host LU number (0001 and 1 are the same value). To display HBAPortWWN and PathName, execute the view operation as follows: >dlnkmgr view -path -hbaportwwn For details on how to execute the view operation and display the HBA port WWN and path name, see (3) Parameters Used When Displaying Path Information in 6.7.2 Parameters.
6. Command Reference Example The following example shows how to display the format of the offline operation: >dlnkmgr offline -help offline: Format dlnkmgr offline [-path] -hba HBAPortNumber.
6. Command Reference The above command will display information pertaining to only those paths that pass through the specified channel adapter port. Note: When the LU dynamic deletion function is used, a path might be deleted due to an error. If this happens, when you attempt to change the path status, an error will occur. Confirm that the path of which you attempt to change the status has been deleted, and then resolve the path error. For details, see 4.7.2 Deleting an LU Dynamically.
6. Command Reference 6.5 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. 6.5.1 Format (1) To Place Paths Online dlnkmgr online [-path] [-hba host-port-number.
6. Command Reference Specify the host port number and bus number of the target HBA port: the numbers are found in the PathName field displayed using the view operation. Enter a period between these two parameter values. For details about the view operation, see 6.7 view (Displays Information). 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.
6. Command Reference KAPL01061-I 2 path(s) were successfully placed Online; 0 path(s) were not. Operation name = online > -pathid AutoPATH_ID 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 6.7 view (Displays Information).
6. Command Reference to the Online status. Is this OK? [y/n]: y KAPL01061-I 1 path(s) were successfully placed Online; 0 path(s) were not. Operation name = online -s Executes the command without displaying the message asking for confirmation of command execution from the user. Specify this parameter if you want to skip the response to the confirmation message: for example, when you want to execute the command in a shell script or batch file.
6. Command Reference > 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 6.7 view (Displays Information). We recommend that you use the following command and verify the information on the target paths before you execute the online operation to place online all the paths connected to a specific HBA port or channel adapter port.
6. Command Reference 6.6 set (Sets Up the Operating Environment) The dlnkmgr command's set operation sets the HDLM operating environment. 6.6.
6. Command Reference 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. Error log collection level 3 3 Collect error information for the Information level and higher. Collect error information for the Information level and higher.
6. Command Reference SMS series, Universal Storage Platform V/VM, Virtual Storage Platform, and the EMC DMX series. The conditions mentioned above will be used no matter what for the settings for the EMC DMX series, EMC CX series, and HP EVA series. For example, in a cluster environment, the load balancing function is disabled even if it is set to on for the EMC DMX series. For details on the cluster software supported by HDLM, see 2.14 Cluster Support.
6. Command Reference Value Description 2 Collects error information for the Warning or higher level. 3 Collects error information for the Information or higher level. 4 Collects error information for the Information or higher level (including maintenance information). The higher the error log collection level value, the more log information will be output. As the amount of log information that is output increases, the amount of time before existing information will be overwritten becomes shorter.
6. Command Reference indicates a file number of 1 or 2)), the number of log files is set at 2. -systflv trace-level Specify the trace output level. The trace files for which trace levels can be set are hdlmtrn.log (n indicates a file number from 1 to 64). Table 6-4: Trace Level Values shows the values of the trace level. The default is 0. If an error occurs, set the trace level to 1 or higher to collect the log information. Table 6-4: Trace Level Values Value Description 0 Does not output any trace.
6. Command Reference 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). -pchk {on [-intvl checking-interval]|off} Enables or disables path health checking. on: Enabled off: Disabled Path health checking checks all online paths.
6. Command Reference on: Enabled off: Disabled 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.
6. Command Reference error-monitoring-interval >= checking-interval-for-automatic-failback x number-of-times-error-is-to-occur-during-intermittent-error-monitoring If this condition is not satisfied, the KAPL01080-W message will be output and an error will occur. If this happens, change any of the following settings: the checking interval for automatic failbacks, the intermittent error-monitoring interval, or the number of times that the error is to occur.
6. Command Reference occur is reached during the monitoring interval. A path that is assumed to have an intermittent error is excluded from automatic failbacks. Intermittent error monitoring is performed on each path. Intermittent error monitoring starts when a path is recovered from an error by performing an automatic failback.
6. Command Reference after the next time an automatic failback is successful. Because the errors and elapsed time are not counted or measured while intermittent errors are not being monitored, the values will not change. The monitoring interval specified in this parameter is stored even though specifying -iem off disables intermittent error monitoring.
6. Command Reference that if you use the view -sys operation to display the HDLM functionality configuration, Intermittent Error Monitor will be shown as on. When the automatic failback function is returned to on, intermittent error monitoring will once again be enabled. The executable operations for the automatic failback function and intermittent error monitoring depend on the settings for those functions.
6. Command Reference Setting AFB Available operation IEM Set IEM to off. off off Result of operation on#2 off • IEM is disabled. • The error count, elapsed monitoring time, and information about paths not subject to automatic failbacks are cleared. Set AFB to on. The operations of AFB and IEM do not change. Change the AFB setting. AFB operates using new settings. Set AFB to off. AFB is disabled. Set IEM to on. IEM is enabled.#1 Set AFB to on. AFB and IEM are enabled.#1 Set AFB to off.
6. Command Reference -lic Specify this option for when a license is updated. The HDLM license is provided via a license key or license key file. A license key file is a file that stores the HDLM license key. If you use a license key file: Store the license key file named hdlm_license directly under the Windows installation drive, and then execute the set -lic operation.
6. Command Reference KAPL01071-I A permanent license was installed. > Example 2 The following example shows how to update the license key when the license key file does not exist: >dlnkmgr set -lic KAPL01049-I Would you like to execute the operation? Operation name = set [y/n]: y KAPL01083-I There is no license key file. File name =Windows-installation-destination-drive-name\hdlm_license KAPL01068-I Enter a license key:************* KAPL01071-I A permanent license was installed.
6. Command Reference Value Description on The LU is removed from HDLM-management when all the paths to the LU are disconnected. However, if an Offline(C) path is among the disconnected paths, the LU will not be deleted from HDLM-management. The deleted LU is restored after it is recovered from the physical failure and the disk is re-scanned. on -force The LU is removed from HDLM-management when all the paths to the LU are disconnected, even when an Offline(C) path is included.
6. Command Reference Indicating Audit Log Data Categories lists the values that indicate categories of audit log data. The default is all. Note that if you enter -category without specifying any category (ss, a, ca, or all), it is assumed that all is specified. Table 6-9: Values Indicating Audit Log Data Categories Value Explanation ss Audit log events of the StartStop category are collected. a Audit log events of the Authentication category are collected.
6.
6. Command Reference Interval-Time { 1 - 1440 }(Minute) (Default Value 1) Error-Monitor-Interval { 1 - 1440 }(Minute) (Default Value 30) Number-Of-Times { 1 - 99 }(Times) (Default Value 3) AudlogLevel { 0 - 7 } (Default Value 6) Category-Value { [ss] [a] [ca] | (afb) all } (Default Value all) KAPL01001-I The HDLM command completed normally.
6. Command Reference 6.7 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. 6.7.
6.
6. Command Reference 6.7.
6. Command Reference Parameter and program information to be displayed 246 Item Description Load Balance Settings for load balancing • Setting status: on: Enabled off: Disabled • Algorithm: 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.
6. Command Reference Parameter and program information to be displayed Item Number Of Trace Files Number of trace 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.
6.
6. Command Reference Parameter and program information to be displayed Item Audit Log Category Description The categories of audit log data to be output are displayed. When more than one category is displayed, commas (,) are used as separators. ss: StartStop a: Authentication ca: ConfigurationAccess If all the above categories are specified, all is displayed. If the collection of audit log data is disabled, a hyphen (-) is displayed.
6. Command Reference >dlnkmgr view -sys -msrv HDLM Manager Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss > Example 3 The following example shows how to display information about the HDLM alert driver: >dlnkmgr view -sys -adrv 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.
6. Command Reference >dlnkmgr view -sys -audlog Audit Log : off Audit Log Category : KAPL01001-I The HDLM command completed normally.
6. Command Reference #2 The EMC DMX series and the HP EVA series cannot be managed. -t Does not display the title for each information item. Example >dlnkmgr view -stinfo EMC Symmetrix DMX Series, CLARiiON CX Series : on HP StorageWorks EVA Series : on KAPL01001-I The HDLM command completed normally.
6. Command Reference the host device unless a drive letter has been assigned. The host-device-name string is case sensitive. If the command ends with the KAPL01064-W or KAPL01013-E message, follow the recommended action in the message.
6. Command Reference • When the only HDLM management-target devices are the Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP, Hitachi AMS2000/AMS/WMS/SMS series, Universal Storage Platform V/VM, or Virtual Storage Platform: 16 digits will be displayed for the iLU, even if this parameter is specified. -hbaportwwn Displays port WWN information for the HBAs connected to the storage system. -t Omits the title for each information item.
6. Command Reference When the -exlu parameter is specified: 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.
6. Command Reference Table 6-12: Items That Can Be Selected by the -path -item Parameter and the Sub-parameters Selectable items Sub-parameters PathID# None PathName pn HBAPortWWN hbaportwwn DskName dn iLU lu ChaPort cp Status# None Type type IO-Count ic IO-Errors ie DNum dnu HDevName hd IEP iep # Because both PathID and Status are always displayed, you do not have to specify any parameters.
6. Command Reference 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. -stname Use this parameter for the Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP, Hitachi AMS2000/AMS/WMS/SMS series, Universal Storage Platform V/VM, or Virtual Storage Platform to display the model ID of the storage system in the product ID element of the DskName field.
6. Command Reference 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 9900 series, Lightning 9900V series, Hitachi USP, Hitachi AMS2000/AMS/WMS/SMS series, Universal Storage Platform V/VM, or Virtual Storage Platform: 16 digits are displayed for the iLU even if this parameter is specified. -t Omits the title for each information item.
6. Command Reference Parameters to display a summary of path information: -path -c If the -c parameter is specified at the same time as the -path parameter, only PathID, DskName, iLU, CP, Status, and Type are displayed for the path information. The displayed contents are also shortened, so that each path information item is displayed on a single line. The items that are displayed are PathID, DskName, iLU, CP, Status, and Type.
6. Command Reference in the product ID element of the DskName field is limited to 10. When there are 11 or more characters in the product ID, the 8th and following characters are abbreviated to ellipses (...).
6. Command Reference Displayed path information Table 6-13: Displayed Path Informationdescribes 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.
6. Command Reference Displayed Item No summary displayed Description Summary displayed PathStatus Status of the displayed paths. The displayed status indicates the following: • Online: All paths are available. • Reduced: Some paths are not available. Reduced means that some paths might have an error status, in which case you should check the status of individual paths and resolve the problem for any paths that have an error status.
6. Command Reference Displayed Item No summary displayed Summary displayed DskName#1 DskName Description The storage system name, which identifies the storage system that is accessed by a path. A storage system name consists of the following three elements, separated by periods: • Vendor ID: The name of the storage system vendor (for example, HITACHI). • Product ID: Indicates the storage system product ID, emulation type, or model ID (for example, DF600F).
6. Command Reference Displayed Item Description No summary displayed Summary displayed iLU#1 iLU • For the Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP, Hitachi AMS2000/AMS/WMS/SMS series, Universal Storage Platform V/VM, and Hitachi Virtual Storage Platform: LU number of the storage system. This number combined with the storage system name (shown in DskName) identifies the LU that is accessed by a path.
6. Command Reference Displayed Item No summary displayed Description Summary displayed Status of the path • Online: Online • Offline(C): Placed offline using the Path Management window of the HDLM GUI or by a command • Offline(E): Offline due to an error • Online(E): Failure has occurred (If none of the paths accessing one LU have an Online status, one of those paths is changed to the Online(E) status.
6. Command Reference Displayed Item Description No summary displayed Summary displayed DNum#1 - When Dev indicates an entire LU, 0 is displayed. HDevName#1 - Host device name. 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.
6. Command Reference #3 The drive letter assigned to a dynamic disk volume is not displayed.
6.
6. Command Reference # • When a summary is displayed by specifying the -path -c parameter and there are 11 or more characters in the summary string, any 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).
6. Command Reference -pathid AutoPATH_ID Use this parameter to display only the information about the LU that is connected to the path with that specified AutoPATH_ID. -exlu • When an HDLM management-target device is the EMC DMX series, EMC CX series, or HP EVA series: If this parameter is specified, all 32 digits of the iLU are displayed instead of truncating the iLU to 13 digits.
6. Command Reference 000009 Online Product SerialNumber LUs : EMC : : 4 iLU HDevName PathID Status 6006048000018... L 000000 Online 000010 Online 6006048000018... M 000001 Online 000011 Online 6006048000018... N 000002 Online 000012 Online 6006048000018... O 000003 Online 000013 Online KAPL01001-I The HDLM command completed normally.
6. Command Reference iLU HDevName PathID Status 6006048000018781000153594D423031 L 000000 Online 000010 Online 6006048000018781000153594D423032 M 000001 Online 000011 Online 6006048000018781000153594D423033 N 000002 Online 000012 Online 6006048000018781000153594D423034 O 000003 Online 000013 Online KAPL01001-I The HDLM command completed normally.
6. Command Reference In the sub-parameters, -hdev or -pathid, you can filter the LU information to be displayed. If you omit both parameters, the command displays the information about all the LUs recognized by HDLM. For details on the contents of each displayed item, see Table 6-18: Displayed LU Information. The sub-parameters are: -hdev host-device-name Displays information only for the paths accessing the specified host device. Specify a drive letter to indicate the desired host device.
6. Command Reference Parameters to display a summary of LU information: -lu -c When the -c parameter is specified with the -lu parameter, a summary of LU configuration information is displayed on one line. The total number of paths recognized by HDLM and the number of online paths are displayed for each LU.
6. Command Reference 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.
6. Command Reference 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-18: Displayed LU Informationfor the contents of each displayed item.
6. Command Reference Displayed LU information Table 6-18: Displayed LU Information describes the displayed LU information. The following explains the table headings: • No summary displayed: The user specifies the -lu parameter or -lu -item parameter. • Summary displayed: The user specifies the -lu -c parameter or -lu -c -item parameter.
6. Command Reference Displayed item No summary displayed Description Summary displayed • For the Thunder 9500V series, Lightning 9900 series, Lightning 9900V series, Hitachi USP, Hitachi AMS2000/AMS/WMS/SMS series, Universal Storage Platform V/VM, and Hitachi Virtual Storage Platform: LU number in the storage system This number combined with the storage system name (shown in DskName) identifies the LU that is accessed by a path.
6. Command Reference Displayed item No summary displayed Description Summary displayed PathName#1 - The path name. When you modify the system configuration or replace a hardware item, you should check the path names to identify the path that will be affected by the change.
6. Command Reference Displayed item No summary displayed Description Summary displayed Status - Status of the path • Online: Online • Offline(C): Placed offline by using the Path Management window of the HDLM GUI or by a command • Offline(E): Offline due to an error • Online(E): Failure has occurred (If none of the paths accessing one LU have an Online status, one of those paths is changed to the Online(E) status.
6. Command Reference Displayed item No summary displayed Description Summary displayed IO-Errors#1 - Total I/O error count for a path. The maximum value that can be displayed is 232 - 1 (4294967295). If the total I/O error count reaches the maximum value, it is reset, and the count is re-started from 0. To reset the IO-Errors value to 0, execute the dlnkmgr command's clear operation. Executing the clear operation also clears the number of I/O operations (IO-Count) to 0.
6. Command Reference This information is displayed when one of the following conditions exist: - The user selected the item to be displayed by using the -lu -c -item parameter. - No value was specified for the parameter. #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.
Chapter 7. Utility Reference This chapter explains the utilities used by HDLM. 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.
7. Utility Reference 7.1 Overview of the Utilities HDLM provides the following utilities: • The DLMgetras utility for collecting HDLM error information When an error occurs, this utility collects the files that contain the information that you need to submit to your HDLM vendor or maintenance company. For details about the DLMgetras utility, see 7.2 The DLMgetras Utility for Collecting HDLM Error Information.
7. Utility Reference Administrators group. If you are executing the utilities in Windows Server 2008, see 4.1.6 Using Windows Server 2008.
7. Utility Reference 7.2 The DLMgetras Utility for Collecting HDLM Error Information This utility collects information that is needed to analyze HDLM errors that have occurred: information such as error logs, integrated trace files, trace files, definition files, and 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.
7. Utility Reference DLMgetras utility. The output-destination folders shown in Table 7-1: List of Error Information Collected by the DLMgetras Utility for Collecting Error Information are created in a folder of your choosing, and the information is then stored in the output-destination folders. -eventlogtime yyyy/mm/dd 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.
7. Utility Reference Folder that stores collected files#1 Files Explanation hdlmservicepack HDLM SP version number hdlmversion HDLM version number folder-to-which-collected-informa tion-is-output\HDLM-installation -destination-drive-name_\Progr dlmmgrn.log HDLM manager log (including the driver log) am Files\HITACHI\DynamicLink hcmdslicense2.log Log when updating the license Manager\log#2 hdlmtrn.log Trace file hs_err_pidnnnn.log Java execution log (nnnn indicates a process ID) setupact.
7. Utility Reference Folder that stores collected files#1 folder-to-which-collected-informa tion-is-output\HDLM-installation -destination-drive-name_\Progr am Files_\HITACHI\DynamicLin Files dlmgui_version HDLM GUI version and build numbers dlmmgr.xml HDLM configuration file dlmwebagent.properties Configuration file for Hitachi Command Suite Common Agent Component cluster.log MSCS log All files under logs Volume Manager log All files under log VCS log hntrn.
7. Utility Reference Folder that stores collected files#1 Files Explanation cluster-sys.txt MSCS information dirHdlmRoot.txt All the folders and the list of files in the HDLM installation destination folder dirSystemRoot.txt All the folders and the list of files in the Windows installation destination folder dlm_iscsims.txt#9 iSCSI information dlm-reg.txt Contents of the HDLM registry dlmmemorytraces.txt HDLM memory trace information dlmmgr-lic.
7. Utility Reference Folder that stores collected files#1 Files evSystem.evt#10 Explanation Event log for the system evSystem.log#10 wevSystem.evtx#4 wevSystem.txt#4 wevSetup.evtx#4 wevSetup.txt Event log for setup programs #4 HBA-reg.txt Registry setting information for HBAs hdlmdsm-status.txt HDLM driver information hntrlib-reg.txt Contents of the HNTRLib registry iscsi-reg.txt iSCSI registry information Localhost_Cluster.log#4 MSCS log mpio-list.txt MPIO information mpio-reg.
7. Utility Reference which collected information is output, or if the DLMgetras utility is executed from the Windows Start menu, the default for the folder to which collected information is output is Windows-installation-destination-drive\hdlmtemp\hdlmgetras_nn, where nn is a number from 00 to 99. #2 The underlined part indicates the folder specified during installation #3 In Windows Server 2008, files residing in %SystemRoot%\inf\ are also acquired.
7. Utility Reference product other than HDLM from which error information is to be collected is being used.
7. Utility Reference 7.3 The dlmpr Utility for Clearing HDLM Persistent Reservations The dlmpr utility clears the persistent reservation that is left in an LU after HDLM is uninstalled. However, a persistent reservation is not left in an LU when you uninstall HDLM as instructed by the procedure in this manual.
7. Utility Reference box, and then click the OK button. 4. In the Computer Management window, choose Device Manager. From the View menu, select Show hidden devices. Right-click Cluster Disk Driver from Non-Plug and Play Drivers in the right window, and then choose Disabled. The message Disabling this device will cause it to stop functioning. Do you really want to disable it? is displayed. Choose Yes. A message prompting you to restart the system is displayed. Choose Yes.
7. Utility Reference the LU you specified will be cleared. Please confirm that no other servers are accessing this LU. [y/n]:y KAPL10658-I The persistent reservation information of PathID = 0 was cleared. KAPL10640-I The dlmpr utility completed normally. 7. Choose Start, Settings, Control Panel, double-click Administrative Tool, and then double-click Computer Management. 8. Choose Services and Applications, and then double-click Services. A list of services is displayed.
7. Utility Reference 7.4 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. This utility is located in the following location: HDLM-installation-folder\bin 7.4.1 Format dlmprsvkey {-r [PRSV-key-to-be-specified-by-user][-s]| -v | -h} 7.4.
7. Utility Reference now start. Is this OK? [y/n]: y KAPL12106-I An attempt to register the PRSV key was successful. (PRSV key = 0123456789abcdef) In the following example, the utility registers the PRSV key by specifying it on the host: >dlmprsvkey -r 0123456789ABCDEF KAPL12104-I The operation for PRSV key registration will now start. Is this OK? [y/n]: y KAPL12106-I An attempt to register the PRSV key was successful.
7. Utility Reference 7.5 The dlmchkpath Utility for Checking HDLM Paths If you install or uninstall HDLM in a multi-path configuration, the disk might become corrupted. Use the dlmchkpath utility to check HDLM paths and to make sure that the system is in a single-path configuration. During an upgrade installation, a re-installation, or uninstallation of HDLM, the dlmchkpath utility is executed automatically.
7. Utility Reference >dlmchkpath -singleconnect KAPL12402-W iLU(0100) is in a multi-path configuration. PathID = 0,3 KAPL12402-W iLU(0101) is in a multi-path configuration. PathID = 1,4 KAPL12402-W iLU(0102) is in a multi-path configuration. PathID = 5,2 In the following example, the view operation is performed when the utility determines that the system is in a multi-path configuration. For details about the view operation, see 6.7 view (Displays Information).
7. Utility Reference 7.6 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.
7. Utility Reference Displays installation information. Example: Without specifying the -output parameter: >dlmhostinfo "installDirectory","C:\Program Files\Hitachi\DynamicLinkManager" "version","x.x.x-xx" KAPL13801-I The dlmhostinfo utility for confirming HDLM installation information completed normally. Table 7-2: Installation Information refers to the items that make up the output installation information, as shown below.
7. Utility Reference 7.7 The installhdlm Utility for Installing HDLM The installhdlm utility can perform a new installation, upgrade installation, or re-installation of HDLM in the unattended installation mode. How the utility should respond during an installation, and the HDLM function settings must be predefined in an installation-information settings file. You can also use this utility later to check the information that was set during installation.
7. Utility Reference storage_emc=n storage_eva=n HDLM_core=n For an explanation of each display item, see Table 7-3: Keys That Can Be Defined in the [INSTALLATION_SETTINGS] Section. -h Displays the format of the installhdlm utility. 7.7.3 Contents of an Installation-Information Settings File For information about setting the installation-information settings file, see 3.5.2 Preparations for Installing HDLM by Performing an Unattended Installation.
7. Utility Reference Key name Description Necessity of definition New installati on licensekeyfile Specify an absolute path to a license key file stored on the host.
7. Utility Reference Key name Description Necessity of definition New installati on Upgrade installati on or Re-insta llation Maximu m charact er length#1 storage_eva Specify whether to include the HP EVA series as possible management targets of HDLM. Specify either of the following values:#2 y: Include them as management targets. n: Do not include them as management targets. If this key is omitted • In Windows Server 2003, the two series are not included as management targets.
7. Utility Reference #2 If a value is not of an allowable type, an error will occur. #3 The value to be specified does not have to be enclosed within double quotation marks ("), even if the value includes space characters. #4 When you perform a new installation of HDLM, or when you perform an upgrade installation and the license is expired, you must prepare the license key file.
7. Utility Reference Table 7-4: Keys That Can Be Defined in the [ENVIRONMENT_SETTINGS] Section Key name#1 Description#2 Necessity of definition New installati on Upgrad e installati on or Re-insta llation Maximu m charact er length#3 load_balance Specify whether to enable load balancing by specifying either of the following values: on: Enable load balancing (default). off: Do not enable load balancing.
7. Utility Reference Key name#1 Description#2 Necessity of definition New installati on Upgrad e installati on or Re-insta llation Maximu m charact er length#3 trace_file_number Specify the maximum number of trace files (hdlmtr[1-64].log). You can specify a value from 2 to 64. The default is 4. Optional Optional 2 path_health_check Specify whether to enable path health checking by specifying either of the following values: on: Enable path health checking (default).
7. Utility Reference Key name#1 Description#2 Necessity of definition Maximu m charact er length#3 New installati on Upgrad e installati on or Re-insta llation Specify how many times an error needs to occur to cause HDLM to assume an intermittent error. You can specify a value from 1 to 99. The default is 3. Optional Optional 2 remove_lu Specify whether to enable the LU dynamic removal function by setting either of the following values: on: Enable the LU dynamic removal function.
7. Utility Reference Specifying an invalid value results in an error. For details about the function settings, see 6.6 set (Sets Up the Operating Environment). #3 If the value exceeds the maximum value, an error occurs.
7. Utility Reference intermittent_error_monitor=off #intermittent_error_monitor_interval=30 #intermittent_error_monitor_number=3 remove_lu=off remove_lu_force=off Note: • If a hash mark (#) is placed at the beginning of a line in the installation-information settings file, that line is assumed to be a comment. • If you do not want to specify a key or setting value, enter a hash mark (#) at the beginning of that particular line. 7.7.
7. Utility Reference 7.8 The uninstallhdlm Utility for Uninstalling HDLM The uninstallhdlm utility uninstalls HDLM. If you execute the uninstallhdlm utility with the -s parameter specified, no dialog boxes will be displayed during an unattended uninstallation. 7.8.1 Format uninstallhdlm [-s [-r] [-w work-folder] | -h] 7.8.2 Parameters -s [-r] [-w work-folder] Executes an unattended uninstallation. -r Restarts the host after an uninstallation. -w work-folder Specifies the folder to which uninstallhdlm.
7. Utility Reference the host, check the results of the HDLM uninstallation recorded in the uninstallhdlm.log file.
Chapter 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 8.15 Return Codes for Hitachi Command Suite Common Agent Component. 8.1 Before Viewing the List of Messages 8.2 KAPL01001 to KAPL02000 8.3 KAPL02001 to KAPL03000 8.4 KAPL03001 to KAPL04000 8.
8. Messages 8.1 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 8.2 KAPL01001 to KAPL02000. • Format and meaning of the message IDs • Terms used in the messages and message explanations This information is explained below. 8.1.1 Format and Meaning of Message IDs Each message has a message ID.
8. Messages 8.2 KAPL01001 to KAPL02000 KAPL01001-I The HDLM command completed normally. Operation name = aa...aa, completion time = bb...bb Details The HDLM command completed successfully. aa...aa: clear, help, offline, online, set, or view bb...bb: Year/month/day hour:minute:second Action None. KAPL01002-I The HDLM command started. Operation name = aa...aa Details The HDLM command was executed. aa...aa: clear, offline, online, set, or view Action None. KAPL01003-W No operation name is specified.
8. Messages KAPL01005-W A parameter is invalid. Operation name = aa...aa, parameter = bb...bb Details aa...aa: clear, set, online, offline, or view bb...bb: Specified parameter Action Execute help operation-name of the HDLM command (dlnkmgr) to check the parameter, and then retry. For details on the help operation, see 6.3 help (Displays the Operation Format). KAPL01006-W A necessary parameter is not specified. Operation name = aa...
8. Messages Specify the parameter value, and then retry. KAPL01009-W A parameter value is invalid. Operation name = aa...aa, parameter = bb...bb, parameter value = cc...cc, Valid value = dd...dd Details aa...aa: offline, online, set, or view bb...bb: Parameter name cc...cc: Specified parameter value dd...dd: Specifiable parameter value range Action Specify a correct value for the parameter, and then retry. KAPL01012-E Could not connect the HDLM manager. Operation name = aa...
8. Messages KAPL01014-W No authority to execute the HDLM command. Operation name = aa...aa Details You do not have the administrator permissions necessary to execute the HDLM command. aa...aa: clear, offline, online, set, or view Action Execute the command as a user with Administrators group permissions. KAPL01015-W The target HBA was not found. Operation name = aa...aa Details The path having the port number and path number specified in the -hba parameter could not be found. aa...
8. Messages aa...aa: view Action Execute the view operation of the HDLM command (dlnkmgr view -path) to check the value displayed in HDevName. Specify a host device for the value of HDevName, and then retry. For details on the view operation, see 6.7 view (Displays Information). KAPL01019-W The target path was not found. Operation name = aa...aa Details aa...aa: offline, online, or view • offline/online operation The specified path does not exist.
8. Messages Terminate unnecessary applications to increase the amount of free memory, and then try again. KAPL01023-W The last Online path for the device cannot be placed Offline(C). Details The path specified for the offline operation cannot be set to Offline(C) because it is the last, available path to the LU from the host. Action Use the view operation of the HDLM command (dlnkmgr) to check the status of the paths. For details on the view operation, see 6.7 view (Displays Information).
8. Messages Action Remove the error in the path, and then retry. KAPL01039-W During the online operation processing of the HDLM command, a path that cannot be placed in the Online status was detected. PathID = aa...aa Would you like to continue the processing of the online operation? [y/n]: Details A path that cannot be placed Online was detected during multi-path online processing. To ignore this path and perform online processing for the next path, enter y. To cancel processing, enter n. aa...
8. Messages Details The same parameter value is specified two or more times. aa...aa: view bb...bb: Parameter name cc...cc: Duplicate parameter value Action Delete the duplicate parameter value, and then retry. KAPL01045-W Too many parameter values are specified. Operation name = aa...aa, parameters = bb...bb, parameter value = cc...cc Details aa...aa: offline, online, set, or view bb...bb: Parameter name cc...
8. Messages 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...aa: Specified operation name Action Use the help operation of the HDLM command (dlnkmgr) to check the operation name. And then retry. For details on the help operation, see 6.3 help (Displays the Operation Format).
8. Messages 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. Action If you want to execute online processing, enter y.
8. Messages PathID = aa...aa Would you like to continue the processing of the offline operation? [y/n]: Details 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...aa: Path ID (decimal (base-10) number) Action If you want to continue processing the offline operation of the HDLM command for other paths, enter y.
8. Messages Details Multiple paths will be collectively placed Online because the -hba or -cha parameter has been specified. To continue processing, enter y. To cancel processing, enter n. aa...aa: CHA port or HBA Action If you want to execute online processing for the paths that meet the specified requirements, enter y. If you want to terminate processing, enter n. KAPL01058-W The specified parameter value is not needed. Operation name = aa...aa, parameter = bb...bb, parameter value = cc...
8. Messages see 6.3 help (Displays the Operation Format). KAPL01060-I The user terminated the operation. Operation name = aa...aa Details Command processing will be aborted because n was entered for a required confirmation. aa...aa: online, offline, set, or clear Action None. KAPL01061-I aa...aa path(s) were successfully placed bb...bb; cc...cc path(s) were not. Operation name = dd...dd Details This message indicates the number of the paths processed in an online/ offline operation. aa...
8. Messages cc...cc: The number of paths that were not successfully taken offline (decimal (base-10) number) dd...dd: offline Action For batch processing of registering paths, execute the view operation to check the registered paths. For details on the view operation, see 6.7 view (Displays Information). KAPL01063-I The target path(s) are already aa...aa. Details As a result of a previous online/offline operation, the specified path has already been set to Online/Offline(C). aa...
8. Messages 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.
8. Messages The license was renewed and is registered as a permanent license. Action None. KAPL01072-I The emergency license was installed. The license expires on aa...aa. Details A license was renewed and is registered as an emergency license. aa...aa: Year (4 digits)/month (01-12)/day (01-31) Action Install a permanent license by the expiration day. KAPL01073-E The temporary license expired. Details The temporary license has expired. Register a permanent license. Action Register a permanent license.
8. Messages You do not need to install a license because a permanent license has already been installed. Action None. KAPL01079-W The intermittent error monitoring function cannot be set up because automatic failback is disabled. Details The intermittent error monitoring function cannot be set up because automatic failbacks are disabled. Action Enable automatic failbacks, and then re-execute.
8. Messages Details There is no useable license key for HDLM in the license key file. aa...aa: Windows-installation-destination-drive-name\hdlm_license Action Make sure that the license key file is correct, and then re-execute. KAPL01083-I There is no license key file. File name = aa...aa Details There is no license key file in the designated folder: aa...
8. Messages which parameter can be specified, and then retry. For details on the help operation, see 6.3 help (Displays the Operation Format). KAPL01089-E One of the following was executed at the same time as an HDLM command set -lic operation: another set -lic operation, or an update of the license for an update installation. Action Check the license by using the HDLM command's view -sys -lic operation. If necessary, re-execute the HDLM command's set -lic operation.
8. Messages 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. To cancel the operation, enter n. Action If you want to execute the operation of the HDLM command, enter y. If you want to terminate processing, enter n. KAPL01098-W The storage subsystem (aa...aa, bb...
8. Messages Action Use the view operation of the HDLM command (dlnkmgr view -path -hbaportwwn) to check the target HBA port WWN. After that, specify the appropriate HBA port WWN, and then retry. KAPL01102-I All the paths which pass the specified aa...aa port will be changed to the Offline(C) status. 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.
8. Messages If you want to execute the online processing for the paths which pass the specified target, enter y. If you want to terminate the processing, enter n. KAPL01106-W One or more connected storage subsystem cannot use the load balancing function. Action None. KAPL01107-I The load balancing type specified for individual LUs will become invalid when this operation is executed.
8. Messages KAPL01115-W The audit log configuration file cannot be opened. Execute the "dlnkmgr view -sys -audlog" command and check whether a normal result is displayed. Details The audit log configuration file cannot be opened. Action If the dlnkmgr view -sys -audlog command does not display a normal result, contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. KAPL01116-W The audit log configuration file is invalid.
8. Messages KAPL01119-W An error occurred during processing to output the audit log configuration file. Details An internal parameter error when the audit-log data was output. Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL01120-W A storage subsystem model ID could not be displayed. Details = aa...aa, bb...bb Details A storage system model ID could not be displayed. aa...aa: Storage recognition information bb...
8. Messages 8.3 KAPL02001 to KAPL03000 KAPL02001-I HDLM GUI has started normally. java.version = aa...aa Details aa...aa: Version Action None. KAPL02002-I HDLM GUI has terminated. Action None. KAPL02003-E You lack permission to start HDLM GUI. Action Execute the command as a user with Administrators group permissions or as an Administrator. KAPL02004-E An error occurred during internal processing of HDLM GUI. HDLM GUI cannot start. Details = aa...
8. Messages DLMgetras Utility for Collecting HDLM Error Information. KAPL02005-E An attempt to start HDLM GUI has failed due to insufficient memory. Details There is not enough memory to use the HDLM GUI. Action Terminate unnecessary applications to increase the amount of free memory, or restart the host. KAPL02006-W No path was detected. Details The target path could not be found. Action Set up a path between the host and storage system, and then restart the host.
8. Messages 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. Details aa...aa: Operation (character string) • Export CSV • Define Option Information • Refresh • Clear Data Action None. KAPL02014-W No data has been input in aa...aa.
8. Messages • Error Log File Size • Monitoring Interval • Number of times • Error Log Number of Files • Trace File Size • Trace Number of Files Action Data has not been input for the specified item. See 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...
8. Messages • Path Health Checking Interval • Auto Failback Checking Interval • Error Log File Size • Monitoring Interval • Number of times • Error Log Number of Files • Trace File Size • Trace Number of Files Action See the HDLM GUI Help to specify a number within the valid range. KAPL02017-I The currently selected paths will be changed to the Online status. Is this OK? [OK/Cancel] Details The currently selected paths will be changed to the Online status. If you want to continue, click OK.
8. Messages The currently selected paths will be changed to the Offline(C) status. If you want to continue, click OK. If you do not want to proceed, click Cancel. Action If you want to execute offline processing, click OK. To cancel offline processing, click Cancel. KAPL02020-I If you are sure that there would be no problem when the path is placed in the Offline(C) status, click OK. Otherwise, click Cancel.
8. Messages Action If you want to continue online processing, click OK. To cancel online processing, click Cancel. For the paths in which online processing failed, correct the problem, and then re-execute online processing. KAPL02023-W A path that cannot be placed in the Offline(C) status has been detected. PathID = aa...
8. Messages KAPL02027-E The last Online path or Online(E) path to the LU cannot be placed in the Offline(C) status. PathID = aa...aa Details The path specified for offline processing cannot be placed Offline(C) because it is the last, remaining path connected to the LU. aa...aa: Path ID (decimal (base-10) number) Action Click Refresh to update the contents of the view operation, check the path status, and then retry. KAPL02028-W You lack write permission for the aa...aa.
8. Messages • Get HDLM Driver Status • Get HDLM Alert Driver Status bb...bb: Issuing API name (character string) • JHSPGetOption • JHSPSetOption • JHSPOnlinePath • JHSPOfflinePath • JHSPGetPathBy • JHSPClearStatistics • JHSPGetManagerStatus • JHSPGetDriverStatus • JHSPGetADriverStatus • JHSPGetClusterService 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.
8. Messages • Set Option Information • Get HDLM Manager Status • Get HDLM Driver Status • Get HDLM Alert Driver Status Action 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...
8. Messages aa...aa: Path ID (decimal (base-10) number) Action Remove the error in the path, and then retry. KAPL02041-W The cluster support function is active, so the load balancing function is not supported. Details The load balancing function cannot be enabled because MSCS is installed. Action The load balancing function is not supported in an environment where MSCS is installed. If you want to use the load balancing function, uninstall MSCS. KAPL02042-E An unexpected error occurred.
8. Messages The existing file will be overwritten. To continue, click OK. Otherwise, click Cancel. aa...aa: File name Action To overwrite the existing file, click OK. Otherwise, click Cancel. KAPL02052-W The HDLM manager could not be connected. Details The HDLM manager could not be accessed when the HDLM GUI was started. Action Execute the view operation of the HDLM command (dlnkmgr) to check whether the HDLM manager has started.
8. Messages KAPL02055-I The target path(s) are already aa...aa. Details The specified paths are already Online/Offline(C), as a result of the online/ offline operation that was just executed. aa...aa: Online or Offline(C) Action Click Refresh to check the status of the path. KAPL02058-E The configuration does not support the simultaneous use of the load balancing and cluster support functions.
8. Messages After confirming that the paths are not currently being reconfigured, click the Refresh button. KAPL02063-W The version number cannot be displayed. Details The version number could not be acquired because an attempt to read a parameter file, which starts up the HDLM GUI, failed. Action The version number cannot be displayed, but HDLM GUI operations can be executed. If you want to display the version number, reinstall HDLM.
8. Messages The HDLM version information could not be acquired. aa...aa: Code showing the reason for the error Action Re-execute the command. If the same error occurs again, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. KAPL02077-W An attempt to acquire the Service Pack version information failed. Details = aa...aa Details aa...
8. Messages Details During the GUI startup, an error occurred that was plrobably not a result of a user operation. aa...aa: Executed function name (character string) bb...bb: Return value of function (decimal (base-10) number) cc...cc: Information detailing where the failure occurred (character string) Action Re-execute the command.
8. Messages aa...aa: Trace information Action None.
8. Messages 8.4 KAPL03001 to KAPL04000 KAPL03001-I HDLM API information - aa...aa 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...aa: API trace information Action Refer to the contents of the warning. KAPL03003-E HDLM API Error information - aa...aa Details This information is required for resolving problems. aa...
8. Messages 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 7.2 The DLMgetras Utility for Collecting HDLM Error Information. KAPL03006-E An access to the HDLM driver causes an error. (aa...aa) Details This information is required for resolving problems. aa...
8. Messages KAPL03999-E An unexpected error occurred. Details Conflicting versions of HDLM modules are being used. 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 7.2 The DLMgetras Utility for Collecting HDLM Error Information.
8. Messages 8.5 KAPL04001 to KAPL05000 KAPL04001-I HDLM manager started. Action None. KAPL04002-E Could not start the HDLM manager. Details The HDLM manager failed to start because the current environment is unsuitable for the HDLM manager to run in. Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see 7.
8. Messages Action The HDLM manager starts as a service and as such, to start HDLM from the command line, use the net start DLMManager command. KAPL04006-E Cannot register the service control handler function. Return value = aa...aa Details HDLM manager could not start normally because it was unable to register the service control handler function. aa...aa: OS error code Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
8. Messages Details HDLM manager could not start normally because some of the definitions in the option definition file were invalid. Action If the KAPL04033-W message is output after this message, execute the dlnkmgr view -sys -sfunc command, and then check the option settings. Use the dlnkmgr set operation to return options settings back to where you had them. If the KAPL04033-W message is not output, restart HDLM manager. If the same error occurs, re-install HDLM.
8. Messages 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 7.2 The DLMgetras Utility for Collecting HDLM Error Information. KAPL04013-E Input is impossible via the communication pipe. RC = aa...aa Details Data could not be read from the pipe file while communicating with an HDLM command. aa...
8. Messages KAPL04021-I HDLM manager information - aa...aa Details This information is required for resolving problems. aa...aa: HDLM manager trace information Action None. KAPL04022-W HDLM manager warning information - aa...aa Details This information is required for resolving problems. aa...
8. Messages 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 7.2 The DLMgetras Utility for Collecting HDLM Error Information. KAPL04025-C A memory shortage occurred in the HDLM manager. Details There was not enough memory to run the HDLM manager processes.
8. Messages Install a permanent license. KAPL04030-E The temporary license has already expired. Action Install a permanent license. KAPL04031-E The emergency license has already expired. Action Install a permanent license. KAPL04032-C A fatal error occurred in HDLM. The system environment is invalid Details A part of the HDLM configuration file is missing. Action Re-install HDLM. KAPL04033-W The option definition file was re-created.
8. Messages KAPL04035-I The path health check will now start. Total number of paths = aa...aa Details aa...aa: Total number of paths Action None. KAPL04036-I The path health check for the path aa...aa was executed. Number of error paths = bb...bb Details aa...aa: Number of paths targeted 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...
8. Messages aa...aa: Trap ID bb...bb: Destination IP address of the trap cc...cc: Destination port number of the trap dd...dd: Community name given to the trap ee...ee: Transmission data Action None.
8. Messages 8.6 KAPL05001 to KAPL06000 KAPL05001-I DriverEntry() started. Details The initialization function was executed. Action None. KAPL05002-I DriverEntry() completed normally. Details The initialization function completed successfully. Action None. KAPL05003-I The HDLM driver (filter component) was successfully attached to Disk (aa...aa), Partition (bb...bb). Details aa...aa: Disk sequence number (decimal (base-10) number) bb...
8. Messages None. KAPL05005-I The control function (aa...aa) for the HDLM driver (filter component) was initialized successfully. Details The HDLM driver (filter component) was successfully initialized for each device object. aa...aa: Device object address (hexadecimal number) Action None. KAPL05008-E Could not allocate memory. (aa...aa:bb...bb) Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company.
8. Messages 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...
8. Messages Details aa...aa: Path ID (hexadecimal 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 path (aa...aa) failed.(bb...bb,cc...cc,dd...dd) Details aa...aa: Path ID (hexadecimal number) bb...bb: Disk sequence number (decimal (base-10) number) cc...cc: Degree of progress in disk recognition processing (hexadecimal number) dd...
8. Messages company. Refer to the HDLM User's Guide for instructions how to execute the DLMgetras utility. Details When the LU deletion function is enabled, path information is output to the event log. Removed path information is displayed in the event viewer with the following format: PathID PathName DskName iLU ChaPort When a path is added to an LU, this message might appear. Note that this message is output by Windows activities, and not as a result of an error.
8. Messages 8.7 KAPL07001 to KAPL08000 KAPL07819-I Data for maintenance: aa...aa bb...bb cc...cc dd...dd. Details This message is generated by the core logic for maintenance. aa...aa: Detailed information 1 (decimal (base-10) number) bb...bb: Internal function number of the core logic (decimal (base-10) number) cc...cc: Detailed information 2 (decimal (base-10) number) dd...dd: Detailed information 3 (decimal (base-10) number) Action None.
8. Messages KAPL07822-W An LU connected to PathID (aa...aa) cannot use the load balancing function in a cluster configuration. Details The LU connected to the PathID aa...aa is part of a storage system that cannot use persistent reservations. In a cluster configuration, the load balancing function cannot be used for this kind of LU. aa...aa: Path ID (same as PathID of view -path) (decimal (base-10) number) Action None. KAPL07823-W An LU connected to PathID (aa...
8. Messages 8.8 KAPL08001 to KAPL09000 KAPL08019-E The path (aa...aa) detected an error (bb...bb). (cc...cc) Details An error occurred in the path. The error is most likely due to a disconnected cable. aa...aa: Path identifier (hexadecimal number) bb...bb: Error code (hexadecimal number) • When the Windows plug-and-play 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.
8. Messages bb...bb: Path ID (same as PathID of view -path) (decimal (base-10) number) cc...cc: Host port number (same as PathName of view -path) (hexadecimal number) dd...dd: Bus number (same as PathName of view -path) (hexadecimal number) ee...ee: Target ID (same as PathName of view -path) (hexadecimal number) ff...ff: HLU number (same as PathName of view -path) (hexadecimal number) gg...gg: Dev number (same as DNum of view -path) (decimal (base-10) number) hh...
8. Messages paths is recovered. aa...aa: Path ID(same as PathID of view -path) (decimal (base-10) number) Action None. KAPL08026-E An error occurred on all the paths of the LU. PathID = aa...aa Details An error occurred in the last, remaining path of an LU. (This is most likely as a result of a disconnection.) aa...
8. Messages 8.9 KAPL09001 to KAPL10000 KAPL09001-E There is no system management permission. Login with administrator permission and aa...aa HDLM. Details The current user does not have the necessary administrator permission to install or uninstall HDLM. aa...aa: re-install or re-uninstall Action Re-install or re-uninstall HDLM as a user who is a member of the Administrators group. KAPL09002-E The disk does not have sufficient free space.
8. Messages No. I will restart my computer later check box. KAPL09005-E Could not stop the HDLM manager. Stop it manually, and then try the installation program or the uninstallation program again. Details An attempt to stop the HDLM manager service has failed. Action Stop the HDLM manager manually, and then try the installation program or the uninstallation program again. KAPL09006-E Could not install HDLM. Action If the installation was interrupted, incomplete files and folders might remain.
8. Messages KAPL09010-E You cannot install onto storage media that is not a built-in disk. Action Install HDLM onto a built-in disk. KAPL09014-E The OS must be restarted before you install HDLM. Action Restart the OS before HDLM is installed. KAPL09015-E HDLM cannot be installed. A newer version of HDLM is already installed. Action Uninstall HDLM, and then restart the installation program. KAPL09016-E Because HDLM has been installed in another system, HDLM cannot be installed in this system.
8. Messages KAPL09020-E An attempt to uninstall Hitachi Network Objectplaza Trace Library 2 failed. Details An attempt to uninstall HNTRLib2 has failed. Action Manually uninstall Hitachi Network Objectplaza Trace Library 2. If the attempt to uninstall Hitachi Network Objectplaza Trace Library 2 fails again, contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM.
8. Messages Action Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM. KAPL09071-E The specified installation folder is read-only. Specify a different folder. Details Since the install folder you specified is read-only, you cannot install. Action Specify an installation folder that is not read-only. KAPL09076-I The permanent license was installed. Action None. KAPL09077-I The temporary license was installed. The license expires on aa...aa.
8. Messages None. KAPL09080-I The temporary license has been installed. The license expires on aa...aa. 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 installed. The license expires on aa...aa. Details aa...aa: Year (4 digits)/month (01-12)/day (01-31) Action Install a permanent license by the expiration day. KAPL09082-W The temporary license expired. Action Enter a permanent license key.
8. Messages Action Install a permanent license. KAPL09086-W The entered license key is invalid. Action Enter a valid license key. KAPL09087-E The entered license key is invalid. Renewal of the license key will now stop. Obtain a valid license key, and then re-install HDLM. Details The renewal of the license key will be aborted because an invalid license key was entered three times in a row. Action Obtain a valid license key, and then re-install HDLM. KAPL09088-E The entered license key is invalid.
8. Messages Install a permanent license at a later time. KAPL09091-E A fatal error occurred in HDLM. The system environment is invalid. Contact your HDLM vendor or the maintenance company if there is a maintenance contract of HDLM. Details A part of the HDLM configuration file is missing. Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract of HDLM. KAPL09093-I aa...aa will be installed. Is this OK? Details aa...aa: SP version that will be installed.
8. Messages 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-installation-destination-drive-name\hdlm_license or the-file-that-the-user-specified Action Store a correct license key file in the designated directory, and then re-execute the installation program. KAPL09119-W There is no installable license key in the license key file. File name = aa...
8. Messages In this case, the following message is not displayed: Driver aa...aa has already been installed. The file version is bb...bb is not displayed. aa...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.
8. Messages KAPL09134-E The HDLM path cannot be added to the Path environment variable. Refer to the Messages section of the HDLM User's Guide for instructions to correct this problem. Details The HDLM path could not be added to the Path environment variable. Action Edit the Path environment variable so that it stays within the following length after adding the HDLM paths.
8.
8. Messages When linkage is performed with Global Link Manager, cancel remote access. If this message is still output, execute the hbsasrv stop -f command as shown in the Hitachi Global Link Manager Software Installation and Configuration Guide. Then, install or uninstall HDLM again as necessary. KAPL09173-W HDLM version aa...aa is installed. Do you want to overwrite it with version bb...bb? Details aa...aa: Installed version number of HDLM (character string) bb...
8. Messages 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 uninstallation of HDLM failed. aa...aa: install or uninstall bb...bb: Version number of HDLM you attempted to install or uninstall Action See the previous warning and error messages to resolve the problems. KAPL09183-I HDLM version aa...aa is installed. This version will now be overwritten with version bb...bb. Details aa...
8. Messages Action • In installhdlm utility for installing HDLM: Restart the computer and make sure that HDLM is running correctly. • In uninstallhdlm utility for uninstalling 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.
8. Messages for uninstalling HDLM. Action Make sure that the parameters for the installhdlm or uninstallhdlm utilities are appropriate, and then try again. For details on the installhdlm utility, see 7.7 The installhdlm Utility for Installing HDLM. For details on the uninstallhdlm utility, see 7.8 The uninstallhdlm Utility for Uninstalling HDLM. KAPL09189-W The parameter contains an incorrect value. (Value = aa...
8. Messages Make sure that the path name of the installation-information settings file is appropriate, and then try again. KAPL09192-W An installation information settings file of an unsupported product version is specified. (hdlmversion = aa...aa) Details The specified installation-information settings file is not supported by this version of HDLM. aa...
8. Messages KAPL09195-W The setup.exe file does not exist. Details HDLM cannot be installed, because the installation program (setup.exe) does not exist in the folder that is specified in the installfile_location key. Action Specify drive-in-which-the-installation-DVD-is-inserted:\HDLM_Windows\ in the installfile_location key of the installation-information settings file. KAPL09196-W Some of the LUs managed by HDLM are not in a single path configuration.
8. Messages bb...bb: Detailed information (decimal (base-10) number) Action Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM. KAPL09210-I aa...aa will now start. Details aa...aa has just started. aa...aa: dlnkmgr Action None. KAPL09211-I aa...aa completed successfully. Details aa...aa: dlnkmgr Action None. KAPL09212-E aa...aa ended abnormally. Details aa...
8. Messages KAPL09216-E An error occurred during I/O of a file that aa...aa uses. Error Code = bb...bb cc...cc Details An error occurred during an I/O from a file that the installhdlm utility for installing HDLM or the uninstallhdlm utility for uninstalling HDLM uses. aa...aa: installhdlm or uninstallhdlm bb...bb: Error number that indicates the executed processing (decimal (base-10) number) cc...
8. Messages aa...aa: Feature that has not been installed • If the value of aa...aa is HDLM GUI: The HDLM GUI cannot be used. • If Hitachi Command Suite Common Agent Component is used: HDLM cannot be managed from Global Link Manager. • If the value of aa...aa is MPIO Setting: An MPIO setting managed by Windows Management Instrumentation (WMI) has not been changed. Action Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM.
8. Messages KAPL09253-W y cannot be specified in the HDLM_core key when all HDLM components are installed. Details In an environment where all HDLM components have been installed, HDLM cannot be reinstalled or upgraded using the HDLM Core installation option. Action To install HDLM using the HDLM Core installation option in an environment where all the HDLM components have already been installed, uninstall everything and then perform a new installation of HDLM.
8. Messages If you are not sure which search paths were specified during the installation of Windows, contact Microsoft. KAPL09257-W HDLM cannot be installed on a system where MPIO aa...aa has already been installed. Delete the MPIO aa...aa setup information files (the INF files) from the system, and then continue the installation. Details There is an mpio.sys file in the %SystemRoot%\system32\drivers folder whose version is newer than any of the versions that HDLM supports. aa...
8. Messages None. KAPL09260-W Errors were detected during the HDLM aa...aa installation check. See the previous messages to resolve the problems. Details Errors were detected during the HDLM installation check. aa...aa: Version of HDLM that will be installed Action See the previous warning and error messages to resolve the problems. KAPL09261-I A permanent license will be installed. Action None. KAPL09262-I A temporary license will be installed. The license expires on aa...aa.
8. Messages KAPL09265-I A temporary license (excluding HDLM Light) will be installed. The license expires on aa...aa. Details A temporary license (excluding HDLM Light) will be installed. aa...aa: Year (4 digits)/Month (01-12)/Day (01-31) Action None. KAPL09266-I A emergency license (excluding HDLM Light) will be installed. The license expires on aa...aa. Details A emergency license (excluding HDLM Light) will be installed. aa...aa: Year (4 digits)/Month (01-12)/Day (01-31) Action None.
8. Messages aa...aa: HDLM installation folder Action To execute a silent installation, use drive-to-which-the-installation-DVD-is-inserted:\HDLM_Windows\DLMTools\ installhdlm.exe. KAPL09284-W HDLM is not installed. Details If HDLM is not installed, the installhdlm utility for installing HDLM cannot be executed with the -v parameter. Action None. KAPL09501-E HDLM is not installed on this system. Details An SP cannot be applied because HDLM is not installed on the system.
8. Messages installed HDLM or SP. When installing HDLM: First uninstall the installed HDLM or SP, and then perform a new installation. When installing a SP: Obtain, and then install an SP or corrected version that can be applied to the installed version of HDLM. KAPL09509-E Service Pack aa...aa cannot be installed. The same version has already been installed. Details The version of the SP being installed is the same as the already installed SP. Installation of the SP has stopped. aa...
8. Messages 8.10 KAPL10001 to KAPL11000 KAPL10002-W Too many parameters have been specified. 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 7.2 The DLMgetras Utility for Collecting HDLM Error Information. KAPL10003-W The first parameter has not been set to a directory. Value = aa...
8. Messages Action The specified folder already exists. Enter y to overwrite the existing file. Enter n or press any other key to terminate the DLMgetras utility for collecting HDLM error information, without executing it. For details on the DLMgetras utility, see 7.2 The DLMgetras Utility for Collecting HDLM Error Information. KAPL10012-W The specified file or directory does not exist. Line = aa...aa, Value = bb...
8. Messages aa...aa: Collected file name bb...bb: Year/month/day hour:minute:second Action None. KAPL10022-I The utility for collecting HDLM error information completed normally. Details Error information has been collected. Action None. For details on the DLMgetras utility, see 7.2 The DLMgetras Utility for Collecting HDLM Error Information. KAPL10030-I A user terminated the utility for collecting HDLM error information.
8. Messages Re-execute the DLMgetras utility. For details on the DLMgetras utility, see 7.2 The DLMgetras Utility for Collecting HDLM Error Information. KAPL10033-W The file does not exist. Filename = aa...aa Details No file to collect information exists. aa...aa: Information collection file Action None. KAPL10034-E The file could not be copied. Filename = aa...aa, Details = bb...bb Details Execution of the cp command failed. aa...aa: File name you tried to copy bb...
8. Messages 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. KAPL10045-W A parameter is invalid. Details The specified parameter is invalid.
8. Messages error information are appropriate, and then try again. KAPL10048-E An error occurred in internal processing of the utility for collecting HDLM error information. Details = aa...aa, bb...bb Details aa...aa: Error number (character string) bb...bb: Error number (character string) Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL10080-I Data for maintenance: aa...aa bb...bb cc...cc dd...dd Details aa...aa: Maintenance information bb...
8. Messages Action None. For details on the dlmpr utility, see 7.3 The dlmpr Utility for Clearing HDLM Persistent Reservations. KAPL10644-W The specified parameters cannot be specified at the same time. parameter = aa...aa Details aa...aa: Specified parameter (character string) Action Execute the dlmpr utility for clearing HDLM persistent reservation with the -h parameter to check the parameter, and then retry. For details on the dlmpr utility, see 7.
8. Messages KAPL10652-E The entered value is invalid. The operation stops Details An invalid response to a request was entered three times in a row. Action Re-execute the dlmpr utility. KAPL10653-W The entered value is invalid. Please Re-enter it [y/n]: Action Enter y or n. KAPL10654-W The parameter (aa...aa) cannot be not specified alone. Action Specify the correct value for the parameter, and then retry.
8. Messages We recommend that you report the effects of using the utility to the user for confirmation. Action To clear the LU reservation, enter y. Enter n to cancel. KAPL10658-I The persistent reservation information of PathID = aa...aa was cleared. Details aa...aa: The path ID (decimal (base-10) number) Action None. KAPL10659-I There is no LU for which persistent reservation information exists. Action None. KAPL10660-I There is no LU managed by HDLM. Action None.
8. Messages • An LU was disconnected from the server during execution of a utility. KAPL10662-E Free memory is insufficient. Action 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.
8. Messages Action None. KAPL10667-C An attempt to the get physical drive number failed. LU = aa...aa Details An LU without a physical drive number existed. aa...aa: LU number Action If the following condition is satisfied, contact your HDLM vendor or maintenance company if you have a maintenance contract for HDLM. - The cluster system service and the driver are running. KAPL10668-E An attempt to open a device failed. DeviceName = aa...aa Details aa...
8. Messages 8.11 KAPL11001 to KAPL12000 KAPL11901-I aa...aa has started. Details The operation has started on the host. aa...aa : Operation (character string) • Get Path Information • Get Option Information • Set Option Information • Clear Data • Get HDLM Manager Status • Get HDLM Driver Status • Get HDLM Alert Driver Status • Get SNMP Trap Information • Set SNMP Trap Information • Set LU Load Balance • Get Path Status Log Information • Get Local Time Action None. KAPL11902-I aa...aa has started.
8. Messages None. KAPL11903-I aa...aa has completed normally. Details The operation has completed normally on the host. aa...aa: Any of the following operations (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 • Get Local Time Action None.
8. Messages • 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 bb...bb: Error status returned from API (character string) Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if you have a maintenance contract for HDLM.
8. Messages 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. aa...aa: XML information (character string) Action None.
8. Messages 8.12 KAPL12001 to KAPL13000 KAPL12101-W A parameter has not been specified. Action Make sure that the parameters for the dlmprsvkey utility for registering an HDLM persistent reservation key are appropriate, and then try again. For details on the dlmprsvkey utility, see 7.4 The dlmprsvkey Utility for Registering an HDLM Persistent Reservation Key.
8. Messages Action To execute the operation, enter y. To stop the operation, enter n. KAPL12105-W The user does not have permission to execute the utility for registering HDLM persistent reservation key. Details The dlmprsvkey utility for registering an HDLM persistent reservation key must be executed by a user who is a member of the Administrators group. Action Try again as a user who is a member of the Administrators group. For details on the dlmprsvkey utility, see 7.
8. Messages Registering an HDLM Persistent Reservation Key. KAPL12110-W The entered value is invalid. Processing of the utility for registering the HDLM persistent reservation key will now terminate. Details Processing of the dlmprsvkey utility for registering an HDLM persistent reservation key will now stop, because an invalid response was made three times in a row for the response request. Action Re-execute the dlmprsvkey utility. For details on the dlmprsvkey utility, see 7.
8. Messages KAPL12113-E An attempt to acquire the PRSV key has failed. Details An attempt to acquire the PRSV key from the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HDLMds m\Parameters\PRSVKeyString failed when the dlmprsvkey utility for registering an HDLM persistent reservation key was executed with -v specified. Action If the PRSV key was not registered using the dlmprsvkey utility, register the PRSV key, and then re-execute the utility with the -v option.
8. Messages None. KAPL12117-I Trace data for maintenance: registered PRSV key = aa...aa Details Output when PRSV key registration is successful. aa...aa contains the PRSV key (hexadecimal number). Message for trace logs. Action None. KAPL12118-E Trace data for maintenance: aa...aa bb...bb cc...cc dd...
8. Messages KAPL12150-W An error occurred during internal processing of HDLM Performance Monitor. HDLM Performance Monitor cannot start. Details = aa...aa Details An attempt to start HDLM Performance Monitor has failed. There might not be enough memory or the host might be under a heavy load. This message might also be output when the WMI repository is corrupted. aa...aa: Error details (character string) Action Check the system status.
8. Messages There might not be enough memory or the host might be under a heavy load. This message might also be output when the WMI repository is corrupted. aa...aa: Internal processing name (character string) bb...bb: Error code (decimal (base-10) number) Action Check the system status. If this message is output repeatedly, contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. If the WMI repository is corrupted, consider rebuilding the repository.
8. Messages Details aa...aa: Specified parameter Action Execute the dlmchkpath utility for checking HDLM paths with the -h parameter to check the parameter, and then retry. For details on the dlmchkpath utility, see 7.5 The dlmchkpath Utility for Checking HDLM Paths. KAPL12405-E Cannot execute the utility for checking HDLM paths due to insufficient memory. Details Not enough memory could be allocated for the dlmchkpath utility for checking HDLM paths.
8. Messages 8.13 KAPL13001 to KAPL14000 KAPL13601-W The audit log configuration file does not exist. Execute the "dlnkmgr view -sys -audlog" command and check the setting. Details The audit log configuration file does not exist. Action Restart the HDLM manager, execute the dlnkmgr view -sys -audlog command, and then specify any desired settings by using the dlnkmgr set -audlog command. KAPL13602-W The audit log configuration file cannot be opened.
8. Messages 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. Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL13606-W An error occurred during processing to output the audit log configuration file.
8. Messages message. KAPL13803-W The user does not have the privileges required to execute the dlmhostinfo utility for confirming HDLM installation information. Details The dlmhostinfo utility must be executed by a user with Administrator group privileges. Action Re-execute the dlmhostinfo utility as a user with Administrator group privileges. KAPL13804-W Too many parameters have been specified. Details Three or more parameters have been specified.
8. Messages Details The dlmhostinfo utility for confirming HDLM installation information cannot be executed if HDLM is not installed. Action None. KAPL13808-W An attempt to create the installation information file has failed. Code = aa...aa Details aa...aa: Error code (decimal number) The installation information file will not be created if any of the following conditions are met: • The installation information file already exists.
8. Messages 8.14 KAPL15001 to KAPL16000 KAPL15010-W The HDLM utility was executed by the user who does not have the authority. Command Line = aa...aa Details aa...aa: Name of the utility that the user executed KAPL15030-I An HDLM persistent reservation key was successfully registered. Command Line = aa...aa Details aa...aa: Name of the utility that the user executed KAPL15031-W An attempt to register an HDLM persistent reservation key has failed. Command Line = aa...aa Details aa...
8. Messages KAPL15035-W An attempt to display the status that indicates whether paths are in an individual or multiple path configuration has failed. Command Line = aa...aa Details aa...aa: Name of the utility that the user executed KAPL15060-I DLMgetras was invoked. Command Line = aa...aa Details aa...aa: Name of the utility that the user executed KAPL15061-I DLMgetras successfully executed. Command Line = aa...aa Details aa...
8. Messages bb...bb: Online or Offline(c) cc...cc: Command that the user executed KAPL15105-I Setting up the operating environment succeeded. Command Line = aa...aa Details aa...aa: Command that the user executed KAPL15106-W Setting up the operating environment failed. Command Line = aa...aa Details aa...aa: Command that the user executed KAPL15107-I Program information was successfully displayed. Command Line = aa...aa Details aa...
8. Messages aa...aa: Command that the user executed KAPL15201-I HDLM GUI has started successfully. KAPL15202-I HDLM GUI has terminated. KAPL15203-W HDLM GUI was executed by the user who does not have the authority. KAPL15204-W HDLM GUI has not started successfully. KAPL15205-I aa...aa has completed successfully. Details aa...aa: Refresh, Clear Data, Export CSV, Get Option Information, or Set Option Information KAPL15206-W aa...aa has failed. Details aa...
8. Messages KAPL15402-W Could not start the HDLM manager. KAPL15403-I HDLM Manager successfully stopped. KAPL15404-W The HDLM Manager was executed by the user who does not have the authority.
8. Messages 8.15 Return Codes for Hitachi Command Suite Common Agent Component When an operation requested of HDLM from Global Link Manager terminates abnormally, or terminates normally with a warning, HDLM outputs one of the return codes described below. 1002 Details There is no path on which the operation can be performed. Action Refresh the host information, check the path status, and then perform the operation again. 1003 Details No path was detected.
8. Messages Action Click Refresh to update the host information, check the path status, and then retry the offline operation. 1015 Details The Offline path cannot be placed Online. Action Remove the error in the path, and then retry. 1016 Details The target path(s) are already Online. Action Update the host information, and then check the path status. 1017 Details The target path(s) are already Offline(C). Action Update the host information, and then check the path status.
8. Messages maintenance contract for HDLM. For details on the DLMgetras utility, see 7.2 The DLMgetras Utility for Collecting HDLM Error Information. 1021 Details MSCS is not installed on the host. Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if you have a maintenance contract for HDLM. For details on the DLMgetras utility, see 7.2 The DLMgetras Utility for Collecting HDLM Error Information.
8. Messages 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 7.2 The DLMgetras Utility for Collecting HDLM Error Information.
8. Messages Re-execute the command. If the same error occurs again, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see 7.2 The DLMgetras Utility for Collecting HDLM Error Information. 1035 Details An attempt to acquire information about the HDLM version or SP version has failed. Action Re-execute the command.
8. Messages A storage system that cannot use the load balancing function is connected. Action Check the system configuration. One or more connected storage systems cannot use the load balancing function. The load balancing function does not operate on the LUs of such storage systems. 1041 Details An attempt to communicate with the HDLM manager has failed. Action Check whether the HDLM manager is running on the host. If it is not running, start the HDLM manager.
8. Messages 1046 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 7.2 The DLMgetras Utility for Collecting HDLM Error Information.
8. Messages 8.16 Events Output to Windows Event Logs by HDLM The following table lists Table 8-3: Events Output to the Windows Application Log and Table 8-4: Events Output to the Windows System Log events output by HDLM to Windows event logs.
8.
Appendixes A. Functional Differences Between Versions of HDLM B.
A. Functional Differences Between Versions of HDLM A. Functional Differences Between Versions of HDLM This section explains the functional differences between newer and older versions of HDLM. A.1 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.
A. Functional Differences Between Versions of HDLM longer needs to be removed as a target of the Data Execution Prevention (DEP) functionality. • In a new installation of HDLM, the default value for the automatic failback function has been changed from off to on. A.5 Functional Differences Between Version 5.9.4 or Later and Versions Earlier Than 5.9.
A. Functional Differences Between Versions of HDLM following conditions is satisfied, the path status remains Online: • A path is disconnected and is free from any I/O errors • An LU has been removed from being an HDLM management-target (2) 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.
A. Functional Differences Between Versions of HDLM recovered • An LU was removed from being an HDLM management-target, and then the same LU is re-added as an HDLM management-target A.9 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.
A. Functional Differences Between Versions of HDLM Offline(E) Status in A.8 Path Status Transition and Automatic Path Switching. A.10 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.
A. Functional Differences Between Versions of HDLM A.12 Differences in the Load Balancing Function in an MSCS Environment HDLM 05-00 or earlier does not support the load balancing function in an MSCS environment. Therefore, when you use HDLM 05-00 or earlier in an MSCS environment, even if you set the load balancing function to on, it will automatically change to off.
B. Glossary B. 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.
B. Glossary 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. HDLM operates assuming that one LU has one Dev, so the Dev number is always fixed to 0. (See also: Dev) dynamic reconfiguration Dynamic reconfiguration enables HDLM to recognize devices whose configuration has been changed without restarting the host.
B. Glossary In this manual, the term HBA indicates an interface card that is mounted on a host from which the host connects to a storage system via a SCSI or FC connection. HDLM alert driver A program that receives information about an error detected by the HDLM driver, and then reports the error information to the HDLM manager. HDLM driver A program that controls all the HDLM functions, manages paths, and detects errors. HDLM manager A program that manages error information.
B. Glossary L LDEV (Logical Device) A combination of the storage system's product name, serial number, and an internal LU. HDLM uses this value to identify a particular LU. load balancing A function for distributing the load across all the paths that are accessing the logical areas within an LU. To distribute the load, load balancing uses multiple paths to perform I/O operations.
B. Glossary (See also: owner path, non-owner controller) O owner controller A controller that has been set as an owner controller for an LU. Owner controllers are only in the Thunder 9500V series, or Hitachi AMS/WMS series. A controller other than an owner controller is called a non-owner controller. When using Lightning 9900 series, Lightning 9900V series, Hitachi USP, Universal Storage Platform V/VM, Virtual Storage Platform, Hitachi AMS2000 series, or Hitachi SMS, all controllers are owner controllers.
B. Glossary • 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.
B. Glossary SLPR (Storage Logical Partition) A function supported by Hitachi USP, Universal Storage Platform V/VM, and Virtual Storage Platform 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.
Index A abbreviations defined ii active host 60 audit log categories and audit events that HDLM can output 50 collecting data 49 data format 55 automatic failback 28, 230, 456 automatic failover 26 automatic path switching 26 AutoPATH_ID 9, 11, 456 B buffer size 154 bus number 267 C CHA 10, 12 CHA (Channel Adapter) 456 channel adapter 9, 11 checking path information using Windows administrative tool (Performance) 183 clear 210 CLPR(Cache Logical Partition) 456 cluster 456 support 60 cluster software 60 cl
Index driver level HDLM and MPIO drivers 18 dynamic reconfiguration 457 examining message 203 F E EMC CX series cluster software 67 EMC DMX series cluster software 67 dlnkmgr view -lu -c 275 EMC DMX series and CX series dlnkmgr view -lu 270 dlnkmgr view -path -c 260 EMC DMX series, CX series, and HP EVA series available SAN environment 9 notes 170 EMC DMX series, EMC CX series, or HP EVA series -exlu parameter 253 emulation type 457 Error 47 error information 45, 197 collecting with DLMgetras 286 filteri
Index HDev 15 HDevName 198 HDLM features 4 functions 7 installing 90 new installation (on Windows Server 2003) 94 new installation (on Windows Server 2008) 120 notes on versions 78 output to Windows event logs 446 overview 1 program information 245 setup 142 uninstalling 158 HDLM alert driver 17, 458 HDLM command 17 HDLM Core components 17 HDLM driver 17, 458 driver level 18 HDLM environment creating 61 HDLM GUI 17 HDLM installation types 77 HDLM installation type migration of HDLM 77 new installation of H
Index installing 136 K KB meaning xiv L LDEV (Logical Device) 459 load balancing 4, 19, 226, 459 load balancing algorithms 23 log collection level values 227 logical unit 9, 11 logical unit ID 267 logs HDLM output to Windows event logs 446 LU 10, 13, 188 configuration 14 LU (Logical Unit) 459 LU configuration recognized by the host 15 LUN 267 M manual formats xiv manual path switching 29 MB meaning xiv message examining 203 message element DNum 198 ErrorCode 198 PathID 198 PathName 198 message explanati
Index view [view operation] 249 operation name 316 operations 208 displaying format 212 of the HDLM command 208 Oracle RAC note 85 organization of this manual i overview command 208 HDLM 1 owner controller 21, 460 owner path 21, 460 P P 10, 13 path 9, 11, 460 checking the configuration 140 path error handling 200 Path Health Checking 41 path health checking 4, 41, 230, 460 path information obtaining 201 path name 460 path status transition 30 path status transitions 32 path switching automatically 26 manu
Index TB meaning xiv term in message 316 trace file 45 trace file size 229 trace level values 229 types of collected logs 45 types of error information 45 U unattended installation 92 notes on 93 uninstallation HDLM 158, 159 uninstallhdlm 313 uninstalling Hitachi Network Objectplaza Trace Library (HNTRLib2) 165 upgrade installation or re-installation of HDLM 134 using Windows administrative tool (Performance) checking path information 183 utilities for checking HDLM installation information 301 for checki
