HP XP P9500 User Manual

Hitachi dynamic link manager software user guide for aix (6.6) (t5208-96012, november 2011).
Hide thumbs
   
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450
Hitachi Command Suite
Dynamic Link Manager Software
User Guide (for AIX(R))
Document Organization
Product Version
Contents
MK-92DLM111-20

Advertising

   Also See for HP XP P9500

   Related Manuals for HP XP P9500

   Summary of Contents for HP XP P9500

  • Page 1

    Hitachi Command Suite Dynamic Link Manager Software User Guide (for AIX(R)) Document Organization Product Version Getting Help Contents MK-92DLM111-20...

  • Page 2

    © 2011 Hitachi, Ltd., Hitachi Data Systems Corporation. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd.

  • Page 3: Table Of Contents

    Contents Preface....................xi Intended audience....................xii Product version......................xii Release notes......................xii Document revision level....................xii Document organization.....................xii Referenced documents.....................xiii Document conventions.....................xiii Convention for storage capacity values..............xv Getting help......................xvi Comments......................xvi 1 Overview of HDLM................1-1 What is HDLM?.......................1-2 HDLM Features.......................1-3 2 HDLM Functions...................2-1 Devices Managed by HDLM..................2-3 System Configuration....................2-3 LU Configuration.....................2-5 Program Configuration....................2-6...

  • Page 4: Table Of Contents

    Path status transition..................2-19 The online path status................2-19 The offline path status................2-19 Correspondence Between Path Statuses Displayed by the OS and by HDLM2-20 Status transitions of a path..............2-20 Monitoring intermittent errors (functionality when automatic failback is used)...2-22 Checking intermittent errors................2-23 Setting up intermittent error monitoring............2-23 Intermittent Error Monitoring Actions...............2-23 When an intermittent error occurs............2-24 When an intermittent error does not occur..........2-24...

  • Page 5: Table Of Contents

    Notes on the Automatic Failback..............3-16 Notes on the queue_depth Parameter Value for an HDLM-Managed device..3-16 Installing HDLM....................3-16 Available Installation Methods................3-16 When Performing a New Installation, Upgrade Installation, or Re-installation of HDLM....................3-17 When Performing a Migration of HDLM...........3-19 Preparations for a New Installation of HDLM.............3-21 Perform Operations for HDLM Management-Target Devices......3-21 Set Up the Hardware................3-22 Switch the Kernel Mode ................3-23...

  • Page 6: Table Of Contents

    Displaying the Hitachi Network Objectplaza Trace Library setup menu....3-79 Changing the Size of Integrated Trace Files............3-79 Changing the Number of Integrated Trace Files..........3-80 Changing the Buffer Size Per Monitoring Interval Duration.........3-81 Adjusting the Number of Messages to be Output Per Monitoring Interval....3-82 Finishing the Hitachi Network Objectplaza Trace Library Settings......3-83 Applying the Hitachi Network Objectplaza Trace Library Settings......3-84 About the Reservation Policy..................3-84...

  • Page 7: Table Of Contents

    Setting Up the Operating Environment............4-10 Viewing License Information................4 -11 Updating the License..................4 -11 Viewing HDLM Version Information..............4-12 Viewing HDLM Component Information............4-13 Starting and Stopping the HDLM Manager............... 4 -14 Starting the HDLM Manager................4 -14 Stopping the HDLM Manager................4-14 HDLM Resident Processes..................

  • Page 8: Table Of Contents

    To Display the Format of the Clear Operation..........6-3 help (Displays the Operation Format)...............6-4 Format......................6-4 Parameter......................6-4 offline (Places Paths Offline)..................6-6 Format......................6-6 To Place Paths Offline................6-6 To Display the Format of the Offline Operation..........6-6 Parameters......................6-6 To Place Paths Offline................6-6 To Display the Format of the Offline Operation........6-10 online (Places Paths Online)...................6-11 Format......................6-11 To Place Paths Online................6-11...

  • Page 9: Table Of Contents

    Parameters.....................7-12 dlmgetrasinst Utility for Collecting HDLM Installation Error Information.....7-14 Format......................7-15 Parameters.....................7-15 List of Collected Error Information..............7-15 dlminstcomp Utility for HDLM Component Installation..........7-17 Format......................7-18 Parameter......................7-18 dlmmigsts Utility for Assisting HDLM Migration............7-18 Format......................7-18 Parameters.....................7-18 dlmodmset Utility for Setting the HDLM Execution Environment ODM......7-20 Format......................7-20 Parameters.....................7-20 dlmpostrestore Utility for HDLM Restoration Support..........7-21...

  • Page 10: Table Of Contents

    KAPL15001 to KAPL16000..................8-110 Return Codes for Hitachi Command Suite Common Agent Component.....8-113 A Functional Differences Between Versions of HDLM........A-1 Functional Differences Between Version 6.2 and Versions Earlier than 6.2....A-2 Functional Differences Between Version 6.1 and Versions Earlier than 6.1....A-2 Functional Differences Between Version 6.0 or Later and Versions Earlier than 6.0..A-2 B Differences Between HDLM Version 5.9 or Later and Version 5.8.1 or Earlier ......................B-1 Add-in HDLM Driver Module..................B-2...

  • Page 11

    Preface This document describes how to use the Hitachi Dynamic Link Manager. □ Intended audience □ Product version □ Release notes □ Document revision level □ Document organization □ Referenced documents □ Document conventions □ Convention for storage capacity values □...

  • Page 12: Overview Of Hdlm

    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 •...

  • Page 13: B Differences Between Hdlm Version 5.9 Or Later And Version 5.8.1 Or Earlier, Utility Reference

    Chapter Description 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. 5 Troubleshooting on page 5-1 Explains how to troubleshoot a path error, HDLM failure, or any other problems that you might encounter.

  • Page 14

    • General font conventions • Conventions in syntax explanations These conventions are described below. General Font Conventions The following table lists the general font conventions: Font Convention Bold Bold type indicates text on a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels.

  • Page 15

    Example font or Convention symbol database-name This font style marks a placeholder that indicates where appropriate characters are to be entered in an actual command. Bold code-font characters indicate the abbreviation for a command. Underlined characters indicate the default value. perm Square brackets enclose an item or set of items whose specification is optional.

  • Page 16: Getting Help

    Logical capacity unit Value 1 MB 1,024 KB or 1,024 bytes 1 GB 1,024 MB or 1,024 bytes 1 TB 1,024 GB or 1,024 bytes 1 PB 1,024 TB or 1,024 bytes 1 EB 1,024 PB or 1,024 bytes Getting help The Hitachi Data Systems customer support staff is available 24 hours a day, seven days a week.

  • Page 17: Overview Of Hdlm

    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.

  • Page 18: What Is Hdlm

    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.

  • Page 19: Hdlm Features

    HDLM Features HDLM features include the following: The ability to distribute a load across multiple paths. This is also known as load balancing. When a host is connected to a storage system via multiple paths, HDLM can distribute the load across all the paths. This prevents one, loaded down path from affecting the processing speed of the entire system.

  • Page 20

    Overview of HDLM Hitachi Dynamic Link Manager User Guide (for AIX(R))

  • Page 21: Hdlm Functions

    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.

  • Page 22: Cluster Support

    □ Cluster support HDLM Functions Hitachi Dynamic Link Manager User Guide (for AIX(R))

  • Page 23: Parameters

    Devices Managed by HDLM Below is a list of devices that can or cannot be managed by HDLM. The devices that can be managed by HDLM are called HDLM management-target devices. HDLM management-target devices: The following devices are from the storage systems listed in Section What is HDLM? on page 1-2:...

  • Page 24

    Figure 2-1 HDLM System Configuration Table 2-1 HDLM System Components on page 2-4 lists the HDLM system components. Table 2-1 HDLM System Components Components Description A host bus adapter. This serves as a cable port on the host. A dedicated network that is used for data transfer between the host machine and storage systems.

  • Page 25: Lu Configuration

    LU Configuration On a system using HDLM, the logical device file for the HDLM management- target 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).

  • Page 26: Program Configuration

    Program Configuration HDLM is actually a combination of several programs. Because each program corresponds to a specific HDLM operation, it is important to understand the name and purpose of each program, along with how they are all interrelated. Figure 2-3 Configuration of the HDLM Programs on page 2-6 configuration of the HDLM programs.

  • Page 27

    Program name Functions • Change the default value of the hdisk attribute • 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 •...

  • Page 28: Distributing A Load Using Load Balancing

    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.

  • Page 29

    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.

  • Page 30: Paths To Which Load Balancing Is Applied

    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.

  • Page 31: Load Balancing Algorithms

    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,...

  • Page 32

    • The Extended Round Robin algorithm • The Least I/Os algorithm • The Extended Least I/Os algorithm • The Least Blocks algorithm • The Extended Least Blocks algorithm The above algorithms are divided into two categories, which differ in their processing method.

  • Page 33: Performing Failovers And Failbacks Using Path Switching

    Table 2-4 Features of the Load Balancing Algorithms Algorithm type Algorithm features • These types of algorithms are most effective when a lot of Round Robin discontinuous, non-sequential I/Os are issued. • Least I/Os • Least Blocks • Extended Round If there is a read request for I/O data that is sequential with Robin the data of the I/O that was issued immediately beforehand,...

  • Page 34: Automatic Failovers

    • An error occurred on the path. • A user executed the HDLM command's offline operation. For details on the offline operation, see offline (Places Paths Offline) on page 6-6. For details on path statuses and the transitions of those statuses, see Path status transition on page 2-19.

  • Page 35: Priority Of Switching Destination Paths

    Figure 2-8 Path switching 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.

  • Page 36

    following shows an example of the procedure for setting the path priority number. Execute a command that displays the path information for the LU: # lspath -l hdisk4 -F"name parent path_id connection path_status status" hdisk4 fscsi0 0 50060e8005271720,31000000000000 Available Enabled hdisk4 fscsi1 1 50060e8005271730,31000000000000 Available Enabled hdisk4 fscsi2 2 50060e8005271740,31000000000000 Available...

  • Page 37

    000002 hdisk2 00000 9500V.0051.0020 000003 hdisk0 00001 9500V.0051.0005 000004 hdisk1 00001 9500V.0051.0015 000005 hdisk2 00001 9500V.0051.0020 Execute the following command to find the parent device of hdisk (the HBA device instance). # lsdev -C -l hdisk4 -F 'parent' fscsi0 Execute the following command to find the physical location code, based on the HBA device instance.

  • Page 38: Manual Path Switching

    In order to use the automatic failback function, HDLM must already be monitoring error recovery on a regular basis. When using the Thunder 9500V series, or Hitachi AMS/WMS series, HDLM will select the next path to be used first from among the online owner paths, and then from the online non-owner paths.

  • Page 39: Path Status Transition, The Online Path Status, The Offline Path Status

    owner paths. When the Lightning 9900V series, Hitachi USP, Universal Storage Platform V/VM, Virtual Storage Platform, Hitachi AMS2000 series, or Hitachi SMS is being used, all paths that access the same LU are candidates for the switching destination path. All other paths that run through the same physical path are switched.

  • Page 40: Status Transitions Of A Path, Correspondence Between Path Statuses Displayed By The Os And By

    • Offline(E) The status indicating that an I/O could not be issued on a given path, because an error occurred on the path. The (E) means error. Correspondence Between Path Statuses Displayed by the OS and by HDLM Table 2-5 Correspondence Between Path Statuses Displayed by the OS and by HDLM on page 2-20 shows the correspondence between the path statuses displayed when commands such as the AIX lspath command are...

  • Page 41

    Figure 2-9 Path status transitions Legend: Online operation: Online operation performed by executing the dlnkmgr command's online operation. Offline operation: Offline operation performed by executing the dlnkmgr command's offline operation. When no Online or Offline(E) paths exist among the paths that access the same LU.

  • Page 42

    This path is deleted when the AIX chdev command is executed on an hdisk where an Online or Offline(E) path exists. To restore the deleted path, remove the cause of the error and then execute the AIX mkdev -l hdisk-name or cfgmgr command. When an Online or Offline(E) path exists among the paths that access the same LU.

  • Page 43: Setting Up Intermittent Error Monitoring, Intermittent Error Monitoring Actions

    We recommend that you use intermittent error monitoring along with the automatic failback function. A path in which an error occurs a specified number of times within a specified interval is determined to have an intermittent error. The path where an intermittent error occurs has an error status until the user chooses to place the path back online.

  • Page 44: When An Intermittent Error Occurs, When An Intermittent Error Does Not Occur

    When an intermittent error occurs When an error occurs on a path a specified number of times within a specified interval, the error monitoring will finish and the path is determined to have an intermittent error, upon which the path is removed from those subject to automatic failbacks.

  • Page 45

    Figure 2-11 What Will Happen When an Intermittent Error Does Not Occur on a Path As shown in Figure 2-11 What Will Happen When an Intermittent Error Does Not Occur on a Path on page 2-25, normally the count for the number of times that an error occurs is started after the path is first recovered from an error by using the automatic failback function.

  • Page 46: When A User Changes The Intermittent Error Information

    Figure 2-12 What Will Happen When Conditions Are Changed During Error Monitoring When a User Changes the Intermittent Error Information The following might be reset when a user changes any of the values set for the intermittent error or the path status: the number of errors that have already been counted during error monitoring, the amount of time that has passed since error monitoring has started, and the information about whether an intermittent error has occurred.

  • Page 47

    Number of Information errors and time about paths passed since User operation not subject to error automatic monitoring failback started the set operation, (but not changing the conditions) while intermittent error monitoring is being performed Changing the intermittent (Not applicable) Inherited error monitoring conditions (Not counted.)

  • Page 48: Detecting Errors By Using Path Health Checking, Error Management

    The number of errors and the time passed since error monitoring had started are both reset to 0, and then monitoring restarts from the time the HDLM manager starts. Detecting errors by using path health checking HDLM can check the status of paths for which I/O operations are not being performed at regular intervals.

  • Page 49: Types Of Collected Logs

    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.

  • Page 50

    Table 2-7 Types of error information Log name Description Output destination Integrated trace Operation logs of the HDLM The default file path is /var/ file command are collected. 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.

  • Page 51: Filtering Of Error Information

    Log name Description Output destination HDLM HDLM configuration log is an /var/DynamicLinkManager/ configuration log operation log of the configuration log/dlmconfig[1-2].log processing for the HDLM driver. 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.

  • Page 52: Installation Error Information (dlmgetrasinst)

    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).

  • Page 53: Collecting Audit Log Data

    Collecting Audit Log Data HDLM and other Hitachi storage-related products provide an audit log function so that compliance with regulations, security evaluation standards, and industry-specific standards can be shown to auditors and evaluators. The following table describes the categories of audit log data that Hitachi storage- related products can collect.

  • Page 54: Categories And Audit Events That Hdlm Can Output To The Audit Log

    Category Explanation An event indicating that a permitted operation performed ConfigurationAccess 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 •...

  • Page 55

    Severit Category Explanation Audit event Message ID Startup of the HDLM KAPL15402-E manager failed. The HDLM manager KAPL15403-I stopped. Startup of the KAPL15060-I DLMgetras utility Termination of the KAPL15061-I DLMgetras utility Startup of the KAPL15084-I dlmgetrasinst utility Termination of the KAPL15085-I dlmgetrasinst utility...

  • Page 56

    Severit Category Explanation Audit event Message ID An attempt to display KAPL15108-E program information failed. An attempt to display KAPL15109-I HDLM management- target information was successful. An attempt to display KAPL15110-E HDLM management- target information failed. Processing of the KAPL15001-I dlmpr -k command was successful.

  • Page 57: Requirements For Outputting Audit Log Data, Destination And Filtering Of Audit Log Data

    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. 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.

  • Page 58: Audit Log Data Formats

    • 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.

  • Page 59

    [process-ID] ¢ message-section ¢ The following shows the format of message-section and explains its contents. The format of message-section: common-identifier,common-specification-revision-number,serial- number,message-ID,date-and-time,entity-affected,location- affected,audit-event-type,audit-event-result,subject-ID-for-audit-event- result,hardware-identification-information,location-information,location- identification-information,FQDN,redundancy-identification- information,agent-information,host-sending-request,port-number- sending-request,host-receiving-request,port-number-receiving- request,common-operation-ID,log-type-information,application- identification-information,reserved-area,message-text Up to 950 bytes of text can be displayed for each message-section. Table 2-12 Items Output in the Message Section Explanation Item...

  • Page 60: Integrated Hdlm Management Using Global Link Manager

    Explanation Item Agent information Agent information Host sending request Name of the host sending a request Port number sending Number of the port sending a request request Host receiving request Name of the host receiving a request Port number receiving Number of the port receiving a request request Common operation ID...

  • Page 61

    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 •...

  • Page 62

    2-42 HDLM Functions Hitachi Dynamic Link Manager User Guide (for AIX(R))

  • Page 63: Creating An Hdlm Environment

    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.

  • Page 64

    □ Settings for Using Oracle RAC 10g or Oracle RAC 11g □ Settings for Using VCS □ Uninstalling HDLM Creating an HDLM Environment Hitachi Dynamic Link Manager User Guide (for AIX(R))

  • Page 65: Hdlm System Requirements, Host And Os Support For Hdlm

    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 shown in Table 3-1 Applicable OSs for the Host on page 3-3.

  • Page 66

    Kernel Technology Level 01 ioslevel 2.1.0.xx to 2.2.0.xx (where xx is a number) AIX V7.1 (Virtual I/O Server) Every SP is applicable, unless otherwise specified. To set up a boot disk environment that uses Thunder 9500V series, Hitachi AMS/WMS series, or Hitachi SMS, use SP2 or a later service pack. An environment in which the Secure by Default functionality is enabled during installation of the OS is not supported.

  • Page 67: Storage Systems Supported By Hdlm, Storage Systems

    Universal Storage Platform V/VM (excluding HP XP20000 and HP ¢ XP24000) Hitachi Virtual Storage Platform ¢ 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.1 or later: HP XP series...

  • Page 68: When Handling Intermediate Volumes Managed By Hitachi Rapidxchange, Cluster Software Supported By Hdlm

    • 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. For applicable HBAs, see the HDLM Release Notes.

  • Page 69

    Related Programs • Oracle RAC 10g 10.2.0.3.0 If the HDLM device is specified for direct access: #1#2 ASM + raw devices • Oracle RAC 10g 10.2.0.4.0 If the HDLM device is specified for direct access: ASM + raw devices • Oracle RAC 11g 11.1.0.6.0 If the HDLM device is specified for direct access: ASM + raw devices...

  • Page 70

    Related Programs AIX V6.1 (Virtual I/O • PowerHA 5.5 Server) Client: Technology Level 02 or later Server: ioslevel 2.1.0.xx to 2.2.0.xx (where xx is a number) • PowerHA 6.1 Client: Technology Level 02 or later Server: ioslevel 2.1.0.xx to 2.2.0.xx (where xx is a number) •...

  • Page 71: Disk Capacity Requirements

    Sometimes, if JFS2 is being used and a crash (halt -q) fails over a node, the resource to be mounted on the failover-destination node is not properly mounted. This problem occurs regardless of whether HDLM is installed. Apply fix pack 3.3.0.3 or later. Memory and Disk Capacity Requirements This subsection explains the memory and disk capacity requirements.

  • Page 72: Number Of Paths Supported In Hdlm, Flow For Creating An Hdlm Environment

    q = (t × n) / 1024 (in MB), where: t is the size of the trace file (units: KB, default is 1,000), and n is the number of trace files (default is 4). The resulting fraction will be rounded up. This is the amount of unused capacity required to use the installhdlm utility.

  • Page 73: Types Of Hdlm Installation

    Figure 3-1 Flow of HDLM Environment Setup Types of HDLM Installation This section describes the following HDLM installation types: new installation, upgrade installation, migration, and re-installation. New installation of HDLM Installing HDLM on a server where HDLM has not yet been installed is called a new installation.

  • Page 74: Notes On Creating An Hdlm Environment, Notes On Installing Hdlm

    Re-installation of HDLM Installing the same version of HDLM for repair purposes without uninstalling the existing instance of HDLM is called re-installation of HDLM. Notes on Creating an HDLM Environment This section provides notes on creating an HDLM environment. For notes on operating HDLM, see Notes on Using HDLM on page 4-2.

  • Page 75: Notes On The Virtual I/o Server

    • If you upgrade or re-install HDLM before you resolve a path failure, LU reservations might persist without being released. In such a case, use the utility for clearing HDLM persistent reservations (dlmpr) to release the LU reservation, if necessary. •...

  • Page 76: Notes On A License Key, Notes On Trace Files

    When the NPIV option is set to on, HBA adapter number and bus number for PathName, which are output by HDLM command view operations, are changed to adapter type and adapter number respectively. The view operation parameters for which the above changes are to be applied are as follows: -path parameter (displays path information) ¢...

  • Page 77: Notes On Storage Systems, Notes On The Cluster

    Trace files after the migration: /var/DynamicLinkManager/log/ hdlmtrn.log (n indicates a file number) Notes on Storage Systems • Do not change the vendor ID or product ID of a storage system. If you do, HDLM will not be able to recognize the storage system. •...

  • Page 78: Notes On The Automatic Failback, Notes On The Queue_depth Parameter Value For An Hdlm-managed Device

    • If you are using PowerHA, note that HDLM does not support non- concurrent volume groups due to limitations in PowerHA. For details, contact IBM. • If all of the following conditions are met, HDLM can be migrated without stopping PowerHA services: The shared volume groups used by PowerHA are concurrent volume ¢...

  • Page 79

    Upgrade installation ¢ Re-installation ¢ Unattended installation ¢ • Use SMIT or the installp command. You can also copy the contents of the HDLM DVD-ROM to a desired directory, and then perform installation from that directory. Copy the following files from the installation DVD-ROM to the same directory: DLManager.mpio.bff ¢...

  • Page 80

    Table 3-7 Combination of Available Installation Methods and Installation Environments Installation environment Host Virtual I/O server Installation method Local boot Local boot Boot disk Boot disk disk disk environment environment environment environment installux.sh or installp command SMIT Unattended installation Installation on alternate disks Legend: Yes: Can be executed...

  • Page 81: When Performing A Migration Of Hdlm

    Only new installations, upgrade installations, and re-installations are supported. Only upgrade installations and re-installations are supported. The installation procedures are explained in this manual in the locations shown below. installux.sh or installp command Performing a New Installation of HDLM on page 3-24 ¢...

  • Page 82

    Table 3-9 Combination of Available Migration Methods and Migration Environments Migration environment Host Virtual I/O server Migration method Local boot Local boot disk Boot disk Boot disk disk environment environment environment environment installux.sh installp command SMIT Unattended installation Installation on alternate disks Legend: Yes: Can be executed...

  • Page 83: Preparations For A New Installation Of Hdlm, Perform Operations For Hdlm Management-target Devices

    Yes: Can be executed No: Cannot be executed N/A: Not applicable Before you migrate HDLM to an environment that uses PowerHA and a virtual I/O server, cancel the virtual disk definitions of the virtual I/O server. After you have migrated HDLM, redefine these virtual disk definitions.

  • Page 84: Set Up The Hardware

    Figure 3-2 Execution Result Example of the Mount -p Command (Preparations for a New Installation of HDLM) The following example manages the device, which is shown in the shaded portion of Figure 3-2 Execution Result Example of the Mount - p Command (Preparations for a New Installation of HDLM) on page 3-22, by using HDLM.

  • Page 85: Switch The Kernel Mode, Set Up Cluster Software

    # cfgmgr # lsdev -Cc disk Switch the Kernel Mode Before installing HDLM, decide which kernel mode you will use to operate AIX, and change to the desired kernel mode if necessary. The following shows how to switch the kernel mode. Check the kernel mode currently being used.

  • Page 86: Performing A New Installation Of Hdlm, When Installing Hdlm In A Local Boot Disk Environment

    Performing a New Installation of HDLM When Installing HDLM in a Local Boot Disk Environment To perform a new installation of HDLM: Log in to AIX as the root user. If you are using a virtual I/O server, see the virtual I/O server documentation to log in to AIX.

  • Page 87

    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 ¢...

  • Page 88

    As required, execute the dlmodmset utility for setting the HDLM execution environment ODM. For details, see dlmodmset Utility for Setting the HDLM Execution Environment ODM on page 7-20. Execute the following command to configure the hdisk: # cfgmgr If the hosts and storage systems are connected by a Fibre Channel switch, perform steps 14 to 18.

  • Page 89

    Make sure that hdisks are available: # lsdev -Cc disk hdisk0 Available 1S-08-00-8,0 16 Bit LVD SCSI Disk Drive hdisk1 Available 1S-08-00-9,0 16 Bit LVD SCSI Disk Drive hdisk2 Available 1S-08-00-10,0 16 Bit LVD SCSI Disk Drive hdisk3 Available 1H-08-02 Hitachi Disk Array (Fibre) hdisk4 Available 1H-08-02...

  • Page 90: When Installing Hdlm In A Boot Disk Environment

    If you are using a virtual I/O server, define an hdisk as a virtual target device. Execute the following command on the virtual I/O server: When creating the hdisk as a virtual target device: $ mkvdev -vdev hdisk-name -vadapter virtual-SCSI-server- adapter-name When creating the logical volume as a virtual target device: $ mkvdev -vdev logical-volume-name -vadapter virtual-SCSI-...

  • Page 91

    Identify the physical volume that contains the boot logical volume ¢ hd5: # lsvg -M rootvg | grep -w hd5 hdisk3:1 hd5:1 In this example, hdisk3 contains the boot logical volume hd5. Identify the physical volume used for booting: ¢ # getconf BOOT_DEVICE hdisk3 In this example, hdisk3 is used for booting.

  • Page 92

    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 6. If any devices to be managed by HDLM are not recognized, proceed to step 8.

  • Page 93

    Even though a message asking you to restart the host is displayed during installation, you do not have to restart the host. 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 6.

  • Page 94

    Make sure that the number of configured boot disks is the same as the number of paths that you checked in step 15: # bootlist -m normal -o hdisk10 blv=hd5 hdisk10 blv=hd5 hdisk0 blv=hd5 hdisk1 blv=hd5 If the hosts and storage systems are connected by a Fibre Channel switch, perform steps 19 to 23.

  • Page 95

    Make sure that hdisks are available: # lsdev -Cc disk hdisk0 Available 1S-08-00-8,0 16 Bit LVD SCSI Disk Drive hdisk1 Available 1S-08-00-9,0 16 Bit LVD SCSI Disk Drive hdisk2 Available 1S-08-00-10,0 16 Bit LVD SCSI Disk Drive hdisk3 Available 1H-08-02 Hitachi Disk Array (Fibre) hdisk4 Available 1H-08-02...

  • Page 96: Perform Operations For Hdlm Management-target Device

    If HDLM Manager, HDLM Alert Driver, and HDLM Driver are all Alive, all programs are running correctly. If you are not using a virtual I/O server, go to step 33. If you are using a virtual I/O server, define an hdisk as a virtual target device.

  • Page 97: Performing An Upgrade Installation Or Re-installation Of Hdlm

    Unmount the disks. If the HDLM management-target devices are mounted, unmount them as follows: First, execute the command below to check the current settings. ¢ # mount -p The current settings will be output as shown in Figure 3-3 Example of Results from Executing the Mount -p Command (Preparations for an Upgrade Installation or Re-installation of HDLM) on page 3-35.

  • Page 98

    If an upgrade installation or re-installation fails, AIX automatically uninstalls HDLM, and the HDLM settings are deleted. Perform this step so that a copy of the HDLM settings is available in this case. If an upgrade installation or re-installation fails, perform a new installation, and then re-execute setup to reflect the settings that have been backed up.

  • Page 99

    KAPL10526-I An attempt to unmount the file system has succeeded. (file system = /mnt/fs01) KAPL10527-I An attempt to inactivate the volume group has succeeded. (volume group = vg01) hdisk7 Defined hdisk8 Defined hdisk9 Defined hdisk10 Defined KAPL10531-I The status of all of the HDLM drivers was changed to "Defined".

  • Page 100

    utility without the -e parameter specified, the existing HDLM device is deleted. /DVD-ROM-mounted-directory/HDLM_AIX/hdlmtool/dlmrmdev Deleting an existing hdisk ¢ 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.

  • Page 101

    Note that the hdlm_license and dlm.lic_key files are deleted after installation finishes successfully. Insert the HDLM DVD-ROM into the DVD-ROM drive, and mount the DVD- ROM.. If you install HDLM by using a directory to which the DVD-ROM is copied, you do not have to perform this step.

  • Page 102

    If you execute the dlmrmdev utility without the -e parameter specified at step 3 or 7 and then the KAPL09048-E message is displayed, the hdisk for the device that is managed by HDLM still remains. If you execute the dlmrmdev utility with the -e parameter specified at step 3 or 7 and then the KAPL09048-E message is displayed, the hdisk for the device that is managed by HDLM still remains, and its status is Available.

  • Page 103

    Support Cluster Elog Level Elog File Size (KB) : 9900 Number Of Elog Files Trace Level Trace File Size(KB) : 1000 Number Of Trace Files Path Health Checking : on(30) Auto Failback : on(60) Intermittent Error Monitor : off HDLM Manager Ver WakeupTime Alive x.x.x-xx...

  • Page 104

    Execute the following command in the client logical partition to confirm that the physical volume has been recognized as hdisk. If the following message is displayed, then the physical volume (hdisk) was recognized correctly. # lsdev -Cc disk hdisk1 Available Virtual SCSI Disk Drive Table 3-11 List of Files Inherited During an Upgrade Installation or Re- installation on page 3-42 lists and describes the files that are inherited...

  • Page 105

    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-file- name Make sure that the license has not expired. Save the HDLM execution environment ODM settings.

  • Page 106

    Execute the following command and verify the status of the hdisks recognized as HDLM-managed devices: # lsdev -Cc disk If you attempted to delete an existing hdisk by executing the ¢ dlmrmdev utility, verify that the hdisk has been deleted. If you attempted to inherit the existing hdisk configuration by ¢...

  • Page 107

    Even though a message asking you to restart the host is displayed during installation, you do not have to restart the host. If you execute the dlmrmdev utility without the -e parameter specified at step 6 and then the KAPL09172-E message is displayed, the hdisk for the device that is managed by HDLM still remains.

  • Page 108

    Make sure that the fileset item in the output listing contains DLManager.mpio.rte, and all the displayed statuses are COMMITTED. If one or more of the displayed statuses are BROKEN, uninstall HDLM, and then proceed to step 13 to perform a new installation of HDLM. If HDLM was not upgraded or re-installed properly, perform a new installation of HDLM.

  • Page 109

    Elog Level Elog File Size (KB) : 9900 Number Of Elog Files Trace Level Trace File Size(KB) : 1000 Number Of Trace Files Path Health Checking : on(30) Auto Failback : on(60) Intermittent Error Monitor : off HDLM Manager Ver WakeupTime Alive x.x.x-xx...

  • Page 110: When Installing Hdlm On Alternate Disks

    # cfgmgr Execute the following command in the client logical partition to confirm that the physical volume has been recognized as hdisk. If the following message is displayed, then the physical volume (hdisk) was recognized correctly: # lsdev -Cc disk hdisk1 Available Virtual SCSI Disk Drive Table Table 3-12 List of Files Inherited During an Upgrade Installation or Re-...

  • Page 111

    If you are using a virtual I/O server, see the virtual I/O server documentation to log in to AIX. If the license has expired, prepare the license key or license key file. If the license has not expired, proceed to step 3. When only the license key has been provided ¢...

  • Page 112

    # alt_disk_copy -d hdisk-name hdisk-name ... -I aXF -w DLManager.mpio.rte -l /directory-in-which-the-DVD-ROM-is- mounted/HDLM_AIX When installing HDLM onto an alternate disk from the directory to ¢ which the DVD-ROM was copied # alt_disk_copy -d hdisk-name hdisk-name ... -I aXF -w DLManager.mpio.rte -l /directory-copied-from-DVD-ROM/HDLM_AIX When installing HDLM on an alternate disk on a NIM client from a NIM ¢...

  • Page 113: Migrating From Hdlm Version 5.8.1 Or Earlier To Version 5.9 Or Later

    If HDLM Version is x.x.x-xx, the installed version of HDLM is correct. x.x.x-xx is the installed version of HDLM. From the execution result of the view operation, check that the programs are running properly. If HDLM Manager, HDLM Alert Driver, and HDLM Driver are all Alive, all programs are running correctly.

  • Page 114

    the HDLM device (dlmfdrvn) to hdisk. If the user application uses an LU managed by HDLM, modify the user application appropriately. To migrate to HDLM version 5.9 or later: 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 ¢...

  • Page 115

    Execute the following command to delete the virtual SCSI disk in the client logical partition: # rmdev -dl hdisk-name Execute the following command to delete the virtual target device in the virtual I/O server: $ rmdev -dev vtscsin Insert the DVD-ROM. If there is no directory for mounting the DVD-ROM, make the directory.

  • Page 116

    Perform steps 4 to 9 of When Installing HDLM in a Local Boot Disk Environment on page 3-24 Performing a New Installation of HDLM on page 3-24. Note that you do not have to perform steps 2 to 3. Execute the dlmmigsts utility to restore the HDLM environment settings information and the HDLM execution environment ODM settings that you saved in step 14.

  • Page 117: Installing Hdlm In A Powerha 5.5 Or Powerha 6.1 Environment

    If you performed step 5, restore the volume group you backed up. # restvg -f any-desired-file-name-or-device-name hdisk-name Check the path configuration according to the steps described in Checking the Path Configuration on page 3-67. Unmount the DVD-ROM. # umount /cdrom Delete any mount directory you may have created in step 11.

  • Page 118

    Upgrading or Re-installing HDLM in a PowerHA 5.5 or PowerHA 6.1 Environment (in a Boot Disk Environment) For details about setting up PowerHA, see the PowerHA documentation. To upgrade or re-install HDLM in an environment that uses PowerHA and a boot disk: Log in to AIX as the root user.

  • Page 119

    Start PowerHA on the standby host. When PowerHA starts, a warning message may be output, stating that the custom disk method file (/usr/DynamicLinkManager/cluster/ dlm_hacmp_gdisk_check) does not exist. This message can be ignored because it does not affect any operations. The following is an example of such a message: WARNING: Custom disk method: ghostdisks's file: /usr/DynamicLinkManager/cluster/dlm_hacmp_gdisk_check does not exist or is not executable on node: xxx...

  • Page 120

    Installing HDLM in a PowerHA 7.1 Environment In a PowerHA 7.1 environment, even if the cluster service is stopped, the cluster repository disk remains in the used state. Therefore, if you perform a new installation, upgrade installation, or re-installation of HDLM in an environment in which PowerHA 7.1 is already in use, perform the procedure below.

  • Page 121

    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 Execute the following command on the standby host to start PowerHA.

  • Page 122

    Perform the procedure described in When Installing HDLM in a Boot Disk Environment on page 3-42 Performing an Upgrade Installation or Re-installation of HDLM on page 3-35. 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: # clusterconf -r hdiskxx When the OS used in a PowerHA 7.1 environment is AIX V6.1 TL07 or...

  • Page 123

    If you copied the files on the DVD-ROM to your desired directory, proceed to step 5. 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.

  • Page 124

    The following shows examples of when the default storage directory specified in the installation information settings file is to be used: When only the license key has been provided ¢ Create the /var/DLM directory, and then, in this directory, create the license key file (dlm.lic_key).

  • Page 125

    For an upgrade installation or re-installation of HDLM, the configuration of the existing hdisks recognized as HDLM management-target devices is inherited. Unmount the DVD-ROM. # umount /cdrom Delete the created mount directory. # rm -r /cdrom Delete the installation information settings file. # rm -r /directory-containing-the-installation-information- settings-file Perform the procedure appropriate for the installation type.

  • Page 126

    # getconf BOOT_DEVICE hdisk3 In this example, hdisk3 is used for booting. If the boot physical volume that contains the logical volume hd5 is different from the physical volume used for booting, the following message appears, and the HDLM installation ends with an error: 0503-497 installp: An error occurred during bosboot test processing.

  • Page 127

    installhdlm ¢ installhdlm_analysis ¢ dlmrmdev ¢ Also, these files need to be copied to the same directory to which the installhdlm utility is copied. For a new installation, proceed to step 8. If you are upgrading or re-installing HDLM, back up the HDLM settings. If an upgrade installation or re-installation fails, AIX automatically uninstalls HDLM, and the HDLM settings are deleted.

  • Page 128

    # cp -p /cdrom/HDLM_AIX/hdlmtool/instutil/ sample_installhdlm.conf /any-directory You can change the sample_installhdlm.conf file name. The following shows an example of copying the sample_installhdlm.conf file, and then changing the file name to install_set.conf: # cp -p /cdrom/HDLM_AIX/hdlmtool/instutil/ sample_installhdlm.conf /any-directory/install_set.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...

  • Page 129: Checking The Path Configuration

    has failed. After installing HDLM, resolve the problem according to the KAPL09241-W message if necessary. When installation is successful, the KAPL09211-I message is output and the host restarts. After the host has restarted, check to make sure that the settings have been updated as specified in the installation information settings file.

  • Page 130: Setting Up Hdlm

    you install HDLM or change the hardware configuration, check the structure and statuses of the paths. To check the path information, use the dlnkmgr command's view operation. The following describes how to check path information by using the dlnkmgr command's view operation. For details about the view operation, see view (Displays Information) on page 6-30.

  • Page 131: Checking The Current Settings, Setting Up The Hdlm Functions

    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.x-xx Service Pack Version...

  • Page 132: Setting Up Load Balancing

    Function Default value Recommended value Automatic failback The recommended checking interval depends on the 60-minute check interval operating environment. Intermittent Error Monitor The recommended checking interval depends on the operating environment. Remove LU (Not specifiable) (Not specifiable) Logging level 3: Collects all the error 3: Collects all the error information for the information for the...

  • Page 133

    specify an algorithm, load balancing will still be executed by using the algorithm that was previously specified. Setting Up Path Health Checking You can choose whether you want to use path health checking. The following is an example of how to set up path health checking by using a command: # /usr/DynamicLinkManager/bin/dlnkmgr set -pchk on -intvl 10 When path health checking is enabled by specifying on for the -pchk...

  • Page 134

    Setting Up Intermittent Error Monitoring Intermittent error monitoring is specifiable only when the automatic failback function is enabled. To prevent an intermittent error from reducing I/O performance, we recommend that you monitor intermittent errors when automatic failback is enabled. When intermittent error monitoring is enabled, you can specify intermittent error conditions.

  • Page 135

    Value Description All information for errors of the "Warning" level or higher is collected. All information for errors of the "Information" level or higher is collected. All information for errors of the "Information" level or higher (including maintenance information) is collected. If an error occurs, you might have to set the error log collection level to 1 or higher to collect any log information.

  • Page 136

    might decrease, or trace information required to analyze the cause of an error might be overwritten. The following is an example of setting up the trace level by using a command: # /usr/DynamicLinkManager/bin/dlnkmgr set -systflv 1 Specify the trace level in as a number. Setting the Error Log File Size The error log file size (the HDLM manager log (dlmmgrn.log (n indicates a file number from 1 to 16))) can be set.

  • Page 137

    (KAPL01097-W) will be displayed to confirm the execution, and the trace file will be is temporarily deleted. When all the trace files become full, the oldest file is overwritten with any new trace data. By specifying both the trace file size and the number of trace files, you can collect up to 1024000KB of trace data.

  • Page 138

    Value (severity) Explanation Critical-level audit log data is collected. Critical-level and Error-level audit log data is collected. Critical-level, Error-level, and Warning-level audit log data is collected. Critical-level, Error-level, Warning-level, and Informational-level audit log data is collected. Table 3-18 Values Indicating Audit Log Data Categories on page 3-76 describes the values that indicate audit log data categories.

  • Page 139: Checking The Updated Settings

    Table 3-19 Values Indicating Audit Log Facility Value Corresponding facility value in the /etc/syslog.conf file user or 1 user local0 or 16 local0 local1 or 17 local1 local2 or 18 local2 local3 or 19 local3 local4 or 20 local4 local5 or 21 local5 local6 or 22 local6...

  • Page 140: Setting Up Integrated Traces

    Audit Log : on(6) Audit Log Category : all Audit Log Facility : local0 KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss Setting up Integrated Traces When HDLM is used, the dlnkmgr command logs are output to the integrated trace information files of Hitachi Network Objectplaza Trace Library (HNTRLib2) (/var/opt/hitachi/HNTRLib2/spool/hntr2n.log (n indicates a file number)).

  • Page 141: Displaying The Hitachi Network Objectplaza Trace Library Setup Menu

    Notes on Using the Hitachi Network Objectplaza Trace Library Note the following when using Hitachi Network Objectplaza trace library: • If HNTRLib has already been installed when you install HDLM, the settings in the trace library will not be inherited by HNTRLib2. HDLM uses the HNTRLib2 default settings.

  • Page 142: Changing The Number Of Integrated Trace Files

    To change the size of integrated trace files: 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. The current value is displayed in Current Size (KB). Enter the desired size in New Size (KB).

  • Page 143: Changing The Buffer Size Per Monitoring Interval Duration

    If you do not want to change the number of integrated trace files, leave New Number (KB) blank, type !, and then press the Enter key to return to the Hitachi Network Objectplaza Trace Library setup menu. Press the Enter key. The new setting is applied and the Hitachi Network Objectplaza Trace Library setup menu appears again.

  • Page 144: Adjusting The Number Of Messages To Be Output Per Monitoring Interval

    The specifiable range is between 1 second and 300 seconds, with a default of 10. We recommend setting a value of 5 when collecting an integrated trace. To leave the monitoring interval as is, leave New Span (sec) blank, enter ! and press the Enter key. You will be returned to the Hitachi Network Objectplaza Trace Library setup menu.

  • Page 145: Finishing The Hitachi Network Objectplaza Trace Library Settings

    Lookout span will appear. The current value is displayed in Current Max (sec). Adjust the maximum number of messages output to the integrated trace files in New Max (sec). The specifiable range is between 0 messages and 500 messages, with a default of 0.

  • Page 146: Applying The Hitachi Network Objectplaza Trace Library Settings, About The Reservation Policy

    Applying the Hitachi Network Objectplaza Trace Library Settings To apply the settings, after you change the amount of integrated trace information by using Hitachi Network Objectplaza Trace Library: Log in as a user with root permissions. Execute the following command to check the programs using HNTRLib2. In the following example, only HDLM uses HNTRLib2.

  • Page 147: Settings For Using Powerha, Storage System Settings, Setting Up A Thunder 9500v Series Device

    Setting Description • In an Oracle RAC environment, the hdisk for an HDLM-managed device is specified as a disk used by Oracle RAC • PowerHA 7.1 is used Replaces a reservation with a persistent reservation. PR_exclusive About changing the reservation policy You should check that the hdisk is not being accessed by any other ¢...

  • Page 148: Setting Up A Hitachi Ams/wms Series Device, Registering The Hdlm Script For Powerha

    Setting Up a Hitachi AMS/WMS Series Device To use a Hitachi AMS/WMS series device as a storage system, perform the setup as shown in Table 3-23 Hitachi AMS/WMS Series Setting for Using PowerHA on page 3-86. For details about how to set up a Hitachi AMS/WMS series device, see the documentation for the Hitachi AMS/WMS series.

  • Page 149: Setting The Reservation Policy

    Method to break a reserve TARGET Break reserves in parallel false Method to make the disk available MKDEV When you finish specifying the settings, click the OK button. From the SMIT window, display the Single Select List window. Choose the following sequence of menu items to display this window: Communications Applications and Services, HACMP for AIX, Extended Configuration, and finally choose Extended Verification and Synchronization.

  • Page 150: Settings For Using Gpfs, Settings For Using Oracle Rac 10g Or Oracle Rac 11g

    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 GPFS To use GPFS or GPFS+RVSD, carry out the following procedure before starting GPFS or GPFS+RVSD: To use GPFS+RVSD, add the following lines to the last line in the /etc/ vsd/oemdisktypes.lst file: When a HP XP series is used ¢...

  • Page 151

    Table 3-24 Formula for Calculating MISSCOUNT Storage system type Formula for obtaining the value of MISSCOUNT • Hitachi AMS2000/AMS/WMS/ number-of-paths-connected-to-the-voting-disk × 30 SMS series seconds • Thunder 9500V series • Hitachi USP number-of-paths-connected-to-the-voting-disk × 60 seconds • Lightning 9900V series •...

  • Page 152: Settings For Reservation Policy, Settings For Using Vcs

    Settings for Reservation Policy When you set up an Oracle RAC environment, if you specify the hdisk for an HDLM-managed device as a disk used by Oracle RAC, use the procedure below to check the value of the reserve_policy attribute. If reserve_policy is set to PR_exclusive, change its value to no_reserve.

  • Page 153: Uninstalling Hdlm, Preparations For Hdlm Uninstallation

    # haconf -makerw # hagrp -modify service-group PreOnline 1 # haconf -dump -makero # cp -r /opt/VRTSvcs/bin/sample_triggers/preonline /opt/VRTSvcs/ bin/triggers In the preonline script used when VCS starts, register the script provided by HDLM. Add the following code to the line under # put your code here... in the preonline script.

  • Page 154: When Uninstalling Hdlm In A Local Boot Disk Environment, Uninstalling Hdlm

    • When uninstalling HDLM on a host where version 5.0 or later of a Device Manager agent is installed, do not execute any of the following Device Manager agent commands during the uninstallation. Also, do not uninstall HDLM while executing any of the following Device Manager agent commands: hbsasrv, HiScan, hdvmagt_account, hdvmagt_schedule, hldutil, TIC Uninstalling HDLM...

  • Page 155

    # reducevg -df volume-group-name hdisk-name Execute the following command to delete the virtual SCSI disk in the client logical partition: # rmdev -dl hdisk-name Execute the following command to delete the virtual target device on the virtual I/O server: $ rmdev -dev vtscsin Stop all processes and services that use the HDLM management-target paths.

  • Page 156

    If the KAPL09012-I message is not displayed, the HDLM driver has not been deleted, or the HDLM manager has not stopped. Make sure that no process, service, file system, or volume group is using the HDLM management-target path, and then re-execute the above command. Execute the following command to make sure that the hdisks recognized as the devices to be managed by HDLM have been deleted: # lsdev -Cc disk...

  • Page 157: When Uninstalling Hdlm In The Boot Disk Environment

    If the KAPL09022-E message is displayed, the hdisks recognized as the devices to be managed by HDLM still remain. Re-execute the procedure starting from step 14. If you are using a virtual I/O server, define an hdisk as a virtual target device.

  • Page 158

    Execute the following command to unmount the file system in the client logical partition: # umount file-system-mount-point Execute the following command to delete the volume group in the client logical partition: # reducevg -df volume-group-name hdisk-name Execute the following command to delete the virtual SCSI disk in the client logical partition: # rmdev -dl hdisk-name Execute the following command to delete the virtual target device in the...

  • Page 159

    # /usr/DynamicLinkManager/bin/dlmpreuninst If you execute the dlmpreuninst utility, the hdisk recognized as a boot disk stops being the HDLM's management target. When the command terminates normally, the following message appears: KAPL13103-I HDLM can be uninstalled after rebooting the host. KAPL13101-I The dlmpreuninst utility completed successfully. If the KAPL13108-E message is displayed, the hdisk for the device that is managed by HDLM still remains.

  • Page 160: Uninstalling Hitachi Network Objectplaza Trace Library (hntrlib2)

    # hagrp -modify service-group PreOnline 0 # haconf -dump -makero Execute the following command: # installp -u DLManager.mpio Change the boot device list, according to the host environment you are using. If you are not using a virtual I/O server, uninstallation of HDLM is complete and you do not need to perform the remaining steps.

  • Page 161: Uninstalling Hitachi Network Objectplaza Trace Library (hntrlib)

    # /opt/hitachi/HNTRLib2/etc/hntr2setup The HNTRLib2 setup menu will appear. From the Setup menu, select 9. HNTRLib2 will be uninstalled. If HNTRLib2 is not being used by any other programs: HNTRLib2 will be uninstalled normally, and the following message will appear. Unsetup is complete. If HNTRLib2 is being used by another program: HNTRLib2 will not be uninstalled, and the following message will appear.

  • Page 162: Canceling Cluster Software (powerha) Settings

    Shared library files (symbolic links) ¢ /opt/hitachi/common/lib/libhntr* Directory that contains shared library files ¢ /opt/hitachi/common/lib/D001 If the /opt/hitachi directory only contains the files and directories shown above, delete the directory. Note If the log output directory set in HNTRLib was not the default ¢...

  • Page 163: Hdlm Operation

    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 different for HDLM 5.8.1 or earlier and HDLM 5.9 or later.

  • Page 164: Notes On Using Hdlm, Displaying Path Information, When A Path Error Is Detected

    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.

  • Page 165: Storage System, Notes On Shutting Down A Host, Notes On Errors In A Host

    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. •...

  • Page 166: Same Server, Notes On An Lvm Mirror Configuration

    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: Create a pair of the primary volume and the secondary volume (paircreate).

  • Page 167: Notes On Replicating A System, Hdlm Operations Using Commands, Notes On Using Commands

    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 HDLM- managed devices.

  • Page 168: Changing The Status Of Paths To Online

    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.

  • Page 169: Changing The Status Of Paths To Offline(c)

    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.

  • Page 170: Viewing Lu Information

    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.

  • Page 171: Initializing Statistical Information For Paths

    operation, see view (Displays Information) on page 6-30. 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...

  • Page 172: Viewing And Setting Up The Operating Environment, Viewing The Operating Environment

    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...

  • Page 173: Viewing License Information, Updating The License

    • 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 For details on how to set up each function, see set (Sets Up the Operating Environment) on page 6-16.

  • Page 174: Viewing Hdlm Version Information

    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.

  • Page 175: Viewing Hdlm Component Information

    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. Viewing HDLM Component Information This section explains how to display HDLM component information. To display HDLM component information, execute the dlnkmgr command's view operation with the -sys parameter specified.

  • Page 176: Starting And Stopping The Hdlm Manager, Starting The Hdlm Manager, Stopping The Hdlm Manager

    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.

  • Page 177: Hdlm Resident Processes, Changing The Configuration Of The Hdlm Operating Environment

    When the HDLM Manager column shows Dead, the HDLM manager is inactive. HDLM Resident Processes Table 4-1 HDLM resident processes on page 4-15 lists and describes the resident processes in HDLM. To monitor these processes, use the names below. Table 4-1 HDLM resident processes Process Description HDLM manager process...

  • Page 178: Changing An Hdlm Management-target Device, Changing Hdisk Attributes

    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 Execute the following command to delete the device (or devices): To delete all devices ¢ # /usr/DynamicLinkManager/bin/dlmrmdev To delete a specific device ¢...

  • Page 179: Automatically Performing Hdisk Reconfiguration

    To change attribute values for an individual hdisk, use the chdev command instead of the dlmchpdattr utility to change the values actually used. The following explains how to use the dlmchpdattr utility to change default hdisk values, and apply them as the actually used values. If you execute the dlmchpdattr utility with the -A parameter specified, after the default values are changed, hdisks will be automatically reconfigured.

  • Page 180: Manually Performing Hdisk Reconfiguration

    hdisk1 Available 1S-08-00-9,0 16 Bit LVD SCSI Disk Drive hdisk2 Available 1S-08-00-10,0 16 Bit LVD SCSI Disk Drive hdisk3 Available 1H-08-02 Hitachi Disk Array (Fibre) hdisk4 Available 1H-08-02 Hitachi Disk Array (Fibre) In this example, hdisk3 and hdisk4 are recognized as HDLM-managed devices.

  • Page 181

    For details on the dlmrmdev utility, see dlmrmdev Utility for Deleting HDLM Drivers on page 7-25. If the command terminates normally, the KAPL10531-I message is displayed. If the KAPL10531-I message is not displayed, make sure that HDLM- managed paths are not being used by a process, service, file system, or volume group, and then perform step 2 again.

  • Page 182

    Execute the dlmchpdattr utility with the -o parameter specified. # /usr/DynamicLinkManager/bin/dlmchpdattr -o uniquetype = disk/fcp/Hitachi reserve_policy : no_reserve KAPL10571-I The dlmchpdattr utility completed successfully. Perform the following according to the execution environment: If the execution environment is a local boot disk environment: ¢...

  • Page 183: Changing A Path, Adding A Path (to A Volume Group Other Than Rootvg)

    # lsattr -El hdisk-name | grep reserve_policy reserve_policy no_reserve Reserve Policy TRUE Activate the volume group used by HDLM. # varyonvg volume-group-name Mount the file system used by HDLM. # mount file-system-mount-point Changing a Path This subsection explains how to add and delete paths. Adding a Path (to a Volume Group Other than rootvg) Connect the path to the system and execute the following command: # cfgmgr...

  • Page 184: Deleting A Path (of A Volume Group Other Than Rootvg)

    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. 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.

  • Page 185: Deleting A Path (of A Device Included In Rootvg), Replacing An Hba

    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. 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...

  • Page 186

    # /usr/DynamicLinkManager/bin/dlmodmset -o The following are execution examples: Lun Reset : off Online(E) IO Block : on NPIV Option : off Check the NPIV Option line. Place in Offline (C) status the path that goes through the HBA to be replaced.

  • Page 187

    Choose Hot Plug Task. The Hot Plug Task window appears. Choose PCI Hot Plug Manager. The PCI Hot Plug Manager window appears. Select List PCI Hot Plug Slots to check the PCI slot to be replaced: The shading indicates the PCI slot where the HBA is to be replaced. Go back to the PCI Hot Plug Manager window, select Unconfigure a Device, and enter in Device name the device that is to be replaced.

  • Page 188

    If LUN security has been set up for the storage system, delete the WWN of the previous HBA from the LUN security. 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-30.

  • Page 189

    For details on path information, see view (Displays Information) on page 6-30. Execute the utility for clearing HDLM persistent reservation (dlmpr) to clear the reservation of LUs comprising the applicable volume group: # /usr/DynamicLinkManager/bin/dlmpr -c hdisk-name hdisk- name ... Execute the following command to activate the applicable volume group: # varyonvg volume-group-name •...

  • Page 190: Replacing A Fiber Cable

    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.

  • Page 191: Replacing A Fibre Channel Switch

    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.

  • Page 192

    # /usr/DynamicLinkManager/bin/dlmodmset -o The following are execution examples: Lun Reset : off Online(E) IO Block : on NPIV Option : off Check the NPIV Option line. Place in Offline (C) status the path that goes through the Fibre Channel switch to be replaced. Depending on the NPIV option setting for the dlmodmset utility checked in step 2, execute one of the following commands: If the NPIV option is set to off:...

  • Page 193

    fcsn indicates the name of the parent device that was acquired in step 5; n indicates the instance number of the fcs device. 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-30.

  • Page 194

    4-32 HDLM Operation Hitachi Dynamic Link Manager User Guide (for AIX(R))

  • Page 195: Troubleshooting

    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. □...

  • Page 196: Information Collected By The Dlmgetras Utility For Collecting Hdlm Error Information

    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.

  • Page 197

    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. A path name consists of the following four elements, separated by periods: HBA adapter number or adapter type (character string) ¢...

  • Page 198

    Figure 5-1 Error location when the KAPL08022-E message is output Figure 5-2 Troubleshooting procedure when a path error occurs on page 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.

  • Page 199: Examining The Messages, Narrowing Down The Hardware That Might Have Caused The 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.

  • Page 200: What To Do For A Program Error

    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.

  • Page 201: What To Do For The Program Error, Contacting Your Hdlm Vendor Or Maintenance Company

    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.

  • Page 202

    Troubleshooting Hitachi Dynamic Link Manager User Guide (for AIX(R))

  • Page 203: Command Reference

    Command Reference This chapter describes the HDLM command (dlnkmgr) and its operations. □ Overview of the HDLM Command dlnkmgr □ clear (Returns the Path Statistics to the Initial Value) □ help (Displays the Operation Format) □ offline (Places Paths Offline) □...

  • Page 204: Overview Of The Hdlm Command Dlnkmgr

    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.

  • Page 205: To Set The Path Statistics To 0, To Display The Format Of The Clear Operation

    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. Format To Set the Path Statistics to 0 /usr/DynamicLinkManager/bin/dlnkmgr clear -pdst [-s] To Display the Format of the Clear Operation /usr/DynamicLinkManager/bin/dlnkmgr clear -help...

  • Page 206

    # /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.

  • Page 207

    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.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...

  • Page 208: To Place Paths Offline, To Display The Format Of The Offline Operation, Parameters

    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.

  • Page 209

    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-adapter- number.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.

  • Page 210

    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.

  • Page 211

    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.

  • Page 212: To Display The Format Of The Offline Operation

    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.

  • Page 213: To Place Paths Online

    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-30. 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.

  • Page 214: To Display The Format Of The Online Operation, Parameters, To Place Paths Online

    [-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.

  • Page 215

    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. To display the HBA port IDs, execute the following view operation: # /usr/DynamicLinkManager/bin/dlnkmgr view -hba For details about how to execute the view operation to display the HBA...

  • Page 216

    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.

  • Page 217

    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-49 Parameters on page 6-32.

  • Page 218

    { -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...

  • Page 219: To Set Up The Hdlm Operating Environment, To Display The Format Of The Set Operation

    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 {on [-audlv audit-log-data-collection-level] [-category [[ss] [a] [ca]|all]]|off}...

  • Page 220

    Item name Default value Recommended value Number of error log files 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 Path health on (Interval is 30 minutes.) checking The recommended checking interval depends on the operating...

  • Page 221

    -ellv error-log-collection-level Specify the level of error information you want to collect for an error log. The HDLM manager log (dlmmgr[1-16].log) contains log files in which an error log collection level can be set. Table 6-3 Values of the Error Logging Level on page 6-19 shows the values of the error logging level.

  • Page 222

    Specify the trace output level. The trace files for which trace levels can be set are hdlmtrn.log (n indicates a file number from 1 to 64). Table 6-4 Trace Level Values on page 6-20 shows the values of the trace level.

  • Page 223

    Enables or disables path health checking. on: Enabled off: Disabled For a standby host, or a host connected to the Thunder 9500V series, or Hitachi AMS/WMS series storage system, we recommend that you activate path health checking so that you can detect errors in paths where I/Os operations do not occur.

  • Page 224

    Path where an error occurred during the startup of the HDLM ¢ manager. To prevent intermittent errors from deteriorating I/O performance, we recommend that you also enable intermittent error monitoring when the automatic failback function is enabled. Intermittent error monitoring is specifiable only when automatic failbacks are enabled.

  • Page 225

    -iem { on [-intvl error-monitoring-interval] [-iemnum number-of-times- error-is-to-occur] | off } Enables or disables intermittent error monitoring. on: Enabled off: Disabled Intermittent error monitoring can be enabled only when automatic failback is set to on. When you use automatic failback, we recommend that you set intermittent error monitoring to on to prevent an intermittent error from reducing I/O performance.

  • Page 226

    number of times that an error is to occur, the error count and the elapsed time measured since monitoring has started are reset to 0. When intermittent error monitoring is not being performed, if changes are made in the settings of the intermittent error monitoring interval or the number of times that an error is to occur, the new settings will take effect after the next time an automatic failback is successful.

  • Page 227

    Table 6-5 Relationship Between the Setting for the Automatic Failback Function and Intermittent Error Monitoring and the Executable Operations on page 6-25 shows the relationship between the settings for the automatic failback function and intermittent error monitoring and the executable operations for those functions. Table 6-5 Relationship Between the Setting for the Automatic Failback Function and Intermittent Error Monitoring and the Executable Operations Setting...

  • Page 228

    Setting Available operation Result of operation Set IEM to on. IEM is enabled. Set AFB to on. AFB and IEM are enabled. Set AFB to off. The operations of AFB and IEM do not change. Set AFB to on. AFB is enabled. Set AFB to off.

  • Page 229

    When the set -lic operation is executed, a message (KAPL01068-I) asking the user to enter a license key appears. Enter the license key. A message confirming that the license key has been registered is displayed, depending on the license key type described in the license key file.

  • Page 230

    on: Audit log data is collected. off: Audit log data is not collected. -audlv audit-log-data-collection-level Specifies the severity level of audit log data to be collected. Table 6-7 Values Indicating Audit Log Data Collection Levels on page 6-28 describes the values that indicate audit log data collection levels. The default is 6.

  • Page 231: To Display The Format Of The Set Operation

    Table 6-9 Values of the Audit Log Facility Value Corresponding facility value in the /etc/syslog.conf file user or 1 user local0 or 16 local0 local1 or 17 local1 local2 or 18 local2 local3 or 19 local3 local4 or 20 local4 local5 or 21 local5 local6 or 22...

  • Page 232

    | -lic | -audlog on [ -audlv AudlogLevel ] [ -category Category-Value ] | -audlog off | -audfac { Facility-Name | Facility-Number } [-s] Valid value ElogLevel { 0 | 1 | 2 | 3 | 4 } (Default Value 3) ElogFileSize { 100 - 2000000 }(KB) (Default Value 9900)

  • Page 233: To Display Program Information, To Display Path Information, To Display Lu Information

    Format To Display Program Information /usr/DynamicLinkManager/bin/dlnkmgr view -sys [-sfunc|-msrv|-adrv|-pdrv|-lic|-audlog] [-t] To Display Path Information To display path information /usr/DynamicLinkManager/bin/dlnkmgr view -path [-hdev host-device-name] [-stname] [-iem] [-srt {pn|lu|cp}] [-hbaportwwn] [-t] To display path information (by selecting a display item) /usr/DynamicLinkManager/bin/dlnkmgr view -path -item [pn] [dn] [lu] [cp] [type] [ic] [ie] [dnu] [hd] [iep] [hbaportwwn] [-hdev host-device-name]...

  • Page 234: To Display Hba Port Information, To Display Cha Port Information

    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] | all ] [-hdev host-device-name | -pathid AutoPATH_ID] [-t] To display a summary of LU information /usr/DynamicLinkManager/bin/dlnkmgr view -lu -c [-t] To display a summary of LU information (by adding items to be displayed)

  • Page 235

    To Display the Format of the View Operation on page 6-61 To Display Program Information -sys [-sfunc|-msrv|-adrv|-pdrv|-lic|-audlog] Displays the HDLM program information. Use one of the sub-parameters (following -sys) to specify the program information that you want to display. If you do not specify a sub- parameter, the command displays all of the program information except the information about audit log data collection settings.

  • Page 236

    Parameter program Item Description informatio n to be displayed Error logging level: Elog Level • 0: Collects no error information. • 1: Collects error information at the Error level or higher. • 2: Collects error information at the Warning level or higher. •...

  • Page 237

    Parameter program Item Description informatio n to be displayed When the setting of the automatic failback is on, the checking interval of automatic failback is displayed within the parentheses following on. The time is in minutes. • Setting for intermittent error monitoring Intermittent Error Monitor on: Enabled...

  • Page 238

    Parameter program Item Description informatio n to be displayed License type -lic License Type Information • Permanent: permanent license about the • Temporary: temporary license HDLM • Emergency: emergency license license License expiration Expiration When using a permanent license: - When using a temporary license or emergency license: The license expiration period is displayed in the format: yyyy/mm/dd (ndays after).

  • Page 239

    When you use cluster software, the settings of the cluster support function and the product name of the cluster software is not displayed. However, the cluster support function will operate normally. Examples Example 1 The following example shows how to display information about the HDLM function settings: # /usr/DynamicLinkManager/bin/dlnkmgr view -sys -sfunc HDLM Version...

  • Page 240: To Display Path Information

    The following example shows how to display information about the HDLM driver. # /usr/DynamicLinkManager/bin/dlnkmgr view -sys -pdrv HDLM Driver 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 5 The following example shows how to display information about the HDLM license.

  • Page 241

    AutoPATH_IDs displayed by the -path parameter depend on the sequence in which HDLM detects the paths after when a host is started up. Because of this, make sure that you use the path name PathName to identify a path. The sub-parameters are as follows: -hdev host-device-name Displays information only for the paths accessing the specified host device.

  • Page 242

    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.

  • Page 243

    Because both PathID and Status are always displayed, you do not have to specify any parameters. In the sub-parameters following -path -item, you can list the paths (- hdev) and sort the list (-srt). If you omit both parameters, the command displays information for all the paths in ascending order of AutoPATH_IDs.

  • Page 244

    Example In the following example, IO-Count is selected as the display item and the path information is sorted in ascending order by LUs. 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.

  • Page 245

    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 about product IDs, see Table 6-14 Product ID Displayed by the View -Path Operation on page...

  • Page 246

    • No summary displayed: The user specifies only the -path parameter or the-path -item parameter. • Summary displayed: The user specifies the -path -c parameter. Table 6-12 Displayed Path Information Displayed Item Description Summary summary displayed displayed Total number of displayed paths, indicated by a decimal (i.e., Paths base 10) number.

  • Page 247

    Displayed Item Description Summary summary displayed displayed For details about each element of the path name and its representation in AIX, see Table 6-13 Elements of a Path Name on page 6-47. Storage system name, which identifies the storage system that DskName DskName is accessed by a path.

  • Page 248

    Displayed Item Description Summary summary displayed displayed Status of the path Status • 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 Online status, one of those paths is changed to the Online(E) status.) Paths that are Offline(E) or Online(E) require corrective...

  • Page 249

    Displayed Item Description Summary summary displayed displayed This item is displayed only when you specify -iem with the - path parameter. 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.

  • Page 250

    Corresponding Element AIX representation information Target ID (example: Target ID The value of scsi_id, which 00000000000000E2) is displayed by executing the lsattr -El hdisk-name command Host LU number(example: Logical unit ID or LUN The value of lun_id, which 0001) is displayed by executing the lsattr -El hdisk-name command This element is applied when the NPIV option is set to off for the...

  • Page 251: To Display Lu Information

    Product ID With the -stname Model names of storage Without the -stname parameter systems parameter (Displays the following for the model name) Hitachi Virtual Storage Platform P9500 P9500 HP XP128 XP128 HP XP1024 XP1024 HP XP10000 XP10000 HP XP12000 XP12000 HP XP20000 XP20000 HP XP24000...

  • Page 252

    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. Omits the title for each information item.

  • Page 253

    Table 6-15 Items That Can Be Added by Using the -lu -item Parameter and Sub-parameters on page 6-51 lists the items that can be added by using the -item parameter and the parameters that can be specified after the -item parameter. Table 6-15 Items That Can Be Added by Using the -lu -item Parameter and Sub-parameters Item that can be added...

  • Page 254

    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.

  • Page 255

    The following example shows how to display a summary of the LU information (without selecting items to be displayed): # /usr/DynamicLinkManager/bin/dlnkmgr view -lu -c Product LUs iLU HDevName Paths OnlinePaths 0014010 003A hdisk0 003B hdisk1 003C hdisk2 003D hdisk3 003E hdisk4 003F hdisk5 0040 hdisk6 0041 hdisk7...

  • Page 256

    Displayed LU information Table 6-17 Displayed LU Information on page 6-54 describes the displayed LU information. The following explains the table headings: • No summary displayed: The user specifies the -lu parameter or -lu - item parameter. • Summary displayed: The user specifies the -lu -c parameter or -lu -c - item parameter.

  • Page 257

    Displayed item Description No summary Summary displayed displayed within the CU. The first character of the CU number is the value 0. • For the Thunder 9500V series, or Hitachi AMS2000/AMS/WMS/SMS series, indicated by a decimal number. The entire value of iLU is the internal LU number within the storage system.

  • Page 258

    Displayed item Description No summary Summary displayed displayed You can identify an actual CHA port by referencing this number from the storage system management program. The number of the CLPR to which the CHA port CLPR belongs, indicated by a decimal number from 0 to 31.

  • Page 259

    Displayed item Description No summary Summary displayed displayed the maximum value, it is reset, and the count is re- started from 0. To reset the IO-Errors value to 0, execute the dlnkmgr command's clear operation. Executing the clear operation also clears the number of I/O operations (IO-Count) to 0.

  • Page 260

    - The user selected the item to be displayed by using the -lu -item parameter. - all was specified. - No value was specified for the parameter. This information is displayed when one of the following conditions exist: - The user selected the item to be displayed by using the -lu -c -item parameter.

  • Page 261: To Display Cha Port Information

    Example # /usr/DynamicLinkManager/bin/dlnkmgr view -hba HbaID Port.Bus IO-Count IO-Errors Paths OnlinePaths 00000 08.11 71520 00001 08.1D 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).

  • Page 262

    Item Description Number of online paths in the displayed paths, indicated by a OnlinePaths decimal number. When the value of Paths equals the value of OnlinePaths, all paths are online. If the value of OnlinePaths is less than that of Paths, some paths are offline. In this case, you should check the offline paths and take appropriate action for any path that has an error status.

  • Page 263: To Display The Format Of The View Operation

    Table 6-20 Items Displayed as the Correspondences Between hdisks, OS Management Path IDs, and LDEVs Item Description AutoPATH_ID indicated by a decimal number. PathID AutoPATH_ID is assigned when the host is restarted or when a path configuration is changed. When a new LU was added and the host has not been restarted, AutoPATH_ID is assigned to each path of the LU, AutoPATH_ID is assigned when you execute the cfgmgr...

  • Page 264

    -item [pn] [dn] [lu] [cp] [type] [ic] [ie] [dnu] [hd] [iep] [hbaportwwn] [ -hdev HostDeviceName ] [-stname] [-srt {pn | lu | cp}] [-t] dlnkmgr view -path -c [-stname] [-srt {lu | cp}] [-t] dlnkmgr view -lu [ -hdev HostDeviceName | -pathid AutoPATH_ID ] [-t] dlnkmgr view -lu -item [ [slpr] [vg] [pn] [cp] [clpr] [type]...

  • Page 265: Utility Reference

    Utility Reference This chapter explains the utilities used by HDLM. □ Overview of the Utilities □ DLMgetras Utility for Collecting HDLM Error Information □ dlmchpdattr Utility for Changing HDLM Default Settings □ dlmgetrasinst Utility for Collecting HDLM Installation Error Information □...

  • Page 266: Overview Of The Utilities

    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...

  • Page 267

    about the dlmpr utility, see dlmpr Utility for Clearing HDLM Persistent Reservation on page 7-22. • The dlmpreuninst utility executed before uninstalling HDLM This utility excludes the hdisk recognized as a boot disk from being an HDLM management target. Execute this utility before uninstalling HDLM. For details about the dlmpreuninst utility, see dlmpreuninst Utility for Executed Before Uninstalling HDLM on page...

  • Page 268: Dlmgetras Utility For Collecting Hdlm Error Information

    Table 7-1 Examples of the Starting Time of the Host and the Execution Time of the Utilities Number of paths for an LU/ Total Operation #1, #3 Execution time number of paths Execution time of the device 4/1024 42 seconds configuration on starting the host 8/2048 42 seconds...

  • Page 269: List Of Collected Error Information, Format

    collected information is archived in a file and saved to the directory that you specified. The following files are output: • Name-of-the-directory-containing-a-system-crash-dump-file/system- crash-dump-file This file contains a symbolic link to the system crash dump file. • hbsa.tar.Z This file contains compressed error information of the Hitachi Command Suite products other than HDLM.

  • Page 270

    Figure 7-1 Coding Example of a File that Defines the Information to be Collected on page 7-6 shows an example of the coding in this file. 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 •...

  • Page 271

    entering y instructs the DLMgetras utility to overwrite the existing files; entering n (or anything other than y) instructs the utility to terminate without executing. In the latter case, you can either rename the existing directory before re- executing the utility, or you can execute the utility with a different directory name specified.

  • Page 272

    Files Explanation Output directory Hitachi Command Suite Common dlmwebagent[1-16].l Agent Component log files Inquiry log dlminquiry[1-2].log dlminquiry[1-2].txt Installation linkage script log used dlmguiinst.log when linking with Hitachi Command Suite products other than HDLM Trace file hdlmtr[1-64].log HDLM configuration log dlmconfig[1-2].log dlmconfig[1-2].txt HDLM utility's log file dlmutil[1-2].log...

  • Page 273

    Files Explanation Output directory error-log-file error-log-file Error log file obtained by /usr/ lib/errdemon -1 syslog-output-directory- syslog-name syslog files and backup files name defined in /etc/syslog.conf (Not applicable) Directory in which command getrasinfo execution results are stored Default history file in the Bourne .bash_history Again shell (bash) Default history file in the C shell...

  • Page 274

    Files Explanation Output directory HDLM LU information (including the dlmmgr-lu-all.txt number of times an intermittent error occurred) HDLM path information dlmmgr-path.txt dlmmgr-path-iem.txt HDLM path information (including the number of times an intermittent error occurred) HDLM system settings dlmmgr-sys.txt HDLM execution environment ODM dlmodmset.txt settings Persistent reservation key...

  • Page 275

    Files Explanation Output directory Information of Object Database PdPathAt.txt Manager Information of Object Database PdDv.txt Manager Information on the executing ps-ef.txt process Limits on system resources (data ulimit-a.txt segments, stack segments, file descriptors) that are available to processes Information on the AIX version uname-a.txt Information output by the what whatlist.txt...

  • Page 276

    • When the chdev command is used to set as defined, and then reconfigure, an existing individual hdisk for which the attribute value has not changed. • When deleting an existing hdisk , and then reconfiguring it. When an hdisk for which the attribute value has been defined is reconfigured without being deleted, the set attribute value is carried over.

  • Page 277

    Attribute names that can be Values that can be specified specified in dlmchpdattr no_reserve: Reservation requests are ignored, and LUs are not reserved. PR_exclusive: Reservations are converted to persistent reservations. The default is PR_exclusive. Specifies the maximum size of data that can be max_transfer transferred to the disk.

  • Page 278

    • 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. • If you cancel the execution of the dlmchpdattr utility by pressing Ctrl + C, the KAPL10571-I message might be output depending on the timing of the cancellation.

  • Page 279

    Format DVD-ROM-drive-directory/HDLM_AIX/hdlmtool/dlmgetrasinst {directory- to-which-collected-information-is-output | -h} Parameters directory-to-which-collected-information-is-output Specify the output directory for the information that is to be collected by the dlmgetrasinst utility for collecting HDLM installation error information. The collected information is compiled into two files shown in Function and output in the specified directory.

  • Page 280

    Files Explanation Output directory File for defining the directory for syslog.conf the output destination of syslog Hitachi Command Suite Common HBaseAgent_install. Agent Component installation log files syslog-output-directory- syslog-name syslog files and backup files name defined in /etc/syslog.conf (Not applicable) Directory in which command getrasinfo execution results are stored Default history file in the Bourne...

  • Page 281

    Files Explanation Output directory CPU information lsdev-proc.txt File system information lsfs.txt List of installed packages lslpp.txt MPIO path information lspath.txt Swap area, usage of swap lsps-a.txt Physical volume information lspv.txt Information of volume groups lsvg.txt Maintenance level of information, Maintenance- displayed when the instfix -i Level.txt command was executed...

  • Page 282

    • When HDLM is installed, the KAPL09241-W message is output Execute this utility after installing the JDK. For details about the JDK version to be installed, see the JDK required for linkage with Global Link Manager section in Host and OS Support for HDLM on page 3-3.

  • Page 283

    /opt/hitachi • Make sure you have write permission for odm-environment- settings-file, set-environment-settings-file, and the storage directory before executing. • Do not change the contents of the saved odm-environment- settings-file and set-environment-settings-file. Restores the settings files by using the names specified in the -odm and - set parameters.

  • Page 284

    dlmodmset Utility for Setting the HDLM Execution Environment ODM This utility sets ODM to define HDLM operations. Format /usr/DynamicLinkManager/bin/dlmodmset {{-r {on | off} | -i {on | off } | -v {on | off }} [-s] | -h | -o } Parameters -r { on | off } Enables or disables the LUN RESET option.

  • Page 285

    off: Disable The default is off. To use HDLM in a client partition to which a virtual HBA is applied by using the NPIV functionality of the virtual I/O server, specify on. For details, see Notes on the Virtual I/O Server on page 3-13.

  • Page 286: Dlmpr Utility For Clearing Hdlm Persistent Reservation

    Parameters Suppresses display of a confirmation message when the utility executes. Displays the format of the dlmpostrestore utility. Notes • When the dlmpostrestore utility is executed in a local boot disk environment, the devices are reconfigured; when the utility is executed in a boot disk environment, the host is restarted.

  • Page 287

    Specify this parameter to clear the Reservation Key. Note • Do not use the -c parameter during normal operation. Once the Reservation Key is cleared, the hdisk can be accessed from other hosts, which may lead to data corruption. Use the -c parameter only when you need to clear a Reservation Key that was improperly retained.

  • Page 288

    hdisk5 Reservation Key : [0xbbbbbbbbbbbbbbbb]*, reserve_policy : no_reserve Regist Key : [0xbbbbbbbbbbbbbbbb] , Key Count : 4 hdisk6 Reservation Key : [0x0000000000000000] , reserve_policy : single_path Regist Key : [0xcccccccccccccccc] , Key Count : 4 hdisk7 Reservation Key : [0x????????????????] , reserve_policy : - KAPL10665-I The dlmpr utility completed.

  • Page 289

    # /usr/DynamicLinkManager/bin/dlmpreuninst -s KAPL13103-I HDLM can be uninstalled after rebooting the host. KAPL13101-I The dlmpreuninst utility completed successfully. In the following example, the utility displays Help: # /usr/DynamicLinkManager/bin/dlmpreuninst -h Usage : dlmpreuninst [-h | -s] dlmrmdev Utility for Deleting HDLM Drivers This utility deletes hdisks or changes the status of hdisks to Defined according to the parameter settings.

  • Page 290: Installhdlm Utility For Installing Hdlm

    stopping the processes and services that are using the paths managed by HDLM, hdisks recognized as HDLM management-target devices might not be deleted completely or changed to the Defined status Examples In the following example, the utility unmounts the file system used by HDLM, inactivates the volume group used by HDLM, and deletes all the hdisks recognized as HDLM management-target devices: # /usr/DynamicLinkManager/bin/dlmrmdev -A...

  • Page 291

    Items To Be Defined in an installation-information Settings File The following describes the information defined in the installation information settings file. [INSTALLATION_SETTINGS] section This section defines information that is used when the installhdlm utility is executed. Specify this section name at the beginning of the installation information settings file (although an empty paragraph or comment line can be inserted above this section name).

  • Page 292

    Necessity of Maxim definition Upgrade number Key name Description installatio installa n or re- charact tion installatio Specify the absolute path name Optional Optional licensekey of the file that records the license key stored on the host. The file specified here is not deleted after an unattended installation is performed.

  • Page 293

    You need to delete the licensekeyfile key if you specify the licensekey key. However, you do not need to delete the licensekey key if you specify the licensekeyfile key. If no value is specified for either of these keys, the files below are read in the order listed: License key file (/var/tmp/hdlm_license) File containing the license key (/var/DLM/dlm.lic_key)

  • Page 294

    Optional: If a key and its setting are not specified, one of the following values will be used: For a new installation: ¢ The default value will be used. For an upgrade installation or re-installation: ¢ The previous setting will be inherited. Enter one key and one setting per line.

  • Page 295

    Necessity of Maxim definition Upgrade number Key name Description installatio installa n or re- charact tion installatio enable or disable the NPIV option: on: Enabled off: Disabled (default) Legend: Optional: If a key and its setting are not specified, one of the following values will be used: For a new installation: ¢...

  • Page 296

    Table 7-8 Keys in the [ENVIRONMENT_SETTINGS] Section Necessity of definition Maxim Upgrad numbe Key name Description installa r of installa tion or charac tion ters installa tion Specify one of the following values Optional Optional 3 load_balance to indicate whether to enable or disable the load balancing function: on: Enabled (default) off: Disabled...

  • Page 297

    Necessity of definition Maxim Upgrad numbe Key name Description installa r of installa tion or charac tion ters installa tion You can set a size from 100 to 16000. The default is 1000. Set the number of trace files Optional Optional 2 trace_file_number (hdlmtr[1-64].log).

  • Page 298

    Necessity of definition Maxim Upgrad numbe Key name Description installa r of installa tion or charac tion ters installa tion You can specify a check interval from 1 to 1440. The default is 210. Specify the number of times an Optional Optional 2 intermittent_error error (that is assumed to be an...

  • Page 299: Log File

    If you want to enable intermittent error monitoring, specify this key after specifying the auto_failback and auto_failback_interval keys. 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.lic_key driver_config=y restart=n [DISK_DEFAULT_SETTINGS] reserve_policy=PR_exclusive [ODM_SETTINGS] odm_lun_reset=off odm_online_e_io_block=off odm_npiv_option=off...

  • Page 300

    • If installhdlm.log already exists, log information is added to this log file. For details about the unused capacity required for the log output directory, see Performing an Unattended Installation of HDLM on page 3-60. Note • Note that installhdlm.log is not deleted after HDLM is uninstalled. Therefore, delete the original installhdlm.log manually if it is no longer required.

  • Page 301

    file is created and named hdlm_installux_sh.log, to which the execution information is output. Note The hdlm_installux_sh.log and hdlm_installux_sh2.log log files are not deleted when HDLM is uninstalled. Manually delete the log files, if they are no longer required. 7-37 Utility Reference Hitachi Dynamic Link Manager User Guide (for AIX(R))

  • Page 302

    7-38 Utility Reference Hitachi Dynamic Link Manager User Guide (for AIX(R))

  • Page 303: Messages

    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...

  • Page 304

    □ Return Codes for Hitachi Command Suite Common Agent Component Messages Hitachi Dynamic Link Manager User Guide (for AIX(R))

  • Page 305: Before Viewing The List Of Messages, Format And Meaning Of Message Ids

    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 •...

  • Page 306: Kapl01001 To Kapl02000, Kapl01001 To Kapl

    • HDLM manager • HDLM driver (filter component) • HDLM alert driver • HDLM management target KAPL01001 to KAPL02000 Message Message Text Explanation KAPL01001- The HDLM command completed normally. Details Operation name = aa...aa, completion The HDLM command time = bb...bb completed successfully.

  • Page 307

    Message Message Text Explanation aa...aa: clear, set, online, offline, or view bb...bb: Specified parameter Action Execute help operation- name of the HDLM command (dlnkmgr) to check the parameter, and then retry. For details on the help operation, see help (Displays the Operation Format) on page 6-4.

  • Page 308

    Message Message Text Explanation KAPL01009- A parameter value is invalid. Operation Details name = aa...aa, parameter = bb...bb, aa...aa: offline, online, parameter value = cc...cc, Valid value = set, or view dd...dd bb...bb: Parameter name cc...cc: Specified parameter value dd...dd: Specifiable parameter value range Action Specify a correct value for...

  • Page 309

    Message 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 Details command. Operation name = aa...aa You do not have the administrator permissions necessary to execute the...

  • Page 310

    Message 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...

  • Page 311

    Message Message Text Explanation For details on the view operation, see view (Displays Information) on page 6-30. KAPL01019- The target path was not found. Operation Details name = aa...aa aa...aa: offline, online, or view offline/online ¢ operation The specified path does not exist.

  • Page 312

    Message 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, DLMgetras Utility for Collecting HDLM Error Information on page 7-4. KAPL01021- Cannot execute the HDLM command due Details to insufficient memory.

  • Page 313

    Message Message Text Explanation Operation Format) on page 6-4. KAPL01036- The Offline path cannot be placed online. Details PathID = aa...aa 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 the HDLM command, a path that cannot A path that cannot be...

  • Page 314

    Message Message Text Explanation Check the correct value, and then re-execute the HDLM command. KAPL01044- A duplicate parameter value is specified. Details Operation name = aa...aa, parameter = aa...aa:view bb...bb, parameter value = cc...cc bb...bb: Parameter name cc...cc: Duplicate parameter value Action Delete the duplicate parameter value, and then...

  • Page 315

    Message Message Text Explanation cancel the operation, enter 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.

  • Page 316

    Message Message Text Explanation (dlnkmgr) to check the path status. For details on the view operation, see view (Displays Information) on page 6-30. For details on the online operation, see online (Places Paths Online) on page 6-11. KAPL01052- The currently selected paths will be Details changed to the Offline(C) status.

  • Page 317

    Message 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.

  • Page 318

    Message 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.

  • Page 319

    Message 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. Details Operation name = aa...aa Command processing will be aborted because n was entered for a required confirmation.

  • Page 320

    Message 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-30. For details on the online operation, see online (Places Paths Online) on page 6-11.

  • Page 321

    Message 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. Details The temporary license has expired. Register a permanent license. Action Register a permanent license. KAPL01074- The emergency license expired.

  • Page 322

    Message Message Text Explanation Action Enable automatic failbacks, and then re-execute. KAPL01080- The error monitoring interval and the Details number of times that the error is to occur An intermittent error conflict with the automatic failback cannot be detected by checking interval.

  • Page 323

    Message 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.

  • Page 324

    Message Message Text Explanation company if there is a maintenance contract for HDLM. Do not perform the following operations: 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...

  • Page 325

    Message 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 Action If you want to execute the operation of the HDLM command, enter y. If you want to terminate processing, enter n.

  • Page 326

    Message 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 Details problem when all the paths which pass This message re-asks the...

  • Page 327

    Message Message Text Explanation Perform one of the following procedures. When performing an installation Installing HDLM on page 3-16, and then complete the installation. When performing an uninstallation Uninstalling HDLM on page 3-91, and then complete the uninstallation. When performing neither of the above, or if the same error continues to occur even after one of the...

  • Page 328

    Message 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. Details Restart the HDLM Manager, and execute The audit log configuration...

  • Page 329: Kapl03001 To Kapl04000, Kapl03001 To Kapl

    Message Message Text Explanation KAPL01120- A storage system model ID could not be Details displayed. Details = aa...aa, bb...bb 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...

  • Page 330

    Message ID Message Text Explanation 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.

  • Page 331

    Message ID Message Text Explanation theDLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-4. KAPL03007- An error occurred during communication Details with the HDLM manager. (aa...aa) This information is required for resolving problems. aa...aa: API trace error information Action Execute the DLMgetras...

  • Page 332: Kapl04001 To Kapl05000, Kapl04001 To Kapl

    Message ID Message Text Explanation 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 Message Text Explanation KAPL04001- HDLM manager started.

  • Page 333

    Message Message Text Explanation DLMgetras Utility for Collecting HDLM Error Information on page 7-4. KAPL04004- HDLM manager will now terminate. Action None. KAPL04008- Cannot open the option definition file Details (aa...aa). HDLM manager could not start normally because it was unable to open the option definition file.

  • Page 334

    Message Message Text Explanation Environment) on page 6-16. KAPL04010- Could not open the error log file. 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...

  • Page 335

    Message Message Text Explanation KAPL04013- Input is impossible via the communication Details 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...

  • Page 336

    Message Message Text Explanation Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-4.

  • Page 337

    Message Message Text Explanation 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 Details manager.

  • Page 338

    Message Message Text Explanation Month (01-12)/Day (01-31) Action Install a permanent license by the expiration day. KAPL04028- The temporary license expired. Action Install a permanent license. KAPL04029- The emergency license expired. Action Install a permanent license. KAPL04030- The temporary license has already Action expired.

  • Page 339

    Message Message Text Explanation 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. Details Total number of paths = aa...aa aa...aa: Total number of...

  • Page 340: Kapl05001 To Kapl06000, Kapl05001 To Kapl

    Message Message Text Explanation KAPL04045- HDLM SNMP TRAP was sent. Trap ID = Details aa...aa, IP Address = bb...bb, Port SNMP TRAP was sent. Number= cc...cc, Community = dd...dd, aa...aa: Trap ID Trap Data = ee...ee bb...bb: Destination IP address of the trap cc...cc: Destination port number of the trap dd...dd: Community name...

  • Page 341

    Message ID Message Text Explanation sequence number) and Partition (bb...bb: Fixed at 0) was successfully registered in the core logic. Action None. KAPL05008- Could not allocate memory. (aa:bb) Details Execute the DLMgetras utility to collect The OS memory allocation error information, and then contact your function was started but vendor or maintenance company.

  • Page 342

    Message ID Message Text Explanation normally. If it has not started or contains an error, contact your HDLM vendor or the maintenance company, if there is a maintenance contract for HDLM, and report the error and detail code. KAPL05014-I The device object (aa...aa) was Details registered as the path (bb...bb).

  • Page 343

    Message ID Message Text Explanation None. KAPL05023- Could not process the IOCTL(aa). (aa:cc) Details Check the message of the HDLM Processing corresponding command or the HDLM manager, and to the requested IOCTL then take the appropriate action. If you (aa...aa: IOCTL code do not know the appropriate action, (hexadecimal number)) is execute the DLMgetras utility to collect...

  • Page 344: Kapl06001 To Kapl07000, Kapl06001 To Kapl

    Message ID Message Text Explanation bb...bb: Message output location information cc...cc: Detailed information 1 dd...dd: Detailed information 2 Action None. KAPL06001 to KAPL07000 Message ID Message Text Explanation KAPL06003-I Initialization of the HDLM alert driver Details (aa...aa) was successful. Initialization of the alert driver (aa...aa: alert driver management table address (hexadecimal number))

  • Page 345

    Message ID Message Text Explanation KAPL06009-I Invalid IOCTL (aa...aa) was received. Details The processing is canceled. A request having an invalid IOCTL code (aa...aa: IOCTL code (hexadecimal number)) was issued to the alert driver. Action None. KAPL06010- Could not process the IOCTL (aa...aa). Details (bb...bb:cc...cc) Although the IOCTL...

  • Page 346

    Message ID Message Text Explanation by the core logic was generated, its log information was discarded by the HDLM alert driver. aa...aa: log message code (hexadecimal number) bb...bb: log area size (hexadecimal number) Action Check whether any other error occurred. The information that could not be written is discarded.

  • Page 347: Kapl07001 To Kapl08000, Kapl07001 To Kapl

    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 if another error does not occur. If the actual memory size is insufficient, increase the actual memory size.

  • Page 348: Kapl08001 To Kapl09000, Kapl08001 To Kapl

    KAPL08001 to KAPL09000 Message ID Message Text Explanation KAPL08019- The path (aa...aa) detected an error Details (bb...bb). (cc...cc) An error occurred in the path. The error is most likely due to a disconnected cable. aa...aa: Path identifier (hexadecimal number) bb...bb: Error code (hexadecimal number) When the path error is ¢...

  • Page 349

    Message ID Message Text Explanation view -path) (character string) dd...dd: Bus number or Adapter number (character string) ee...ee: Target ID (hexadecimal number) ff...ff: Host LU number (same as PathName of view -path) (hexadecimal number) gg...gg: Dev number (same as DNum of view - path) (decimal number) hh...hh: Host device name Action...

  • Page 350

    Message ID Message Text Explanation KAPL08026- An error occurred on all the paths of the Details LU. PathID = aa...aa An error occurred in the last, remaining path of an LU. (This is most likely as a result of a disconnection.) aa...aa: Path ID (same as PathID of view -path)

  • Page 351: Kapl09001 To Kapl10000, Kapl09001 To Kapl

    KAPL09001 to KAPL10000 Message Message Text Explanation KAPL09003- Cannot install in this system. Install Details HDLM on a supported OS. HDLM cannot be installed on this system. Action Host and OS Support for HDLM on page 3-3 install HDLM on a supported OS.

  • Page 352

    Message Message Text Explanation there is a maintenance contact of HDLM. KAPL09020- An attempt to uninstall Hitachi Network Details Objectplaza Trace Library 2 failed. An attempt to uninstall HNTRLib2 has failed. Action Manually uninstall Hitachi Network Objectplaza Trace Library 2. If the attempt to uninstall Hitachi Network Objectplaza Trace Library 2 fails again, contact your...

  • Page 353

    Message Message Text Explanation Messages section of the HDLM User's An attempt to copy a file Guide for instructions to correct this related to HDLM to the problem. directory of Hitachi Command Suite products other than HDLM has failed. Action If this message is output while installing HDLM, re- install HDLM.

  • Page 354

    Message Message Text Explanation An attempt to install HNTRLib2 failed. Action Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM. KAPL09029- This version of HDLM cannot be updated Action by installation. Uninstall the already Uninstall the HDLM that installed version of HDLM.

  • Page 355

    Message Message Text Explanation Action Install a permanent license by the expiration day. KAPL09078- The emergency license was installed. The Details license expires on aa...aa. An emergency license was installed. aa...aa: Year (4 digits)/ month (01-12)/day (01-31) Action Install a permanent license by the expiration day.

  • Page 356

    Message Message Text Explanation Obtain a valid license key, and then re-install HDLM. KAPL09088- The entered license key is invalid. The Action HDLM installation will now terminate. Obtain a valid license key, Obtain a valid license key, and then re- and then re-install HDLM.

  • Page 357

    Message Message Text Explanation KAPL09113- There is no installable license key in the Details license key file. File name = aa...aa There is no HDLM- Make sure that the license key file is installable license key in correct, and then re-install HDLM. the license key file.

  • Page 358

    Message Message Text Explanation different name. If you want to use the output name, use the output command to overwrite or re-install. KAPL09135- One of the following was executed at the Action same time as an HDLM command set -lic Check the license by using operation: another set -lic operation, or the HDLM command's view...

  • Page 359

    Message Message Text Explanation bb...bb: Internal code (decimal number) Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL09171- An internal error occurred in the Details installation of the HDLM. Error Code = A system-based error, not aa...aa bb...bb caused by the user,...

  • Page 360

    Message Message Text Explanation KAPL09183- HDLM version aa...aa is installed. This Details version will now be overwritten with aa...aa: Installed version version bb...bb. number of HDLM bb...bb: Version number of HDLM you attempted to install Action None. KAPL09187- No parameter is specified. Details No installation-information settings file has been...

  • Page 361

    Message Message Text Explanation the second parameter does not exist. Action Make sure that the path name of the installation- information settings file is appropriate, and then try again. KAPL09210- aa...aa will now start. Details aa...aa has just started. aa...aa: installhdlm, installp, cfgmgr, dlmodmset, dlnkmgr, or dlmrmdev...

  • Page 362

    Message Message Text Explanation Action Check the error message that was output just before this message, and then perform the action indicated in that error message. KAPL09214- A parameter is invalid. parameter = Details aa...aa A parameter is invalid. aa...aa: The specified parameter (character string) Action...

  • Page 363

    Message Message Text Explanation storage location of the /tmp directory. If the error code is 4: The /var/tmp directory does not exist. Prepare the / var/tmp directory, and then retry the operation. If the error code is 5: You do not have write permission for the / var/tmp or /var/DLM directory.

  • Page 364

    Message Message Text Explanation The status of the installed HDLM is BROKEN. Please uninstall HDLM. If the error code is 10: The cfgmgr command is not in the correct location, or you do not have a required permission. Check the state of the cfgmgr command.

  • Page 365

    Message Message Text Explanation aa...aa: Error number (decimal number) that specifies the executed processing bb...bb: Return value (decimal number) of the executed processing Action If the error code is9001 ,-1: You do not have read permissions for the installation information settings file.

  • Page 366

    Message Message Text Explanation The correct location of dlmrmdev and installhdlm_analysi s is the same directory as installhdlm. Make sure that the utility you want to execute is in the correct location and that you have the required permissions. If a utility is not in the correct location, copy the required files to the correct location,...

  • Page 367

    Message Message Text Explanation bb...bb: Return value (decimal number) of the executed processing Action Specify the revised installation information settings file, and then retry the operation. KAPL09221- The definition of the installation Details information settings file includes an A character that cannot be unusable character.

  • Page 368

    Message Message Text Explanation KAPL09228- The definition of the installation Details information settings file includes an The format of a key value invalid key value. Error Code = is invalid. aa...aa,bb...bb, line = cc...cc aa...aa: Error number (decimal number) that specifies the executed processing bb...bb: Return value...

  • Page 369

    Message Message Text Explanation 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. KAPL09231- The definition of the installation Details information settings file includes a A duplicated key is duplicated key.

  • Page 370

    Message Message Text Explanation KAPL09233- The definition of the installation Details information settings file is too long. Error The length of a single line Code = aa...aa,bb...bb, line = cc...cc of the definition exceeds 1023 characters. aa...aa: Error number (decimal number) that specifies the executed processing bb...bb: Return value...

  • Page 371

    Message Message Text Explanation You do not have write permission for the log file destination directory. Modify your access permissions as necessary, and then retry the operation. If the error code is 3: You do not have write permission for the file system of the log file.

  • Page 372

    Message Message Text Explanation to the installation status: • If installing HDLM by using the installhdlm utility has already finished, setting up HDLM might have not completed. You need to manually set up the values that are not set up, or re-execute installhdlm.

  • Page 373

    Message Message Text Explanation Action none. KAPL09241- An attempt to install an HDLM component Details failed. Error Code = aa...aa An attempt to install an HDLM component failed. aa...aa: Error number that identifies the executed processing Action If there is no need to access the Hitachi Command Suite products that use HDLM remote...

  • Page 374

    Message Message Text Explanation execute dlminstcomp utility. KAPL09243- dlminstcomp completed successfully. Details dlminstcomp utility completed successfully. Action None. KAPL09246- An attempt to install an HDLM component Details failed because an HDLM component was An attempt to install an operating. Error Code = aa...aa HDLM component failed because an HDLM component was operating.

  • Page 375

    Message Message Text Explanation edition of HDLM, or vice versa. Action Acquire the Service Pack that has the same language as the installed HDLM, and then try again. KAPL09601- Cannot install in this system. Install Details HDLM on a supported OS. HDLM cannot be installed on this system.

  • Page 376: Kapl10001 To Kapl11000, Kapl10001 To Kapl

    Message Message Text Explanation When the output information is an OS command: Confirm that the OS ¢ command exists, and that you have the proper permission. KAPL09604- A system error occurred. The installation Details will now stop. aa...aa: Command that (command = aa...aa, error code = failed bb...bb)

  • Page 377

    Message Message Text Explanation retry. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-4. KAPL10003- The first parameter has not been set to a Details directory. Value = aa...aa The first parameter must be set to a directory to which collected information is output.

  • Page 378

    Message Message Text Explanation Collecting HDLM Error Information on page 7-4. KAPL10006- The file for defining the information to be Details collected does not exist, or cannot be The file for defining the read. Value = aa...aa information to be collected does not exist, or the specified file exists but the permission to read the file...

  • Page 379

    Message Message Text Explanation Check whether the specified directory name is correct. Check that the disk has sufficient unused capacity. KAPL10009- The specified directory already exists. Do Details you want to overwrite it? [y/n]: The specified directory already exists. Enter y to overwrite it, or n to cancel.

  • Page 380

    Message Message Text Explanation the file for defining the information to be collected. aa...aa: Line number of the file for defining information to be collected (decimal number) bb...bb: Indicated contents in a line Action After the DLMgetras utility for collecting HDLM error information terminates, check the contents of the file for defining the...

  • Page 381

    Message Message Text Explanation message. If the contents of the file are incorrect, correct them, and then try to collect error information again. The DLMgetras utility will ignore the specified file or directory and continue processing. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error...

  • Page 382

    Message Message Text Explanation information to be collected (decimal number) bb...bb: Indicated contents in a line Action After the DLMgetras utility for collecting HDLM error information terminates, check the contents of the file for defining the information to be collected. This file is shown in the message.

  • Page 383

    Message Message Text Explanation collecting HDLM error information, and then re- execute. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-4. KAPL10017- You lack privileges for executing the Details utility for collecting HDLM error The DLMgetras utility for information.

  • Page 384

    Message Message Text Explanation None. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-4. KAPL10030- A user terminated the utility for collecting Details HDLM error information. Processing of the DLMgetras utility for collecting HDLM error information has been terminated because the...

  • Page 385

    Message Message Text Explanation KAPL10034- The file could not be copied. Filename = Details aa...aa, Details = bb...bb Execution of the cp command failed. aa...aa: File name you tried to copy bb...bb : cp command output message Action An error occurred while the information collection file was being copied.

  • Page 386

    Message Message Text Explanation company if you have a maintenance contract for HDLM. KAPL10049- Error information collection command = Details aa...aa, Return value = bb...bb, Execution A command was executed time = cc...cc to collect information targeted for collection. aa...aa: Executed command bb...bb: Return value of the executed command...

  • Page 387

    Message Message Text Explanation failed file system manually and re-execute the program. For details on the dlmrmdev utility, see dlmrmdev Utility for Deleting HDLM Drivers on page 7-25. KAPL10524- An attempt to inactivate the volume Details group has failed. (volume group = An attempt to inactivate aa...aa) the volume group has...

  • Page 388

    Message Message Text Explanation aa...aa: volume group succeeded (character string) Action None. KAPL10528- The volume group will be made inactive, Details and the file system that is using HDLM Notice unmount of the file will be unmounted. Is this OK? [y/n]: system used by HDLM or inactivation of the volume group to prompt the users...

  • Page 389

    Message Message Text Explanation Action To execute dlmpostrestore utility, enter y. If you do not want to execute dlmpostrestore utility, enter n. KAPL10553- Too many parameters have been Action specified. With the -h parameter specified, execute the dlmpostrestore utility. Make sure that the format of the utility is correct, and then re-execute it.

  • Page 390

    Message Message Text Explanation because n was sent to a request. Action None. KAPL10558- The entered value is invalid. The Details operation will now stop. The dlmpostrestore utility has been stopped because an invalid response was sent three times consecutively to a request. Action To execute dlmpostrestore utility again, enter either y...

  • Page 391

    Message Message Text Explanation aa...aa: Error number (decimal number) Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL10561- A user operation ended dlmpostrestore Details utility. The dlmpstrestore process has been terminated by an operation such as Ctrl+C.

  • Page 392

    Message Message Text Explanation KAPL10575- No parameter value has been specified. 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. KAPL10576- A parameter value is invalid. parameter Details value = aa...aa An invalid parameter value...

  • Page 393

    Message Message Text Explanation 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. KAPL10580- The entered value is invalid. Re-enter. [y/ Details A value other than y or n has been entered for a [y/ n] request.

  • Page 394

    Message Message Text Explanation stopped, and then restart them. If the error code is 19,1: Check for path errors. If there is a path error, restore the path status and then retry. Contact your HDLM vendor or the maintenance company, if you have an HDLM maintenance contract.

  • Page 395

    Message Message Text Explanation or the user does not have execution permissions for the dlmpr utility. Check the status of the dlmpr utility. If the error code is 11,2 or 12,-1: The mkdev command is not in the default location, or the user does not have execution permissions for the mkdev...

  • Page 396

    Message Message Text Explanation aa...aa: Specified attribute Action Delete the duplicate attribute, and then retry the operation. KAPL10641- Reservation Key will now be cleared. Is Details this OK? [y/n]: Enter y to clear and n to not clear the Reservation Key.

  • Page 397

    Message Message Text Explanation Utility for Clearing HDLM Persistent Reservation on page 7-22. KAPL10645- A parameter value is invalid. parameter = Details aa...aa An invalid parameter value has been specified for the dlmpr utility. aa...aa: specified parameter (character string) Action Specify the correct value for the parameter, and then retry.

  • Page 398

    Message Message Text Explanation your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. If a message with Error Code = 36 is output, check for a path error. If there is a path error, restore the path status and then retry.

  • Page 399

    Message Message Text Explanation An invalid response was sent three times consecutively to a request. Action Re-execute the dlmpr utility. KAPL10653- The entered value is invalid. Please re- Details enter it [y/n]: A value other than y or n has been entered for a [y/ n] request.

  • Page 400

    Message Message Text Explanation aa...aa: Specified operation (character string) Action Execute help of the dlmodmset utility to check the parameters that can be specified, and then retry. For details on the dlmodmset utility, see KAPL08001 to KAPL09000 on page 8-46. KAPL10802- A parameter is invalid.

  • Page 401

    Message Message Text Explanation want to change to the user for confirmation. aa...aa: Lun Reset, Online(E) IO Block (character string) bb...bb: on, off (character string) Action Enter y to execute setup, or enter n to cancel. KAPL10806- The entered value is invalid. Re-enter [y/ Details A value other than y or n has been entered for a [y/...

  • Page 402: Kapl11001 To Kapl12000, Kapl11001 To Kapl

    Message Message Text Explanation 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-46. KAPL11001 to KAPL12000 Message ID Message Text Explanation KAPL11901-I aa...aa has started.

  • Page 403

    Message ID Message Text Explanation aa...aa: Operation (character string) Online ¢ Offline ¢ bb...bb: The Path ID of the target path (decimal number) Action None. KAPL11903-I aa...aa has completed normally. Details The operation has completed normally on the host. aa...aa: Any of the following operations (character string) Get Path Information...

  • Page 404

    Message ID Message Text Explanation Get Option ¢ Information Set Option ¢ Information Clear Data ¢ Get HDLM Driver ¢ Status Get HDLM Manager ¢ Status Get HDLM Alert Driver ¢ Status Online ¢ Offline ¢ Get SNMP Trap ¢ Information Set SNMP Trap ¢...

  • Page 405: Kapl13001 To Kapl14000, Kapl13001 To Kapl

    Message ID Message Text Explanation maintenance contract for HDLM.For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-4. KAPL11906-I GUI information - aa...aa Details This information is required for resolving problems. aa...aa: Trace information Action None.

  • Page 406

    Message ID Message Text Explanation KAPL13005- The entered value is invalid. The Action operation will now stop. To execute dlmmigsts again, re-execute. For details about the dlmmigsts utility, see dlmmigsts Utility for Assisting HDLM Migration on page 7-18. KAPL13006-I The user stopped the operation. Action To execute dlmmigsts again, re-execute.

  • Page 407

    Message ID Message Text Explanation the dlmmigsts utility, see dlmmigsts Utility for Assisting HDLM Migration on page 7-18. KAPL13010- The specified file does not exist. Details parameter = aa...aa, Filename = bb...bb aa...aa: Parameter (character string) bb...bb: Filename (character string) Action If parameter = -odm, specify odmsetfile in...

  • Page 408

    Message ID Message Text Explanation is enough capacity, and then try again. For details about the dlmmigsts utility, see dlmmigsts Utility for Assisting HDLM Migration on page 7-18. KAPL13014- An internal error occurred in the Details dlmmigsts utility. Error Code = aa...aa aa...aa: Error Code Execute the DLMgetras utility to collect (decimal number)

  • Page 409

    Message ID Message Text Explanation KAPL13017- The restoration operation cannot be Action performed because DLManager.mpio.rte Install is not installed. DLManager.mpio.rte, and then execute the dlmmigsts utility again. KAPL13018- The backup operation cannot be Action performed because there is no /usr/ Contact your HDLM vendor DynamicLinkManager/config/dlmmgr.xml or the maintenance...

  • Page 410

    Message ID Message Text Explanation an invalid response was sent three times consecutively to a request. Action To execute dlmpreuninst again, enter either y or n. KAPL13107-I The user stopped the operation. Details The dlmpreuninst utility has been terminated because n was sent to a request.

  • Page 411

    Message ID Message Text Explanation Executed Before Uninstalling HDLM on page 7-24. KAPL13110- The dlmpreuninst utility cannot be Action executed because the HDLM driver is Execute the dlmrmdev running. Execute the dlmrmdev utility, command, and then re- and then re-execute the dlmpreuninst execute the utility.

  • Page 412: Kapl15001 To Kapl16000, Kapl15001 To Kapl

    Message ID Message Text Explanation "dlnkmgr view -sys - audlog" command, and then specify the desired setting by using the "dlnkmgr set -audlog" or the "dlnkmgr set - audfac" command as necessary. KAPL13604- An error occurred during processing to Details read the audit log configuration file.

  • Page 413

    Message ID Message Text Explanation KAPL15002- An attempt to display the registered Details value of ReserveKey has failed. aa...aa: Name of the utility Command Line = aa...aa that the user executed KAPL15005-I Information of HDLM execution Details environment ODM was successfully aa...aa: Name of the utility displayed.

  • Page 414

    Message ID Message Text Explanation aa...aa: Name of the utility that the user executed KAPL15085-I dlmgetrasinst successfully executed. Details Command Line = aa...aa aa...aa: Name of the utility that the user executed KAPL15101-I Clear operation was completed Details successfully. Command Line = aa...aa aa...aa: Command that the user executed KAPL15102-...

  • Page 415: Return Codes For Hitachi Command Suite Common Agent Component

    Message ID Message Text Explanation KAPL15110- An attempt to display information about Details HDLM-management targets has failed. aa...aa: Command that the Command Line = aa...aa user executed KAPL15111- The HDLM command was started or Details stopped by the user who does not have aa...aa: Command that the the authority.

  • Page 416

    Message ID Explanation Remove the error in the path, and then retry. 1007 Details The target path of the offline operation is the last, remaining path connected to the device and therefore, cannot be placed in the offline status. Action Click Refresh to update the host information, check the path status, and then retry the offline operation.

  • Page 417

    Message ID Explanation Refresh the host information, and then perform the operation again. If the same error occurs again, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or maintenance company if you have a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page...

  • Page 418

    Message ID Explanation 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. 1036 Details An attempt to acquire information about the HDLM version or SP version has failed.

  • Page 419

    Message ID Explanation 1046 Details A parameter is invalid. Action Refresh the host information, and then perform the operation again. If the same error occurs again, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or maintenance company if you have a maintenance contract for HDLM.

  • Page 420

    8-118 Messages Hitachi Dynamic Link Manager User Guide (for AIX(R))

  • Page 421: A Functional Differences Between Versions Of Hdlm

    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 □...

  • Page 422: Functional Differences Between Version 6.2 And Versions Earlier Than 6.2

    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 uninstall HDLM before executing the mksysb command.

  • Page 423

    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. □...

  • Page 424: Add-in Hdlm Driver Module, To The Logical Device Files

    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.

  • Page 425

    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 ¢...

  • Page 426: The Logical Device Files

    Commands of the utilities for Corresponding AIX commands operating HDLM volume groups 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. dlmchkdev utility for checking the HDLM device configuration ¢...

  • Page 427: Migrating Reservation Control Settings, Support For A Boot Disk Environment

    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.

  • Page 428: Changing A Virtual I/o Server's Method Of Recognizing Virtual Scsi Disks

    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.

  • Page 429: Acronyms And Abbreviations

    Acronyms and abbreviations The following acronyms and abbreviations might be used in this guide. Arbitrated Loop Application Programming Interface Automatic Storage Management Channel Adapter CHRP Common Hardware Reference Platform CLPR Cache Logical Partition Central Processing Unit Control Unit Acronyms-1 Hitachi Dynamic Link Manager User Guide (for AIX(R))

  • Page 430

    DBMS Database Management System Device Domain Name Server Fibre Channel FC-SP Fibre Channel Security Protocol Failover FQDN Fully Qualified Domain Name Greenwich Mean Time Graphical User Interface Host Bus Adapter HDev Host Device Acronyms-2 Hitachi Dynamic Link Manager User Guide (for AIX(R))

  • Page 431

    Host Logical Unit HTTP Hypertext Transfer Protocol Input/Output Internet Protocol iSCSI Internet Small Computer System Interface Local Area Network LDAP Lightweight Directory Access Protocol LDEV Logical Device LPAR Logical Partition Logical Unit Logical Unit Number Logical Volume Manager Acronyms-3 Hitachi Dynamic Link Manager User Guide (for AIX(R))

  • Page 432

    MPIO Multipath I/O Network Attached Storage Network Installation Management NPIV N-Port ID Virtualization Network Time Protocol Object Data Manager Operating System Port Peripheral Component Interconnect PVID Physical Volume Identifier Acronyms-4 Hitachi Dynamic Link Manager User Guide (for AIX(R))

  • Page 433

    RADIUS Remote Authentication Dial in User Service 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 Service Pack Secure Sockets Layer Service Processor Volume Group Acronyms-5 Hitachi Dynamic Link Manager User Guide (for AIX(R))

  • Page 434

    World Wide Name Acronyms-6 Hitachi Dynamic Link Manager User Guide (for AIX(R))

  • Page 435: Automatic Failback

    Glossary This glossary explains the terms used in this manual. 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.

  • Page 436

    CLPR(Cache Logical Partition) A function supported by the Hitachi USP, Universal Storage Platform V/VM, Virtual Storage Platform, and Hitachi AMS2000/AMS/WMS/SMS 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.

  • Page 437

    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. 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.

  • Page 438: Load Balancing

    intermittent error An error that occurs irregularly due to, for example, a loose cable connection. 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.

  • Page 439: Non-owner Path, Odm (object Data Manager)

    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) ODM (Object Data Manager) An AIX-dedicated database for managing system information. HDLM uses ODM to add or delete drivers.

  • Page 440: Path Name

    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.

  • Page 441

    SLPR (Storage Logical Partition) A function supported by Hitachi USP, Universal Storage Platform V/VM, and Virtual Storage Platform for logically splitting up a storage system. This function splits up the resources, such as ports, CLPR, and volumes, in the storage system, so that the user can manage each resource independently.

  • Page 442

    V W X Glossary-8 Hitachi Dynamic Link Manager User Guide (for AIX(R))

  • Page 443

    Index cluster Glossary-2 support 2-41 active host 2-41 cluster software 2-41 adapter number 3-14, 6-47 setup 3-23 adapter type 3-14, 6-47 Cluster Software (PowerHA) audit log Canceling Settings 3-100 categories and audit events that HDLM can coding file that defines information to be collected output 2-34 rules for...

  • Page 444

    Dev number Glossary-2 message 5-5, 5-6 directory to which collected information is output 7-5, 7-15 Displayed program information 6-33 displaying failback 1-3, 2-13, Glossary-2 information 6-30 failover 1-3, 2-13, Glossary-3 LU information 6-49 features of HDLM path information 6-31, 6-38 fiber cable path information (by selecting a display item) replacing...

  • Page 445

    functions host device name Glossary-3 installing 3-16 host LU 2-5, Glossary-3 Migrating 3-51 host LU number 6-48, Glossary-3 migration of 3-11 host, supported new installation 3-24 new installation of 3-11 overview preparations for an upgrade installation or re- installation of 3-34 count preparations for new installation of...

  • Page 446: Table Of Contents

    load distribution using load balancing number of error log files 6-19 log filter 2-31 number of trace files 6-20 logging level values 6-19 logical device file Glossary-4 logical unit obtaining logical unit ID 6-48 path information logical volume number Glossary-2 program information ODM (Object Data Manager) Glossary-5...

  • Page 447

    Performing Failovers and Failbacks Using Path GPFS 3-88 Switching 2-13 PowerHA 3-85 persistent reservation Glossary-6 3-90 placing a path or paths offline setup placing a path or paths online 6-11 cluster software 3-23 placing online HDLM 3-68 path integrated traces 3-78 port slot number...

  • Page 448

    upgrade installation 3-11 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-21 dlmpr, for clearing HDLM persistent reservation 7-22 dlmpreuninst, Utility for Executed Before Uninstalling HDLM 7-24 dlmrmdev, Utility for Deleting HDLM Drivers7-25...

  • Page 449

    Hitachi Dynamic Link Manager User Guide (for AIX(R))

  • Page 450

    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...

Comments to this Manuals

Symbols: 0
Latest comments: