Page of 640
Download Print This PagePrint Bookmark

HP XP P9500 User Manual

Hitachi dynamic link manager software users guide for linux (6.6) (hit5203-96005, 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 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640

Advertisement

Hitachi Command Suite
Dynamic Link Manager Software
User Guide (for Linux(R))
Document Organization
Product Version
Contents
MK-92DLM113-18

Advertisement

   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 Linux(R)) Document Organization Product Version Getting Help Contents MK-92DLM113-18...

  • 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....................xiii Intended audience....................xiv Product version.......................xiv Release notes......................xiv Document revision level...................xiv Document organization....................xiv Referenced documents.....................xv Document conventions.....................xvi Convention for storage capacity values..............xvii Getting help......................xviii Comments......................xviii 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 System Configuration Using an FC-SAN..............2-3 System Configuration Using an IP-SAN...............2-4...

  • Page 4: Table Of Contents

    Automatic Failbacks................2-20 Manual Path Switching..................2-21 Path Status Transition..................2-22 The Online Path Status................2-22 The Offline Path Status................2-22 Status Transitions of a Path..............2-22 Monitoring Intermittent Errors (Functionality When Automatic Failback Is Used)..2-24 Checking Intermittent Errors................2-24 Setting Up Intermittent Error Monitoring............2-24 Intermittent Error Monitoring Actions...............2-25 When an Intermittent Error Occurs............2-25 When an Intermittent Error Does Not Occur..........2-26 When the Conditions for an Intermittent Error Are Changed During Error...

  • Page 5: Table Of Contents

    File Systems Supported by HDLM............3-49 Boot Disk Environments Supported by HDLM (If an FC-SAN Is Used)..3-50 Related Products When Using SUSE LINUX Enterprise Server 9......3-50 Cluster Software Supported by HDLM.............3-50 Volume Managers Supported by HDLM............3-50 File Systems Supported by HDLM............3-51 Related Products When Using SUSE LINUX Enterprise Server 10......3-51 Cluster Software Supported by HDLM.............3-51 Volume Managers Supported by HDLM............3-53...

  • Page 6: Table Of Contents

    Deactivating the Volume Group..............3-85 Setting Up Xen..................3-86 Performing a Re-installation of HDLM...............3-86 Performing an Upgrade Installation of HDLM............3-91 Unattended Installation of HDLM..............3-96 Installing HDLM for Managing Boot Disks..............3-101 Notes on Installing HDLM in a Boot Disk Environment........3-101 Overview of the Procedure for Installing HDLM in a Boot Disk Environment..3-104 Settings for Using an HDLM Device as a Boot Disk.........3-104 Upgrade Installation in an Environment Where an HDLM Device Is Used as a Boot Disk....................3-104...

  • Page 7: Table Of Contents

    Setting Up Load Balancing..............3-185 Setting Up Path Health Checking............3-186 Setting Up the Automatic Failback Function...........3-186 Setting Up Intermittent Error Monitoring..........3-187 Setting the Error Log Collection Level............3-188 Setting the Trace Level................3-188 Setting the Error Log File Size...............3-189 Setting the Number of Error Log Files...........3-189 Setting the Trace File Size..............3-190 Setting the Number of Trace Files............3-190 Setting Up Audit Log Data Collection.............3-190...

  • Page 8: Table Of Contents

    Notes When Using SUSE LINUX Enterprise Server 9..........4-5 Notes When Using SUSE LINUX Enterprise Server 10..........4-6 Notes When Using SUSE LINUX Enterprise Server 11..........4-7 Updating Kernel Packages and Applying OS Update Packages........4-8 Environment Where an HDLM Device Is not Used as the Boot Disk.......4-9 Environment Where an HDLM Device Is Used as the Boot Disk......4-9 Environment Where a Logical Volume (LVM2) on an HDLM Device Is Used as the Boot Disk.......................4-10...

  • Page 9: Table Of Contents

    5 Troubleshooting..................5-1 Information Collected by the DLMgetras Utility for Collecting HDLM Error Information. 5-2 Checking Error Information in Messages..............5-2 What To Do for a Path Error..................5-3 Examining the Messages................... 5-5 Obtain Path Information..................5-5 Identifying the Error Path..................5-5 Narrowing Down the Hardware That Might Have Caused the Error....... 5-5 Identifying the Error Location and Correcting any Hardware Error......

  • Page 10: Table Of Contents

    To Display Program Information.............6-28 To Display Path Information..............6-28 To Display LU Information..............6-29 To display corresponding information about an HDLM device, SCSI device, and LDEV....................6-29 To Display the Format of the view Operation...........6-29 Parameters (To display program information)...........6-29 To display program information..............6-30 To display path information..............6-36 To display LU information..............6-47 To display corresponding information about an HDLM device, SCSI device, and...

  • Page 11: Table Of Contents

    Parameters.....................7-48 Log file......................7-48 8 Messages..................... 8-1 Before Viewing the List of Messages.................8-3 Format and Meaning of Message IDs..............8-3 Terms Used in Messages and Message Explanations..........8-3 Components That Output Messages to syslog............. 8-3 KAPL01001 to KAPL02000..................8-4 KAPL03001 to KAPL04000..................8-23 KAPL04001 to KAPL05000..................8-25 KAPL05001 to KAPL06000..................8-33 KAPL06001 to KAPL07000..................8-39...

  • Page 12

    Functional Differences Between Version 5.7.1 or Later and Versions Earlier Than 5.7.1 ..........................C-5 Functional Differences Between Version 5.7.0-01 or Later and Versions Earlier Than 5.7.0-01.........................C-5 Functional Differences Between Version 5.7 or Later and Versions Earlier Than 5.7..C-6 Functional Differences Between Version 5.6.3 or Later and Versions Earlier Than 5.6.3 ..........................C-6 Functional Differences Between Version 5.4 or Later and Versions Earlier Than 5.4..C-6 Acronyms and abbreviations...

  • Page 13

    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 14: 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: • Linux and its management functionality •...

  • Page 15: C Functional Differences Between Versions Of Hdlm

    Chapter Description HDLM manager. This chapter also describes how to configure an environment to properly operate HDLM, such as changing the HDLM management-target devices that connect paths or replacing the hardware that makes up 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 16: Document Conventions

    Document conventions Font and symbol conventions are classified as: • General font conventions • Conventions in syntax explanations These conventions are described below. General Font Conventions The following table lists the general font conventions: Font 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 17

    Example font or Convention symbol Code-font characters must be entered exactly as shown. StoreDatabase 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.

  • Page 18: Getting Help

    Logical capacity unit Value 1 KB 1,024 (2 ) bytes 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...

  • Page 19: 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 20: What Is Hdlm

    What is HDLM? With the widespread use of data warehousing and increasing use of multimedia data, the need for high-speed processing of large volumes of data on networks has rapidly grown. To satisfy this need, networks dedicated to the transfer of data, such as SANs, are now being used to provide access to storage systems.

  • Page 21: 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 22

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

  • Page 23: 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 24

    □ Integrated HDLM management using Global Link Manager □ Cluster Support HDLM Functions Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 25: Devices Managed By Hdlm, System Configuration, System Configuration Using An Fc-san

    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 of the storage systems listed in Section What is HDLM? on page 1-2:...

  • Page 26: System Configuration Using An Ip-san

    Figure 2-1 Configuration of an HDLM System When Using an FC-SAN Table 2-1 HDLM System Components When Using an FC-SAN on page 2-4 lists the HDLM system components when using an FC-SAN. Table 2-1 HDLM System Components When Using an FC-SAN Components Description A host bus adapter.

  • Page 27

    The cable port on the storage system is called a port (P) on a channel adapter (CHA) used for iSCSI connections. A logical unit (LU) contained in a storage system is the target of input to, or output from, the host. You can divide an LU into multiple areas. Each area after the division is called a Dev.

  • Page 28: Ip-san Environments Supported By Hdlm

    Table 2-2 HDLM System Components When Using an IP-SAN Components Description iSCSI software The driver software that contains the iSCSI initiator function. A network interface card that serves as a cable port on a host. The NIC is referred to as the HBA in HDLM commands. Sometimes, it is also just simply called an HBA in this manual.

  • Page 29

    Restrictions on using HDLM in an IP-SAN environment The following restrictions apply when using HDLM in an IP-SAN environment: • Use of HDLM in cluster configurations or boot disk environments is not supported. • The kdump function cannot be used. LU Configuration After you have properly installed HDLM, the LU configuration will change as follows:...

  • Page 30: Program Configuration

    Figure 2-3 LU Configuration Recognized by the Host After HDLM Installation Table 2-3 LU Components on page 2-8 lists the components recognized by the host. Table 2-3 LU Components Components Description HDev A Dev (partition) in an LU that the host recognizes via the HDLM driver.

  • Page 31

    Figure 2-4 Configuration of the HDLM Programs Table 2-4 Functionality of HDLM Programs on page 2-9 lists and describes the functions of these programs. Table 2-4 Functionality of HDLM Programs Program name Functions HDLM command Provides the dlnkmgr command, which enables you to: •...

  • Page 32: Position Of The Hdlm Driver And Hdlm Device

    Program name Functions HDLM manager Provides the HDLM manager, which enables you to: • Configure the HDLM operating environment • Request path health checks and automatic failbacks to be performed • Collect error log data HDLM alert driver Reports the log information collected by the HDLM driver to the HDLM manager.

  • Page 33: Logical Device Files For Hdlm Devices

    Figure 2-5 Position of the HDLM Driver and HDLM Devices Logical Device Files for HDLM Devices The logical device file name of an HDLM device is different from the logical device file name of a SCSI device. When you configure the logical device file of an HDLM device for applications such as volume management software, these applications can access the LUs that HDLM manages.

  • Page 34

    Table 2-5 Example of Using the Logical Device File Name of the Device Used When the Application Accesses the LU Host status Device file name that the application uses Before installing HDLM The application uses the logical device file name for the SCSI device.

  • Page 35: Distributing A Load Using Load Balancing

    Figure 2-6 About Alphabetic Letters Used in the Logical Device File Name About numeric values used in a logical device file name: [1-15] indicates a partition number in the applicable LU. For example, if the logical device file name of an HDLM device is sddlmaa1, it indicates partition 1 on sddlmaa.

  • Page 36

    function is used. Both figures show examples of I/O operations being issued for the same LU by multiple applications. Figure 2-7 Flow of I/O Data When the Load Balancing Function Is Not Used When the load balancing function is not used, I/O operations converge onto a single path (A).

  • Page 37: Paths To Which Load Balancing Is Applied

    Figure 2-8 Flow of I/O Data When the Load Balancing Function Is Used When the load balancing function is used, I/O operations are distributed via multiple paths (A, B, C, and D). This helps to prevent problems with system performance and helps prevent bottlenecks from occurring. Paths To Which Load Balancing Is Applied This subsection describes, for each type of storage system, the paths to which the load balancing function is applied.

  • Page 38: Series, Or Hitachi Sms, Load Balancing Algorithms

    among the remaining usable owner paths. When all owner paths cannot be used, load balancing is performed among the non-owner paths. For the example in Figure 2-9 Overview of Load Balancing on page 2-16, suppose that in the owner controller of LU0 is CHA0. When the LU is accessed, the load is balanced between the two paths A and B, which are both owner paths.

  • Page 39

    • 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. The following describes both of these processing methods: The Round Robin, Least I/Os, and Least Blocks algorithms These algorithms select the path to use each time a certain number of I/...

  • Page 40: Performing Failovers And Failbacks Using Path Switching

    Table 2-6 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 the I/O data is from something like a read request and is Robin generally sequential with the previous I/Os, an improvement...

  • Page 41: Automatic Path Switching, 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-5. For details on path statuses and the transitions of those statuses, see Path Status Transition on page 2-22.

  • Page 42

    Figure 2-10 Path Switching Automatic Failbacks When a path recovers from an error, HDLM can automatically place the recovered path back online. This function is called the automatic failback function. In order to use the automatic failback function, HDLM must already be monitoring error recovery on a regular basis.

  • Page 43: Manual Path Switching

    When intermittent errors occur on paths and you are using the automatic failback function, the path status might frequently alternate between the online and offline statuses. In such a case, because the performance of I/Os will most likely decrease, if there are particular paths in which intermittent errors might be occurring, we recommend that you set up intermittent error monitoring so you can detect these paths, and then remove them from those subject to automatic failbacks.

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

    use is not switched even if you change the path status to online by using the online operation. Path Status Transition Each of the online and offline statuses described in Performing Failovers and Failbacks Using Path Switching on page 2-18 is further subdivided into two statuses.

  • Page 45

    Figure 2-11 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 the following conditions are satisfied, a path that has been determined to have an intermittent error also becomes subject to automatic failback: All the paths connected to an LU are Online(E), Offline(E), or...

  • Page 46: Monitoring Intermittent Errors (functionality When Automatic Failback Is Used), Checking Intermittent Errors

    If an error occurs in the only available online path for an LU, the status of the path will change to Online(E). If you are using the automatic failback function, after the path has recovered from the error, HDLM will automatically place the path online. When you are using intermittent error monitoring, the path in which the intermittent error occurred is not automatically placed online when the path recovers from the error.

  • Page 47: Intermittent Error Monitoring Actions, When An Intermittent Error Occurs

    number of times that the error needs to occur. If an error occurs on a particular path the specified number of times within the specified error- monitoring interval, then an intermittent error will occur on the path. For example, if you specify 30 for the error monitoring interval and 3 for the number of times that the error needs to occur, the path is determined to have an intermittent error if an error occurs 3 or more times in 30 minutes.

  • Page 48: When An Intermittent Error Does Not Occur

    Figure 2-12 Action What Will Happen When an Intermittent Error Occurs on a Path When an Intermittent Error Does Not Occur If an error does not occur on a path a specified number of times within a specified interval, an intermittent error will not occur. In such a case, the error monitoring will finish when the specified error-monitoring interval finishes, upon which the number of errors is reset to 0.

  • Page 49

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

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

    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 51: Detecting Errors By Using Path Health Checking

    Number of Information errors and time about paths passed since User operation not subject to error automatic monitoring failback started Placing the path Online Inherited (Not applicable) while intermittent error If a path has monitoring is being been removed performed from the paths subject to automatic...

  • Page 52: Error Management

    For example, in a normal state, I/O operations are not performed on the paths coming from the standby host in the cluster configuration or on non- owner paths (that is, some of the paths that access a Thunder 9500V series and Hitachi AMS/WMS series storage system).

  • Page 53: Types Of Collected Logs

    Figure 2-15 Flow of Data When Collecting Error Information Logs might be collected in layers below HDLM, such as for the SCSI driver. For more details, see the Linux documentation. Types of Collected Logs HDLM collects information on the detected error and trace information in the process-specific-trace information file, trace file, error logs, log for the dlmcfgmgr utility for managing the HDLM configuration and syslog.

  • Page 54: Error Information

    Table 2-8 Types of Error Information on page 2-32 describes the types of error information. Table 2-8 Types of Error Information Log name Description Output destination Process-specific- Operation logs for the HDLM command The default file path is / trace information are collected.

  • Page 55: Filtering Of Error Information

    The following shows an example where the system function name is user, and messages at the info level or higher are output to the /tmp/ syslog.user.log file: user.info /tmp/syslog.user.log For details on error levels, see Filtering of Error Information on page 2-33.

  • Page 56: Utility For Collecting Hdlm Installation Error Information (installgetras), Collecting Audit Log Data

    Outputs error information only ¢ Outputs trace information on program operation summaries ¢ Outputs trace information on program operation details ¢ Outputs all trace information ¢ For details on how to set the collection level, see Setting Up the HDLM Functions on page 3-184.

  • Page 57

    Category Explanation • Startup and termination of hardware components (including micro-program) • Startup and termination of software running on storage systems, software running on SVPs (service processors), and Hitachi Command Suite products An abnormal hardware or software event, including: Failure •...

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

    Category Explanation • Adding or removing software components An event indicating an abnormal state such as exceeding AnomalyEvent a threshold, including: • Exceeding a network traffic threshold • Exceeding a CPU load threshold • Reporting that the temporary audit log data saved internally is close to its maximum size limit or that the audit log files have wrapped back around to the beginning...

  • Page 59

    Severity Category Explanation Audit event Message ID Processing of the KAPL15062-I dlmstart utility was successful. Processing of the KAPL15063-E dlmstart utility failed. Administrator or Permission has KAPL15111-W Authentication end-user not been granted authentication to execute the HDLM command. Permission has KAPL15010-W not been granted to execute HDLM...

  • Page 60

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

  • Page 61

    Severity Category Explanation Audit event Message ID Processing of the KAPL15045-E dlmcfgmgr -i command failed. Processing of the KAPL15046-I dlmcfgmgr -v command was successful. Processing of the KAPL15047-E dlmcfgmgr -v command failed. Processing of the KAPL15048-I dlmcfgmgr -u command was successful.

  • Page 62: Requirements For Outputting Audit Log Data

    Severity Category Explanation Audit event Message ID Processing of the KAPL15058-I dlmupdatesysini t command was successful. Processing of the KAPL15059-E dlmupdatesysini t command failed. The severity levels are as follows: 3: Error, 4: Warning, 6: Informational 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.

  • Page 63: Destination And Filtering Of Audit Log Data

    Destination and Filtering of Audit Log Data Audit log data is output to syslog. Because HDLM messages other than audit log data are also output to syslog, we recommend that you specify the output destination that is used exclusively for audit log data. For example, to change the output destination of audit log data to /usr/ local/audlog, specify the following two settings: •...

  • Page 64: Audit Log Data Formats

    Audit Log Data Formats The following describes the format of audit log data: Format of audit log data output to syslog: priority ¢ date-and-time ¢ host-name ¢ program-name ¢ [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-...

  • Page 65: Integrated Hdlm Management Using Global Link Manager

    Explanation Item Hardware identification Hardware model name or serial number information Location information Hardware component identification information Location identification Location identification information information FQDN Fully qualified domain name Redundancy Redundancy identification information identification information Agent information Agent information Host sending request Name of the host sending a request Port number sending Number of the port sending a request...

  • Page 66: Cluster Support

    to perform system-wide load balancing, and centrally manage the system by collecting HDLM failure information in Global Link Manager. Global Link Manager collects and manages information about paths from instances of HDLM installed on multiple hosts. Even if multiple users manage these hosts, they can control and view this centralized information from client computers.

  • Page 67

    Software Supported by HDLM (If an FC-SAN Is Used) on page 3-49 Related Products When Using Red Hat Enterprise Linux 6 on page 3-48, Cluster Software Supported by HDLM on page 3-50 Related Products When Using SUSE LINUX Enterprise Server 9 on page 3-50, Cluster Software Supported by HDLM on page 3-51...

  • Page 68

    2-46 HDLM Functions Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 69: Creating An Hdlm Environment

    Creating an HDLM Environment This chapter explains the procedure for setting up an HDLM environment and the procedure for canceling the environment settings. Make sure that HDLM installation and function setup has been performed. Set up volume groups and cluster software according to the environment you are using.

  • Page 70

    □ Settings for Oracle RAC □ Settings for the RHCM □ Settings for VCS □ Checking the Path Configuration □ Setting Up HDLM □ The Process-specific-trace Information File □ Creating a Character-Type Device File for an HDLM Device □ Creating File Systems for HDLM (When Volume Management Software Is Not Used) □...

  • Page 71: Hdlm System Requirements, Hosts And Oss Supported By Hdlm

    HDLM System Requirements Check the following before installing HDLM: Hosts and OSs Supported by HDLM HDLM supports hosts on which OSs listed in Table 3-2 Red Hat Enterprise Linux AS4/ES4 Kernels Supported by HDLM on page 3-4, Table 3-3 Red Hat Enterprise Linux 5 Kernels Supported by HDLM on page 3-7, Table 3-4...

  • Page 72

    The following shows the meaning of the execution result of the uname command: i686: IA32 architecture ia64: IPF architecture x86_64: AMD64/EM64T architecture Execute the following command to check the vendor of the CPU you are using: # cat /proc/cpuinfo processor vendor_id : AuthenticAMD cpu family...

  • Page 73

    Kernel Kernel architecture 2.6.9-34.EL 2.6.9-34.ELsmp 2.6.9-34.ELhugemem 2.6.9-34.0.2.EL 2.6.9-34.0.2.ELsmp 2.6.9-34.0.2.ELhugemem 2.6.9-42.EL 2.6.9-42.ELsmp 2.6.9-42.ELhugemem 2.6.9-42.0.3.EL 2.6.9-42.0.3.ELsmp 2.6.9-42.0.3.ELhugemem 2.6.9-55.EL 2.6.9-55.ELsmp 2.6.9-55.ELhugemem 2.6.9-67.EL 2.6.9-67.ELsmp 2.6.9-67.ELhugemem 2.6.9-78.EL 2.6.9-78.ELsmp 2.6.9-78.ELhugemem 2.6.9-89.EL 2.6.9-89.ELsmp 2.6.9-89.ELhugemem 2.6.9-100.EL 2.6.9-100.ELsmp 2.6.9-100.ELhugemem 2.6.9-11.EL 2.6.9-34.EL 2.6.9-42.EL 2.6.9-42.0.3.EL 2.6.9-55.EL 2.6.9-55.ELlargesmp 2.6.9-67.EL 2.6.9-67.ELlargesmp 2.6.9-78.EL 2.6.9-78.ELlargesmp 2.6.9-89.EL Creating an HDLM Environment Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 74

    Kernel Kernel architecture 2.6.9-89.ELlargesmp 2.6.9-100.EL 2.6.9-100.ELlargesmp 2.6.9-11.EL EM64T/AMD64 2.6.9-11.ELsmp 2.6.9-34.EL 2.6.9-34.ELsmp 2.6.9-34.ELlargesmp 2.6.9-34.0.2.EL 2.6.9-34.0.2.ELsmp 2.6.9-34.0.2.ELlargesmp 2.6.9-42.EL 2.6.9-42.ELsmp 2.6.9-42.ELlargesmp 2.6.9-42.0.3.EL 2.6.9-42.0.3.ELsmp 2.6.9-42.0.3.ELlargesmp 2.6.9-55.EL 2.6.9-55.ELsmp 2.6.9-55.ELlargesmp 2.6.9-67.EL 2.6.9-67.ELsmp 2.6.9-67.ELlargesmp 2.6.9-78.EL 2.6.9-78.ELsmp 2.6.9-78.ELlargesmp 2.6.9-89.EL 2.6.9-89.ELsmp 2.6.9-89.ELlargesmp 2.6.9-100.EL 2.6.9-100.ELsmp 2.6.9-100.ELlargesmp Only kernels that are provided by OS distributors in binary format are supported.

  • Page 75

    HDLM supports an environment where an IPF kernel is installed on a system that uses an Intel CPU. Note the following in an EM64T/AMD64 environment: HDLM supports an environment where an EM64T/AMD64 kernel is ¢ installed on a system that uses an Intel CPU or AMD Opteron CPU. In an EM64T/AMD64 environment, the RPM (Red Hat Package ¢...

  • Page 76

    Kernel Kernel architecture 2.6.18-238.el5 2.6.18-274.el5 2.6.18-8.el5 EM64T/AMD64 2.6.18-53.el5 2.6.18-92.el5 2.6.18-128.el5 2.6.18-164.el5 2.6.18-194.el5 2.6.18-238.el5 2.6.18-274.el5 Only kernels that are provided by OS distributors in binary format are supported. HDLM supports an environment where an IA32 kernel is installed on a system that uses an Intel CPU or AMD Opteron processor. HDLM supports an environment where an IPF kernel is installed on a system that uses an Intel CPU.

  • Page 77

    Kernel Kernel architecture 2.6.32-131.0.15.el6.x86_64 Only kernels that are provided by OS distributors in binary format are supported. HDLM supports an environment where an IA32 kernel is installed on a system that uses an Intel CPU or AMD Opteron processor. Note the following in an EM64T/AMD64 environment: HDLM supports an environment where an EM64T/AMD64 kernel is ¢...

  • Page 78

    Among the functions for SUSE LINUX Enterprise Server, HDLM only ¢ supports CFQ, and the default I/O scheduler functionality. An HDLM device that applies EVMS functions is not supported. ¢ You cannot use DRBD functions in an environment where HDLM is ¢...

  • Page 79

    Kernel Kernel architecture 2.6.16.60-0.85.1-xenpae 2.6.16.21-0.8-default 2.6.16.46-0.14-default 2.6.16.60-0.21-default 2.6.16.60-0.54.5-default 2.6.16.60-0.85.1-default EM64T/AMD64 2.6.16.21-0.8-default 2.6.16.21-0.8-smp 2.6.16.46-0.14-default 2.6.16.46-0.14-smp 2.6.16.60-0.21-default 2.6.16.60-0.21-smp 2.6.16.60-0.21-xen 2.6.16.60-0.54.5-default 2.6.16.60-0.54.5-smp 2.6.16.60-0.54.5-xen 2.6.16.60-0.85.1-default 2.6.16.60-0.85.1-smp 2.6.16.60-0.85.1-xen Note: This subsection describes the operating environment common to SUSE LINUX Enterprise Server 10. Among the functions for SUSE LINUX Enterprise Server, HDLM only ¢...

  • Page 80

    A gdb package of version 6.5-21.2 or later must be installed. All of the packages of SP1 for SUSE LINUX Enterprise Server 10 must be installed. All of the SP2 packages for SUSE LINUX Enterprise Server 10 must be installed. All of the SP3 packages for SUSE LINUX Enterprise Server 10 must be installed.

  • Page 81

    An HDLM device that applies EVMS functions is not supported. ¢ You cannot use DRBD functions in an environment where HDLM is ¢ installed. You cannot use HDLM in a User-Mode Linux environment. ¢ Only kernels that are provided by OS distributors in binary format are supported.

  • Page 82

    HDLM supports an environment where an EM64T/AMD64 kernel is ¢ installed on a system that uses an Intel CPU or AMD Opteron CPU. In an EM64T/AMD64 environment, the RPM (Red Hat Package ¢ Manager) packages listed below are required. Install these RPM packages before installing HDLM: - libstdc++- RPM package version .i386.rpm - libgcc- RPM package version .i386.rpm...

  • Page 83: Storage Systems Supported By Hdlm

    RPM package version depends on the OS version you are using. Storage Systems Supported by HDLM The following shows the storage systems that HDLM supports. Storage Systems The following storage systems are supported by HDLM: If an FC-SAN is used: •...

  • Page 84: Hba (if An Fc-san Is Used), Nic (if An Ip-san Is Used)

    Boot Disk Environments and BladeSymphony Environments Supported ¢ by HDLM (If an FC-SAN Is Used) on page 3-46 Related Products When Using Red Hat Enterprise Linux 5 on page 3-36 Boot Disk Environments Supported by HDLM (If an FC-SAN Is Used) ¢...

  • Page 85

    Table 3-10 Cluster Software When Using Red Hat Enterprise Linux AS4 (IA32) Usable kernels Cluster software 2.6.9-11.EL LifeKeeper v6 2.6.9-11.ELsmp LifeKeeper v6 Update1 2.6.9-11.ELhugemem LifeKeeper v6 Update2 LifeKeeper v6 Update3 LifeKeeper v6 Update4 LifeKeeper v7 LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 Oracle9i RAC Release 2 (9.2.0.8.0) Oracle RAC 10g Release 2 (10.1.0.5.0)

  • Page 86

    Usable kernels Cluster software LifeKeeper v6 Update4 LifeKeeper v7 LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 Oracle RAC 10g Release 2 (10.1.0.5.0) Oracle RAC 10g Release 2 (10.2.0.2.0) Oracle RAC 10g Release 2 (10.2.0.3.0) Oracle RAC 10g Release 2 (10.2.0.4.0) Oracle RAC 11g Release 1 (11.1.0.6.0) Oracle RAC 11g Release 1 (11.1.0.7.0) RHCM 1.0.4-0...

  • Page 87

    Usable kernels Cluster software Oracle RAC 10g Release 2 (10.2.0.3.0) Oracle RAC 10g Release 2 (10.2.0.4.0) Oracle RAC 11g Release 1 (11.1.0.6.0) Oracle RAC 11g Release 1 (11.1.0.7.0) RHCM 1.0.11-0 2.6.9-55.EL LifeKeeper v6 2.6.9-55.ELsmp LifeKeeper v6 Update1 2.6.9-55.ELhugemem LifeKeeper v6 Update2 LifeKeeper v6 Update3 2.6.9-67.EL LifeKeeper v6 Update4...

  • Page 88

    Usable kernels Cluster software Oracle RAC 11g Release 2 (11.2.0.2.0) Only configurations that include Oracle Cluster Management Software using raw devices are supported. For details, see Settings for Oracle RAC on page 3-178. Only configurations that include the Automatic Storage Management (ASM) function (the ASMLib kernel driver (ASMLib) is used) and Cluster Ready Service (CRS) are supported.

  • Page 89

    Configurations that include the Automatic Storage Management (ASM) ¢ function (raw devices used) and Oracle Clusterware Configurations that include the Automatic Storage Management (ASM) ¢ function (the ASMLib kernel driver (ASMLib) is used) and Oracle Clusterware Configurations that include the Oracle Cluster File System 2 and ¢...

  • Page 90

    Usable kernels Cluster software Oracle RAC 10g Release 2 (10.2.0.4.0) Oracle RAC 11g Release 1 (11.1.0.6.0) Oracle RAC 11g Release 1 (11.1.0.7.0) RHCM 1.0.0-0 2.6.9-34.EL LifeKeeper v6 2.6.9-34.ELsmp LifeKeeper v6 Update1 2.6.9-34.ELhugemem LifeKeeper v6 Update2 LifeKeeper v6 Update3 2.6.9-34.0.2.EL LifeKeeper v6 Update4 2.6.9-34.0.2.ELsmp LifeKeeper v7 2.6.9-34.0.2.ELhugemem...

  • Page 91

    Usable kernels Cluster software 2.6.9-67.ELsmp LifeKeeper v6 Update4 2.6.9-67.ELhugemem LifeKeeper v7 LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 Oracle RAC 10g Release 2 (10.1.0.5.0) Oracle RAC 10g Release 2 (10.2.0.2.0) Oracle RAC 10g Release 2 (10.2.0.3.0) Oracle RAC 10g Release 2 (10.2.0.4.0) Oracle RAC 11g Release 1 (11.1.0.6.0) Oracle RAC 11g Release 1 (11.1.0.7.0) RHCM 1.0.17-0...

  • Page 92

    Configurations that include raw devices and Cluster Ready Service ¢ (CRS) Configurations that include the Automatic Storage Management (ASM) ¢ function (raw devices used) and Cluster Ready Service (CRS) When 2.6.9-11.ELsmp is used for the kernel, the following configuration is also supported: Configurations that include the Automatic Storage Management (ASM) ¢...

  • Page 93

    The following configurations are supported: Configurations that include raw devices and Cluster Ready Service ¢ (CRS) Configurations that include the Automatic Storage Management (ASM) ¢ function (raw devices used) and Cluster Ready Service (CRS) For details, see Settings for Oracle RAC on page 3-178.

  • Page 94

    For details, see Settings for Oracle RAC on page 3-178. The following configurations are supported: Configurations that include raw devices and Cluster Ready Service ¢ (CRS) Configurations that include the Automatic Storage Management (ASM) ¢ function (raw devices used) and Cluster Ready Service (CRS) Configurations that include the Automatic Storage Management (ASM) ¢...

  • Page 95

    Usable kernels Cluster software Oracle RAC 10g Release 2 (10.2.0.3.0) Oracle RAC 10g Release 2 (10.2.0.4.0) Oracle RAC 11g Release 1 (11.1.0.6.0) Oracle RAC 11g Release 1 (11.1.0.7.0) RHCM 1.0.4-0 VCS 4.1 MP3 2.6.9-34.0.2.EL LifeKeeper v6 2.6.9-34.0.2.ELsmp LifeKeeper v6 Update1 2.6.9-34.0.2.ELlargesmp LifeKeeper v6 Update2 LifeKeeper v6 Update3...

  • Page 96

    Usable kernels Cluster software LifeKeeper v6 Update3 LifeKeeper v6 Update4 LifeKeeper v7 LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 Oracle RAC 10g Release 2 (10.2.0.2.0) Oracle RAC 10g Release 2 (10.2.0.3.0) Oracle RAC 10g Release 2 (10.2.0.4.0) Oracle RAC 11g Release 1 (11.1.0.6.0) Oracle RAC 11g Release 1 (11.1.0.7.0) RHCM 1.0.11-0 2.6.9-55.EL...

  • Page 97

    Usable kernels Cluster software 2.6.9-100.ELlargesmp Oracle RAC 10g Release 2 (10.2.0.4.0) Oracle RAC 11g Release 1 (11.1.0.6.0) Oracle RAC 11g Release 1 (11.1.0.7.0) Oracle RAC 11g Release 2 (11.2.0.2.0) The following configurations are supported: Configurations that include raw devices and Cluster Ready Service ¢...

  • Page 98: Volume Managers Supported By Hdlm

    The following functions are not supported: I/O fencing function provided by VCS ¢ DiskReservation function provided by VCS ¢ Linkage with VxVM and VxFS ¢ Only configurations that include the Automatic Storage Management (ASM) function (using raw devices) and Oracle Clusterware are supported. For details, see Settings for Oracle RAC on page 3-178.

  • Page 99

    Kernel architecture Kernel Volume Manager 2.6.9-78.ELhugemem 2.6.9-89.EL LVM2.02.42-5.el4 2.6.9-89.ELsmp 2.6.9-89.ELhugemem 2.6.9-100.EL LVM2.02.42-9.el4 2.6.9-100.ELsmp 2.6.9-100.ELhugemem 2.6.9-11.EL LVM2.01.08-1.0.RHEL4 2.6.9-34.EL LVM2.02.01-1.3.RHEL4 LVM2.02.21-5.el4 2.6.9-42.EL LVM2.02.06-6.0.RHEL4 2.6.9-42.0.3.EL 2.6.9-55.EL LVM2.02.21-5.el4 2.6.9-55.ELlargesmp 2.6.9-67.EL LVM2.02.27-2.el4 2.6.9-67.ELlargesmp 2.6.9-78.EL LVM2.02.21-5.el4 2.6.9-78.ELlargesmp LVM2.02.37-3.el4 2.6.9-89.EL LVM2.02.42-5.el4 2.6.9-89.ELlargesmp 2.6.9-100.EL LVM2.02.42-9.el4 2.6.9-100.ELlargesmp EM64T/AMD64 2.6.9-11.EL LVM2.01.08-1.0.RHEL4 2.6.9-11.ELsmp 2.6.9-34.EL...

  • Page 100: File Systems Supported By Hdlm

    Kernel architecture Kernel Volume Manager 2.6.9-55.ELlargesmp 2.6.9-67.EL LVM2.02.27-2.el4 2.6.9-67.ELsmp 2.6.9-67.ELlargesmp 2.6.9-78.EL LVM2.02.21-5.el4 2.6.9-78.ELsmp LVM2.02.37-3.el4 2.6.9-78.ELlargesmp 2.6.9-89.EL LVM2.02.42-5.el4 2.6.9-89.ELsmp 2.6.9-89.ELlargesmp 2.6.9-100.EL LVM2.02.42-9.el4 2.6.9-100.ELsmp 2.6.9-100.ELlargesmp File Systems Supported by HDLM When using a file system, the related programs are as follows: • ext2 (supplied with the OS) •...

  • Page 101

    Kernel Kernel Supported storage systems architecture 2.6.9-55.EL 2.6.9-78.EL EM64T 2.6.9-11.ELsmp 2.6.9-34.ELsmp 2.6.9-55.ELsmp 2.6.9-78.ELsmp The XP series is not supported. The storage system is not supported in an environment where an HDLM device is specified for the boot disk. HDLM supports boot disks in all of the environments listed in Table 3-16 Operating Environments for Boot Disks When Using Red Hat Enterprise Linux AS4/ES4(IA32) on page...

  • Page 102

    Kernel Supported storage systems 2.6.9-55.ELsmp QLogic 2.6.9-55.ELhugemem 2.6.9-67.EL 2.6.9-67.ELsmp 2.6.9-67.ELhugemem 2.6.9-78.EL 2.6.9-78.ELsmp 2.6.9-78.ELhugemem 2.6.9-89.EL 2.6.9-89.ELsmp 2.6.9-89.ELhugemem 2.6.9-100.EL 2.6.9-100.ELsmp 2.6.9-100.ELhugemem Table 3-17 Operating Environments for Boot Disks When Using Red Hat Enterprise Linux AS4/ES4 (IPF) Kernel Supported storage systems 2.6.9-55.EL Emulex Hitachi AMS2000/AMS/WMS/SMS series 2.6.9-55.ELlargesmp...

  • Page 103

    Kernel Supported storage systems 2.6.9-34.0.2.ELsmp 2.6.9-34.0.2.ELhugemem 2.6.9-42.EL 2.6.9-42.ELsmp 2.6.9-42.ELlargesmp 2.6.9-42.0.3.EL 2.6.9-42.0.3.ELsmp 2.6.9-42.0.3.ELlargesmp 2.6.9-55.EL Emulex 2.6.9-55.ELsmp QLogic 2.6.9-55.ELlargesmp 2.6.9-67.EL 2.6.9-67.ELsmp 2.6.9-67.ELlargesmp 2.6.9-78.EL 2.6.9-78.ELsmp 2.6.9-78.ELlargesmp 2.6.9-89.EL 2.6.9-89.ELsmp 2.6.9-89.ELlargesmp 2.6.9-100.EL 2.6.9-100.ELsmp 2.6.9-100.ELlargesmp Table 3-19 Operating Environments for BladeSymphony and Boot Disks When Using Red Hat Enterprise Linux AS4/ES4 on page 3-35 lists the operating environments when an HDLM device is used as a boot disk in a BladeSymphony environment.

  • Page 104: Cluster Software Supported By Hdlm (if An Fc-san Is Used)

    Kernel architecture Kernel Supported storage systems 2.6.9-55.EL 2.6.9-78.EL EM64T 2.6.9-11.ELsmp 2.6.9-34.ELsmp 2.6.9-55.ELsmp 2.6.9-78.ELsmp The HP XP series is not supported. Notes on using HDLM in a BladeSymphony environment When HDLM is used in a BladeSymphony environment, the following functions cannot be used: •...

  • Page 105

    Enterprise Linux 5 (EM64T/AMD64) on page 3-39 list the related programs used when creating a cluster. Table 3-20 Cluster Software Used with Red Hat Enterprise Linux 5 (IA32) Usable kernels Cluster software 2.6.18-8.el5 LifeKeeper v6 Update1 2.6.18-8.el5PAE LifeKeeper v6 Update2 LifeKeeper v6 Update3 LifeKeeper v6 Update4 LifeKeeper v7...

  • Page 106

    Usable kernels Cluster software LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 Oracle RAC 10g Release 2 (10.2.0.4.0) Oracle RAC 11g Release 1 (11.1.0.6.0) Oracle RAC 11g Release 1 (11.1.0.7.0) Oracle RAC 11g Release 2 (11.2.0.1.0) Oracle RAC 11g Release 2 (11.2.0.2.0) RHCM 2.0.98-1 2.6.18-164.el5 LifeKeeper v6 Update4...

  • Page 107

    Configurations that include the Automatic Storage Management (ASM) ¢ function (the ASMLib kernel driver (ASMLib) is used) and Oracle Clusterware Configurations that include the Oracle Cluster File System 2 and ¢ Oracle Clusterware For details, see Settings for Oracle RAC on page 3-178.

  • Page 108

    Usable kernels Cluster software LifeKeeper v6 Update3 LifeKeeper v6 Update4 LifeKeeper v7 LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 Oracle RAC 10g Release 2 (10.2.0.1.0) Oracle RAC 10g Release 2 (10.2.0.3.0) Oracle RAC 10g Release 2 (10.2.0.4.0) Oracle RAC 11g Release 1 (11.1.0.6.0) Oracle RAC 11g Release 1 (11.1.0.7.0) Oracle RAC 11g Release 1 (11.1.0.7.0) + Patch 8833297...

  • Page 109

    Usable kernels Cluster software Oracle RAC 11g Release 1 (11.1.0.7.0) + Patch 8833297 Oracle RAC 11g Release 2 (11.2.0.1.0) Oracle RAC 11g Release 2 (11.2.0.2.0) RHCM 2.0.84-2 2.6.18-128.el5 LifeKeeper v6 Update4 LifeKeeper v7 LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 Oracle RAC 10g Release 2 (10.2.0.1.0) Oracle RAC 10g Release 2 (10.2.0.3.0) Oracle RAC 10g Release 2 (10.2.0.4.0)

  • Page 110

    Usable kernels Cluster software Oracle RAC 11g Release 1 (11.1.0.7.0) + Patch 8833297 Oracle RAC 11g Release 2 (11.2.0.1.0) Oracle RAC 11g Release 2 (11.2.0.2.0) Only configurations that include the Automatic Storage Management (ASM) function (raw devices used) and Cluster Ready Service (CRS) are supported.

  • Page 111

    Configurations that include raw devices and Oracle Clusterware ¢ Configurations that include the Automatic Storage Management (ASM) ¢ function (raw devices used) and Oracle Clusterware Configurations that include the Automatic Storage Management (ASM) ¢ function (the ASMLib kernel driver (ASMLib) is used) and Oracle Clusterware Configurations that include the Oracle Cluster File System 2 and ¢...

  • Page 112

    Kernel architecture Kernel Volume manager 2.6.18-194.el5 LVM2.02.56-8.el5 2.6.18-194.el5PAE 2.6.18-238.el5 LVM2.02.74-5.el5 2.6.18-238.el5PAE LVM2.02.84-3.el5 2.6.18-274.el5 LVM2.02.84-3.el5 2.6.18-274.el5PAE 2.6.18-8.el5 LVM2.02.16-3.el5 2.6.18-53.el5 LVM2.02.26-3.el5 2.6.18-92.el5 LVM2.02.32-4.el5 2.6.18-128.el5 LVM2.02.40-6.el5 2.6.18-164.el5 LVM2.02.46-8.el5 2.6.18-194.el5 LVM2.02.56-8.el5 2.6.18-238.el5 LVM2.02.74-5.el5 LVM2.02.84-3.el5 2.6.18-274.el5 LVM2.02.84-3.el5 EM64T/AMD64 2.6.18-8.el5 LVM2.02.16-3.el5 2.6.18-53.el5 LVM2.02.26-3.el5 2.6.18-92.el5 LVM2.02.32-4.el5 2.6.18-128.el5 LVM2.02.40-6.el5 2.6.18-164.el5 LVM2.02.46-8.el5...

  • Page 113

    Kernel architecture Kernel File system 2.6.18-53.el5 2.6.18-53.el5PAE 2.6.18-92.el5 2.6.18-92.el5PAE 2.6.18-128.el5 ext2 (supplied with the OS) 2.6.18-128.el5PAE ext3 (supplied with the OS) GFS2 (supplied with the OS) 2.6.18-164.el5 2.6.18-164.el5PAE 2.6.18-194.el5 2.6.18-194.el5PAE 2.6.18-238.el5 ext2 (supplied with the OS) 2.6.18-238.el5PAE ext3 (supplied with the OS) ext4 (supplied with the OS) 2.6.18-274.el5 GFS2 (supplied with the OS)

  • Page 114: Hdlm (if An Fc-san Is Used)

    Boot Disk Environments and BladeSymphony Environments Supported by HDLM (If an FC-SAN Is Used) HDLM supports BladeSymphony in any of the environments listed in Table 3-25 Operating Environments for BladeSymphony When Using Red Hat Enterprise Linux 5 on page 3-46. For details on OSs (kernels) that each BladeSymphony model supports, see the BladeSymphony documentation.

  • Page 115

    Supported storage Kernel architecture Kernel systems 2.6.18-92.el5PAE Virtual Storage Platform 2.6.18-128.el5 2.6.18-128.el5PAE 2.6.18-164.el5 2.6.18-164.el5PAE 2.6.18-194.el5 2.6.18-194.el5PAE 2.6.18-238.el5 2.6.18-238.el5PAE Emulex 2.6.18-274.el5 QLogic 2.6.18-274.el5PAE 2.6.18-8.el5 Emulex 2.6.18-53.el5 2.6.18-92.el5 2.6.18-128.el5 Brocade 2.6.18-164.el5 Emulex 2.6.18-194.el5 2.6.18-238.el5 Emulex 2.6.18-274.el5 EM64T/AMD64 2.6.18-8.el5 Emulex QLogic 2.6.18-53.el5 Brocade Emulex 2.6.18-92.el5 QLogic...

  • Page 116: Related Products When Using Red Hat Enterprise Linux 6

    environments when an HDLM device is used as a boot disk in a BladeSymphony environment. Table 3-27 Operating Environments for BladeSymphony and Boot Disks When Using Red Hat Enterprise Linux 5 Kernel Kernel Supported storage systems architecture IA32 2.6.18-53.el5PAE hitachi Hitachi AMS2000/AMS/WMS/ SMS series 2.6.18-92.el5PAE...

  • Page 117

    Cluster Software Supported by HDLM (If an FC-SAN Is Used) When you use HDLM in a cluster configuration, you must install the same version of HDLM on all the nodes that comprise the cluster. If different versions of HDLM are installed, the cluster system may not operate correctly. If the HDLM Version and Service Pack Version, which are displayed by executing the following command, are the same, the versions of HDLM are the same:...

  • Page 118: Boot Disk Environments Supported By Hdlm (if An Fc-san Is Used)

    Boot Disk Environments Supported by HDLM (If an FC-SAN Is Used) HDLM supports boot disks in any of the environments listed in Table 3-30 Operating Environments for Boot Disks When Using Red Hat Enterprise Linux 6 on page 3-50. For details on OSs (kernels) that each storage system model supports, see the storage system documentation.

  • Page 119: Related Products When Using Suse Linux Enterprise Server 10, File Systems Supported By Hdlm

    Notes on using a volume manager Note the following when using a volume manager: • Although disk partitioning and system backup functions are supported for disks in a YaST2 system, the combination of YaST2 and LVM is not supported. • When you execute an LVM-related command such as pvscan or vgscan, a CD-ROM IOCTL command might be sent to each device in the OS.

  • Page 120

    Table 3-31 Cluster Software When Using SUSE LINUX Enterprise Server 10 Kernel architecture Usable kernels Cluster software IA32 2.6.16.21-0.8-default Oracle RAC 10g Release 2 (10.2.0.3.0) 2.6.16.21-0.8-smp 2.6.16.21-0.8-bigsmp 2.6.16.46-0.14-default Heartbeat (2.0.8-0.19) 2.6.16.46-0.14-smp Oracle RAC 10g Release 2 (10.2.0.3.0) 2.6.16.46-0.14-bigsmp Oracle RAC 11g Release 1 (11.1.0.6.0) 2.6.16.60-0.21-default Heartbeat (2.1.3-0.9)

  • Page 121

    Kernel architecture Usable kernels Cluster software 2.6.16.60-0.54.5-smp 2.6.16.60-0.54.5-xen 2.6.16.60-0.85.1-default Heartbeat (2.1.4-0.24.9) 2.6.16.60-0.85.1-smp 2.6.16.60-0.85.1-xen Only configurations that include the Automatic Storage Management (ASM) function (using raw devices) and Cluster Ready Service (CRS) are supported. For details, see Settings for Oracle RAC on page 3-178.

  • Page 122

    Kernel architecture Kernel Volume manager 2.6.16.60-0.85.1-default LVM2.02.17-7.30.1 2.6.16.60-0.85.1-smp 2.6.16.60-0.85.1-bigsmp 2.6.16.60-0.85.1-xenpae 2.6.16.21-0.8-default LVM2.02.02-11.2 2.6.16.46-0.14-default LVM2.02.17-7.9 2.6.16.60-0.21-default LVM2.02.17-7.19 2.6.16.60-0.54.5-default LVM2.02.17-27.8 2.6.16.60-0.85.1-default LVM2.02.17-7.30.1 EM64T/AMD64 2.6.16.21-0.8-default LVM2.02.02-11.2 2.6.16.21-0.8-smp 2.6.16.46-0.14-default LVM2.02.17-7.9 2.6.16.46-0.14-smp 2.6.16.60-0.21-default LVM2.02.17-7.19 2.6.16.60-0.21-smp 2.6.16.60-0.21-xen 2.6.16.60-0.54.5-default LVM2.02.17-27.8 2.6.16.60-0.54.5-smp 2.6.16.60-0.54.5-xen 2.6.16.60-0.85.1-default LVM2.02.17-7.30.1 2.6.16.60-0.85.1-smp 2.6.16.60-0.85.1-xen Notes on using a volume manager Note the following when using a volume manager: •...

  • Page 123

    The system is started. ¢ You execute the utility for supporting a boot disk (dlmmkinitrd). ¢ File Systems Supported by HDLM When using a file system, the related programs are as follows: • ext2 (supplied with the OS) • ext3 (supplied with the OS) •...

  • Page 124

    Table 3-34 Operating Environments for Boot Disks When Using SUSE LINUX Enterprise Server 10 Kernel Kernel Supported storage systems architecture IA32 2.6.16.46-0.14- QLogic Hitachi AMS2000/AMS/WMS/SMS default series 2.6.16.46-0.14-smp Hitachi USP 2.6.16.46-0.14- Lightning 9900V series bigsmp Thunder 9500V series 2.6.16.60-0.21- Brocade Universal Storage Platform V/VM default QLogic...

  • Page 125

    Kernel Kernel Supported storage systems architecture 2.6.16.60-0.54.5- 2.6.16.60-0.54.5- 2.6.16.60-0.85.1- QLogic default 2.6.16.60-0.85.1- 2.6.16.60-0.85.1- Table 3-35 Operating Environments for BladeSymphony and Boot Disks When Using SUSE LINUX Enterprise Server 10 on page 3-57 lists the operating environments when an HDLM device is used as a boot disk in a BladeSymphony environment.

  • Page 126

    For details on the functions provided by ServerConductor/ DeploymentManager, see the manual ServerConductor/DeploymentManager User's Guide. Related Products When Using SUSE LINUX Enterprise Server 11 The following describes related products when SUSE LINUX Enterprise Server 11 is used. Volume Managers Supported by HDLM Table 3-36 Volume Managers When Using SUSE LINUX Enterprise Server 11 on page 3-58 lists and describes the related programs when using a volume...

  • Page 127: Related Products When Using Oracle Enterprise Linux 4, File Systems Supported By Hdlm

    This message is also output in the following cases, but HDLM operations are not affected: You execute the utility for collecting HDLM error information ¢ (DLMgetras). The system is started. ¢ File Systems Supported by HDLM When using a file system, the related programs are as follows: •...

  • Page 128: Volume Manager Supported By Hdlm, File Systems Supported By Hdlm

    Volume Manager Supported by HDLM Table 3-38 Volume Managers When Using Oracle Enterprise Linux 4 on page 3-60 lists and describes the related programs when using a volume manager. Table 3-38 Volume Managers When Using Oracle Enterprise Linux 4 Kernel architecture Kernel Volume manager IA32...

  • Page 129: Related Products When Using Oracle Enterprise Linux 5, Cluster Software Supported By Hdlm

    Kernel Kernel Supported storage systems architecture 2.6.9-67.0.0.0.1.EL Virtual Storage Platform 2.6.9-67.0.0.0.1.EL hugemem EM64T/AMD64 2.6.9-55.0.0.0.2.EL 2.6.9-55.0.0.0.2.EL 2.6.9-55.0.0.0.2.ELl argesmp 2.6.9-67.0.0.0.1.EL 2.6.9-67.0.0.0.1.EL 2.6.9-67.0.0.0.1.ELl argesmp Related Products When Using Oracle Enterprise Linux 5 The following describes related products when Oracle Enterprise Linux 5 is used.

  • Page 130

    Kernel architecture Usable kernels Cluster software 2.6.18-238.el5 2.6.18-238.el5PAE EM64T/AMD64 2.6.18-53.el5 Oracle RAC 11g Release 1(11.1.0.6.0) RHCM 2.0.73-1 2.6.18-164.el5 Oracle RAC 11g Release 2(11.2.0.2.0) 2.6.18-194.el5 None 2.6.18-238.el5 Only configurations that include the Automatic Storage Management (ASM) function (raw devices are used) and Cluster Ready Service (CRS) are supported.

  • Page 131: Boot Disk Environments Supported By Hdlm

    Table 3-42 Supported File Systems When Using Oracle Enterprise Linux 5 Kernel architecture Kernel File system IA32 2.6.18-53.el5 ext2 (supplied with the OS) 2.6.18-53.el5PAE ext3 (supplied with the OS) 2.6.18-164.el5 ext2 (supplied with the OS) 2.6.18-164.el5PAE ext3 (supplied with the OS) GFS2 (supplied with the OS) 2.6.18-194.el5 2.6.18-194.el5PAE...

  • Page 132: Memory And Disk Capacity Requirements, Memory Requirements

    Supported storage Kernel architecture Kernel systems 2.6.18-238.el5 Memory and Disk Capacity Requirements This section describes memory and disk capacity requirements. Memory Requirements Table 3-44 Memory Requirements for a Host on page 3-64 lists the memory requirements for a host. Table 3-44 Memory Requirements for a Host Required memory Red Hat Enterprise Linux 26 MB...

  • Page 133

    p is obtained by the following formula: p = (s x m) / 1024 [MB] Where s is the error log file size (unit: KB, default value: 9900) and m is the number of error log files (default value: 2). The result is rounded up to MB.

  • Page 134: Number Of Paths Supported In Hdlm

    The size of the configuration definition file. y is obtained by using the following formula: y = (2500 bytes x number-of-paths x 4) / 1024 / 1024 [MB] The result is rounded up to MB. The size of the file that defines non-HDLM-managed disks. z is obtained by using the following formula: z = (20 bytes x number-of-non-HDLM-managed-disks x 4) / 1024 / 1024 [MB]...

  • Page 135: Virtual Environments Supported By Hdlm

    Note that the range of values supported by HDLM is from 0 to 255. Therefore, do not assign an LU whose LUN is 256 or greater. Virtual Environments Supported by HDLM HDLM supports the following virtual environments: • HVM where the server virtualization mechanism is mounted on a BladeSymphony blade server •...

  • Page 136: Flow For Creating An Hdlm Environment

    Table 3-48 KVM Operating Environments Supported by HDLM Kernel Kernel KVM version architecture Red Hat Enterprise EM64T/AMD64 2.6.18-164.el5 KVM supplied with the Linux 5 OS is supported. 2.6.18-194.el5 2.6.18-238.el5 2.6.18-274.el5 Red Hat Enterprise EM64T/AMD64 2.6.32-71.el6.x86_ Linux 6 2.6.32-131.0.15.el6 .x86_64 Flow for Creating an HDLM Environment Set up the environment to use HDLM as shown in the following diagram.

  • Page 137: Hdlm Installation Types

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

  • Page 138: Knowledge Required Before You Install Hdlm

    Installing a new version of HDLM without uninstalling the existing old version is called an upgrade installation of HDLM. Re-installation of HDLM: Installing the same version of HDLM, to restore the existing version, without first uninstalling that version is called a re-installation of HDLM. Knowledge Required Before You Install HDLM •...

  • Page 139: Notes On Creating An Hdlm Environment, Notes On Hardware Settings

    Notes on Creating an HDLM Environment This section provides notes on creating an HDLM environment. For notes on operating HDLM, see Notes on Using HDLM on page 4-2. Notes on Hardware Settings • The types of HBA that are installed on one host can be mixed. However, the HBAs connected to an HDLM-managed device must all be of the same type.

  • Page 140: Notes On Linux

    sure that the following coding is in the line for INITRD_MODULES= in the / etc/sysconfig/kernel file. When using the QLA22XX HBA: ¢ qla2200 When using the QLA23XX HBA: ¢ qla2300 If qla2xxx is appears in the file instead of qla2200 or qla2300, change qla2xxx to qla2200 or qla2300 as follows: INITRD_MODULES="mptscsih qla2300 reiserfs"...

  • Page 141: Notes On Installing Hdlm

    An HDLM device for which automatic mounting is specified has not ¢ been mounted. An md device created on an HDLM device has not been activated. ¢ An LVM created on an HDLM device has not been activated. ¢ HDLM information is missing in the /etc/init.d/boot.localfs file, ¢...

  • Page 142: Notes On An Upgrade Installation Or Re-installation Of Hdlm

    # /sbin/service haldaemon stop Make sure that the HAL daemon is stopped. Execute the /sbin/service command to make sure that the HAL daemon is not running. # /sbin/service haldaemon status Execute the dlmcfgmgr utility (dlmcfgmgr -r or dlmcfgmgr -i) to configure the HDLM device.

  • Page 143: Notes On A Device Manager Agent, Installing Hdlm, Preparations For A New Installation Of Hdlm

    Notes on a Device Manager Agent • When installing HDLM on a host where Device Manager agent 5.0 or later is installed, do not execute any of the following commands of Device Manager agent during installation: hbsasrv, HiScan, hdvmagt_account, hdvmagt_schedule, hldutil, TIC Installing HDLM The following section describes how to install HDLM for a new installation, for a re-installation, and for an upgrade installation.

  • Page 144: Checking The Volume Group

    When accessing a device that is to be managed after HDLM installation, the setting name used until now cannot be used for access because the logical device file name for the HDLM device that HDLM creates is used. Unmount the disks. If the disks to be managed by HDLM were mounted by specifying SCSI devices, unmount them.

  • Page 145

    Migration is not affected even when a logical volume or file system has been created. • A physical volume is created for only one of the logical device files on any one path for each SCSI device to be managed by HDLM. In addition, a volume group is created for only the physical volume.

  • Page 146: Setting In The Syslogd Settings File

    Figure 3-5 Result of Executing vgdisplay -v (When There Are Two Physical Volumes) Check the shaded portion and confirm that vg02 consists of /dev/sde and / dev/sdu, both of which have been defined for the same device to be managed by HDLM. Setting in the syslogd Settings File The log upon executing the installation is output to syslog.

  • Page 147: Performing A New Installation Of Hdlm

    Figure 3-6 Example of the Contents of the syslogd Settings File (In Red Hat Enterprise Linux) When you collect audit log data, we recommend that you use any of the extended facilities (local0 to local7) as the exclusive output destination for the data.

  • Page 148

    Store the license key file (*.plk) in the /var/tmp directory, under the ¢ name hdlm_license. /var/tmp/hdlm_license Execute the following commands to create the license key file ¢ (dlm.lic_key) in the /etc/opt/DynamicLinkManager directory. # mkdir /etc/opt/DynamicLinkManager # echo "license-key" > /etc/opt/DynamicLinkManager/dlm.lic_key Insert the DVD-ROM and mount it.

  • Page 149

    To copy the DVD-ROM to a directory, and then install HDLM from that directory, copy the DVD-ROM to a directory with the same name as the mount point noted above. If the file permissions or the directory structure differs, HDLM cannot be installed. This refers to the volume name for the CD-ROM or other media, formatted for ISO-9660 file systems.

  • Page 150

    The KAPL09093-I message is displayed to confirm that you want to perform a new installation. Check the HDLM version, and if it is correct, enter y. The license key file will be deleted when installation finishes. Make sure that HDLM is installed. Execute the following command to display detailed information about the installed package.

  • Page 151

    A path will be established in the HDLM device and the HDLM manager will start. If you have edited the /etc/fstab file as described in Operations Required for Devices to Be Managed by HDLM on page 3-75 Preparations for a New Installation of HDLM on page 3-75, add the line show below to change the setting from a SCSI device specification to an HDLM device specification.

  • Page 152: Preparations For An Upgrade Installation Or Re-installation Of Hdlm

    For details on setting the cluster software, see Settings for Heartbeat on page 3-178, Settings for Oracle RAC on page 3-178, Settings for the RHCM on page 3-181, or Settings for VCS on page 3-183. Execute the dlnkmgr command's view operation to check the HDLM settings and status of each program.

  • Page 153: Operations Required For Devices To Be Managed By Hdlm, Deactivating The Md Devices

    For details on how to re-install HDLM, see Performing a Re-installation of HDLM on page 3-86. For details on how to upgrade-install HDLM, see Performing an Upgrade Installation of HDLM on page 3-91. Operations Required for Devices to Be Managed by HDLM Before performing an upgrade installation or re-installation of HDLM, you must unmount the HDLM devices that correspond to HDLM-managed devices, and then back up the HDLM-managed devices.

  • Page 154

    0 logical volume(s) in volume group "vg01" now active Setting Up Xen If Xen is being used, make sure that domainU has been stopped. If domainU has been set up to automatically start whenever domain0 starts, temporarily change the setting so that domainU will not start automatically. Performing a Re-installation of HDLM The following is the procedure for a re-installation.

  • Page 155

    # mount /dev/cdrom /media/cdrom For details about the fixed mount point for each distribution, see Table 3-50 Mount Point for Each Distribution on page 3-87. Table 3-50 Mount Point for Each Distribution Distribution Mount point Red Hat Enterprise Linux AS4/ •...

  • Page 156

    Execute installux.sh or the HDLM installation utility (installhdlm) stored on the HDLM DVD-ROM to check the version of HDLM that will be installed. The following example shows how to execute the command when the mount point for the DVD-ROM is /media/cdrom: When executing installux.sh ¢...

  • Page 157

    For details on this utility, see dlmsetopt Utility for Setting HDLM Driver Options on page 7-35. If you performed this step, go to step 11. When you want to install HDLM without restarting the host, go to step 10. When you want to install HDLM with restarting the host, then go to step Execute the dlmstart utility for starting HDLM.

  • Page 158

    Perform this step if your host OS uses LUKS. If HDLM manages a SCSI device that has been configured to use LUKS, the LUKS settings must be migrated from the SCSI device to an HDLM device. For details on setting up LUKS, see Settings for LUKS on page 3-152.

  • Page 159: Performing An Upgrade Installation Of Hdlm

    If you are using Xen, set up Xen to use HDLM devices in domainU. If you are using KVM, register HDLM devices into the hardware configuration file. For details on operating environments for the virtual environments supported by HDLM, see Virtual Environments Supported by HDLM on page 3-67.

  • Page 160

    The following shows an example of command execution when the mount point is /media/cdrom: # mount /dev/cdrom /media/cdrom For details about the fixed mount point for each distribution, see Table 3-51 Mount Point for Each Distribution on page 3-92. Table 3-51 Mount Point for Each Distribution Distribution Mount point Red Hat Enterprise Linux AS4/...

  • Page 161

    Check the version of HDLM. Execute installux.sh or the HDLM installation utility (installhdlm) stored on the HDLM DVD-ROM to check the version of HDLM that will be installed. The following example shows how to execute the command when the mount point for the DVD-ROM is /media/cdrom: When executing installux.sh ¢...

  • Page 162

    If IP-SAN is used for the connection between the host and the storage system, change iscsi_boot=n, written in the /etc/opt/ DynamicLinkManager/hdlm.conf file, to iscsi_boot=y. When you want to set the HDLM driver options, run the dlmsetopt utility for setting HDLM driver option. For details on this utility, see dlmsetopt Utility for Setting HDLM Driver Options on page...

  • Page 163

    Add the shaded line shown in the above figure. Specify the settings required for using LUKS. Perform this step if your host OS uses LUKS. If HDLM manages a SCSI device that has been configured to use LUKS, the LUKS settings must be migrated from the SCSI device to an HDLM device.

  • Page 164: Unattended Installation Of Hdlm

    # vgchange -ay vg01 vgchange -- volume group "vg01" successfully activated Mount the logical volume that was moved. In the following example, the logical volume is /dev/vg01/lvol1 and the command mounts the volume on /mnt/lvol1: # mount /dev/vg01/lvol1 /mnt/lvol1 Specify the settings required for using virtual environments. If you are using Xen, set up Xen to use HDLM devices in domainU.

  • Page 165

    For an unattended installation, you can specify any directory to store the license key file. For details, see Editing an Installation-Information Settings File on page 7-42. Insert the DVD-ROM and mount it. If the DVD-ROM was not automatically mounted, execute the mount command to mount the DVD-ROM to the fixed mount point.

  • Page 166

    The following shows an execution example for when media-volume-id is VOL01234. # volname /dev/cdrom VOL01234 Check the version of HDLM. Execute installux.sh or the HDLM installation utility (installhdlm) stored on the HDLM DVD-ROM to check the version of HDLM that will be installed.

  • Page 167

    # /media/cdrom/installux.sh -f /any-directory/installation- information-settings-file When executing the installhdlm utility ¢ # /media/cdrom/HDLM_Linux/installhdlm -f /any-directory/ installation-information-settings-file Note that, if you edited the installation information settings file in step 5 so that the host is restarted, the host is automatically restarted. Make sure that HDLM is installed.

  • Page 168

    Add the shaded line shown in the above figure. Specify the settings required for using LUKS. Perform this step if your host OS uses LUKS. If HDLM manages a SCSI device that has been configured to use LUKS, the LUKS settings must be migrated from the SCSI device to an HDLM device.

  • Page 169: Installing Hdlm For Managing Boot Disks, Notes On Installing Hdlm In A Boot Disk Environment

    If you are using Xen, set up Xen to use HDLM devices in domainU. If you are using KVM, register HDLM devices into the hardware configuration file. For details on operating environments for the virtual environments supported by HDLM, see Virtual Environments Supported by HDLM on page 3-67.

  • Page 170

    In this case, if a problem occurs, use the log displayed on the console to analyze the problem. • The dlmcfgmgr log created at startup is output to /etc/opt/ DynamicLinkManager/hdlmboot.log. • Once you have built an environment for starting the OS from an HDLM device, you cannot change the boot disk.

  • Page 171

    Upgrade Installation in an Environment Where an HDLM Device Is Used as a Boot Disk on page 3-116 and perform operations while reading the SCSI device names in those subsections as the new SCSI device names (udev name) that were changed by using the udev function. In an environment where HDLM has been installed, you can use the dlmcfgmgr utility to check the correspondence between a SCSI device and a udev name.

  • Page 172: Overview Of The Procedure For Installing Hdlm In A Boot Disk Environment

    Overview of the Procedure for Installing HDLM in a Boot Disk Environment This subsection provides an overview of the procedure for installing HDLM in a boot disk environment. Settings for Using an HDLM Device as a Boot Disk Check whether LABEL is used. If it is, remove it. To use HDLM, you must remove the LABEL setting, because a SCSI device cannot be identified from the value set in LABEL in an HDLM environment.

  • Page 173: Upgrade Installation In An Environment Where A Logical Volume (lvm2) On An Hdlm Device Is Used As A Boot Disk

    Settings for Using a Logical Volume (LVM2) on an HDLM Device as a Boot Disk To migrate a single-path boot disk environment that uses a logical volume (LVM2) on a SCSI device to a multi-path boot disk environment that uses a logical volume on an HDLM device (for details, see Settings for Using a Logical Volume (LVM2) on an HDLM Device as a Boot Disk on page...

  • Page 174: For Suse Linux Enterprise Server 10 Or Suse Linux Enterprise Server

    After completing the above procedure, you can perform an upgrade installation of HDLM in a multi-path boot disk environment that uses a logical volume (LVM2) on an HDLM device. Settings for Using an HDLM Device as a Boot Disk This subsection describes how to perform a new installation of HDLM in a single-path boot disk environment that uses a SCSI device and how to set up the environment.

  • Page 175

    When GRUB is used as the boot loader with Xen kernels: ¢ For details on Xen kernels, see Table 3-47 Xen Hypervisor Operating Environments Supported by HDLM on page 3-67. title XEN root (hd0,0) kernel /xen-pae.gz module /vmlinuz-2.6.16.60-0.54.5-xenpae \ root=/dev/disk/by-id/scsi-SFUJITSU_MAS3735NC_A050P360007N- part6 vga=0x317 \ resume=/dev/disk/by-id/scsi- SFUJITSU_MAS3735NC_A050P3600077-part2 \...

  • Page 176

    defaults /dev/disk/by-id/scsi-1HITACHI_D60H03750019-part3 / ext3 acl,user_xattr 1 1 Check the definition in the boot loader configuration file. Check whether LABEL is used in the definition in the boot loader configuration file. The following shows examples for LABEL. When GRUB is used as the boot loader with non-Xen kernels: ¢...

  • Page 177

    Xen Hypervisor Operating Environments Supported by HDLM on page 3-67. title XEN root (hd0,1) kernel /boot/xen.gz module /boot/vmlinuz-2.6.16.60-0.21-xen root=/dev/disk/by-id/ scsi-1HITACHI_D60H03750027-part2 vga=0x31a resume=/dev/sda1 splash=silent showopts module /boot/initrd-2.6.16.60-0.21-xen If LABEL or the device name (udev name) was not used in step 3 and step 4, proceed to step 17 and install a new instance of HDLM.

  • Page 178

    Execute the udevinfo command. Specify the device name (udev name) in the /dev/disk directory for -n. # udevinfo -q name -n /dev/disk/by-id/scsi-2000c50fffecb6ae0- part2 sda2 The sda2 value output is the SCSI device name corresponding to / dev/disk/by-id/scsi-2000c50fffecb6ae0-part2. Back up the /etc/fstab file. Edit the /etc/fstab file, and delete the LABEL setting.

  • Page 179

    When GRUB is used as the boot loader with non-Xen kernels: ¢ For details on kernels supported by HDLM, see Hosts and OSs Supported by HDLM on page 3-3. title Red Hat Enterprise Linu Linux (2.6.18-194.el5) root (hd0,0) kernel /vmlinuz-2.6.18-194.el5 ro option root=LABEL=/ option initrd /initrd-2.6.18-194.el5 When LILO or ELILO is used as the boot loader:...

  • Page 180

    Change the root specification on the kernel line to root=SCSI- device. When LILO or ELILO is used as the boot loader: ¢ Change the specification for root to root=SCSI-device. If no options have been specified to suit the user environment, delete or comment out the append line.

  • Page 181

    The following shows an example of executing the command: # /sbin/dracut /boot/initramfs-hdlm-2.6.32-71.el6.i686.img `uname -r` For OSs other than the above: ¢ Execute the utility for supporting a boot disk (dlmmkinitrd). For details on the dlmmkinitrd utility, see dlmmkinitrd Utility for Supporting a Boot Disk on page 7-31.

  • Page 182

    title sd-Red Hat Enterprise Linux (2.6.18-194.el5) After: title HDLM-Red Hat Enterprise Linux (2.6.18-194.el5) When LILO or ELILO is used as the boot loader: ¢ Change the underlined text as follows: Before: label=linux-sd After: label=linux-HDLM Edit the root specification written in the boot loader configuration file. From the following, perform the procedure that corresponds to the host For Red Hat Enterprise Linux 6: ¢...

  • Page 183

    Change the initrd specification in the configuration that you copied in step 23. If you are using a Xen kernel, change the initrd file name specified in module to the initial RAM disk image file you created in step 19. For details on Xen kernels, see Table 3-47 Xen Hypervisor Operating Environments Supported by HDLM on page...

  • Page 184: Disk

    /dev/sddlmaa6 on /usr type ext2 (rw) none on /dev/shm type tmpfs (rw) Check the underlined section. If Red Hat Enterprise Linux, SUSE LINUX Enterprise Server 10, or SUSE LINUX Enterprise Server 11 is used, make sure that the HDLM device is allocated to the swap partition.

  • Page 185

    When LILO is used as the boot loader: ¢ Root directory (/), /tmp, /usr, /var, swap The following shows an example of the /etc/fstab file: /dev/sddlmaa2 ext2 defaults /dev/sddlmaa4 /tmp ext2 defaults Execute the HDLM-configuration definition utility (dlmcfgmgr) with the -v parameter specified to check the correspondence between the HDLM device and the SCSI device.

  • Page 186

    title XEN root (hd0,1) kernel /boot/xen.gz module /boot/vmlinuz-2.6.16.60-0.21-xen vga=0x31a splash=silent showopts module /boot/initrd-2.6.16.60-0.21-xen.hdlm When GRUB is used as the boot loader with non-Xen kernels: ¢ For details on kernels supported by HDLM, see Hosts and OSs Supported by HDLM on page 3-3.

  • Page 187

    Change the specification for root contained in the configuration that you copied in step 5. When GRUB is used as the boot loader: ¢ Add root=SCSI-device to the kernel line. title Red Hat Enterprise Linux (2.6.18-194.el5) root (hd0,0) kernel /vmlinuz-2.6.18-194.el5 ro option ramdisk_size=18958 root=/dev/sda2 option When LILO or ELILO is used as the boot loader: ¢...

  • Page 188

    Start the host. Execute the mount command to make sure that the SCSI device is mounted. The following shows an execution example for when GRUB is used as the boot loader: # mount /dev/sda2 on / type ext2 (rw) /dev/sda1 on /boot type ext2 (rw) /dev/sda4 on /tmp type ext2 (rw) /dev/sda5 on /var type ext2 (rw) /dev/sda6 on /usr type ext2 (rw)

  • Page 189

    # /sbin/dracut /boot/initramfs-hdlm-2.6.32-71.el6.i686.img `uname -r` For OSs other than the above: ¢ Execute the utility for supporting a boot disk (dlmmkinitrd). If the initial RAM disk image file to be created already exists and you are using Red Hat Enterprise Linux AS4/ES4 or Red Hat Enterprise Linux 5, specify the -f parameter to overwrite this file.

  • Page 190

    /dev/sda2 on / type ext4 (rw) proc on /proc type proc (rw) Check the underlined device name. Execute the blkid command to check the UUID of the device that you checked above. The following shows an example of executing the command. # blkid /dev/sda2 /dev/sda2: UUID="19597725-5d20-4d1d-9906-f9f891b7711a"...

  • Page 191

    Edit the /etc/fstab file. Change the mount points for the following HDLM management-target devices from the SCSI device to the HDLM device: When ELILO is used as the boot loader: ¢ Root directory (/), /boot/efi, /tmp, /usr, /var, swap When GRUB is used as the boot loader: ¢...

  • Page 192: Settings For Using A Logical Volume (lvm2) On An Hdlm Device As A Boot Disk

    If Red Hat Enterprise Linux, SUSE LINUX Enterprise Server 10, or SUSE LINUX Enterprise Server 11 is used, make sure that the HDLM device is allocated to the swap partition. Make sure that the HDLM device name is displayed in the Filename column of the /proc/swaps file.

  • Page 193

    kernel /xen-pae.gz module /vmlinuz-2.6.16.60-0.54.5-xenpae \ root=/dev/disk/by-id/scsi-SFUJITSU_MAS3735NC_A050P360007N- part6 vga=0x317 \ resume=/dev/disk/by-id/scsi- SFUJITSU_MAS3735NC_A050P3600077-part2 \ splash=silent showopts multipath=off module /initrd-2.6.16.60-0.54.5-xenpae multipath=off is set in the underlined section. When GRUB is used as the boot loader with non-Xen kernels: ¢ For details on kernels supported by HDLM, see Hosts and OSs Supported by HDLM on page 3-3.

  • Page 194

    Figure 3-9 Example of Executing the mount Command on page 3-126 shows an example of executing the mount command. Figure 3-9 Example of Executing the mount Command The shaded portion indicates the SCSI device for which LABEL is set. This example assumes that IA32 uses GRUB as the boot loader. When you use IPF that uses ELILO as the boot loader, the mount point is displayed as /boot/efi instead of /boot (in the line where /boot is coded), and the file system type is displayed as vfat instead of ext3.

  • Page 195

    For SUSE LINUX Enterprise Server 10 or SUSE LINUX Enterprise ¢ Server 11 Execute the udevinfo command. Specify the device name (udev name) in the /dev/disk directory for -n. # udevinfo -q name -n /dev/disk/by-id/scsi-2000c50fffecb6ae0- part1 sda1 The sda1 value output is the SCSI device name corresponding to / dev/disk/by-id/scsi-2000c50fffecb6ae0-part1.

  • Page 196

    procedure differs depending on whether the host is restarted after installation. In steps 12 to 27 that follow, you will edit the configuration file to change the definition so that the OS starts with HDLM specified. Execute the HDLM-configuration definition utility (dlmcfgmgr) with the -v parameter specified to check the correspondence between the HDLM device and the SCSI device.

  • Page 197

    Change hdlm_dracut=n defined in the /etc/opt/ DynamicLinkManager/hdlm.conf file to hdlm_dracut=y. Execute the dracut command. The following shows an example of executing the command: # /sbin/dracut /boot/initramfs-hdlm-2.6.32-71.el6.i686.img `uname -r` For OSs other than the above: ¢ Execute the utility for supporting a boot disk (dlmmkinitrd). For details on the dlmmkinitrd utility, see dlmmkinitrd Utility for Supporting a Boot Disk on page...

  • Page 198

    Edit the /etc/fstab file. Change the /boot mount point that you changed in step 8 from the SCSI device to the HDLM device. Comment out the existing SCSI device specification by placing a hash mark (#) at the beginning of each line, and then add the HDLM device specification as shown below, based on the correspondence between the HDLM device and the SCSI device as checked in step 11.

  • Page 199

    Figure 3-12 Example of Editing /etc/grub.conf file Edit the shaded portion. Figure 3-13 Example of Editing /boot/grub/menu.lst file (When using a kernel that supports Xen) Edit the shaded portion. 3-131 Creating an HDLM Environment Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 200

    Figure 3-14 Example of Editing /etc/elilo.conf file Edit the shaded portion. If necessary, back up the file. Copy the configuration that was used for startup from the SCSI device. Assign a name to the copied configuration that indicates that the configuration is used for specifying the HDLM device.

  • Page 201

    root=/dev/mapper/systemvg-rootlv To specify a UUID for root: Execute the mount command to check the root device name. Below is an example of executing the command. The underlined part is the root device name. # mount /dev/mapper/systemvg-rootlv on / type ext4 (rw) proc on /proc type proc (rw) Execute the blkid command to check the UUID of the root device name that you checked above.

  • Page 202

    Shut down the host. Execute the following command to shut down the host: # shutdown -h now Change the configuration from a single-path configuration to a multi-path configuration. Start the host. Update the information about the volume group. Execute the following command to update the information about the volume group.

  • Page 203: Device Is Used As A Boot Disk

    Upgrade Installation in an Environment Where a Logical Volume (LVM2) on an HDLM Device Is Used as a Boot Disk This subsection describes how to perform an upgrade installation of HDLM in a multi-path boot disk environment that uses a logical volume (LVM2) on an HDLM device.

  • Page 204

    Make sure that the HDLM device is defined in the /etc/fstab file. /dev/sddlmaa1 /boot ext3 defaults This example assumes that IA32 uses GRUB as the boot loader. When you use IPF that uses ELILO as the boot loader, the mount point is displayed as /boot/efi instead of /boot in the line where /boot is coded, and the file system type is displayed as vfat instead of ext3.

  • Page 205

    Edit the /etc/lvm/lvm.conf file so that the LVM2 recognizes the SCSI device, not the HDLM device. Figure 3-15 Example of Editing /etc/lvm/lvm.conf file on page 3-138 shows an example of editing the /etc/lvm/lvm.conf file. 3-137 Creating an HDLM Environment Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 206

    Figure 3-15 Example of Editing /etc/lvm/lvm.conf file Comment out the existing filter and types lines, and add the shaded lines in the figure. In addition, set md_component_detection to its original value before installation. Edit the boot loader configuration file so that the OS will start with a SCSI device specified.

  • Page 207

    Figure 3-16 Example of Editing /etc/grub.conf file Edit the shaded portion. Figure 3-17 Example of Editing /boot/grub/menu.lst file (When using a kernel that supports Xen) Edit the shaded portion. 3-139 Creating an HDLM Environment Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 208

    Figure 3-18 Example of Editing /etc/elilo.conf file Edit the shaded portion. Copy the configuration that was used for startup from the HDLM device. Assign a name to the copied configuration. You can assign any name that indicates that the configuration is used for specifying the SCSI device.

  • Page 209

    When ELILO is the boot loader ¢ Specify label for default. Shut down the host. Execute the following command to shut down the host: # shutdown -h now Change the configuration from a multi-path configuration to a single-path configuration. Start the host. Execute the mount command to check that the SCSI device is mounted in /boot.

  • Page 210

    Perform an upgrade installation of HDLM. To perform an upgrade installation of HDLM, see Performing an Upgrade Installation of HDLM on page 3-91, perform steps 2 to 12 to create an HDLM device. You will also need to perform step 13 if you are only restarting the host.

  • Page 211

    The HDevName column indicates the HDLM device, and the Device column indicates the SCSI device. Edit the /etc/lvm/lvm.conf file so that the LVM2 recognizes the HDLM device, not the SCSI device. Figure 3-19 Example of Editing /etc/lvm/lvm.conf file on page 3-143 shows examples of editing the /etc/lvm/lvm.conf file.

  • Page 212

    If the initial RAM disk image file to be created already exists and you are using Red Hat Enterprise Linux AS4/ES4 or Red Hat Enterprise Linux 5, specify the -f parameter to overwrite this file. If you are using SUSE LINUX Enterprise Server 10 or SUSE LINUX Enterprise Server 11, this file is overwritten even if you do not specify the parameter.

  • Page 213

    Execution example of the command when GRUB as the boot loader is ¢ used # rm /boot/initrd-hdlm-2.6.9-11.EL.gz Execution example of the command when IPF (with ELILO as the boot ¢ loader) is used # rm /boot/efi/efi/redhat/initrd-hdlm-2.6.9-11.EL.gz Edit the /etc/fstab file. Change the /boot mount point that you changed in step 4 from the SCSI device to the HDLM device.

  • Page 214

    Figure 3-20 Example of Editing /etc/grub.conf file Edit the shaded portion. Figure 3-21 Example of Editing /boot/grub/menu.lst file (When using a kernel that supports Xen) Edit the shaded portion. 3-146 Creating an HDLM Environment Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 215

    Figure 3-22 Example of Editing /etc/elilo.conf file Edit the shaded portion. Copy the configuration that was used for startup from the HDLM device. Assign a name to the copied configuration that indicates that the configuration is used for specifying the HDLM device after update. If you will use GRUB as the boot loader ¢...

  • Page 216

    /dev/mapper/systemvg-rootlv on / type ext4 (rw) proc on /proc type proc (rw) Change the root specification contained in the configuration that you copied in step 28 to the root device name checked above. root=/dev/mapper/systemvg-rootlv To specify a UUID for root: Execute the mount command to check the root device name.

  • Page 217

    Specify the position of the valid title for default. When ELILO is the boot loader ¢ Specify label for default. Shut down the host. Execute the following command to shut down the host: # shutdown -h now Change the configuration from a single-path configuration to a multi-path configuration.

  • Page 218: Countermeasures For Unsuccessful Startup Of The Os From An Hdlm Device

    Countermeasures for Unsuccessful Startup of the OS from an HDLM Device This subsection explains what actions you should take if the OS cannot be started from an HDLM device. If startup of the OS fails, either of the following happens: •...

  • Page 219: When An Error Message Appears And The Os Stops

    When an Error Message Appears and the OS Stops The probable causes of this error are as follows: Cause 1 The initial RAM disk image file was specified incorrectly in the boot loader configuration. Cause 2 The initial RAM disk image file is corrupted. Cause 3 The startup disk was no longer recognized first because the system environment configuration was modified.

  • Page 220: Notes On Using Luks

    To correct the above error: Enter the root user password. Execute mount -o remount rw / to mount the root directory again. In the /etc/fstab file, change the mount destination of root to the SCSI device. Restart the host to start the OS from the SCSI device. To restart the OS from an HDLM device, set up the environment according to the following procedure: Follow the procedure in...

  • Page 221: Using Hdlm In An Luks Environment

    Using HDLM in an LUKS Environment This subsection describes how to migrate LUKS from a SCSI device environment using LUKS to HDLM devices. To migrate from /dev/sdh to /dev/sddlmaa: Check the HDLM device to be migrated from the SCSI device. Execute the HDLM-configuration definition utility (dlmcfgmgr) with the -v parameter specified to check the correspondence between the SCSI device and the HDLM device.

  • Page 222: Settings For Md Devices, Notes On Setting Up Md Devices

    The following shows an example of changing the setting in the /etc/ crypttab file's second field. Before: luks-volume1 UUID=”050f9901-3ab8-4556-a091-9c6e4a404f09” /etc/ cryptpassword1 After: luks-volume1 /dev/sddlmaa /etc/cryptpassword1 Unmap the SCSI device from the device used by the device mapper. The following shows an example of unmapping the SCSI device from the /dev/mapper/luks-volume1 device.

  • Page 223: Creating An Md Device

    • In mdadm package versions 1.6.0-2 or earlier, you cannot manage devices whose major or minor number is 256 or greater. Use mdadm package versions 1.6.0-3 or later. • You cannot simultaneously specify SCSI devices and HDLM devices to configure an md device. Figure 3-23 Example of Incorrectly Configured md Devices on page 3-155 shows an example when SCSI devices and...

  • Page 224

    During this procedure, /dev/md0 is created on /dev/sddlmaa1 and /dev/ sddlmab1. Use the following procedure to configure the environment shown in Figure 3-25 Device Configuration When Creating an md Device on an HDLM Device on page 3-156. Figure 3-25 Device Configuration When Creating an md Device on an HDLM Device To create an md device: Create a disk partition.

  • Page 225

    /dev/sddlmaa1 1018 5238597 Linux Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. Syncing disks. Also perform the above operation for /dev/sddlmab. Create an md device. In the following example, RAID1 (mirroring) is used for the md device: # mdadm -C /dev/md0 -l1 -n2 /dev/sddlmaa1 /dev/sddlmab1 mdadm: /dev/sddlmaa1 appears to contain an ext2fs file system size=5238592K...

  • Page 226: Using Hdlm In An Md Device Environment

    Edit the configuration file created in step 5. Edit the /etc/mdadm.conf file to add auto=yes to the ARRAY line: DEVICE /dev/sddlmaa1 /dev/sddlmab1 ARRAY /dev/md0 level=raid1 num-devices=2 UUID=e39a6b15:32e48a5d:ca05f4db:25bc8af9 auto=yes Restart the host. Make sure that the md device has been activated. In the following example, RAID1 (mirroring) is used for the md device: # cat /proc/mdstat Personalities : [raid1]...

  • Page 227

    Figure 3-26 Device Configuration Where an md Device on a SCSI Device Is Migrated to an HDLM Device (An Environment that Uses the md Device's RAID Functionality) To migrate /dev/md0: Stop all applications that are using the existing md device. If necessary, back up the application data residing on the md device.

  • Page 228

    # mdadm --detail --scan | grep -w “/dev/md0” >> /etc/mdadm.conf For sdh1 and sdi1, specify the SCSI devices displayed in step 4. The following example shows the contents of the created configuration file: The underlined part indicates the lines added in this step. # cat /etc/mdadm.conf DEVICE /dev/sdh1 /dev/sdi1 DEVICE /dev/sdf1 /dev/sdg1 /dev/sdh1 /dev/sdi1...

  • Page 229

    ARRAY /dev/md0 level=raid1 num-devices=2 UUID=e39a6b15:32e48a5d:ca05f4db:25bc8af9 auto=yes Execute the following command to deactivate the md device. # mdadm -Ss /dev/md0 Make sure that the md device has been deactivated. In the following example, RAID1 (mirroring) is used for the md device: # cat /proc/mdstat Personalities : [raid1] unused devices: <none>...

  • Page 230: When The Multipath Function Is Being Used For Md Devices

    Disk /dev/sddlmaa: 5368 MB, 5368709120 bytes 166 heads, 62 sectors/track, 1018 cylinders Units = cylinders of 10292 * 512 = 5269504 bytes Device Boot Start Blocks System /dev/sddlmaa1 1018 5238597 Linux raid autodetect Command (m for help): t Selected partition 1 Hex code (type L to list codes): 83 Changed system type of partition 1 to 83 (Linux) Command (m for help): p...

  • Page 231

    how to migrate an md device for which the MULTIPATH function is used to an md device for which the LINEAR function is used. In this procedure, the device /dev/md0 on /dev/sdo1 and /dev/sdh1 is migrated to the device /dev/md0 on /dev/sddlmaa1. Use the following procedure to configure the environment shown in Figure 3-27 Device Configuration Where an md Device (An Environment that Uses the md...

  • Page 232

    Execute the HDLM-configuration definition utility dlmcfgmgr with the -v parameter specified: # dlmcfgmgr -v HDevName Management Device Host Channel Target Lun /dev/sddlmaa configured /dev/sdh /dev/sdo KAPL10302-I /sbin/dlmcfgmgr completed normally. The HDevName and Device columns display HDLM devices and SCSI devices, respectively. Create an md device.

  • Page 233

    DEVICE /dev/sdo1 /dev/sdh1 ARRAY /dev/md0 level=multipath num-devices=2 UUID=6b2ec21b: 06d0f50b:bbf04d32:1e00b09a auto=yes ARRAY /dev/md0 level=linear num-devices=1 UUID=426a9f1c: 9cfa6310:6aa9a80b:11ea2102 Edit the /etc/mdadm.conf file to add auto=yes to the ARRAY line in the configuration file: DEVICE /dev/sdo1 /dev/sdh1 ARRAY /dev/md0 level=linear num-devices=1 UUID=426a9f1c: 9cfa6310:6aa9a80b:11ea2102 auto=yes On the DEVICE line of the configuration file, change a SCSI device name to an HDLM device name.

  • Page 234: Settings For Lvm2, Notes On Using Lvm2

    Settings for LVM2 This section describes the procedure for setting the following items in an LVM2 environment: • When using an HDLM device to create a new logical volume • When moving a logical volume created on a SCSI device in a single-path environment, to an HDLM device When using HDLM in an LVM2 environment, use the HDLM device as an LVM2 physical volume.

  • Page 235

    Figure 3-28 Device configuration When Creating a Logical Volume on an HDLM Device To create a new logical volume on an HDLM device: Stop all processes and services that are using the HDLM device. Create a disk partition on the HDLM device and change the system ID from Linux (83 in hexadecimal representation) to Linux LVM (8e in hexadecimal representation).

  • Page 236

    Example of executing the parted command (IA32, IPF or EM64T/AMD64): 3-168 Creating an HDLM Environment Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 237

    When you use the parted command to change the partition, to let the system recognize the partitions on the HDLM device, execute the blockdev command after the parted command. Edit the /etc/lvm/lvm.conf file. Edit the device section in the file as shown below to disable the SCSI device configuration and enable the HDLM device configuration: Adding and deleting filter entry information ¢...

  • Page 238

    Figure 3-29 Example of Editing the /etc/lvm/lvm.conf File Create the physical volumes. The following example shows how to define /dev/sddlmad1 and /dev/ sddlmad2 as physical volumes: # pvcreate /dev/sddlmad1 Physical volume "/dev/sddlmad1" successfully created # pvcreate /dev/sddlmad2 Physical volume "/dev/sddlmad2" successfully created Create a volume group.

  • Page 239: Environment To An Hdlm Device

    Create the logical volume. In the following example, the command creates the logical volume (lvol1: 100 MB) by using the vg01 volume group: # lvcreate -L 100M -n lvol1 vg01 Logical volume "lvol1" created Create a file system. The following example shows how to use the mke2fs command to create a file system on the lvol1 logical volume: # mke2fs /dev/vg01/lvol1 Filesystem label=...

  • Page 240

    Figure 3-30 Device Configuration When a Logical Volume on a SCSI Device Is Moved to an HDLM Device Figure 3-30 Device Configuration When a Logical Volume on a SCSI Device Is Moved to an HDLM Device on page 3-172, sdn indicates the different LUs. sddlmad1 and sddlmad2 indicate the HDLM devices corresponding to each LU.

  • Page 241

    In the following example, the logical volume subject to the move has been mounted on /mnt/lvol1: # umount /mnt/lvol1 Deactivate the volume group. In the following example, the logical volume to be moved belongs to the vg01 volume group: # vgchange -an vg01 0 logical volume(s) in volume group "vg01"...

  • Page 242

    Figure 3-31 Example of Editing the /etc/lvm/lvm.conf File Execute the VG scan. To re-create the volume group on the HDLM device, execute the vgscan command as shown in the following example: # vgscan Reading all physical volumes. This may take a while... Found exported volume group "vg01"...

  • Page 243: Settings For Xen

    Execute the following command to make sure that the information about the physical volume for the target logical volume has been changed to the information about the HDLM device: # pvscan PV /dev/sddlmad1 VG vg01 lvm2 [468.00 MB / 368.00 MB free] PV /dev/sddlmad2 VG vg01 lvm2 [548.00 MB / 548.00 MB free]...

  • Page 244

    HDLM devices are listed in the HDevName column, and SCSI devices are listed in the Device column. Check whether the SCSI devices can be migrated to the HDLM devices. Execute the command shown below. In the following example, the domU configuration information is retrieved from the management domain: # /usr/sbin/xm list -l domU (device...

  • Page 245: Settings For Kvm

    Settings for KVM If you install HDLM in an environment in which KVM is used, you need to register HDLM devices into the hardware configuration file (/etc/libvirt/ qemu/domain-name.xml). For details on the hardware configuration file, see the OS documentation. To register HDLM devices by using the virsh command: Execute the following command to check the domain name and operating status of the guest OS.

  • Page 246: Settings For Oracle Rac

    # virsh define /etc/libvirt/qemu/domK.xml Start the guest OS. For details on how to start the guest OS, see the OS documentation. Settings for Heartbeat This section describes the procedure that the user must perform when HDLM is installed in an environment in which Heartbeat is used for SUSE LINUX Enterprise Server.

  • Page 247

    (number-of-paths-connected-to-Oracle-Cluster-file-System-2 x 60 seconds / 2) + 1 If the Thunder 9500V Series or the Hitachi AMS2000/AMS/WMS/SMS ¢ series is being used: (number-of-paths-connected-to-Oracle-Cluster-file-System-2 x 30 seconds / 2) + 1 • When a host and an Oracle RAC voting disk are connected by multiple paths, HDLM performs failover processing for those paths (in the same way as for normal paths) when an I/O timeout occurs for one of the paths.

  • Page 248

    Table 3-56 Formula for Calculating DISKTIMEOUT Number of paths Storage system Formula for obtaining the value of connected to the type DISKTIMEOUT voting disk • Lightning 3 or less You do not need to change the value of 9900 series DISKTIMEOUT.

  • Page 249: Settings For The Rhcm, Notes On Using Rhcm, When Using Red Hat Enterprise Linux As4/es4

    # /etc/init.d/oracleasm configure Open the ASMLib configuration file (/etc/sysconfig/oracleasm). Change the ORACLEASM_SCANORDER line as follows: ORACLEASM_SCANORDER ="sddlm" If an ASM disk defined in an HDLM device already exists, perform this procedure, and then restart all the nodes. This step must be done to enable the settings. •...

  • Page 250: When Using Red Hat Enterprise Linux 5, Or Red Hat Enterprise Linux 6

    Executing the following command to start the service: # service ccsd start # service cman start # service rgmanager start When Using Red Hat Enterprise Linux 5, or Red Hat Enterprise Linux To specify settings for RHCM: Stop the service of the RHCM cluster. Stop the RHCM service with the following command if the service is running: # service rgmanager stop...

  • Page 251: Settings For Vcs, Checking The Path Configuration

    Settings for VCS The following is the procedure that must be executed by the user when HDLM is installed in an environment that uses VCS. For details on how to operate the VCS GUI, see the VCS documentation. Stop the cluster service of VCS. Change the SCSI device used by VCS to an HDLM device.

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

    # /opt/DynamicLinkManager/bin/dlnkmgr view -drv > redirect- destination-file-2 Open redirect-destination-file-2 and check the HDevName and Device entries to see whether the HDLM device corresponding to the SCSI device has been created. Setting Up HDLM HDLM includes functions like the load balancing function, the automatic failback function, the error logging function, the audit logging function, etc.

  • Page 253: Setting Up Load Balancing

    Table 3-57 The Recommended and Default Values of Each Function Function Default value Recommended value Load-balancing The Extended Least I/Os The recommended algorithm algorithm is used. depends on the operating environment. Path health checking 30-minute check interval The recommended checking interval depends on the operating environment.

  • Page 254: Setting Up Path Health Checking, Setting Up The Automatic Failback Function

    • lio for the Least I/Os algorithm • exlio for the Extended Least I/Os algorithm • lbk for the Least Blocks. algorithm • exlbk for the Extended Least Blocks algorithm The type of algorithm specified by the -lbtype parameter remains stored in the system, even if, you disable the load balancing function by specifying -lb off.

  • Page 255: Setting Up Intermittent Error Monitoring

    # /opt/DynamicLinkManager/bin/dlnkmgr set -afb on -intvl 10 To enable automatic failback, specify on. Specify off otherwise. When you specify on, you can use the -intvl parameter to specify the checking interval can be specified with the -intvl parameter when on is specified. The value that was specified previously will be applied if the checking interval is not specified.

  • Page 256: Setting The Error Log Collection Level, Setting The Trace Level

    Setting the Error Log Collection Level The error log (the HDLM manager log (dlmmgrn.log (n indicates a file number from 1 to 16)) collection level can be set. Table 3-58 Values for the Error Log Collection Level Setting on page 3-188 lists and describes the values for the error log collection level setting.

  • Page 257: Setting The Error Log File Size, Setting The Number Of Error Log Files

    Value Description All information is output. If an error occurs, you might have to set the trace level to 1 or higher to collect any trace information. The higher this value is set, the more information that will be output. As the amount of trace information to be output increases, it will take less time to overwrite the old trace information with the new information.

  • Page 258: Setting The Trace File Size, Setting The Number Of Trace Files

    # /opt/DynamicLinkManager/bin/dlnkmgr set -elfn 5 Specify the number of error log files by a number. Setting the Trace File Size Trace files for which a trace file size can be set are hdlmtrn.log (n indicates a file number from 1 to 64). The length of a trace file is fixed, regardless of how much trace information is actually in the file.

  • Page 259: Setting The Audit Log Facility

    Table 3-60 Values Indicating Audit Log Data Collection Levels on page 3-191 describes the values that indicate audit log data collection levels. An audit log data collection level is a severity level. The default is 6. Table 3-60 Values Indicating Audit Log Data Collection Levels Value (severity) Explanation No audit log data is collected.

  • Page 260: Checking The Updated Settings

    If you want to specify the output destination for audit log data, first specify the audit log facility by using the dlnkmgr set -audfac command. Next, define the output destination of the facility in the /etc/syslog.conf file. Table 3-62 Values Indicating Audit Log Facility on page 3-192 describes the values that indicate audit log facility.

  • Page 261: The Process-specific-trace Information File, Notes On Using The Hitachi Network Objectplaza Trace Library

    view, completion time = yyyy/mm/dd hh:mm:ss After you have set up the collection of audit log data, use the following command to make sure that the setting has been specified correctly: # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -audlog Audit Log : on(6) Audit Log Category : all Audit Log Facility...

  • Page 262: When Using Red Hat Enterprise Linux 5 Or Red Hat Enterprise Linux 6

    Hat Enterprise Linux AS4/ES4 or SUSE LINUX Enterprise Server, use the raw command to create the character-type device file. The following shows the difference between these two methods: The character-type device file created by using the raw command is ¢ deleted when the host is restarted.

  • Page 263: Mounting A File System, Creating A File System

    Mounting a File System To mount an HDLM-managed device as a file system by specifying the logical device file name for an HDLM device: Create a file system by using an HDLM device. If the file system already exists, skip to step 2. Note that the file systems supported by HDLM are ext2, ext3, ReiserFS, and VxFS.

  • Page 264: Settings For Automatic Mounting, Setting The Hdlm Device For The First Time

    Settings for Automatic Mounting If you specify the name of a logical device file of an HDLM device at host startup, an HDLM-managed device is automatically mounted in the same way as if you had specified the name of a logical device file of a SCSI device. To mount an HDLM-managed device automatically, you need to edit the /etc/ fstab file.

  • Page 265: Migrating From An Environment Where A Scsi Device Is Already Set

    /dev/sddlmaa /mnt/sda ext2 defaults For IP-SAN environments ¢ • If the OS is Red Hat Enterprise Linux 5.6, Red Hat Enterprise Linux 5.6 Advanced Platform, Red Hat Enterprise Linux 5.7, Red Hat Enterprise Linux 5.7 Advanced Platform, or Red Hat Enterprise Linux 6: /dev/sddlmaa /mnt/sda...

  • Page 266: Canceling The Settings For Hdlm

    In the example, the name of the logical device file of the HDLM device that corresponds to /dev/sda can be identified as sddlmaa. In the /etc/fstab file, change the logical device file name for a SCSI device to that for the HDLM device that you confirmed in step 1. The following is an example of editing the /etc/fstab file: For FC-SAN environments ¢...

  • Page 267: Operations On Hdlm-managed Devices

    Figure 3-36 Overview of HDLM Uninstallation Perform as required. Operations on HDLM-Managed Devices The following procedure must be performed before uninstalling HDLM: Back up all HDLM-managed devices as required (for example, using a tape backup). Collect all information on the correspondence between logical device file names for the HDLM devices and LU numbers of the LUs in the storage system.

  • Page 268: Canceling The Heartbeat Settings

    For details on how to cancel the Xen settings, see Canceling the Xen Settings on page 3-203. Cancel the KVM settings. Delete the HDLM devices from the hardware configuration file. For details on how to cancel the KVM settings, see Canceling the KVM Settings on page 3-204.

  • Page 269: Canceling The Settings For Oracle Rac, Canceling The Settings For Rhcm

    If a SCSI device that is subordinate to an HDLM device is being used as a file system resource, edit the settings as shown in the following example: # host1 172.26.4.321 Filesystem::/dev/sddlmaa::/mnt/point::ext3 host1 172.26.4.321 Filesystem::/dev/sda::/mnt/point::ext3 In this example, the HDLM device /dev/sddlmaa is commented out, and the SCSI device /dev/sda is added.

  • Page 270

    Edit as shown below to use the SCSI device /dev/sda, which is the lower SCSI device of the HDLM device/dev/sddlmaa, as /dev/raw/raw1. # /dev/raw/raw1 /dev/sddlmaa /dev/raw/raw1 /dev/sda Comment out /dev/sddlmaa and add /dev/sda. Restart the rawdevices service to apply the changes made in Step 2. Execute the following command to restart the service: # service rawdevices restart Start the cluster service of RHCM.

  • Page 271: Canceling The Settings For Vcs, Canceling The Xen Settings

    # /sbin/start_udev Start the cluster service of RHCM. Executing the following command to start the service: # service cman start # service rgmanager start Canceling the Settings for VCS This section describes how to cancel the HDLM device settings in VCS in an environment where VCS is used.

  • Page 272: Canceling The Kvm Settings

    In the following example, the domU configuration information is checked from the management domain: # /usr/sbin/xm list -l domU (device (vbd (uuid 6b393aaa-89e7-44dc-7a57-24d477dee43d) (bootable 0) (driver paravirtualised) (dev sdx) (uname phy:/dev/sddlmaa) (mode w) The HDLM device displayed on the uname phy line is an HDLM device that appeared in the check in step 1.

  • Page 273: Canceling The Settings For Lvm2

    Id Name State ---------------------------------- domK running The underlined part indicates the domain name. If the guest OS is running, stop it. For details on how to stop the guest OS, see the OS documentation. If necessary, delete the HDLM device from the hardware configuration file.

  • Page 274

    To create the environment shown in Figure 3-37 Device Configuration When a Logical Volume on an HDLM Device Is Moved to a SCSI Device on page 3-206, carry out the procedure below. To uninstall HDLM, carry out the steps before the uninstallation. Figure 3-37 Device Configuration When a Logical Volume on an HDLM Device Is Moved to a SCSI Device Figure 3-37 Device Configuration When a Logical Volume on an HDLM...

  • Page 275

    # vgchange -an vg01 0 logical volume(s) in volume group "vg01" now active Export the volume group. In the following example, the command exports information about the vg01 volume group: # vgexport vg01 Volume group "vg01" successfully exported If the LVM environment uses an HDLM device in a multi-path configuration, configure the path to an existing LU as a single path.

  • Page 276

    Figure 3-38 Example of Editing the /etc/lvm/lvm.conf File Execute the vgscan command. To re-create the volume group on the HDLM device, execute the vgscan command as shown in the following example: # vgscan Reading all physical volumes. This may take a while... Found exported volume group "vg01"...

  • Page 277: Canceling The Md Device Settings

    Execute the pvscan command to check that the environment has been changed successfully. The following shows an example of executing the pvscan command: # pvscan PV /dev/sda1 VG vg01 lvm2 [468.00 MB / 368.00 MB free] PV /dev/sda2 VG vg01 lvm2 [548.00 MB / 548.00 MB free] Total: 2 [1016.00 MB] / in use: 2 [1016.00 MB] / in no VG: 0 Activate the volume group.

  • Page 278

    to a SCSI Device (An Environment that Uses the md Device's RAID Functionality) on page 3-210, carry out the procedure below. To uninstall HDLM, carry out the steps before the uninstallation. Figure 3-39 Device Configuration When an md Device on an HDLM Device Is Moved to a SCSI Device (An Environment that Uses the md Device's RAID Functionality) To migrate /dev/md0:...

  • Page 279

    unused devices: <none> Make sure that md0 : active is not displayed. Check the correspondence between the HDLM devices and SCSI devices. Execute the HDLM-configuration definition utility dlmcfgmgr with the -v parameter specified: # dlmcfgmgr -v HDevName Management Device Host Channel Target Lun /dev/sddlmaa configured /dev/sdh /dev/sddlmab configured /dev/sdi KAPL10302-I /sbin/dlmcfgmgr completed normally.

  • Page 280: Migrating To Md Devices For Which The Multipath Function Is Used

    Disk /dev/sddlmaa: 5368 MB, 5368709120 bytes 166 heads, 62 sectors/track, 1018 cylinders Units = cylinders of 10292 * 512 = 5269504 bytes Device Boot Start Blocks System /dev/sddlmaa1 1018 5238597 Linux raid autodetect Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table.

  • Page 281

    Figure 3-40 Device Configuration When an md Device on an HDLM Device Is Moved to a SCSI Device (An Environment that Uses the md Device's MULTIPATH Functionality) To migrate /dev/md0: Deactivate the md device. Perform steps 3 to 5 in Migrating to md Devices for which the MULTIPATH Function Is Not Used on page 3-209.

  • Page 282

    # dlmcfgmgr -v HDevName Management Device Host Channel Target Lun /dev/sddlmaa configured /dev/sdh /dev/sdo KAPL10302-I /sbin/dlmcfgmgr completed normally. The HDevName and Device columns display HDLM devices and SCSI devices, respectively. Create an md device. Based on the correspondence between the HDLM devices and SCSI devices checked in step 5, create an md device.

  • Page 283

    # cat /etc/mdadm.conf DEVICE /dev/sddlmaa1 ARRAY /dev/md0 level=linear num-devices=1 UUID=426a9f1c: 9cfa6310:6aa9a80b:11ea2102 auto=yes ARRAY /dev/md0 level=multipath num-devices=2 UUID=8db667ff:e7472a25:3a84b801:025a6a57 Edit the /etc/mdadm.conf file to add auto=yes to the ARRAY line in the configuration file: DEVICE /dev/sdo1 /dev/sdh1 ARRAY ARRAY /dev/md0 level=multipath num-devices=2 UUID=8db667ff:e7472a25:3a84b801:025a6a57 auto=yes On the DEVICE line of the configuration file, change an HDLM device name to a SCSI device name.

  • Page 284: Canceling The Luks Settings, Uninstalling Hdlm

    Note that, in step 13 in Migrating to md Devices for which the MULTIPATH Function Is Not Used on page 3-209, [linear] will be displayed until the host is restarted. However, there are no operational problems. Canceling the LUKS Settings This subsection describes how to migrate LUKS from a HDLM device environment using LUKS to SCSI devices.

  • Page 285

    Uninstalling HDLM Note If the system initiates path health checking or automatic failback ¢ while HDLM is being uninstalled, an error message (KAPL04023) might be output to syslog. However, HDLM operations are not affected. If you uninstall HDLM, the error logs (/var/tmp/hdlminstlog/ ¢...

  • Page 286

    If a value other than 0 is displayed for Used, perform the operation described in Operations on HDLM-Managed Devices on page 3-199, and then perform steps 2 and 3 in Uninstalling HDLM on page 3-217 so that the HDLM devices can no longer be used. Execute the uninstall command.

  • Page 287

    Root directory (/), /boot, /tmp, /usr, /var, swap When LILO is used as the boot loader: ¢ Root directory (/), /tmp, /usr, /var, swap When LVM2 is used: ¢ /boot The following shows an example of the /etc/fstab file: /dev/sddlmaa2 ext2 defaults Execute the HDLM-configuration definition utility (dlmcfgmgr) with the -v...

  • Page 288

    #/dev/sddlmaa2 ext2 defaults /dev/sda2 ext2 defaults If LVM2 is used in cases other than above, go to step 5. If LVM2 is not used, go to step 6. When LVM2 is used, edit the /etc/lvm/lvm.conf file so that the LVM2 recognizes the SCSI device, not the HDLM device.

  • Page 289

    boot=/dev/sda map=/boot/map install=/boot/boot.b prompt timeout=50 linear #default=HDLM_194.EL default=linux image=/boot/vmlinuz-2.6.18-194.el5 label=HDLM_194.EL initrd=/boot/initrd-hdlm-2.6.18-194.el5.gz read-only append="option ramdisk_size=18245 option" image=/boot/vmlinuz-2.6.18-194.el5 label=linux initrd=/boot/initrd-2.6.18-194.el5 read-only append="option" root=/dev/sda2 When the boot loader is GRUB ¢ Example 1 below shows an example of editing the /etc/grub.conf file (the underlined sections). Example 2 below shows an example of editing the /boot/grub/ menu.lst file when a kernel supporting Xen in SUSE LINUX Enterprise Server 10 is used (the underlined sections).

  • Page 290

    default 1 timeout 8 gfxmenu (hd0,1)/boot/message title XEN-hdlm root (hd0,1) kernel /boot/xen.gz module /boot/vmlinuz-2.6.16.60-0.21-xen vga=0x31a splash=silent showopts module /boot/initrd-2.6.16.60-0.21-xen.hdlm title XEN-sd root (hd0,1) kernel /boot/xen.gz module /boot/vmlinuz-2.6.16.60-0.21-xen root=/dev/sda2 vga=0x31a splash=silent showopts module /boot/initrd-2.6.16.60-0.21-xen When the boot loader is ELILO running on an IPF host ¢...

  • Page 291

    title Red Hat Enterprise Linux AS (2.6.9-11.EL) root (hd1,0) kernel /vmlinuz-2.6.9-11.EL ro root=/dev/VolGroup00/ LogVol00 rhgb quiet initrd /initrd-hdlm-2.6.9-11.EL.img initrd /initrd-2.6.9-11.EL.img Copy the configuration that was used for startup from the HDLM device. Assign a name to the copied configuration. You can assign any name that indicates that the configuration is used for specifying the SCSI device.

  • Page 292

    Make sure that the SCSI device is used by the file system and the swap partition. Make sure of the following three things: that the root directory is associated with the SCSI device, that the SCSI device is mounted, and that the SCSI device is assigned to the swap partition.

  • Page 293

    Execute the following command to make sure that the physical volumes that make up the volume group are not HDLM devices. Delete the initial RAM disk image file that was created with the dlmmkinitrd utility for supporting a boot disk or the dracut command. To do this, execute the following command: When an IA32 host is used: ¢...

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

    Execute the following command and make sure that 0 is displayed for Used for sddlmfdrv: # /sbin/lsmod Module Size Used by sddlmfdrv 254092 If a value other than 0 is displayed for Used, perform the operation described in Operations on HDLM-Managed Devices on page 3-199, and then perform steps 2 and 3 in Uninstalling HDLM on page 3-217...

  • Page 295

    Unsetup is complete. If HNTRLib2 is being used by another program: HNTRLib2 will not be uninstalled, and the following message will appear. Because a bundle PP name is registered, I did not do the Uninstall. If HNTRLib2 was not uninstalled, execute the following command to check if any programs are using it.

  • Page 296

    3-228 Creating an HDLM Environment Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 297: 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. □ Notes on Using HDLM □ Updating Kernel Packages and Applying OS Update Packages □...

  • Page 298: Notes On Using Hdlm, Notes Common To Oss

    Notes on Using HDLM Note the following when using HDLM. Notes Common to OSs The following notes are common to OSs: • Do not activate the same volume group concurrently from multiple servers. • When a path error exists, the period of time required to return a response to the application that made an I/O request to HDLM depends on the timeout values specified for the fibre channel switch and HBA.

  • Page 299

    Figure 4-1 Overview of the Period Required to Respond to an Application's I/O Request As shown in the preceding diagram, when an HDLM device has two paths (SCSI devices), the maximum period of time required to respond to the application's I/O request is n1 + n2 seconds; where n1 indicates the timeout value specified for the path that uses SCSI device A, and n2 indicates the timeout value specified for the path that uses SCSI device B.

  • Page 300

    • If all the following conditions are satisfied, even a path in the normal status might become Offline(E) or Online(E): A storage system that has a SATA drive is being used. ¢ There is a heavy I/O load on the storage system. ¢...

  • Page 301: Notes When Using Suse Linux Enterprise Server 9

    • You cannot execute the partprobe command for HDLM devices because this command does not support HDLM devices. If you want to add a partition to or delete a partition from an HDLM device (LU), first stop all applications that are using the target HDLM device (LU) so that the HDLM device (LU) is not being used If you add or delete a partition while an HDLM device (LU) is being used, restart the host to reload the partition table.

  • Page 302: Notes When Using Suse Linux Enterprise Server 10

    • SCSI devices corresponding to an HDLM device can be removed dynamically even while the HDLM device is in use. Before doing so, perform the following operations: Unmount any devices mounted on the HDLM device. Execute the dlmcfgmgr -o command to exclude the HDLM device from management.

  • Page 303: Notes When Using Suse Linux Enterprise Server 11

    • If you execute the sync command on the file system that is mounted by ext3/ReiserFS, the following message is output to syslog, but there is no problem with HDLM operations. JBD: barrier-based sync failed on sddlmaa1 - disabling barriers •...

  • Page 304: Updating Kernel Packages And Applying Os Update Packages

    • HDLM devices cannot be used to create an md device. • If you execute the sync command on the file system that is mounted by ext3/ReiserFS, the following message is output to syslog, but there is no problem with HDLM operations. JBD: barrier-based sync failed on sddlmaa1 - disabling barriers •...

  • Page 305: Environment Where An Hdlm Device Is Not Used As The Boot Disk

    Table 4-1 HDLM Installation Environments in Which Kernel Packages Can Be Updated or OS Update Packages Applied on page 4-9 shows the HDLM installation environments in which kernel packages can be updated or OS update packages applied. Table 4-1 HDLM Installation Environments in Which Kernel Packages Can Be Updated or OS Update Packages Applied HDLM installation environment See:...

  • Page 306: Notes On Using Commands, Viewing Path Information

    Specify the settings required for using an HDLM device as a boot disk. Perform step 17 to 32 in Upgrade Installation in an Environment Where an HDLM Device Is Used as a Boot Disk on page 3-116. Environment Where a Logical Volume (LVM2) on an HDLM Device Is Used as the Boot Disk To update a kernel package or apply an OS update package when a logical volume (LVM2) on an HDLM device is used as the boot disk:...

  • Page 307: Changing The Status Of Paths, Changing The Status Of Paths To Online

    # /opt/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. The following example shows how to execute the command: For details on the displayed items and their descriptions, see view (Displays Information) on page 6-28.

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

    KAPL01057-I All the paths which pass the specified HBA will be changed to the Online status. Is this OK? [y/n]:y KAPL01061-I 3 path(s) were successfully placed Online; 0 path(s) were not. Operation name = online Check to see if the statuses of all the applicable paths have changed. The following is an example of executing the command: # /opt/DynamicLinkManager/bin/dlnkmgr view -path Changing the Status of Paths to Offline(C)

  • Page 309: Viewing Lu Information

    The following is an example of executing the command: # /opt/DynamicLinkManager/bin/dlnkmgr view -path Viewing LU Information This section explains how to display LU information by using an HDLM command. To display LU information, execute the dlnkmgr command's view operation with the -lu parameter specified. The following is an example of executing the command: # /opt/DynamicLinkManager/bin/dlnkmgr view -lu Product...

  • Page 310: Initializing Statistical Information For Paths

    the -drv parameter specified. For details on the view operation, see view (Displays Information) on page 6-28. The execution result of this operation is displayed on a single line for each path. The following is an example of executing the dlnkmgr command's view operation: # /opt/DynamicLinkManager/bin/dlnkmgr view -drv PathID HDevName...

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

    Check to see whether the statistical information for all the paths has been initialized. The following is an example of executing the command: # /opt/DynamicLinkManager/bin/dlnkmgr view -path Viewing and Setting Up the Operating Environment This section explains how to display and set up the HDLM operating environment.

  • Page 312: Setting Up The Operating Environment, Viewing License Information

    Setting Up the Operating Environment To set up the HDLM operating environment, execute the dlnkmgr command's set operation. This operation allows you to set up the following functions: • Load balancing • Path health checking • Automatic failback • Intermittent error monitoring •...

  • Page 313: Updating The License, Viewing Hdlm Version Information

    For details on the displayed items and their descriptions, see view (Displays Information) on page 6-28. Updating the License This section explains how to update the license. To update the license, execute the dlnkmgr command's set operation with the -lic parameter specified. When the confirmation message is displayed, enter y to execute, or n to cancel the command.

  • Page 314: Viewing Hdlm Component Information

    Path Health Checking : on(30) Auto Failback : on(1) Reservation Status Intermittent Error Monitor : off HDLM Manager Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.x-xx yyyy/mm/dd hh:mm:ss 1000 HDLM Driver Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss...

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

    Also, you can view information for each HDLM component. Execute the dlnkmgr command's view operation with the -sys and subsequent parameter specified. The following is an example of executing the command: # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -msrv # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -adrv # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -pdrv Starting and Stopping the HDLM Manager If an error occurs in the system, such as in an HDLM program, you may need...

  • Page 316: Stopping The Hdlm Manager

    Use the dlnkmgr command's view operation: Execute the following command: # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -msrv HDLM Manager Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss KAPL01001-I The HDLM command completed normally. operation name = view, completion time = yyyy/mm/dd hh:mm:ss When the HDLM Manager column shows Alive, the HDLM manager is active.

  • Page 317: Hdlm Resident Processes

    = view, completion time = yyyy/mm/dd hh:mm:ss When the HDLM Manager column shows Dead, the HDLM manager is inactive. Use a script for confirmation: Execute the following command to confirm that the HDLM manager is inactive: # /etc/init.d/DLMManager status dlmmgr is stopped. Note If an error occurs, the execution results of the dlnkmgr command's view operation might be different from those of the DLMManager status...

  • Page 318: Preparation For Replacing Hbas In A Bladesymphony Environment

    • Add devices to or remove devices from the list of devices to be managed by HDLM Replacing HBAs You can replace HBAs without stopping any applications when all of the following conditions are satisfied: • The OS on the host is either of the following: Red Hat Enterprise Linux 5 ¢...

  • Page 319: Procedure For Replacing Hbas

    # chmod 755 /etc/sysconfig/modules/acpiphp.modules Finally, after the chmod command has been executed, confirm that the execution permissions have been set as indicated by the underlined portion below. # ls –l /etc/sysconfig/modules/acpiphp.modules -rwxr-xr-x 1 root root 35 mm dd hh:mm /etc/sysconfig/modules/ acpiphp.modules Load the acpiphp module.

  • Page 320

    The following steps assume that the HBAs whose WWN information is underlined above are to be replaced. Execute the view operation of the dlnkmgr command (dlnkmgr view - path -hbaportwwn) to check the information about the paths that pass through the HBAs you want to replace. See the port WWN information of the HBAs you checked in step 1 and HBAPortWWN displayed as the execution result to check the host port number and the bus number displayed in PathName.

  • Page 321

    Replace the HBAs. Execute the dlmcfgmgr utility (dlmcfgmgr -r) to change the HDLM device configuration. # dlmcfgmgr –r Execute the view operation of the dlnkmgr command (dlnkmgr view - path -hbaportwwn) to confirm that the new paths have been added. In the above figure, new paths that have been added are indicated by shading.

  • Page 322: Updating The Path Information After The Host Is Restarted

    Execute the dlmcfgmgr utility (dlmcfgmgr -u) to delete the information about the old paths and SCSI devices. In the -u parameter, specify an HDevName device for which old SCSI device information is displayed in step 9. Note that you need to execute the utility for each HDevName device that contains old SCSI device information.

  • Page 323

    The paths existing when the HBAs were replaced remain in Offline(E) status. Execute the dlmcfgmgr utility (dlmcfgmgr -v) to check the HDLM device status. Because the paths existing when HBAs were replaced are in Offline(E) status, a hyphen (-) is displayed for Device. Execute the dlmcfgmgr utility (dlmcfgmgr -u) to delete the old information about paths and SCSI devices.

  • Page 324: Replacing A Fiber Cable

    # dlmcfgmgr -v Execute the view operation of the dlnkmgr command (dlnkmgr view - path -hbaportwwn) to confirm that all the information about the paths that were placed in Offline(E) status has been deleted. # /opt/DynamicLinkManager/bin/dlnkmgr view -path -hbaportwwn Replacing a Fiber Cable If there are multiple online paths for a device in an LU, you can replace a desired fiber cable while running your applications by placing offline only the path that goes through the fiber cable to be replaced, and using other paths...

  • Page 325

    For example, to place in Offline (C) status the path that goes through the HBA with host port number 0001 and bus number 0000, execute the following command: # /opt/DynamicLinkManager/bin/dlnkmgr offline -hba 0001.0000 While the path that goes through the HBA with host port number 0001 is placed Offline, the status of the path that goes through the HBA with host port number 0002 is Online.

  • Page 326: Replacing The Fibre Channel Switch

    For example, execute the following command: # /opt/DynamicLinkManager/bin/dlnkmgr view -path For details about the path information, see view (Displays Information) on page 6-28. Replacing the Fibre Channel Switch If there are multiple online paths for a device in an LU, you can replace a desired Fibre Channel switch while running your applications by placing offline only the path that goes through the Fibre Channel switch to be replaced, and using other paths to continue accesses.

  • Page 327

    For example, to place in Offline (C) status the path that goes through the HBA with host port number 0001 and bus number 0000, execute the following command: # /opt/DynamicLinkManager/bin/dlnkmgr offline -hba 0001.0000 While the path that goes through the HBA with host port number 0001 is placed Offline, the status of the path that goes through the HBA with host port number 0002 is Online.

  • Page 328: Changing The Hdlm Device Configuration, Notes On Changing The Hdlm Device Configuration

    # /opt/DynamicLinkManager/bin/dlnkmgr view -path For details about the path information, see view (Displays Information) on page 6-28. Changing the HDLM Device Configuration This section describes the actions and procedures to change the HDLM device configuration. To set up or change (add, change or delete) an LU in a storage system, use the management program of the storage system, rather than the HDLM functionality.

  • Page 329

    • When the dlmcfgmgr utility is executed to change the HDLM device configuration, memory might become insufficient due to the HAL daemon . In this case, the host will not respond. To avoid this, stop the HAL daemon when executing the dlmcfgmgr utility. For details on how to stop the HAL daemon, see Notes on Installing HDLM on page...

  • Page 330

    Adding a New LU To add a new LU (HDLM device) to the host on which the HDLM is installed: Use the management program of the storage system to allocate an LU, which is not yet allocated to the relevant host, to a port of the storage system that has a path to the relevant host and configure the path.

  • Page 331

    Operation Command - Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 6 and a Brocade HBA driver - SUSE LINUX Enterprise Server and a Brocade HBA driver Execute the following command: # echo "- - -" > /sys/class/scsi_host/hostn/scan Execute the following command to check whether the OS has recognized any devices: # cat /proc/scsi/scsi...

  • Page 332: Adding A Path To An Existing Lu

    n: host port number driver-name: qlaxxxx (driver name in use) Example entries are shown below. When adding a device by using a QLogic HBA driver in Red Hat Enterprise Linux AS4/ES4: # echo "scsi-qlascan" > /proc/scsi/qla2200/1 # cat /proc/scsi/qla2200/1 # echo "scsi add-single-device 1 0 1 1" > /proc/scsi/scsi Execute the HDLM-configuration definition utility (dlmcfgmgr -r).

  • Page 333: Deleting An Existing Lu

    The following is an example of executing the dlmcfgmgr utility: # /sbin/dlmcfgmgr -r Restart the host on which the HDLM is installed. If you performed step 3 and step 4, the host does not have to be restarted. Go to step 6. While restarting, the additional path configured in the above step 1 is automatically added as a path to the relevant HDLM device.

  • Page 334: Deleting A Path To An Existing Lu

    Make sure that all the SCSI device names corresponding to the LU for which path allocations were cancelled in step 2 are represented with a hyphen (-) (optional). The following is an example of executing the dlmcfgmgr utility with the -v option: # /sbin/dlmcfgmgr -v The following is an example of executing the view operation with the -drv...

  • Page 335

    If you performed step 4, the host does not have to be restarted. Go to step 6. Execute the HDLM-configuration definition utility (dlmcfgmgr -v) or the view operation of the dlnkmgr command (dlnkmgr view -drv) (optional). Check if the SCSI device name of the HDLM device whose path was deleted in the above step 2 is represented with a hyphen (-).

  • Page 336: Changing A Device Managed By Hdlm Into One Not Managed By Hdlm:

    # /sbin/dlmcfgmgr -v Changing a Device Managed by HDLM into One Not Managed by HDLM: The following operation can be done without restarting the host. To change a device managed by HDLM into one not managed by HDLM: Stop all accesses to the relevant LU. Execute the HDLM-configuration definition utility (dlmcfgmgr -v) to check if the device you want to exclude from HDLM management is being managed by HDLM.

  • Page 337

    HDLM. Perform this operation if necessary. If it is not necessary to check this, go to step 3. Execute the dlmcfgmgr utility (dlmcfgmgr - ilogical_device_file_name_of_HDLM_device ) on the relevant device you want to HDLM to manage. The specified device is managed by HDLM. The following is an example of executing the dlmcfgmgr utility: # /sbin/dlmcfgmgr -i name-of-logical-device-file-for-HDLM-device Refer to /var/opt/DynamicLinkManager/log/dlmcfgmgr1.log or...

  • Page 338

    Connect the cable. If the cable is broken, replace it. Restart the host on which the HDLM is installed. The SCSI device is recreated, the path to the HDLM device, which was determined in step 1 to be in disconnected status when the host was started, is restored automatically, and the status changes to online.

  • Page 339

    Since you restore the path without restarting, the path for the SCSI device which was in disconnected status during bootup will not be created and you must execute the command for adding a device, shown in Table 4-4 Add SCSI Devices on page 4-43, to manually create the SCSI device.

  • Page 340

    Purpose Command If you are using Red Hat Enterprise Linux 5, Red Hat Enterprise Linux 6, SUSE LINUX Enterprise Server 10, or SUSE LINUX Enterprise Server 11, the devices might be automatically recognized by the OS hot plug function. If the devices are recognized, the above procedure is not necessary.

  • Page 341: Restoring The Path In Disconnected Status, About Creating A New Hdlm Device

    # /sbin/dlmcfgmgr -v Restoring the Path in Disconnected Status This subsection describes how to restore the path to an HDLM device that was in disconnected status (the cable was pulled out or broken). Execute the HDLM-configuration definition utility (dlmcfgmgr -v) to check while the path to the relevant HDLM device was in disconnected status.

  • Page 342

    detected path is already registered and a situation where a new HDLM device is created. If the SCSI device of the new path that HDLM detected is already registered, the HDLM device mapped with the path already registered is allocated. For example, if the path between the host and an LU of the storage system already exists and a new path is added, the HDLM device that already exists is allocated to the path.

  • Page 343: Note On Adding A Bladesymphony I/o Drawer

    device(s) not in use (or, represented with a hyphen (-)) to release the available name(s) to create an HDLM device file for the new LU. Even if you add a path to an HDLM device that is not managed by HDLM and restart the host, the HDLM device will not be managed by HDLM.

  • Page 344

    4-48 HDLM Operation Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 345: Troubleshooting

    Troubleshooting This chapter describes how to properly use HDLM error information, and then how to resolve the problem, if an error has occurred in HDLM. The resolutions for path errors, HDLM program errors, and other types of errors are all described separately.

  • Page 346: 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, DLMgetras Utility for Collecting HDLM Error Information on page 7-3.

  • Page 347

    The path name indicates a path. When you modify the system configuration or replace a piece of hardware, 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: Host port number (hexadecimal) ¢...

  • Page 348

    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 349: 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 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 has occurred.

  • Page 350: What To Do For A Program Error, Examining The Messages, Obtaining Program Information

    If any path cannot be placed online due to an error, the KAPL01039-W message will appear. To ignore such paths and to continue processing, type y. Type n to cancel processing. Check the statuses of the paths that cannot be placed online, and resolve the problem.

  • Page 351: 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 352

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

  • Page 353: 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 354: Overview Of The Hdlm Command Dlnkmgr

    Overview of the HDLM Command dlnkmgr This section describes how to specify the HDLM command dlnkmgr and its subcommands (called operations in HDLM). Command format Enter the command using the following format: dlnkmgr operation [parameter [parameter-value]] dlnkmgr The command name. operation The type of operation entered after dlnkmgr.

  • Page 355: 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 /opt/DynamicLinkManager/bin/dlnkmgr clear -pdst [-s] To display the format of the clear operation /opt/DynamicLinkManager/bin/dlnkmgr clear -help...

  • Page 356

    Example # /opt/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 357

    Example 2 The following example shows how to display the formats of multiple operations. # /opt/DynamicLinkManager/bin/dlnkmgr help online offline help online: Format dlnkmgr online [-path] [-s] dlnkmgr online [-path] -hba HBAPortNumber.BusNumber [-s] dlnkmgr online [-path] -cha -pathid AutoPATH_ID [-s] dlnkmgr online [-path] [-pathid AutoPATH_ID] [-s] dlnkmgr online [-path] [-device SCSI_Device_Name] [-s] Valid value AutoPATH_ID...

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

    Placing too many paths offline might prevent paths from being able to switch if an error occurs. Before placing a path offline, use the view operation to check how many online paths remain. For details about the view operation, view (Displays Information) on page 6-28.

  • Page 359

    When the confirmation message is displayed, the user enters y to continue, or n to cancel the operation. # /opt/DynamicLinkManager/bin/dlnkmgr offline -hba 0010.0000 KAPL01055-I All the paths which pass the specified HBA will be changed to the Offline(C) status. Is this OK? [y/n]:y KAPL01056-I If you are sure that there would be no problem when all the paths which pass the specified HBA are placed in the Offline(C) status, enter y.

  • Page 360

    Specify the current AutoPATH_ID of the target path, which is displayed by using the view operation. For details about the view operation, see view (Displays Information) on page 6-28. Leading zeros can be omitted (000001 and 1 indicate the same AutoPATH_ID); however, when the target AutoPATH_ID is 000000, enter 000000 or 0 for the parameter value.

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

    KAPL01061-I 1 path(s) were successfully placed Offline(C); 0 path(s) were not. Operation name = offline To Display the Format of the Offline Operation -help Displays the format of the offline operation. Example The following example shows how to display the format of the offline operation: # /opt/DynamicLinkManager/bin/dlnkmgr offline -help offline:...

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

    # /opt/DynamicLinkManager/bin/dlnkmgr view -path -stname | grep 9500V | grep 0A The above command will display information pertaining to only those paths that pass through the specified CHA port. online (Places Paths Online) The dlnkmgr command's online operation places offline paths online. Specify the paths to be placed online by specifying an HBA port, CHA port, or single path.

  • Page 363

    connected to the HBA port that has the specified host port number and bus number. Specify the host port number and bus number of the target HBA port: the numbers are found in the PathName field displayed using the view operation.

  • Page 364

    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 -pathid AutoPATH_ID Use this parameter to place a single path online. Specify the current AutoPATH_ID of the target path, which is displayed by using the view operation.

  • Page 365: To Display The Format Of The Online Operation

    The following example shows how to place a path, whose AutoPATH_ID is 000002, online without asking for confirmation of command execution from the user: # /opt/DynamicLinkManager/bin/dlnkmgr online -pathid 2 -s KAPL01061-I 1 path(s) were successfully placed Online; 0 path(s) were not. Operation name = online To Display the Format of the Online Operation -help Displays the format of the online operation.

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

    Example 2 The following example shows how to filter and display the information on all paths that pass through the CHA port 0A of the Thunder 9500V series: # /opt/DynamicLinkManager/bin/dlnkmgr view -path -stname | grep 9500V | grep 0A The above command will display information pertaining to only those paths that pass through the specified CHA port.

  • Page 367: Parameters, To Set Up The Hdlm Operating Environment

    Parameters To Set Up the HDLM Operating Environment Table 6-2 Default and Recommended Values on page 6-15 shows the defaults and recommended values for each setting. If you change the value of the set operation, the new value takes effect immediately. Table 6-2 Default and Recommended Values Item name Default value...

  • Page 368

    -lbtype {rr|exrr|lio|exlio|lbk|exlbk} Specify the algorithm to be used for load balancing. rr: The Round Robin algorithm exrr: The Extended Round Robin algorithm lio: The Least I/Os algorithm exlio: The Extended Least I/Os algorithm lbk: The Least Blocks algorithm exlbk: The Extended Least Blocks algorithm The type of algorithm specified by the -lbtype parameter remains stored in the system, even when you disable the load balancing function by specifying -lb off.

  • Page 369

    -elfs error-log-file-size Specify a value from 100 to 2,000,000 (in KB) for the size of the error log files (dlmmgrn.log (n indicates a file number from 1 to 16)). The specified files size is applied to HDLM manager logs. By specifying both the error log file size and the number of error log files, you can collect up to 32,000,000 KB (approximately 30 GB) of error logs in total.

  • Page 370

    Trace files for which the trace file size can be set are hdlmtrn.log (where n is a value from 1 to 64). The length of a trace file is fixed. Therefore, even if the amount of written trace information is less than the set file size, the file size of each output trace file is always fixed.

  • Page 371

    not change the interval, the path health interval stored in the system is used. -afb {on [-intvl checking-interval]|off} Enables or disables automatic failback. on: Enabled off: Disabled Enabling automatic failbacks might automatically place paths online that were intentionally placed offline (for example, paths placed offline for maintenance work).

  • Page 372

    intermittent-error-monitoring If this condition is not satisfied, the KAPL01080-W message will be output and an error will occur. If this happens, change any of the following settings: the checking interval for automatic failbacks, the intermittent error-monitoring interval, or the number of times that the error is to occur.

  • Page 373

    When a value of 2 or more is specified for the number of times, the following condition must be satisfied: error-monitoring-interval >= checking-interval-for-automatic- failback x number-of-times-error-is-to-occur-during-intermittent- error-monitoring If this condition is not satisfied, the KAPL01080-W message will be output and an error will occur. If this happens, change any of the following settings: the checking interval for automatic failback, intermittent error monitoring interval, or the number of times that the error is to occur.

  • Page 374

    completes. When intermittent error monitoring is not being performed, the number of errors that determine that an intermittent error has occurred is not counted and this value is not changed. The number of times that the error is to occur is stored in the system, even when -iem off is specified and intermittent error monitoring is disabled.

  • Page 375

    Setting Available operation Result of operation • When a path is not being monitored, nothing changes. Change the IEM settings. • While a path is being monitored, the value of the error count and the elapsed monitoring time are reset to 0, and then intermittent error monitoring will restart.

  • Page 376

    # /opt/DynamicLinkManager/bin/dlnkmgr set -iem on -intvl 20 - iemnum 2 KAPL01049-I Would you like to execute the operation? Operation name = set [y/n]: y KAPL01001-I The HDLM command completed normally. Operation name = set, completion time = yyyy/mm/dd hh:mm:ss -lic Specify this option for when a license is updated.

  • Page 377

    The following example shows how to update the license key when the license key file exists: # /opt/DynamicLinkManager/bin/dlnkmgr set -lic KAPL01049-I Would you like to execute the operation? Operation name = set [y/n]: y KAPL01071-I A permanent license was installed. Example 2 The following example shows how to update the license key when the license key file does not exist:...

  • Page 378

    -category [[ss] [a] [ca]|all] Specifies the categories of audit log data to be collected. Table 6-8 Values Indicating Audit Log Data Categories on page 6-26 describes the values that indicate categories of audit log data. The default is all. If you specify the -category parameter without specifying a value, all is assumed.

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

    Executes the command without displaying the message asking for confirmation of command execution from the user. Specify this parameter if you want to skip the response to the confirmation message: for example, when you want to execute the command in a shell script or batch file.

  • Page 380: To Display Program Information, To Display Path Information

    Number-Of-Times { 1 - 99 }(Times) (Default Value 3) AudlogLevel { 0 - 7 } (Default Value 6) Category-Value { [ss] [a] [ca] | all } (Default Value all) Facility-Name { user | local0 - local7 } (Default Value user) Facility-Number { 1 | 16 - 23 } (Default Value 1)

  • Page 381: To Display Lu Information, Ldev, To Display The Format Of The View Operation

    To display path information (by abbreviating the list items) /opt/DynamicLinkManager/bin/dlnkmgr view -path -c [-stname] [-srt {lu|cp}] [-t] To Display LU Information To display LU information /opt/DynamicLinkManager/bin/dlnkmgr view -lu [-hdev host-device-name|-pathid AutoPATH_ID] [-t] To display LU information (by selecting items to be displayed) /opt/DynamicLinkManager/bin/dlnkmgr view -lu -item [ [slpr] [pn] [cp] [clpr] [type] [ic] [ie] [dnu] [iep] [hctl]|all]...

  • Page 382

    To display path information on page 6-36 To display LU information on page 6-47 To display corresponding information about an HDLM device, SCSI device, and LDEV on page 6-55 To display the format of the view operation on page 6-57 To display program information -sys [-sfunc|-msrv|-adrv|-pdrv|-lic|-audlog|-lbpathusetimes] Displays the HDLM program information.

  • Page 383

    Parameter and program Item Description information to be displayed extended lbk: The Extended Least Blocks algorithm Support Blank Cluster Error logging level: Elog Level • 0: Collects no error information. • 1: Collects error information at the Error level or higher. •...

  • Page 384

    Parameter and program Item Description information to be displayed • Checking interval: 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. Blank Reservation Status •...

  • Page 385

    Parameter and program Item Description information to be displayed Version number of the HDLM driver Startup time of the HDLM driver WakeupTime License type -lic License Type Information • Permanent about the HDLM • Temporary license • Emergency License expiration: Expiration When using a permanent license: - When using a temporary license or emergency...

  • Page 386

    Parameter and program Item Description information to be displayed If the collection of audit log data is disabled, a hyphen (-) is displayed. The number of times the same path can be used Times Same for I/O operations when the Round Robin (rr), lbpathusetime Path Was Used Least I/Os (lio), or Least Blocks (lbk) algorithm...

  • Page 387

    KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss Example 3 The following example shows how to display information about the HDLM alert driver: # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -adrv HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.x-xx...

  • Page 388: To Display Path Information

    The following example shows how to display the number of times the same path can be used for load balancing: # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -lbpathusetimes Times Same Path Was Used : 32 KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss To display path information When displaying path information, if you specify either the -item or -c...

  • Page 389

    -iem Use this parameter to add IEP to path information and display information about intermittent errors. -srt {pn|lu|cp} Use this parameter to sort the path information in ascending order, according to the specified sorting keys. The sorting keys are as follows: the first sorting key is the name of the storage system (DskName), the second sorting key is the value specified by the -srt parameter, and the third sorting key is AutoPATH_ID.

  • Page 390

    displayed by the dlnkmgr view -path -item command and the parameter values for displaying each item. Table 6-11 Correspondence between the items displayed by the dlnkmgr view -path -item command and the values of the -item parameter Items displayed by the dlnkmgr view Values specified after the -item -path -item command parameter...

  • Page 391

    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 to be displayed for product IDs, see Table 6-14 Product ID displayed by the view -path operation on page 6-46.

  • Page 392

    To display path information, by abbreviating the list items -path -c When you specify the -path parameter together with the -c parameter, the command selects certain items to be displayed, and shortens the contents of each item so that the information about each path fits into a single line on the screen.

  • Page 393

    For details about the information about product IDs, see Table 6-14 Product ID displayed by the view -path operation on page 6-46. -srt {lu|cp} Use this parameter to sort the path information in ascending order, according to the specified sorting key. The sorting keys are as follows: the first sorting key is the name of the storage system (DskName), the second sorting key is the value specified by the -srt parameter, and the third sorting key is...

  • Page 394

    Table 6-12 Path Information Displayed Item Description Summary summary displayed displayed Total number of displayed paths, indicated by a decimal Paths number. Number of online paths from within the displayed paths, OnlinePaths indicated by a decimal number. When the value of Paths equals the value of OnlinePaths, all paths are online.

  • Page 395

    Displayed Item Description Summary summary displayed displayed Storage system name, which identifies the storage system DskName DskName that is accessed by a path. A storage system name consists of the following three elements, separated by periods: • Vendor ID: The name of the storage system vendor (for example, HITACHI).

  • Page 396

    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 397

    Displayed Item Description Summary summary displayed displayed Information about the intermittent error. 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 398

    Table 6-14 Product ID displayed by the view -path operation Product ID With the -stname Model names of storage Without the -stname parameter systems parameter (Displays the following for the model name) Thunder 9500V series 9500V product identifier Hitachi AMS2000 series Hitachi AMS Hitachi SMS Hitachi WMS...

  • Page 399

    To display LU information When displaying LU information, if the -item parameter, -c parameter, or the -c -item parameter is specified at the same time as the -lu parameter, you can add and display items and display a summary of LU information. This section describes each parameter and the LU information and displayed items.

  • Page 400

    /dev/sdj 000013 Online /dev/sdo 000018 Online 0002 sddlmae /dev/sdu 000004 Online /dev/sdf 000009 Online /dev/sdk 000014 Online /dev/sdp 000019 Online 0003 sddlmaa /dev/sdq 000000 Online /dev/sdv 000005 Online /dev/sdg 000010 Online /dev/sdl 000015 Online 0004 sddlmab /dev/sdr 000001 Online /dev/sdw 000006 Online /dev/sdh 000011 Online /dev/sdm 000016 Online KAPL01001-I The HDLM command completed normally.

  • Page 401

    Items displayed by the dlnkmgr view Values specified after the -item -lu -item command parameter HCTL hctl All items are displayed In the sub-parameters, -hdev or -pathid, you can filter the LU information to be displayed. If you omit both parameters, the command displays the information about all the LUs recognized by HDLM.

  • Page 402

    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 403

    The sub-parameter is: Omits the title for each information item. Example The following example shows how to display a summary of LU information, and selecting the items to be displayed. Execute the following command to display SLPR: Items of LU information Table 6-17 LU Information on page 6-51 describes the displayed LU information.

  • Page 404

    Displayed item Description No summary Summary displayed displayed characters are the internal LU number within the CU. • For HP XP10000/HP XP12000, P9500, and SVS, indicated by a hexadecimal number. The first three characters of iLU are the CU number, and the last two characters are the internal LU number within the CU.The first character of a CU number is 0.

  • Page 405

    Displayed item Description No summary Summary displayed displayed The AutoPATH_ID. PathID AutoPATH_ID is assigned every time the host is restarted. When a new LU was added and the host has not been restarted, AutoPATH_ID is re- assigned to each path of the LU when you execute the HDLM-configuration definition utility (dlmcfgmgr).

  • Page 406

    Displayed item Description No summary Summary displayed displayed determined by referring to What To Do for a Path Error on page 5-3. Attribute of the path Type • Own: Owner path • Non: Non-owner path When connecting to Lightning 9900 series, Lightning 9900V series, Hitachi USP, Universal Storage Platform V/VM, Virtual Storage Platform, Hitachi AMS2000 series, or Hitachi SMS, all...

  • Page 407: Ldev

    Displayed item Description No summary Summary displayed displayed • A value of at least 0: Indicates the number of errors that occurred during intermittent error monitoring. • *: Indicates that an intermittent error occurred (automatic failback does not check the path). SCSI device configuration information.

  • Page 408

    Using this parameter displays the PathID, the HDLM device, SCSI device for the HDLM device, and information on the LDEV in the storage system (storage system model name, serial number, and LU number, separated by period). For details on the contents of each display item, see Table 6-18 To display corresponding information about an HDLM device, SCSI device, and LDEV on page...

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

    000004 sddlmad 9970/9980.15001.05B2 000005 sddlmae /dev/sdu 9970/9980.15001.05B3 000006 sddlmaf /dev/sdv 9970/9980.15001.05B4 000007 sddlmag /dev/sdw 9970/9980.15001.05B5 000008 sddlmah /dev/sdx 9970/9980.15001.05B6 KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss To display the format of the view operation -help Use this parameter to display the view operation format.

  • Page 410

    6-58 Command Reference Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 411: Utility Reference

    Utility Reference This chapter explains the utilities used by HDLM. □ Overview of the Utilities □ DLMgetras Utility for Collecting HDLM Error Information □ dlmcfgmgr Utility for Managing the HDLM Configuration □ dlmmkinitrd Utility for Supporting a Boot Disk □ dlmpr Utility for Clearing HDLM Persistent Reservation □...

  • Page 412: 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 on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page...

  • Page 413: Dlmgetras Utility For Collecting Hdlm Error Information

    This utility performs a new installation, upgrade installation, or re- installation of HDLM. For details on the installhdlm utility, see installhdlm Utility for Installing HDLM on page 7-41. For details about how to perform an unattended installation, see Installing HDLM on page 3-75.

  • Page 414

    Format /opt/DynamicLinkManager/bin/DLMgetras {directory-to-which-collected- information-is-output [-f file-that-defines-information-to-be-collected]|-h} You can also use lower-case characters (dlmgetras instead of DLMgetras) as follows: /opt/DynamicLinkManager/bin/dlmgetras {directory-to-which-collected- information-is-output [-f file-that-defines-information-to-be-collected]|-h} Parameters directory-to-which-collected-information-is-output Specify the output directory for the information that is to be collected by the DLMgetras utility for collecting HDLM error information. The collected information is compiled into the three files shown in Function and output in the specified directory.

  • Page 415: List Of Collected Error Information

    • Lines beginning with the hash mark (#) are handled as comment lines. • If the hash mark (#) is encountered anywhere other than at the beginning of a line, it is assumed to be part of a path name. •...

  • Page 416

    stored in the cluster.tar.gz file. Table 7-2 Information Stored in the cluster.tar.gz File, which Is Recorded by the OS and HDLM Commands When the DLMgetras Utility Is Executed on page 7-7 lists and describes the detailed information stored in the cluster.tar.gz file, which is recorded by the OS and cluster commands when the DLMgetras utility is executed.

  • Page 417

    Files Explanation Output directory Heart Beat debug log file ha-debug (when using SUSE LINUX Enterprise Server) All subdirectories and VCS log /var/VRTSvcs/log files Each output directory is created in the directory that is specified when the user expands the cluster.tar.gz file. This information is collected only if software for which information is to be collected is installed.

  • Page 418

    Executed command Files Explanation VCS cluster status /opt/VRTSvcs/bin/hastatus - VCS_hastatus- information summary summary.txt VCS node information /opt/VRTSvcs/bin/hasys - VCS_hasys-display.txt display VCS node status /opt/VRTSvcs/bin/hasys - VCS_hasys-state.txt information state RHCM cluster configuration /sbin/cluconfig -l RHCM_cluconfig-l.txt information (when using Red Hat Enterprise Linux) RHCM cluster status /sbin/clustat RHCM_clustat.txt...

  • Page 419

    Files Explanation Output directory Boot selection list (when using SUSE /boot/grub menu.lst LINUX Enterprise Server (IA32/ EM64T/AMD64)) Boot loader configuration file (when grub.conf using Red Hat Enterprise Linux (IA32/EM64T/AMD64)) Block device information encrypted /etc crypttab using LUKS (when using Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 6) dracut settings file...

  • Page 420

    Files Explanation Output directory Red Hat Enterprise Linux 5, or SUSE LINUX Enterprise Server 9) OpenAIS settings file /etc/ais openais.conf All subdirectories and cron file /etc/cron* files All subdirectories and dracut settings directory /etc/dracut.conf.d files Information about modules that /etc/hotplug blacklist have not been loaded by a hot plug Script for starting and initializing...

  • Page 421

    Files Explanation Output directory File that defines non-HDLM- .dlmfdrv.unconf managed disks Backup files for the file that defines .dlmfdrv1.unconf non-HDLM-managed disks .dlmfdrv2.unconf .dlmfdrv3.unconf Manager setting information dlmmgr.xml Hitachi Command Suite Common dlmwebagent.proper Agent Component settings file ties iSCSI system configuration hdlm.conf information file HDLM boot log...

  • Page 422

    Files Explanation Output directory All subdirectories and HDLM-related script /etc/sysconfig/hdlm- files scripts /etc/sysconfig/mkinitrd All subdirectories and initrd related file (when using Red files Hat Enterprise Linux 5) NIC network information /etc/sysconfig/network ifcfg-eth* NIC network information /etc/sysconfig/network- ifcfg-eth* scripts syslog-ng settings file (when using /etc/syslog-ng syslog-ng.conf SUSE LINUX Enterprise Server 10 or...

  • Page 423

    Files Explanation Output directory Information about interruption to a interrupts processor I/O memory map information iomem I/O port information ioports Kernel symbol information kallsyms Information about average load time loadavg File lock information locks md device information mdstat Memory information meminfo MISC Driver information misc...

  • Page 424

    Files Explanation Output directory Xen-related information (when using /proc/xen balloon SUSE LINUX Enterprise Server 10 or capabilities SUSE LINUX Enterprise Server 11) All subdirectories and Fibre Channel switch information /sys/class/fc_host files (when using Red Hat Enterprise Linux, SUSE LINUX Enterprise Server 10, or SUSE LINUX Enterprise Server 11) All subdirectories and...

  • Page 425

    Files Explanation Output directory HDLM manager log (including the /var/opt/ dlmmgr1.log driver log) DynamicLinkManager/log dlmmgr16.log Hitachi Command Suite Common dlmwebagent[1- Agent Component log files N].log Inquiry information log dlminquiry.log dlmcfgmgr utility log dlmcfgmgr1.log, dlmcfgmgr2.log On-memory trace log .dlmomtrace1.log .dlmomtrace2.log .dlmomtrace5.log Process-specific-trace information dlnkmgr1.log, file...

  • Page 426

    Table 7-4 Information Stored in the getras.tar.gz File, which Is Recorded by the OS and HDLM Commands When the DLMgetras Utility Is Executed Executed command Files Explanation Disk usage of the file system /bin/df bdf.txt System diagnostic message /bin/dmesg dmesg.txt List of disks to be handled as /bin/ls -altR /dev dev_dsk.txt...

  • Page 427

    Executed command Files Explanation information (when using Red Hat Enterprise Linux) List of installed packages /bin/rpm -qai rpm-qai.txt HDLM package file information /bin/rpm -qlv HDLM HDLM_rpm-qlv.txt HDLM package revised /bin/rpm -V HDLM rpm-V.txt information OS version /bin/uname -a uname-a.txt DRBD status information /etc/init.d/drbd status drbd-status.txt o2cb status information...

  • Page 428

    Executed command Files Explanation /opt/DynamicLinkManager/ bin/dlnkmgr view -sys - pdrv, /opt/DynamicLinkManager/ bin/dlnkmgr view -sys -lic, /opt/DynamicLinkManager/ bin/dlnkmgr view -sys - audlog, /opt/DynamicLinkManager/ bin/dlnkmgr view -sys - lbpathusetimes Block device attribute /sbin/blkid blkid.txt information (when using Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 6) Service settings /sbin/chkconfig --list...

  • Page 429

    Executed command Files Explanation Enterprise Linux 5, Red Hat Enterprise Linux 6, or SUSE LINUX Enterprise Server 11) Boot loader information (when /sbin/lilo -t lilo-t.txt using IA32, EM64T, or AMD64) List of load modules /sbin/lsmod lsmod.txt PCI information /sbin/lspci -v lspci-v.txt lvm disk information (when /sbin/lvmdiskscan...

  • Page 430

    Executed command Files Explanation segment, stack segment, and file descriptor) for the process Environment variables /usr/bin/env env.txt information Memory information /usr/bin/free free.txt getconfPAGESIZE.txt Memory page size information /usr/bin/getconf PAGESIZE Program build number /usr/bin/ident dlnkmgr whatlist.txt (dlnkmgr, dlmmgr, DLMgetras, dlmmgr DLMgetras libdlm.so libhdlmhcc-* libhdlmhccmp-* libdlm.so libhdlmhcc-*, dlmcfgmgr sddlmadrv.ko...

  • Page 431

    Executed command Files Explanation KVM guest OS information /usr/bin/virsh list --all virsh-list.txt (when using Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 6) clvmd version /usr/sbin/clvmd -V clvmd-V.txt Pacemaker resource list /usr/sbin/crm_resource -L crm_resource-L.txt Security control values for /usr/sbin/getsebool -a getsebool-a.txt daemon execution (Boolean...

  • Page 432: Dlmcfgmgr Utility For Managing The Hdlm Configuration

    dlmcfgmgr Utility for Managing the HDLM Configuration For management by HDLM, the HDLM-configuration definition utility obtains the SCSI device information stored by Linux by detecting the information on the path between the host and storage system to register in HDLM, and then creates, updates, or deletes the HDLM devices.

  • Page 433

    Specify this parameter when you do not want to display the confirmation messages during execution of the dlmcfgmgr utility. When you execute this utility with this parameter specified, the confirmation message for each HDLM device is not displayed. Use this parameter when you want to skip a response to the confirmation message (to eliminate the manual intervention).

  • Page 434

    Status before executing the dlmcfgmgr Status after executing the dlmcfgmgr utility (dlmcfgmgr -r) utility (dlmcfgmgr -r) /dev/sddlmac /dev/sddlmaa /dev/sddlmaa /dev/sddlmpp /dev/sddlmpp /dev/sddlmaaa /dev/sddlmaa /dev/sddlmaa /dev/sddlmaap /dev/sddlmaap /dev/sddlmbaa A newly assigned logical device file name of the HDLM device Every time the host starts, the dlmcfgmgr utility (dlmcfgmgr -r) is automatically executed.

  • Page 435

    from being managed immediately after execution of the utility, except when the specified HDLM device is in use. If the specified HDLM device is in use, an error occurs. You can use this parameter to exclude the HDLM devices that are no longer required to be managed by HDLM.

  • Page 436

    You can specify one or more logical device file names of an HDLM device (/dev/sddlm[aa-pap]) as a value of the -u parameter. For details on logical device files for HDLM devices, see Logical Device Files for HDLM Devices on page 2-11.

  • Page 437

    In response to the confirmation message, enter y to execute the utility and n not to execute the utility. Example 2: To exclude the HDLM device sddlmaa from being managed without confirming the execution of the utility: Example 3: To delete the information for all the unavailable paths and unregister the path information from HDLM after confirming the execution of the utility: In response to the confirmation message, enter y to execute the utility and n not to execute the utility.

  • Page 438

    Table 7-7 Information for the Management Status and Configuration Information of an HDLM Device Item Description Indicates the logical device file name of the HDLM device, using an HDevName absolute path. This is indicated only for the first path for the relevant Indicates the current management status of the HDLM device.

  • Page 439: Reference Information

    Reference information If you do not specify a parameter, the syntax of the dlmcfgmgr utility is displayed. # /sbin/dlmcfgmgr KAPL10319-W usage: /sbin/dlmcfgmgr [-s] { -r | -o {special-file-name ... | all} | -i {special-file-name ... | all} | -v [-udev] | -u {special-file-name ...

  • Page 440

    all the specified HDLM devices (/dev/sddlmaa, /dev/sddlmab, and /dev/ sddlmac) is executed continuously. • After changing partition configuration directly from a SCSI device for LUs corresponding to the HDLM devices not to be managed, if the HDLM device is returned to management target, execute the following operations: Execute the dlmcfgmgr utility with the -i parameter specified.

  • Page 441: For Red Hat Enterprise Linux As4/es4 Or Red Hat Enterprise Linux 5

    dlmcfgmgr utility with the -r parameter specified, the HDLM partition information will be lost from /proc/partitions. To restore the information, follow these steps: Delete the SCSI device you just added. Dynamically add the SCSI device once again. Execute the online operation to place the device path online. Execute the dlmcfgmgr utility with the -r parameter specified.

  • Page 442

    For SUSE LINUX Enterprise Server 10 or SUSE LINUX Enterprise Server 11 /opt/DynamicLinkManager/bin/dlmmkinitrd [-i initrd-image] [-b boot-directory] [-h] Parameters For Red Hat Enterprise Linux AS4/ES4 or Red Hat Enterprise Linux 5 Specify this parameter to output a log to the console during execution of the dlmmkinitrd utility.

  • Page 443: Dlmpr Utility For Clearing Hdlm Persistent Reservation

    Example: The name of the initial RAM disk image file for the vmlinuz-2.6.16.46-0.14-bigsmp kernel is initrd-2.6.16.46-0.14- bigsmp.hdlm. -i initrd-image Specify the name of the initial RAM disk image file to be created by using the dlmmkinitrd utility. This parameter is used to create an initial RAM disk image file with a name other than the default file name (initrd- version.hdlm).

  • Page 444

    Specify this parameter to display the reservation key. The following explains the items displayed when the -k parameter is specified: Reservation Key If the reservation key is not set, [0x0000000000000000] is displayed. Regist Key The registered keys are displayed. Key Count The number of registered keys is displayed.

  • Page 445: Dlmsetopt Utility For Setting Hdlm Driver Options

    The confirmation message appears. Enter y to clear. Otherwise, enter n. KAPL10641-I Reservation Key will now be cleared. Is this OK? [y/n]:y KAPL10642-I Reservation Key of sdb was cleared. KAPL10642-I Reservation Key of sdc was cleared. Note • Before executing the dlmpr utility, make sure that the LU for which persistent reservation will be cleared is not being accessed.

  • Page 446

    allocation fails, the KAPL05708-E message is output to syslog and to the HDLM manager log file. retrycount Specify a numeric value from -1 to 2,147,483,646. -1 : The system retries until memory is allocated. This is the initial value of the system. 0 : The system does not retry.

  • Page 447

    1 to 2,147,483,646: The system retries the specified number of times. If the following values are specified, the KAPL12553-W message is displayed and then processing ends: • Value of -1 or less • Value more than 2,147,483,646 • Non-numeric value Displays the format of the dlmsetopt utility for setting the HDLM driver option.

  • Page 448: Dlmstart Utility For Starting Hdlm

    Table 7-8 conf files used by the dlmsetopt utility File Name Red Hat Enterprise Linux AS4/ES4 /etc/modprobe.conf Red Hat Enterprise Linux 5 SUSE LINUX Enterprise Server Red Hat Enterprise Linux 6 /etc/modprobe.d/dlmdrvopt.conf • If you use the dlmsetopt utility in an environment where an HDLM device is used for the boot disk, after changing the settings, you need to re- create the initial RAM disk image file.

  • Page 449: Dlmupdatesysinit Utility For Updating System Scripts

    Notes: • You cannot execute multiple instances of the dlmstart utility at the same time. • You cannot execute the dlmstart utility while the dlmcfgmgr utility is executing. • If you execute the dlmstart utility while one or more HDLM devices are mounted, an error message (KAPL05023-E) is output to the syslog.

  • Page 450: Error Information To Be Collected

    rc.d/rc.sysinit KAPL13502-I The utility for update system scripts completed successfully. Example 2 In this example, the utility was executed but there was no need to re- register the HDLM information: # /opt/DynamicLinkManager/bin/dlmupdatesysinit KAPL13501-I The utility for update system scripts started. KAPL13502-I The utility for update system scripts completed successfully.

  • Page 451: Installhdlm Utility For Installing Hdlm

    page 7-41 describes the detailed information contained in installgetras.tar.gz. Table 7-10 Information Contained in installgetras.tar.gz File Description Output directory installgetras.log Log file of the output-directory-of- installgetras utility collected-information- specified-when-executing- the- -installgetras-utility OS syslog file /var/log messages All subdirectories and Log information /var/tmp/hdlminstlog files created during HDLM...

  • Page 452

    For details about the installation-information settings file, see Editing an Installation-Information Settings File on page 7-42. Editing an Installation-Information Settings File This section describes how to edit the installation-information settings file. How to Edit an Installation-Information Settings File Keep the following in mind when you edit an installation-information settings file: •...

  • Page 453

    Necessity of Maxim definition Upgrade numbe Key name Description installati r of installati on or re- charac installati ters The default is /var/tmp/ hdlm_license. If you perform an upgrade installation or re-installation without updating the license, delete the licensekeyfile key and value. Specify the absolute path name of a 1024 Optional...

  • Page 454

    License key file (/var/tmp/hdlm_license) File containing the license key (/etc/opt/DynamicLinkManager/ dlm.lic_key) If none of these files exist when you attempt to perform a new installation, the KAPL09011-E and KAPL09212-E message is output. If you specify a value for either the licensekey or licensekeyfile key, the specified file will not be deleted after the installhdlm utility is executed.

  • Page 455

    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 5 load_balance_type to indicate the load balancing algorithm: rr: The Round Robin algorithm exrr: The Extended Round Robin algorithm lio: The Least I/Os algorithm...

  • Page 456

    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 457

    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 30. Specify the number of times an Optional Optional 2 intermittent_error error occurs.

  • Page 458: Log File

    error_log_size=9900 error_log_number=2 trace_level=0 trace_file_size=1000 trace_file_number=4 path_health_check=on path_health_check_interval=30 auto_failback=on auto_failback_interval=1 # intermittent_error_monitor=off # intermittent_error_monitor_interval=210 # intermittent_error_monitor_number=3 installux.sh Utility for HDLM Common Installer This utility determines what OS HDLM will be installed on, and installs the corresponding version of HDLM from the DVD-ROM. This utility can also perform unattended installations via a parameter specification.

  • Page 459

    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-49 Utility Reference Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 460

    7-50 Utility Reference Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 461: 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 462

    □ KAPL15001 to KAPL16000 □ Return Codes for Hitachi Command Suite Common Agent Component Messages Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 463: 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 464: Kapl01001 To Kapl02000, Kapl01001 To Kapl

    • HDLM management target KAPL01001 to KAPL02000 Message ID Message Text Explanation KAPL01001-I The HDLM command completed Details normally. Operation name = The HDLM command completed aa...aa, completion time = successfully. bb...bb aa...aa: clear, help, offline, online, set, or view bb...bb: Year/month/day hour:minute:second Action...

  • Page 465

    Message ID Message Text Explanation operation, see help (Displays the Operation Format) on page 6-4. KAPL01006-W A necessary parameter is not Details specified. Operation name = The specified operation does not aa...aa contain the necessary parameter. aa...aa: clear, set, offline, or view Action Execute help operation-name of...

  • Page 466

    Message ID Message Text Explanation Action Execute the view operation of the HDLM command (dlnkmgr) to check whether the HDLM manager has started. Start the HDLM manager if it has not started, and then retry the HDLM command. For details on the view operation, view (Displays Information) on page 6-28.

  • Page 467

    Message ID Message Text Explanation path) and check the value displayed in PathName. Use the two leftmost digits of PathName for the relevant HBA port, and then retry. For details on the view operation, see view (Displays Information) on page 6-28.

  • Page 468

    Message ID Message Text Explanation HDLM operating environment have not finished. Action offline/online operation ¢ Use the view operation of the HDLM command (dlnkmgr) to check the settings, and then retry. For details on the view operation, see view (Displays Information) on page 6-28.

  • Page 469

    Message ID Message Text Explanation view (Displays Information) on page 6-28. KAPL01024-W The specified parameters cannot Details be specified at the same time. aa...aa: clear, offline, online, Operation name = aa...aa, set, or view parameters = bb...bb bb...bb: Parameters that cannot be specified at the same time Action Execute help operation of the...

  • Page 470

    Message ID Message Text Explanation KAPL01041-E The entered value is invalid. The Details operation stops. Operation Command processing will be name = aa...aa aborted because an incorrect value was entered three times in a row for a request. aa...aa: clear, offline, online, or set Action Check the correct value, and then...

  • Page 471

    Message ID Message Text Explanation Action If you want to execute the operation, enter y. If you want to terminate processing, enter n. For details on the clear operation, clear (Returns the Path Statistics to the Initial Value) on page 6-3.

  • Page 472

    Message ID Message Text Explanation If you want to execute the offline processing, enter y. If you want to terminate processing, enter n. For details on the offline operation, see offline (Places Paths Offline) on page 6-5. KAPL01053-I If you are sure that there would Details be no problem when the path is The offline operation will be...

  • Page 473

    Message ID Message Text Explanation y. If you want to terminate processing, enter n. KAPL01056-I If you are sure that there would Details be no problem when all the This message re-asks the user paths which pass the specified whether they want to set all the aa...aa are placed in the paths to Offline(C).

  • Page 474

    Message ID Message Text Explanation specify parameter bb...bb and A parameter value is conflicting parameter value cc...cc. with the value of another Operation name = dd...dd parameter. aa...aa: Parameter name bb...bb: Parameter name cc...cc: Parameter value dd...dd: view or set Action Execute help operation-name of the HDLM command (dlnkmgr) to...

  • Page 475

    Message ID Message Text Explanation path has already been set to Online/Offline(C). aa...aa: Online or Offline(C) Action Use the view operation of the HDLM command (dlnkmgr) to check the status of the path. For details on the view operation, see view (Displays Information) on page 6-28.

  • Page 476

    Message ID Message Text Explanation KAPL01073-E The temporary license expired. Details The temporary license has expired. Register a permanent license. Action Register a permanent license. KAPL01074-E The emergency license expired. Details The emergency license has expired. Register a permanent license. Action Register a permanent license.

  • Page 477

    Message ID Message Text Explanation KAPL01081-E The license key file is invalid. Details File name = aa...aa The format of the license key file is invalid. aa...aa: /var/tmp/hdlm_license Action Save the correct license key file in the designated, and then re- execute.

  • Page 478

    Message ID Message Text Explanation Execute help operation-name of the HDLM command (dlnkmgr) to check which parameter can be specified, and then retry. For details on the help operation, see help (Displays the Operation Format) on page 6-4. KAPL01089-E One of the following was Action executed at the same time as Check the license by using the...

  • Page 479

    Message ID Message Text Explanation company for which you have a service contract. KAPL01097-W All the current trace files will be Details deleted. Is this OK? [y/n] If you set a value that is less than the current value of the trace file size or number of trace files, all the current trace files will be deleted.

  • Page 480

    Message ID Message Text Explanation If you did not perform HDLM configuration, Perform HDLM configuration. When performing neither of the above, or if the same error continues to occur even after one of the above procedures is performed, execute the utility for collecting HDLM error information (DLMgetras) to collect the error information, and then contact...

  • Page 481

    Message ID Message Text Explanation Manager, and execute the The audit log configuration file is "dlnkmgr view -sys -audlog" invalid. command and check the setting. Action Restart the HDLM Manager, and execute the dlnkmgr view -sys -audlog command, and then specify the desired setting by using the dlnkmgr set -audlog command or the dlnkmgr set -...

  • Page 482

    Message ID Message Text Explanation HDLM Error Information on page 7-3. KAPL01122-W The file does not exist. File Details name = aa...aa aa...aa: / etc/.DynamicLinkManager/ Path00 Action Reinstall HDLM. KAPL01123-W You do not have read Details permission for the file. File aa...aa: / name = aa...aa etc/.DynamicLinkManager/...

  • Page 483: Kapl03001 To Kapl04000, Kapl03001 To Kapl

    Message ID Message Text Explanation 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 clear (Returns the Path Statistics to the Initial Value) on page 6-3.

  • Page 484

    Message ID Message Text Explanation contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL03004-C A critical error occurred in the Details HDLM API. (aa...aa) This information is required for resolving problems.

  • Page 485: Kapl04001 To Kapl05000, Kapl04001 To Kapl

    Message ID Message Text Explanation HDLM Error Information on page 7-3. KAPL03008-E An error occurred during log Details input to the HDLM alert driver. This information is required for (aa...aa) 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...

  • Page 486

    Message ID Message Text Explanation 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-3. KAPL04003-E The startup parameter is invalid.

  • Page 487

    Message ID Message Text Explanation Use the dlnkmgr set operation to return options settings back to where you had them. If the KAPL04033-W message is not output, restart HDLM manager. If the same error occurs, re-install HDLM. For details on the view operation, see view (Displays Information) on page...

  • Page 488

    Message ID Message Text Explanation HDLM Error Information on page 7-3. KAPL04013-E Input is impossible via the Details communication pipe. RC = Data could not be read from the aa...aa pipe file while communicating with an HDLM command. aa...aa: OS error code (decimal (base-10) number) Action Execute the DLMgetras utility for...

  • Page 489

    Message ID Message Text Explanation HDLM Error Information on page 7-3. KAPL04021-I HDLM manager information - Details aa...aa This information is required for resolving problems. aa...aa: HDLM manager trace information Action None. KAPL04022-W HDLM manager warning Details information - aa...aa This information is required for resolving problems.

  • Page 490

    Message ID Message Text Explanation 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-3. KAPL04025-C A memory shortage occurred in Details...

  • Page 491

    Message ID Message Text Explanation KAPL04033-W The option definition file was re- Details created. When an existing option definition file cannot be read, a new option definition file will be re-created by using the default values. If some of the options can be read, those values can be used.

  • Page 492

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

  • Page 493: Kapl05001 To Kapl06000, Kapl05001 To Kapl

    Message ID Message Text Explanation aa...aa: /HDLM installation path/bin/.dlnkmgr_exe Action Reinstall HDLM. KAPL04052-E You do not have execute Details permission for the file. File aa...aa: /HDLM installation name = aa...aa path/bin/.dlnkmgr_exe 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...

  • Page 494

    Message ID Message Text Explanation how to execute the DLMgetras Execute the utility for setting utility. HDLM driver option (dlmsetopt) and increase the number of retries for allocating memory. For details on the dlmsetopt utility, see dlmsetopt Utility for Setting HDLM Driver Options on page 7-35.

  • Page 495

    Message ID Message Text Explanation None. KAPL05018-W The FO processing in the path Details (aa...aa) failed. (bb...bb:cc...cc) An attempt at FO processing for Check the connection status of path aa...aa has failed. the path aa...aa. If there is no aa...aa: Core logic path identifier problem with the connection for the failed FO (hexadecimal status, execute the DLMgetras...

  • Page 496

    Message ID Message Text Explanation Check the message of the HDLM An attempt to process the command or the HDLM requested IOCTL call has failed. manager, and then take the aa...aa: IOCTL code (hexadecimal appropriate action. If you do not number) know the appropriate action, bb...bb: Error code (hexadecimal...

  • Page 497

    Message ID Message Text Explanation KAPL05704-E The LDEV information for an Details HDLM device has changed. HCTL The LDEV information for the value = aa...aa bb...bb cc...cc HCTL value corresponding to an dd...dd HDLM device has changed. LDEV information (storage system model name, serial number, and LU number, separated by period) aa...aa: Host ID (host port...

  • Page 498

    Message ID Message Text Explanation Driver Options on page 7-35. Increase system memory. Stop any unnecessary processes. If the problem is not solved, 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 499: Kapl06001 To Kapl07000, Kapl06001 To Kapl

    Message ID Message Text Explanation bb...bb: Maintenance information (hexadecimal number) cc...cc: Maintenance information (hexadecimal number) dd...dd: Maintenance information (hexadecimal number) Action None. KAPL06001 to KAPL07000 Message ID Message Text Explanation KAPL06004-E Could not allocate memory. Details (aa...aa:bb...bb) An attempt to reserve memory to save alert information has failed.

  • Page 500

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

  • Page 501

    Message ID Message Text Explanation Check whether any other error occurred. The information that could not be written is discarded. Review the actual memory size when another error does not occur. When the actual memory size is insufficient, increase the actual memory size.

  • Page 502: Kapl07001 To Kapl08000, Kapl08001 To Kapl09000, Kapl07001 To Kapl, Kapl08001 To Kapl

    Message ID Message Text Explanation does not match the currently The version of the kernel booting kernel version. supported by the installed HDLM is different from the currently running kernel version. It may be that you booted the kernel that is different from the kernel when you installed HDLM.

  • Page 503

    Message ID Message Text Explanation 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 a path error is detected ¢ by a path health checking or the online operation Displays 0x000F0000 (Fixed).

  • Page 504

    Message ID Message Text Explanation hh...hh: Host device name (same as HDevName of view -path) Action There could be an error in the path. See What To Do for a Path Error on page 5-3 and restore the path displayed in the message to running status.

  • Page 505: Kapl09001 To Kapl10000, Kapl09001 To Kapl

    Message ID Message Text Explanation because the system judged that an intermittent error was occurring in that path. aa...aa: Path ID (same as PathID of view -path) (decimal (base-10) number) Action An intermittent error has occurred. Check the path for any possible problems.

  • Page 506

    Message ID Message Text Explanation installation program or the uninstallation program. KAPL09011-E Cannot find a license key file / Details etc/opt/DynamicLinkManager/ The license key file, /etc/opt/ dlm.lic_key. DynamicLinkManager/ dlm.lic_key, cannot be found in the specified directory. Action Create a license key file, and re- execute the installation program.

  • Page 507

    Message ID Message Text Explanation Network Objectplaza Trace Action Library 2 failed. Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM. KAPL09023-E A file or directory related to Details HDLM could not be found. Re- A target file to copy to the install HDLM.

  • Page 508

    Message ID Message Text Explanation Execute the /etc/init.d/ DLMManager command with the start parameter to start the HDLM manager. KAPL09037-E The status of the HDLM Details manager could not be checked. An attempt to acquire the status If the HDLM manager does not of the HDLM manager has failed.

  • Page 509

    Message ID Message Text Explanation KAPL09044-I The uninstallation of aa...aa Details completed successfully. HDLM was uninstalled. aa...aa: Name of uninstalled file. Action None. KAPL09045-E An attempt to create a file or Details directory related to HDLM has Installation could not be executed failed.

  • Page 510

    Message ID Message Text Explanation Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM. KAPL09051-E You do not have permission to Details execute the file. File name = Installation or uninstallation failed aa...aa because there was no execution permission for a file.

  • Page 511

    Message ID Message Text Explanation aa...aa: Year (4 digits)/month (01-12)/day (01-31) Action Install a permanent license by the expiration day. KAPL09082-W The temporary license expired. Action Enter a permanent license key. KAPL09083-W The emergency license expired. Action Install a permanent license. KAPL09087-E The entered license key is Details...

  • Page 512

    Message ID Message Text Explanation KAPL09093-I aa...aa will be installed. Is this Details OK? [y/n]: The message checks whether you want to install aa...aa. aa...aa: The version of HDLM to be installed, or the version of the HDLM SP to be installed Action Please enter "y"...

  • Page 513

    Message ID Message Text Explanation KAPL09113-E There is no installable license Details key in the license key file. File There is no HDLM-installable name = aa...aa license key in the license key file. Make sure that the license key aa...aa: /var/tmp/hdlm_license file is correct, and then re-install Action HDLM.

  • Page 514

    Message ID Message Text Explanation the DVD-ROM was copied, make sure that all the contents of the DVD-ROM have been copied to that directory, and then retry the installation. KAPL09135-E One of the following was Action executed at the same time as Check the license by using the an HDLM command set -lic HDLM command's view -sys -...

  • Page 515

    Message ID Message Text Explanation after creating the directory displayed in the message. KAPL09147-E An attempt to create a file Details related to HDLM has failed. File aa...aa: File that an attempt was name = aa...aa. Remove made to create unnecessary files and secure Action free space on the file system.

  • Page 516

    Message ID Message Text Explanation Check the HDLM installation media, or check the current kernel. KAPL09177-I HDLM version: aa...aa Details aa...aa: The version of HDLM to be installed. Action None. KAPL09191-W The installation information Details settings file does not exist. The installation information settings file specified for the second parameter does not exist.

  • Page 517

    Message ID Message Text Explanation aa...aa: installhdlm, installhdlm_analysis, ENVIRONMENT_SETTINGS, driver_config_settings, or dlmcfgmgr Action None. KAPL09211-I aa...aa completed successfully. Details aa...aa completed successfully. aa...aa: installhdlm, installhdlm_analysis, ENVIRONMENT_SETTINGS, driver_config_settings, or dlmcfgmgr Action None. KAPL09212-E aa...aa ended abnormally. Details aa...aa ended abnormally. aa...aa: installhdlm, or installhdlm_analysis Action Check the error message that was...

  • Page 518

    Message ID Message Text Explanation aa...aa: Error number (decimal number) that specifies the executed processing Action If the error code is 4: The /var/tmp directory does not have enough unused capacity, or the user does not have write permission for it. Make sure there is enough unused capacity and that the user has write permission for...

  • Page 519

    Message ID Message Text Explanation KAPL09217-E An error occurred during Details reading of the installation An error occurred while reading information settings file. Error the installation information Code = aa...aa,bb...bb settings file. aa...aa: Error number (decimal number) that specifies the executed processing bb...bb: Return value (decimal number) of the executed...

  • Page 520

    Message ID Message Text Explanation the required files to the correct location, and then retry the operation. If you do not have a required permission, grant required permissions to yourself, and then retry the operation. If aa...aa is dlmcfgmgr: The correct location of dlmcfgmgr is /sbin.

  • Page 521

    Message ID Message Text Explanation aa...aa: Error number (decimal number) that specifies the executed processing bb...bb: Return value (decimal number) of the executed processing cc...cc: Line number (decimal number) of an installation information settings file. Action Specify the revised installation information settings file, and then retry the operation.

  • Page 522

    Message ID Message Text Explanation Code = aa...aa,bb...bb, line = aa...aa: Error number (decimal cc...cc number) that specifies the executed processing bb...bb: Return value (decimal number) of the executed processing cc...cc: Line number (decimal number) of an installation information settings file. Action Specify the revised installation information settings file and then...

  • Page 523

    Message ID Message Text Explanation aa...aa: Error number (decimal number) that specifies the executed processing bb...bb: Return value (decimal number) of the executed processing cc...cc: Line number (decimal number) of an installation information settings file. Action Specify the revised installation information settings file and then retry the operation.

  • Page 524

    Message ID Message Text Explanation KAPL09239-I The system will now restart. Details The host will restart because restart was specified in the installation information settings file. Action None. KAPL09240-I There is no license key file. File Details name = aa...aa If you want to There is no license key file.

  • Page 525

    Message ID Message Text Explanation 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-3. KAPL09269-W The file is invalid. File name = Details aa...aa aa...aa: /...

  • Page 526

    Message ID Message Text Explanation version that can be applied to the installed version of HDLM. KAPL09509-E Service Pack aa...aa cannot be Details installed. The same version has The version of the SP being already been installed. installed is the same as the already installed SP.

  • Page 527: Kapl10001 To Kapl11000, Kapl10001 To Kapl

    Message ID Message Text Explanation If an installation is performed from the DVD-ROM, confirm that the DVD-ROM is not damaged. If an installation is performed by using files copied from the DVD- ROM, re-copy all of the DVD-ROM files. KAPL09603-E The installation will now stop Details because a command or utility...

  • Page 528

    Message ID Message Text Explanation Action Check the parameters of the DLMgetras utility for collecting HDLM error information, and then retry. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL10002-W Too many parameters have Details been specified.

  • Page 529

    Message ID Message Text Explanation KAPL10005-W The number of parameters is Details insufficient. The -f parameter exists but the file for defining the information to be collected does not exist. The number of parameters is insufficient. Action Check the parameters of the DLMgetras utility for collecting HDLM error information, and then retry.

  • Page 530

    Message ID Message Text Explanation Check whether you have access permission for the specified directory. Check whether the specified directory name is correct. Check that the disk has sufficient unused capacity. KAPL10009-W The specified directory already Details exists. Do you want to overwrite The specified directory already it? [y/n]: exists.

  • Page 531

    Message ID Message Text Explanation 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. If the contents of the file are incorrect, correct them and then try to collect error information...

  • Page 532

    Message ID Message Text Explanation 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 information to be collected.

  • Page 533

    Message ID Message Text Explanation aa...aa: Third parameter Action After the DLMgetras utility for collecting HDLM error information terminates, check whether the file for defining the information to be collected is a text file. The file is shown in the message. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page...

  • Page 534

    Message ID Message Text Explanation The utility for collecting HDLM error information terminated before completion. If the directory is unnecessary, delete directory. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL10022-I The utility for collecting HDLM Details error information completed...

  • Page 535

    Message ID Message Text Explanation Action None. KAPL10034-E The file could not be copied. Details Filename = aa...aa, Details = Execution of the cp command bb...bb failed. aa...aa: Name of the file you tried to copy bb...bb: cp command output message Action An error occurred while the...

  • Page 536

    Message ID Message Text Explanation There is no output file, or the user does not have execution permission. aa...aa: file name Action Make sure the specified file exists and the user has execution permission. KAPL10049-I Error information collection Details command = aa...aa, Return aa...aa: Executed command value = bb...bb, Execution time bb...bb: Return value of the...

  • Page 537

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

  • Page 538

    Message ID Message Text Explanation KAPL10312-I HDLM has created an HDLM Details device special file. Device = A logical device file for an HDLM aa...aa device has been created. aa...aa: Logical device file name of HDLM device Action None. KAPL10313-I HDLM has deleted an HDLM Details device special file.

  • Page 539

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

  • Page 540

    Message ID Message Text Explanation Action Specify a correct logical device file name of an HDLM device, and then re-execute the dlmcfgmgr utility. For details on the dlmcfgmgr utility, see dlmcfgmgr Utility for Managing the HDLM Configuration on page 7-22. KAPL10322-E A file that defines HDLM- Details...

  • Page 541

    Message ID Message Text Explanation KAPL10325-E A regular expression cannot be Details established. The files will not be An HDLM device could not be deleted. Errno = aa...aa. deleted because the device could Execute the DLMgetras utility to not be found by using a regular collect error information, and expression.

  • Page 542

    Message ID Message Text Explanation Re-execute the dlmcfgmgr utility. For details on the dlmcfgmgr utility, see dlmcfgmgr Utility for Managing the HDLM Configuration on page 7-22. KAPL10329-E A file could not be opened. File Details name = aa...aa, Errno = The file could not be opened.

  • Page 543

    Message ID Message Text Explanation 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-3. KAPL10332-E The registering of the partition Details information for HDLM device(s) An attempt to register the...

  • Page 544

    Message ID Message Text Explanation 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-3. KAPL10335-E A directory cannot be created.

  • Page 545

    Message ID Message Text Explanation KAPL10339-I This operation will change the Details configuration of HDLM devices. This message checks whether you Do you want to continue? [y/n]: want to change the configuration definition of an HDLM device. Action Enter y to continue. Enter n to cancel.

  • Page 546

    Message ID Message Text Explanation HDLM device = aa...aa, Device By executing the HDLM- = bb...bb (Host: cc...cc configuration definition utility Channel: 0 ID: dd...dd Lun: (dlmcfgmgr), a newly detected ee...ee) path has been added to the registered HDLM device. aa...aa: HDLM device name bb...bb: SCSI device name cc...cc: Host ID (decimal number)

  • Page 547

    Message ID Message Text Explanation Utility for Managing the HDLM Configuration on page 7-22. KAPL10347-I The HDLM device is no longer Details under management. HDLM By executing the HDLM- device = aa...aa configuration definition utility (dlmcfgmgr), the HDLM device has been removed from HDLM management.

  • Page 548

    Message ID Message Text Explanation Execute the following command to load the HDLM driver # /opt/ DynamicLinkManager/bin/ dlminsadrv # modprobe sddlmfdrv Re-execute the dlmcfgmgr utility. For details on the dlmcfgmgr utility, see dlmcfgmgr Utility for Managing the HDLM Configuration on page 7-22.

  • Page 549

    Message ID Message Text Explanation utility to collect error aa...aa: File name information, and then contact Action your vendor or maintenance Execute the DLMgetras utility for company. collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.

  • Page 550

    Message ID Message Text Explanation Restart the host. If the host does not recover, 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...

  • Page 551

    Message ID Message Text Explanation running dlmcfgmgr utility ends, instances of dlmcfgmgr were and then try the dlmcfgmgr executed simultaneously. utility again. Action Wait until the running HDLM- configuration definition utility (dlmcfgmgr) ends, and then re- execute the HDLM-configuration definition utility (dlmcfgmgr). For details on the dlmcfgmgr utility, dlmcfgmgr Utility for Managing the HDLM Configuration...

  • Page 552

    Message ID Message Text Explanation None. For details on the dlmcfgmgr utility, see dlmcfgmgr Utility for Managing the HDLM Configuration on page 7-22. KAPL10362-W HDLM has detected an active Details path that cannot be deleted. An attempt to execute the HDLM- HDLM device = aa...aa, Device configuration definition utility = bb...bb (Host: cc...cc...

  • Page 553

    Message ID Message Text Explanation corresponding to an HDLM device was changed. aa...aa: Logical device file name of an HDLM device Action None. KAPL10365-W The LDEV for an HDLM device Details has changed. The processing for The processing for the HDLM that HDLM device will be device was interrupted because an cancelled.

  • Page 554

    Message ID Message Text Explanation Execute the dlmpr -h utility to check the parameter, and then retry execution. For details on the dlmpr utility, see dlmpr Utility for Clearing HDLM Persistent Reservation on page 7-33. KAPL10644-W The specified parameters cannot Details be specified at the same time.

  • Page 555

    Message ID Message Text Explanation When the error code is 1: Make sure that there is sufficient memory. When the error code is 2: Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. When the error code is 4 or 5: Make sure that the SCSI device file permissions permit reading...

  • Page 556

    Message ID Message Text Explanation KAPL10653-W The entered value is invalid. Details Please re-enter it [y/n]: A value other than y or n has been entered for a [y/n] request. Action Enter y or n. KAPL10665-I The dlmpr utility completed. Details The dlmpr utility completed normally.

  • Page 557

    Message ID Message Text Explanation DynamicLinkManager/ An attempt to open the settings hdlm_utillog.conf, Errno = file for the HDLM utility log (/etc/ aa...aa. Refer to the Messages opt/DynamicLinkManager/ section of the HDLM User's hdlm_utillog.conf) has failed.A Guide for instructions to correct maximum log file size of 1024 KB this problem.

  • Page 558

    Message ID Message Text Explanation Action Execute the dlmcfgmgr utility with the -logfs parameter specified. If the error occurs again, /etc/opt/ DynamicLinkManager/ hdlm_utillog.conf which is not a regular file might exist. Delete / etc/opt/DynamicLinkManager/ hdlm_utillog.conf and then execute the dlmcfgmgr utility again.

  • Page 559

    Message ID Message Text Explanation Action Confirm that the configuration for HDLM devices is correct. If it is not correct, 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 560

    Message ID Message Text Explanation (aa...aa) function. File name = An error occurred during bb...bb, Errno = cc...cc processing to read a file in the (aa...aa) function. bb...bb: File name cc...cc: Errno Action Confirm that the configuration for HDLM devices is correct. If it is not correct, execute the DLMgetras utility for collecting HDLM error information, and then...

  • Page 561: Kapl11001 To Kapl12000, Kapl11001 To Kapl

    KAPL11001 to KAPL12000 Message ID Message Text Explanation KAPL11901-I aa...aa has started. Details The operation has started on the host. aa...aa: Operation (character string) Get Path Information ¢ Get Option Information ¢ Set Option Information ¢ Clear Data ¢ Get HDLM Manager Status ¢...

  • Page 562

    Message ID Message Text Explanation Get HDLM Alert Driver ¢ Status Online ¢ Offline ¢ Get SNMP Trap Information ¢ Set SNMP Trap Information ¢ Set LU Load Balance ¢ Get Path Status Log ¢ Information Get Local Time ¢ Action None.

  • Page 563: Kapl12001 To Kapl13000, Kapl12001 To Kapl

    Message ID Message Text Explanation An exception occurred during processing on the host. Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if you have a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for...

  • Page 564

    Message ID Message Text Explanation Install HDLM that adjusts to the kernel that is running now. KAPL12036-E The HDLM file is invalid. File Details name = aa...aa A file necessary for processing HDLM cannot be found. Alternatively, the content of a file is invalid. aa...aa: Name of file where error was detected.

  • Page 565

    Message ID Message Text Explanation /etc/opt/DynamicLinkManager/ ¢ dlmmkinitrd.conf /lib/modules/kernel-version/ ¢ kernel/drivers/ DynamicLinkManager/ sddlmfdrv.o /lib/modules/kernel-version/ ¢ kernel/drivers/ DynamicLinkManager/ sddlmfdrv.ko /lib/modules/kernel-version/ ¢ kernel/drivers/ DynamicLinkManager/ sddlmadrv.o /lib/modules/kernel-version/ ¢ kernel/drivers/ DynamicLinkManager/ sddlmadrv.ko If the file name displayed in the message is another file name The OS (kernel) or the HBA driver may not be installed correctly.

  • Page 566

    Message ID Message Text Explanation KAPL12313-I Initial ramdisk is being Action unmounted. None. KAPL12314-I The compressed initial Action ramdisk image is being None. created. KAPL12315-I A compressed initial ramdisk Details image aa...aa was created aa...aa: The created initial ramdisk with the ramdisk size = image bb...bb KB.

  • Page 567

    Message ID Message Text Explanation overwriting the existing file, specify the -f parameter. Note that if you attempt to specify an existing directory name as the initial RAM disk image file, it is impossible to overwrite the file even if the -f parameter is specified.

  • Page 568

    Message ID Message Text Explanation KAPL12326-E The command could not Details execute. Command name = aa...aa: The failed command aa...aa Action Perform the following confirmation corresponding to the output command, and then retry. Re-execute the dlmmkinitrd utility for supporting the boot disk after performing the next check according to the outputted command.

  • Page 569

    Message ID Message Text Explanation Confirm that the user has write permission in the root directory (/). mkdir: Confirm that there is enough unused capacity and that the user has write permission in the following directory: /etc/opt/DynamicLinkManager. ¢ /opt/DynamicLinkManager. ¢ The root directory (/) ¢...

  • Page 570

    Message ID Message Text Explanation page 3-124 Upgrade Installation in an Environment Where a Logical Volume (LVM2) on an HDLM Device Is Used as a Boot Disk on page 3-135: - filter - types - md_component_detection In the case of /etc/opt/ DynamicLinkManager/ dlmmkinitrd.conf file Install an HBA driver, which is...

  • Page 571

    Message ID Message Text Explanation Action Perform the dlmmkinitrd utility again after performing the following check: Confirm that the kernel of the version displayed into the message is installed. In Red Hat Enterprise Linux, confirm the kernel version specified as a parameter. For the details of the parameter, dlmmkinitrd Utility for Supporting a Boot Disk on page...

  • Page 572

    Message ID Message Text Explanation Also, make sure that the HBA driver has been installed. KAPL12334-E Multiple root partition entries Details exist in the file. File name = aa...aa: The name of the file aa...aa referenced by the dlmmkinitrd utility for supporting the boot disk Action Modify the fstab file specified in the...

  • Page 573

    Message ID Message Text Explanation KAPL12342-I Execution of bootup script Action completed. None. KAPL12343-I The bootup executable is Action being created. None. KAPL12344-I A compressed initial ramdisk Details image (aa...aa) was created. aa...aa: The created initial ramdisk image Action None. KAPL12345-E The version of the kernel Details...

  • Page 574

    Message ID Message Text Explanation The collection of files for HDLM completed. Action None. KAPL12551-E The utility for setting HDLM Action driver option can be Change the utility name back to executed with the name dlmsetopt, and then execute it. dlmsetopt only.

  • Page 575

    Message ID Message Text Explanation KAPL12558-I Please restart the computer Action so that the option settings Restart the computer. take effect. KAPL12559-E An invalid value was Details specified in the parameter. aa...aa: Option Option = aa...aa, Parameter bb...bb: Specified = bb...bb parameter(Maximum 10 characters.

  • Page 576

    Message ID Message Text Explanation utility for setting HDLM driver option (dlmsetopt). Delete any unnecessary files in the file system, and then re-execute the dlmsetopt utility. KAPL12564-E An attempt to back up a file Details has failed. File name = aa...aa: Backup file name aa...aa Action...

  • Page 577

    Message ID Message Text Explanation DLMSETOPT/modprobe.conf file, and then re-configure the content that was configured in the /etc/modprobe.conf file according to the user's environment. Then, delete the / etc/opt/DynamicLinkManager/ DLMSETOPT/modprobe.conf file. Finally, re-execute the dlmsetopt utility to make sure that an error does not occur. KAPL12567-E The version of the kernel Details...

  • Page 578: Kapl13001 To Kapl14000, Kapl13001 To Kapl

    Message ID Message Text Explanation HDLM does not match the The version of the kernel to which currently running kernel installed HDLM has adjusted and the version. kernel that is running now is not corresponding. There is a possibility of installing the package of the kernel after installing HDLM.

  • Page 579

    Message ID Message Text Explanation Reinstall HDLM. KAPL13205-W You do not have read Details permission for the file. File aa...aa: / name = aa...aa etc/.DynamicLinkManager/ Path00, /etc/.HBaseAgent/ Path00 Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company, if you have a maintenance contract for HDLM.

  • Page 580

    Message ID Message Text Explanation KAPL13403-E You lack write permission for Details the specified directory. Value= You do not have write permission aa...aa for the specified directory, or the creation of a subdirectory of the specified directory failed. aa...aa: first parameter Action Check the following.

  • Page 581

    Message ID Message Text Explanation cc...cc: the year of grace/month/ day hour:minute:second(GMT) Action None. KAPL13408-E Processing terminated before Details completion because a signal was The process has been terminated received. by an operation such as Ctrl + c. Action The utility for collecting HDLM install error information terminated before completion.

  • Page 582

    Message ID Message Text Explanation The file subject to collecting does not exist. aa...aa: Name of file to collect Action None. KAPL13414-E The file could not be copied. File Details = aa...aa, Details = bb...bb Execution of the cp command failed.

  • Page 583

    Message ID Message Text Explanation After installing HDLM, re-execute the installgetras utility. KAPL13418-E Too many parameters have Details been specified. Two or more parameters have been specified. Action Check the parameters of the utility for collecting HDLM install error information, and then retry. KAPL13501-I The utility for update system Action...

  • Page 584

    Message ID Message Text Explanation was output just before this message. KAPL13508-E You lack permission for Details executing the utility for update The current user does not have system scripts. authority to execute dlmupdatesysinit utility. Action Re-execute dlmupdatesysinit utility as a user with root permission.

  • Page 585

    Message ID Message Text Explanation Check for parameters, and then re-execute the dlmupdatesysinit utility. Refer to dlmupdatesysinit Utility for Updating System Scripts on page 7-39. KAPL13514-W Usage: /opt/ Action DynamicLinkManager/bin/ Check for parameters, and then dlmupdatesysinit re-execute the dlmupdatesysinit utility. Refer to dlmupdatesysinit Utility for Updating System Scripts on page...

  • Page 586

    Message ID Message Text Explanation dlmupdatesysinit Utility for Updating System Scripts on page 7-39. KAPL13519-E An HDLM file required for the Details dlmupdatesysinit utility was not aa...aa: File name found. File name = aa...aa Action Reinstall an HDLM. KAPL13520-E An HDLM directory required for Details the dlmupdatesysinit utility was aa...aa: Directory name...

  • Page 587

    Message ID Message Text Explanation command and check whether a The audit log configuration file normal result is displayed. cannot be opened. Action If the "dlnkmgr view -sys - audlog" command does not display a normal result, contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM.

  • Page 588

    Message ID Message Text Explanation KAPL13902-I Alert driver had been loaded. Action Alert driver's loading was None. skipped. KAPL13903-I The process related to Alert Action driver had been completed. The None. process related to Alert driver was skipped. KAPL13904-I Filter driver had been loaded. Action Filter driver's loading was None.

  • Page 589

    Message ID Message Text Explanation KAPL13909-W Usage: /opt/ Action DynamicLinkManager/bin/ Re-execute the utility for HDLM dlmstart start if necessary. Refer to dlmstart Utility for Starting HDLM on page 7-38. KAPL13910-W The error occurred while Action processing the utility for HDLM Resolve the problem according to start.

  • Page 590: Kapl15001 To Kapl16000

    Message ID Message Text Explanation Remove the error cause described in the message output by the command indicated in the message KAPL13913-E. Next, re- execute the utility for HDLM start if necessary. Refer to dlmstart Utility for Starting HDLM on page 7-38.

  • Page 591

    Message ID Message Text Explanation KAPL15044-I Processing to add devices to Details HDLM management succeeded. aa...aa: Name of the utility that Command Line = aa...aa the user executed KAPL15045-E Processing to add devices to Details HDLM management has failed. aa...aa: Name of the utility that Command Line = aa...aa the user executed KAPL15046-I...

  • Page 592

    Message ID Message Text Explanation command has failed. Command Line = aa...aa KAPL15056-I The number of retries for the Details SCSI INQUIRY command was aa...aa: Name of the utility that successfully set. Command Line the user executed = aa...aa KAPL15057-E An attempt to set the number of Details retries for the SCSI INQUIRY...

  • Page 593

    Message ID Message Text Explanation KAPL15101-I Clear operation was completed Details successfully. Command Line = aa...aa: Command that the user aa...aa executed KAPL15102-E Clear operation has failed. Details Command Line = aa...aa aa...aa: Command that the user executed KAPL15103-I aa...aa path(s) were Details successfully placed bb...bb.

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

    Message ID Message Text Explanation KAPL15401-I HDLM Manager successfully started. KAPL15402-E Could not start the HDLM manager. KAPL15403-I HDLM Manager successfully stopped. KAPL15404-W The HDLM Manager was executed by the user who does not have the authority. Return Codes for Hitachi Command Suite Common Agent Component When an operation requested of HDLM from Global Link Manager terminates abnormally, or terminates normally with a warning, HDLM outputs one of the...

  • Page 595

    Message ID Explanation Action Click Refresh to update the host information, check the path status, and then retry the offline operation. 1015 Details The Offline path cannot be placed Online. Action Remove the error in the path, and then retry. 1016 Details The target path(s) are already Online.

  • Page 596

    Message ID Explanation 1026 Details The acquisition of path information has been aborted, because the path configuration was changed while the system was attempting to acquire the path information. Action Refresh the host information, check the path status, and then perform the operation again. 1027 Details The error monitoring interval and the number of times that...

  • Page 597

    Message ID Explanation Action Re-execute the command. If the same error occurs again, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3.

  • Page 598

    Message ID Explanation you have a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. 8-138 Messages Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 599: A Notes On Linux Commands And Files

    Notes on Linux Commands and Files This section provides notes on Linux commands and files. □ Notes on the /proc/partitions File □ Notes on Linux Commands □ Notes on the iostat Command □ Notes on the mkfs Command □ Notes on the fdisk Command □...

  • Page 600: Notes On The /proc/partitions File, Notes On Linux Commands

    Notes on the /proc/partitions File The HDLM device and each partition of the HDLM device that is recognized by Linux and can be used are recorded in the /proc/partitions file. The / proc/partitions file records the I/O statistics per device; however, it does not record the I/O statistics of the HDLM device.

  • Page 601: Notes On The Iostat Command

    Table A-1 Examples of Linux Command Execution Times Time Linux Example 1 Example 2 commands Before HDLM After HDLM Before HDLM After HDLM installation installation installation installation lvmdiskscan 6.1 sec 19.6 sec 3.8 sec 10.6 sec pvscan 2.6 sec 12.6 sec 1.5 sec 5.2 sec CPU: Pentium III 1.4 GHz x 2...

  • Page 602: Notes On The Mkfs Command, Notes On The Fdisk Command, Notes On The Sar Command

    Notes on the mkfs Command If you are going to create a file system for an HDLM device, specify the name of a logical device file of the HDLM device for the mkfs command. However, if a file system is created for a SCSI device that is already in use, the applicable HDLM device will be created with a file system even without creating a new file system by using the mkfs command.

  • Page 603: Notes On The Fdisk And Parted Commands, Notes On The Parted Command

    Figure A-3 Example of Executing the sar Command Notes on the fdisk and parted Commands When creating partitions on an HDLM device, only use the fdisk command or the parted command. If partitions have been created on an HDLM device using the fdisk or parted command, some of the partitions created by the fdisk command might not be visible to the parted command.

  • Page 604

    change, deactivate the volume group, and then activate the volume group after restarting the md device. Notes on Linux Commands and Files Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 605: B Troubleshooting Products That Use The Weak-modules Script

    Troubleshooting Products That Use the Weak-Modules Script This section explains how to deal with errors that are caused by installing or uninstalling products that use the weak-modules script. □ Overview □ Installing Products That Use the Weak-Modules Script □ Uninstalling Products That Use the Weak-Modules Script Troubleshooting Products That Use the Weak-Modules Script Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 606: Overview, Installing Products That Use The Weak-modules Script

    Overview If you use an HDLM device as a boot disk in Red Hat Enterprise Linux 5 and attempt to install or uninstall a product that uses the weak-modules script, the following message might be output, and installation or uninstallation of that product might fail: grubby fatal error: unable to find a suitable template Therefore, when using an HDLM device as a book disk in Red Hat Enterprise...

  • Page 607

    proc /proc proc defaults /dev/sddlmaa3 swap swap defaults Example when the boot loader is grub and LVM is used: # cat /etc/fstab /dev/VolGroup00/LogVol00 / ext3 defaults /dev/VolGroup00/LogVol02 /tmp ext3 defaults /dev/VolGroup00/LogVol04 /usr ext3 defaults /dev/VolGroup00/LogVol03 /opt ext3 defaults /dev/sda1 /boot ext3 defaults /dev/sddlmaa1...

  • Page 608

    Perform installation according to the documentation for relevant products (packages). Back up the currently used initial RAM disk image file for HDLM. Execute the dlmmkinitrd utility (utility for supporting a boot disk) with the -f parameter specified to create an initial RAM disk image file for HDLM.

  • Page 609

    The underlined portion is the device that indicates the root directory (/). # mount /dev/sddlmaa2 on / type ext3 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) /dev/sddlmaa1 on /boot/efi type vfat (rw) tmpfs on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)

  • Page 610: Uninstalling Products That Use The Weak-modules Script

    Uninstalling Products That Use the Weak-Modules Script To uninstall a product that uses the weak-modules script: Add a parameter to the boot loader configuration file. Perform steps 1 and 2 in Installing Products That Use the Weak-Modules Script on page B-2.

  • Page 611: Functional Differences Between Version 5.9.4 Or Later And Versions Earlier Than 5

    Functional Differences Between Versions of HDLM This section explains the functional differences between newer and older versions of HDLM. □ Functional Differences Between Version 7.2 and Versions Earlier Than 7.2 □ Functional Differences Between Version 6.2.1 and Versions Earlier Than 6.2.1 □...

  • Page 612

    □ Functional Differences Between Version 5.7.0-01 or Later and Versions Earlier Than 5.7.0-01 □ Functional Differences Between Version 5.7 or Later and Versions Earlier Than 5.7 □ Functional Differences Between Version 5.6.3 or Later and Versions Earlier Than 5.6.3 □ Functional Differences Between Version 5.4 or Later and Versions Earlier Than 5.4 Functional Differences Between Versions of HDLM Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 613

    Functional Differences Between Version 7.2 and Versions Earlier Than 7.2 • When creating an initial RAM disk image file in Red Hat Enterprise Linux 6, the dracut command is now used, instead of the dlmmkinitrd boot disk support utility. Due to this change, the dlmmkinitrd utility is no longer installed in a Red Hat Enterprise Linux 6 environment.

  • Page 614

    Functional Differences Between Version 5.9.4 or Later and Versions Earlier Than 5.9.4 • The maximum number of LUs for one port for one storage that was guaranteed in HDLM for each storage system is now guaranteed for each • The maximum number of LUs guaranteed in HDLM has been changed to 512.

  • Page 615

    Functional Differences Between Version 5.8 or Later and Versions Earlier Than 5.8 Table C-1 JRE/JDK Version Required for HDLM GUI on page C-5 describes the version of the JRE or JDK required to use the HDLM GUI on a host. Table C-1 JRE/JDK Version Required for HDLM GUI Required version of JRE or Earlier than...

  • Page 616

    Functional Differences Between Version 5.7 or Later and Versions Earlier Than 5.7 In version 5.7 or later, if there are no files under the /etc/opt/ DynamicLinkManager directory when HDLM is uninstalled, the directory is deleted. Functional Differences Between Version 5.6.3 or Later and Versions Earlier Than 5.6.3 Table C-2 JRE/JDK Version Required for HDLM GUI on page C-6 describes...

  • Page 617: Acronyms And Abbreviations

    Acronyms and abbreviations The following acronyms and abbreviations might be used in this guide. Application Programming Interface BIOS Basic Input / Output System Complete Fair Queuing Channel Adapter CLPR Cache Logical Partition Central Processing Unit Control Unit Acronyms-1 Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 618

    DBMS Database Management System Device Desktop Management Interface Domain Name Server DRBD Distributed Replicated Block Device ELILO Extensible Firmware Interface Linux Loader EM64T Extended Memory 64 Technology Extended UNIX Code EVMS Enterprise Volume Management System Extended File System Fibre Channel FC-SP Fibre Channel Security Protocol Acronyms-2...

  • Page 619

    Failover FQDN Fully Qualified Domain Name Greenwich Mean Time GRUB GRand Unified Bootloader Graphical User Interface Host Bus Adapter HDev Host Device Host Logical Unit HTTP Hypertext Transfer Protocol Input/Output IA32 Intel Architecture 32 Integrated Drive Electronics Acronyms-3 Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 620

    Internet Protocol Inter Process Communication Itanium(R) Processor Family Interrupt ReQuest iSCSI Internet Small Computer System Interface Kernel-based Virtual Machine Local Area Network LDAP Lightweight Directory Access Protocol LDEV Logical Device LILO Linux Loader Logical Unit Logical Unit Number Logical Volume Manager Acronyms-4 Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 621

    Multiple Devices Network Attached Storage Network Interface Card Network Time Protocol Operating System Port Peripheral Component Interconnect RADIUS Remote Authentication Dial in User Service Storage Area Network Acronyms-5 Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 622

    SCSI Small Computer System Interface SLPR Storage Logical Partition SMTP Simple Mail Transfer Protocol SNMP Simple Network Management Protocol Service Pack Secure Sockets Layer Service Processor UUID Universally Unique Identifier Volume Group World Wide Name Acronyms-6 Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 623: 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 624

    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 split up a cache into parity groups in the storage system, so that other parity groups do not affect the cache performance.

  • Page 625

    failback A function for placing the status of a path recovered from an error into the Online status, and then switching the access path to the path that was just recovered. 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.

  • Page 626: Load Balancing, Host Lu Number, Intermittent Error, Kvm (kernel-based Virtual Machine), Ldev (logical Device)

    (See also: LU, host LU number, host device) host LU number A number assigned to a host LU. The host LU number is part of a path name. (See also: host LU, path name) hypervisor Software that enables host virtualization. intermittent error An error that occurs irregularly due to, for example, a loose cable connection.

  • Page 627: Logical Device File, Lu (logical Unit)

    logical device file A device file in the /dev directory. Note that the term logical device here is different from LDEV. LU (Logical Unit) A logical unit that is a logical volume defined in the storage system, and with which the host can perform input or output operations.

  • Page 628: Physical Path

    path An access path from a host to a storage system. Access to an area within an LU in a storage system is made via a cable connecting the HBA on the host and the CHA on the storage system. This cable is a path. Each path has an AutoPATH_ID. (See also: AutoPATH_ID) path health checking A function for checking the status of paths at regular intervals.

  • Page 629

    reservation The reservation function enables a host to declare that it has exclusive rights to use a particular LU, and prevents other hosts from accessing that LU. Access permission for an LU that has been reserved is given only to the host that issued the reservation, so the LU cannot be accessed from multiple paths (coming from multiple hosts) simultaneously.

  • Page 630

    Glossary-8 Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 631

    Index Symbols when using Red Hat Enterprise Linux AS4/ES4 3-32, 3-33, 3-34, 3-35 /proc/partitions files when using SUSE LINUX Enterprise Server 10 3-55, 3-56, 3-57 when using SUSE LINUX Enterprise Server 11 3-59 active host 2-45 boot loader configuration file 3-106 adding new LU 4-34...

  • Page 632

    when using Red Hat Enterprise Linux 5 3-36 putting under HDLM management 4-40 when using Red Hat Enterprise Linux 6 3-49 removing from HDLM management 4-40 when using Red Hat Enterprise Linux AS4/ES4 directory to which collected information is output 3-16 when using SUSE LINUX Enterprise Serve 9 3-50 Displayed program information...

  • Page 633

    Error-level errors 2-33 ErrorCode handling errors path error detected by HDLM 2-33 2-4, 3-16 management 2-30 procedure for replacing 4-23 examining replacing 4-22 message 5-5, 5-6 HBA (Host Bus Adapter) Glossary-3 HDev HDevName HDLM failback 2-18, Glossary-3 features failover 2-18, Glossary-3 functions FC-SAN 2-3, 2-4, Glossary-3...

  • Page 634: Table Of Contents

    help IP-SAN 2-4, 2-6, Glossary-4 Hitachi Network Objectplaza Trace Library IP-SAN environments supported by HDLM Notes 3-193 iSCSI 2-6, Glossary-4 Hitachi Network Objectplaza Trace Library iSCSI software (HNTRLib2) Uninstalling 3-226 host 3-3, Glossary-3 kernel host bus adapter when using Oracle Enterprise Linux 4 3-13 host device 2-7, Glossary-3...

  • Page 635

    recognized by host LU configuration recognized by the host obtaining LUKS path information notes 3-152 program information LVM2 offline 2-18, 6-5 notes on using LVM2 3-166 offline(C) status 2-22 setting LVM2 3-166 offline(E) status 2-22 lvrename commands online 2-18, 6-10 online status 2-22 online(E) status...

  • Page 636

    path information Red Hat Enterprise Linux AS4/ES4 3-80 obtaining boot disk environment and BladeSymphony path name Glossary-6 environment 3-32 path status transition 2-22 cluster software 3-16 path switching file system 3-32 automatically 2-19 kernel manually 2-21 volume manager 3-30 PathID related products PathName related products when using Oracle Enterprise...

  • Page 637

    SUSE LINUX Enterprise Server 10 3-80 for updating system scripts 7-39 boot disk environment and BladeSymphony installing HDLM 7-41 environment 3-55 installux.sh, Utility for HDLM Common Installer cluster software 3-51 7-48 file system 3-55 overview kernel 3-10 utility volume manager 3-53 for collecting HDLM installation error information SUSE LINUX Enterprise Server 11...

  • Page 638

    Index-8 Hitachi Dynamic Link Manager User Guide (for Linux(R))

  • Page 639

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

  • Page 640

    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: