Hitachi Command Suite Dynamic Link Manager Software User Guide for AIX® Document Organization Product Version Getting Help Contents MK-92DLM111-21
© 2011-2012 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. (hereinafter referred to as "Hitachi") and Hitachi Data Systems Corporation (hereinafter referred to as "Hitachi Data Systems").
Contents Preface..................................................................................................xi Intended audience....................................................................................................xii Product version........................................................................................................xii Release notes...........................................................................................................xii Document revision level...
The online path status...........................................................................2-20 The offline path status...........................................................................2-20 Correspondence Between Path Statuses Displayed by the OS and by HDLM2-20 Status transitions of a path....................................................................2-21 Monitoring intermittent errors (functionality when automatic failback is used)...........2-23 Checking intermittent errors...........
Notes on Storage Systems...............................................................................3-15 Notes on the Cluster.......................................................................................3-16 Notes on the Automatic Failback......................................................................3-16 Notes on the queue_depth Parameter Value for an HDLM-Managed device.........3-16 Installing HDLM..........................................................................................
Setting the Audit Log Facility..................................................................3-79 Checking the Updated Settings........................................................................3-79 Setting up Integrated Traces.................................................................................3-80 Notes on Using the Hitachi Network Objectplaza Trace Library...........................3-81 Displaying the Hitachi Network Objectplaza Trace Library setup menu................
Displaying the Correspondences Between hdisks, OS Management Path IDs, and LDEVs..............................................................................................................4-8 Initializing Statistical Information for Paths.........................................................4-9 Viewing and Setting Up the Operating Environment...........................................4-10 Viewing the Operating Environment........................................................
Format.............................................................................................................6-3 To Set the Path Statistics to 0..................................................................6-3 To Display the Format of the Clear Operation............................................6-3 Parameters......................................................................................................6-3 To Set the Path Statistics to 0.....................................................
Format.............................................................................................................7-5 Parameters......................................................................................................7-5 List of Collected Error Information..................................................................... 7-7 dlmchpdattr Utility for Changing HDLM Default Settings...........................................7-12 Format............................................................
KAPL08001 to KAPL09000......................................................................................8-48 KAPL09001 to KAPL10000......................................................................................8-51 KAPL10001 to KAPL11000......................................................................................8-77 KAPL11001 to KAPL12000....................................................................................8-102 KAPL13001 to KAPL14000.......................................
Preface This document describes how to use the Hitachi Dynamic Link Manager.
Intended audience This manual is intended for system administrators who use Hitachi Dynamic Link Manager (HDLM) to operate and manage storage systems. The readers of this manual must have a basic knowledge of the following areas: • AIX and its management functionality • Storage system management functionality • Cluster software functionality • Volume management software functionality Product version This document revision applies to HDLM for AIX version 7.3 or later.
Chapter Description 4 HDLM Operation on page 4-1 Describes procedures for operating HDLM by using the HDLM commands, and procedures for manually starting and stopping the HDLM manager. This chapter also describes how to configure the appropriate environment for operating HDLM, such as changing the HDLM management-target devices that connect paths or replacing the hardware that comprises a path.
Document conventions This document uses the following typographic conventions: Convention Description Bold Indicates text on a window, other than the window title, including menus, menu options, buttons, fields, and labels. Example: Click OK. Italic Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: copy source-file target-file Note: Angled brackets (< >) are also used to indicate variables.
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,024 MB or 1,0243 bytes 1 TB 1,024 GB or 1,0244 bytes 1 PB 1,024 TB or 1,0245 bytes 1 EB 1,024 PB or 1,0246 bytes Getting help The Hitachi Data Systems customer support staff is available 24 hours a day, seven days a week. If you need technical support, log on to the Hitachi Data Systems Portal for contact information: https://portal.hds.
xvi Preface Hitachi Dynamic Link Manager User Guide for AIX®
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 User Guide for AIX®
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 User Guide for AIX®
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 ¢ Hitachi AMS2000 series# ¢ Hitachi SMS series ¢ HUS100 series# # 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-32. 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.
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 two statuses. The following explains the two online path statuses and the two offline statuses. The online path status The online path statuses are as follows: • Online I/Os can be issued normally. • Online(E) An error has occurred on the path, but none of the other paths that access the same LU are in the Online status.
Table 2-5 Correspondence Between Path Statuses Displayed by the OS and by HDLM Path status displayed by an AIX command Path status displayed by the HDLM Can be used Either Online or Online(E) Cannot be used Offline(C) Error Offline(E) Status transitions of a path The following figure shows the status transitions of a path. Figure 2-9 Path status transitions Legend: Online operation: Online operation performed by executing the dlnkmgr command's online operation.
#2 When the following conditions are satisfied, a path that has been determined to have an intermittent error also becomes subject to automatic failback: ¢ ¢ ¢ All the paths connected to an LU are Online(E), Offline(E), or Offline(C). All the paths connected to an LU have been determined to have an intermittent error. The processing of continuous I/O operations issued to an LU is successful.
Monitoring intermittent errors (functionality when automatic failback is used) An intermittent error refers to an error that occurs irregularly because of something like a loose cable. In such a case, I/O performance might decrease while an automatic failback is being performed to repair an intermittent error. This is because the automatic failback operation is being performed repeatedly (because the intermittent error keeps occurring).
Intermittent Error Monitoring Actions Intermittent error monitoring is performed on each path, and it automatically starts as soon as a path is recovered from an error by using the automatic failback function.
the path again at a later time, error monitoring will resume when the path is recovered from the error via an automatic failback. If it takes a long time for an error to occur, an intermittent error can be more easily detected by increasing the error-monitoring interval or by decreasing the number of times that the error needs to occur. The figure below shows the action taken when an intermittent error is assumed not to have occurred on the path.
The figure below shows the action taken when the conditions for an intermittent error are changed during intermittent error monitoring. For this example, the conditions have been changed from 3 or more errors in 30 minutes, to 3 or more errors in 40 minutes. The events that occur are described by using the time arrows.
User operation Number of errors and time passed since error monitoring started Information about paths not subject to automatic failback intermittent error monitoring is being performed Turning intermittent error monitoring on by executing the set operation, (but not changing the conditions) while intermittent error monitoring is being performed Changing the intermittent error monitoring conditions while intermittent error monitoring is not being performed (Not applicable) (Not counted.
The number of errors and the time passed since error monitoring had started are both reset to 0, and then monitoring restarts from the time the setting change is made in accordance with the changed monitoring conditions. #3 The number of errors and the time passed since error monitoring had started are both reset to 0, and then monitoring restarts from the time the HDLM manager starts.
statuses on the controller and prevents storage system performance from decreasing. The following is a list of the storage systems that provide the dynamic load balance controller function and are supported by HDLM. • Hitachi AMS2000 series# • HUS100 series # For using the dynamic load balance controller function there are restrictions on the versions of the microprograms you install. For details, see the release notes of HDLM.
Figure 2-13 Flow of Data When Collecting Error Information 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.
Table 2-7 Types of error information Log name Integrated trace file Description Operation logs of the HDLM command are collected. Output destination The default file path is /var/ opt/hitachi/HNTRLib2/ spool/hntr2[1-16].log. To specify the output destination directory and the file prefix for the integrated trace file, use a Hitachi Network Objectplaza Trace Library (HNTRLib2) utility. Trace file Trace information on the HDLM manager is collected at the level specified by the user.
Log name HDLM configuration log Description HDLM configuration log is an operation log of the configuration processing for the HDLM driver. Output destination /var/DynamicLinkManager/ log/dlmconfig[1-2].log # When you want to configure the system so that HDLM messages are output to syslog, specify user for the facility in the /etc/syslog.conf file. The following shows an example where the system function name is user, and messages at the info level or higher are output to the /tmp/ syslog.user.
¢ Collects error information at the Error level and higher. ¢ Collects error information at the Warning level and higher. ¢ Collects error information at the Information level and higher. ¢ Collects error information at the Information level and higher (including maintenance information).
Collecting Audit Log Data HDLM and other Hitachi storage-related products provide an audit log function so that compliance with regulations, security evaluation standards, and industry-specific standards can be shown to auditors and evaluators. The following table describes the categories of audit log data that Hitachi storagerelated products can collect.
Category ConfigurationAccess Maintenance AnomalyEvent Explanation An event indicating that a permitted operation performed by the administrator has terminated normally or failed, including: • Viewing or updating configuration information • Updating account settings, such as adding and deleting accounts • Setting up security • Viewing or updating audit log settings An event indicating that a maintenance operation has terminated normally or failed, including: • Adding or removing hardware componen
Category Explanation Audit event Severit y#1 Message ID Startup of the HDLM manager failed. 3 KAPL15402-E The HDLM manager stopped. 6 KAPL15403-I Startup of the DLMgetras utility 6 KAPL15060-I Termination of the DLMgetras utility#2 6 KAPL15061-I Startup of the dlmgetrasinst utility 6 KAPL15084-I Termination of the 6 KAPL15085-I Permission has not been granted to execute the HDLM command. 4 KAPL15111-W Permission has not been granted to execute HDLM utilities.
Category Explanation Audit event Severit y#1 Message ID An attempt to display program information failed. 3 KAPL15108-E An attempt to display HDLM managementtarget information was successful. 6 KAPL15109-I 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.
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.
• 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. Filtering by severity: The following table lists the severity levels that can be specified.
¢ [process-ID] ¢ message-section The following shows the format of message-section and explains its contents.
Item# Explanation 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 identification Program identification information information Reserved area This
Figure 2-14 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 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 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 User Guide for AIX®
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. 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 AIX V7.1 (Virtual I/O Server)#3 Kernel ioslevel 2.1.0.0 to 2.2.1.xx (where xx is a number) #1 Every SP is applicable, unless otherwise specified. #2 To set up a boot disk environment that uses Thunder 9500V series, Hitachi AMS/WMS series, or Hitachi SMS series, use SP2 or a later service pack. #3 An environment in which the Secure by Default functionality is enabled during installation of the OS is not supported.
¢ Universal Storage Platform V/VM series (excluding XP20000 and XP24000) ¢ Hitachi Virtual Storage Platform ¢ HUS100 series Note: When you install HTC_ODM in an HDLM environment where XP_ODM has already been installed, install HTC_ODM, and then re-install HDLM. • XP_ODM 5.0.52.1 or later If you are using the following storage systems, use XP_ODM 5.0.52.
• P9500 • SVS • HUS100 series The applicable storage systems require a dual controller configuration. If you use the system in a hub-connected environment, you must set unique loop IDs for all connected hosts and storage systems. For details about microprograms, see the HDLM Release Notes. HBA For applicable HBAs, see the HDLM Release Notes.
OS Related Programs • Oracle RAC 10g 10.1.0.5.0 If the HDLM device is specified for direct access: ASM + raw devices#1 • Oracle RAC 10g 10.2.0.2.0 If the HDLM device is specified for direct access: ASM + raw devices#1, or raw devices#1 • Oracle RAC 10g 10.2.0.3.0 If the HDLM device is specified for direct access: ASM + raw devices#1#2 • Oracle RAC 10g 10.2.0.4.0 If the HDLM device is specified for direct access: ASM + raw devices#1 • Oracle RAC 10g 10.2.0.5.
OS Related Programs • VCS 5.1#4 • Oracle RAC 10g 10.2.0.4.0 If the HDLM device is specified for direct access: ASM + raw devices • Oracle RAC 10g 10.2.0.5.0 If the HDLM device is specified for direct access: raw devices • Oracle RAC 11g 11.2.0.2.0 If the HDLM device is specified for direct access: ASM + raw devices • Oracle RAC 11g 11.2.0.3.0 If the HDLM device is specified for direct access: ASM + raw devices • GPFS 3.3#3#7 • GPFS 3.4#3 AIX V6.1 (Virtual I/O • Server)#5 PowerHA 5.
OS Related Programs • PowerHA 7.1.1 Client: No Technology Level Server: ioslevel 2.1.0.0 to 2.2.1.xx (where xx is a number) #1 When using Technology Level 05, apply IY92037. #2 If you have updated the host environment by, for example, applying Oracle-specific patches, the Oracle I/O timeout threshold (MISSCOUNT) might have been changed. Therefore, when you update an environment, you need to review the MISSCOUNT value. #3 Only the NSD (Network Shared Disk) configuration is supported.
Disk Capacity Requirements The following table lists the disk capacity used by the host. Table 3-5 Disk Capacity Occupied by the Host Directory Disk capacity requirement /etc 150 KB /opt 2 MB /usr 220 MB /var p MB#1 +4MB + 2 MB + q MB#2 + 19 MB + 200 KB#3 #1 This value depends on the error log file settings. The maximum is 30,000 MB. p = (s × m) / 1024 (in MB), where: s is the size of the error log file (units: KB, default is 9,900), and m is the number of error log files (default is 2).
Item Total number of paths Supported number 1 to 8,192 #1 For details on the maximum number of LUs that can be recognized by a CHA port, see the specifications of the storage system that you use. #2 If the reservation policy is PR_exclusive, and the Thunder 9500V series, Hitachi AMS2000/AMS/WMS/SMS series, or HUS100 series, is used, the number of supported paths to an LU is 1 to 32. For details on reservation policy, see About the Reservation Policy on page 3-87.
Installing HDLM on a server where HDLM has not yet been installed is called a new installation. Upgrade installation of HDLM Installing a new version of HDLM over an already installed, earlier version of HDLM without first removing the earlier version is called an upgrade installation. You can perform an upgrade installation only for HDLM version 5.9 or later. Migration of HDLM Removing HDLM version 5.8.1 or earlier, and then performing a new installation of HDLM 5.9 or later is called a migration.
• When HDLM is installed, all devices shown under Devices that HDLM can manage in Devices Managed by HDLM on page 2-3 are set to be targets for HDLM management. • When installing HDLM on a host where version 5.
• If you want to use HDLM in a client partition to which a virtual HBA is applied by using the virtual I/O server NPIV functionality, set the NPIV option to on. If the option is not set to on, HDLM might not be able to recognize a path that goes through the virtual HBA. To set the NPIV option, execute the dlmodmset utility. For details on this utility, see dlmodmset Utility for Setting the HDLM Execution Environment ODM on page 7-20.
Notes on Trace Files In HDLM 5.6 or later, trace files for versions of HDLM earlier than 5.6 are divided into integrated trace files and trace files. The logs for the HDLM command are output to integrated trace files. Trace information for an HDLM manager is output to trace files. The output destinations for the files are changed as follows: When you migrate from HDLM 04-00 or earlier Trace files before the migration: /opt/hitachi/HNTRLib/spool/ hntrn.
Notes on the Cluster • When you use HDLM in a cluster configuration, you must install the same version of HDLM on all the nodes that comprise the cluster. If different versions of HDLM are installed, the cluster system may not operate correctly.
Installing HDLM When you install HDLM, Hitachi Network Objectplaza Trace Library will also be installed. The file path of the integrated trace information file of Hitachi Network Objectplaza Trace Library is /var/opt/hitachi/HNTRLib2/spool/ hntr2n.log, where n is the number of the integrated trace information file. Available Installation Methods To install HDLM, use one of the following procedures: • Use installux.sh. By using installux.
In addition to installing HDLM on a typical host, you can install it in the following environments: • Boot disk • You can install HDLM on a virtual I/O server. A virtual I/O server is a system that enables multiple client logical partitions to share one resource. • PowerHA environments PowerHA is IBM’s HA cluster software that runs on AIX.
Only upgrade installations are supported. Table 3-8 Combination of Installation Methods that Are Available in an PowerHA Environment and 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 installux.
¢ ¢ Upgrading or Re-installing HDLM in a PowerHA 5.5 or PowerHA 6.1 Environment (in a Boot Disk Environment) on page 3-57 in Installing HDLM in a PowerHA 5.5 or PowerHA 6.1 Environment on page 3-57 Installing HDLM in a PowerHA 7.
Only new installations, upgrade installations, and re-installations are supported. 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-88 of Settings for Using PowerHA on page 3-87. 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-69. 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-53.
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.
hdisk8 Defined hdisk9 Defined hdisk10 Defined KAPL10531-I The status of all of the HDLM drivers was changed to "Defined". To avoid inheriting the existing hdisk configuration: # /usr/DynamicLinkManager/bin/dlmrmdev -A KAPL10528-I The volume group will be made inactive, and the file system that is using HDLM will be unmounted. Is this OK? [y/n]:y hdisk7 deleted hdisk8 deleted hdisk9 deleted hdisk10 deleted KAPL09012-I All HDLM drivers were removed.
When an existing hdisk is successfully deleted, the KAPL09012-I message is displayed. If the KAPL09012-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 re-execute the procedure of step 7. ¢ Inheriting the existing hdisk configuration When the existing hdisk configuration is successfully inherited, the KAPL10531-I message is displayed.
11. For an upgrade installation, execute the following command: ¢ When installing HDLM from the DVD-ROM # /directory-in-which-the-DVD-ROM-is-mounted/installux.sh or # installp -aXgd /directory-in-which-the-DVD-ROM-is-mounted/ HDLM_AIX all ¢ When installing HDLM from the directory to which the DVD-ROM was copied # /directory-copied-from-DVD-ROM/installux.
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. 13. Execute the following command to make sure that the package is installed. # lslpp -la DLManager.mpio.rte Make sure that the fileset item in the output listing contains DLManager.mpio.rte, and all the displayed statuses are COMMITTED.
Intermittent Error Monitor : off Dynamic I/O Path Control : off(10) HDLM Manager Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.x-xx yyyy/mm/dd hh:mm:ss 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.
When Installing HDLM in a Boot Disk Environment 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. Back up the HDLM settings. If an upgrade installation or re-installation fails, AIX automatically removes HDLM, and the HDLM settings are deleted. Perform this step so that a copy of the HDLM settings is available in this case.
HDLM management-target paths, and then re-execute the procedure of step 6. The hdisk of the boot disk cannot be deleted. ¢ Inheriting the existing hdisk configuration When the existing hdisk configuration is 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 re-execute the procedure in step 6.
# /directory-in-which-the-DVD-ROM-is-mounted/installux.sh or # installp -aXgd /directory-in-which-the-DVD-ROM-is-mounted/ HDLM_AIX all ¢ When installing HDLM from the directory to which the DVD-ROM was copied # /directory-copied-from-DVD-ROM/installux.sh 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 re-installation ends with an error, HDLM might be removed. In this case, proceed to step 13. 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. 12. Execute the following command to make sure that the package is installed. # lslpp -la DLManager.mpio.
After executing the lspv command, if there is no hdisk other than the one that constitutes rootvg, re-execute the procedure starting from step 14. 16. Execute the dlnkmgr command's view operation to check the status of each program: # /usr/DynamicLinkManager/bin/dlnkmgr view -sys HDLM Version : x.x.
Execute the following command on the virtual I/O server: When creating an hdisk as a virtual target device: $ mkvdev -vdev hdisk-name -vadapter virtual-SCSI-serveradapter-name When creating a logical device as a virtual target device: $ mkvdev -vdev logical-volume-name -vadapter virtual-SCSIserver-adapter-name 20. Execute the following command in the client logical partition to reconfigure the device: # cfgmgr 21.
You do not need to mount the DVD-ROM. If you install HDLM by using a directory to which the DVD-ROM is copied or if you use the nim command, you do not have to perform this step. 4. For an upgrade installation, execute the following command: ¢ ¢ ¢ When installing HDLM on an alternate disk from the DVD-ROM # alt_disk_copy -d hdisk-name hdisk-name ... -w DLManager.mpio.
# /usr/DynamicLinkManager/bin/dlnkmgr view -sys HDLM Version : x.x.x-xx Service Pack Version : Load Balance : on(rr) Support Cluster : Elog Level : 3 Elog File Size (KB) : 9900 Number Of Elog Files : 2 Trace Level : 0 Trace File Size(KB) : 1000 Number Of Trace Files : 4 Path Health Checking : on(30) Auto Failback : on(60) Intermittent Error Monitor : off Dynamic I/O Path Control : off(10) HDLM Manager Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.
¢ ¢ ¢ ¢ 2. If you prepared a license key for an upgrade installation of HDLM on a standby BOS to be newly created, go to step 2. If you prepared a license key file for an upgrade installation of HDLM on a standby BOS to be newly created, go to step 3. If you prepared a license key for an upgrade installation of HDLM on an already created standby BOS, go to step 4. If you prepared a license key file for an upgrade installation of HDLM on an already created standby BOS, go to step 5.
6. If you install HDLM as an installation bundle, create a bundle file containing the HDLM syntax. The following is an operation example of adding the HDLM syntax to a bundle file named /tmp/hdlm_bandle: # echo "I:DLManager.mpio.rte" > /tmp/hdlm_bandle 7. Insert the DVD-ROM, and then mount it. This step is not necessary when you install HDLM from a directory to which you have copied the contents of the DVD-ROM. 8. Execute the following commands to perform an upgrade installation of HDLM.
If there is even one BROKEN status displayed, remove HDLM and then perform a new installation, or delete the standby BOS and then re-create the standby BOS. 10. Execute the HDLM command's view operation to display the status of the programs. The following is an example of executing the command: # /usr/DynamicLinkManager/bin/dlnkmgr view -sys HDLM Version : x.x.
¢ ¢ 2. If you are using a virtual I/O server, see the virtual I/O server documentation for details about how to log in to AIX. If you are not using a virtual I/O server, proceed to step 10. Check the virtual SCSI disk recognition method being used. Execute the dlmodmset utility for setting the HDLM execution environment ODM in order to check the unique_id value: The following shows an example of executing this utility when HDLM 5.6.
$ rmdev -dev vtscsin 10. Insert the DVD-ROM. 11. 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. 12. Mount the DVD-ROM. # mount -r -v cdrfs /dev/cd0 /cdrom The /dev/cd0 part depends on the system. 13. Back up the HDLM settings. To check whether the HDLM settings information has been properly inherited after migration, save the HDLM settings information into separate files.
directory/odm-environment-settings-file-name -set /tmp/anydesired-directory/set-environment-settings-file-name For details about the dlmmigsts utility, see dlmmigsts Utility for Assisting HDLM Migration on page 7-18. 18. Execute the following command to reconfigure the device: # cfgmgr 19. Make sure that the HDLM settings information has been properly inherited. ¢ ¢ Make sure that the HDLM environment settings information has been properly inherited.
# umount /cdrom 26. Delete any mount directory you may have created in step 11. # rm -r /cdrom Installing HDLM in a PowerHA 5.5 or PowerHA 6.1 Environment This subsection explains how to install HDLM when you are running services in a PowerHA 5.5 or PowerHA 6.1 environment. Upgrading or Re-installing HDLM in a PowerHA 5.5 or PowerHA 6.1 Environment (in a Local Boot Disk Environment) Because HDLM version 5.8.1 or earlier cannot be upgraded to HDLM version 5.9 or later, migration is necessary.
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 2 through 21 in When Installing HDLM in a Boot Disk Environment on page 3-43 of Performing an Upgrade Installation or Re-installation of HDLM on page 3-36 on the standby host. 4. Start PowerHA on the standby host. 5. Stop PowerHA on the active host. Specify takeover as the shutdown mode. 6.
WARNING: Custom disk method: ghostdisks's file: /usr/DynamicLinkManager/cluster/dlm_hacmp_gdisk_check does not exist or is not executable on node: xxx# # Name of the node being used. 6. Stop PowerHA on the active host. Specify takeover as the shutdown mode. 7. Migrate HDLM on the active 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-53 on the active host. 8. Start PowerHA on the active host.
1. Log in to the standby host as the root user. 2. Execute the following command on the standby host to stop PowerHA. # smitty cl_stop 3. Execute the following command on the standby host. When the OS used in a PowerHA 7.1 environment is AIX V6.1 TL06 or AIX V7.1 with no TL: # clcmd stopsrc -s clconfd # clusterconf -fu When the OS used in a PowerHA 7.1 environment is AIX V6.1 TL07 or later or AIX V7.1 TL01 or later: # clctrl -stop -m node-name 4.
# 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. Execute the following command on the active host. When the OS used in a PowerHA 7.1 environment is AIX V6.1 TL06 or AIX V7.1 with no TL: # clcmd stopsrc -s clconfd # clusterconf -fu When the OS used in a PowerHA 7.1 environment is AIX V6.1 TL07 or later or AIX V7.
When the OS used in a PowerHA 7.1 environment is AIX V6.1 TL06 or AIX V7.1 with no TL: # clusterconf -r hdiskxx When the OS used in a PowerHA 7.1 environment is AIX V6.1 TL07 or later or AIX V7.1 TL01 or later: # clctrl -start -m node-name 11. Execute the following command on the active host to start PowerHA. # smitty cl_start Performing an Unattended Installation of HDLM This subsection explains how to install HDLM using the installhdlm utility.
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 you are using a copy of the installhdlm utility that you have placed in a separate directory to install HDLM, make sure you copy the necessary files from the /cdrom/HDLM_AIX/hdlmtool/instutil directory.
Create the /var/DLM directory, and then, in this directory, create the license key file (dlm.lic_key). The following shows an example when the license key is 123456789ABCDEF: # mkdir /var/DLM # echo "123456789ABCDEF" > /var/DLM/dlm.lic_key ¢ When the license key file has been provided Store the license key file directly under the /var/tmp/ directory by using the hdlm_license name. /var/tmp/hdlm_license The license key file or license key is not deleted after the installation. 8.
# 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. Perform the procedure appropriate for the installation type. If you are performing a new installation, perform steps 14 to the end of the procedure described in When Installing HDLM in a Local Boot Disk Environment on page 3-24 of Performing a New Installation of HDLM on page 3-24.
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.
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. Perform this step so that a copy of the HDLM settings is available in this case.
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.conf For details about how to edit the installation information settings file, which is used by the installhdlm utility, see Items To Be Defined in an installation-information Settings File on page 7-27.
the settings have been updated as specified in the installation information settings file. Note that, if the upgrade installation or re-installation ends in an error, HDLM may no longer be installed at all. In this case, proceed to step 12. If unattended installation ends normally, proceed to step 13. 13. If HDLM was not upgraded or re-installed properly, perform a new installation of HDLM. ¢ ¢ When AIX 5L V5.
The following describes how to check path information by using the dlnkmgr command's view operation. For details about the view operation, see view (Displays Information) on page 6-32. Specify the -path parameter and check the output information: Execute the following command: # /usr/DynamicLinkManager/bin/dlnkmgr view -path > redirectdestination-file-1 Open redirect-destination-file-1 and check the following: ¢ ¢ ¢ Make sure that an LU accessed by a path exists. A path can be identified with PathName.
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. Check the current settings by executing the following command: # /usr/DynamicLinkManager/bin/dlnkmgr view -sys -sfunc HDLM Version : x.x.
Function Default value Recommended value 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. Intermittent Error Monitor off on Dynamic I/O path control# off off 10-minute check interval The recommended checking interval depends on the operating environment.
• rr for the Round Robin algorithm • exrr for the Extended Round Robin algorithm • lio for the Least I/Os algorithm • exlio for the Extended Least I/Os algorithm • lbk for the Least Blocks. algorithm • exlbk for the Extended Least Blocks algorithm The type of algorithm specified by the -lbtype parameter remains stored in the system, even if, you disable the load balancing function by specifying -lb off.
# /usr/DynamicLinkManager/bin/dlnkmgr set -afb on -intvl 10 To enable the automatic failback function, set it to on. The checking interval can be specified by the -intvl parameter. The previously specified value will be applied when a checking interval is not specified.
The dynamic I/O path control function can be set for each storage system or LU.
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. Table 3-14 Values for the Trace Level Setting Value Description 0 No trace is output. 1 Only error information is output. 2 Program operation summaries are output. 3 Program operation details are output. 4 All information is output.
# /usr/DynamicLinkManager/bin/dlnkmgr set -elfs 1000 Specify the size of the error log file in kilobytes. Setting the Number of Error Log Files The number of the error log files (the HDLM manager log (dlmmgrn.log (n indicates a file number from 1 to 16))) can be set. You can specify a value from 2 to 16 for the number of error log files (log files for the HDLM manager).
KAPL01097-W message will be displayed to confirm the execution, and the trace file will be temporarily deleted. By specifying both the trace file size and the number of trace files, you can collect up to 1024000KB of trace data. The following is an example of setting up the number of trace files by using a command: # /usr/DynamicLinkManager/bin/dlnkmgr set -systfn 10 Specify the number of trace files by using numbers. Setting Up Audit Log Data Collection You can set whether to collect audit log data.
This example shows how to enable the collection of audit log data: # /usr/DynamicLinkManager/bin/dlnkmgr set -audlog on -audlv 6 category all Specify on if you want to collect audit log data, and off if you do not want to collect audit log data. If you specify on, you can use the -audlv parameter to specify the collection level for audit log data and the -category parameter to specify the audit log categories. If you want to set the audit log facility, see Setting the Audit Log Facility on page 3-79.
When you change some settings, you can display information about all of HDLM function settings. The following is an example of executing the command: # /usr/DynamicLinkManager/bin/dlnkmgr view -sys -sfunc HDLM Version : x.x.
Table 3-18 Default and Recommended Values for the Integrated Trace File Settings Setting Recommended value Default value Integrated trace file size 256 (KB) 4096 (KB) Number of integrated trace files 4 8 Buffer size per monitoring interval Monitoring cycle 10 (seconds) 5 (seconds) Buffer size per monitoring interval 64 (KB) 256 (KB) Number of messages to be output per monitoring interval Monitoring cycle 0 (seconds) 0 (seconds) Number of messages to be output 0 0 If Hitachi Network Ob
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: 3-82 1. In the Hitachi Network Objectplaza Trace Library setup menu, type 1 and then press the Enter key. A screen to set the size of the integrated trace file will appear.
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. The current value is displayed in Current Number (KB). 2. Enter the desired number in New Number (KB). You can specify a value from 1 to 16. The default is 4.
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-82. 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. You will be returned to the Hitachi Network Objectplaza Trace Library setup menu. 3. Press the Enter key. The new setting is applied and the Hitachi Network Objectplaza Trace Library setup menu appears again. 4.
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. To leave the monitoring interval as is, leave New Span (sec) blank, type ! and press the Enter key. You will be returned to the Hitachi Network Objectplaza Trace Library setup menu.
The new setting is applied and the Hitachi Network Objectplaza Trace Library setup menu appears again. Finishing the Hitachi Network Objectplaza Trace Library Settings This section explains how to close the Hitachi Network Objectplaza Trace Library setup menu when you are finished. 1. In the Hitachi Network Objectplaza Trace Library setup menu, type e and press the Enter key. You will be asked to if you want to save the new settings. 2. To save the new settings, click Yes, otherwise, click No.
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. Table 3-19 Reservation Policy Settings Setting no_reserve PR_exclusive Description Ignores a reservation request and does not reserve an LU.
Storage System Settings Setting Up a Thunder 9500V Series Device To use a Thunder 9500V series device as the storage system, perform the setup shown in the table below. For details about setting up a Thunder 9500V series device, see the manual for Thunder 9500V series.
¢ ¢ When a XP series is used: disk/fcp/HP When a 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, Hitachi AMS2000/AMS/WMS/SMS series, or HUS100 series is used: disk/fcp/Hitachi Method to identify ghost disks SCSI3 Method to determine if a reserve is held /usr/DynamicLinkManager/cluster/ dlm_hacmp_gdisk_reserve_check Method to break a reserv
# 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.
Note that, depending on the settings of Oracle RAC, Oracle RAC might determine that a node error has occurred before the failover processing performed by HDLM is completed, and then re-configure the cluster. Therefore, when HDLM manages the paths that are connected to an Oracle RAC voting disk, change the following settings according to your version of Oracle RAC: When using Oracle RAC 10g 10.1.0.3.0 or later or Oracle RAC 11g: Change the value of MISSCOUNT to match the type of storage system.
Storage system type • Hitachi USP series • Lightning 9900V series • Universal Storage Platform V/VM series • Virtual Storage Platform series Number of paths connecte d to the voting disk Formula for obtaining the value of DISKTIMEOUT 3 or less You do not need to change the value of DISKTIMEOUT.
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. # lsattr -El hdisk-name -a reserve_policy reserve_policy no_reserve N/A TRUE Settings for Using VCS To use VCS, install HDLM on all of the hosts that comprise the cluster, and then configure the HDLM devices. Also, carry out the following procedure before starting VCS: 1.
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, Hitachi AMS2000/AMS/WMS/SMS series, or HUS100 series was used, delete the following line: disk/fcp/Hitachi fscsi disk/fcp 17. If GPFS or GPFS + RVSD was used, execute the following utility to set the LUN RESET option to off: # /usr/DynamicLinkManager/bin/dlmodmset -r off 18.
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.
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/HNTRLib2/etc/hntr2getname If you are unable to complete removal even though no programs other than HDLM are using HNTRLib2, contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. Note If the log output directory set in HNTRLib2 was not the default directory, the log files will not be deleted during 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. Canceling Cluster Software (PowerHA) Settings When PowerHA is used, delete the custom disk method. The following deletion procedure assumes that PowerHA 6.1 is used. The actual screen transitions for the SMIT menu might be different depending on the PowerHA version. Therefore, please also refer to the PowerHA documentation.
3-104 Creating an HDLM Environment Hitachi Dynamic Link Manager User Guide for AIX®
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 B Differences Between HDLM Version 5.9 or Later and 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-22. 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-32. 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 • 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 Environment) on page 6-16.
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.
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 ...
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. # /usr/DynamicLinkManager/bin/dlmrmdev -e -A For details on the dlmrmdev utility, see dlmrmdev Utility for Deleting HDLM Drivers on page 7-25.
# /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.
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. # lsattr -El hdisk-name | grep reserve_policy reserve_policy no_reserve Reserve Policy TRUE 15. Activate the volume group used by HDLM.
# 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. Execute the following HDLM command to check the OS management path ID of the path that is to be deleted and to determine the devices (hdisk name) connected to the path. # /usr/DynamicLinkManager/bin/dlnkmgr view -drv PathID HDevName OSPathID LDEV 000000 hdisk5 00000 USP.0014050.
# rmpath -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. Delete a path of a volume group other than rootvg by performing the procedure described in Deleting a Path (of a Volume Group Other than rootvg) on page 4-22: 2.
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. # /usr/DynamicLinkManager/bin/dlmodmset -o The following are execution examples: Lun Reset Online(E) IO Block NPIV Option : off : on : off Check the NPIV Option line. 3.
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.
# 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. Execute the following command to check the path information: # /usr/DynamicLinkManager/bin/dlnkmgr view -path For details about the path information, see view (Displays Information) on page 6-32.
Specify the device name of the PCI slot (fcs device) where each HBA has been replaced. n indicates the instance number of the fcs device. f. Execute the following command to check path information: # /usr/DynamicLinkManager/bin/dlnkmgr view -path For details on path information, see view (Displays Information) on page 6-32. • g.
Replacing a Fiber Cable If there are multiple active paths for an LU, you can replace a desired cable while running your applications by placing offline only the path that goes through the cable to be replaced and using other paths to continue access. Note The following procedure is only for replacing a fiber cable. To replace a fiber cable: 1. Execute the dlmodmset utility for setting the HDLM execution environment ODM to check the NPIV option setting.
Depending on the NPIV option setting for the dlmodmset utility checked in step 1, execute one of the following commands: ¢ If the NPIV option is set to off: Specify the HBA adapter number and bus number, and then execute the command shown below. The following example shows how to place the path in Offline (C) status when the path goes through an HBA whose HBA adapter number is 08 and whose bus number is 11: # /usr/DynamicLinkManager/bin/dlnkmgr online -hba 08.
# /usr/DynamicLinkManager/bin/dlmodmset -o The following are execution examples: Lun Reset Online(E) IO Block NPIV Option : off : on : off Check the NPIV Option line. 3. Place in Offline (C) status the path that goes through the Fibre Channel switch to be replaced.
fcsn indicates the name of the parent device that was acquired in step 5; n indicates the instance number of the fcs device. 9. Execute the following command to check the path information: # /usr/DynamicLinkManager/bin/dlnkmgr view -path For details about path information, see view (Displays Information) on page 6-32.
4-32 HDLM Operation Hitachi Dynamic Link Manager User Guide for AIX®
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.
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-4.
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 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-32.
5-8 Troubleshooting Hitachi Dynamic Link Manager User Guide for AIX®
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.
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.
# /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. Format /usr/DynamicLinkManager/bin/dlnkmgr help [operation] [operation] ...
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.
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. There must always be at least one online path accessing each LU. Placing too many paths offline might prevent paths from being able to switch if an error occurs. Before placing a path offline, use the view operation to check how many online paths remain.
Use this parameter to place offline, at one time, all the paths that pass through a specific HBA port. The command will place offline all the paths connected to the HBA port that has the specified HBA-adapternumber.bus-number or adapter-type.adapter-number. Specify the HBA adapter number and bus number, or adapter type and adapter number, of the target HBA port: the numbers are found in the PathName field displayed using the view operation. Enter a period between these two parameter values.
path(s) were not. Operation name = offline # -cha -pathid AutoPATH_ID Use this parameter to place offline, at one time, all the paths that pass through a specific CHA port. The command will place offline all the paths that pass through the CHA port to which the path with the specified AutoPATH_ID is connected. 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-32.
The following example shows how to place offline all paths connected to the CHA port whose CHA-port-ID is 00001. # /usr/DynamicLinkManager/bin/dlnkmgr offline -chaid 00001 KAPL01102-I All the paths which pass the specified CHA 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.
hdisk0 -ospathid 1 KAPL01052-I The currently selected paths will be changed to the Offline(C) status. Is this OK? [y/n]:y KAPL01053-I If you are sure that there would be no problem when the path is placed in the Offline(C) status, enter y. Otherwise, enter n. [y/n]:y KAPL01061-I 1 path(s) were successfully placed Offline(C); 0 path(s) were not. Operation name = offline # -s Executes the command without displaying the message asking for confirmation of command execution from the user.
Reference Using the view operation together with standard UNIX commands enables you to filter the path information listed for a specific HBA port or CHA port. For details about the view operation, see view (Displays Information) on page 6-32. We recommend that you use the following command and verify the information on the target paths before you execute the offline operation to place offline all the paths connected to a specific HBA port or CHA port.
[-s] To Display the Format of the Online Operation /usr/DynamicLinkManager/bin/dlnkmgr online -help Parameters To Place Paths Online -path Indicates that the target of the operation is a path managed by HDLM. This parameter is optional because online is always used for paths, so it is assumed. Specify the paths to be placed online by using the -hba, -hbaid, -cha, chaid, -pathid, or -hdev parameter. If you do not specify any of these parameters, the command will place all the offline paths online.
path(s) were not. Operation name = online # -hbaid HBA-port-ID Use this parameter to place online, at one time, all paths that pass through a specific HBA port. The command will place online all paths connected to the HBA port that has the specified HBA-port-ID.
KAPL01057-I All the paths which pass the specified CHA port will be changed to the Online status. Is this OK? [y/n]:y KAPL01061-I 2 path(s) were successfully placed Online; 0 path(s) were not. Operation name = online # -chaid CHA-port-ID Use this parameter to place online, at one time, all paths that pass through a specific CHA port. The command will place online all paths connected to the CHA port that has the specified CHA-port-ID.
To display HDevName and OSPathID, execute the view operation as follows: # /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-52 in Parameters on page 6-34. Only one set of values can be specified for the -hdev parameter. This parameter is not case sensitive.
{ -hba HBAPortNumber.BusNumber | -hbaid HBA_ID } [-s] dlnkmgr online [-path] { -cha -pathid AutoPATH_ID | chaid CHA_ID } [-s] dlnkmgr online [-path] [-pathid AutoPATH_ID] [-s] dlnkmgr online [-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 Set Up the HDLM Operating Environment /usr/DynamicLinkManager/bin/dlnkmgr set {-lb {on [-lbtype {rr|exrr|lio|exlio|lbk|exlbk}]|off} |-ellv error-log-collection-level |-elfs error-log-file-size |-elfn number-of-error-log-files |-systflv trace-level |-systfs trace-file-size |-systfn number-of-trace-files |-pchk {on [-intvl checking-interval]|off} |-afb {on [-intvl checking-interval]|off} |-iem { on [-intvl error-monitoring-interval] [-iemnum number-of-times-error-is-to-occur] | off } |-lic |-audlog
Item name Default value Recommended value 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. 0: Do not output any trace. Trace file size 1000 (KB) 1000 (KB) Number of trace files 4 4 Path health checking on (Interval is 30 minutes.
Enables or disables load balancing. on: Enabled off: Disabled Load balancing distributes load among paths and prevents the performance of the entire system from deteriorating. As such, we recommend that you set this parameter to on. -lbtype {rr|exrr|lio|exlio|lbk|exlbk} Specify the algorithm to be used for load balancing.
# /usr/DynamicLinkManager/bin/dlnkmgr set -ellv 1 KAPL01049-I Would you like to execute the operation? Operation name = set [y/n]: y KAPL01001-I The HDLM command completed normally. Operation name = set, completion time = yyyy/mm/dd hh:mm:ss # -elfs error-log-file-size Specify a value from 100 to 2000000 (KB) for the size of the error log files (dlmmgrn.log (n indicates a file number from 1 to 16)). The specified value is used for HDLM manager logs.
When combined with the specification for the number of trace files, the maximum size of the trace files that can be collected is 1024000KB. If the value is changed to something smaller than the value that is currently set, the execution confirmation message KAPL01097-W will be displayed and the trace file will be deleted temporarily. The trace files for which a file size can be set are hdlmtrn.log (n indicates a file number from 1 to 64). The trace files are fixed in length.
health check) has already elapsed, the path health check will start over. The path health check interval setting remains stored in the system even if you disable the function by changing the path health checking to off. Therefore, when you re-enable path health checking and do not change the interval, the path health interval stored in the system is used. -afb {on [-intvl checking-interval]|off} Enables or disables automatic failback.
If intermittent error monitoring is on and the number of times that the error is to occur is set to a value of 2 or more, the following condition must be satisfied: error-monitoring-interval >= checking-interval-for-automaticfailback × number-of-times-error-is-to-occur-duringintermittent-error-monitoring If this condition is not satisfied, the KAPL01080-W message will be output and an error will occur.
When the intermittent error monitoring interval or the number of times that the error is to occur has been specified before: The values specified from the last time are used.
value will take effect after the next automatic failback successfully completes. When intermittent error monitoring is not being performed, the number of errors that determine that an intermittent error has occurred is not counted and this value is not changed. The number of times that the error is to occur is stored in the system, even when -iem off is specified and intermittent error monitoring is disabled.
Setting AFB IEM Available operation Change the IEM settings. Set IEM to off. off off on#2 off Result of operation • While a path is being monitored, the value of the error count and the elapsed monitoring time are reset to 0, and then intermittent error monitoring will restart.#1 • When a path is not being monitored, the IEM settings will take effect again when the path is recovered from the error status by performing an automatic failback. • IEM is disabled.
KAPL01049-I Would you like to execute the operation? Operation name = set [y/n]: y KAPL01001-I The HDLM command completed normally. Operation name = set, completion time = yyyy/mm/dd hh:mm:ss # -lic Specify this option for when a license is updated. The HDLM license is provided via a license key or license key file. A license key file is a file that stores the HDLM license key.
KAPL01049-I Would you like to execute the operation? Operation name = set [y/n]: y KAPL01071-I A permanent license was installed. # Example 2 The following example shows how to update the license key when the license key file does not exist: # /usr/DynamicLinkManager/bin/dlnkmgr set -lic KAPL01049-I Would you like to execute the operation? Operation name = set [y/n]: y KAPL01083-I There is no license key file.
Table 6-8 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 collected. -audfac facility-value Specifies the audit log facility. The table below lists the values used for this setting.
You an specify a decimal (base 10) value from 0 to 999999. The default is 100. If you specify 0, the same path is used as long as the sequential I/O operations continue. -dpc {on|off} [-pathid path-ID -lu | -pathid path-ID -storage] Enables or disables the dynamic I/O path control function for each storage system or LU. The default value is "off". on: Enabled off: Disabled -pathid path-ID -lu Sets the dynamic I/O path control function to enabled or disabled for each LU.
| | | | | | | | | | | | -elfn Number-Of-ElogFiles -systflv TraceLevel -systfs TraceFileSize -systfn Number-Of-TraceFiles -pchk on [ -intvl Interval-Time ] -pchk off -afb on [ -intvl Interval-Time ] -afb off -iem on [ -intvl Error-Monitor-Interval ] [ -iemnum Number-Of-Times ] -iem off -lic -audlog on [ -audlv AudlogLevel ] [ -category Category-Value ] -audlog off -audfac { Facility-Name | Facility-Number } -lbpathusetimes Number-Of-PathUseTimes -expathusetimes Number-Of-ExPathUseTimes -dpc { on | off } [-p
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 # { 0 - 999999 }(Times) (Default { 0 - 999999 }(Times) (Default { 000000 - 999999 }(Decimal) { 1 - 1440 }(Minute) (Default completed normally.
To display a summary of path information /usr/DynamicLinkManager/bin/dlnkmgr view -path -c [-stname] [-srt {lu|cp}] [-t] To Display LU Information To display LU information /usr/DynamicLinkManager/bin/dlnkmgr view -lu [-hdev host-device-name | -pathid AutoPATH_ID] [-t] To display LU information (by adding items to be displayed) /usr/DynamicLinkManager/bin/dlnkmgr view -lu -item [ [slpr] [pn] [cp] [clpr] [type] [ic] [ie] [dnu] [iep] [vg] [dpc] | all ] [-hdev host-device-name | -pathid AutoPATH_ID] [-t] To
Parameters This section describes the parameters for the view operation, in the following order: To Display Program Information on page 6-34 To Display Path Information on page 6-41 To Display LU Information on page 6-52 To Display HBA Port Information on page 6-62 To Display CHA Port Information on page 6-63 To Display the Correspondences Between hdisks, OS Management Path IDs, and LDEVs on page 6-64 To Display the Format of the View Operation on page 6-65 To Display Program Information -sys [-sfunc|-msrv
Parameter and program informatio n to be displayed Item Description off: Disabled • Algorithm When the setting status of load balancing is on, one of the following types of algorithms is used for load balancing is displayed in the parentheses following on.
Parameter and program informatio n to be displayed Item Description Trace File Size(KB) Trace file size in kilobytes Number Of Trace Files Number of trace files. Path Health Checking • Settings for path health checking: on: Enabled off: Disabled • Checking interval: When the setting of the path health checking is on, the checking interval of path health checking is displayed within the parentheses following on. The time is in minutes.
Parameter and program informatio n to be displayed Item Description • Checking interval The parentheses following the setting status shows the checking interval for reviewing information about the switching of controllers performed by the storage system. "Minute" is used as the unit. If different settings have been specified for each storage system or LU, * is added after the parentheses in which the checking interval is displayed.
Parameter and program informatio n to be displayed Item Description view -sys -lic operation is executed, (ndays after) appears if there are n days left until the license period expires.
Parameter and program informatio n to be displayed expathuse times The number of times the same path can be used for extended load balancing Item Times Same ExPath Was Used Description The number of times the same path can be used for sequential I/O operations when the extended Round Robin (exrr), Least I/Os (exlio), or Least Blocks (exlbk) algorithm is used for load balancing.
# /usr/DynamicLinkManager/bin/dlnkmgr view -sys -msrv HDLM Manager Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss # Example 3 The following example shows how to display information about the HDLM alert driver. # /usr/DynamicLinkManager/bin/dlnkmgr view -sys -adrv HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.x-xx yyyy/mm/dd hh:mm:ss 4000 KAPL01001-I The HDLM command completed normally.
# /usr/DynamicLinkManager/bin/dlnkmgr view -sys -lbpathusetimes Times Same Path Was Used : 20 KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss # Example 8 The following example shows how to display the number of times the same path can be used for extended load balancing: # /usr/DynamicLinkManager/bin/dlnkmgr view -sys -expathusetimes Times Same ExPath Was Used : 100 KAPL01001-I The HDLM command completed normally.
Use this parameter to display the model ID of the storage system in the product ID element of the DskName field. When this parameter is omitted, the command displays the product ID or emulation type of the storage system instead. For details about the information displayed for product IDs, see Table 6-14 Product ID Displayed by the View -Path Operation on page 6-51. -iem Use this parameter to add IEP to path information and display information about intermittent errors.
Parameters to display path information by selecting a display item: -path -item When you specify the -path parameter together with the -item parameter, the command only displays the items specified by the value of the -item parameter. If you specify no value for the -item parameter, only the PathID and the Status fields are displayed.
When you specify this parameter, HDevName is displayed by default. Therefore, it is not necessary to specify hd for the -item parameter. -stname Use this parameter to display the model ID of the storage system in the product ID element of the DskName field. When this parameter is omitted, the command displays the product ID or emulation type of the storage system instead.
To display a summary of path information -path -c If the -c parameter is specified at the same time as the -path parameter, only PathID, DskName, iLU, CP, Status, and Type are displayed for the path information. The displayed contents are also shortened, so that each path information item is displayed on a single line. The items that are displayed are PathID, DskName, iLU, CP, Status, and Type. For details on what is displayed for each item, see Table 6-12 Displayed Path Information on page 6-47.
For details about the information about product IDs, see Table 6-14 Product ID Displayed by the View -Path Operation on page 6-51. -srt {lu|cp} Use this parameter to sort the path information in ascending order, according to the specified sorting key. The sorting keys are as follows: the first sorting key is the name of the storage system (DskName), the second sorting key is the value specified by the -srt parameter, and the third sorting key is AutoPATH_ID.
Table 6-12 Displayed Path Information Displayed Item No summary displayed Description Summary displayed Paths Total number of displayed paths, indicated by a decimal (i.e., base 10) number. OnlinePaths Number of online paths from within the displayed paths, indicated by a decimal number. When the value of Paths equals the value of OnlinePaths, then all the paths are online. If the value of OnlinePaths is less than that of Paths, some paths are offline.
Displayed Item No summary displayed DskName#1 Description Summary displayed DskName Storage system name, which identifies the storage system that is accessed by a path. A storage system name consists of the following three elements, separated by periods: • Vendor ID: The name of the storage system vendor (for example, HITACHI). • Product ID: Indicates the storage system product ID, emulation type, or model name (for example, OPEN-3).
Displayed Item No summary displayed Description Summary displayed • Offline(C): Offline status caused by a command operation • Offline(E): Offline due to an error • Online(E): Failure has occurred (If none of the paths accessing one LU have an Online status, one of those paths is changed to the Online(E) status.) Paths that are Offline(E) or Online(E) require corrective action. The appropriate action can be determined by referring to What To Do for a Path Error on page 5-3.
Displayed Item No summary displayed Description Summary displayed One of the following values is displayed for each path: • Indicates that intermittent error monitoring is disabled or the monitoring time for an intermittent error is out of range. • A value of at least 0 Indicates the number of errors that occurred during intermittent error monitoring. • * Indicates that an intermittent error occurred (automatic failbacks do not check the path).
Element Corresponding information AIX representation 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 hdisk-name command #1 This element is applied when the NPIV option is set to off for the dlmodmset utility for setting the HDLM execution environment ODM.
Product ID Model names of storage systems With the -stname parameter (Displays the following for the model name) Without the -stname parameter Hitachi Virtual Storage Platform VSP P9500 P9500 XP128 XP128 XP1024 XP1024 XP10000 XP10000 XP12000 XP12000 XP20000 XP20000 XP24000 XP24000 # When a summary is displayed by specifying the -path -c parameter and there are 11 or more characters in the summary string, any characters after the 9th character are not displayed,and ellipsis (...
Filters the information only for the paths accessing the specified host device. Specify hdisk name for host-device-name. The host-device-name string is case-sensitive. -pathid AutoPATH_ID Use this parameter to display only the information about the LU that is connected to the path with that specified AutoPATH_ID. -t Omits the title for each information item.
The table below lists the correspondence between the display items that can be added by using the -item parameter and the parameter values that can be specified after the -item parameter.
Example 2 When using Hitachi AMS2000 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 User Guide for AIX® 6-55
# 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-17 Displayed LU Information on page 6-57.
Table 6-16 Items That Can Be Added by Using the -lu -c -item Parameter and Sub-parameters Item that can be added Sub-parameter SLPR slpr VG vg All items all The sub-parameter is: -t Omits the title for each information item. Example The following example describes how to add and display a summary of SLPR and VG. Displayed LU information Table 6-17 Displayed LU Information on page 6-57 describes the displayed LU information.
Displayed item No summary displayed Description Summary displayed Total number of LUs managed by HDLM among the LUs in the storage system LUs Dynamic I/O Path Control - The setting information about the dynamic I/O path control function is displayed for each storage system. on: The dynamic I/O path control function is enabled. off: The dynamic I/O path control function is disabled. -: The dynamic I/O path control function is not supported.
Displayed item No summary displayed Description Summary displayed displayed if the storage logical partition functionality for the storage system for the target LU is not supported. HDevName#1 - Host device name. Hdisk name is displayed. DPC - The setting information about the dynamic I/O path control function is displayed for each LU. on: The dynamic I/O path control function is enabled. off: The dynamic I/O path control function is disabled.
Displayed item No summary displayed Status Description Summary displayed - • CHA ports in the storage system that do not support cache logical partition functionality • Paths connected to the Snapshot image of the Copy-on-write Snapshot of the Hitachi AMS2000/AMS/WMS/SMS series Status of the path • Online: Online • Offline(C): Offline status caused by a command operation • Offline(E): Offline due to an error • Online(E): Failure has occurred (If none of the paths accessing one LU have an Onl
Displayed item No summary displayed Description Summary displayed For details about the clear operation, see clear (Returns the Path Statistics to the Initial Value) on page 6-3. DNum#1 - Dev number, indicated by a decimal number. This item pertains to a logical volume number. 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.
- The user selected the item to be displayed by using the -lu -c -item parameter. - all was specified. - No value was specified for the parameter. #3 This storage system applies when the dynamic I/O path control function is disabled. To Display HBA Port Information -hba Use this parameter to display information about the paths to each HBA port. HDLM displays the unique HBA port ID assigned to each HBA port. This HBA port ID can also be used in Offline and Online operations.
KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss # The subsequent sub-parameters are: -srt pb Sorts the HBA port information by the HBA adapter number (Port) and bus numbers (Bus) (or adapter type and adapter number). -portwwn Displays port WWN information for HBAs connected to the storage system using a 16-digit hexadecimal number. -t Omits the title for each information item.
Item Description should check the offline paths and take appropriate action for any path that has an error status. Example The subsequent sub-parameters are: -srt cp Sorts the CHA port information by the storage system model IDs (Product), storage system serial numbers (S/N), and CHA port numbers (ChaPort). -t Does not display the title for each information item.
Item Description AutoPATH_ID is assigned when you execute the cfgmgr command. HDevName Host device name. Hdisk name is displayed. OSPathID OS management path ID. LDEV The model ID, serial number, and iLU number for the storage system, separated by periods. The information about an LDEV can physically identify an LU.
dlnkmgr view -lu -item [ [slpr] [vg] [pn] [cp] [clpr] [type] [ic] [ie] [dnu] [iep] [dpc] | all ] [ -hdev HostDeviceName | -pathid AutoPATH_ID ] [-t] dlnkmgr view -lu -c [-t] dlnkmgr view -lu -c -item [ [slpr] [vg] | all ] [-t] dlnkmgr view -drv [-t] dlnkmgr view -hba [-srt pb] [-portwwn] [-t] dlnkmgr view -cha [-srt cp] [-t] KAPL01001-I The HDLM command completed normally.
7 Utility Reference This chapter explains the utilities used by HDLM.
Overview of the Utilities HDLM provides the following utilities: • The DLMgetras utility for collecting HDLM error information When an error occurs, this utility collects the files that contain 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-4. • 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-22. • The dlmpreremove utility executed before removing HDLM This utility excludes the hdisk recognized as a boot disk from being an HDLM management target. Execute this utility before removing HDLM. For details about the dlmpreremove utility, see dlmpreremove Utility for Executed Before Removing HDLM on page 7-24.
Operation (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 8/2048 42 seconds 16/4096 43 seconds 4/1024 32 seconds 8/2048 38 seconds 16/4096 1 minutes 37 seconds 4/1024 53 seconds 8/2048 1 minutes 14 seconds 16/4096 1 minutes 51 seconds 4/1024 1 minutes 15 seconds 8/2048 1 minutes 27 secon
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. This file is output only when using the Hitachi Command Suite products that is the target for collecting error information. • getras.tar.Z This file contains compressed HDLM information and system information. For details about the information that is stored in the system crash dump file and getras.tar.
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. If you use a relative path to specify a directory or file, that directory or file will be searched for only within the directory in which the DLMgetras utility was executed, and the files found will be collected.
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. • If you create an archive for the system crash dump collected by the DLMgetras utility, execute the following: # cd directory-to-which-collected-information-is-output # tar cvfh archive-file-name .
Output directory#1 Files dlminquiry[1-2].lo g Explanation 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/ DynamicLinkManager/ log/mmap hdlmtr.mm Trace management file dlmutil.
Output directory#1 Files Explanation dlmwebagent.proper ties Hitachi Command Suite Common Agent Component settings file dlmmgr_DPC.xml DPC option setting file filesystems Mount information of the file system inittab inittab file syslog.conf File for defining the directory for the output destination of syslog error-log-file error-log-file Error log file obtained by /usr/ lib/errdemon -1 syslog-output-directoryname syslog-name syslog files and backup files defined in /etc/syslog.
Output directory#1 7-10 Files Explanation 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.txt HDLM LU information (including the number of times an intermittent error occurred) dlmmgr-path.txt HDLM path information dlmmgr-pathiem.
Output directory#1 Files Explanation 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.txt Information of Object Database Manager PdPathAt.txt Information of Object Database Manager PdDv.txt Information of Object Database Manager ps-ef.txt Information on the executing process ulimit-a.
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. Note that the number 2 following the integrated trace file prefix does not represent a file number. dlmchpdattr Utility for Changing HDLM Default Settings This utility changes the default value for the hdisk attribute.
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 ("). The following table lists the attribute names and values that can be specified.
Prevents the confirmation message from being displayed when the utility is executed. -o Displays the current value set for the reservation policy. -h Displays the format of the dlmchpdattr utility. Notes • Before you execute the dlmchpdattr utility, stop all application processes that access HDLM-managed devices. • Before you execute the dlmchpdattr utility, make sure that no path errors are occurring. If there are any errors, the dlmchpdattr utility might end with an error.
dlmgetrasinst Utility for Collecting HDLM Installation Error Information This utility collects information that is needed to analyze errors that have occurred for some reason during installation of HDLM. The collected information is archived in a file and saved to the directory that you specified. The following files are output: • getrasinst.tar.Z This file contains compressed system information. For details about the information that is stored in the system crash dump file and getrasinst.tar.
List of Collected Error Information The following table lists and describes the information collected by the dlmgetrasinst utility. Table 7-4 Information Stored in the getrasinst.tar.Z File Output directory# 7-16 Files Explanation getrasinst.log Directly under the directory to which collected information is output dlmgetrasinst utility log file etc filesystems Mount information of the file system inittab inittab file syslog.
Output directory# 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 dlmls-la.txt HDLM directory information file env.txt Environment variable file errpt-a.txt Error log edit file genkex.txt Information of loaded drivers histfile_XXXXX File specified in the HISTFILE environment variable lscfg.txt Firmware version of HBA etc lsdev-C.txt Kernel parameter value lsdev-proc.
Output directory# Files Explanation descriptors) that are available to processes uname-a.txt Information on the AIX version rootvginfo.txt rootvg information # An output directory is created in the specified directory when you open the getrasinst.tar.Z file dlminstcomp Utility for HDLM Component Installation This utility complements HDLM installation.
| -h } Parameters -b Saves the settings files by using the names specified in the -odm and -set parameters. Notes on specifying the -b parameter • Do not save odm-environment-settings-file and set-environmentsettings-file to an HDLM-related directory. If you do so, the saved file will be deleted during HDLM removal.
Examples In the following example, the utility saves the ODM environment settings in the /tmp/odmset file and the set environment settings in the /tmp/dlnkset file, when the DVD-ROM drive directory is cdrom: # cdrom/HDLM_AIX/hdlmtool/dlmmigsts -b -odm /tmp/odmset -set / tmp/dlnkset KAPL13001-I The dlmmigsts utility completed successfully.
When an error (such as one that might occur in a LVM mirror configuration) is detected and I/O access for a path in the Online(E) status continues, detection of errors will continue. When this parameter is set to on, I/O access is suppressed until troubleshooting measures are taken. This can shorten the time needed to deal with the problem. You do not need to reconfigure the hdisk or restart the host when you change this parameter.
| | } [ | | } -i {on | off} -v {on | off} -s ] -o -h dlmpostrestore Utility for HDLM Restoration Support This utility updates HDLM information to match that of the target system environment when a system replication (clone) is created from a mksysb image that includes HDLM-managed devices. Format /usr/DynamicLinkManager/bin/dlmpostrestore [-s | -h] Parameters -s Suppresses display of a confirmation message when the utility executes. -h Displays the format of the dlmpostrestore utility.
Parameters -k Specify this parameter to display the Reservation Key. The following explains the items displayed when the -k parameter is specified: Reservation Key An asterisk (*) is displayed at the end of the Reservation Key for a Reservation Key of another host. If the Reservation Key is not set, [0x0000000000000000] is displayed. Regist Key The registered Keys are displayed. Key Count The number of registered Keys is displayed. -c Specify this parameter to clear the Reservation Key.
1.
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.
Format /directory-in-which-the-DVD-ROM-is-mounted-or-copied/HDLM_AIX/ hdlmtool/instutil/installhdlm { -f installation-information-settingsfile-name | -h} Parameters -f installation-information-settings-file-name Defines the information needed for installing HDLM. For details about the installation-information settings file, see Items To Be Defined in an installation-information Settings File on page 7-27. -h Displays the format of the installhdlm utility.
Necessity of definition Key name#1 Description#2 Specify the absolute path name of the directory in which the file that contains log information is output. logdir Maxim um Upgrade number New installatio of installa n or re- charact tion installatio ers n Optional Optional 60 Optional Optional#4 60 The default is /var/tmp. For details about the log file, see Log file on page 7-37. licensekeyfile#3 Specify an absolute path to a license key file stored in the host.
Necessity of definition Key name#1 restart Description#2 Specify whether to restart the host after installation. Specify either of the following values: Maxim um Upgrade number New installatio of installa n or re- charact tion installatio ers n Optional Optional 1 y: Restart. n: Do not restart (default). Legend: Optional: If a key and its setting are not specified, the default value will be used.
For details about the dlmchpdattr utility, see dlmchpdattr Utility for Changing HDLM Default Settings on page 7-12. The following table lists and describes the keys defined in the [DISK_DEFAULT_SETTINGS] section. 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.
Table 7-7 Keys in the [ODM_SETTINGS] Section Necessity of definition Key name#1 Description#2 Maxim um Upgrade number New installatio of installa n or re- charact tion installatio ers n 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 3 odm_lun_reset Specify one of the following values to indicate whether to enable or disable the LUN RESET op
[ENVIRONMENT_SETTINGS] section This section defines information that is used when the set operation of the HDLM command is executed. This section is optional. If this section name is omitted, or if any of the keys in the section are not defined, setup by means of the set operation of the HDLM command will not be executed. For details on the set operation, see set (Sets Up the Operating Environment) on page 6-16. The following table lists and describes the keys defined in the [ENVIRONMENT_SETTINGS] section.
Necessity of definition Maxim Upgrad um e numbe installa r of tion or charac reters installa tion Key name#1 Description#2 New installa tion lbex_usetimes_limi t Specify the number of times the same path can be used for sequential I/O operations when the extended Round Robin (exrr), Least I/Os (exlio), or Least Blocks (exlbk) algorithm is used for extended load balancing.
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 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 Description#2 New installa tion Maxim Upgrad um e numbe installa r of tion or charac reters installa tion off: Disabled (default) dynamic_io_path_co ntrol_interval Optional For the dynamic I/O path control function, specify the checking interval (in minutes) for reviewing the information about the switching of controllers performed by the storage system.#5 Optional 4 You can set the checking interval from 1 to 1440. The default is 10.
#4 If you want to enable intermittent error monitoring, specify this key after specifying the auto_failback and auto_failback_interval keys. #5 The checking interval can be set regardless of whether the dynamic I/O path control function is enabled or disabled. The following shows an example of an edited installation information settings file. [INSTALLATION_SETTINGS] installfile_location=/dev/cd0 logdir=/var/tmp licensekeyfile=/var/tmp/hdlm_license licensekey=/var/DLM/dlm.
Log file A log file (installhdlm.log) is output after an unattended installation of HDLM. The following explains the installhdlm.log file. • installhdlm.log is created in the folder whose path is specified by the logdir key in the installation-information settings file. Do not share the log file output directory among the hosts on which unattended installation is being performed. If no value is specified for logdir key, the log file is output to the /var/tmp directory. • If installhdlm.
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.log log file already exists, the utility appends execution information onto the end of the log file. If the size of the log file is equal to or greater than 1 MB when the utility is executed, the log file is renamed to hdlm_installux_sh2.log, and a new log file is created and named 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-115.
□ Return Codes for Hitachi Command Suite Common Agent Component 8-2 Messages Hitachi Dynamic Link Manager User Guide for AIX®
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. aa...aa: clear, help, offline, online, set,or view bb...bb: Year/month/day hour:minute:second Action None. KAPL01002- The HDLM command started. Operation I name = aa...
Message ID Message Text Explanation aa...aa: clear, set, online, offline, or view bb...bb: Specified parameter Action Execute help operationname of the HDLM command (dlnkmgr) to check the parameter, and then retry. For details on the help operation, see help (Displays the Operation Format) on page 6-4. KAPL01006- A necessary parameter is not specified. W Operation name = aa...aa Details The specified operation does not contain the necessary parameter. aa...
Message ID Message Text KAPL01009- A parameter value is invalid. Operation W name = aa...aa, parameter = bb...bb, parameter value = cc...cc, Valid value = dd...dd Explanation Details aa...aa: offline, online, set, or view bb...bb: Parameter name cc...cc: Specified parameter value dd...dd: Specifiable parameter value range Action Specify a correct value for the parameter, and then retry. KAPL01012- Could not connect the HDLM manager. E Operation name = aa...
Message ID Message Text Explanation 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-4. KAPL01014- No authority to execute the HDLM W command. Operation name = aa...aa Details You do not have the administrator permissions necessary to execute the HDLM command. aa...aa: clear, offline, online, set, or view Action Execute the command as a user with root permissions.
Message ID Message Text Explanation 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. Then, specify the applicable path management path ID, and retry the operation. For details about the view operation, see view (Displays Information) on page 6-32.
Message ID Message Text Explanation For details on the view operation, see view (Displays Information) on page 6-32. 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. ¢ view operation The paths have not been configured because creation of the HDLM environment or configuration changes to the HDLM operating environment have not finished.
Message ID Message Text Explanation 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-4. KAPL01021- Cannot execute the HDLM command due E to insufficient memory. Details Memory required for HDLM command processing could not be allocated. Action Terminate unneeded applications to increase the amount of free memory, and then retry.
Message ID Message Text Explanation 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. KAPL01039- During the online operation processing of Details W the HDLM command, a path that cannot A path that cannot be be placed in the Online status was placed Online was detected detected. PathID = aa...
Message ID Message Text Explanation 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. KAPL01045- Too many parameter values are specified. Details W Operation name = aa...aa, parameters = aa...aa: offline, online, bb...
Message ID Message Text Explanation 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. For details on the clear operation, see clear (Returns the Path Statistics to the Initial Value) on page 6-3. For details on the set operation, see set (Sets Up the Operating Environment) on page 6-16. KAPL01050- The currently selected paths will be I changed to the Online status.
Message ID Message Text Explanation (dlnkmgr) to check the path status. For details on the view operation, see view (Displays Information) on page 6-32. 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. Is this OK? [y/n]: Details The offline operation will be started. To continue the offline operation, enter y. To cancel the operation, enter n.
Message ID Message Text Explanation 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 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. If you want to terminate processing, enter n. KAPL01058- The specified parameter value is not W needed. Operation name = aa...aa, parameter = bb...bb, parameter value = cc...
Message ID Message Text Explanation 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...aa path(s) were successfully placed I bb...bb; cc...cc path(s) were not. Operation name = dd...
Message ID Message Text Explanation 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-32. For details on the online operation, see online (Places Paths Online) on page 6-11. For details on the offline operation, see offline (Places Paths Offline) on page 6-6. KAPL01068- Enter a license key: I Details The license key will now be renewed. Enter a license key. Action None.
Message ID Message Text Explanation aa...aa: Year (4 digits)/ month (01-12)/day (01-31) Action Install a permanent license by the expiration day. KAPL01073- The temporary license expired. E Details The temporary license has expired. Register a permanent license. Action Register a permanent license. KAPL01074- The emergency license expired. E Details The emergency license has expired. Register a permanent license. Action Register a permanent license. KAPL01075- A fatal error occurred in HDLM.
Message ID Message Text Explanation Action Enable automatic failbacks, and then re-execute. KAPL01080- The error monitoring interval and the W number of times that the error is to occur conflict with the automatic failback checking interval. Details An intermittent error cannot be detected by using the values specified for the following: the checking interval for automatic failbacks, the error-monitoring interval, and the number of times the error needs to occur.
Message ID Message Text Explanation aa...aa: /var/tmp/ hdlm_license Action When the message that prompts you to enter the license key is displayed, enter the license key. Alternatively, cancel the HDLM command, save the correct license key file in the designated directory, and then re-execute the HDLM command. aa...aa: /var/tmp/ hdlm_license KAPL01084- An attempt to delete the license key file W has failed. File name = aa...aa Details aa...
Message ID Message Text Explanation company if there is a maintenance contract for HDLM. Do not perform the following operations: ¢ ¢ KAPL01095- An attempt to acquire the HDLM version E information has failed. details = aa...aa Simultaneously execute the HDLM command's set -lic operation with the view -sys -lic operation. Execute the HDLM command's set -lic operation while the license for an upgrade or re-installation is being updated. Details aa...
Message ID Message Text Explanation number of trace files, all the current trace files will be deleted. To continue the operation, enter y. To cancel the operation, enter n. Action If you want to execute the operation of the HDLM command, enter y. If you want to terminate processing, enter n. KAPL01100- aa...aa I Details This message indicates the executed command line. aa...aa: Name of the executed command. Action None. KAPL01101- The target HBA port was not found. W Operation name = aa...
Message ID Message Text Explanation If you want to execute the offline processing for the paths which pass the specified target, enter y. If you want to terminate the processing, enter n. KAPL01103- If you are sure that there would be no I problem when all the paths which pass the specified aa...aa port are placed in the Offline(C) status, enter y. Otherwise, enter n. [y/n]: Details This message re-asks the user whether to place all the paths Offline(C). To place all the paths Offline(C), enter y.
Message ID Message Text Explanation Perform one of the following procedures. When performing an installation See Installing HDLM on page 3-17, and then complete the installation. When performing an remove See Removing HDLM on page 3-94, and then complete the remove.
Message ID Message Text Explanation If the dlnkmgr view -sys -audlog command does not display a normal result, contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. KAPL01116- The audit log configuration file is invalid. W Restart the HDLM Manager, and execute the "dlnkmgr view -sys -audlog" command and check the setting. Details The audit log configuration file is invalid.
Message ID Message Text KAPL01120- A storage system model ID could not be W displayed. Details = aa...aa, bb...bb Explanation Details A storage system model ID could not be displayed. aa...aa: Storage recognition information bb...bb: Error code 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 Use the view operation of the HDLM command (dlnkmgr) to check the setting for storage. For details on the view operation, see view (Displays Information) on page 6-32. KAPL01156- The dynamic I/O path control function I was set to aa...aa for storage. Details aa...aa: "on" or "off" Action Use the view operation of the HDLM command (dlnkmgr) to check the setting for storage and LUs. For details on the view operation, see view (Displays Information) on page 6-32.
Message ID Message Text Explanation aa...aa: Trace information Action None. KAPL03003E HDLM API Error information - aa...aa Details This information is required for resolving problems. aa...aa: API trace error information Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Message ID Message Text Explanation 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-4. KAPL03007E An error occurred during communication with the HDLM manager. (aa...aa) Details This information is required for resolving problems. aa...
Message ID Message Text Explanation Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-4. KAPL04001 to KAPL05000 Message ID Message Text Explanation KAPL04001- HDLM manager started. I Action KAPL04002- Could not start the HDLM manager. E Details None.
Message ID Message Text Explanation 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-4. KAPL04004- HDLM manager will now terminate. I Action KAPL04008- Cannot open the option definition file E (aa...aa). Details None. HDLM manager could not start normally because it was unable to open the option definition file. aa...
Message ID Message Text Explanation For details on the set operation, see set (Sets Up the Operating Environment) on page 6-16. KAPL04010- Could not open the error log file. E Details HDLM manager cannot start normally (unable to open the error log file / var/opt/ DynamicLinkManager/log/ dlmmgr[1-16].log). Action Check whether another program is using the file (or has opened the file with Notepad), or whether the error log file has been deleted inadvertently.
Message ID Message Text Explanation DLMgetras Utility for Collecting HDLM Error Information on page 7-4. KAPL04013- Input is impossible via the communication Details E pipe. RC = aa...aa Data could not be read from the pipe file while communicating with an HDLM command. 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 aa...aa: API return code (decimal (base-10) number) Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-4. KAPL04021- HDLM manager information - aa...aa I Details This information is required for resolving problems. aa...
Message ID Message Text Explanation Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-4. KAPL04024- A critical error occurred in the HDLM C manager. (aa...aa) Details This information is required for resolving problems. aa...
Message ID Message Text KAPL04027- The emergency license is valid. The I license expires in aa...aa days on (bb...bb). Explanation 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. KAPL04028- The temporary license expired. E Action KAPL04029- The emergency license expired. E Action KAPL04030- The temporary license has already E expired.
Message ID Message Text Explanation Environment) on page 6-16. KAPL04034- An attempt to create the option definition E file has failed. Details An attempt to re-create an option definition file (/usr/ DynamicLinkManager/ config/dlmmgr.xml) using the default values has failed. Action Remove unnecessary files and secure unused capacity on the file system, Check the write permissions for the directory and file. KAPL04035- The path health check will now start. I Total number of paths = aa...aa Details aa.
Message ID Message Text Explanation Action None. KAPL04045- HDLM SNMP TRAP was sent. Trap ID = I aa...aa, IP Address = bb...bb, Port Number= cc...cc, Community = dd...dd, Trap Data = ee...ee Details SNMP TRAP was sent. aa...aa: Trap ID bb...bb: Destination IP address of the trap cc...cc: Destination port number of the trap dd...dd: Community name given to the trap ee...ee: Transmission data Action None. KAPL04046- An attempt to connect to the HDLM alert E driver has failed. RC = aa...aa.
Message ID Message Text Explanation to recover the settings. For details on the view operation, see view (Displays Information) on page 6-32. For details on the set operation, see set (Sets Up the Operating Environment) on page 6-16. KAPL04054- The owner controller will now be revised. I (number of LUs = aa...aa) Details aa...aa: number of targeted LUs Action None. KAPL04055- The owner controller was revised. I (number of changed LUs = aa...aa) Details aa...aa: number of changed LUs Action None.
Message ID Message Text Explanation The OS memory allocation function was started but an error was returned from the memory allocation function. error information, and then contact your vendor or maintenance company. Refer to the HDLM User's Guide for instructions how to execute the DLMgetras utility. aa...aa: Number of program lines bb...bb: Memory capture size Action Check whether the HDLM driver has started normally.
Message ID Message Text KAPL05014-I The device object (aa...aa) was registered as the path (bb...bb). Explanation Details The path (bb...bb: Core logic path identifier) of the device object (aa...aa: Filter driver management table address) was successfully registered into the core logic. Action None. KAPL05018W Details The FO processing in the path (aa) failed. (bb:cc) Check the connection FO processing failed in the status of the path %x. If there is no path (aa...
Message ID Message Text vendor or maintenance company. Refer to the HDLM User's Guide for instructions how to execute the DLMgetras utility. Explanation bb...bb: Fixed at 0 cc...cc: Fixed at 0 Action Check the message of the HDLM command (dlnkmgr) or the HDLM manager, and then take the appropriate action.
Message ID Message Text Explanation None. KAPL06001 to KAPL07000 Message ID Message Text KAPL06003-I Initialization of the HDLM alert driver (aa...aa) was successful. Explanation Details Initialization of the alert driver (aa...aa: alert driver management table address (hexadecimal number)) completed normally. Action None. KAPL06004E Could not allocate memory. (aa...aa:bb...bb) Details An attempt to reserve memory to save alert information has failed. aa...aa: Program line (hexadecimal number) bb..
Message ID KAPL06010E Message Text Could not process the IOCTL (aa...aa). (bb...bb:cc...cc) Explanation Details Although the IOCTL request (aa...aa: code (hexadecimal number)) from the HDLM manager or API was accepted, it is not one of the requests expected to be processed by the alert driver. bb...bb: error code (hexadecimal number) cc...cc: 0 (fixed) Action Check the message of the HDLM command (dlnkmgr) or HDLM manager, and then take the appropriate action.
Message ID Message Text Explanation Check whether any other error occurred. The information that could not be written is discarded. Review the actual memory size when another error does not occur. When the actual memory size is insufficient, increase the actual memory size. When the actual memory size is sufficient, 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 If the actual memory size is sufficient, 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-4. KAPL07001 to KAPL08000 Message ID Message Text KAPL07819- Data for maintenance: aa...aa bb...bb I cc...cc dd...dd.
Message ID Message Text Explanation bb...bb: Owner controller ID after the change. (Hexadecimal number) Action None. KAPL07825- The owner core of the LU connected to I the path (aa...aa) was changed to (bb...bb). Details The owner core 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...bb: Owner core ID after the change. (Hexadecimal number) Action None.
Message ID Message Text Explanation Check the path in which the error was detected. KAPL08022E A path error occurred. ErrorCode = aa...aa, PathID = bb...bb, PathName = cc...cc.dd...dd.ee...ee.ff...ff, DNum = gg...gg, HDevName = hh...hh Details A physical or logical error occurred in the path. aa...aa: Error code (hexadecimal number) ¢ When the path error was detected by a path health checking or the online operation Displays 0x000F0000 (Fixed).
Message ID Message Text Explanation bb...bb.cc...cc.dd...dd.ee...ee, DNum = ff...ff, HDevName = gg...gg aa...aa: Path ID (same as PathID of view -path) (decimal number) bb...bb: HBA adapter number or Adapter type (same as PathName of view -path) (character string) cc...cc: Bus number or Adapter number (character string) dd...dd: Target ID (hexadecimal number) ee...ee: Host LU number (same as PathName of view -path) (hexadecimal number) ff...
Message ID Message Text Explanation (decimal (base-10) number) Action An intermittent error has occurred. Check the path for any possible problems. For details on what to do, see What To Do for a Path Error on page 5-3, and switch the path shown in the message into Online. KAPL08032-I A path was recovered. (PathID = aa...aa) Details The path has changed to an online status. aa...aa: Path ID (same as PathID of view -path) (decimal (base-10) number) Action None.
Message ID Message Text Explanation Action None. KAPL09013- Some HDLM drivers could not be E removed. 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 KAPL09022- HDLM cannot be removed. aa...aa is running. E Explanation Details 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.
Message ID Message Text Explanation /usr/HDVM/agent/ classes/com/Hitachi/ soft/HiCommand/DVM/ 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.
Message ID Message Text KAPL09048- HDLM cannot be installed. aa...aa is running. E 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 a while, and then perform aa...aa again. E 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-62.
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 KAPL09603- The installation will now stop because a E command or utility cannot be executed. Confirm that the command or utility (aa...aa) exists, and that you have the proper permission. Explanation Details 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.
KAPL10001 to KAPL11000 Message ID Message Text KAPL10001- No parameter has been specified. W Explanation Details No directory to which the collected information will 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-4. KAPL10002- Too many parameters have been W specified.
Message ID Message Text Explanation aa...aa: Invalid parameter 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-4. 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.
Message ID Message Text Explanation 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-4. 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...
Message ID Message Text Explanation be collected in the file for defining the information to be collected. aa...aa: Line number of the file for defining 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-4.
Message ID Message Text Explanation Collecting HDLM Error Information on page 7-4. KAPL10012- The specified file or directory does not W exist. Line = aa...aa, Value = bb...bb Details The specified file or directory does not exist in the file for defining the 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...
Message ID Message Text Explanation check the contents of the file for defining the information to be collected. This file is shown in the message. If the contents of the file are incorrect, 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-4. KAPL10014- You lack read permission for the specified W directory.
Message ID Message Text Explanation aa...aa: Third parameter Action After the DLMgetras utility for collecting HDLM error 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-4. KAPL10016- The root directory has been specified in W the first parameter.
Message ID Message Text Explanation Action None. KAPL10021- Processing terminated before completion I because a signal was received. 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-4.
Message ID Message Text KAPL10032- The entered value is invalid. The utility W for collecting HDLM error information stops. Explanation Details Processing of the DLMgetras utility for 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-4. KAPL10033- The file does not exist. Filename = aa..
Message ID Message Text Explanation the output directory specified at the time of execution, and then contact your HDLM vendor 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 KAPL10521- A parameter is invalid. (parameter = W aa...aa) Explanation Details aa...aa: invalid parameter (character string) 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-25. KAPL10523- An attempt to unmount the file system E has failed. (file system = aa...aa) Details aa...
Message ID Message Text Explanation Details KAPL10525- An internal error occurred in the E dlmrmdev utility. (error code = aa...aa)) In the dlmrmdev utility an Execute the DLMgetras utility to collect error not caused by a user error information, and then contact your occurred. vendor or maintenance company. Refer to aa...aa: error code the HDLM User's Guide for instructions (decimal number) how to execute the DLMgetras utility.
Message ID Message Text Explanation The dlmrmdev command was executed, but some hdisks could not be deleted. Action 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 KAPL10555- Executing the dlmpostrestore utility will I reboot the host. Is this OK? [y/n] : Explanation Details Executing the dlmpostrestore utility will reboot the host. Action 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. [y/ Details W n]: A value other than y or n has been entered for a [y/ n] request. Action Enter either y or n.
Message ID Message Text Explanation Confirm that all of the processes and services that use HDLM managed paths have stopped. After confirming that all the processes and services have stopped, restart them. 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...
Message ID Message Text Explanation An invalid parameter is specified. 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. 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.
Message ID Message Text Explanation dlmchpdattr utility. Make sure that the format of the utility is correct, and then re-execute it. KAPL10578- An attribute value is invalid. attribute W value = aa...aa Details An invalid attribute value is specified. 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.
Message ID Message Text Explanation Action To execute dlmchpdattr utility again, enter either "y" or "n". KAPL10583- An internal error occurred in the E dlmchpdattr utility. Error Code = aa...aa,bb...bb Details A system-based error, not caused by the user, occurred during dlmchpdattr utility processing. aa...aa: Error number (decimal number) bb...
Message ID Message Text Explanation The dlmrmdev utility is not in the default location, or the user does not have execution permissions for the dlmrmdev utility. Check the status of the dlmrmdev utility. 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.
Message ID Message Text Explanation Reboot the host to apply the changes to the settings. Action None. KAPL10586- Processing terminated before completion I because a signal was received. Details The dlmchpdattr process has been terminated by an operation such as Ctrl+C. Action None. KAPL10587- The specified ODM is not installed. W parameter value = aa...aa Details The specified ODM is not installed. aa...
Message ID Message Text Explanation A parameter is not specified for the dlmpr utility. 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-22. KAPL10644- The specified parameters cannot be W specified at the same time. parameter = aa...aa Details The specified parameters cannot be specified for the dlmpr utility at the same time. aa...
Message ID Message Text Explanation aa...aa: specified parameter (character string) Action Execute help of the dlmpr utility to check the parameters that can be specified, and then retry. For details on the dlmpr utility, see dlmpr Utility for Clearing HDLM Persistent Reservation on page 7-22. KAPL10648- An internal error occurred in the dlmpr E utility. Error Code = aa...aa Details An error not caused by the user has occurred in the dlmpr utility. aa...
Message ID Message Text Explanation Make sure that an error has not occurred in the HDLM-management target device, and that the device can be managed by HDLM. If either of the above conditions are not met, contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. DLMgetras utility to collect error information, and then contact your vendor or maintenance company. Refer to the HDLM User's Guide for instructions how to execute the DLMgetras utility. KAPL10650- aa...
Message ID Message Text Explanation KAPL10670- aa...aa: The HDLM driver's hdisk, which is Details I the boot disk, was excluded from the hard aa...aa: Hdisk name disks subject to the clear operation. Action If you want to clear the Reservation Key of the HDLM driver's hdisk, which is t he boot disk, specify and execute the dlmpr utility to clear the HDLM persistent reservation. KAPL10800- The dlmodmset utility completed I normally. Details The dlmodmset utility completed normally. Action None.
Message ID Message Text Explanation specified, and then retry. For details on the dlmodmset utility, see KAPL08001 to KAPL09000 on page 8-48. Details KAPL10804- An internal error occurred in the E dlmodmset utility. Error Code = aa...aa An error not caused by the Execute the DLMgetras utility to collect user has occurred in the error information, and then contact your dlmodmset utility. vendor or maintenance company. Refer to aa...
Message ID Message Text KAPL10808- The user terminated the operation. I Explanation Details The utility has been terminated because n was sent to a request. Action None. KAPL10809- No operation has been specified. W Details 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-48. KAPL10810- An operation is invalid. operation = W aa...
Message ID Message Text Explanation ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ ¢ Set Option Information Clear Data Get HDLM Manager Status Get HDLM Driver Status Get HDLM Alert Driver Status Get SNMP Trap Information Set SNMP Trap Information Set LU Load Balance Get Path Status Log Information Get Local Time Action None. KAPL11902-I aa...aa has started. 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 Manager Status Get HDLM Alert Driver Status ¢ Online ¢ Offline ¢ ¢ ¢ ¢ ¢ Get SNMP Trap Information Set SNMP Trap Information Set LU Load Balance Get Path Status Log Information Get Local Time Action None. 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 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-4. KAPL11905E An unexpected error occurred. Details An exception occurred during processing on the host.
Message ID Message Text Explanation 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. Refer to action of the message outputted just before this message. KAPL13003-I The specified file already exists. Do you want to overwrite it? [y/n]: Action KAPL13004W The entered value is invalid. Re-enter.
Message ID KAPL13008W Message Text A parameter is invalid. parameter = aa...aa Explanation Details aa...aa: Parameter (character string) 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-18. KAPL13009W No parameter value has been specified. parameter = aa...aa Details aa...
Message ID Message Text Explanation option that should be specified, and then reexecute. For details about the dlmmigsts utility, see dlmmigsts Utility for Assisting HDLM Migration on page 7-18. KAPL13012W Too many parameters have been specified. Action KAPL13013E The directory for storing the specified file Details could not be created. Filename = aa...aa aa...
Message ID Message Text Explanation after another, or specify the modified odmsetfile in dlmmigsts again, and then re-execute. For details about the dlmmigsts utility, see dlmmigsts Utility for Assisting HDLM Migration on page 7-18. For details on the dlmodmset utility, see dlmodmset Utility for Setting the HDLM Execution Environment ODM on page 7-20. If parameter = -set, execute dlnkmgr set one after another, or specify the modified dlnksetfile in dlmmigsts again, and then re-execute.
Message ID KAPL13021E Message Text The file dlnksetfile was not restored. Explanation Action Check file name, and then try again. KAPL13101-I The dlmpreremove utility completed successfully. Action KAPL13102-I HDLM can now be removed. Action None. None. KAPL13103-I HDLM can be removed after rebooting the host. Action KAPL13104-I The settings will be changed so that the HDLM driver is not configured on the hdisk. Is this OK? [y/n] Action None. To execute dlmpreremove, enter y.
Message ID Message Text Explanation bb...bb: Return value of the executed processing (decimal number) Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL13109W A parameter is invalid. parameter = aa...aa Details An invalid parameter is specified. aa...aa: The specified parameter (character string) Action With the -h parameter specified, execute the HDLM pre-remove utility (dlmpreremove).
Message ID Message Text Explanation audlog" command, and then specify any desired 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 Contact your HDLM vendor or the maintenance 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.
Message ID KAPL15010W Message Text The HDLM utility was executed by the user who does not have the authority. Command Line = aa...aa Explanation Details aa...aa: Name of the utility that the user executed 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...
Message ID KAPL15104W Message Text aa...aa path(s) were failed to place bb...bb. Command Line = cc...cc Explanation Details aa...aa: Number of paths that failed to be placed online or offline bb...bb: Online or Offline(c) cc...cc: Command that the user executed KAPL15105-I Setting up the operating environment succeeded. Command Line = aa...aa Details KAPL15106E Setting up the operating environment failed. Command Line = aa...aa Details KAPL15107-I Program information was successfully displayed.
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. Action Check whether a path between the host and the storage system is connected. If a path is connected, check whether HDLM is configured correctly. 1004 Details Memory required for HDLM internal processing could not be allocated.
Message ID Explanation 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-4. 1020 Details An unexpected error occurred during HDLM internal processing.
Message ID Explanation Re-execute the command. If the same error occurs again, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-4. 1034 Details An attempt to acquire information about the HDLM version or SP version has failed. Action Re-execute the command.
Message ID Explanation Action Check whether the HDLM manager is running on the host. If it is not running, start the HDLM manager. 1042 Details Information about the path configuration on the specified LU does not match the path configuration information held by HDLM. Action Refresh the host information, check the path status, and then perform the operation again. 1045 Details A parameter is invalid. Action Refresh the host information, and then perform the operation again.
8-120 Messages Hitachi Dynamic Link Manager User Guide for AIX®
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 User Guide for AIX® 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 User Guide for AIX®
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 User Guide for AIX® 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 User Guide for AIX®
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 User Guide for AIX® 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, Hitachi AMS2000/AMS/WMS/SMS series, and HUS100 series 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 HBA (Host Bus Adapter) Device that functions as an interface connecting a host with external devices. In this manual, the term HBA refers to an interface card installed in a host, in configurations where the host and storage units are connected via a FC connection.
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. To distribute the load, load balancing uses multiple paths to perform I/O operations.
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. owner controller A controller that has been set as an owner controller for an LU. Owner controllers are only in the Thunder 9500V series, or Hitachi AMS/WMS series.
path name The path name consisting of the following four elements, separated by periods: - HBA adapter number or adapter type (character string) - Bus number or adapter number (character string) - Target ID (hexadecimal number) - Host LU number (hexadecimal number) A path name is used to identify a path.
SLPR (Storage Logical Partition) A function supported by Hitachi USP series, Universal Storage Platform V/VM series, and Virtual Storage Platform 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 User Guide for AIX® T U V W X Y Z
Index A active host 2-42 adapter number 3-14, 6-50 adapter type 3-14, 6-50 audit log categories and audit events that HDLM can output 2-35 collecting data 2-34 data format 2-39 automatic failback 2-18, 6-22, Glossary-1 automatic failover 2-14 automatic path switching 2-14 AutoPATH_ID 2-3, Glossary-1 B base 10 6-47 boot disk environment Glossary-1 buffer size 3-80 changing the buffer size per monitoring interval duration 3-83 bus number 6-50 C CHA 2-4 CHA (Channel Adapter) Glossary-1 changing HDLM default
Dev number Glossary-2 directory to which collected information is output 7-5, 7-15 Displayed program information 6-34 displaying information 6-32 LU information 6-52 path information 6-32, 6-41 path information (by selecting a display item) 6-32 program information 6-32, 6-34 summary of path information 6-33 dlmchpdattr 7-12 DLMgetras 5-6, 5-7 dlmgetras 7-4 dlmgetrasinst 7-15 dlminstcomp 7-18 dlmmigsts 7-18 dlmodmset 7-20 dlmpostrestore 7-22 dlmpr 7-22 dlmpreremove 7-24 dlmrmdev 7-25 dlnkmgr 6-1 DNum 5-3 dy
HDLM features 1-2 functions 2-1 installing 3-17 Migrating 3-53 migration of 3-12 new installation 3-24 new installation of 3-11 overview 1-1 preparations for an upgrade installation or reinstallation of 3-35 preparations for new installation of 3-22 program information 6-34 re-installation of 3-12 removing 3-94 setup 3-70 type of installation 3-11 upgrade installation of 3-12 Upgrade Installation or Re-installation 3-36 HDLM alert driver 2-7, Glossary-3 HDLM command 2-6 HDLM driver 2-7, Glossary-3 HDLM env
load balancing 1-2, 2-8, 6-19, Glossary-4 load balancing algorithms 2-12 load distribution using load balancing 2-8 log filter 2-32 logging level values 6-19 logical device file Glossary-4 logical unit 2-3 logical unit ID 6-51 logical volume number Glossary-2 LU 2-4 configuration 2-5 LU (Logical Unit) Glossary-4 LUN 6-51 M manual path switching 2-19 message examining 5-5, 5-6 format and meaning of ID 8-3 terms that appear 8-3 terms used for explanation 8-3 message level 8-3 Messages 8-1 messages adjusting
S 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-50 Performing Failovers and Failbacks Using Path Switching 2-14 persistent reservation Glossary-6 placing a path or paths offline 6-6 placing a path or paths online 6-11 placing online path 5-5 port 2-3 position of the HDLM driver and hdisk 2-7 PowerHA installing HDLM, in a PowerHA 5.5 or PowerHA 6.1 environment 3-57 installing HDLM, in a PowerHA 7.
U unattended installation installation-information settings file 7-27 log file 7-37 upgrade installation 3-12 utilities dlmmigsts Utility for Assisting HDLM Migration 7-18 dlmodmset Utility for Setting the HDLM Execution Environment ODM 7-20 dlmpostrestore Utility for HDLM Restoration Support 7-22 dlmpr, for clearing HDLM persistent reservation 7-22 dlmpreremove, Utility for Executed Before Removing HDLM 7-24 dlmrmdev, Utility for Deleting HDLM Drivers7-25 installhdlm, Utility for Installing HDLM 7-26 inst
Hitachi Dynamic Link Manager User Guide for AIX®
Hitachi Data Systems Corporate Headquarters 750 Central Expressway Santa Clara, California 95050-2627 U.S.A. Phone: 1 408 970 1000 www.hds.com info@hds.com Asia Pacific and Americas 750 Central Expressway Santa Clara, California 95050-2627 U.S.A. Phone: 1 408 970 1000 info@hds.com Europe Headquarters Sefton Park Stoke Poges Buckinghamshire SL2 4HD United Kingdom Phone: + 44 (0)1753 618000 info.eu@hds.
