Hitachi Command Suite Dynamic Link Manager (for AIX) User Guide Document Organization Product Version Getting Help Contents MK-92DLM111-28
© 2014 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd. Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use.
Contents Preface.................................................................................................xiii Intended audience...................................................................................................xiv Product version....................................................................................................... xiv Release notes..........................................................................................................xiv Document revision level....
Path status transition...................................................................................... 2-20 The online path status........................................................................... 2-20 The offline path status........................................................................... 2-20 Correspondence Between Path Statuses Displayed by the OS and by HDLM2-21 Status transitions of a path....................................................................
Notes on Trace Files....................................................................................... 3-16 Notes on Storage Systems...............................................................................3-17 Notes on the Cluster....................................................................................... 3-17 Notes on the Automatic Failback...................................................................... 3-18 Notes on the queue_depth Parameter Value for an HDLM-Managed device....
Setting the Number of Error Log Files..................................................... 3-84 Setting the Trace File Size......................................................................3-84 Setting the Number of Trace Files...........................................................3-85 Setting Up Audit Log Data Collection.......................................................3-85 Setting the Audit Log Facility..................................................................
Changing the Status of Paths.............................................................................4-6 Changing the Status of Paths to Online..................................................... 4-6 Changing the Status of Paths to Offline(C)................................................ 4-7 Viewing LU Information.....................................................................................4-8 Displaying the Correspondences Between hdisks, OS Management Path IDs, and LDEVs.....................
6 Command Reference.............................................................................6-1 Overview of the HDLM Command dlnkmgr................................................................6-2 clear (Returns the Path Statistics to the Initial Value)................................................ 6-3 Format.............................................................................................................6-3 To Set the Path Statistics to 0................................................
Format...........................................................................................................6-75 To Add a Path Dynamically.....................................................................6-75 To Display the Format of the add Operation............................................ 6-75 Parameters.....................................................................................................6-75 To Add a Path Dynamically..............................................................
dlmrmprshkey Utility for Clearing HDLM Persistent Reservation (Shared-Host Methodology)....................................................................................................... 7-31 Format...........................................................................................................7-31 Parameters.....................................................................................................7-31 installhdlm Utility for Installing HDLM...........................................
Changing a Virtual I/O Server's Method of Recognizing Virtual SCSI Disks...................
xii Hitachi Dynamic Link Manager (for AIX) User Guide
Preface This document describes how to use the Hitachi Dynamic Link Manager.
Intended audience This document is intended for storage administrators who use Hitachi Dynamic Link Manager (HDLM) to operate and manage storage systems, and assumes that readers have: • Knowledge of AIX and its management functionality • Knowledge of Storage system management functionality • Knowledge of Cluster software functionality • Knowledge of Volume management software functionality Product version This document revision applies to HDLM for AIX version 8.0.0 or later.
Document organization The following table provides an overview of the contents and organization of this document. Click the chapter title in the left column to go to that chapter. The first page of each chapter provides links to the sections in that chapter. Chapter/Appendix Description Chapter 1, Overview of HDLM on page 1-1 Gives an overview of HDLM, and describes its features.
• Hitachi Command Suite Global Link Manager Messages, MK-95HC108 • Hitachi Adaptable Modular Storage Series User's Guide • Hitachi Simple Modular Storage Series User's Guide • Hitachi Unified Storage Series User's Guide • Hitachi USP Series User's Guide • Hitachi Workgroup Modular Storage Series User's Guide • Thunder9580V Series Disk Array Subsystem User's Guide • Reference Manual / File Conversion Utility & File Access Library • Universal Storage Platform V User's Guide • Universal Stor
Physical capacity unit Value 1 kilobyte (KB) 1,000 (103) bytes 1 megabyte (MB) 1,000 KB or 1,0002 bytes 1 gigabyte (GB) 1,000 MB or 1,0003 bytes 1 terabyte (TB) 1,000 GB or 1,0004 bytes 1 petabyte (PB) 1,000 TB or 1,0005 bytes 1 exabyte (EB) 1,000 PB or 1,0006 bytes Logical storage capacity values (for example, logical device capacity) are calculated based on the following values: Logical capacity unit Value 1 block 512 bytes 1 KB 1,024 (210) bytes 1 MB 1,024 KB or 1,0242 bytes 1 GB 1
our existing Support Portal and support services by providing an area where you can get answers to non-critical issues and questions. Join the conversation today! Go to community.hds.com, register, and complete your profile. Comments Please send us your comments on this document: doc.comments@hds.com. Include the document title and number, including the revision level (for example, -07), and refer to specific sections and paragraphs whenever possible.
1 Overview of HDLM HDLM is a software package that manages paths between a host and a storage system. HDLM is designed to distribute loads across multiple paths and will switch a given load to another path if there is a failure in the path that is currently being used, thus improving system reliability. This chapter gives an overview of HDLM and describes its features.
What is HDLM? The widespread use of data warehousing and increasing use of multimedia data have increased the need for high-speed processing of large volumes of data on networks. To satisfy this need, networks dedicated to data transfer, such as a SAN, are now being used to provide access to storage systems. The HDLM software manages access paths to storage systems. HDLM uses MPIO functionality supported by AIX 5L V5.2 or later.
The ability to continue running operations between a host and storage system, even if there is a failure. This is also known as performing a failover. When a host is connected to a storage system via multiple paths, HDLM can automatically switch to another path if there is some sort of failure in the path that is currently being used. This allows operations to continue between a host and a storage system.
1-4 Overview of HDLM Hitachi Dynamic Link Manager (for AIX) User Guide
2 HDLM Functions This chapter describes the various functions that are built into HDLM. Before the function specifications are explained though, this chapter will go into detail about the HDLM management targets, system configuration, and basic terms that are necessary to know to effectively operate HDLM. After that, the rest of the chapter focus on describing all the HDLM functions, including the main ones: load distribution across paths and path switching.
□ Integrated HDLM management using Global Link Manager □ Cluster support 2-2 HDLM Functions Hitachi Dynamic Link Manager (for AIX) User Guide
Devices Managed by HDLM Below is a list of devices that can or cannot be managed by HDLM. The devices that can be managed by HDLM are called HDLM management-target devices.
Figure 2-1 HDLM System Configuration The following table lists and describes the HDLM system components. Table 2-1 HDLM System Components Components 2-4 Description HBA A host bus adapter. This serves as a cable port on the host. SAN A dedicated network that is used for data transfer between the host machine and storage systems. CHA A channel adapter. P A port on a CHA. This serves as a cable port on a storage system. LU A logical unit (a logical volume defined on the storage system).
LU Configuration On a system using HDLM, the logical device file for the HDLM managementtarget device is used to access the target LU. An LU recognized by a host after HDLM installation, is called a host LU (HLU). The areas in a host LU that correspond to the Dev in a storage system LU are called host devices (HDev). An LU in the storage system corresponds one-to-one with a host LU, a host device, or an hdisk.
Program Configuration HDLM is actually a combination of several programs. Because each program corresponds to a specific HDLM operation, it is important to understand the name and purpose of each program, along with how they are all interrelated. The following figure shows the configuration of the HDLM programs. Figure 2-3 Configuration of the HDLM Programs The following table lists and describes the functions of these programs.
Program name HDLM manager Functions • Migration of HDLM • Clear HDLM persistent reservation • Exclude the hdisk recognized as a boot disk from being an HDLM management target • Set ODM to define HDLM operations • Delete hdisks according to the parameter settings • Install HDLM • The unattended installation of HDLM • Install Hitachi Command Suite Common Agent Component • Collect information about errors that occur during HDLM installation • Perform maintenance when HDLM-managed devices a
Figure 2-4 Position of the HDLM Driver and hdisk 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.
Figure 2-5 Flow of I/O Data When the Load Balancing Function Is Not Used When the load balancing function is not being used, I/O operations converge on one physical path (A). The load on the physical path (A) will cause a bottleneck, which might cause deterioration of the whole system's performance.
Figure 2-6 Flow of I/O Data When the Load Balancing Function Is Used When the load balancing function is being used, I/O operations are distributed via physical paths (A), (B), (C), and (D). This prevents deterioration of the whole system's performance from a bottleneck on one path. 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.
paths and non-owner paths. If failures occur across some of the owner paths, load balancing will be performed among the remaining, usable owner paths. It is only when absolutely no owner paths are available, that load balancing is then performed among the non-owner paths. For the example in Figure 2-7 Overview of load balancing on page 2-11, suppose that in the owner controller of LU0 is CHA0. When the LU is accessed, the load is balanced between the two paths A and B, which are both owner paths.
¢ Virtual Storage Platform series ¢ VSP G1000 series ¢ Hitachi AMS2000 series# ¢ Hitachi SMS series# ¢ HUS100 series# HUS VM #: This storage system applies when the dynamic I/O path control function is disabled.
If the data is not sequential, these algorithms select the path to be used each time an I/O request is issued. ¢ ¢ ¢ Extended Round Robin The paths are simply is selected in order from among all the connected paths. Extended Least I/Os The path that has the least number of I/Os being processed is selected from among all the connected paths. Extended Least Blocks The path that has the least number of I/O blocks being processed is selected from among all the connected paths.
Performing Failovers and Failbacks Using Path Switching When the system contains multiple paths to an LU and an error occurs on the path that is currently being used, HDLM can switch to another functional path, so that the system can continue operating. This is called a failover. If a path in which an error has occurred recovers from the error, HDLM can then switch back to that path. This is called a failback.
controller of an LU is CHA0, and access to the LU is made via only one path (A). After that access path (A) is placed offline, the first choice for the switching destination is the other path connected to CHA0 (B). If an error also occurs on that path (B), then the next possibility for a path comes from one of the two paths (C or D) connected to CHA1.
Priority of Switching Destination Paths Priority of paths varies depending on the architecture of the host machine. If the architecture of the host is CHRP, the switching destination path is selected based on four keys. First, the path with the smallest path priority number (first key) is selected.
d. Execute a command that displays the information for the path for which a new path priority number has been set: # lspath -l hdisk4 -p fscsi0 -w 50060e8005271720,31000000000000 -E scsi_id 0x651400 SCSI ID False node_name 0x50060e8005271720 FC Node Name False state Enabled N/A True priority 5 N/A True Slot number This number indicates the position of the slot where an HBA is mounted. You can find the order of the slot numbers by comparing their physical location code.
Note Depending on the HBA, you need to repeat steps b and c. For details on the position of slots, see the manual of the host. CHA port number The port number of the CHA. You can check this number by using the dlnkmgr command's view operation. For details on the view operation, see view (Displays Information) on page 6-34. AutoPATH_ID The ID assigned to a path. This ID is re-assigned each time the host or the HDLM Manager is started. You can check this ID by using the dlnkmgr command's view operation.
#1 This storage system applies when the dynamic I/O path control function is disabled. #2 An intermittent error means an error that occurs irregularly because of some reason such as a loose cable connection. Manual path switching You can switch the status of a path by manually placing the path online or offline. Manually switching a path is useful, for example, when system maintenance needs to be done.
This storage system applies when the dynamic I/O path control function is disabled. Path status transition Each of the online and offline statuses described in Performing Failovers and Failbacks Using Path Switching on page 2-14 is further subdivided into several statuses. The path statuses (the online path statuses and offline path statuses) are explained below. The online path status The online path statuses are as follows: • Online I/Os can be issued normally.
change the status to the Online(D) status, specify the -dfha parameter for the HDLM command's online operation. # The status changes to this status when using HAM (High Availability Manager). Correspondence Between Path Statuses Displayed by the OS and by HDLM The following table lists the correspondence between the path statuses displayed when commands such as the AIX lspath command are executed and the path statuses displayed when the HDLM command's view operation is executed.
Figure 2-9 Path status transitions Legend: Online operation: Online operation performed by executing the dlnkmgr command's online operation. Offline operation: Offline operation performed by executing the dlnkmgr command's offline operation. #1 When no Online or Offline(E) paths exist among the paths that access the same LU.
This path is deleted when the AIX chdev command is executed on an hdisk where an Online or Offline(E) path exists. To restore the deleted path, remove the cause of the error and then execute the AIX mkdev -l hdisk-name or cfgmgr command. #4 When an Online or Offline(E) path exists among the paths that access the same LU. #5 One of the Offline(E) paths is changed to the Online(E) path. #6 When an Offline(E) path exists among the paths that access the same LU.
The last available online path for each LU cannot be placed offline by executing the offline operation. This ensures access to the LU. For details on the offline operation, see offline (Places Paths Offline) on page 6-6. If an error occurs in the last available online path for each LU, the status of the path is changed to Online(E). If you are using automatic failback, when the path recovers from an error, HDLM automatically places the path online.
Setting up intermittent error monitoring When you enable the intermittent error monitoring function, specify the following monitoring conditions: the error monitoring interval, and the number of times that the error needs to occur. If an error occurs on a particular path the specified number of times within the specified errormonitoring interval, then an intermittent error will occur on the path.
Figure 2-11 Action What Will Happen When an Intermittent Error Occurs on a Path When an intermittent error does not occur If an error does not occur on a path a specified number of times within a specified interval, an intermittent error will not occur. In such a case, the error monitoring will finish when the specified error-monitoring interval finishes, upon which the number of errors is reset to 0.
As shown in Figure 2-12 What Will Happen When an Intermittent Error Does Not Occur on a Path on page 2-26, normally the count for the number of times that an error occurs is started after the path is first recovered from an error by using the automatic failback function.
When a User Changes the Intermittent Error Information The following might be reset when a user changes any of the values set for the intermittent error or the path status: the number of errors that have already been counted during error monitoring, the amount of time that has passed since error monitoring has started, and the information about whether an intermittent error has occurred.
User operation Placing the path Online while intermittent error monitoring is being performed Number of errors and time passed since error monitoring started Inherited Information about paths not subject to automatic failback (Not applicable) If a path has been removed from the paths subject to automatic monitoring, that path is no longer monitored.
For example, in a normal state, I/O operations are not performed on the paths coming from the standby host in the cluster configuration or on nonowner paths (that is, some of the paths that access a Thunder 9500V series, or Hitachi AMS/WMS series storage system). Because of this, for the standby host or for a host connected to non-owner paths, we recommend that you use path health checking to detect errors.
The dynamic I/O path control function can be specified by using the HDLM command's set operation. For details about the set operation, see set (Sets Up the Operating Environment) on page 6-18. 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.
Logs might be collected in layers below HDLM, such as for the HBA driver. For more details, see the AIX documentation. Types of Collected Logs HDLM collects information on the detected error and trace information in the integrated trace file, trace file, error logs, HDLM utility's log file, and syslog. You can use the error information to examine the status of an error and analyze the cause of the error. The following table lists and describes the error information that can be collected in logs.
Log name Syslog Description Output destination The HDLM messages on or above the Syslog is not output by level set by the user with /etc/ default. syslog.conf are collected.# To output syslog, The syslog file path is specified in the We recommend that you configure the system so that information at the file /etc/syslog.conf. For details, see the AIX Information level and higher is documentation. output. Syslogs can be checked using a text editor.
Error information is filtered according to the error level, and then collected. In syslog, the HDLM messages on or above the level set by the user configured in /etc/syslog.conf are collected. It is recommended that you set the Information to be output at the info level or higher. The error information in error logs and trace files are collected based on a user-defined collection level. The collection levels are as follows: Collection levels for error logs ¢ Collects no error information.
By executing the dlmgetrasinst utility, you can collect system information and log files needed to analyze errors that occurred during installation. You can use the collected information when you contact your HDLM vendor or maintenance company (if there is a maintenance contract for HDLM). For details on the dlmgetrasinst utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-5.
Category AccessControl ContentAccess ConfigurationAccess Maintenance AnomalyEvent Explanation An event indicating that a resource access attempt made by a device, administrator, or end-user has succeeded or failed, including: • Device access control • Administrator or end-user access control An event indicating that an attempt to access critical data has succeeded or failed, including: • Access to a critical file on a NAS or content access when HTTP is supported • Access to the audit log file A
Categories and Audit Events that HDLM Can Output to the Audit Log The following table lists and explains the categories and audit events that HDLM can output to the audit log. The severity is also indicated for each audit event. Table 2-10 Categories and Audit Events that Can Be Output to the Audit Log Category Explanation Startup and termination of the software StartStop Audit event Severit y#1 Message ID Startup of the HDLM manager was successful.
Category 2-38 Explanation Audit event Severit y#1 Message ID Processing of the dlmpremkcd -u command was successful. 6 KAPL15090-I Processing of the dlmpremkcd -u command failed. 3 KAPL15091-E Processing of the 6 dlmrmprshkey -l hdiskn command was successful. KAPL15092-I Processing of the 6 dlmrmprshkey -l hdiskn -R RegistKey command was successful. KAPL15093-I Processing of the dlmrmprshkey command failed. 3 KAPL15094-E Initialization of path statistics was successful.
Category Explanation Audit event Severit y#1 Message ID An attempt to display HDLM managementtarget information failed. 3 KAPL15110-E Processing of the dlmpr -k command was successful. 6 KAPL15001-I Processing of the dlmpr -k command failed. 3 KAPL15002-E Processing of the dlmpr -c command was successful. 6 KAPL15008-I Processing of the dlmpr -c command failed. 3 KAPL15009-E Processing of the dlmodmset -o command was successful.
The severity levels are as follows: 3: Error, 4: Warning, 6: Informational #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. #3 If you use Ctrl + C to cancel the dlmgetrasinst utility for collecting HDLM installation error information, audit log data indicating that the dlmgetrasinst utility has terminated will not be output.
For example, to change the output destination of audit log data to /usr/ local/audlog, specify the following two settings: • Specify the following setting in the /etc/syslog.conf file: local0.info /usr/local/audlog • Use the HDLM command's set operation to specify local0 for the audit log facility: You can also filter the audit log output by specifying a severity level and type for the HDLM command's set operation.
¢ program-name ¢ [process-ID] ¢ message-section The following shows the format of message-section and explains its contents.
Item# Explanation Redundancy identification information Redundancy identification information Agent information Agent information Host sending request Name of the host sending a request Port number sending request Number of the port sending a request Host receiving request Name of the host receiving a request Port number receiving request Number of the port receiving a request Common operation ID Operation serial number in the program Log type information Fixed to BasicLog Application iden
The following figure is an example of a system configuration using HDLM and Global Link Manager. Figure 2-15 Example System Configuration Using HDLM and Global Link Manager Cluster support HDLM can also be used in cluster configurations. HDLM supports the cluster software listed below. • GPFS • PowerHA • Oracle RAC 10g • Oracle RAC 11g • VCS • DB2 pureScale HDLM uses a path of the active host to access an LU. The details of host switching depend on the application.
3 Creating an HDLM Environment This chapter describes the procedures for creating an HDLM environment and for canceling the setup. Make sure that HDLM is installed and its functions have been set up. The volume groups and cluster software programs must be set up appropriately for your system environment. Note that, in the required procedures and notes, there are differences between HDLM version 5.8.1 or earlier, and HDLM version 5.9 or later. For details, see Appendix B, Differences Between HDLM Version 5.
□ Settings for Using Oracle RAC 10g or Oracle RAC 11g □ Settings for Using VCS □ Removing HDLM 3-2 Creating an HDLM Environment Hitachi Dynamic Link Manager (for AIX) User Guide
HDLM System Requirements Check the following before installing HDLM. For OS patches and software provided by OS vendors, download them from the Web site of the appropriate OS vendor. For the requirements for using HDLM in an HAM environment, see the release notes of HDLM. Host and OS Support for HDLM You can install HDLM on hosts running the OSs in the following table. Table 3-1 Applicable OSs for the Host OS AIX 5L V5.
OS Kernel Apply SP1 or later For Technology Level 09 Apply SP1 or later AIX V6.1 (Virtual I/O Server)#3, ioslevel 2.1.0.01 to 2.2.3.xx (where xx is a number) #5 AIX V7.1#1, #3 No Technology Level Technology Level 01 For Technology Level 02 Apply SP1 or later For Technology Level 03 Apply SP1 or later AIX V7.1 (Virtual I/O Server)#3, ioslevel 2.1.0.0 to 2.2.3.xx (where xx is a number) #5 #1 Every SP is applicable, unless otherwise specified.
Execute the following command, as applicable, to check the runtime version: For AIX 5L V5.3: # lslpp -L xlC.aix50.rte For AIX V6.1 # lslpp -L xlC.aix61.rte For AIX V7.1 # lslpp -L xlC.aix61.rte • HTC_ODM 5.0.52.1 or later If you are using the following storage systems, use HTC_ODM 5.0.52.
is not used, this message requires no action. Note that the display of the KAPL09241-W message does not affect HDLM operation.
Table 3-2 HDLM-Related Programs Required When Handling Intermediate Volumes Managed by Hitachi RapidXchange OS Related Programs AIX 5L V5.3 File Access Library and File Conversion Utility (FAL/FCU) 01-03-56/20 or later File Access Library and File Conversion Utility (FAL/FCU) 01-04-64/21 or later AIX V6.1 File Access Library and File Conversion Utility (FAL/FCU) 01-07-68/00 or later AIX V7.
OS Related Programs • Oracle RAC 11g 11.1.0.6.0 If the HDLM device is specified for direct access: ASM + raw devices#1, or raw devices#1 • Oracle RAC 11g 11.1.0.7.0 If the HDLM device is specified for direct access: ASM + raw devices#1 • Oracle RAC 11g 11.2.0.3.0 If the HDLM device is specified for direct access: ASM + raw devices#1 AIX 5L V5.3 (Virtual I/O Server) • GPFS 3.3#3, #6 • GPFS 3.4#3 • VCS 5.0#4 • VCS 5.0.1#4 • VCS 5.0.3#4, #5 • VCS 5.1#4 • PowerHA 6.
OS Related Programs • VCS 5.0.1#4 • VCS 5.0.3#4, #5 • VCS 5.1#4 • DB2 pureScale 9.8#8 • DB2 pureScale 10.1#8 • DB2 pureScale 10.5#8 AIX V6.1 (Virtual I/O • Server) PowerHA 6.1 Client: Technology Level 02 or later Server: ioslevel 2.1.0.0 to 2.2.3.xx (where xx is a number) • PowerHA 7.1 Client: Technology Level 06 or later Server: ioslevel 2.1.0.0 to 2.2.3.xx (where xx is a number) • PowerHA 7.1.1 Client: Technology Level supported by PowerHA Server: ioslevel 2.1.0.0 to 2.2.3.
OS Related Programs AIX V7.1 (Virtual I/O • Server) PowerHA 6.1 Client: No Technology Level, or Technology Level 01 or later Server: ioslevel 2.1.0.0 to 2.2.3.xx (where xx is a number) • PowerHA 7.1 Client: No Technology Level, or Technology Level 01 or later Server: ioslevel 2.1.0.0 to 2.2.3.xx (where xx is a number) • PowerHA 7.1.1 Client: Technology Level supported by PowerHA Server: ioslevel 2.1.0.0 to 2.2.3.xx (where xx is a number) • PowerHA 7.1.
To use Tiebreaker Disk, Global Link Manager is required. Use Global Link Manager to set Tiebreaker Disk load balancing to off. Memory and Disk Capacity Requirements The table below shows the memory requirements for the host. Memory Requirements Table 3-4 Memory Requirements for the Host on page 3-11 shows the memory requirements for the host. Table 3-4 Memory Requirements for the Host OS AIX Required memory 5000 KB + 0.256 KB × number-of-LUs + 1.
#3 This is the amount of unused capacity required to use the installhdlm utility. For details on this utility, see installhdlm Utility for Installing HDLM on page 7-32. Number of LUs and Paths That Are Supported in HDLM The following table lists the number of LUs and paths that are supported by HDLM.
Figure 3-1 Flow of HDLM Environment Setup Types of HDLM Installation This section describes the following HDLM installation types: new installation, upgrade installation, migration, and re-installation. New installation of HDLM Installing HDLM on a server where HDLM has not yet been installed is called a new installation.
Re-installation of HDLM Installing the same version of HDLM for repair purposes without removing the existing instance of HDLM is called re-installation of HDLM. Notes on Creating an HDLM Environment This section provides notes on creating an HDLM environment. For notes on operating HDLM, see Notes on Using HDLM on page 4-2. Notes on Installing HDLM • Install HDLM on the boot disk. • To install HDLM, a license key is required.
• If you upgrade or re-install HDLM before you resolve a path failure, LU reservations might persist without being released. In such a case, use the utility for clearing HDLM persistent reservations (dlmpr) to release the LU reservation, if necessary. • Performing an upgrade installation or re-installation might change the physical volume (hdisk name).
When the NPIV option is set to on, HBA adapter number and bus number for PathName, which are output by HDLM command view operations, are changed to adapter type and adapter number respectively. The view operation parameters for which the above changes are to be applied are as follows: ¢ -path parameter (displays path information) ¢ -lu parameter (displays LU information) ¢ -hba parameter (displays HBA port information) For details on the view operations, see view (Displays Information) on page 6-34.
Trace files after the migration: /var/DynamicLinkManager/log/ hdlmtrn.log (n indicates a file number) Notes on Storage Systems • Do not change the vendor ID or product ID of a storage system. If you do, HDLM will not be able to recognize the storage system. • Before you connect multiple storage systems to the same host, make sure that the storage systems have unique serial numbers.
• If you are using PowerHA, note that HDLM does not support nonconcurrent volume groups due to limitations in PowerHA. For details, contact IBM. • If all of the following conditions are met, HDLM can be migrated without stopping PowerHA services: ¢ The shared volume groups used by PowerHA are concurrent volume groups. ¢ A custom disk method is specified in the PowerHA script. ¢ A virtual I/O server environment is not used on the host.
• ¢ Upgrade installation ¢ Re-installation ¢ Unattended installation Use SMIT or the installp command. You can also copy the contents of the HDLM DVD-ROM to a desired directory, and then perform installation from that directory. Copy the following files from the installation DVD-ROM to the same directory: ¢ DLManager.mpio.bff ¢ .toc To use SMIT, in software-input-device/directory specify the directory in which the contents of the DVD-ROM have been copied.
Methods that Are Available in an PowerHA Environment and the Supported Installation Environments on page 3-20 lists the combinations of installation methods that are available in an PowerHA environment versus the supported installation environments.
Installation environment Installation method Host Virtual I/O server Local boot disk environment Boot disk environment Local boot disk environment Boot disk environment No No No No Installation on alternate disks Yes#2 Yes#2 Yes#2 Yes#2 Installation in a multibos environment Yes#3 Yes#3 Yes#3 Yes#3 Unattended installation Legend: Yes: Can be executed No: Cannot be executed #1 Only new installations, upgrade installations, and re-installations are supported.
When Installing HDLM on Alternate Disks on page 3-52 in Performing an Upgrade Installation or Re-installation of HDLM on page 3-38 To use SMIT, see the AIX documentation. When Performing a Migration of HDLM Table 3-9 Combination of Available Migration Methods and Migration Environments on page 3-22 lists the combinations of available migration methods and target environments.
Table 3-10 Combinations of Migration Methods Available in an PowerHA Environment and the Migration Environments Migration environment Host Virtual I/O server Migration method Local boot disk environment Boot disk environment Local boot disk environment installux.
Preparations for a New Installation of HDLM In this subsection, you will perform such preparations as backing up the HDLM management-target devices, applying AIX patches, and performing hardware setup. When using HDLM in a cluster configuration, make sure to perform the operations described in the following sub-sections on all hosts that comprise the cluster.
For details on how to set up the storage system, see the maintenance documentation for the storage system. If you are using PowerHA, see also Storage System Settings on page 3-95 of Settings for Using PowerHA on page 3-95. 2. Set up the Fibre Channel switches. For details on how to set up a Fibre Channel switch, see the documentation for the Fibre Channel switch. If you do not use Fibre Channel switches, this setup is not necessary. 3. Set up the HBA.
4. Restart the system. # shutdown -Fr 5. Execute the following command to confirm that the kernel mode has been changed properly. # bootinfo -K Set Up Cluster Software To use HDLM in a cluster configuration, you need to perform the following setup for the cluster software. To set up cluster software: 1. Install the cluster software on all of the hosts in the cluster. For details on the installation, see the documentation of the corresponding cluster software. 2. Stop the cluster software services.
In this example, hdisk3 and hdisk4 are recognized as devices to be managed by HDLM. If all devices to be managed by HDLM are recognized, proceed to step 5. If any devices to be managed by HDLM are not recognized, proceed to step 7. 5. Execute the following utility to remove, from the running kernel, the HDLM management-target device: # /cdrom/HDLM_AIX/hdlmtool/dlmrmdev -f The KAPL10529-I message is displayed.
If the KAPL09172-E message is displayed, the hdisk for the device that is managed by HDLM still remains. Re-execute the procedure starting from step 5. During installation, the KAPL09241-W message might be output. In this case, installation of HDLM continues, but installation of HDLM components has failed. After installing HDLM, resolve the problem according to the KAPL09241-W message if necessary. 9. Execute the following command to make sure that the package is installed. # lslpp -la DLManager.mpio.
18. Enable the defined parent device (fscsin). # cfgmgr 19. Execute the chdev command, as required, to change the attributes of the hdisk: # chdev -l hdisk-name -a queue_depth=8 -a rw_timeout=60 20. Execute one of the following commands, as required, to add /usr/ DynamicLinkManager/bin to the PATH environment variable.
HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.x-xx yyyy/mm/dd hh:mm:ss 4000 HDLM Driver Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss License Type Expiration Permanent KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss Even if cluster software is used, the name of the cluster software is not displayed in Support Cluster. However, the cluster support function is operating normally. 23.
30. Check the path configuration according to the procedure described in Checking the Path Configuration on page 3-77. When Installing HDLM in a Boot Disk Environment To perform a new installation of HDLM: 1. For AIX 5.3, use a single-path configuration for hosts and storage systems. For AIX 6.1 or AIX 7.1, you can use a single-path configuration or a multipath configuration for hosts and storage systems. 2. Log in to AIX as the root user.
4. If there is no directory for mounting the DVD-ROM, make the directory. # mkdir /cdrom cdrom is the desired directory name. Hereafter, cdrom is used for purposes of explanation. 5. Mount the DVD-ROM. # mount -r -v cdrfs /dev/cd0 /cdrom The /dev/cd0 part depends on the system. 6. Execute the following command to check that the devices to be managed by HDLM have been recognized by the system: # lsdev -Cc disk hdisk0 Available hdisk1 Available hdisk2 Available hdisk3 Available hdisk4 Available ...
Store the license key file directly under the /var/tmp/ directory by using the hdlm_license name. /var/tmp/hdlm_license Note that the hdlm_license and dlm.lic_key files are deleted after installation finishes successfully. 10. Execute the following command: ¢ When installing HDLM from the DVD-ROM # /directory-in-which-the-DVD-ROM-is-mounted/installux.
16. Make sure that the boot disk is in a multi-path configuration: # lspath -l hdisk10 -s available Available hdisk10 fscsi0 Available hdisk10 fscsi1 ... The following procedure assumes that hdisk10 is recognized as a boot disk: 17. Check the current boot disk list: # bootlist -m normal -o hdisk10 blv=hd5 hdisk0 blv=hd5 hdisk1 blv=hd5 ... 18. Specify boot disks that are suitable for your host environment: # bootlist -m normal hdisk10 hdisk0 hdisk1 19.
25. Execute the chdev command, as required, to change the attributes of the hdisk: # chdev -l hdisk-name -a queue_depth=8 -a rw_timeout=60 26. Execute one of the following commands, as required, to add /usr/ DynamicLinkManager/bin to the PATH environment variable.
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 4000 HDLM Driver Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss License Type Expiration Permanent KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss Even if cluster software is used, the name of the cluster software is not displayed in Support Cluster. However, the cluster support function is operating normally. 29.
Preparations for an Upgrade Installation or Re-installation of HDLM Make necessary preparations, such as backing up the HDLM managementtarget devices. When using HDLM in a cluster configuration, make sure to perform the operations described in the following sub-sections on all hosts that comprise the cluster.
Performing an Upgrade Installation or Re-installation of HDLM This subsection explains how to perform an upgrade installation from an earlier version, or how to re-install HDLM. Because HDLM version 5.8.1 or earlier cannot be upgraded to HDLM version 5.9 or later, migration is necessary. For details about migration, see Migrating from HDLM Version 5.8.1 or Earlier to Version 5.9 or Later on page 3-61.
If an upgrade installation or re-installation fails, perform a new installation, and then re-execute setup to reflect the settings that have been backed up. ¢ ¢ Save the HDLM environment settings information. # /usr/DynamicLinkManager/bin/dlnkmgr view -sys > any-filename Make sure that the license has not expired. Save the HDLM execution environment ODM settings. # /usr/DynamicLinkManager/bin/dlmodmset -o > any-file-name Reconfigure the HDLM device.
To inherit the existing hdisk configuration, execute the dlmrmdev utility with the -e parameter specified. If you execute the dlmrmdev utility without the -e parameter specified, the existing HDLM device is deleted. To inherit the mapping between virtual target devices and HDLM devices on the virtual I/O server, specify the -e parameter to inherit the existing hdisk configuration. Note that if you want to inherit the existing hdisk configuration when the installed HDLM version is earlier than 6.
¢ When the existing hdisk configuration has been successfully inherited, the KAPL10531-I message is displayed. If the KAPL10531-I message is not displayed, make sure that no processes, services, file systems, or volume groups are using any HDLM management-target paths, and then perform step 9 again. ¢ When an existing hdisk has been successfully deleted, the KAPL09012I message is displayed.
HDLM management-target paths, and then re-execute the procedure of step 13. 14. Execute the following command and verify the status of the hdisks recognized as HDLM-managed devices: # lsdev -Cc disk ¢ ¢ If you attempted to delete an existing hdisk by executing the dlmrmdev utility, verify that the hdisk has been deleted. If you attempted to inherit the existing hdisk configuration by executing the dlmrmdev utility, verify that the status of the hdisks recognized as HDLM-managed devices is Defined.
or # installp -aXgd /directory-copied-from-DVD-ROM/HDLM_AIX all Even though a message asking you to restart the host is displayed during installation, you do not have to restart the host. If you execute the dlmrmdev utility without the -e parameter specified at step 9 or 13 and then the KAPL09048-E message is displayed, the hdisk for the device that is managed by HDLM still remains.
If one or more of the displayed statuses are BROKEN, remove and then reinstall HDLM. 20. Execute the following command to make sure that the hdisk. # cfgmgr 21.
Even when cluster software is being used, the name of the cluster software is not displayed in Support Cluster. However, the cluster support function is operating normally. 25. From the execution result of the view operation, check that the correct version of HDLM is installed. If HDLM Version is x.x.x-xx, the installed version of HDLM is correct. x.x.x-xx is the installed version of HDLM. 26. From the execution result of the view operation, check that the programs are running properly.
Perform this step so that a copy of the HDLM settings is available in this case. If an upgrade installation or re-installation fails, perform a new installation, and then re-execute setup to reflect the settings that have been backed up. ¢ ¢ Save the HDLM environment settings information. # /usr/DynamicLinkManager/bin/dlnkmgr view -sys > any-filename Make sure that the license has not expired. Save the HDLM execution environment ODM settings.
10. Execute the following command to display all the activated volume groups. # lsvg -o 11. Among the displayed volume groups, inactivate the volume groups used by HDLM. # varyoffvg volume-group-name 12. Execute the utility indicated below to change the status of the hdisks recognized as HDLM management-target devices by the active kernel, and then stop the HDLM manager. To inherit the existing hdisk configuration, execute the dlmrmdev utility with the -e parameter specified.
hdisk2 Available 1S-08-00-10,0 16 Bit LVD SCSI Disk Drive hdisk3 Defined 1H-08-02 Hitachi Disk Array (Fibre) hdisk4 Defined 1H-08-02 Hitachi Disk Array (Fibre) ... 14. If the license has expired, prepare the license key or license key file. If the license has not expired, proceed to step 15. ¢ ¢ When only the license key has been provided Create the /var/DLM directory, and then, in this directory, create the license key file (dlm.lic_key).
During installation, the KAPL09241-W message might be output. In this case, installation of HDLM continues, but installation of HDLM components has failed. After installing HDLM, resolve the problem according to the KAPL09241-W message if necessary. 17. For a re-installation, execute the following command: ¢ When installing HDLM from the DVD-ROM # /directory-in-which-the-DVD-ROM-is-mounted/installux.
# shutdown -F ¢ When an environment other than the above is used Execute the following command to restart the host, and then perform the procedure in Perform Operations for HDLM Management-Target Device on page 3-37: # shutdown -Fr After performing a new installation of HDLM, set up HDLM again based on the HDLM settings backed up in step 2. 20. Execute the following command to restart the host: # shutdown -Fr 21.
Alive x.x.x-xx yyyy/mm/dd hh:mm:ss License Type Expiration Permanent KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss Even when cluster software is being used, the name of the cluster software is not displayed in Support Cluster. However, the cluster support function is operating normally. 23. From the execution result of the view operation, check that the correct version of HDLM is installed. If HDLM Version is x.x.
When Installing HDLM on Alternate Disks Perform the procedure below if you want to install HDLM on an alternate disk in a local boot disk environment or a boot disk environment. Only upgrade installations and re-installations are supported when HDLM is installed on alternate disks. 1. Log in to AIX as a user with root permissions. If you are using a virtual I/O server, see the virtual I/O server documentation to log in to AIX. 2. If the license has expired, prepare the license key or license key file.
For details about the alt_disk_copy and nim commands, see the manual for AIX. 5. For a re-installation, execute the following command: ¢ ¢ ¢ When installing HDLM on an alternate disk from the DVD-ROM # alt_disk_copy -d hdisk-name hdisk-name ... -I aXF -w DLManager.mpio.rte -l /directory-in-which-the-DVD-ROM-ismounted/HDLM_AIX When installing HDLM onto an alternate disk from the directory to which the DVD-ROM was copied # alt_disk_copy -d hdisk-name hdisk-name ... -I aXF -w DLManager.mpio.
Even when cluster software is being used, the name of the cluster software is not displayed in Support Cluster. However, the cluster support function is operating normally. 7. From the execution result of the view operation, check that the correct version of HDLM is installed. If HDLM Version is x.x.x-xx, the installed version of HDLM is correct. x.x.x-xx is the installed version of HDLM. 8. From the execution result of the view operation, check that the programs are running properly.
The hdlm_license file is automatically deleted after the upgrade installation of HDLM is completed normally. Go to step 6. 4. Mount the file system of an already created standby BOS, and then store the license key you prepared. Create the /bos_inst/var/DLM directory, and then, in this directory, create the license key file (dlm.lic_key). Then unmount the file system of the standby BOS. The following is an example of executing the command when the license key is 123456789ABCDEF.
which-the-DVD-ROM-is-mounted-or-the-contents-of-the-DVDROM-have-been-copied/HDLM_AIX When performing an upgrade installation of HDLM on an already created standby BOS • An example of executing the command to install HDLM from the DVD-ROM or a directory to which the contents of the DVD-ROM have been copied: # multibos -Xc -a -l name-of-the-directory-to-which-theDVD-ROM-is-mounted-or-the-contents-of-the-DVD-ROM-havebeen-copied/HDLM_AIX • An example of executing the command to install HDLM as an installatio
License Type Expiration Permanent KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss Even if cluster software is used, the name of the cluster software is not displayed in Support Cluster. However, the cluster support function is operating normally. 11. Use the view operation to check the installed version of HDLM. If x.x.x-xx is displayed for HDLM Version, the installed version of HDLM is correct. x.x.x-xx is the installed version of HDLM. 12.
¢ When the license key file has been provided Store the license key file directly under the /var/tmp/ directory on a NIM client by using the hdlm_license name. /var/tmp/hdlm_license On the NIM client, execute the set operation of the HDLM command while specifying the -lic parameter. # /usr/DynamicLinkManager/bin/dlnkmgr set –lic KAPL01049-I Would you like to execute the operation? Operation name = set [y/n]:y KAPL01071-I The permanent license was installed.
License Type Expiration Permanent KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss Even if cluster software is used, the name of the cluster software is not displayed in Support Cluster. However, the cluster support function is operating normally. 6. Use the view operation to check the installed version of HDLM. If x.x.x-xx is displayed for HDLM Version, the installed version of HDLM is correct. x.x.x-xx is the installed version of HDLM. 7.
The following is an example of executing the command to check the location of spot_7102_HDLM when the name of the SPOT to which HDLM is installed is spot_7102_HDLM: # lsnim -l spot_7102_HDLM | grep location location = /export/spot_7102/spot_7102_HDLM/usr In the above example, the license key file will be /export/ spot_7102/spot_7102_HDLM/usr/lpp/bos/inst_root/var/tmp/ hdlm_license. 3.
Migrating from HDLM Version 5.8.1 or Earlier to Version 5.9 or Later When HDLM version 5.8.1 or earlier is migrated to HDLM version 5.9 or later, the logical device file that can be controlled by the HDLM driver changes from the HDLM device (dlmfdrvn) to hdisk. If the user application uses an LU managed by HDLM, modify the user application appropriately. To migrate to HDLM version 5.9 or later: 1. Log in to AIX as a user with root permissions. ¢ ¢ 2.
7. Execute the following command to delete the volume group in the client logical partition: # reducevg -df volume-group-name hdisk-name 8. Execute the following command to delete the virtual SCSI disk in the client logical partition: # rmdev -dl hdisk-name 9. Execute the following command to delete the virtual target device in the virtual I/O server: $ rmdev -dev vtscsin 10. Insert the DVD-ROM. 11. If there is no directory for mounting the DVD-ROM, make the directory.
Because HDLM version 5.9 or later requires deletion of hdisk, do not attempt to perform device configuration (cfgmgr command) before performing step 17. 16. Perform a new installation of HDLM version 5.9 or later. Perform steps 4 to 9 of When Installing HDLM in a Local Boot Disk Environment on page 3-26 in Performing a New Installation of HDLM on page 3-26. Note that you do not have to perform steps 2 to 3. 17.
# rm -r /tmp/any-desired-directory-that-stores-set-environmentsetting-file 22. Perform the procedure described in When Installing HDLM in a Local Boot Disk Environment on page 3-26 in Performing a New Installation of HDLM on page 3-26, starting from step 14. 23. If you performed step 5, restore the volume group you backed up. # restvg -f any-desired-file-name-or-device-name hdisk-name 24. Check the path configuration according to the steps described in Checking the Path Configuration on page 3-77. 25.
7. Start PowerHA on the active host. Upgrading or Re-installing HDLM in a PowerHA 6.1 Environment (in a Boot Disk Environment) For details about setting up PowerHA, see the PowerHA documentation. To upgrade or re-install HDLM in an environment that uses PowerHA and a boot disk: 1. Log in to AIX as the root user. If you are using a virtual I/O server, see the virtual I/O server documentation to log in to AIX. 2. Stop PowerHA on the standby host. 3. Upgrade or re-install HDLM on the standby host.
To do so, perform steps 10 to 26 in Migrating from HDLM Version 5.8.1 or Earlier to Version 5.9 or Later on page 3-61 on the standby host. 5. Start PowerHA on the standby host. When PowerHA starts, a warning message may be output, stating that the custom disk method file (/usr/DynamicLinkManager/cluster/ dlm_hacmp_gdisk_check) does not exist. This message can be ignored because it does not affect any operations.
Installing HDLM in an Environment Running PowerHA 7.1 or a Later Version In an environment running PowerHA 7.1 or a later version, even if the cluster service is stopped, the cluster repository disk remains in the used state. Therefore, if you perform a new installation, upgrade installation, or reinstallation of HDLM in an environment in which PowerHA is already in use, perform the procedure below. For details on how to use and set up PowerHA, see the PowerHA documentation. 1.
5. Execute the following command on the standby host. When the OS used in a PowerHA environment is AIX V6.1 TL06 or AIX V7.1 with no TL: # clusterconf -r hdiskxx When the OS used in a PowerHA environment is AIX V6.1 TL07 or later or AIX V7.1 TL01 or later: # clctrl -start -m node-name 6. Execute the following command on the standby host to start PowerHA. # smitty cl_start 7. Execute the following command on the active host to stop PowerHA. # smitty cl_stop 8.
When performing an upgrade installation or re-installation of HDLM in a boot disk environment: Perform the procedure described in When Installing HDLM in a Boot Disk Environment on page 3-45 of Performing an Upgrade Installation or Re-installation of HDLM on page 3-38. 10. Execute the following command on the active host. When the OS used in a PowerHA environment is AIX V6.1 TL06 or AIX V7.1 with no TL: # clusterconf -r hdiskxx When the OS used in a PowerHA environment is AIX V6.1 TL07 or later or AIX V7.
# cp -rp /cdrom/HDLM_AIX /tmp/hdlm/ # cp -p /cdrom/installux.sh /tmp/hdlm/ If you copied the files on the DVD-ROM to your desired directory, proceed to step 5. 3. If there is no directory for mounting the DVD-ROM, make the directory. # mkdir /cdrom cdrom is the desired directory name. Hereafter, cdrom is used for purposes of explanation. 4. Mount the DVD-ROM. # mount -r -v cdrfs /dev/cd0 /cdrom The /dev/cd0 part depends on the system. 5.
If the directory that contains the license key or the license key file is specified in the installation information settings file, you can use any storage directory name and file name. The following shows examples of when the default storage directory specified in the installation information settings file is to be used: ¢ ¢ When only the license key has been provided Create the /var/DLM directory, and then, in this directory, create the license key file (dlm.lic_key).
has failed. After installing HDLM, resolve the problem according to the KAPL09241-W message if necessary. For an upgrade installation or re-installation of HDLM, the configuration of the existing hdisks recognized as HDLM management-target devices is inherited. 10. Unmount the DVD-ROM. # umount /cdrom 11. Delete the created mount directory. # rm -r /cdrom 12. Delete the installation information settings file. # rm -r /directory-containing-the-installation-informationsettings-file 13.
¢ Identify the physical volume used for booting: # getconf BOOT_DEVICE hdisk3 In this example, hdisk3 is used for booting. If the boot physical volume that contains the logical volume hd5 is different from the physical volume used for booting, the following message appears, and the HDLM installation ends with an error: 0503-497 installp: An error occurred during bosboot test processing.
The necessary files to be copied from the /cdrom/HDLM_AIX/hdlmtool/ instutil directory are shown below: ¢ installhdlm ¢ installhdlm_analysis ¢ dlmrmdev Also, these files need to be copied to the same directory to which the installhdlm utility is copied. For a new installation, proceed to step 8. 8. If you are upgrading or re-installing HDLM, back up the HDLM settings. If an upgrade installation or re-installation fails, AIX automatically removes HDLM, and the HDLM settings are deleted.
To use the sample file, copy it from the DVD-ROM to a directory on the hard disk. # cp -p /cdrom/HDLM_AIX/hdlmtool/instutil/ sample_installhdlm.conf /any-directory You can change the sample_installhdlm.conf file name. The following shows an example of copying the sample_installhdlm.conf file, and then changing the file name to install_set.conf: # cp -p /cdrom/HDLM_AIX/hdlmtool/instutil/ sample_installhdlm.conf /any-directory/install_set.
During installation, the KAPL09241-W message might be output. In this case, installation of HDLM continues, but installation of HDLM components has failed. After installing HDLM, resolve the problem according to the KAPL09241-W message if necessary. When installation is successful, the KAPL09211-I message is output and the host restarts. After the host has restarted, check to make sure that the settings have been updated as specified in the installation information settings file.
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. The following describes how to check path information by using the dlnkmgr command's view operation.
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. The following subsections describe these setup methods. Checking the Current Settings This chapter describes how to check the HDLM function settings before any changes are made by using the dlnkmgr command's view operation.
Table 3-12 The Recommended and Default Values of Each Function Function Load-balancing Default value Recommended value on on The Extended Least I/Os algorithm is used. The recommended algorithm depends on the operating environment. on on 30-minute check interval The recommended checking interval depends on the operating environment. on 60-minute check interval The recommended checking interval depends on the operating environment.
Setting Up Load Balancing You can select whether to enable load balancing. The following is an example command to set load-balancing. # /usr/DynamicLinkManager/bin/dlnkmgr set -lb on -lbtype exlio Set it to on to enable load balancing. Otherwise, set it to off.
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 needs to occur. If you set the number of times that the error needs to occur to 1, the above condition does not need to be satisfied.
occur in the -iemnum parameter. When these parameters are omitted, the default values of 210 and 3 are used, respectively. Setting Up Dynamic I/O Path Control To prevent degrading of I/O performance, this function dynamically switches the output controllers for HDLM, following the switching of controllers performed by the storage system. The dynamic I/O path control function can be set for each storage system or LU.
The following is an example of setting up the error log collection level by using a command: # /usr/DynamicLinkManager/bin/dlnkmgr set -ellv 2 Specify the error log collection level as a number. Setting the Trace Level The trace output level can be set. You can set up the trace level for a trace file hdlmtrn.log (n indicates a file number from 1 to 64). The following table lists and describes the values for the trace level setting.
When an error log file reaches the specified size, the information in the old error log file is replaced with new information, beginning with the oldest file. By specifying both the log file size and the number of log files, you can collect up to 32000000KB (approximately 30 GB) of error logs in total. The following shows an example of executing the command to set the error log file size. # /usr/DynamicLinkManager/bin/dlnkmgr set -elfs 1000 Specify the size of the error log file in kilobytes.
Setting the Number of Trace Files You can set the number of the trace files. Trace files for which the number of files can be set are hdlmtrn.log (n indicates a file number from 1 to 64). For the number of the trace files, you can specify a value from 2 to 64. If you specify a value smaller than the value that has already been specified, the KAPL01097-W message will be displayed to confirm the execution, and the trace file will be temporarily deleted.
Table 3-16 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. 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 specify the audit log facility: # /usr/DynamicLinkManager/bin/dlnkmgr set -audfac local0 Checking the Updated Settings This chapter describes steps involved in how to check the updated settings by using the dlnkmgr command's set operation after settings have been changed. When you change some settings, you can display information about all of HDLM function settings.
into the integrated trace files. To save as much information as possible, change the settings for Hitachi Network Objectplaza Trace Library, increasing the integrated trace file size and buffer size. Note that if the values are too large, it will place a heavy load on the system. When determining these values, be sure to consider these operational tradeoffs. The following table lists the default values and recommended values for the integrated trace file setting.
# /opt/hitachi/HNTRLib2/bin/hntr2utl2 The Hitachi Network Objectplaza Trace Library setup menu appears. If you do not want to change the settings, type e and then press the Enter key to quit the menu. The following explains how to modify each setting. Changing the Size of Integrated Trace Files The following procedure shows how to change the size of integrated trace files. To change the size of integrated trace files: 1.
3. Press the Enter key. The new setting is applied and the Hitachi Network Objectplaza Trace Library setup menu appears again. Changing the Number of Integrated Trace Files The following procedure shows how to change the number of integrated trace files. To change the number of integrated trace files: 1. In the Hitachi Network Objectplaza Trace Library setup menu, type 2 and then press the Enter key. A screen to set the number of integrated trace files will appear.
2. Enter the desired size in New Size (KB). Set a new buffer size to fit the monitoring interval set in 5: Interval Timer. The specifiable range is between 8 KB and 2048 KB, with a default of 64. Set this to a value smaller than that set in step 2 of Changing the Size of Integrated Trace Files on page 3-89. We recommend setting a value of 256 when collecting an integrated trace. To leave the buffer size as is, leave New Size (KB) blank, type ! and press the Enter key.
To adjust the number of messages to be output per monitoring interval: 3-92 1. In the Hitachi Network Objectplaza Trace Library setup menu, type 6 and then press the Enter key. A screen to set the monitoring interval for the amount of messages output to the integrated trace file will appear. The current value is displayed in Current Span (sec). 2. Enter a desired interval in New Span (sec). The specifiable range is between 0 and 3600 seconds, with a default of 0. We recommend setting a value of 0.
Also, when you specify a value of 0 for New Max (sec), even if you specify the monitoring interval in 6: Lookout span, the maximum number of messages output will not be adjusted. To leave the maximum number of messages output as is, leave New Max (sec) blank, enter ! and press the Enter key. You will be returned to the Hitachi Network Objectplaza Trace Library setup menu. 6. Press the Enter key. The new setting is applied and the Hitachi Network Objectplaza Trace Library setup menu appears again.
5. Execute the following command to delete the memory mapped file: # rm /opt/hitachi/HNTRLib2/mmap/hntr2mmap.mm 6. Execute the following command to start the integrated trace collection process: # /opt/hitachi/HNTRLib2/bin/hntr2mon -d & 7. Start the programs stopped in step 3. If you stopped programs other than HDLM in step 3, start them. About the Reservation Policy The following table lists and describes the values for the reservation policy setting.
mkdev -l hdisk-name cfgmgr Settings for Using PowerHA To use PowerHA, install HDLM on all hosts comprising the cluster, configure the hdisks, set up the storage system (if using Thunder 9500V series, or Hitachi AMS/WMS series devices), and register the HDLM script for PowerHA. Also, set up the same reservation policy in all of the hdisks that are shared by multiple hosts in the cluster.
To specify a custom disk method: 1. From the SMIT window, display the Add Custom Disk Methods window. Choose the following sequence of menu items to display this window: Communications Applications and Services, HACMP for AIX, Extended Configuration, Extended Resource Configuration, HACMP Extended Resource Configuration, Configure Custom Disk Methods, and finally choose Add Custom Disk Methods. 2.
use the following procedure to check, in the virtual I/O server partition, the settings for the reserve_policy attribute of the hdisk. If reserve_policy is set to PR_exclusive, change its value to no_reserve. 1. Check the setting for the reserve_policy attribute of the hdisk. # lsattr -El hdisk-name -a reserve_policy reserve_policy PR_exclusive N/A TRUE Perform the following steps if reserve_policy is set to PR_exclusive: 2.
2. When GPFS or GPFS+RVSD is used, in the dlmodmset utility for setting the HDLM execution environment ODM, set the LUN RESET option to on. # /usr/DynamicLinkManager/bin/dlmodmset -r on Settings for Using Oracle RAC 10g or Oracle RAC 11g Settings for MISSCOUNT and DISKTIMEOUT When a host and an Oracle RAC voting disk are connected by multiple paths, HDLM performs failover processing for those paths (in the same way as for normal paths) when an I/O timeout occurs for one of the paths.
then change the current value to a value equal to or greater than the value you have obtained.
3. Execute the following command to unmount the file system used by HDLM. # umount file-system-mount-point 4. Execute the following command to display all the activated volume groups. # lsvg -o 5. Among the displayed volume groups, inactivate the volume groups used by HDLM. # varyoffvg volume-group-name 6. Execute the chdev command to change the reserve_policy attribute to no_reserve. # chdev -l hdisk-name -a reserve_policy=no_reserve 7. Confirm that the setting was changed to no_reserve.
Figure 3-4 Example of Editing the Preonline Script Removing HDLM This section explains how to return the HDLM environment to the way it was before HDLM was installed, and describes each step of the process. Preparations for HDLM Removal • Back up all HDLM management-target devices onto a medium such as a tape. • Remove HDLM in a multi-user mode environment. • When removing HDLM on a host where version 5.
Hitachi Network Objectplaza Trace Library (HNTRLib2), only HDLM will be removed. You can use the installp command or SMIT to remove HDLM. The following explains how to remove HDLM using the installp command. For details about how to use SMIT, see the AIX documentation. For the virtual I/O server and boot disk environment, execute the required steps among those listed below. When Removing HDLM in a Local Boot Disk Environment 1. Log in to AIX as a user with root permissions.
For details about the stopping method, see the manual for each application. 10. Specify the -A parameter, as required, and execute the dlmrmdev utility to remove HDLM drivers. When you specify the -A parameter and execute the dlmrmdev utility, you can skip steps 11 through 14. When dlmrmdev is executed, a message appears asking for confirmation that processing is to continue. Enter y for this message to continue processing.
¢ If Thunder 9500V series, Lightning 9900V series (excluding XP series), Hitachi USP series (excluding XP series), Universal Storage Platform V/VM series (excluding XP20000 and XP24000), Hitachi Virtual Storage Platform, VSP G1000, Hitachi AMS2000/AMS/WMS/SMS series, HUS100 series, or HUS VM was used, delete the following line: disk/fcp/Hitachi fscsi disk/fcp 17.
22. Execute the following command in the client logical partition to reconfigure the device: # cfgmgr 23. Execute the following command in the client logical partition to check that the physical volume has been recognized as hdisk: # lsdev -Cc disk Check that the following execution result is displayed: hdisk1 Available Virtual SCSI Disk Drive 24.
$ rmdev -dev vtscsin If the boot disk is in a single-path configuration, proceed to step 12. 9. If the boot disk is in a multi-path configuration, execute the following command to shut down the host. # shutdown -F 10. Configure the host and storage system so that only a single path connects the host to the storage system (single-path configuration). 11. Start the host. 12. Execute the following command to unmount the file system used by HDLM: # umount file-system-mount-point 13.
# shutdown -Fr 18. If GPFS + RVSD was used, delete the setting information from the /etc/vsd/oemdisktypes.lst file.
$ mkvdev -vdev hdisk-name -vadapter virtual-SCSI-serveradapter-name ¢ To create a logical volume as a virtual target device $ mkvdev -vdev logical-volume-name -vadapter virtual-SCSIserver-adapter-name 25. Execute the following command in the client logical partition to reconfigure the device: # cfgmgr 26.
4. From the Setup menu, select 9. HNTRLib2 will be removed. If HNTRLib2 is not being used by any other programs: HNTRLib2 will be removed normally, and the following message will appear. Unsetup is complete. If HNTRLib2 is being used by another program: HNTRLib2 will not be removed, and the following message will appear. Because a bundle PP name is registered, I did not do the Uninstall. If HNTRLib2 was not removed, execute the following command to check if any programs are using it.
/opt/hitachi/common/lib/D001 If the /opt/hitachi directory only contains the files and directories shown above, delete the directory. Note ¢ ¢ If the log output directory set in HNTRLib was not the default directory, the log files will not be deleted during removal. In this case, delete these files after removal. Even if you attempt to remove HNTRLib2 when HNTRLib is installed, HNTRLib will not be removed. If no other programs are using HNTRLib, delete it manually.
4 HDLM Operation This chapter describes operating procedures for HDLM, including how to operate HDLM and the HDLM manager, and how to change the configuration of the operating environment. Some of the cautionary notes in Notes on Using HDLM on page 4-2 are different for HDLM 5.8.1 or earlier and HDLM 5.9 or later. In addition, the contents of Changing the Configuration of the HDLM Operating Environment on page 4-15 have changed. For details, see Appendix B, Differences Between HDLM Version 5.
Notes on Using HDLM This section provides notes on using HDLM and using the environment in which HDLM is installed. Make sure that you read this section. Displaying Path Information The AutoPATH_ID that is displayed during the HDLM dlnkmgr command's view operation differs depending on the order in which paths are detected when the host starts. For this reason, you should always use the path name to specify a path.
Storage System • Start up the storage system before you start up the hosts, so that AIX can detect the storage system. • To delete an LU from the storage system, you must delete the hdisk first, and then you can delete the LU. • If you change the storage system's owner controller for the LU, you must re-configure the hdisk or restart the server.
Notes on Enabling Both Primary and Secondary Volumes to Be Viewed From the Same Server To enable both primary and secondary volumes to be viewed from the same server, operate the disks according to the following steps: 1. Create a pair of the primary volume and the secondary volume (paircreate). 2. Split the pair (pairsplit). 3. Enable the secondary volume to be recognized as a volume group (recreatevg). When you execute the recreatevg command, characteristics of the volume group will be initialized.
To cancel the reservation for the LU, execute the dlmpr utility from a host that can access this LU. For details on this utility, see dlmpr Utility for Clearing HDLM Persistent Reservation on page 7-26. Notes on Replicating a System You can use the OS's mksysb command to back up hosts that include HDLMmanaged devices.
To display path information, execute the dlnkmgr command's view operation with the -path parameter specified. The following example shows how to execute the command: # /usr/DynamicLinkManager/bin/dlnkmgr view -path To display information only for the paths accessing the specified host device, execute the dlnkmgr command's view operation with the -path and -hdev parameters specified.
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. The following shows an example in which the command is executed: # /usr/DynamicLinkManager/bin/dlnkmgr online -hba 01.01 KAPL01057-I All the paths which pass the specified HBA will be changed to the Online status. Is this OK? [y/n]:y KAPL01061-I 3 path(s) were successfully placed Online; 0 path(s) were not.
3. Check to see if the statuses of all the applicable paths have changed. The following example shows how to execute the command: # /usr/DynamicLinkManager/bin/dlnkmgr view -path Viewing LU Information This section explains how to display LU information by using an HDLM command. To display LU information, execute the dlnkmgr command's view operation with the -lu parameter specified.
operation, see view (Displays Information) on page 6-34. The execution result of this operation is displayed on a single line for each path. The following shows an example in which the view operation is executed: # /usr/DynamicLinkManager/bin/dlnkmgr view -drv PathID HDevName OSPathID LDEV 000000 hdisk0 00000 9500V.0051.0005 000001 hdisk1 00000 9500V.0051.0015 000002 hdisk2 00000 9500V.0051.0020 000003 hdisk0 00001 9500V.0051.0005 000004 hdisk1 00001 9500V.0051.0015 000005 hdisk2 00001 9500V.0051.
Viewing and Setting Up the Operating Environment This section explains how to display and set up the HDLM operating environment. 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: # /usr/DynamicLinkManager/bin/dlnkmgr view -sys -sfunc HDLM Version : x.x.
• Dynamic I/O path control • Displaying the physical storage system information • 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 • Audit log facility • Number of times the same path can be used for load balancing • Number of times the same path can be used for extended load balancing For details on how to set up each function, see set (Sets Up the Operating Enviro
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.
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 4000 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 # The value displayed in HDLM version indicates the HDLM version.
# /usr/DynamicLinkManager/bin/dlnkmgr view -sys -msrv # /usr/DynamicLinkManager/bin/dlnkmgr view -sys -adrv # /usr/DynamicLinkManager/bin/dlnkmgr view -sys -pdrv Starting and Stopping the HDLM Manager If an error occurs in the system, such as in an HDLM program, you may need to manually stop or start HDLM to recover from the error. Starting the HDLM Manager To start the HDLM manager, log in to AIX as a user with root permissions and then execute the following command.
# /usr/DynamicLinkManager/bin/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. HDLM Resident Processes The table below lists and describes the resident processes in HDLM. To monitor these processes, use the names below.
2. Stop all processes and services that are using the device that is to be deleted. 3. Execute the following command to unmount the file system that uses the device that is to be deleted: # umount file-system-mount-point 4. If the device to be deleted is registered in a volume group, execute the following command to inactivate the volume group: # varyoffvg volume-group-name 5. Execute the following command to delete the device (or devices): ¢ ¢ 6.
Changing hdisk attributes hdisk attributes consist of default values and values actually used. When a new hdisk is configured, or deleted and then reconfigured, the actual value for hdisk attributes is set using the default values. The HDLM default settings modification utility (dlmchpdattr) can be used to change the default values. Note: To change attribute values for an individual hdisk, use the chdev command instead of the dlmchpdattr utility to change the values actually used.
If the execution environment is a boot disk environment, proceed to step 4. If the execution environment is a local boot disk environment, proceed to step 5. 4. Execute the following command to restart the host. # shutdown -Fr 5. Execute the following command to make sure that the status of the hdisks recognized as HDLM-managed devices is Available. # lsdev -Cc disk hdisk0 Available hdisk1 Available hdisk2 Available hdisk3 Available hdisk4 Available ...
To manually reconfigure an hdisk: 1. Log in to AIX as a user with root permissions. Reconfigure the HDLM device. Proceed to step 2 to automatically perform the processing needed to unmount for reconfiguration, and processing to change the active status of the volume group. Proceed to step 3 to perform these actions manually. 2. Execute the utility for deleting HDLM drivers (dlmrmdev) with the -e parameter and -A parameter specified.
8. Execute the utility for changing HDLM default settings (dlmchpdattr). # /usr/DynamicLinkManager/bin/dlmchpdattr -A -a reserve_policy=no_reserve A message is displayed to confirm whether processing should continue. Enter y to continue processing. If the command terminates normally, the KAPL10571-I message is displayed. 9. Make sure that the default value for the hdisk reservation policy has been changed. Execute the dlmchpdattr utility with the -o parameter specified.
hdisk4 ... Available 1H-08-02 Hitachi Disk Array (Fibre) In this example, hdisk3 and hdisk4 are recognized as HDLM-managed devices. If the status of all hdisks is Available, proceed to step 14. If there are any hdisks with the Defined status, perform step 10 again. 14. Check the setting for the hdisk reservation policy attribute. Make sure that the changed default value is reflected in the value actually used.
4. Make sure that the boot disk is configured with the specified number of paths. The following shows an example of executing the command: # bootlist -m normal -o hdisk0 blv=hd5 hdisk0 blv=hd5 hdisk1 blv=hd5 ... Deleting a Path (of a Volume Group Other than rootvg) The following shows an example of deleting a path of a volume group other than rootvg. 1.
# rmpath -d -l device-name -p fscsi-number -w connection-position The following example deletes the path whose OS-management-path-ID is 2: # rmpath -d -l hdisk10 -p fscsi5 -w 50060e800436e240,6a000000000000 4. Check that the path has been deleted. # /usr/DynamicLinkManager/bin/dlnkmgr view -drv Deleting a Path (of a Device Included in rootvg) The following shows an example of deleting a path of hdisk0 in an environment where rootvg consists of hdisk0 and hdisk1. 1.
The following are execution examples: fscsi0 available 1H-08-02 FC SCSI I/O controller protocol device fscsi1 available 11-08-02 FC SCSI I/O controller protocol device In the second line of the above examples, 11 in 11-08-02 indicates the bus number and 08 indicates the HBA adapter number. The fscsi number to be used when replacing this HBA is 1. 2. Execute the dlmodmset utility for setting the HDLM execution environment ODM to check the NPIV option setting.
6. Execute the following command: # diag Note For details on the operations after executing the diag command, see the AIX documentation. Steps 7 to 14 below provide an example of the execution procedure for AIX V6.1 (Technology Level 02). 7. From the displayed menu, choose Task Selection. The Task Selection List window appears. 8. Choose Hot Plug Task. The Hot Plug Task window appears. 9. Choose PCI Hot Plug Manager. The PCI Hot Plug Manager window appears. 10.
When you finish replacing the HBA, connect the cable and press Enter. 15. Execute the following command to reconfigure the device: # cfgmgr -l fcsn To reconfigure the device, specify the device name of the PCI slot where the HBA was replaced (fcs device); n indicates the instance number of the fcs device. 16. If LUN security has been set up for the storage system, delete the WWN of the previous HBA from the LUN security. 17.
b. Start the host. c. Execute the following command to delete the HDLM devices on the paths that go through the old HBAs: # rmdev -dl hdisk-name n indicates the instance number of the HDLM device. d. If LUN security has been set up for the storage system, delete the WWNs of the old HBAs from the LUN security. e. Execute the following command to reconfigure the devices: # cfgmgr -l fcsn Specify the device name of the PCI slot (fcs device) where each HBA has been replaced.
d. Specify boot disks that are suitable for your host environment: # bootlist -m normal hdisk10 hdisk0 hdisk1 e. Make sure that the number of configured boot disks is the same as the number of paths that you checked in step 2: # bootlist -m normal -o hdisk10 blv=hd5 hdisk10 blv=hd5 hdisk0 blv=hd5 hdisk1 blv=hd5 ...
Use the fscsi number to execute the command below. The following example shows how to place the path in Offline (C) status when the path goes through fscsi number 1 (fscsi1): # /usr/DynamicLinkManager/bin/dlnkmgr offline -hba 00.01 3. Replace the cable. Note If you change the port on the Fibre Channel switch or on the storage system, the path configuration will be changed. Delete the hdisk that are associated with the cable to be replaced and then reconfigure the device. 4.
To replace a Fibre Channel switch: 1.
# rmpath -p fscsin -d Because the fscsi number found in step 1 is 1 (fscsi1), the result is as follows: # rmpath -p fscsi1 -d 5. Execute the following command to get the name of the parent device: # lsdev -C -l fscsin -F parent 6. Delete the HBA device associated with the Fibre Channel switch that is to be replaced. # rmdev -dl fscsin -R 7. Replace the Fibre Channel switch. 8.
4-32 HDLM Operation Hitachi Dynamic Link Manager (for AIX) User Guide
5 Troubleshooting This chapter describes how to check HDLM error information, and how to take action if an error occurs in HDLM. Descriptions of the actions are separated into those for path errors, HDLM program errors, and other types of errors. If you need technical support, see Getting help on page xvii.
Information Collected by the DLMgetras Utility for Collecting HDLM Error Information Immediately after an error occurs, execute the DLMgetras utility for collecting HDLM error information, since restarting the machine might delete error information before the information is collected by DLMgetras. For details about the DLMgetras utility and the error information it collects, see DLMgetras Utility for Collecting HDLM Error Information on page 7-5.
PathName The path name, which indicates a path. When you modify the system configuration or replace a hardware item, you should check the path names to identify the paths that will be affected by the change.
Figure 5-1 Error location when the KAPL08022-E message is output The following figure shows the troubleshooting procedure when the KAPL08022-E message is output. Figure 5-2 Troubleshooting procedure when a path error occurs The following shows the procedure for using the HDLM command (dlnkmgr) to handle a path error.
Examining the messages Examine the message that is output to syslog in the management-target host by using applications or tools for monitoring messages. If the KAPL08022-E message is output, view the message to check the path in which the error occurs. For details on each item displayed in the message, see Checking error information in messages on page 5-2. Obtain path information Obtain path information.
If any path cannot be placed online due to an error, the KAPL01039-W message will appear. To ignore such paths and to continue processing, type y. Type n to cancel processing. Check the statuses of the paths that cannot be placed online, and resolve the problem. What To Do for a Program Error The following describes what to do to handle errors that occur in an HDLM program. The following figure shows the troubleshooting procedure.
What To Do for the Program Error Follow the recommended actions for messages in Chapter 8, Messages on page 8-1. If the error occurs again after you thought that you had resolved the problem, use the dlnkmgr command's view operation to check the status of the HDLM program, and then do whatever is necessary to resolve the problem. For details on the view operation, see view (Displays Information) on page 6-34.
5-8 Troubleshooting Hitachi Dynamic Link Manager (for AIX) User Guide
6 Command Reference This chapter describes the HDLM command (dlnkmgr) and its operations.
Overview of the HDLM Command dlnkmgr This section describes command formats and operations used for HDLM. Command format Enter the command using the following format: dlnkmgr operation-name [parameter [parameter-value]] dlnkmgr The command name. operation-name The type of operation entered after dlnkmgr. parameter A value required for an operation. parameter-value A value required for a parameter.
¢ ¢ Execute the command as a user with root permissions. To specify a value that contains a space in its parameter, enclose the entire value in double quotes ("). clear (Returns the Path Statistics to the Initial Value) The dlnkmgr command's clear operation clears the statistics (I/O count and I/O errors) of all paths that are managed by HDLM, and returns them to their initial value.
To Display the Format of the Clear Operation -help Displays the format of the clear operation. Example # /usr/DynamicLinkManager/bin/dlnkmgr clear -help clear: Format dlnkmgr clear -pdst [-s] KAPL01001-I The HDLM command completed normally. Operation name = clear, completion time = yyyy/mm/dd hh:mm:ss # help (Displays the Operation Format) The dlnkmgr command's help operation displays the list of operations available for the HDLM command, or the format of individual operations.
# /usr/DynamicLinkManager/bin/dlnkmgr help dlnkmgr: Format dlnkmgr { clear | help | offline | online | set | view | add | delete} KAPL01001-I The HDLM command completed normally. Operation name = help, completion time = yyyy/mm/dd hh:mm:ss # Example 2 The following example shows how to display the formats of multiple operations. # /usr/DynamicLinkManager/bin/dlnkmgr help online offline help online: Format dlnkmgr online [-path] [-s] dlnkmgr online [-path] { -hba HBAPortNumber.
# /usr/DynamicLinkManager/bin/dlnkmgr help help help: Format dlnkmgr help { clear | offline | online | set | view | add | delete } KAPL01001-I The HDLM command completed normally. Operation name = help, completion time = yyyy/mm/dd hh:mm:ss # 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 host device.
This parameter is optional because offline is always used for paths, so it is assumed. Make sure that you specify the paths to be placed offline by using the hba, -hbaid, -cha, -chaid, or -pathid parameter, or the -hdev and ospathid parameters. -hba HBA-adapter-number.bus-number Or -hba adapter-type.adapter-number Use this parameter to place offline, at one time, all the paths that pass through a specific HBA port.
The following example shows how to place offline all paths connected to the HBA port whose HBA-port-ID is 00001. # /usr/DynamicLinkManager/bin/dlnkmgr offline -hbaid 00001 KAPL01102-I All the paths which pass the specified HBA port will be changed to the Offline(C) status. Is this OK? [y/n]:y KAPL01103-I If you are sure that there would be no problem when all the paths which pass the specified HBA port are placed in the Offline(C) status, enter y. Otherwise, enter n.
Use this parameter to place offline, at one time, all paths that pass through a specific CHA port. The command will place offline all paths connected to the CHA port that has the specified CHA-port-ID. Paths that pass through a specific CHA port on a storage system recognized by the operating system will be offline. If there are multiple physical CHA ports that correspond to the CHA port ID, use -cha -pathid AutoPATH_ID to place paths offline.
# /usr/DynamicLinkManager/bin/dlnkmgr view -lu For details on how to execute the view operation and display the host device name and OS management path ID, see To Display LU Information on page 6-57 in Parameters on page 6-36. Only one set of values can be specified for the -hdev parameter. This parameter is not case sensitive. Example The following shows an example of placing offline path for which the host device name is hdisk0 and OS management path ID is 00001 while confirming command operation.
s] dlnkmgr offline [-path] { -cha -pathid AutoPATH_ID | chaid CHA_ID } [-s] dlnkmgr offline [-path] -pathid AutoPATH_ID [-s] dlnkmgr offline [-path] -hdev Host_Device_Name -ospathid OS_Path_ID [-s] Valid value AutoPATH_ID { 000000 - 999999 }(Decimal) HBA_ID { 00000 - 99999 }(Decimal) CHA_ID { 00000 - 99999 }(Decimal) OS_Path_ID { 00000 - 99999 }(Decimal) KAPL01001-I The HDLM command completed normally.
Format To Place Paths Online /usr/DynamicLinkManager/bin/dlnkmgr online [-path] [-hba HBA-adapter-number.bus-number-or-adapter-type.
between these two parameter values. For details about the view operation, see view (Displays Information) on page 6-34. The HBAadapter-number.bus-number and adapter-type.adapter-number strings are case-sensitive. Example The following example shows how to place online all paths connected to an HBA port whose HBA adapter number is 01 and bus number is 01. When the confirmation message is displayed, the user enters y to continue, or n to cancel the operation.
target AutoPATH_ID is 000000, enter 000000 or 0 for the parameter value. AutoPATH_IDs are re-assigned every time the host is restarted. When you want to add a new LU without restarting the host, AutoPATH_IDs are reassigned to each path of the LU when you execute the cfgmgr command. Always make sure that you use the view operation to find the current AutoPATH_ID of the target path, before executing the online operation.
Specify the current AutoPATH_ID of the target path, which is displayed by using the view operation. For details about the view operation, see view (Displays Information) on page 6-34. Leading zeros can be omitted (000001 and 1 indicate the same AutoPATH_ID); however, when the target AutoPATH_ID is 000000, enter 000000 or 0 for the parameter value. AutoPATH_IDs are re-assigned every time the host is restarted.
Use this parameter to change the paths to the primary volume (P-VOL) in an HAM environment to Online(D). The Online(S) status changes to the Online(D) status. When you do not specify this parameter, the status of the P-VOL paths in the HAM environment will be changed to the Online(S) status. If I/O operations to the secondary volume (S-VOL) have never occurred and only the paths to the P-VOL recover from an error, the path to the P-VOL will be in the Online status regardless of this parameter specification.
dlnkmgr online [-path] [-s] dlnkmgr online [-path] { -hba HBAPortNumber.
set (Sets Up the Operating Environment) The dlnkmgr command's set operation sets the HDLM operating environment.
Table 6-2 Default and Recommended Values Item name Load balancing Default value Recommended value on on The Extended Least I/Os algorithm is used. The recommended algorithm depends on the operating environment. Error log collection level 3: Collect error information for the Information level and higher. 3: Collect error information for the Information level and higher. Error log file size 9900 (KB) 9900 (KB) Number of error log files 2 2 Trace level 0: Do not output any trace.
Item name Default value Recommended value off Displaying the physical storage system information The recommended value depends on the operating environment. Set to on if you want to display the physical storage system information. # This item is applied only when Hitachi AMS2000 series, Hitachi SMS series, or HUS100 series storage is used. -lb {on [-lbtype {rr|exrr|lio|exlio|lbk|exlbk}]|off} Enables or disables load balancing.
Value Description 1 Collects error information for the Error or higher level. 2 Collects error information for the Warning or higher level. 3 Collects error information for the Information or higher level. 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.
Table 6-4 Trace Level Values Value Description 0 Does not output any trace. 1 Only outputs error information. 2 Outputs a summary of program operation. 3 Outputs details of program operation. 4 Outputs all information. The 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 is overwritten becomes shorter.
activate path health checking so that you can detect errors in paths where I/Os operations do not occur. When you specify on, specify the checking interval of path health checking by specifying the parameter immediately following on.
See Table 6-5 Relationship Between the Setting for the Automatic Failback Function and Intermittent Error Monitoring and the Executable Operations on page 6-27 for the relationship between automatic failbacks and intermittent error monitoring. When you specify on, specify the checking interval by specifying the parameter immediately following on.
Intermittent error monitoring can be enabled only when automatic failback is set to on. When you use automatic failback, we recommend that you set intermittent error monitoring to on to prevent an intermittent error from reducing I/O performance. If on is specified, be sure to also specify the intermittent error monitoring interval and the number of times that the error is to occur.
Because the errors and elapsed time are not counted or measured while intermittent errors are not being monitored, the those values will not change. The monitoring interval specified in this parameter is stored even though specifying -iem off disables intermittent error monitoring. Therefore, when you re-enable intermittent error monitoring and a monitoring interval is not specified, error monitoring will be performed by using the stored monitoring interval.
Table 6-5 Relationship Between the Setting for the Automatic Failback Function and Intermittent Error Monitoring and the Executable Operations Setting AFB on IEM on Available operation Set AFB to on. The operations of AFB and IEM do not change. Change the AFB setting. AFB is performed under the new settings.#1 Set AFB to off. • AFB and IEM are disabled. • The error count, elapsed monitoring time, and information about paths not subject to automatic failback are cleared.
Setting AFB IEM off Available operation Result of operation Set AFB to on. AFB is enabled. Set AFB to off. The operations of AFB and IEM do not change. Legend: AFB: Automatic failback IEM: Intermittent error monitoring #1 When this condition is not satisfied, the KAPL01080-W message is output and an error occurs. The status of intermittent error monitoring does not change. #2 Because automatic failback is off, intermittent error monitoring is disabled.
The following table lists and describes the license key types. Table 6-6 License Key Types Type Description Permanent license key Permanent licenses are valid for using HDLM permanently. Temporary license key# Temporary license key are used temporarily, for example, when a user needs to perform product evaluations. Temporary licenses keys are valid for 120 days after the installation. You cannot reuse a temporary license key.
Specifies the severity level of audit log data to be collected. The table below lists and describes the values used for this setting. The default is 6. Table 6-7 Values Indicating Audit Log Data Collection Levels Value (severity) 0 Explanation No audit log data is collected. 1 2 Critical-level audit log data is collected. 3 Critical-level and Error-level audit log data is collected. 4 Critical-level, Error-level, and Warning-level audit log data is collected.
Value Corresponding facility value in the /etc/syslog.conf file local1 or 17 local1 local2 or 18 local2 local3 or 19 local3 local4 or 20 local4 local5 or 21 local5 local6 or 22 local6 local7 or 23 local7 -lbpathusetimes number-of-path-use-times Specifies the number of times the same path can be used for I/O operations when the Round Robin (rr), Least I/Os (lio), or Least Blocks (lbk) algorithm is used for load balancing. You can specify a decimal (base 10) value from 0 to 999999.
Specifies the checking interval (in minutes) for reviewing information about switching of controllers performed by the storage system which is used in the dynamic I/O path control function. Specify a value in the range from 1 to 1440. The default value is "10". -pstv {on|off} Enables or disables the display of the physical storage system information. The default value is "off".
Displays the format of the set operation.
Error-Monitor-Interval Value 210) Number-Of-Times Value 3) AudlogLevel Value 6) Category-Value Value all) Facility-Name Value user) Facility-Number Value 1) Number-Of-PathUseTimes Value 20) Number-Of-ExPathUseTimes Value 100) AutoPATH_ID Dpc-Interval Value 10) KAPL01001-I The HDLM command name = view, completion time # { 1 - 1440 }(Minute) (Default { 1 - 99 }(Times) (Default { 0 - 7 } (Default { [ss] [a] [ca] | all } (Default { user | local0 - local7 } (Default { 1 | 16 - 23 } (Default { 0 - 9999
[-hbaportwwn] [-t] To display path information (by selecting a display item) /usr/DynamicLinkManager/bin/dlnkmgr view -path -item [pn] [dn] [lu] [cp] [type] [ic] [ie] [dnu] [hd] [iep] [hbaportwwn] [phys] [virt] [vid] [ha] [-pstv|-vstv] [-hdev host-device-name] [-stname] [-srt {pn|lu|cp}] [-t] To display a summary of path information /usr/DynamicLinkManager/bin/dlnkmgr view -path -c [-pstv|-vstv] [-stname] [-srt {lu|cp}] [-t] To Display LU Information To display LU information /usr/DynamicLinkManager/bin/
To display a summary of LU information (by adding items to be displayed) /usr/DynamicLinkManager/bin/dlnkmgr view -lu -c -item [[slpr] [vg] | all ] [-pstv|-vstv] [-t] To Display HBA Port Information /usr/DynamicLinkManager/bin/dlnkmgr view -hba [-srt pb] [portwwn] [-t] To Display CHA Port Information /usr/DynamicLinkManager/bin/dlnkmgr view -cha [-srt cp] [-t] Correspondences Between hdisks, OS Management Path IDs, and LDEVs /usr/DynamicLinkManager/bin/dlnkmgr view -drv [-pstv|-vstv] [-t] To Display the
times the same path can be used for load balancing, the number of times the same path can be used for extended load balancing, and the value of the display-of-the-physical-storage-system-information setting. Table 6-11 Displayed Program Information on page 6-37 describes the specifiable parameters, displayed information, displayed items, and a corresponding description. -t Does not display the title for each information item.
Parameter and program informatio n to be displayed Item Elog File Size (KB) Description • 3: Collects error information at the Information level or higher. • 4: Collects error information at the Information level or higher (including maintenance information). Size of the error log file in kilobytes Number Of Elog Number of error log files Files Trace Level Trace output level: • 0: Does not output any trace. • 1: Only outputs error information. • 2: Outputs a summary of program operation.
Parameter and program informatio n to be displayed Item Description When automatic failback is off, intermittent error monitoring is disabled although Intermittent Error Monitor will be shown as on. When the automatic failback function is on, intermittent error monitoring will be enabled.
Parameter and program informatio n to be displayed -pdrv Item HDLM Driver Information about the HDLM driver Ver -lic Description Status of the HDLM driver: Alive: Normal Dead: Stopped Version number of the HDLM driver WakeupTime Startup time of the HDLM driver License Type License type Information about the HDLM license Expiration • Permanent: permanent license • Temporary: temporary license • Emergency: emergency license License expiration When using a permanent license: When using a temp
Parameter and program informatio n to be displayed Item Description If the collection of audit log data is disabled, a hyphen (-) is displayed. Audit Log Facility The name of the audit log facility is displayed. user, local0, local1, local2, local3, local4, local5, local6, or local7 is displayed. If the collection of audit log data is disabled, a hyphen (-) is displayed.
Examples Example 1 The following example shows how to display information about the HDLM function settings: # /usr/DynamicLinkManager/bin/dlnkmgr view -sys -sfunc HDLM Version : x.x.
Example 5 The following example shows how to display information about the HDLM license. # /usr/DynamicLinkManager/bin/dlnkmgr view -sys -lic License Type Expiration Permanent KAPL01001-I The HDLM command completed normally.
To Display Path Information When displaying path information, if you specify either the -item or -c parameter and also specify the -path parameter, you can select the items to display and display a summary of path information. This section describes each parameter, path information and displayed items.
For details about the information displayed for product IDs, see Table 6-15 Product ID Displayed by the View -Path Operation on page 6-56. -iem Use this parameter to add IEP to path information and display information about intermittent errors. -srt {pn|lu|cp} Use this parameter to sort the path information in ascending order, according to the specified sorting keys.
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. The following table lists the correspondence between the display items that can be selected by using the -item parameter and the parameter values that can be specified after the -item parameter.
These sub-parameters are: -pstv|-vstv If the -pstv parameter is specified, information about the physical storage system is displayed. If the -vstv parameter is specified, information about the storage system recognized by the operating system is displayed. If neither parameter is specified, information is displayed according to the value specified in the -pstv parameter of set operations.
When you use this parameter, the items used for the sorting keys (DskName, AutoPATH_ID, and the item specified by this parameter) are displayed by default. Therefore, it is not necessary to specify these items for the -item parameter. -t Omits the title for each information item. Example In the following example, IO-Count is selected as the display item and the path information is sorted in ascending order by LUs.
When you use the -c parameter, the number of characters that can be displayed in the product ID element of the DskName field is limited to 10. When there are 11 or more characters in the product ID, the 8th and following characters are abbreviated to ellipses (...). The sub-parameters (following -path -c) are: -pstv|-vstv If the -pstv parameter is specified, information about the physical storage system is displayed.
Displayed path information Table 6-13 Displayed Path Information on page 6-50 describes the displayed path information. The following explains the table headings: • No summary displayed: The user specifies only the -path parameter or the-path -item parameter. • Summary displayed: The user specifies the -path -c parameter. Table 6-13 Displayed Path Information Displayed Item No summary displayed Description Summary displayed Paths Total number of displayed paths, indicated by a decimal (i.e.
Displayed Item No summary displayed Description Summary displayed IO-Count Total I/O count for all the displayed paths, indicated by a decimal number. The maximum value that can be displayed is 232 - 1 (4294967295). If the total I/O count reaches the maximum value, it is reset, and the count is re-started from 0. IO-Errors Total I/O error count for all the displayed paths, indicated by a decimal number. The maximum value that can be displayed is 232 - 1 (4294967295).
Displayed Item No summary displayed ChaPort#1 Description Summary displayed CP • For the Lightning 9900V series, Hitachi NSC55, Hitachi Universal Storage Platform 100, Hitachi Universal Storage Platform 600, Hitachi Universal Storage Platform 1100, or HUS VM, indicated by a hexadecimal number. The first two characters of iLU are the CU number, and the last two characters are the internal LU number within the CU. • For SVS, indicated by a hexadecimal number.
Displayed Item No summary displayed Type#1 Description Summary displayed Type Attribute of the path • Own: Owner path • Non: Non-owner path When connecting to the Lightning 9900V series, Hitachi USP series, Universal Storage Platform V/VM series, Virtual Storage Platform series, VSP G1000 series, Hitachi AMS2000 series#2, Hitachi SMS series#2, HUS100 series#2, or HUS VM, all paths are owner paths. IOCount#1 - Total I/O count for the path, indicated by a decimal number.
Displayed Item No summary displayed Description Summary displayed • * Indicates that an intermittent error occurred (automatic failbacks do not check the path). HBAPortWW N#1 - A 16-digit hexadecimal number indicating the WWN information for an HBA connected to the storage system. This item is displayed only when you specify -iem together with the -hbaportwwn parameter. PhysicalLDEV - The model ID, serial number, and iLU number of a physical volume are separated by periods and displayed.
Displayed Item No summary displayed Description Summary displayed A storage system name consists of the following three elements, separated by periods: • Vendor ID: The name of the storage system vendor. • Product ID: Indicates the storage system product ID, emulation type, or model ID. For more details, see Table 6-15 Product ID Displayed by the View -Path Operation on page 6-56. • Serial number: The serial number of the storage system. If an HAM environment is not used, a hyphen (-) is displayed.
Element Corresponding information AIX representation Adapter type (example: 00)#2 None Always 00 Adapter number (example: 01)#2 fscsi number (the xx part of fscsixx) The fscsi number, which is displayed by executing the lsdev -C command Target ID (example: 00000000000000E2) Target ID The value of scsi_id, which is displayed by executing the lsattr -El hdisk-name command Host LU number(example: 0001) Logical unit ID or LUN The value of lun_id, which is displayed by executing the lsattr -El hdis
Product ID Model names of storage systems • Hitachi NSC55 • Hitachi Universal Storage Platform V • Hitachi Universal Storage Platform VM With the -stname parameter (Displays the following for the model name) Without the -stname parameter USP_V Hitachi Virtual Storage Platform VSP VSP G1000 VSP_G1000 HUS VM HUS_VM P9500 P9500 XP7 XP7 XP128 XP128 XP1024 XP1024 XP10000 XP10000 XP12000 XP12000 XP20000 XP20000 XP24000 XP24000 # When a summary is displayed by specifying the -path -
sorting key is iLU and its configuration information is displayed for each LU. For details on the contents of each displayed item, see Table 6-18 Displayed LU Information on page 6-64. The subsequent parameters are: -pstv|-vstv If the -pstv parameter is specified, information about the physical storage system is displayed. If the -vstv parameter is specified, information about the storage system recognized by the operating system is displayed.
0041 hdisk7 00000 000014 Online 00001 000015 Online 0042 hdisk8 00000 000016 Online 00001 000017 Online 0043 hdisk9 00000 000018 Online 00001 000019 Online KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss # To display LU information (by adding items to be displayed) -lu -item The items specified with the -item option are displayed among with those displayed by the -lu option.
Item that can be added Subsequent parameter Physical-iLU vid Physical-ChaPort vid Org-Product ha Org-SerialNumber ha Org-iLU ha HaStat hastat All items are displayed all For details on the contents of each displayed item, see Table 6-18 Displayed LU Information on page 6-64. The sub-parameters are: -pstv|-vstv If the -pstv parameter is specified, information about the physical storage system is displayed.
Example 2 When using Hitachi AMS2000 series, Hitachi SMS series, or HUS100 series and displaying LU information with DPC added to the display items: # /usr/DynamicLinkManager/bin/dlnkmgr view -lu -item dpc Product : HUS100 SerialNumber : 9203008 LUs : 3 Dynamic I/O Path Control : on* iLU HDevName DPC PathID Status 000006 hdisk0 on 000000 Online 000003 Online 000007 hdisk1 off 000001 Online 000004 Online 000008 hdisk2 on 000002 Online 000005 Online Command Reference Hitachi Dynamic Link Manager (for AIX) Us
# 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. You cannot specify the -c parameter together with the -hdev or -pathid parameter. For details on the contents of each display item, see Table 6-18 Displayed LU Information on page 6-64.
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 option 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 Information on page 6-64 for the contents of each displayed item.
Displayed LU information Table 6-18 Displayed LU Information on page 6-64 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.
Displayed item No summary displayed Description Summary displayed This number combined with the storage system name (shown in DskName) identifies the LU that is accessed by a path. • For the Lightning 9900V series, Hitachi NSC55, Hitachi Universal Storage Platform 100, Hitachi Universal Storage Platform 600, Hitachi Universal Storage Platform 1100, or HUS VM, indicated by a hexadecimal number.
Displayed item No summary displayed Description Summary displayed off: The dynamic I/O path control function is disabled. -: The dynamic I/O path control function is not supported. OSPathID - OS management path ID. PathID - AutoPATH_ID indicated by a decimal number. AutoPATH_ID is assigned when the host is restarted or when a path configuration is changed. When a new LU was added and the host has not been restarted, AutoPATH_ID is assigned to each path of the LU when you execute the cfgmgr command.
Displayed item No summary displayed Description Summary displayed • 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.) • Online(S): I/O operations to the primary volume (P-VOL) in an HAM environment are suppressed. • Online(D): The paths to the primary volume (P-VOL) in an HAM environment can be recovered automatically. Paths that are Offline(E) or Online(E) require corrective action.
Displayed item No summary displayed Description Summary displayed There is one Dev in an LU, so the number is fixed to 0. IEP#1 - The displayed paths are assumed to be in an intermittent error status and checked whether those paths are to be operated for automatic failback. One of the following values is displayed for each path: • -: Indicates that intermittent error monitoring is disabled or the monitoring time for an intermittent error is out of range.
Displayed item No summary displayed Description Summary displayed • For Hitachi Virtual Storage Platform, indicated by a hexadecimal number. The first two characters of iLU are the number of the logical DKC (Disk Controller), the middle two numbers are the CU number, and the last two characters are the internal LU number within the CU. When a virtual ID is not used, a hyphen (-) is displayed.
Displayed item No summary displayed Description Summary displayed If an HAM environment is not used, a hyphen (-) is displayed. Legend: -: Not displayed #1 This information is displayed when one of the following conditions exist: - The user selected the item to be displayed by using the -lu -item parameter. - all was specified. - No value was specified for the parameter.
Item Description IO-Count Total I/O count for the displayed paths, indicated by a decimal number. The maximum value that can be displayed is 232 - 1 (4294967295). If the total I/O count reaches the maximum value, it is reset, and the count is re-started from 0. IO-Errors Total I/O error count for the displayed paths, indicated by a decimal number. The maximum value that can be displayed is 232 - 1 (4294967295).
Table 6-20 Items Displayed as CHA Port Information Item Description ChaID CHA port ID Product Model ID of the storage system S/N Serial number of the storage system ChaPort Port number of the CHA, which identifies the CHA port that is mounted on the storage system. You can identify an actual CHA port by referencing this number from the storage system management program. IO-Count Total I/O count for the displayed paths, indicated by a decimal number.
To Display the Correspondences Between hdisks, OS Management Path IDs, and LDEVs -drv Use this parameter to display the PathIDs, hdisk name, OS management path IDs, and information about the LDEVs in a storage system (identified by the storage system model ID, serial number, and LU number, separated by periods). For details on the contents of each display item, see Table 6-21 Items Displayed as the Correspondences Between hdisks, OS Management Path IDs, and LDEVs on page 6-73.
# /usr/DynamicLinkManager/bin/dlnkmgr view -drv PathID HDevName OSPathID LDEV 000000 hdisk0 00000 9500V.0051.0005 000001 hdisk1 00000 9500V.0051.0015 000002 hdisk2 00000 9500V.0051.0020 000003 hdisk0 00001 9500V.0051.0005 000004 hdisk1 00001 9500V.0051.0015 000005 hdisk2 00001 9500V.0051.0020 KAPL01001-I The HDLM command completed normally.
add (Adds a Path Dynamically) The dlnkmgr command's add operation batch-adds paths that are connected to the host and not configured on the host. You can execute this command dynamically without any effects on existing paths.
Use this parameter to display the add operation format. Example # /usr/DynamicLinkManager/bin/dlnkmgr add -help add: Format dlnkmgr add -path [-s] KAPL01001-I The HDLM command completed normally. Operation name = add, completion time = yyyy/mm/dd hh:mm:ss # delete (Deletes a Path Dynamically) The dlnkmgr command's delete operation batch-deletes paths whose statuses are Offline(C) from the HDLM-management targets. You can execute this command dynamically without any effects on existing paths.
example, when you want to execute the command in a shell script or batch file. Example # /usr/DynamicLinkManager/bin/dlnkmgr delete -path -s KAPL01165-I A path was deleted. (path ID = = 00010, storage = HITACHI.HUS100.9100163, iLU = 0030) : KAPL01164-I Paths were deleted. (number of paths deleted = 2, completion time = yyyy/mm/dd hh:mm:ss) To Display the Format of the delete Operation -help Use this parameter to display the delete operation format.
6-78 Command Reference Hitachi Dynamic Link Manager (for AIX) User Guide
7 Utility Reference This chapter explains the utilities used by HDLM.
□ installux.
Overview of the Utilities HDLM provides the following utilities: • The DLMgetras utility for collecting HDLM error information When an error occurs, this utility collects the files that contain information to be submitted to your HDLM vendor or maintenance company. For details about the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-5. • The dlmchpdattr utility for changing HDLM default settings This utility changes the default value for the hdisk attribute.
about the dlmpr utility, see dlmpr Utility for Clearing HDLM Persistent Reservation on page 7-26. • The dlmpremkcd utility for preparing for a system backup Execute this utility if the error message KAPL09292-W was output during HDLM installation. For details about the dlmpremkcd utility, see dlmpremkcd Utility for Preparing for a System Backup on page 7-28.
Table 7-1 Examples of the Starting Time of the Host and the Execution Time of the Utilities Operation Execution time of the device configuration on starting the host (when HDLM is installed) Execution time of the device configuration on starting the host (when HDLM is not installed) Executing cfgmgr Executing dlmrmdev Executing view -path Number of paths for an LU/ Total number of paths#2 Execution time#1, #3 4/1024 42 seconds 8/2048 42 seconds 16/4096 43 seconds 4/1024 32 seconds 8/2048 38
collected information is archived in a file and saved to the directory that you specified. The following files are output: • Name-of-the-directory-containing-a-system-crash-dump-file/systemcrash-dump-file This file contains a symbolic link to the system crash dump file. • hbsa.tar.Z This file contains compressed error information of the Hitachi Command Suite products other than HDLM.
The following is an example of the coding in the file that defines the information to be collected. Figure 7-1 Coding Example of a File that Defines the Information to be Collected Rules for coding a file that defines the information to be collected • Use an absolute path to specify a directory or file whose information is to be collected.
entering y instructs the DLMgetras utility to overwrite the existing files; entering n (or anything other than y) instructs the utility to terminate without executing. In the latter case, you can either rename the existing directory before reexecuting the utility, or you can execute the utility with a different directory name specified.
Output directory#1 Files Explanation dlmwebagent[1-16]. log Hitachi Command Suite Common Agent Component log files dlminquiry[1-2].lo g Inquiry log dlminquiry[1-2].tx t dlmguiinst.log Installation linkage script log used when linking with Hitachi Command Suite products other than HDLM hdlmtr[1-64].log Trace file dlmconfig[1-2].log HDLM configuration log dlmconfig[1-2].txt dlmutil[1-2].log HDLM utility's log file installhdlm.log Unattended installation execution log var/ hdlmtr.
Output directory#1 Explanation dlmmgr.xml dlmmgr setting file dlmwebagent.proper ties Hitachi Command Suite Common Agent Component settings file dlmmgr_DPC.xml DPC option setting file usr/lpp/bosinst cdfs.optional.list System backup definition file etc filesystems Mount information of the file system inittab inittab file syslog.
Output directory#1 Files Explanation CuPathAt.txt Information of Object Database Manager CuVPD.txt Information of Object Database Manager disk.txt List of disks in the /dev directory dlmgetomtrace.dmp HDLM function trace dlmls-la.txt HDLM directory information file dlmmgr-cha.txt CHA port information dlmmgr-drv.txt hdisk information dlmmgr-hba.txt HBA port information dlmmgr-lu.txt HDLM LU information dlmmgr-lu-all.
Output directory#1 7-12 Files Explanation lslpp.txt List of installed packages lspath.txt MPIO path information lsps-a.txt Swap area, usage of swap lspv.txt Physical volume information lsvg.txt Information of volume groups MaintenanceLevel.txt Maintenance level of information, displayed when the instfix -i command was executed mount.txt Mount information oslevel.txt OS level information pagesize.txt Memory page size PdAt.txt Information of Object Database Manager PdAtXtd.
Output directory#1 Files Explanation /var/adm/csd vsd.log VSD execution log var/adm/ras boot.log OS boot log file emgr.log Log file for the emgr command #1 An output directory is created in the specified directory when you open the getras.tar.Z file. #2 In the actual file name, a file number is appended to Trace-file-prefix specified-in-the-Hitachi-Network-Objectplaza-Trace-Library-utility2. For example, the default will be hntr21.log to hntr216.log.
In HDLM 6.3 or later, the default reservation policy values for multiple hdisks can be changed simultaneously by executing the dlmchpdattr utility. Format /usr/DynamicLinkManager/bin/dlmchpdattr {-a Attribute=Value [Attribute=Value ...] [-u { HTC | XP }] [-A] [-s] | -o | -h} Parameters -a Attribute=Value Specifies one or more attribute name and attribute value pairs. If specifying multiple pairs, separate them by using a space, and enclose the list of pairs in double quotation marks (").
-u {HTC|XP} Specifies the type of ODM whose default value you want to change. HTC: Specify this if you want to change the default value for HTC_ODM. XP: Specify this if you want to change the default value for XP_ODM. If this parameter is omitted, the change is applied to both HTC_ODM and XP_ODM. -A Performs automatic hdisk reconfiguration required to reflect the changed reservation policy. If this parameter is omitted, the hdisk reconfiguration needs to be performed manually.
# /usr/DynamicLinkManager/bin/dlmchpdattr -a "reserve_policy=no_reserve queue_depth=4" KAPL10579-I The HDLM default values will be changed. Is this OK? [y/n]:y KAPL10571-I The dlmchpdattr utility completed successfully. In the following example, the utility displays the current default hdisk reservation policy: # /usr/DynamicLinkManager/bin/dlmchpdattr -o uniquetype = disk/fcp/Hitachi reserve_policy : no_reserve KAPL10571-I The dlmchpdattr utility completed successfully.
Displays the format of the dlmgetrasinst utility. Note • We recommend that you execute the dlmgetrasinst utility on the HDLM installation DVD-ROM. If you use the utility by copying it to another location from the DVD-ROM, also copy the UtilAudLog file to the same directory to which you copy the dlmgetrasinst file. • Because dlmgetrasinst first stores error information in the specified output directory before compressing, ensure that information collection areas allocated are of adequate size.
Output directory# 7-18 Files Explanation syslog-output-directoryname syslog-name syslog files and backup files defined in /etc/syslog.conf getrasinfo (Not applicable) Directory in which command execution results are stored .bash_history Default history file in the Bourne Again shell (bash) .history Default history file in the C shell (csh) .sh_history Default history file in the Korn shell (ksh) bootlist-v.txt List of boot devices Config_Rules.
Output directory# Files Explanation lsps-a.txt Swap area, usage of swap lspv.txt Physical volume information lsvg.txt Information of volume groups Maintenance-Level.txt Maintenance level of information, displayed when the instfix -i command was executed mount.txt Mount information oslevel.txt OS level information pagesize.txt Memory page size PdAt.txt Information of Object Database Manager PdAtXtd.txt Information of Object Database Manager PdPathAt.
Execute this utility after installing the JDK. For details about the JDK version to be installed, see the JDK required for linkage with Global Link Manager section in Host and OS Support for HDLM on page 3-3. Format /usr/DynamicLinkManager/bin/dlminstcomp [-h] Parameter -h Displays the format of the dlminstcomp utility.
• Make sure you have write permission for odm-environmentsettings-file, set-environment-settings-file, and the storage directory before executing. • Do not change the contents of the saved odm-environmentsettings-file and set-environment-settings-file. -r Restores the settings files by using the names specified in the -odm and set parameters. -odm odm-environment-settings-file-name Specifies the file name in which the ODM environment settings are defined. Specify the file path.
dlmodmset Utility for Setting the HDLM Execution Environment ODM This utility sets and displays ODM to define HDLM operations. Format /usr/DynamicLinkManager/bin/dlmodmset {{-r {on | off} | -i {on | off} | -v {on | off} | -j {on | off}} [-s] | -o | -h } Parameters -r { on | off } Enables or disables the LUN RESET option. on: Enable off: Disable The default is off. To use GPFS, specify on. You do not need to reconfigure the hdisk or restart the host when you change this parameter.
on: Enable off: Disable The default is off. To use HDLM in a client partition to which a virtual HBA is applied by using the NPIV functionality of the virtual I/O server, specify on. For details, see Notes on the Virtual I/O Server on page 3-15. -j {on | off} Sets whether to output HDLM messages to the OS error log. on: Output messages. off: Do not output messages. The default is off. You do not need to reconfigure the hdisk or restart the host when you change this parameter.
LABEL: IDENTIFIER: Date/Time: Sequence Number: Machine Id: Node Id: Class: Type: WPAR: Resource Name: Resource Class: Resource Type: Location: L5C000000000000 HDLM_PATH_FAIL 37269DDB WWW MMM dd hh:mm:ss TTT yyyy 3005 00F8782C4C00 natu U INFO Global hdisk8 disk Hitachi U78AA.001.WZSJPKR-P1-C4-T1-W50060E801082EEA0- Description HDLM detected a path failure. Probable Causes HDLM detected a path failure. Failure Causes A physical or logical error occurred in the path.
Examples In the following example, the utility enables the LUN RESET option: # /usr/DynamicLinkManager/bin/dlmodmset -r on KAPL10805-I The setup of the HDLM execution environment ODM will be changed. Lun Reset = on. Is this OK? [y/n]:y KAPL10800-I The dlmodmset utility completed normally.
• Before you execute the dlmpostrestore utility, stop all application processes that access HDLM-managed devices. • Before you execute the dlmpostrestore utility, make sure that no path errors are occurring. If a path error occurs, release of a reservation may fail. dlmpr Utility for Clearing HDLM Persistent Reservation The persistent reservation of a logical unit (LU) may not be canceled due to some reason when multiple hosts share a volume group rather than making up a cluster configuration.
• When the hdisk-name parameter is omitted, the Reservation Key for the hdisks that makes up rootvg will not be cleared. In this case, the KAPL10670-I message is displayed in the execution result. hdisk-name Specify the hdisk for which you want to display or clear the Reservation Key. You can specify more than one volume. If you omit this parameter, the utility assumes all hdisks. -a When multiple hdisks are specified, even if an error occurs during processing, the processing continues for all hdisks.
hdisk4 Reservation Key : [0xbbbbbbbbbbbbbbbb]*, reserve_policy : PR_exclusive Regist Key : [0xaaaaaaaaaaaaaaaa] , Regist Key : [0xbbbbbbbbbbbbbbbb] , hdisk5 Reservation Key : [0xbbbbbbbbbbbbbbbb]*, reserve_policy : no_reserve Regist Key : [0xbbbbbbbbbbbbbbbb] , hdisk6 Reservation Key : [0x0000000000000000] , reserve_policy : single_path Regist Key : [0xcccccccccccccccc] , hdisk7 Reservation Key : [0x????????????????] , reserve_policy : hdisk8 Reservation Key : following , reserve_policy : PR_shared Regist K
• When the error message KAPL09292-W was output during HDLM installation. Format /usr/DynamicLinkManager/bin/dlmpremkcd {-c | -u | -h} Parameters -c Adds information for HDLM backup to the OS backup setting. -u Deletes the HDLM-backup information from the OS backup setting, and restore the setting to its original state. -h Displays the format of the dlmpremkcd utility.
Parameters -h Displays the format of the dlmpreremove utility. -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).
Unmounts file systems and deactivates volume groups that are being used by HDLM before deleting the hdisks that are recognized as HDLM management-target devices or changing the status of those hdisks to Defined. -s Prevents the confirmation message for unmounting and deactivating the volume groups, when the -A parameter is specified. -h Displays the format of the dlmrmdev utility. Note Before executing the dlmrmdev utility, stop all processes and services using the paths managed by HDLM.
Specify the name of the physical volume on which the persistent reservation you want to cancel is registered. You can specify only one name for hdisk-name. -h Displays the format of the dlmrmprshkey utility. Notes • Verify that the specified physical volume is not used. If it is used, the dlmrmprshkey utility fails with an error. • Verify that no error has occurred on the path connected to the specified physical volume.
For details about the installation-information settings file, see Items To Be Defined in an installation-information Settings File on page 7-33. -h Displays the format of the installhdlm utility. Items To Be Defined in an installation-information Settings File The following describes the information defined in the installation information settings file. [INSTALLATION_SETTINGS] section This section defines information that is used when the installhdlm utility is executed.
Necessity of definition Key name#1 Description#2 Maxim um Upgrade number New installatio of installa n or re- charact tion installatio ers n The default is /var/tmp/ hdlm_license. If you perform an upgrade installation or re-installation without updating the license, delete the licensekeyfile key and value. licensekey#3 Specify the absolute path name of the file that records the license key stored on the host. The file specified here is not deleted after an unattended installation is performed.
However, for an upgrade installation or re-installation, the previous license information will be inherited for the licensekeyfile and licensekey keys. #1 Enter one key and one setting per line. #2 If the value is not of an allowable type, an error will occur. #3 You need to delete the licensekeyfile key if you specify the licensekey key. However, you do not need to delete the licensekey key if you specify the licensekeyfile key.
Table 7-6 Keys in the [DISK_DEFAULT_SETTINGS] Section Necessity of definition Key name#1 reserve_policy Description#2 Specify the disk reservation policy. Maxim um Upgrade number New installatio of installa n or re- charact tion installatio ers n Optional Optional 12 no_reserve: Reservation requests are ignored, and no LU is reserved. PR_exclusive: Uses persistent reservations (exclusive-host methodology) to reserve disks (default).
Table 7-7 Keys in the [ODM_SETTINGS] Section Necessity of definition Key name#1 Description#2 Optional Optional 3 odm_online_e_io_blo Specify one of the following Optional ck values to indicate whether to enable or disable suppression of I/O access on the Online(E) status path: Optional 3 Optional Optional 3 Optional Optional 3 odm_lun_reset Specify one of the following values to indicate whether to enable or disable the LUN RESET option: Maxim um Upgrade number New installatio of installa
If the value is not of an allowable type, an error will occur. For details about the functions set by these keys, see dlmodmset Utility for Setting the HDLM Execution Environment ODM on page 7-22. [ENVIRONMENT_SETTINGS] section This section defines information that is used when the set operation of the HDLM command is executed. This section is optional.
Necessity of definition Key name#1 Description#2 New installa tion Maxim Upgrad um e numbe installa r of tion or charac reters installa tion (rr), Least I/Os (lio), or Least Blocks (lbk) algorithm is used for load balancing. You can specify a value from 0 to 999999. The default is 20.
Necessity of definition Key name#1 Description#2 Optional Optional 3 Optional Optional 4 Optional Optional 3 Specify the interval in minutes from Optional the time the previous path status check finished until the time the next path status check started. Optional 4 Optional Optional 3 intermittent_error Specify the interval in minutes that Optional _monitor_interval# monitoring for intermittent errors is performed.
Necessity of definition Key name#1 dynamic_io_path_co ntrol Description#2 New installa tion Specify whether to enable or Optional disable the dynamic I/O path control function by using the values below. Note that, if this function is set, the setting for each storage system or LU is cleared.
When on is specified for the auto_failback key in the installation information settings file ¢ For an upgrade installation or re-installation: When on is specified for the auto_failback key in the installation information settings file, or when automatic failback is enabled in the installation pre-settings #4 If you want to enable intermittent error monitoring, specify this key after specifying the auto_failback and auto_failback_interval keys.
¢ ¢ 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, enter a hash mark (#) at the beginning of the line that defines that key. Log file A log file (installhdlm.log) is output after an unattended installation of HDLM. The following explains the installhdlm.log file. • installhdlm.
Parameters -f installation-information-settings-file-name Defines the information needed for an unattended installation. For details about installation-information settings files, see Items To Be Defined in an installation-information Settings File on page 7-33. -h Displays the format of the installux.sh utility. Log file The installux.sh utility outputs execution information to the log file /var/tmp/hdlm_installux_sh.log. If the hdlm_installux_sh.
8 Messages This chapter describes the format and meaning of the message IDs, and also the terms used in the messages and message explanations. For details on the meaning of the return codes output by HDLM when it receives a request from Global Link Manager and measures to take for them, see Return Codes for Hitachi Command Suite Common Agent Component on page 8-133.
□ Return Codes for Hitachi Command Suite Common Agent Component 8-2 Messages Hitachi Dynamic Link Manager (for AIX) User Guide
Before Viewing the List of Messages This section explains the following information that is needed to locate messages and understand the explanations in the sections from KAPL01001 to KAPL02000 on page 8-4. • Format and meaning of the message IDs • Terms used in the messages and message explanations This information is explained below. Format and Meaning of Message IDs Each message has a message ID. The following table shows the format and meaning of message IDs.
• HDLM manager • HDLM driver (filter component) • HDLM alert driver • HDLM management target KAPL01001 to KAPL02000 Message ID Message Text KAPL01001- The HDLM command completed normally. I Operation name = aa...aa, completion time = bb...bb Explanation Details The HDLM command completed successfully.
Message ID Message Text Explanation (dlnkmgr) to check the operation name, and then retry. For details on the help operation, see help (Displays the Operation Format) on page 6-4. KAPL01005- A parameter is invalid. Operation name = W aa...aa, parameter = bb...bb Details aa...aa: Specified operation name bb...bb: Specified parameter Action Execute help operationname of the HDLM command (dlnkmgr) to check the parameter, and then retry.
Message ID Message Text Explanation aa...aa: Specified operation name bb...bb: Parameter name Action Specify the parameter value, and then retry. KAPL01009- A parameter value is invalid. Operation W name = aa...aa, parameter = bb...bb, parameter value = cc...cc, Valid value = dd...dd Details aa...aa: Specified operation name 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.
Message ID Message Text Explanation bb...bb: The name of the function and processing on which the error occurred Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-5. KAPL01014- No authority to execute the HDLM W command. Operation name = aa...
Message ID Message Text Explanation -pathid option required by the -cha parameter could not be found, or the CHA that has the channel ID (CHA_ID) specified in the chaid parameter could not be found. aa...aa: offline or online Action ¢ If the path ID of the path management path was specified in pathid Execute the view operation of the HDLM command (dlnkmgr view -path), and check the value of the target CHA port and the path ID of the path management path that passes through that CHA port.
Message ID Message Text Explanation 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 view (Displays Information) on page 6-34. KAPL01019- The target path was not found. Operation W name = aa...aa Details aa...aa: offline, online, or view ¢ offline/online operation The specified path does not exist.
Message ID Message Text Explanation configure any paths that exist. If the same message appears again, execute the DLMgetras utility for collecting HDLM error information, acquire the error information, and then contact your HDLM vendor or the company for which you have a service contract. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-5. KAPL01021- Cannot execute the HDLM command due E to insufficient memory.
Message ID Message Text Explanation Execute help operation of the HDLM command (dlnkmgr) to check which parameters can be specified at the same time, and then retry. For details on the help operation, see help (Displays the Operation Format) on page 6-4. KAPL01036- The Offline path cannot be placed online. E PathID = aa...aa Details aa...aa: Path ID (decimal (base-10) number) Action Remove the error in the path, and then retry.
Message ID Message Text Explanation incorrect value was entered three times in a row for a request. aa...aa: clear, offline, online, or set Action Check the correct value, and then re-execute the HDLM command. KAPL01044- A duplicate parameter value is specified. W Operation name = aa...aa, parameter = bb...bb, parameter value = cc...cc Details aa...aa:view bb...bb: Parameter name cc...cc: Duplicate parameter value Action Delete the duplicate parameter value, and then retry.
Message ID Message Text Explanation (Displays the Operation Format) on page 6-4. KAPL01049- Would you like to execute the operation? I Operation name = aa...aa [y/n]: Details The clear/set operation will be started. To continue the operation, enter y. To cancel the operation, enter n. aa...aa: clear or set Action If you want to execute the operation, enter y. If you want to terminate processing, enter n.
Message ID Message Text Explanation y. If you want to terminate processing, enter n. Before you execute the processing, be sure to execute the view operation of the HDLM command (dlnkmgr) to check the path status. For details on the view operation, see view (Displays Information) on page 6-34. For details on the online operation, see online (Places Paths Online) on page 6-11. KAPL01052- The currently selected paths will be I changed to the Offline(C) status.
Message ID Message Text Explanation 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. If you want to terminate processing, enter n. For details on the offline operation, see offline (Places Paths Offline) on page 6-6. KAPL01055- All the paths which pass the specified I aa...aa will be changed to the Offline(C) status.
Message ID Message Text Explanation terminate processing, enter n. KAPL01057- All the paths which pass the specified I aa...aa will be changed to the Online status. Is this OK? [y/n]: Details Multiple paths will all be placed in Online status because the -hba or -cha parameter was specified. To continue the operation, enter y; to cancel the operation, enter n. aa...aa: CHA port, HBA Action If you want to execute online processing for the paths that meet the specified requirements, enter y.
Message ID Message Text Explanation Execute help operationname of the HDLM command (dlnkmgr) to check the parameter and parameter value, and then retry. For details on the help operation, see help (Displays the Operation Format) on page 6-4. KAPL01060- The user terminated the operation. I 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- aa...
Message ID Message Text Explanation As a result of a previous online/offline operation, the specified path has already been set to Online/Online(S)/ Online(D)/Offline(C). aa...aa: Online, Online(S), Online(D), or Offline(C) Action Use the view operation of the HDLM command (dlnkmgr) to check the status of the path. For details on the view operation, see view (Displays Information) on page 6-34. For details on the online operation, see online (Places Paths Online) on page 6-11.
Message ID Message Text Explanation key was entered three times in a row. Action Obtain a valid license key, and then retry. KAPL01071- The permanent license was installed. I Details The license was renewed and is registered as a permanent license. Action None. KAPL01072- The emergency license was installed. The I license expires on aa...aa. Details A license was renewed and is registered as an emergency license. aa...
Message ID Message Text Explanation Action None. KAPL01078- The operation terminated because the W path configuration changed during execution of the HDLM command. Operation name = aa...aa Details aa...aa:offline, online, view Action After the processing to change the path configuration has finished, retry. KAPL01079- The intermittent error monitoring function Details W cannot be set up because automatic The intermittent error failback is disabled.
Message ID Message Text KAPL01082- There is no installable license key in the E license key file. File name = aa...aa Explanation Details There is no useable license key for HDLM in the license key file. aa...aa: /var/tmp/ hdlm_license Action Make sure that the license key file is correct, and then re-execute. /var/tmp/hdlm_license KAPL01083- There is no license key file. File name = I aa...aa Details There is no license key file in the designated directory: aa...
Message ID Message Text Explanation Execute help operationname of the HDLM command (dlnkmgr) to check which parameter can be specified, and then retry. For details on the help operation, see help (Displays the Operation Format) on page 6-4. KAPL01089- One of the following was executed at the E same time as an HDLM command set -lic operation: another set -lic operation, or an update of the license for an update installation. Action Check the license by using the HDLM command's view -sys -lic operation.
Message ID Message Text KAPL01096- An attempt to acquire the Service Pack E version information has failed. details = aa...aa Explanation Details 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, acquire the error information, and then contact your HDLM vendor or the company for which you have a service contract. KAPL01097- All the current trace files will be deleted.
Message ID Message Text Explanation Use the view operation of the HDLM command (dlnkmgr view -hba) to check the target HBA port and the HBA_ID of the target HBA port. After that, specify the appropriate HBA_ID, and then retry. KAPL01102- All the paths which pass the specified I 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 hbaid or -chaid parameter was specified.
Message ID Message Text Explanation place multiple paths Online, enter y. To not collectively place them Online, enter n. aa...aa:CHA, HBA Action 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. KAPL01112- An attempt to connect to the HDLM driver Details E has failed. Operation name = aa...
Message ID Message Text Explanation Collecting HDLM Error Information on page 7-5. KAPL01114- The audit log configuration file does not W exist. Restart the HDLM Manager, and execute the "dlnkmgr view -sys -audlog" command and check the setting. Details The audit log configuration file does not exist.
Message ID Message Text Explanation there is a maintenance contract for HDLM. KAPL01118- An error occurred during processing to W output the audit log configuration file. Details An internal parameter error when the audit-log data was output. Action Contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. KAPL01119- An error occurred during processing to W output the audit log configuration file.
Message ID Message Text Explanation or the maintenance company if there is a maintenance contract for HDLM. KAPL01133- aa...aa path(s) were successfully placed I bb...bb; cc...cc path(s) were successfully placed dd...dd; ee...ee path(s) were not. Operation name = ff...ff Details The number of paths processed by an online operation is shown. aa...aa: The number of paths which changed to the Online status bb...bb: Online or Online(S) cc...
Message ID Message Text KAPL01154- The dynamic I/O path control function is W already set to aa...aa for the system. Explanation Details aa...aa: "on" or "off" Action Use the view operation of the HDLM command (dlnkmgr) to check the setting for the host, storage, and LUs. For details on the view operation, see view (Displays Information) on page 6-34. KAPL01155- The dynamic I/O path control function is W already set to aa...aa for storage. Details aa...
Message ID Message Text Explanation Use the view operation of the HDLM command (dlnkmgr) to check the path ID. For details on the view operation, see view (Displays Information) on page 6-34. KAPL01159- Paths were added. (number of paths I added = aa...aa, completion time = bb...bb) Details This message indicates that an add operation succeeded. aa...aa: number of paths added bb...
Message ID Message Text Explanation - Check whether the paths to be deleted are in the Offline(C) status. - Use the view operation of the HDLM command (dlnkmgr) to check whether the paths have already been deleted from HDLM. KAPL01161- This operation will change the path I configuration. Do you want to continue? [y/n]: Details This message confirms whether to perform a path configuration change by using an add operation or delete operation.
Message ID Message Text Explanation Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or, if you have a maintenance contract for HDLM, the maintenance company. KAPL01164- Paths were deleted. (number of paths I deleted = aa...aa, completion time = bb...bb) Details This message indicates that a delete operation succeeded. aa...aa: number of paths deleted bb...
Message ID Message Text Explanation Action If you want to change the number of times that the same path can be used for the system, enter y. To cancel the operation, enter n. KAPL01167- All paths will be set to Online or I Online(D). Is this OK? [y/n]: Details All paths will be set to Online or Online(D) because no path is specified. To continue, enter y. To cancel the operation, enter n. Action To set all paths to Online or Online(D), enter y. To cancel the operation, enter n.
Message ID Message Text Explanation Action To execute online processing, enter y. To cancel the operation, enter n. Before you execute the processing, you must check the path status by executing the view operation of the HDLM command dlnkmgr. KAPL01170- All Online(S) or Online(D) paths that are Details I connected to the LU that has the specified All paths in the Online(S) path ID will be set to Online. Is this OK? or Online(D) status for [y/n]: each specified LU will be set to Online.
Message ID Message Text Explanation Online(S)/Online(D) status among the specified paths. Action Use the view operation of the HDLM command (dlnkmgr) to check the status of the path. KAPL01173- The target CHA port was constructed from Details W multiple physical CHA ports. Operation In an environment where name = aa...aa. Specify a physical CHA storage systems are port by using the "-cha -pathid" virtualized, when you parameter.
Message ID Message Text Explanation aa...aa: phys, vid, ha, or hastat Action When specifying physical storage information as a display item, disable the Physical Storage View. KAPL03001 to KAPL04000 Message ID Message Text KAPL03001-I HDLM API information - aa...aa Explanation Details This information is required for resolving problems. aa...aa: Trace information Action None. KAPL03003E HDLM API Error information - aa...aa Details This information is required for resolving problems. aa...
Message ID Message Text Explanation error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-5. KAPL03006E An access to the HDLM driver causes an error. (aa...aa) Details This information is required for resolving problems. aa...
Message ID Message Text Explanation aa...aa: API trace error information Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-5. KAPL03999E An unexpected error occurred. Details Conflicting versions of HDLM modules are being used.
Message ID Message Text Explanation contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-5. KAPL04003- The startup parameter is invalid. E Details The HDLM manager internal parameter is invalid.
Message ID Message Text Explanation If the KAPL04033-W message is output after this message, execute the dlnkmgr view -sys sfunc command, and then check the option settings. For options with setting values that have returned to default values, use the dlnkmgr set operation to reset the values. If the KAPL04033-W message is not output, restart HDLM manager. If the same error occurs, re-install HDLM. For details on the view operation, see view (Displays Information) on page 6-34.
Message ID Message Text Explanation HDLM manager could not start normally because it was unable to create a pipe file, which is used in communication with HDLM commands. aa...aa: OS error code (decimal (base-10) number) Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Message ID Message Text Explanation Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-5. KAPL04019- Could not collect the error information. E RC = aa...aa Details An attempt to read the log information from the alert driver failed. aa...
Message ID Message Text Explanation Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-5. KAPL04023- HDLM manager error information - aa...aa Details E This information is required for resolving problems. aa...
Message ID Message Text Explanation KAPL04025- A memory shortage occurred in the HDLM Details C manager. There was not enough memory to run the HDLM manager processes. Action Increase the amount of memory available for the process. KAPL04026- The temporary license is valid. The I license expires in aa...aa days on (bb...bb). Details aa...aa: Expiration day bb...bb: The year of grace (4 numeric characters)/ Month (01-12)/Day (01-31) Action Install a permanent license by the expiration day.
Message ID Message Text KAPL04033- The option definition file was re-created. W Explanation Details When an existing option definition file cannot be read, a new option definition file will be recreated by using the default values. If some of the options can be read, those values can be used. As for any remaining values, the default values will be used. Action For any non-defaults options, use the dlnkmgr set operation to set the options again.
Message ID Message Text Explanation error by path health checking. Action None. KAPL04037- The path health check completed I normally. Path ID = aa...aa Details All the paths that path health checking examined are fine. aa...aa: Path ID for the path examined by path health checking. Action None. KAPL04042- HDLM SNMP TRAP information - aa...aa I Details All the paths that path health checking examined are fine. aa...aa: Start or stop Action None. KAPL04045- HDLM SNMP TRAP was sent. Trap ID = I aa...
Message ID Message Text Explanation to occur even after the procedure is performed, 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 DLMgetras Utility for Collecting HDLM Error Information on page 7-5. KAPL04053- The option definition file was recovered W from a work file. Action KAPL04054- The owner controller will now be revised.
Message ID Message Text Explanation or exclude the LU from dynamic I/O path control. KAPL05001 to KAPL06000 Message ID Message Text KAPL05003-I The HDLM driver (filter component) was successfully attached to Disk (aa...aa), Partition (bb...bb). Explanation Details The path corresponding to Disk (aa...aa: Disk sequence number) and Partition (bb...bb: Fixed at 0) was successfully registered in the core logic. Action None. KAPL05008E Could not allocate memory.
Message ID Message Text Explanation contact your vendor or maintenance company. Refer to the HDLM User's Guide for instructions how to execute the DLMgetras utility. (hdisk) decimal sequence number) and Partition (bb...bb: Partition decimal number) failed in the core logic. cc...cc: Error code (hexadecimal number) dd...dd: Filter driver management table address (hexadecimal number) Action Check whether the HDLM driver has started normally.
Message ID Message Text Explanation contact the HDLM vendor or the maintenance company if you have a maintenance contract for HDLM KAPL05021-I Processing of IOCTL (aa...aa) completed normally. Details The processing for the requested IOCTL operation was successful. aa...aa: IOCTL code (hexadecimal number) Action None. KAPL05023E Could not process the IOCTL(aa).
Message ID Message Text Explanation Action Contact your HDLM vendor or maintenance company if you have a maintenance contract for HDLM. KAPL05508-I Data for maintenance(PathCheck): Error Code = aa...aa, Status Validity = bb...bb, Status Code = cc...cc, Sense Code = dd...dd Details This message outputs the details of a path check error. aa...aa: Error code bb...bb: Status Validity cc...cc: Status code dd...dd: Sense code Action None. KAPL05509-I Data for maintenance(Adapter): Error Code = aa...
Message ID Message Text KAPL05512-I Data for maintenance(SenseData): Sense Key = aa...aa, Sense Code = bb...bb Explanation Details This message outputs the details of a path failure. aa...aa: Sense Key bb...bb: Sense Code Action None. KAPL05819-I Data for maintenance: aa...aa bb...bb cc...cc dd...dd. Details The filter driver outputs this message for maintenance. aa...aa: Device minor number bb...bb: Message output location information cc...cc: Detailed information 1 dd...
Message ID Message Text Explanation started or contains an error, 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 and report the error and detail code. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-5. KAPL06009-I Invalid IOCTL (aa...aa) was received. The processing is canceled.
Message ID Message Text Explanation Collecting HDLM Error Information on page 7-5. KAPL06013E Could not write log information into the log buffer. (aa...aa:bb...bb) Details When a log output request was made from the filter driver, the log information was discarded because of a memory allocation failure. Alternatively, although an HDLM driver message or HDLM alert driver message, or a nonemergency message (C/I) by the core logic was generated, its log information was discarded by the HDLM alert driver.
Message ID Message Text Explanation emergency message (such as a path error message) detected by the core logic was generated as an output message, its log information was discarded by the HDLM alert driver. aa...aa: Message code (hexadecimal number) bb...bb: Buffer size (hexadecimal number) Action Check whether any other error occurred. The information that could not be written is discarded. Review the actual memory size if another error does not occur.
Message ID Message Text Explanation (decimal (base-10) number) cc...cc: Detailed information 2 (decimal (base-10) number) dd...dd: Detailed information 3 (decimal (base-10) number) Action None. KAPL07824- The owner controller of the LU connected I to the path (aa...aa) was changed to (bb...bb). Details The owner controller of the LU connected to the path with the ID shown in the message was changed. aa...aa: Path ID of the changed LU. (same as PathID of view -path) (Decimal number) bb...
Message ID Message Text Explanation likely due to a disconnected cable. aa...aa: Path identifier (hexadecimal number) bb...bb: Error code (hexadecimal number) ¢ When the path error is detected by a path health checking or the online operation Displays 0x000F0000 (Fixed). ¢ When a path error is detected through an I/O error The OS error code is displayed. cc...cc: 0x00000000 (fixed) Action Check the path in which the error was detected. KAPL08022E A path error occurred. ErrorCode = aa...
Message ID Message Text Explanation ee...ee: Target ID (hexadecimal number) ff...ff: Host LU number (same as PathName of view -path) (hexadecimal number) gg...gg: Dev number (same as DNum of view path) (decimal number) hh...hh: Host device name Action There could be an error in the path. See What To Do for a Path Error on page 5-3 and restore the path displayed in the message to running status. KAPL08023-I A path was recovered. PathID = aa...aa, PathName = bb...bb.cc...cc.dd...dd.ee...ee, DNum = ff...
Message ID Message Text Explanation aa...aa: Path ID (same as PathID of view -path) (decimal (base-10) number) Action Errors are detected in all the paths connected to the LUs. See What To Do for a Path Error on page 5-3 to make the path shown in the error message or the paths connected to the target LU. KAPL08027E A path was excluded from the items subject to automatic failback. PathID = aa...
Message ID Message Text Explanation aa...aa: Path ID (same as PathID of view -path) (decimal (base-10) number) Action To return a path to the Online(D) status, resolve the path failure, and then execute the "dlnkmgr online -dfha" command. KAPL09001 to KAPL10000 Message ID Message Text KAPL09003- Cannot install in this system. Install E HDLM on a supported OS. Explanation Details Installation of HDLM failed because the OS is not supported. Make sure that you are using a supported OS.
Message ID Message Text KAPL09013- Some HDLM drivers could not be E removed. Explanation Details The dlmrmdev command was run, but HDLM drivers could not be removed. Action Check the HDLM driver status and remove the drivers. KAPL09019- An attempt to cancel the registration of E the bundle PP name of Hitachi Network Objectplaza Trace Library 2 failed.
Message ID Message Text Explanation HDLM cannot be removed because the HDLM manager, HDLM driver is running. aa...aa: HDLM manager, HDLM driver Action Execute the dlmrmdev utility, and then re-execute the remove program. KAPL09023- A file or directory related to HDLM could E not be found. Re-install HDLM. Details A target file to copy to the directory of Hitachi Command Suite products other than HDLM could not be found among the files related to HDLM Action Re-install HDLM.
Message ID Message Text Explanation agent/module/ HDLMWebAgent.class /usr/HDVM/agent/ classes/jp /usr/HDVM/agent/ classes/com/Hitachi/ soft/HiCommand/DVM/ agent/module/hdlm /usr/HDVM/HBaseAgent/ agent/classes/com/ Hitachi/soft/ HiCommand/DVM/agent/ module/ HDLMWebAgent.class /usr/HDVM/HBaseAgent/ agent/classes/jp /usr/HDVM/HBaseAgent/ agent/classes/com/ Hitachi/soft/ HiCommand/DVM/agent/ module/hdlm KAPL09028- An attempt to install Hitachi Network E Objectplaza Trace Library 2 failed.
Message ID Message Text KAPL09048- HDLM cannot be installed. aa...aa is E running. Explanation Details An attempt to install HDLM failed because either of aa...aa is running. aa...aa: HDLM manager, HDLM driver Action Execute the dlmrmdev utility, and then re-execute the installation program. KAPL09076- The permanent license was installed. I Details The permanent license was installed. Action None. KAPL09077- The temporary license was installed. The I license expires on aa...aa.
Message ID Message Text Explanation KAPL09081- The emergency license has been installed. Details I The license expires on aa...aa. The emergency license has been installed. aa...aa: Year (4 digits)/ month (01-12)/day (01-31) Action Install a permanent license by the expiration day. KAPL09082- The temporary license expired. W Action KAPL09083- The emergency license expired. W Action KAPL09087- The entered license key is invalid. E Renewal of the license key will now stop.
Message ID Message Text KAPL09100- Installation is not possible because E aa...aa is already installed. Explanation Details Installation is not possible because the fileset that was output in the message is installed. aa...aa: DLManager.rte or AutoPath.rte (character string) Action Re-install after removing the fileset that was output in the message. KAPL09112- The license key file is invalid. File name = Details E aa...
Message ID Message Text Explanation correct license key file in the designated directory, and then re-execute the installation. /var/tmp/hdlm_license KAPL09115- An attempt to delete the license key file W has failed. File name = aa...aa Details An attempt to delete the license key file has failed. aa...aa : /var/tmp/ hdlm_license Action If a license key file exists, delete it. /var/tmp/hdlm_license KAPL09116- The command could not be installed. W (command = aa...
Message ID Message Text KAPL09142- HDLM aa...aa cannot be performed. Wait E a while, and then perform aa...aa again. Error Code =bb...bb Explanation Details HDLM cannot be installed or removed. aa...aa: "installation" or "remove" bb...bb: Internal code (decimal (base-10) number) Action Wait a while, and then reperform the installation or remove. After the installation or remove has finished, use the backup acquired in advance and specify the HDLM settings. KAPL09143- HDLM aa...aa cannot be performed.
Message ID Message Text Explanation If any other error code is output: Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL09172- Installation is not possible because an E hdisk exists. Action KAPL09179- Data for maintenance: aa...aa bb...bb I Details Delete the hdisk, and then re-execute the installation program. aa...aa: Message output location information (decimal (base-10) number) bb...bb: Detailed information (character string) Action None.
Message ID Message Text Explanation Action Make sure that the parameters for installhdlm are appropriate, and then try again. KAPL09190- The installation information settings file is Details W not specified. The installation information settings file is not specified for the second parameter in the installhdlm utility for installing HDLM. Action Make sure that the parameters in the installhdlm utility are appropriate, and then try again.
Message ID Message Text KAPL09212- aa...aa ended abnormally. E Explanation Details aa...aa ended abnormally. aa...aa: installhdlm, installp, cfgmgr, dlmodmset, dlnkmgr, or dlmrmdev Action Check the error message that was output just before this message, and then perform the action indicated in that error message. KAPL09213- An error occurred during aa...aa W processing. Details Although the aa...aa processing has ended, an error occurred during the processing. aa...
Message ID Message Text Explanation specifies the executed processing Action If the error code is 1: The /tmp directory does not exist. Prepare the /tmp directory, and then retry the operation. If the error code is 2: You do not have write permission for the /tmp directory. Make sure that you have access permissions for the /tmp directory. If the error code is 3 : You do not have write permission for the file system of the /tmp directory.
Message ID Message Text Explanation If the error code is 7: There is not enough unused capacity for the file system of the /var/tmp or /var/DLM directory. Make sure there is enough unused capacity for these directories. If the error code is 8: The /var directory does not have enough unused capacity, or the user does not have write permission for it. Make sure there is enough unused capacity and that the user has write permission for this directory, and then try again.
Message ID Message Text Explanation processing (decimal (base-10) number) bb...bb: Return value of the executed processing (decimal (base-10) number) Action Make sure that sufficient unused capacity exists for the /tmp directory. If the capacity is insufficient, allocate the required amount of capacity, and then retry the operation. For details about how to determine the amount of capacity that is required, see Performing an Unattended Installation of HDLM on page 3-69.
Message ID Message Text Explanation in the correct location, or you do not have a required permission. aa...aa: installhdlm_analysis, dlmodmset, dlnkmgr, or dlmrmdev Action If aa...aa is dlmodmset or dlnkmgr : The correct location of dlmodmset and dlnkmgr is /usr/ DynamicLinkManager/ bin. If dlmodmset or dlnkmgr was not in the correct location, or you did not have a required permission, re-execute installhdlm If aa...
Message ID Message Text Explanation bb...bb: Return value (decimal number) of the executed processing Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL09220- The composition of the installation W information settings file is invalid. Error Code = aa...aa,bb...
Message ID Message Text Explanation settings file, and then retry the operation. KAPL09227- The definition of the installation W information settings file includes an invalid key. Error Code = aa...aa,bb...bb, line = cc...cc Details A key that does not exist is included. aa...aa: Error number (decimal number) that specifies the executed processing bb...bb: Return value (decimal number) of the executed processing cc...cc: Line number (decimal number) of an installation information settings file.
Message ID Message Text Explanation bb...bb: Return value (decimal number) of the executed processing cc...cc: Line number (decimal number) of an installation information settings file. Action Specify the revised installation information settings file and then retry the operation. KAPL09230- The definition of the installation W information settings file includes a duplicated section name. Error Code = aa...aa,bb...bb, line = cc...cc Details A duplicated section name is included. aa...
Message ID Message Text Explanation settings file and then retry the operation. KAPL09232- The composition of the definition of the W installation information settings file is invalid. Error Code = aa...aa,bb...bb, line = cc...cc Details A key, key value, or equal sign (=) is missing. aa...aa: Error number (decimal number) that specifies the executed processing bb...bb: Return value (decimal number) of the executed processing cc...
Message ID Message Text Explanation Specify the revised installation information settings file and then retry the operation. KAPL09235- The log file cannot be output to its E destination because the environment is invalid. Error Code = aa...aa Details The log file cannot be output in this environment, because certain environment settings are invalid. aa...aa: Error number (decimal number) that specifies the executed processing.
Message ID Message Text Explanation Check the error message output before this message, and then perform the action indicated in that error message. KAPL09237- A user operation ended installhdlm. I Details The process has been terminated by an operation such as Ctrl+C. Action Check the status of HDLM by executing lslpp -la DLManager.mpio.rte. If HDLM is not installed: Re-execute installhdlm.
Message ID Message Text Explanation maintenance company (if an HDLM maintenance contract exists). KAPL09238- The specified file is not a normal one. Fail W name = aa...aa Details A file other than a normal one (for example, a directory file or a special file.) is specified. aa...aa: Specified file name (character string) Action Specify the correct file, and then retry the operation. KAPL09239- The system will now restart.
Message ID Message Text Explanation re-execute dlminstcomp utility. If the error code is 200: Execute dlminstcomp utility. If any other error code is output: Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL09242- No usable JDK or JRE exists. E Details No prerequisite JDK version is installed in the system. Action Install a prerequisite JDK version, and then reexecute dlminstcomp utility. KAPL09243- dlminstcomp completed successfully.
Message ID Message Text Explanation Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL09248- A parameter is invalid. parameter = W aa...aa Details An invalid parameter is specified. aa...aa: The specified parameter (character string) Action With the -h parameter specified, execute the dlminstcomp utility. Make sure that the format of the utility is correct, and then re-execute it.
Message ID Message Text Explanation not affect HDLM operations. If HDLM messages are output to the OS error log, execute the following command: /usr/bin/errupdate -q f /usr/ DynamicLinkManager/ common/.dlmfdrv_err_tem plate If the message is output after command execution is complete, resolve the problem according to the message, and then reexecute the errupdate command. KAPL09504- The language environments of HDLM and E the Service Pack are different.
Message ID Message Text Explanation Confirm that the command or utility (aa...aa) exists, and that you have the proper permission. aa...aa: Name of the command or utility that cannot be executed. Action When the output information is an HDLM utility: ¢ ¢ If an installation is performed from the DVD-ROM, confirm that the DVD-ROM is not damaged. If an installation is performed by using files copied from the DVD-ROM, re-copy all of the DVD-ROM files.
Message ID Message Text Explanation be output has been specified. Action Check the parameters of the DLMgetras utility for collecting HDLM error information, and then retry. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-5. KAPL10002- Too many parameters have been W 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.
Message ID Message Text Explanation collecting HDLM error information, and then retry. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-5. KAPL10005- The number of parameters is insufficient. W Details The -f parameter exists but the file for defining the information to be collected does not exist. Action Check the parameters of the DLMgetras utility for collecting HDLM error information, and then retry.
Message ID Message Text Explanation DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-5. KAPL10008- You lack write permission for the specified Details W directory. Value = aa...aa You do not have write permission for the specified directory, or the creation of a subdirectory of the specified directory failed. aa...aa: first parameter Action Check the following. KAPL10009- The specified directory already exists. Do W you want to overwrite it? [y/n]: a.
Message ID Message Text Explanation information to be collected (decimal number) Action Delete the coding of the root directory from the specified file. The displayed directory will be ignored and the DLMgetras utility for collecting HDLM error information will continue. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-5. KAPL10011- More than one file or directory has been W specified on one line. Line = aa...aa, Value = bb...
Message ID Message Text Explanation where information is to be collected. aa...aa: Line number of the file for defining which information to be collected (decimal (base-10) number) bb...bb: Indicated contents of a line Action After the DLMgetras utility for collecting HDLM error information terminates, check the contents of the file for defining which information to be collected. This file is shown in the message.
Message ID Message Text Explanation correct them and then try to collect error information again. The DLMgetras will ignore the specified file and continue processing. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-5. KAPL10014- You lack read permission for the specified W directory. Line = aa...aa, Value = bb...bb Details You lack read permission for the specified directory in the file for defining information to be collected. aa...
Message ID Message Text Explanation information terminates, check whether the file for defining the information to be collected is a text file. The file is shown in the message. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-5. KAPL10016- The root directory has been specified in W the first parameter. Details A root "/" cannot be specified in a directory to which collected information is output.
Message ID Message Text KAPL10021- Processing terminated before completion I because a signal was received. Explanation Details The process has been terminated by an operation such as Ctrl+C. Action The utility for collecting HDLM error information terminated before completion. If the directory is unnecessary, delete directory. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-5.
Message ID Message Text Explanation collecting HDLM error information will terminate because an invalid response was sent three times in a row to a request. Action Re-execute the DLMgetras utility. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-5. KAPL10033- The file does not exist. Filename = aa...aa Details W No file to collect information exists. aa...aa: File to collect Action None. KAPL10034- The file could not be copied. Filename = E aa..
Message ID Message Text Explanation or your maintenance company if you have a maintenance contract for HDLM. KAPL10036- An attempt to compress the error E information failed. Details = aa...aa Details Execution of the compress command failed. aa...aa : compress command output message Action See the details in the message, and then remove the cause of the error.
Message ID Message Text Explanation Action Execute help of the dlmrmdev utility to check the parameters that can be specified, and then retry. For details on the dlmrmdev utility, see dlmrmdev Utility for Deleting HDLM Drivers on page 7-30. KAPL10523- An attempt to unmount the file system E has failed. (file system = aa...aa) Details aa...aa: failed file system (character string) Action Make sure of the status of the failed file system and then re-execute the program.
Message ID Message Text Explanation the HDLM User's Guide for instructions how to execute the DLMgetras utility. aa...aa: error code (decimal number) Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL10526- An attempt to unmount the file system I has succeeded. (file system = aa...aa) Details aa...aa: file system succeeded (character string) Action None. KAPL10527- An attempt to inactivate the volume I group has succeeded. (volume group = aa..
Message ID Message Text Explanation Check the hdisk status and re-execute the dlmrmdev utility. KAPL10531- The status of all of the HDLM drivers was I changed to "Defined". Action KAPL10532- The status of one or more HDLM drivers E could not be changed to "Defined". Action KAPL10551- The dlmpostrestore utility completed I successfully. Action None. Check the hdisk status and re-execute the dlmrmdev utility. None.
Message ID Message Text Explanation To execute dlmpostrestore utility, enter y. If you do not want to execute dlmpostrestore utility, enter n. KAPL10556- The entered value is invalid. Re-enter. W [y/n]: Details A value other than y or n has been entered for a [y/n] request. Action Enter either y or n. KAPL10557- The user stopped the operation. I Details The dlmpostrestore utility has been terminated because n was sent to a request. Action None. KAPL10558- The entered value is invalid.
Message ID Message Text Explanation dlmpostrestore utility. Any other error code: Contact your HDLM vendor or the maintenance company, if you have an HDLM maintenance contract. KAPL10560- The system environment is invalid. Error E Code = aa...aa Details The system environment is not valid as an environment for executing the dlmpostrestore utility. aa...aa: Error number (decimal number) Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Message ID Message Text Explanation dlmchpdattr utility. Make sure that the format of the utility is correct, and then re-execute it. KAPL10574- The specified parameters cannot be W specified at the same time. parameter = aa...aa Details aa...aa: The specified parameter Action With the -h parameter specified, execute the dlmchpdattr utility. Make sure that the format of the utility is correct, and then re-execute it. KAPL10575- No parameter value has been specified.
Message ID Message Text Explanation aa...aa: The specified attribute Action With the -h parameter specified, execute the dlmchpdattr utility. Make sure that the format of the utility is correct, and then re-execute it. KAPL10579- The HDLM default values will be changed. I Is this OK? [y/n]: Details This message confirms whether it is okay to execute the dlmchpdattr utility. Action With the -h parameter specified, execute the dlmchpdattr utility.
Message ID Message Text Explanation occurred during dlmchpdattr utility processing. aa...aa: Error number (decimal number) bb...bb: Return code (decimal number) Action If the error code is 9,1: Confirm that all of the processes and services that use HDLM managed paths have stopped, and then restart them. If the error code is 19,1: Check for path errors. If there is a path error, restore the path status and then retry.
Message ID Message Text Explanation If the error code is 6,2 or 7,-1: The bosboot command is not in the default location, or the user does not have execution permissions for the bosboot command. Check the status of the bosboot command. If the error code is 9,2 or 10,-1: The dlmpr utility is not in the default location, or the user does not have execution permissions for the dlmpr utility. Check the status of the dlmpr utility.
Message ID Message Text Explanation None. KAPL10587- The specified ODM is not installed. W parameter value = aa...aa Details The specified ODM is not installed. aa...aa: Specified parameter value Action Specify an ODM that has been installed, and then retry the operation. KAPL10588- A duplicate attribute has been specified. W attribute = aa...aa Details A duplicate attribute has been specified. aa...aa: Specified attribute Action Delete the duplicate attribute, and then retry the operation.
Message ID Message Text KAPL10644- The specified parameters cannot be W specified at the same time. parameter = aa...aa Explanation Details The specified parameters cannot be specified for the dlmpr utility at the same time. aa...aa: specified parameter (character string) Action Execute the dlmpr -h utility to check the parameter, and then retry execution. For details on the dlmpr utility, see dlmpr Utility for Clearing HDLM Persistent Reservation on page 7-26. KAPL10645- A parameter value is invalid.
Message ID Message Text KAPL10648- An internal error occurred in the dlmpr E utility. Error Code = aa...aa Explanation Details An error not caused by the user has occurred in the dlmpr utility. aa...aa: error number (decimal number) Action If a message with Error Code = 35 is output, check for the hdisk was deleted. If the hdisk was deleted, recover the state of the hdisk and then retry.
Message ID Message Text KAPL10650- aa...aa: NO RESERVATION I Explanation Details A LU has not been reserved. aa...aa: Hdisk name Action None. KAPL10651- The user terminated the operation. I Details The dlmpr utility has been terminated because n was sent to a request. Action None. KAPL10652- The entered value is invalid. The E operation stops. Details An invalid response was sent three times consecutively to a request. Action Re-execute the dlmpr utility. KAPL10653- The entered value is invalid.
Message ID Message Text Explanation clear the HDLM persistent reservation. KAPL10800- The dlmodmset utility completed I normally. Details The dlmodmset utility completed normally. Action None. For details on the dlmodmset utility, see dlmodmset Utility for Setting the HDLM Execution Environment ODM on page 7-22. KAPL10801- No parameter has been specified. W operation = aa...aa Details No parameter has been specified. aa...
Message ID Message Text Explanation the HDLM User's Guide for instructions how to execute the DLMgetras utility. aa...aa: Error Code (character string) Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the dlmodmset utility, see KAPL08001 to KAPL09000 on page 8-56. KAPL10805- The setup of the HDLM execution I environment ODM will be changed. aa...aa = bb...bb.
Message ID Message Text Explanation No operation has been specified. Action Execute help of the dlmodmset utility to check the operations that can be specified, and then retry. For details on the dlmodmset utility, see KAPL08001 to KAPL09000 on page 8-56. KAPL10810- An operation is invalid. operation = W aa...aa Details The specified operation is invalid. aa...
Message ID Message Text Explanation ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ Get SNMP Trap Information Set SNMP Trap Information Set LU Load Balance Get Path Status Log Information Get Local Time Add Path Information Delete Path Information Set Storage Identification Information Action None. KAPL11902-I aa...aa has started. PathID = bb...bb Details The operation has started on the management-target host. aa...aa: Operation (character string) ¢ Online ¢ Offline bb...
Message ID Message Text Explanation ¢ Get HDLM Alert Driver Status ¢ Online ¢ Offline ¢ ¢ ¢ ¢ Get SNMP Trap Information Set SNMP Trap Information Set LU Load Balance Get Path Status Log Information ¢ Get Local Time ¢ Add Path Information ¢ ¢ Delete Path Information Set Storage Identification Information Action None. KAPL11904E aa...aa has completed abnormally. Error status = bb...bb Details The operation has completed abnormally on the host. aa...
Message ID Message Text Explanation ¢ ¢ ¢ Add Path Information Delete Path Information Set Storage Identification Information bb...bb: Error status returned from API (character string) Action Execute the DLMgetras utility for collecting HDLM error information to collect the 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 DLMgetras Utility for Collecting HDLM Error Information on page 7-5.
Message ID Message Text Explanation This information is required for resolving problems. aa...aa: XML information Action None. KAPL11908-I XML transmission - aa...aa Details This information is required for resolving problems. aa...aa: XML information Action None. KAPL13001 to KAPL14000 Message ID Message Text Explanation KAPL13001-I The dlmmigsts utility completed successfully. Action KAPL13002E Action The dlmmigsts utility ended abnormally. None.
Message ID Message Text Explanation Assisting HDLM Migration on page 7-20. KAPL13007W No parameter has been specified. KAPL13008W A parameter is invalid. parameter = aa...aa Action Specify the -h option in the HDLM migration support utility, confirm the option that should be specified, and then reexecute. For details about the dlmmigsts utility, see dlmmigsts Utility for Assisting HDLM Migration on page 7-20. Details aa...
Message ID Message Text Explanation dlmmigsts again, and then re-execute.If parameter = -set, specify dlnksetfile in dlmmigsts again, and then re-execute. For details about the dlmmigsts utility, see dlmmigsts Utility for Assisting HDLM Migration on page 7-20. KAPL13011W The number of parameters is insufficient. Action KAPL13012W Too many parameters have been specified. KAPL13013E The directory for storing the specified file Details could not be created. Filename = aa...aa aa...
Message ID Message Text Explanation Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL13015E There is an invalid character in the file. parameter = aa...aa, Filename = bb...bb Details aa...aa: Parameter (character string) bb...bb: Filename (character string) Action If parameter = -odm, execute dlmodmset one after another, or specify the modified odmsetfile in dlmmigsts again, and then re-execute.
Message ID Message Text Explanation Guide for instructions how to execute the DLMgetras utility. KAPL13019E The same file name was specified for odmsetfile and dlnksetfile. Filename = aa...aa, bb...bb Details aa...aa: odmsetfile Filename bb...bb: dlnksetfile Filename Action Check file name, and then try again. KAPL13020E The file odmsetfile was not restored. KAPL13021E The file dlnksetfile was not restored. Action Check file name, and then try again. Action Check file name, and then try again.
Message ID Message Text Explanation Action None. KAPL13108E An internal error occurred in the Details dlmpreremove utility. Error Code = A system-based error, not aa...aa, bb...bb Execute the DLMgetras caused by the user, utility to collect error information, and occurred during then contact your vendor or maintenance dlmpreremove utility company. Refer to the HDLM User's processing. Guide for instructions how to execute the aa...aa: The error number DLMgetras utility.
Message ID Message Text Explanation utility, see dlmpreremove Utility for Executed Before Removing HDLM on page 7-29. KAPL13141-I The dlmpremkcd utility completed successfully. Details The dlmpremkcd utility completed successfully. Action None. KAPL13142W No parameters were specified. Details No parameters were specified. Action With the -h parameter specified, execute the dlmpremkcd utility. Make sure that the format of the utility is correct, and then re-execute it.
Message ID Message Text Explanation Action To execute the dlmpremkcd utility, enter "y". If you do not want to execute the dlmpremkcd utility, enter "n". KAPL13146W The entered value is invalid. Re-enter. [y/n]: Details A value other than y or n has been entered for a [y/n] request. Action Enter either "y" or "n". KAPL13147-I The user stopped the operation. Details The dlmpremkcd utility was terminated because the response to a request was "n". Action None. KAPL13148E The entered value is invalid.
Message ID Message Text Explanation environment for executing the dlmpremkcd utility. aa...aa: Error number (decimal number) bb...bb: Return code (decimal number) Action Contact your HDLM vendor or the maintenance company, if you have an HDLM maintenance contract. KAPL13151-I Processing terminated before completion because a signal was received. Details The dlmpremkcd process has been terminated by an operation such as Ctrl+C. Action None. KAPL13157-I The dlmrmprshkey utility completed successfully.
Message ID Message Text Explanation The specified parameters cannot be specified at the same time. aa...aa: The specified parameter Action With the -h parameter specified, execute the dlmrmprshkey utility. Make sure that the format of the utility is correct, and then re-execute it. KAPL13161W No parameter value has been specified. Details No parameter value has been specified. Action With the -h parameter specified, execute the dlmrmprshkey utility.
Message ID Message Text Explanation Action Enter either "y" or "n". KAPL13165-I The user stopped the operation. Details The dlmrmprshkey utility was terminated because the response to a request was "n". Action None. KAPL13166E The entered value is invalid. The operation will now stop. Details The dlmrmprshkey utility has been stopped because an invalid response was sent three times consecutively to a request. Action To execute dlmrmprshkey utility again, enter either "y" or "n".
Message ID Message Text Explanation maintenance contract, the maintenance company. KAPL13168E The system environment is invalid. Error Code = aa...aa,bb...bb Details The system environment is not valid as an environment for executing the dlmrmprshkey utility. aa...aa: Error number (decimal number) bb...bb: Return code (decimal number) Action Contact your HDLM vendor or the maintenance company, if you have an HDLM maintenance contract. KAPL13169W The specified device is not targeted for processing.
Message ID Message Text Explanation settings by using the "dlnkmgr set -audlog" command or the "dlnkmgr set -audfac" command as necessary. KAPL13602W 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.
Message ID Message Text Explanation company if there is a maintenance contract for HDLM. KAPL13606W An error occurred during processing to output the audit log configuration file. Details An internal 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. KAPL15001 to KAPL16000 Message ID Message Text Explanation KAPL15001-I The registered value of ReserveKey was successfully displayed.
Message ID Message Text Explanation KAPL15060-I DLMgetras was invoked. Command Line = aa...aa Details KAPL15061-I DLMgetras successfully executed. Command Line = aa...aa Details KAPL15080-I The information about the HDLM default configuration ODM was displayed successfully. Command Line = aa...aa Details KAPL15081E aa...aa: Name of the utility that the user executed aa...
Message ID KAPL15094E Message Text An attempt to clear the server from the PR_shared reservation for the target device has failed. Command Line = aa...aa Explanation Details aa...aa: Command that the user executed KAPL15101-I Clear operation was completed successfully. Command Line = aa...aa Details KAPL15102E Details Clear operation has failed. Command Line = aa...aa KAPL15103-I aa...aa path(s) were successfully placed bb...bb. cc...cc path(s) were not. Command Line = bb...bb aa...
Message ID Message Text Explanation KAPL15110E An attempt to display information about HDLM-management targets has failed. Command Line = aa...aa Details KAPL15111W The HDLM command was started or stopped by the user who does not have the authority. Command Line = aa...aa Details aa...aa: Command that the user executed aa...aa: Command that the user executed KAPL15116-I bb...bb path(s) were successfully placed Details aa...aa. dd...dd path(s) were successfully aa...aa: Online or placed cc...cc.
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. Message ID 1002 Explanation 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.
Message ID 1017 Explanation Details The target path(s) are already Offline(C). Action Update the host information, and then check the path status. 1019 Details An error occurred during HDLM internal processing. 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 DLMgetras Utility for Collecting HDLM Error Information on page 7-5.
Message ID Explanation Set the intermittent error-monitoring interval to a value that is equal to or greater than (automatic- failback-checkinginterval x number-of-times-error-is-to-occur-forintermittent-error-monitoring). 1033 Details An attempt to acquire the HDLM version information failed. Action Re-execute the command.
Message ID Explanation 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 DLMgetras Utility for Collecting HDLM Error Information on page 7-5. 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.
A Functional Differences Between Versions of HDLM This section explains the functional differences between newer and older versions of HDLM. □ Functional Differences Between Version 6.2 and Versions Earlier than 6.2 □ Functional Differences Between Version 6.1 and Versions Earlier than 6.1 □ Functional Differences Between Version 6.0 or Later and Versions Earlier than 6.
Functional Differences Between Version 6.2 and Versions Earlier than 6.2 • In HDLM version 6.1.0 or earlier, when you create a system replication (clone) on another LPAR or host from an mksysb image by using the mksysb command provided by the OS, you needed to remove HDLM before executing the mksysb command. In HDLM version 6.2.0 or later, you do not need to remove HDLM before executing the mksysb command.
B Differences Between HDLM Version 5.9 or Later and Version 5.8.1 or Earlier HDLM version 5.9 or later supports MPIO used by AIX 5L V5.2 or later, which has improved compatibility with the OS. The items explained in the following subsections represent the changes from HDLM version 5.8.1 or earlier.
Add-in HDLM Driver Module HDLM version 5.9 or later supports MPIO used by AIX 5L V5.2 or later. This has improved compatibility with the OS because users can use standard OS commands to manage paths on HDLM management-target devices. As compared to HDLM version 5.8.1 or earlier, HDLM version 5.9 or later differs in terms of the HDLM driver structure, environment configuration, and HDLM operation procedures.
• Eliminating the rc.shutdown file HDLM version 5.8.1 or earlier provided an rc.shutdown file in order to avoid having physical volumes already defined when a host is started. Because this situation does not occur in HDLM version 5.9 or later, the rc.shutdown file is no longer provided. For this reason, the manual has been changed as follows: ¢ ¢ The portion of the procedure related to the rc.shutdown file has been deleted from the explanation of removing HDLM. The rc.
Commands of the utilities for operating HDLM volume groups ¢ Corresponding AIX commands dlmrestvg restvg dlmsavevg savevg dlmsyncvg syncvg dlmunmirrorvg unmirrorvg dlmvaryoffvg varyoffvg dlmvaryonvg varyonvg dlmcfgmgr utility for managing the HDLM configuration In HDLM version 5.9 or later, the AIX cfgmgr command is used.
Migrating Reservation Control Settings In HDLM version 5.8.1 or earlier, the reservation control setting is called the reservation level and is specified by using the set operation with the -rsv on parameter. The target of the reservation level was every LU in an HDLM management-target device. However, you can set the reservation policy specification on each LU if the AIX version is AIX 5L V5.2 or later. The reservation control setting is specified by using the chdev command in HDLM version 5.9 or later.
Changing a Virtual I/O Server's Method of Recognizing Virtual SCSI Disks In HDLM version 5.8.1 or earlier, either PVID or unique_id can be selected as the method used by a virtual I/O server for recognizing virtual SCSI disks. In HDLM version 5.9 or later, only unique_id can be used because of the MPIO specification. Also, the -u and the -e parameters of the dlmodmset utility for setting the HDLM execution environment ODM are no longer provided because they are also not necessary.
Acronyms and abbreviations The following acronyms and abbreviations might be used in this guide.
D DBMS Database Management System Dev Device DNS Domain Name Server F FC Fibre Channel FC-SP Fibre Channel Security Protocol FO Failover FQDN Fully Qualified Domain Name G GMT Greenwich Mean Time GUI Graphical User Interface H HBA Host Bus Adapter HDev Host Device # A B C D E F G H I J K L M N O P Q R S Acronyms-2 Hitachi Dynamic Link Manager (for AIX) User Guide T U V W X Y Z
HLU Host Logical Unit HTTP Hypertext Transfer Protocol I I/O Input/Output IP Internet Protocol iSCSI Internet Small Computer System Interface L LAN Local Area Network LDAP Lightweight Directory Access Protocol LDEV Logical Device LPAR Logical Partition LU Logical Unit LUN Logical Unit Number LVM Logical Volume Manager # A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Acronyms-3 Hitachi Dynamic Link Manager (for AIX) User Guide
M MPIO Multipath I/O N NAS Network Attached Storage NIM Network Installation Management NPIV N-Port ID Virtualization NTP Network Time Protocol O ODM Object Data Manager OS Operating System P P Port PCI Peripheral Component Interconnect PVID Physical Volume Identifier # A B C D E F G H I J K L M N O P Q R S Acronyms-4 Hitachi Dynamic Link Manager (for AIX) User Guide T U V W X Y Z
R RADIUS Remote Authentication Dial in User Service S SAN Storage Area Network SCSI Small Computer System Interface SLPR Storage Logical Partition SMIT System Management Interface Tool SMTP Simple Mail Transfer Protocol SNMP Simple Network Management Protocol SP Service Pack SSL Secure Sockets Layer SVP Service Processor V VG # Volume Group A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Acronyms-5 Hitachi Dynamic Link Manager (for AIX) User Guide
W WWN World Wide Name # A B C D E F G H I J K L M N O P Q R S Acronyms-6 Hitachi Dynamic Link Manager (for AIX) User Guide T U V W X Y Z
Glossary This glossary explains the terms used in this manual. A automatic failback A function for checking the status of paths at regular intervals, and automatically placing the status of a path recovered from an error into the Online status. If a path with an Offline(E) or Online(E) status recovers from an error, an automatic failback will place the path Online.
CLPR(Cache Logical Partition) A function supported by the Hitachi USP series, Universal Storage Platform V/VM series, Virtual Storage Platform series, VSP G1000 series, Hitachi AMS2000/AMS/WMS/SMS series, HUS100 series, and HUS VM for logically splitting up a cache. This function can splits up a cache into parity groups in the storage system, so that other parity groups do not affect the cache performance.
failover A function for switching to another normal path if there is an error in the current access path, thereby enabling the system to continue to operate. H HAM environment An environment in which volume pairs that are synchronized between two storage systems are created by HAM (High Availability Manager), and hosts are configured to recognize these volumes as one volume. An HAM environment consists of the primary volume (P-VOL) in the primary site and the secondary volume (S-VOL) in the secondary site.
host LU number A number assigned to a host LU. The host LU number is part of a path name. (See also: host LU, path name) I intermittent error An error that occurs irregularly due to, for example, a loose cable connection. 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.
Non-owner controllers exist only in when the Thunder 9500V series, or Hitachi AMS/WMS series. (See also: owner controller, non-owner path) non-owner path A path that passes through a non-owner controller. Non-owner paths exist only in when the Thunder 9500V series, or Hitachi AMS/WMS series. (See also: owner path, non-owner controller) O ODM (Object Data Manager) An AIX-dedicated database for managing system information. HDLM uses ODM to add or delete drivers.
When an error occurs on a path that was in the Online status, path health checking changes the status of the path to the Offline(E) status. Path health checking checks only those paths that have the Online status.
slot number A value indicating the location of a slot on which a HBA is mounted. SLPR (Storage Logical Partition) A function supported by Hitachi USP series, Universal Storage Platform V/VM series, Virtual Storage Platform series, and VSP G1000 series for logically splitting up a storage system. This function splits up the resources, such as ports, CLPR, and volumes, in the storage system, so that the user can manage each resource independently.
# A B C D E F G H I J K L M N O P Q R S Glossary-8 Hitachi Dynamic Link Manager (for AIX) User Guide T U V W X Y Z
Index A active host 2-44 adapter number 3-16, 6-56 adapter type 3-16, 6-56 add 6-75 audit log categories and audit events that HDLM can output 2-37 collecting data 2-35 data format 2-41 automatic failback 2-18, 6-23, Glossary-1 automatic failover 2-14 automatic path switching 2-14 AutoPATH_ID 2-3, Glossary-1 B base 10 6-50 boot disk environment Glossary-1 buffer size 3-88 changing the buffer size per monitoring interval duration 3-90 bus number 6-55 C CHA 2-4 CHA (Channel Adapter) Glossary-1 changing HDLM
D decimal number, meaning 6-50 default and recommended values 6-19 delete 6-76 Dev 2-3, 2-4, Glossary-2 Dev number Glossary-2 directory to which collected information is output 7-6, 7-16 Displayed program information 6-37 displaying information 6-34 LU information 6-57 path information 6-34, 6-44 path information (by selecting a display item) 6-35 program information 6-34, 6-36 summary of path information 6-35 dlmchpdattr 7-13 DLMgetras 5-6, 5-7 dlmgetras 7-5 dlmgetrasinst 7-16 dlminstcomp 7-19 dlmmigsts 7-
H HAM environment Glossary-3 handling path error 5-3 HBA 2-4 HBA (Host Bus Adapter) Glossary-3 HBA adapter number 6-55 HDev 2-5 HDevName 5-3 HDLM features 1-2 functions 2-1 installing 3-18 Migrating 3-61 migration of 3-13 new installation 3-26 new installation of 3-13 overview 1-1 preparations for an upgrade installation or reinstallation of 3-37 preparations for new installation of 3-24 program information 6-36 re-installation of 3-14 removing 3-101 setup 3-78 type of installation 3-13 upgrade installation
intermittent error Glossary-4 definition 2-19 K kernel mode switching 3-25 L LB 8-3 LDEV (Logical Device) Glossary-4 load balancing 1-2, 2-8, 6-20, Glossary-4 load balancing algorithms 2-12 load distribution using load balancing 2-8 log filter 2-34 logging level values 6-20 logical device file Glossary-4 logical unit 2-3 logical unit ID 6-56 logical volume number Glossary-2 LU 2-4 configuration 2-5 LU (Logical Unit) Glossary-4 LUN 6-56 M manual path switching 2-19 message examining 5-5, 5-6 format and m
P P 2-4 path 2-3, Glossary-5 adding dynamically 6-75 checking the configuration 3-77 deleting dynamically 6-76 path error handling 5-3 path health checking 1-3, 2-29, 6-22, Glossary-5 path information obtaining 5-5 path name Glossary-6 path priority number 2-16 path status transition 2-20 path switching automatically 2-14 manually 2-19 PathID 5-2 PathName 5-3 Paths to which load balancing is applied 2-10 PCI bus number 6-55 Performing Failovers and Failbacks Using Path Switching 2-14 persistent reservation
kernel mode 3-25 switching destination path, priority of syslog 2-33 system configuration 2-3 V 2-16 vendor ID 6-51, 6-54, 6-55 W T taking actions for hardware error 5-5 program error 5-6, 5-7 target ID 6-56 trace file 2-32 trace file size 6-22 trace level values 6-22 types of collected logs 2-32 types of error information 2-32 Warning 2-33 what is HDLM? 1-2 working environment view (view operation) U unattended installation installation-information settings file 7-33 log file 7-43 upgrade installatio
Hitachi Dynamic Link Manager (for AIX) User Guide
Hitachi Data Systems Corporate Headquarters 2845 Lafayette Street Santa Clara, California 95050-2639 U.S.A. www.hds.com Regional Contact Information Americas +1 408 970 1000 info@hds.com Europe, Middle East, and Africa +44 (0)1753 618000 info.emea@hds.com Asia Pacific +852 3189 7900 hds.marketing.apac@hds.
