Page of 746
Download Table of ContentsContents Print This PagePrint Bookmark

HP XP P9500 User Manual

Hitachi dynamic link manager software user's guide for linux (6.x) (hit5203-96004, october 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 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746
Hitachi Dynamic Link Manager Software
User's Guide (for Linux(R))
3000-3-F04-60(E)

Advertising

   Also See for HP XP P9500

   Related Manuals for HP XP P9500

   Summary of Contents for HP XP P9500

  • Page 1

    Hitachi Dynamic Link Manager Software User's Guide (for Linux(R)) 3000-3-F04-60(E)

  • Page 2

    Emulex is a registered trademark of Emulex Corporation. HP-UX is a product name of Hewlett-Packard Company. HP StorageWorks is a trademark of Hewlett-Packard Company. Intel Xeon is a trademark of Intel Corporation in the United States and other countries.

  • Page 3

    Summary of Amendments The following table lists changes in this manual (3000-3-F04-60(E)) and product changes related to this manual. Changes Location in this manual Systems that use an IP-SAN are now supported. 2.2, 2.2.2, 3.1.1, 3.1.2, 3.1.4, 3.1.5, 3.6.3, 3.6.6, 3.22.1, 3.22.2, 4.6.4, 6.7.2, 7.2.3, 7.10.3, Appendix D The following messages have been added: 2.12.1, 8.4, 8.5, 8.10, 8.14...

  • Page 5

    Preface This manual describes the functions and use of the following program products: • Hitachi Dynamic Link Manager Intended Readers This manual is intended for system administrators who use Hitachi Dynamic Link Manager (HDLM) to operate and manage storage systems. The readers of this manual must have a basic knowledge of the following areas: •...

  • Page 6: Related Publications

    problems that you might encounter. 6. Command Reference Chapter 6 describes all the HDLM commands. 7. Utility Reference Chapter 7 describes the HDLM utilities. 8. Messages Chapter 8 provides information for all the possible messages that could be output by HDLM. It also lists and explains the HDLM messages and shows the actions to be taken in response to each message.

  • Page 7

    • HITACHI Gigabit Fibre Channel Board User's Guide • ServerConductor/DeploymentManager User's Guide Conventions: Abbreviations This manual uses the following abbreviations for product names. Abbreviation Full name or meaning Device Manager Agent Device Manager Agent included in Hitachi Device Manager Hitachi Global Link Manager Global Link Manager HDLM Hitachi Dynamic Link Manager...

  • Page 8

    Abbreviation Full name or meaning HP XP128 HP StorageWorks XP128 Disk Array HP XP1024 HP StorageWorks XP1024 Disk Array HP XP10000 HP StorageWorks XP10000 Disk Array HP XP12000 HP StorageWorks XP12000 Disk Array HP XP20000 HP StorageWorks XP20000 Disk Array HP XP24000 HP StorageWorks XP24000 Disk Array HP XP series...

  • Page 9

    Abbreviation Full name or meaning Oracle RAC A generic term for: • Oracle9i Real Application Clusters • Oracle Real Application Clusters 10g • Oracle Real Application Clusters 11g P9500 HP StorageWorks P9500 Disk Array Red Hat Enterprise Linux A generic term for: •...

  • Page 10

    Abbreviation Full name or meaning SUSE LINUX Enterprise Server A generic term for: • SUSE LINUX(R) Enterprise Server 9 • SUSE LINUX(R) Enterprise Server 10 • SUSE LINUX(R) Enterprise Server 11 HP StorageWorks 200 Storage Virtualization System Thunder 9200 Hitachi Freedom Storage Thunder 9200 Universal Storage Platform V/VM A generic term for: •...

  • Page 11

    Abbreviation Full name or meaning CLPR Cache Logical Partition Central Processing Unit Control Unit 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 EVMS Enterprise Volume Management System Extended File System...

  • Page 12

    Abbreviation Full name or meaning 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 Multiple Devices Network Attached Storage Network Interface Card...

  • Page 13

    Abbreviation Full name or meaning UUID Universally Unique Identifier Volume Group World Wide Name Conventions: Diagrams This manual uses the following conventions in diagrams: Conventions: Fonts and Symbols Font and symbol conventions are classified as: • General font conventions • Conventions in syntax explanations These conventions are described below.

  • Page 14

    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. For example, bold is used in sentences such as the following: • From the File menu, choose Open. •...

  • Page 15

    Example font or symbol Convention Square brackets enclose an item or set of items whose specification is optional. An item that is underlined is specified when all items are omitted. One of the options enclosed in { } must be specified. Only one of the options separated by a vertical bar can be specified at the same time.

  • Page 17: Table Of Contents

    Contents Preface Intended Readers ......................i Organization of This Manual ..................i Related Publications....................ii Conventions: Abbreviations ..................iii Conventions: Diagrams ....................ix Conventions: Fonts and Symbols................ix Conventions: KB, MB, GB, and TB ................xi 1. Overview of HDLM 1.1 What is HDLM? ......................2 1.2 HDLM Features......................4 2.

  • Page 18: Table Of Contents

    2.11.3 Collecting Error Information Using the Utility for Collecting HDLM Error Information (DLMgetras)................43 2.11.4 Utility for Collecting HDLM Installation Error Information (installgetras) ....................43 2.12 Collecting Audit Log Data..................44 2.12.1 Categories and Audit Events that HDLM Can Output to the Audit Log ... 45 2.12.2 Requirements for Outputting Audit Log Data ..........

  • Page 19: Table Of Contents

    3.7.1 Notes on Installing HDLM in a Boot Disk Environment......172 3.7.2 Overview of the Procedure for Installing HDLM in a Boot Disk Environment....................175 3.7.3 Settings for Using an HDLM Device as a Boot Disk .........177 3.7.4 Upgrade Installation in an Environment Where an HDLM Device Is Used as a Boot Disk ....................188 3.7.5 Settings for Using a Logical Volume (LVM2) on an HDLM Device as a Boot Disk ......................197...

  • Page 20: Table Of Contents

    3.20.2 When Using Red Hat Enterprise Linux AS4/ES4 or SUSE LINUX Enterprise Server ......................282 3.21 Creating File Systems for HDLM (When Volume Management Software Is Not Used)........................284 3.21.1 Mounting a File System................284 3.21.2 Creating a File System................284 3.22 Settings for Automatic Mounting ................

  • Page 21: Table Of Contents

    4.3.5 Displaying Corresponding Information About an HDLM Device, SCSI Device, and LDEV..................344 4.3.6 Initializing Statistical Information for Paths ..........345 4.3.7 Viewing and Setting Up the Operating Environment........346 4.3.8 Viewing License Information..............348 4.3.9 Updating the License...................348 4.3.10 Viewing HDLM Version Information ............349 4.3.11 Viewing HDLM Component Information ..........350 4.4 Starting and Stopping the HDLM Manager............352 4.4.1 Starting the HDLM Manager ..............352...

  • Page 22: Table Of Contents

    6.3.1 Format......................402 6.3.2 Parameter ....................402 6.4 offline (Places Paths Offline)................. 404 6.4.1 Format......................404 6.4.2 Parameters ....................404 6.5 online (Places Paths Online) .................. 409 6.5.1 Format......................409 6.5.2 Parameters ....................409 6.6 set (Sets Up the Operating Environment) .............. 414 6.6.1 Format......................

  • Page 23: Table Of Contents

    7.10.3 Editing an Installation-Information Settings File........514 7.11 installux.sh Utility for HDLM Common Installer ..........521 7.11.1 Format .......................521 7.11.2 Parameters ....................521 7.11.3 Log file ......................521 8. Messages 8.1 Before Viewing the List of Messages..............524 8.1.1 Format and Meaning of Message IDs ............524 8.1.2 Terms Used in Messages and Message Explanations .........524 8.1.3 Components That Output Messages to syslog ..........524 8.2 KAPL01001 to KAPL02000 ..................526...

  • Page 24: Table Of Contents

    C.3 Functional Differences Between Version 6.0 or Later and Versions Earlier Than 6.0 ......................... 703 C.4 Functional Differences Between Version 5.9.4 or Later and Versions Earlier Than 5.9.4..................... 703 C.5 Functional Differences Between Version 5.9.1 or Later and Versions Earlier Than 5.9.1.....................

  • Page 25: Overview Of Hdlm

    Chapter 1. Overview of HDLM HDLM is a software package that manages paths between a host and a storage system. HDLM is designed to distribute loads across multiple paths and will switch a given load to another path if there is a failure in the path that is currently being used, thus improving system reliability.

  • Page 26: What Is Hdlm

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

  • Page 27

    1. Overview of HDLM • Lightning 9900V series • Thunder 9500V series • Universal Storage Platform V/VM • Virtual Storage Platform...

  • Page 28: Hdlm Features

    1. Overview of HDLM 1.2 HDLM Features HDLM features include the following: The ability to distribute a load across multiple paths. This is also known as load balancing. When a host is connected to a storage system via multiple paths, HDLM can distribute the load across all the paths.

  • Page 29: Hdlm Functions

    Chapter 2. HDLM Functions This chapter describes the various functions that are built into HDLM. Before the function specifications are explained though, this chapter will go into detail about the HDLM management targets, system configuration, and basic terms that are necessary to know to effectively operate HDLM.

  • Page 30: Devices Managed By Hdlm

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

  • Page 31: System Configuration, System Configuration Using An Fc-san

    2. HDLM Functions 2.2 System Configuration HDLM manages routes between a host and a storage system by using the SCSI driver. A host and a storage system are connected via an FC-SAN or an IP-SAN. 2.2.1 System Configuration Using an FC-SAN In an FC-SAN, fiber cables connect hosts to storage systems.

  • Page 32

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

  • Page 33: System Configuration Using An Ip-san

    2. HDLM Functions Components Description Path A route that connects a host and a Dev. 2.2.2 System Configuration Using an IP-SAN In an IP-SAN, LAN cables are used to connect hosts to storage systems. The cable port on the host is called a network interface card (NIC). In order to use an NIC, the iSCSI software must be installed ahead of time on the host.

  • Page 34

    2. HDLM Functions Figure 2-2: Configuration of an HDLM System When Using an IP-SAN Table 2-2: HDLM System Components When Using an IP-SAN lists the HDLM system components when using an IP-SAN. Table 2-2: HDLM System Components When Using an IP-SAN Components Description iSCSI software...

  • Page 35

    2. HDLM Functions Components Description Physical path A route that connects a host and an LU. Path A route that connects a host and a Dev. IP-SAN environments supported by HDLM HDLM supports system configurations that use an IP-SAN in the following environments: •...

  • Page 36: Lu Configuration

    2. HDLM Functions 2.3 LU Configuration After you have properly installed HDLM, the LU configuration will change as follows: Before the installation of HDLM: The host recognizes that a SCSI device is connected to each path. Thus, a single LU in the storage system is recognized as though there are as many LUs as there are paths.

  • Page 37

    2. HDLM Functions Figure 2-3: LU Configuration Recognized by the Host After HDLM Installation Table 2-3: LU Components 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 38: Program Configuration

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

  • Page 39

    2. HDLM Functions Table 2-4: Functionality of HDLM Programs Program name Functions HDLM command Provides the command, which enables you to: dlnkmgr • Manage paths • Display error information • Set up the HDLM operating environment HDLM utility Provides the HDLM utility, which enables you to: •...

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

    2. HDLM Functions 2.5 Position of the HDLM Driver and HDLM Device The HDLM driver is positioned above the SCSI driver. Each application on the host uses the HDLM device (logical device file) created by HDLM, to access LUs in the storage system.

  • Page 41: Logical Device Files For Hdlm Devices

    2. HDLM Functions 2.6 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 42

    2. HDLM Functions 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 , it indicates partition sddlmaa1 1 on...

  • Page 43: Distributing A Load Using Load Balancing

    2. HDLM Functions 2.7 Distributing a Load Using Load Balancing When the system contains multiple paths to a single LU, HDLM can distribute the load across the paths by using multiple paths to transfer the I/O data. This function is called load balancing, and it prevents a single, heavily loaded path from affecting the performance of the entire system.

  • Page 44

    2. HDLM Functions Figure 2-7: Flow of I/O Data When the Load Balancing Function Is Not Used When the load balancing function is not used, I/O operations converge onto a single path (A). The load on that one path (A) will cause a bottleneck, which might cause problems with system performance.

  • Page 45: Paths To Which Load Balancing Is Applied

    2. HDLM Functions Figure 2-8: Flow of I/O Data When the Load Balancing Function Is Used When the load balancing function is used, I/O operations are distributed via multiple paths (A, B, C, and D). This helps to prevent problems with system performance and helps prevent bottlenecks from occurring.

  • Page 46

    2. HDLM Functions that uses a CHA other than the owner controller (a non-owner controller). Paths used for load balancing are selected from owner paths first, then non-owner paths. To prevent performance in the entire system from deteriorating, HDLM does not perform load balancing between owner paths and non-owner paths.

  • Page 47: Load Balancing Algorithms

    2. HDLM Functions Data When the Load Balancing Function Is Used, the load is balanced among the four paths A, B, C, and D. If one of the paths were to become unusable, the load would be balanced among the three, remaining paths. 2.7.2 Load Balancing Algorithms HDLM has the following six load balancing algorithms: •...

  • Page 48

    2. HDLM Functions • Extended Round Robin The paths are simply selected in order from among all the connected paths. • Extended Least I/Os The path that has the least number of I/Os being processed is selected from among all the connected paths. •...

  • Page 49: Performing Failovers And Failbacks Using Path Switching, Automatic Path Switching

    2. HDLM Functions 2.8 Performing Failovers and Failbacks Using Path Switching When the system contains multiple paths to an LU and an error occurs on the path that is currently being used, HDLM can switch to another functional path, so that the system can continue operating.

  • Page 50

    2. HDLM Functions For details on error levels, see 2.11.2 Filtering of Error Information. When the Thunder 9500V series, or Hitachi AMS/WMS series is being used, HDLM will select the path to be used next from among the various paths that access the same LU, starting with owner paths, and then non-owner paths.

  • Page 51

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

  • Page 52: Manual Path Switching

    2. HDLM Functions Storage Platform V/VM, Virtual Storage Platform, Hitachi AMS2000 series, or Hitachi SMS is being used, all the paths are owner paths. As a result, if the path that was previously used recovers from an error, and then HDLM automatically places the recovered path online, the path that is currently being used will continue to be used (as opposed to switching over to the path that was just recovered).

  • Page 53: Path Status Transition

    2. HDLM Functions Executing the online operation places the offline path online. For details on the operation, see 6.5 online (Places Paths Online). After a path status is online changed to online, the path can be selected as a useable path by HDLM in the same manner as automatic path switching.

  • Page 54

    2. HDLM Functions The status indicating that an I/O could not be issued on a given path, because an error occurred on the path. The (E) means error. (3) Status Transitions of a Path Figure 2-11: Path Status Transitions shows the status transitions of a path. Figure 2-11: Path Status Transitions Legend: Online operation: Online operation performed by executing the...

  • Page 55

    2. HDLM Functions • All the paths connected to an LU are , or Online(E) Offline(E) Offline(C) • All the paths connected to an LU have been determined to have an intermittent error. • The processing of continuous I/O operations issued to an LU is successful. When an Online or Offline(E) path exists among the paths that access the same If there is only one available online path for an LU, it cannot be placed offline by executing the...

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

    2. HDLM Functions 2.9 Monitoring Intermittent Errors (Functionality When Automatic Failback Is Used) An intermittent error refers to an error that occurs irregularly because of something like a loose cable. In such a case, I/O performance might decrease while an automatic failback is being performed to repair an intermittent error.

  • Page 57: Intermittent Error Monitoring Actions

    2. HDLM Functions 2.9.3 Intermittent Error Monitoring Actions Intermittent error monitoring is performed on each path, and it automatically starts as soon as a path is recovered from an error by using the automatic failback function. This subsection describes the following intermittent error monitoring actions: •...

  • Page 58

    2. HDLM Functions (2) When an Intermittent Error Does Not Occur If an error does not occur on a path a specified number of times within a specified interval, an intermittent error will not occur. In such a case, the error monitoring will finish when the specified error-monitoring interval finishes, upon which the number of errors is reset to 0.

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

    2. HDLM Functions (3) When the Conditions for an Intermittent Error Are Changed During Error Monitoring When the conditions for an intermittent error are changed during error monitoring, the number of errors and the amount of time that has passed since the error monitoring started are both reset to 0.

  • Page 60

    2. HDLM Functions check the IEP item displayed when the command's operation dlnkmgr view -path is executed with the parameter specified. If 0 or greater is displayed in the -iem Intermittent Error Path item, then intermittent error monitoring is being performed. Table 2-7: When Effects of a User Changing the Intermittent Error Information User operation Number of errors...

  • Page 61

    2. HDLM Functions When you turn the intermittent error monitoring function off, information about paths not subject to automatic failback will be reset. If you do not want to reset the information about paths not subject to automatic failback when you turn the intermittent error monitoring function off, change the target paths to Offline(C) The number of errors and the time passed since error monitoring had started are...

  • Page 62: Detecting Errors By Using Path Health Checking

    2. HDLM Functions 2.10 Detecting Errors by Using Path Health Checking HDLM can check the status of paths for which I/O operations are not being performed at regular intervals. This function is called path health checking. Without path health checking, an error cannot be detected unless an I/O operation is performed, because the system only checks the status of a path when an I/O operation is performed.

  • Page 63: Error Management

    2. HDLM Functions 2.11 Error Management HDLM collects information for troubleshooting into log files. HDLM can also filter error information according to the error level when collecting the information. Figure 2-15: Flow of Data When Collecting Error Information shows the flow of data when collecting error information.

  • Page 64

    2. HDLM Functions Figure 2-15: Flow of Data When Collecting Error Information Logs might be collected in layers below HDLM, such as for the SCSI driver. For more details, see the Linux documentation.

  • Page 65: Types Of Collected Logs

    2. HDLM Functions 2.11.1 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. You can use the error information to examine the status of an error and analyze the cause of the error.

  • Page 66: Filtering Of Error Information

    2. HDLM Functions When you want to configure the system so that HDLM messages are output to syslog, specify for the facility in the syslog settings file. The following user shows an example where the system function name is , and messages at the user level or higher are output to the file:...

  • Page 67: Information (dlmgetras)

    2. HDLM Functions • Collects error information from the Information level and higher. • Collects error information from the Information level and higher (including maintenance information). Collection levels for log information in trace files: • Outputs no trace information • Outputs error information only •...

  • Page 68: Collecting Audit Log Data

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

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

    2. HDLM Functions Category Explanation An event indicating that an attempt to access critical data has succeeded or ContentAccess failed, including: • Access to a critical file on a NAS or content access when HTTP is supported • Access to the audit log file An event indicating that a permitted operation performed by the administrator ConfigurationAccess has terminated normally or failed, including:...

  • Page 70

    2. HDLM Functions Table 2-11: Categories and Audit Events that Can Be Output to the Audit Log Category Explanation Audit event Severity Message Startup and Startup of the HDLM KAPL154 StartStop termination of the manager was successful. 01-I software Startup of the HDLM KAPL154 manager failed.

  • Page 71

    2. HDLM Functions Category Explanation Audit event Severity Message Setup of the operating KAPL151 environment was 05-I successful. Setup of the operating KAPL151 environment failed. 06-E An attempt to display KAPL151 program information was 07-I successful. An attempt to display KAPL151 program information failed.

  • Page 72

    2. HDLM Functions Category Explanation Audit event Severity Message Processing of the KAPL150 command 44-I dlmcfgmgr -i was successful. Processing of the KAPL150 command 45-E dlmcfgmgr -i failed. Processing of the KAPL150 command 46-I dlmcfgmgr -v was successful. Processing of the KAPL150 command 47-E...

  • Page 73: Requirements For Outputting Audit Log Data

    2. HDLM Functions Category Explanation Audit event Severity Message Processing of the KAPL150 56-I dlmsetopt -inqr command was successful. Processing of the KAPL150 57-E dlmsetopt -inqr command failed. Processing of the KAPL150 58-I dlmupdatesysinit command was successful. Processing of the KAPL150 59-E dlmupdatesysinit...

  • Page 74: Destination And Filtering Of Audit Log Data

    2. HDLM Functions • You might need to perform operations such as changing the log size and backing up and saving collected log data, because the amount of audit log data might be quite large. • If the severity specified by the HDLM command's operation differs from the severity specified by the configuration file /etc/syslog.conf...

  • Page 75: Audit Log Data Formats

    2. HDLM Functions Filtering by category: The following categories can be specified: • StartStop • Authentication • ConfigurationAccess • All of the above For details on how to specify audit log settings, see 3.18.2 Setting Up the HDLM Functions. 2.12.4 Audit Log Data Formats The following describes the format of audit log data: Format of audit log data output to syslog: •...

  • Page 76

    2. HDLM Functions Explanation Item Common specification Fixed to revision number Serial number Serial number of the audit log message Message ID Message ID in KAPL15nnn-l format Date and time The date and time when the message was output. This item is output in the following format: yyyy ddThh...

  • Page 77

    2. HDLM Functions Explanation Item Reserved area This field is reserved. No data is output here. Message text Data related to the audit event is output. #: The output of this item depends on the audit event. Example of the message section for the audit event An attempt to display HDLM management-target information was successful: CELFSS,1.1,0,KAPL15109-I,2008-04-09T10:18:40.6+09:00,HDLMCo mmand,hostname=moon,ConfigurationAccess,Success,uid=root,,,...

  • Page 78: Integrated Hdlm Management Using Global Link Manager

    2. HDLM Functions 2.13 Integrated HDLM management using Global Link Manager By using Global Link Manager, you can perform integrated path management on systems running multiple instances of HDLM. For large-scale system configurations using many hosts running HDLM, the operational load for managing paths on individual hosts increases with the size of the configuration.

  • Page 79

    2. HDLM Functions Figure 2-16: Example System Configuration Using HDLM and Global Link Manager...

  • Page 80: Cluster Support

    2. HDLM Functions 2.14 Cluster Support HDLM can also be used in cluster configurations. For details about the cluster software supported by HDLM, see (1) Cluster Software Supported by HDLM in 3.1.3 Related Products When Using Red Hat Enterprise Linux AS4/ES4, (1) Cluster Software Supported by HDLM (If an FC-SAN Is Used) in 3.1.4 Related Products When Using Red Hat Enterprise Linux 5, (1) Cluster Software Supported by HDLM (If an FC-SAN Is Used) in 3.1.5 Related Products When Using...

  • Page 81: Creating An Hdlm Environment

    Chapter 3. 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. 3.1 HDLM System Requirements 3.2 Flow for Creating an HDLM Environment 3.3 HDLM Installation Types...

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

    3. Creating an HDLM Environment 3.1 HDLM System Requirements Check the following before installing HDLM: 3.1.1 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, Table 3-3: Red Hat Enterprise Linux 5 Kernels Supported by HDLM, Table 3-4: Red Hat Enterprise Linux 6 Kernels Supported by HDLM, Table 3-5: SUSE LINUX Enterprise Server 9 Kernels Supported by HDLM, Table 3-6: SUSE LINUX Enterprise Server 10 Kernels...

  • Page 83

    3. Creating an HDLM Environment Execute the following command to check which kernel architecture is used: # uname -m x86_64 The following shows the meaning of the execution result of the command: uname : IA32 architecture i686 : IPF architecture ia64 : AMD64/EM64T architecture x86_64...

  • Page 84

    3. Creating an HDLM Environment Table 3-2: Red Hat Enterprise Linux AS4/ES4 Kernels Supported by HDLM Kernel Kernel architecture 2.6.9-11.EL IA32 2.6.9-11.ELsmp 2.6.9-11.ELhugemem 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...

  • Page 85

    3. Creating an HDLM Environment Kernel Kernel architecture 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 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...

  • Page 86

    3. Creating an HDLM Environment Kernel Kernel architecture 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. 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 87

    3. Creating an HDLM Environment Kernel Kernel architecture 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 2.6.18-8.el5 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-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 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.

  • Page 88

    3. Creating an HDLM Environment 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.

  • Page 89

    3. Creating an HDLM Environment RPM package version - glibc- .i686.rpm RPM package version depends on the OS version you are using. Table 3-5: SUSE LINUX Enterprise Server 9 Kernels Supported by HDLM Kernel Kernel architecture 2.6.5-7.308-default IA32 2.6.5-7.308-smp 2.6.5-7.308-bigsmp 2.6.5-7.315-default 2.6.5-7.315-smp 2.6.5-7.315-bigsmp...

  • Page 90

    3. Creating an HDLM Environment HDLM supports an environment where an IPF kernel is installed on a system that uses an Intel CPU. HDLM supports an environment where an EM64T/AMD64 kernel is installed on a system that uses an Intel CPU or AMD Opteron CPU. Table 3-6: SUSE LINUX Enterprise Server 10 Kernels Supported by HDLM Kernel Kernel architecture...

  • Page 91

    3. Creating an HDLM Environment Kernel Kernel architecture 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 supports CFQ, and the default I/O scheduler functionality.

  • Page 92

    3. Creating an HDLM Environment 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. All of the SP4 packages for SUSE LINUX Enterprise Server 10 must be installed.

  • Page 93

    3. Creating an HDLM Environment • 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 installed.

  • Page 94

    3. Creating an HDLM Environment 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 installed on a system that uses an Intel CPU or AMD Opteron CPU.

  • Page 95: Storage Systems Supported By Hdlm

    3. Creating an HDLM Environment 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 Manager) packages listed below are required.

  • Page 96: Related Products When Using Red Hat Enterprise Linux As4/es4

    3. Creating an HDLM Environment Storage systems that are used must have a dual controller configuration. If you use them in a HUB-connected environment, specify a unique loop ID for all the connected hosts and storage systems. For details on the microprogram version required for using HDLM, see HDLM Release Notes.

  • Page 97

    3. Creating an HDLM Environment 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 , which are displayed by executing the following command, Service Pack Version are the same, the versions of HDLM are the same: # /opt/DynamicLinkManager/bin/dlnkmgr view -sys...

  • Page 98

    3. Creating an HDLM Environment Usable kernels Cluster software 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 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) Oracle RAC 10g Release 2 (10.2.0.2.0) Oracle RAC 10g Release 2 (10.2.0.3.0)

  • Page 99

    3. Creating an HDLM Environment Usable kernels Cluster software 2.6.9-42.EL LifeKeeper v6 2.6.9-42.ELsmp LifeKeeper v6 Update1 2.6.9-42.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) Oracle RAC 10g Release 2 (10.2.0.2.0) Oracle RAC 10g Release 2 (10.2.0.3.0)

  • Page 100

    3. Creating an HDLM Environment Usable kernels Cluster software 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 2.6.9-67.ELsmp LifeKeeper v7 2.6.9-67.ELhugemem 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)

  • Page 101

    3. Creating an HDLM Environment For details, see 3.14 Settings for Oracle RAC. Only configurations that include the Automatic Storage Management (ASM) function (the ASMLib kernel driver (ASMLib) is used) and Cluster Ready Service (CRS) are supported. For details, see 3.14 Settings for Oracle RAC. The following configurations are supported: •...

  • Page 102

    3. Creating an HDLM Environment 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 Oracle Clusterware For details, see 3.14 Settings for Oracle RAC.

  • Page 103

    3. Creating an HDLM Environment Table 3-11: Cluster Software When Using Red Hat Enterprise Linux ES4 (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...

  • Page 104

    3. Creating an HDLM Environment Usable kernels Cluster software 2.6.9-42.EL LifeKeeper v6 2.6.9-42.ELsmp LifeKeeper v6 Update1 2.6.9-42.ELhugemem LifeKeeper v6 Update2 LifeKeeper v6 Update3 2.6.9-42.0.3.EL LifeKeeper v6 Update4 2.6.9-42.0.3.ELsmp LifeKeeper v7 2.6.9-42.0.3.ELhugemem 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)

  • Page 105

    3. Creating an HDLM Environment Usable kernels Cluster software 2.6.9-78.EL LifeKeeper v6 Update4 2.6.9-78.ELsmp LifeKeeper v7 2.6.9-78.ELhugemem LifeKeeper v7 Update1 LifeKeeper v7 Update2 2.6.9-89.EL LifeKeeper v7 Update3 2.6.9-89.ELsmp Oracle RAC 10g Release 2 (10.1.0.5.0) 2.6.9-89.ELhugemem 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)

  • Page 106

    3. Creating an HDLM Environment The following configurations are supported: • 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) function (the ASMLib kernel driver (ASMLib) is used) and Cluster Ready Service (CRS) For details, see 3.14 Settings for Oracle RAC.

  • Page 107

    3. Creating an HDLM Environment function (raw devices used) and Cluster Ready Service (CRS) For details, see 3.14 Settings for Oracle RAC. Only configurations that include the Automatic Storage Management (ASM) function (using raw devices) and Oracle Clusterware are supported. For details, see 3.14 Settings for Oracle RAC.

  • Page 108

    3. Creating an HDLM Environment For details, see 3.14 Settings for Oracle RAC. 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) •...

  • Page 109

    3. Creating an HDLM Environment Usable kernels Cluster software 2.6.9-34.EL LifeKeeper v6 2.6.9-34.ELsmp LifeKeeper v6 Update1 2.6.9-34.ELlargesmp LifeKeeper v6 Update2 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)

  • Page 110

    3. Creating an HDLM Environment Usable kernels Cluster software 2.6.9-42.EL LifeKeeper v6 2.6.9-42.ELsmp LifeKeeper v6 Update1 2.6.9-42.ELlargesmp LifeKeeper v6 Update2 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)

  • Page 111

    3. Creating an HDLM Environment Usable kernels Cluster software 2.6.9-55.EL LifeKeeper v6 2.6.9-55.ELsmp LifeKeeper v6 Update1 2.6.9-55.ELlargesmp LifeKeeper v6 Update2 LifeKeeper v6 Update3 2.6.9-67.EL LifeKeeper v6 Update4 2.6.9-67.ELsmp LifeKeeper v7 2.6.9-67.ELlargesmp 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)

  • Page 112

    3. Creating an HDLM Environment For details, see 3.14 Settings for Oracle RAC. 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) •...

  • Page 113

    3. Creating an HDLM Environment Only configurations that include the Automatic Storage Management (ASM) function (using raw devices) and Oracle Clusterware are supported. For details, see 3.14 Settings for Oracle RAC. (2) Volume Managers Supported by HDLM Table 3-14: Volume Managers When Using Red Hat Enterprise Linux AS4/ES4 lists and describes the related programs when using a volume manager.

  • Page 114

    3. Creating an HDLM Environment Kernel architecture Kernel Volume Manager 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 115

    3. Creating an HDLM Environment Kernel architecture Kernel Volume Manager 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 (3) File Systems Supported by HDLM When using a file system, the related programs are as follows: •...

  • Page 116

    3. Creating an HDLM Environment Table 3-15: Operating Environments for BladeSymphony When Using Red Hat Enterprise Linux AS4/ES4 Kernel architecture Kernel Supported storage systems IA32 2.6.9-11.ELsmp hitachi Hitachi AMS2000/AMS/WMS/SMS series Hitachi USP 2.6.9-34.ELsmp #1#2 Lightning 9900V series Thunder 9500V series 2.6.9-55.ELsmp Universal Storage Platform V/VM 2.6.9-78.ELsmp...

  • Page 117

    3. Creating an HDLM Environment Table 3-16: Operating Environments for Boot Disks When Using Red Hat Enterprise Linux AS4/ES4(IA32) Kernel Supported storage systems 2.6.9-11.EL QLogic Hitachi AMS2000/AMS/WMS/SMS series 2.6.9-11.ELsmp Hitachi USP 2.6.9-11.ELhugemem Lightning 9900V series Thunder 9500V series 2.6.9-34.EL Universal Storage Platform V/VM 2.6.9-34.ELsmp Virtual Storage Platform 2.6.9-34.ELhugemem...

  • Page 118

    3. Creating an HDLM Environment 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 Hitachi USP Lightning 9900V series 2.6.9-67.EL Thunder 9500V series 2.6.9-67.ELlargesmp Universal Storage Platform V/VM Virtual Storage Platform 2.6.9-78.EL...

  • Page 119

    3. Creating an HDLM Environment Kernel Supported storage systems 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 lists the operating environments when an HDLM device is used as a boot disk in a BladeSymphony environment.

  • Page 120: Related Products When Using Red Hat Enterprise Linux 5

    3. Creating an HDLM Environment Notes on using HDLM in a BladeSymphony environment When HDLM is used in a BladeSymphony environment, the following functions cannot be used: • HotPlug • SystemManager linkage Note that HDLM cannot use the functions provided by ServerConductor/ DeploymentManager other than the following: •...

  • Page 121

    3. Creating an HDLM Environment 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 LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 Oracle RAC 10g Release 2 (10.2.0.4.0)

  • Page 122

    3. Creating an HDLM Environment Usable kernels Cluster software 2.6.18-128.el5 LifeKeeper v6 Update4 2.6.18-128.el5PAE LifeKeeper v7 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...

  • Page 123

    3. Creating an HDLM Environment Clusterware • Configurations that include the Oracle Cluster File System 2 and Oracle Clusterware For details, see 3.14 Settings for Oracle RAC. The following configurations are supported: • Configurations that include raw devices and Oracle Clusterware •...

  • Page 124

    3. Creating an HDLM Environment Table 3-22: Cluster Software Used with Red Hat Enterprise Linux 5 (EM64T/ AMD64) Usable kernels Cluster software 2.6.18-8.el5 LifeKeeper v6 Update1 LifeKeeper v6 Update2 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)

  • Page 125

    3. Creating an HDLM Environment Usable kernels Cluster software 2.6.18-92.el5 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 2 (11.2.0.1.0)

  • Page 126

    3. Creating an HDLM Environment Only configurations that include the Automatic Storage Management (ASM) function (raw devices used) and Cluster Ready Service (CRS) are supported. For details, see 3.14 Settings for Oracle RAC. The following configurations are supported: • Configurations that include raw devices and Cluster Ready Service (CRS) •...

  • Page 127

    3. Creating an HDLM Environment • 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 •...

  • Page 128

    3. Creating an HDLM Environment Kernel architecture Kernel Volume manager 2.6.18-92.el5 LVM2.02.32-4.el5 2.6.18-92.el5PAE 2.6.18-128.el5 LVM2.02.40-6.el5 2.6.18-128.el5PAE 2.6.18-164.el5 LVM2.02.46-8.el5 2.6.18-164.el5PAE 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 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 EM64T/AMD64 2.6.18-8.el5 LVM2.02.16-3.el5 2.6.18-53.el5...

  • Page 129

    3. Creating an HDLM Environment Table 3-24: Supported File Systems When Using Red Hat Enterprise Linux 5 Kernel architecture Kernel File system IA32 2.6.18-8.el5 ext2 (supplied with the OS) 2.6.18-8.el5PAE ext3 (supplied with the OS) 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)

  • Page 130

    3. Creating an HDLM Environment An HDLM device on a GFS2 file system cannot be used as a boot disk. (4) 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.

  • Page 131

    3. Creating an HDLM Environment Table 3-26: Operating Environments for Boot Disks When Using Red Hat Enterprise Linux 5 Kernel architecture Kernel Supported storage systems IA32 2.6.18-8.el5 Emulex Hitachi AMS2000/AMS/WMS/ SMS series 2.6.18-8.el5PAE QLogic Hitachi USP 2.6.18-53.el5 Brocade Thunder 9500V series 2.6.18-53.el5PAE Emulex Universal Storage Platform V/VM...

  • Page 132

    3. Creating an HDLM Environment Kernel architecture Kernel Supported storage systems 2.6.18-194.el5 2.6.18-238.el5 LUKS is not available in an environment where an HDLM device is used as a boot disk. Table 3-27: Operating Environments for BladeSymphony and Boot Disks When Using Red Hat Enterprise Linux 5 lists the operating environments when an HDLM device is used as a boot disk in a BladeSymphony environment.

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

    3. Creating an HDLM Environment • HotPlug • SystemManager linkage Note that HDLM cannot use the functions provided by ServerConductor/ DeploymentManager other than the following: • Backup and restoration • BIOS/firmware updating For details on the functions provided by ServerConductor/DeploymentManager, see the manual ServerConductor/DeploymentManager User's Guide.

  • Page 134: Related Products When Using Suse Linux Enterprise Server 9

    3. Creating an HDLM Environment Table 3-29: Supported File Systems When Using Red Hat Enterprise Linux 6 Kernel architecture Kernel File system IA32 2.6.32-71.el6.i686 ext2 (supplied with the OS) ext3 (supplied with the OS) EM64T/AMD64 2.6.32-71.el6.x86_64 ext4 (supplied with the OS) GFS2 (supplied with the OS) An HDLM device on a GFS2 file system cannot be used as a boot disk.

  • Page 135: Related Products When Using Suse Linux Enterprise Server 10

    3. Creating an HDLM Environment # /opt/DynamicLinkManager/bin/dlnkmgr view -sys Always use Heartbeat (1.2.5-0.3) in order to create a cluster configuration. Note that environments that combine Heartbeat and LVM are not supported. (2) Volume Managers Supported by HDLM Use LVM2.01.14-3.23 as a volume manager. Notes on using a volume manager Note the following when using a volume manager: •...

  • Page 136

    3. Creating an HDLM Environment 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 , which are displayed by executing the following command, Service Pack Version are the same, the versions of HDLM are the same: # /opt/DynamicLinkManager/bin/dlnkmgr view -sys...

  • Page 137

    3. Creating an HDLM Environment Kernel architecture Usable kernels Cluster software EM64T/AMD64 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.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.60-0.21-default Heartbeat (2.1.3-0.9) 2.6.16.60-0.21-smp Novell Open Enterprise Server 2 SP1 2.6.16.60-0.21-xen Heartbeat (2.1.3-0.9) 2.6.16.60-0.54.5-default...

  • Page 138

    3. Creating an HDLM Environment Kernel architecture Kernel Volume manager 2.6.16.46-0.14-default LVM2.02.17-7.9 2.6.16.46-0.14-smp 2.6.16.46-0.14-bigsmp 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-bigsmp 2.6.16.60-0.21-xenpae 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-bigsmp 2.6.16.60-0.54.5-xenpae 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...

  • Page 139

    3. Creating an HDLM Environment • 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 vgscan CD-ROM IOCTL command might be sent to each device in the OS.

  • Page 140

    3. Creating an HDLM Environment Table 3-33: Operating Environments for BladeSymphony When Using SUSE LINUX Enterprise Server 10 Kernel architecture Kernel Supported storage systems EM64T 2.6.16.46-0.14-smp hitachi Hitachi AMS2000/AMS/WMS/SMS series Hitachi USP #1#2 Lightning 9900V series Thunder 9500V series Universal Storage Platform V/VM Virtual Storage Platform The XP series is not supported.

  • Page 141

    3. Creating an HDLM Environment Kernel architecture Kernel Supported storage systems 2.6.16.60-0.21-default Brocade 2.6.16.60-0.54.5-default EM64T/AMD64 2.6.16.46-0.14-default QLogic 2.6.16.46-0.14-smp 2.6.16.60-0.21-default Brocade 2.6.16.60-0.21-smp QLogic 2.6.16.60-0.21-xen QLogic 2.6.16.60-0.54.5-default Brocade 2.6.16.60-0.54.5-smp QLogic 2.6.16.60-0.54.5-xen 2.6.16.60-0.85.1-default QLogic 2.6.16.60-0.85.1-smp 2.6.16.60-0.85.1-xen Table 3-35: Operating Environments for BladeSymphony and Boot Disks When Using SUSE LINUX Enterprise Server 10 lists the operating environments when an HDLM device is used as a boot disk in a BladeSymphony environment.

  • Page 142: Related Products When Using Suse Linux Enterprise Server 11

    3. Creating an HDLM Environment Note that HDLM cannot use the functions provided by ServerConductor/ DeploymentManager other than the following: • Backup and restoration • BIOS/firmware updating For details on the functions provided by ServerConductor/DeploymentManager, see the manual ServerConductor/DeploymentManager User's Guide. 3.1.8 Related Products When Using SUSE LINUX Enterprise Server The following describes related products when SUSE LINUX Enterprise Server 11 is used.

  • Page 143

    3. Creating an HDLM Environment IOCTL when installing HDLM because HDLM devices are not SCSI devices. HDLM rejects the IOCTL request and assumes that the IOCTL processing has failed. The error message (KAPL05023-E) is output to the syslog, but HDLM operations are not affected.

  • Page 144: Related Products When Using Oracle Enterprise Linux 4

    3. Creating an HDLM Environment Table 3-37: Operating Environments for Boot Disks When Using SUSE LINUX Enterprise Server 11 Kernel architecture Kernel Supported storage systems IA32 2.6.27.21-0.1-default Brocade Hitachi AMS2000/AMS/WMS/ SMS series 2.6.27.21-0.1-pae QLogic Hitachi USP 2.6.27.21-0.1-xen QLogic Lightning 9900V series Thunder 9500V series 2.6.32.12-0.7-default Brocade...

  • Page 145: Related Products When Using Oracle Enterprise Linux 5

    3. Creating an HDLM Environment (2) 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) (3) Boot Disk Environments Supported by HDLM HDLM supports boot disks in any of the environments listed in Table 3-39: Operating Environments for Boot Disks When Using Oracle Enterprise Linux 4.

  • Page 146

    3. Creating an HDLM Environment # /opt/DynamicLinkManager/bin/dlnkmgr view -sys Table 3-40: Cluster Software When Using Oracle Enterprise Linux 5 lists the related programs used when creating a cluster. Table 3-40: Cluster Software When Using Oracle Enterprise Linux 5 Kernel architecture Usable kernels Cluster software IA32...

  • Page 147

    3. Creating an HDLM Environment Kernel architecture Kernel Volume manager EM64T/AMD64 2.6.18-53.el5 LVM2.02.26-3.el5 2.6.18-164.el5 LVM2.02.46-8.el5 2.6.18-194.el5 LVM2.02.56-8.el5 (3) File Systems Supported by HDLM Table 3-42: Supported File Systems When Using Oracle Enterprise Linux 5 lists and describes the related programs when using the file system. Table 3-42: Supported File Systems When Using Oracle Enterprise Linux 5 Kernel architecture Kernel...

  • Page 148: Memory And Disk Capacity Requirements

    3. Creating an HDLM Environment Table 3-43: Operating Environments for Boot Disks When Using Oracle Enterprise Linux 5 Kernel architecture Kernel Supported storage systems IA32 2.6.18-53.el5 QLogic Hitachi AMS2000/AMS/WMS/ SMS series 2.6.18-53.el5PAE Hitachi USP 2.6.18-164.el5 Emulex Lightning 9900V series 2.6.18-164.el5PAE QLogic Thunder 9500V series Universal Storage Platform V/...

  • Page 149

    3. Creating an HDLM Environment Directory Disk capacity requirements p MB + q MB + 4 MB + u MB + 20 MB + v MB + 45 MB /var (100 MB 168 MB /opt y MB + z MB + 5.5 MB /etc (10 MB...

  • Page 150

    3. Creating an HDLM Environment Agent Component. The size of each log file ( ) is 9900 KB (approximately dlmwebagent[1- ].log 10 MB). The size of the log files is calculated as approximately 20 MB because two log files are created by default. You can create a maximum of 16 log files depending on the setting in the file.

  • Page 151: Number Of Paths Supported In Hdlm, Virtual Environments Supported By Hdlm

    3. Creating an HDLM Environment 3.1.12 Number of Paths Supported in HDLM Table 3-46: Number of LUs and Paths Supported in HDLM lists the number of LUs, number of paths per LU, and total number of paths supported in HDLM. Table 3-46: Number of LUs and Paths Supported in HDLM Target Supported...

  • Page 152

    3. Creating an HDLM Environment Table 3-47: Xen Hypervisor Operating Environments Supported by HDLM shows the Xen hypervisor operating environments supported by HDLM. Table 3-47: Xen Hypervisor Operating Environments Supported by HDLM Kernel architecture Kernel Xen hypervisor version SUSE LINUX IA32 2.6.16.60-0.21-xenpae xen-3.2.0_16718_14-0.4...

  • Page 153: Flow For Creating An Hdlm Environment

    3. Creating an HDLM Environment 3.2 Flow for Creating an HDLM Environment Set up the environment to use HDLM as shown in the following diagram. If you are going to use volume management software, the procedure for building a file system shown in the figure is not required.

  • Page 154

    3. Creating an HDLM Environment Figure 3-1: Flow of HDLM Environment Setup...

  • Page 155: Hdlm Installation Types

    3. Creating an HDLM Environment 3.3 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 156: Knowledge Required Before You Install Hdlm

    3. Creating an HDLM Environment 3.4 Knowledge Required Before You Install HDLM You can install HDLM on the following disks or devices: • An internal disk on a host machine • LUs of storage systems that are used as a boot disk For details about the storage systems on which HDLM can be installed, see (4) Boot Disk Environments and BladeSymphony Environments Supported by HDLM in 3.1.3 Related Products When Using Red Hat Enterprise Linux...

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

    3. Creating an HDLM Environment 3.5 Notes on Creating an HDLM Environment This section provides notes on creating an HDLM environment. For notes on operating HDLM, see 4.1 Notes on Using HDLM. 3.5.1 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 158: Notes On Linux

    3. Creating an HDLM Environment However, you can avoid the above situations by setting a permanent target ID for each LU with the HBA driver persistent binding functionality. For details on whether the persistent binding functionality is supported for your HBA driver and the setting method, see the manual provided with the HDLM driver.

  • Page 159: Notes On Installing Hdlm

    3. Creating an HDLM Environment # grep DLM /etc/rc.d/rc.sysinit # grep DLM /etc/init.d/halt If nothing is output after command execution, HDLM information is missing. For details about the utility, see 7.8 dlmupdatesysinit dlmupdatesysinit Utility for Updating System Scripts. In an environment that uses SUSE LINUX Enterprise Server, after upgrading the , or package after HDLM installation and aaa_base...

  • Page 160

    3. Creating an HDLM Environment 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 utility. The dlmcfgmgr following procedure shows how to stop the HAL daemon. The HAL daemon detects hardware configurations changes, for example, when a USB device or CD-ROM is inserted.

  • Page 161: Notes On An Upgrade Installation Or Re-installation Of Hdlm, Notes On A Device Manager Agent

    3. Creating an HDLM Environment # /sbin/dlmcfgmgr -i Start the HAL daemon. Execute the command to start the HAL daemon. /sbin/service # /sbin/service haldaemon start Make sure that the HAL daemon is running. Execute the command to make sure that the HAL daemon /sbin/service is running.

  • Page 162

    3. Creating an HDLM Environment...

  • Page 163: Installing Hdlm, Preparations For A New Installation Of Hdlm

    3. Creating an HDLM Environment 3.6 Installing HDLM The following section describes how to install HDLM for a new installation, for a re-installation, and for an upgrade installation. Depending on the procedure, the host might have to be restarted after HDLM is installed. HDLM can also be installed by performing an unattended installation, which enables a user to install HDLM without entering information.

  • Page 164

    3. Creating an HDLM Environment First, check the current settings. Execute the following command: # mount The current settings will be output as shown in Figure 3-2: Execution Results of the mount Command. Figure 3-2: Execution Results of the mount Command The shaded portion shows the SCSI device to be managed by HDLM.

  • Page 165

    3. Creating an HDLM Environment (2) Checking the Volume Group If you have already created a physical volume, volume group, or logical volume by using LVM, you can use the procedure described in 3.10 Settings for LVM2 only when all of the conditions below are satisfied. Migration is not affected even when a logical volume or file system has been created.

  • Page 166

    3. Creating an HDLM Environment Figure 3-4: Result of Executing vgdisplay -v (When There Is One Physical Volume) Check the shaded portion and confirm that consists of vg02 /dev/sde...

  • Page 167

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

  • Page 168: Performing A New Installation Of Hdlm

    3. Creating an HDLM Environment 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. We also recommend that you specify as the severity level for the extended facility.

  • Page 169

    3. Creating an HDLM Environment Log on to Linux as the root user. Prepare the license key. Use either of the following methods to store the license key file in the specified directories: • Store the license key file ( ) in the directory, under the *.plk...

  • Page 170

    3. Creating an HDLM Environment Distribution Mount point SUSE LINUX Enterprise Server 9 • For a CD-ROM /media/cdrom • For a CD-R or CD-RW /media/cdrecorder • For a DVD-ROM /media/dvd • For a DVD-RW /media/dvdrecorder • For a DVD-RAM /media/dvdram SUSE LINUX Enterprise Server 10 /media/cdrom SUSE LINUX Enterprise Server 11...

  • Page 171

    3. Creating an HDLM Environment • When executing installux.sh # /media/cdrom/installux.sh -v • When executing the utility installhdlm # /media/cdrom/HDLM_Linux/installhdlm -v A command execution example is described below. x.x.x-xx is the version of HDLM. x.x.x-xx KAPL09177-I HDLM version: Perform the installation. Execute or the utility stored on the HDLM...

  • Page 172

    3. Creating an HDLM Environment # rpm -qi HDLM Name : HDLM x.x.x.x.xxx Version Release is x.x.x.x.xxx, the installed version of HDLM is correct. HDLM Version x.x.x.x.xxx indicates the HDLM version that was installed. If IP-SAN is used for the connection between the host and the storage system, change , written in the iscsi_boot=n...

  • Page 173

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

  • Page 174

    3. Creating an HDLM Environment For details on operating environments for the virtual environments supported by HDLM, see 3.1.13 Virtual Environments Supported by HDLM. For details on how to set up a virtual environment, see 3.11 Settings for Xen or 3.12 Settings for KVM.

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

    3. Creating an HDLM Environment 21. Check that the correct version of HDLM is installed. x.x.x-xx is displayed, the installed HDLM version is correct. HDLM version x.x.x-xx is the version of the installed HDLM. 22. Check that the programs are running properly. , and are all , all...

  • Page 176: Performing A Re-installation Of Hdlm

    3. Creating an HDLM Environment Execute the following command to make sure that the md devices have been deactivated. In the following example, RAID1 (mirroring) is used: # cat /proc/mdstat Personalities : [raid1] unused devices: <none> Make sure that is not displayed. : active (3) Deactivating the Volume Group If you are using a logical volume on an HDLM device, you must deactivate the volume...

  • Page 177

    3. Creating an HDLM Environment Prepare the license key. Store the license key file ( ) in the directory, under the name *.plk /var/tmp hdlm_license /var/tmp/hdlm_license Notes on the license key for a re-installation: When a permanent license key has been entered, you do not need to create the license key file.

  • Page 178

    3. Creating an HDLM Environment Table 3-50: Mount Point for Each Distribution Distribution Mount point Red Hat Enterprise Linux AS4/ES4 • For a CD-R, DVD-R, CD-ROM, or DVD-ROM /media/cdrom • For a CD-RW, DVD-RW, or DVD-RAM /media/cdrecorder Red Hat Enterprise Linux 5 /media/cdrom Red Hat Enterprise Linux 6 SUSE LINUX Enterprise Server 9...

  • Page 179

    3. Creating an HDLM Environment Check the version of HDLM. Execute or the HDLM installation utility ( ) stored installux.sh installhdlm 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 •...

  • Page 180

    3. Creating an HDLM Environment The KAPL09093-I message is displayed to confirm that you want to perform an upgrade installation. Check the HDLM version, and if it is correct, enter Make sure that HDLM is installed. Execute the following command to display detailed information about the installed package.

  • Page 181

    3. Creating an HDLM Environment 12. Restart the host. Execute the following command to restart the host: # shutdown -r now A path will be established in the HDLM device and the HDLM manager will start. 13. If you have edited the file as described in (1) Operations Required /etc/fstab for Devices to Be Managed by HDLM in 3.6.1 Preparations for a New...

  • Page 182

    3. Creating an HDLM Environment Personalities : [raid1] md0 : active raid1 sddlmaa1[0] sddlmab1[1] 5238528 blocks [2/2] [UU] unused devices: <none> Make sure that is displayed and that the HDLM devices are md0 : active displayed. 17. Specify the settings required for using the volume management software. If you performed the operations described in (3) Deactivating the Volume Group in 3.6.3 Preparations for an Upgrade Installation or Re-installation of HDLM, perform the following steps to activate the volume group:...

  • Page 183: Performing An Upgrade Installation Of Hdlm

    3. Creating an HDLM Environment HDLM, see 3.1.13 Virtual Environments Supported by HDLM. For details on how to set up a virtual environment, see 3.11 Settings for Xen or 3.12 Settings for KVM. 21. Specify the settings required for operations in a cluster configuration. For a cluster configuration, change the logical device file names of SCSI devices specified in the cluster to logical device file names of HDLM devices.

  • Page 184

    3. Creating an HDLM Environment 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. Table 3-51: Mount Point for Each Distribution Distribution Mount point...

  • Page 185

    3. Creating an HDLM Environment This refers to the volume name for the CD-ROM or other media, formatted for ISO-9660 file systems. Use the command to check volname media-volume-id. The following shows an execution example for when media-volume-id is VOL01234 # volname /dev/cdrom VOL01234...

  • Page 186

    3. Creating an HDLM Environment # /media/cdrom/installux.sh • When executing the utility installhdlm # /media/cdrom/HDLM_Linux/installhdlm The KAPL09093-I message is displayed to confirm that you want to perform an upgrade installation. Check the HDLM version, and if it is correct, enter Make sure that HDLM is installed.

  • Page 187

    3. Creating an HDLM Environment settings file for the root user. This makes executing the HDLM commands and HDLM utilities easier. When the BourneAgain shell or Korn shell is used: PATH=$PATH:/opt/DynamicLinkManager/bin ; export PATH When the C shell is used: set path= ( $path /opt/DynamicLinkManager/bin ) If the environment variable is not set, specify an absolute path to execute...

  • Page 188

    3. Creating an HDLM Environment For details on setting up LUKS, see 3.8 Settings for LUKS. 16. If md devices are used, execute the following command to activate them: # mdadm -A -scan mdadm: /dev/md0 has been started with 2 drives. 17.

  • Page 189: Unattended Installation Of Hdlm

    3. Creating an HDLM Environment 20. Mount the logical volume that was moved. In the following example, the logical volume is and the /dev/vg01/lvol1 command mounts the volume on /mnt/lvol1 # mount /dev/vg01/lvol1 /mnt/lvol1 21. Specify the settings required for using virtual environments. If you are using Xen, set up Xen to use HDLM devices in domainU.

  • Page 190

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

  • Page 191

    3. Creating an HDLM Environment Note 2 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.

  • Page 192

    3. Creating an HDLM Environment Edit the installation information settings file based on your desired settings. Specify any settings that are not specified in this file after installing HDLM, as necessary. To use the sample file, copy it from the DVD-ROM to a directory on the hard disk. Note that the sample file name can be changed to any name.

  • Page 193

    3. Creating an HDLM Environment Name : HDLM x.x.x.x.xxx Version Release is x.x.x.x.xxx, the installed version of HDLM is correct. HDLM Version x.x.x.x.xxx indicates the HDLM version that was installed. If you want to set the HDLM driver options, run the utility.

  • Page 194

    3. Creating an HDLM Environment Add the shaded line shown in the above figure. 11. 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 195

    3. Creating an HDLM Environment 16. Specify the settings required for using virtual environments. 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 3.1.13 Virtual Environments Supported by HDLM.

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

    3. Creating an HDLM Environment 3.7 Installing HDLM for Managing Boot Disks This section explains the procedure for installing HDLM in an environment in which the boot disk is on a SCSI device in the storage system, and for creating an HDLM device.

  • Page 197

    3. Creating an HDLM Environment Check the installation directory of the OS specified in the setting. LABEL # cat /etc/fstab LABEL=/ ext3 defaults LABEL=/boot /boot ext3 defaults Confirm that LABEL indicates the root directory and the directory. /boot Check the correspondence between the setting and the sd device.

  • Page 198

    3. Creating an HDLM Environment In an environment where HDLM has been installed, you can use the dlmcfgmgr utility to check the correspondence between a SCSI device and a name. udev Figure 3-7: Example of Executing the dlmcfgmgr Utility with the -v and -udev Parameters Specified shows an example of executing the utility with dlmcfgmgr...

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

    3. Creating an HDLM Environment in a single-path boot disk environment that uses a SCSI device. 3.7.2 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.

  • Page 200

    3. Creating an HDLM Environment After completing the above procedure, you can perform an upgrade installation of HDLM in a boot disk environment that uses a SCSI device. (3) 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...

  • Page 201: Settings For Using An Hdlm Device As A Boot Disk

    3. Creating an HDLM Environment Change the definition such that the HDLM device can be used as a boot disk. Restore the configuration file to its state before the upgrade installation was performed. See steps 21 to 37 in 3.7.6 Upgrade Installation in an Environment Where a Logical Volume (LVM2) on an HDLM Device Is Used as a Boot Disk.

  • Page 202

    3. Creating an HDLM Environment image = vmlinuz-2.6.16.60-0.54.5-default label = 51 append = "splash=silent multipath=off" description = Linux initrd = initrd-2.6.16.60-0.54.5-default root = /dev/disk/by-id/ scsi-35001862001472c70-part12 is set in the underlined section. multipath=off • 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.

  • Page 203

    3. Creating an HDLM Environment root (hd0,0) kernel /vmlinuz-2.6.16.60-0.54.5-smp root=/dev/VG/ root vga=0x31a \ resume=/dev/VG/swap splash=silent showopts multipath=off initrd /initrd-2.6.16.60-0.54.5-smp is set in the underlined section. multipath=off Check the definition in the file. /etc/fstab Check whether is used in the file. If the file contains LABEL /etc/fstab xxxxx,...

  • Page 204

    3. Creating an HDLM Environment title Red Hat Enterprise Linux (2.6.18-194.el5) root (hd0,0) kernel /vmlinuz-2.6.18-194.el5 ro root=LABEL=/ initrd /initrd-2.6.18-194.el5 is set in the underlined section. LABEL • When LILO or ELILO is used as the boot loader: image=/boot/vmlinuz-2.6.18-194.el5 label=linux initrd=/boot/initrd-2.6.18-194.el5 read-only append="root=LABEL=/"...

  • Page 205

    3. Creating an HDLM Environment 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 or the device name ( name) was not used in step 3 and step 4, LABEL udev proceed to step 17 and install a new instance of HDLM. If the device name ( name) has been specified, replace with the...

  • Page 206

    3. Creating an HDLM Environment # udevadm info --query name -n /dev/disk/by-uuid/ 55574d05-07dc-4c94-a585-5599c284d79b sda2 value output is the SCSI device name corresponding to sda2 55574d05-07dc-4c94-a585-5599c284d79b • For SUSE LINUX Enterprise Server 10 or SUSE LINUX Enterprise Server Execute the command. Specify the device name ( name) in udevinfo udev...

  • Page 207

    3. Creating an HDLM Environment contained in the boot loader configuration file. The following shows an example configuration. Note that option in the example represents an option that can be specified to suit the user environment. • 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.

  • Page 208

    3. Creating an HDLM Environment option option append=" root=LABEL=/ " 12. Change the name of the configuration contained in the boot loader configuration file. Change the name of the configuration that you copied in step 11. You can assign any name that indicates that the configuration is used for specifying the SCSI device.

  • Page 209

    3. Creating an HDLM Environment Change the number so that a boot can be performed using the default configuration copied in step 11. default=2 • When LILO or ELILO is used as the boot loader: Specify label default default linux-sd 15.

  • Page 210

    3. Creating an HDLM Environment Root directory ( /boot/efi /tmp /usr /var swap • When is used as the boot loader: GRUB Root directory ( /boot /tmp /usr /var swap • When is used as the boot loader: LILO Root directory ( /tmp /usr /var...

  • Page 211

    3. Creating an HDLM Environment Change the underlined text as follows: Before: label=linux-sd After: label=linux-HDLM 25. Delete the specification contained in the boot loader configuration file. root Delete the specification in the configuration that you copied in step 23. If root you are using a Xen kernel, delete the root device specification in .

  • Page 212: Upgrade Installation In An Environment Where An Hdlm Device Is Used As A Boot Disk

    3. Creating an HDLM Environment 29. If LILO is used as the boot loader, execute the command to have /sbin/lilo the new settings take effect. 30. Shut down the host. Execute the following command to shut down the host: # shutdown -h now 31.

  • Page 213

    3. Creating an HDLM Environment The name of the boot loader configuration file used in these procedures differs depending on the boot loader and OS. The names of the boot loader configuration files are listed in Table 3-54: Names of Boot Loader Configuration Files. Table 3-54: Names of Boot Loader Configuration Files Boot loader Configuration file name...

  • Page 214

    3. Creating an HDLM Environment parameter specified to check the correspondence between the HDLM device and the SCSI device. # dlmcfgmgr -v HDevName Management Device Host Channel Target Lun /dev/sddlmaa configured /dev/sda KAPL10302-I /sbin/dlmcfgmgr completed normally. column indicates the HDLM device, and the column HDevName Device...

  • Page 215

    3. Creating an HDLM Environment 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 3.1.1 Hosts and OSs Supported by HDLM.

  • Page 216

    3. Creating an HDLM Environment After: title sd-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=HDLM_194.EL After: label=sd-HDLM_194.EL Specify the SCSI device you checked in step 3 for in the boot loader root configuration file.

  • Page 217

    3. Creating an HDLM Environment • When GRUB is the boot loader Change the number so that a boot can be performed using the default configuration copied in step 5. default=2 • When LILO or ELILO is used as the boot loader: Specify label default...

  • Page 218

    3. Creating an HDLM Environment 16. Perform an upgrade installation of HDLM. To perform an upgrade installation of HDLM, see 3.6.5 Performing an Upgrade Installation of HDLM, 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. Note that the procedure differs depending on whether the host is restarted after installation.

  • Page 219

    3. Creating an HDLM Environment 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=sd-HDLM_194.EL After: label=HDLM-HDLM_194.EL 22. Specify the initial RAM disk image file created in step 18 for contained initrd in the boot loader configuration file.

  • Page 220

    3. Creating an HDLM Environment • When is used as the boot loader: GRUB Root directory ( /boot /tmp /usr /var swap • When is used as the boot loader: LILO Root directory ( /tmp /usr /var swap 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 SCSI device and the HDLM device as checked in step 17.

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

    3. Creating an HDLM Environment /dev/sddlmaa6 on /usr type ext2 (rw) none on /dev/shm type tmpfs (rw) Check the underlined section. 30. 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 222

    3. Creating an HDLM Environment append = "splash=silent multipath=off" description = Linux initrd = initrd-2.6.16.60-0.54.5-default root = /dev/disk/by-id/ scsi-35001862001472c70-part12 is set in the underlined section. multipath=off • 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.

  • Page 223

    3. Creating an HDLM Environment multipath=off initrd /initrd-2.6.16.60-0.54.5-smp is set in the underlined section. multipath=off Check whether the definition in the file contains /etc/fstab LABEL Check the contents of the file. /etc/fstab Figure 3-8: Example Content of /etc/fstab file When using LVM2 shows example content of file.

  • Page 224

    3. Creating an HDLM Environment Figure 3-9: Example of Executing the mount Command The shaded portion indicates the SCSI device for which is set. LABEL This example assumes that IA32 uses as the boot loader. When you use IPF GRUB that uses as the boot loader, the mount point is displayed as ELILO...

  • Page 225

    3. Creating an HDLM Environment # udevadm info --query name -n /dev/disk/by-uuid/ 55574d05-07dc-4c94-a585-5599c284d79b sda1 value output is the SCSI device name corresponding to sda1 55574d05-07dc-4c94-a585-5599c284d79b • For SUSE LINUX Enterprise Server 10 or SUSE LINUX Enterprise Server Execute the command. Specify the device name ( name) in udevinfo udev...

  • Page 226

    3. Creating an HDLM Environment that uses as the boot loader, the mount point is displayed as ELILO /boot/efi instead of (in the line where is coded), and the file system type is /boot /boot displayed as instead of vfat ext3 If necessary, back up the file.

  • Page 227

    3. Creating an HDLM Environment Figure 3-11: Example of Editing /etc/lvm/lvm.conf file Comment out the existing lines, and add the shaded lines in filter types the figure. Set 0 in md_component_detection Record the original value, because it is necessary md_component_detection for uninstallation or upgrade installation of HDLM.

  • Page 228

    3. Creating an HDLM Environment KAPL12329-I The utility for supporting the boot disk started. KAPL12344-I A compressed initial ramdisk image /boot/ initrd-hdlm-2.6.9-11.EL.gz was created. KAPL12330-I The utility for supporting the boot disk completed. Example of Executing the utility when IPF (with ELILO as the dlmmkinitrd boot loader) is used # /opt/DynamicLinkManager/bin/dlmmkinitrd /boot/efi/efi/...

  • Page 229

    3. Creating an HDLM Environment /dev/sddlmaa1 /boot ext3 defaults This example assumes that IA32 uses as the boot loader. When you use IPF GRUB that uses as the boot loader, the mount point is displayed as ELILO /boot/efi instead of in the line where is coded, and the file system type is /boot...

  • Page 230

    3. Creating an HDLM Environment Figure 3-13: Example of Editing /boot/grub/menu.lst file (When using a kernel that supports Xen) Edit the shaded portion. Figure 3-14: Example of Editing /etc/elilo.conf file Edit the shaded portion. 17. If necessary, back up the file. 18.

  • Page 231

    3. Creating an HDLM Environment 19. Assign a name to the copied configuration that indicates that the configuration is used for specifying the HDLM device. • If you will use GRUB as the boot loader Change title • If you will use ELILO as the boot loader Change label 20.

  • Page 232

    3. Creating an HDLM Environment # vgscan Reading all physical volumes. This may take a while... Found volume group "VolGroup00" using metadata type lvm2 27. Check the relationship between the volume group and HDLM devices. Execute the following command to make sure that the physical volumes that make up the volume group are HDLM devices.

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

    3. Creating an HDLM Environment 3.7.6 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...

  • Page 234

    3. Creating an HDLM Environment device. Note that if settings are incorrect, the OS might not start. In this subsection, the procedure assumes that you are using as the GRUB ELILO default boot loader in Red Hat Enterprise Linux, SUSE LINUX Enterprise Server 10, or SUSE LINUX Enterprise Server 11.

  • Page 235

    3. Creating an HDLM Environment /dev/sda1 /boot ext3 defaults Update the information about the volume group. Execute the following command to update the information about the volume group. # vgscan Reading all physical volumes. This may take a while... Found volume group "VolGroup00" using metadata type lvm2 Check the relationship between the volume group and HDLM devices.

  • Page 236

    3. Creating an HDLM Environment Edit the file so that the LVM2 recognizes the SCSI /etc/lvm/lvm.conf device, not the HDLM device. Figure 3-15: Example of Editing /etc/lvm/lvm.conf file shows an example of editing the file. /etc/lvm/lvm.conf...

  • Page 237

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

  • Page 238

    3. Creating an HDLM Environment 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.

  • Page 239

    3. Creating an HDLM Environment 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. 10. 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 240

    3. Creating an HDLM Environment 13. Specify the configuration that will be used for booting. • When GRUB is the boot loader Specify the position of the valid title default • When ELILO is the boot loader Specify label default 14.

  • Page 241

    3. Creating an HDLM Environment 20. Perform an upgrade installation of HDLM. To perform an upgrade installation of HDLM, see 3.6.5 Performing an Upgrade Installation of HDLM, 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. Note that the...

  • Page 242

    3. Creating an HDLM Environment procedure differs depending on whether the host is restarted after installation. 21. Execute the utility with the parameter specified to check the dlmcfgmgr correspondence between the HDLM device and the SCSI device. # dlmcfgmgr -v HDevName Management Device Host...

  • Page 243

    3. Creating an HDLM Environment for uninstallation or upgrade installation of HDLM. 23. Execute the utility for supporting a boot disk to create an initial dlmmkinitrd RAM disk image file for HDLM If the initial RAM disk image file to be created already exists and you are using Red Hat Enterprise Linux, specify the parameter to overwrite this file.

  • Page 244

    3. Creating an HDLM Environment initrd-2.6.16.46-0.14-default.hdlm was created. KAPL12330-I The utility for supporting the boot disk completed. 24. When you create a new initial RAM disk image file rather than overwriting the existing one, delete the existing initial RAM disk image file that is no longer required.

  • Page 245

    3. Creating an HDLM Environment Server 11, check the file instead of the /boot/grub/menu.lst /etc/ file. grub.conf The detailed procedure is explained in steps 27 to 31. Figure 3-20: Example of Editing /etc/grub.conf file, Figure 3-21: Example of Editing /boot/grub/menu.lst file (When using a kernel that supports Xen), and Figure 3-22: Example of Editing /etc/elilo.conf file show examples of editing the configuration file.

  • Page 246

    3. Creating an HDLM Environment Figure 3-21: Example of Editing /boot/grub/menu.lst file (When using a kernel that supports Xen) Edit the shaded portion.

  • Page 247

    3. Creating an HDLM Environment Figure 3-22: Example of Editing /etc/elilo.conf file Edit the shaded portion. 27. Copy the configuration that was used for startup from the HDLM device. 28. Assign a name to the copied configuration that indicates that the configuration is used for specifying the HDLM device after update.

  • Page 248

    3. Creating an HDLM Environment 30. In , specify the initial RAM disk image file you created in step 23. initrd If you are using a kernel that supports Xen, change the file name initrd specified in to the initial RAM disk image file you created in step 23. module When an option that depends on the user environment is specified, be careful not to delete the option.

  • Page 249

    3. Creating an HDLM Environment Found volume group "VolGroup00" using metadata type lvm2 37. Check the relationship between the volume group and HDLM devices. Execute the following command to make sure that the physical volumes that make up the volume group are HDLM devices.

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

    3. Creating an HDLM Environment 3.7.7 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 251

    3. Creating an HDLM Environment An error message appears and the OS stops. A prompt for a password for starting maintenance appears, and the OS stops. The following explains the action to be taken for each case. (1) 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...

  • Page 252

    3. Creating an HDLM Environment file, or file to make sure that the etc/elilo.conf /boot/grub/menu.lst initial RAM disk image file and are specified correctly. ramdisk_size Modify any incorrect specification. If startup from the HDLM device still fails after you correctly specify the initial RAM disk image file and , the initial RAM disk image file might ramdisk_size...

  • Page 253: Settings For Luks, Notes On Using Luks, Using Hdlm In An Luks Environment

    3. Creating an HDLM Environment 3.8 Settings for LUKS This section explains the procedures that the user must perform when using LUKS. 3.8.1 Notes on Using LUKS The followings are notes on using LUKS: • HDLM supports LUKS on the following OSs: •...

  • Page 254

    3. Creating an HDLM Environment # dlmcfgmgr -v HDevName Management Device Host Channel Target Lun /dev/sddlmaa configured /dev/sdh /dev/sddlmab configured /dev/sdj KAPL10302-I /sbin/dlmcfgmgr completed normally. HDLM devices are listed in the column, and SCSI devices are listed HDevName in the column.

  • Page 255

    3. Creating an HDLM Environment 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/ device. mapper/luks-volume1 # cryptsetup luksClose luks-volume1 Map the device used by device mapper to the HDLM device.

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

    3. Creating an HDLM Environment 3.9 Settings for md Devices This section explains the procedures that the user must perform when using md devices. 3.9.1 Notes on Setting Up md Devices The following are notes on using md devices: • Because HDLM is multi-path software, it cannot be used with the MULTIPATH function for md devices.

  • Page 257: Creating An Md Device

    3. Creating an HDLM Environment Figure 3-23: Example of Incorrectly Configured md Devices If you want to manage md devices by using HDLM, migrate the md devices that are made up of SCSI devices to the md devices that are made up of HDLM devices.

  • Page 258

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

  • Page 259

    3. Creating an HDLM Environment Selected partition 1 Hex code (type L to list codes): 83 Command (m for help): p 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...

  • Page 260

    3. Creating an HDLM Environment If the configuration file has already been created, execute the /etc/mdadm.conf following command to create a backup: # cp -pr /etc/mdadm.conf /etc/mdadm.conf.backup Execute the following command to create a configuration file: # echo "DEVICE /dev/sddlmaa1 /dev/sddlmab1" >> /etc/ mdadm.conf # mdadm --detail --scan | grep -w "/dev/md0"...

  • Page 261: Using Hdlm In An Md Device Environment

    3. Creating an HDLM Environment Make sure that and the HDLM devices are displayed. md0 : active 3.9.3 Using HDLM in an md Device Environment This subsection describes how to migrate an environment where the md devices were constructed by using SCSI devices to an environment where the md devices were constructed by using HDLM-managed devices.

  • Page 262

    3. Creating an HDLM Environment If necessary, back up the application data residing on the md device. If file systems have been mounted on the md device, unmount them. Check the status of the md device. Execute the following command to check the configuration of the md device: # cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdh1[0] sdi1[1]...

  • Page 263

    3. Creating an HDLM Environment For details about the contents of the configuration file, see the Linux documentation or use the command. If you created a new configuration file, go to step 9. If you have already used a configuration file ( ), delete the /etc/mdadm.conf unnecessary...

  • Page 264

    3. Creating an HDLM Environment # mdadm -Ss /dev/md0 11. 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> Make sure that is not displayed.

  • Page 265

    3. Creating an HDLM Environment The following example shows how to execute the command to change the fdisk disk partition type to # fdisk /dev/sddlmaa Command (m for help): p Disk /dev/sddlmaa: 5368 MB, 5368709120 bytes 166 heads, 62 sectors/track, 1018 cylinders Units = cylinders of 10292 * 512 = 5269504 bytes Device Boot Start...

  • Page 266

    3. Creating an HDLM Environment 5238528 blocks [2/2] [UU] unused devices: <none> Make sure that and the HDLM devices are displayed. md0 : active 18. If you need to mount the file systems on the md device, mount them. 19. Add a path to the LU. Connect a path to the corresponding LU and then restart the host, or add a path to an existing LU by performing the procedure described in (3) Adding a Path to an Existing LU in 4.6.4 Changing the HDLM Device Configuration.

  • Page 267

    3. Creating an HDLM Environment Stop all applications that are using the existing md device. If necessary, back up the application data residing on the md device. If file systems have been mounted on the md device, unmount them. Check the status of the md device. Execute the following command to check the configuration of the md device: # cat /proc/mdstat Personalities : [multipath]...

  • Page 268

    3. Creating an HDLM Environment size=5238528K mtime=Wed Feb 6 19:17:08 2008 mdadm: /dev/sddlmaa1 appears to be part of a raid array: level=-4 devices=2 ctime=Wed Feb 6 19:16:07 2008 Continue creating array? y mdadm: array /dev/md0 started. Create a configuration file. Execute the following command to add an md device definition to the existing configuration file /etc/mdadm.conf...

  • Page 269

    3. Creating an HDLM Environment ARRAY /dev/md0 level=linear num-devices=1 UUID=426a9f1c:9cfa6310:6aa9a80b:11ea2102 auto=yes 11. On the line of the configuration file, change a SCSI device name to an DEVICE HDLM device name. Based on the correspondence between the HDLM devices and SCSI devices checked in step 6, change the SCSI device names on the line to the DEVICE...

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

    3. Creating an HDLM Environment 3.10 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 271

    3. Creating an HDLM Environment logical volume. Use the following procedure to configure the environment shown in Figure 3-28: Device configuration When Creating a Logical Volume on an HDLM Device. 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.

  • Page 272

    3. Creating an HDLM Environment Example of executing the command (IA32, IPF or EM64T/AMD64): parted...

  • Page 273

    3. Creating an HDLM Environment When you use the command to change the partition, to let the parted system recognize the partitions on the HDLM device, execute the blockdev command after the command. parted Edit the file. /etc/lvm/lvm.conf Edit the device section in the file as shown below to disable the SCSI device configuration and enable the HDLM device configuration: •...

  • Page 274

    3. Creating an HDLM Environment • Adding entry information types Add the following line: types = [ "sddlmfdrv", 16 ] Make sure that was commented out. types=[ "fd", 16 ] Figure 3-29: Example of Editing the /etc/lvm/lvm.conf File shows an example of editing the file when the OS is SUSE LINUX Enterprise Server 9.

  • Page 275

    3. Creating an HDLM Environment 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 /dev/ as physical volumes: sddlmad2 # pvcreate /dev/sddlmad1 Physical volume "/dev/sddlmad1" successfully created # pvcreate /dev/sddlmad2...

  • Page 276

    3. Creating an HDLM Environment Physical volume "/dev/sddlmad2" successfully created Create a volume group. In the following example, the command creates the volume group by using vg01 the physical volumes /dev/sddlmad1 /dev/sddlmad2 # vgcreate vg01 /dev/sddlmad1 /dev/sddlmad2 Volume group "vg01" successfully created Create the logical volume.

  • Page 277: Environment To An Hdlm Device

    3. Creating an HDLM Environment # mkdir /mnt/lvol1 Mount the logical volume. The following example shows how to mount the logical volume to the /mnt/ directory: lvol1 # mount /dev/vg01/lvol1 /mnt/lvol1 3.10.3 When Moving a Logical Volume Created on a SCSI Device in a Single-Path Environment to an HDLM Device This subsection explains the procedure for moving a logical volume created on a SCSI device in a single-path environment to an HDLM device in a multi-path environment.

  • Page 278

    3. Creating an HDLM Environment In Figure 3-30: Device Configuration When a Logical Volume on a SCSI Device Is Moved to an HDLM Device, n indicates the different LUs. sddlmad1 indicate the HDLM devices corresponding to each LU. sddlmad2 To move the logical volume to an HDLM device: Make sure that HDLM has been installed.

  • Page 279

    3. Creating an HDLM Environment Edit the file. /etc/lvm/lvm.conf 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 entry information filter Add the following line and comment out all other entry information: filter filter = [ "a|sddlm[a-p][a-p].*|", "r|/dev/sd|"...

  • Page 280

    3. Creating an HDLM Environment 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...

  • Page 281

    3. Creating an HDLM Environment Import the volume group. In the following example, the command imports the volume group: vg01 # vgimport vg01 Volume group "vg01" successfully imported 10. Execute the command to check that the environment has been changed pvscan successfully.

  • Page 282: Settings For Xen

    3. Creating an HDLM Environment 3.11 Settings for Xen When HDLM is installed in an environment that uses Xen, the SCSI devices corresponding to HDLM devices are accessible from a domainU environment. Therefore, you must specify the certain settings so that the SCSI devices cannot be accessed from the domainU environment directly.

  • Page 283

    3. Creating an HDLM Environment (dev sdx) (uname phy:/dev/sda) (mode w) If the SCSI device displayed on the line is the SCSI device that uname phy appeared in in step 1, continue to step 3. (Only a SCSI device that appears in step 1 can be migrated to an HDLM device.) If domainU is running, stop it.

  • Page 284: Settings For Kvm

    3. Creating an HDLM Environment 3.12 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 ). For details on the hardware configuration file, see the OS .xml documentation.

  • Page 285

    3. Creating an HDLM Environment After: <source dev='/dev/sddlmad'/> For details on which SCSI devices correspond to which HDLM devices, see 4.3.5 Displaying Corresponding Information About an HDLM Device, SCSI Device, and LDEV. Execute the following command to enable the settings in the hardware configuration file.

  • Page 286: Settings For Heartbeat

    3. Creating an HDLM Environment 3.13 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. To set up Heartbeat: Stop the Heartbeat service in the cluster.

  • Page 287: Settings For Oracle Rac

    3. Creating an HDLM Environment 3.14 Settings for Oracle RAC The following are notes on using Oracle RAC: When you use Oracle Cluster file System in an Oracle RAC environment, set parameter in the file. comm_voting /etc/ocfs.conf When you use Oracle Cluster file System 2 in an Oracle RAC environment, set parameter in the O2CB_HEARTBEAT_THRESHOLD /etc/sysconfig/o2cbf...

  • Page 288

    3. Creating an HDLM Environment Table 3-55: Formula for Calculating MISSCOUNT Storage system type Formula for obtaining the value of MISSCOUNT • Lightning 9900 series number-of-paths-connected-to-the-voting-disk 60 seconds • Lightning 9900V series • Hitachi USP • Universal Storage Platform V/VM •...

  • Page 289

    3. Creating an HDLM Environment If the Oracle command is executed for HDLM devices, the oracleasm KAPL05023-E message might be output to syslog. If the following message indicating the successful completion of the oracleasm command is output after this message, there is no problem with HDLM operation. oracleasm: succeeded If you use HDLM with Oracle RAC 10g or Oracle RAC 11g and use ASMLib of...

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

    3. Creating an HDLM Environment 3.15 Settings for the RHCM The user must execute the following procedure when HDLM is installed in an environment that uses RHCM. 3.15.1 Notes on Using RHCM The HDLM device used by the cluster service and the HDLM device used by Quorum must be the same.

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

    3. Creating an HDLM Environment 3.15.3 When Using Red Hat Enterprise Linux 5, or Red Hat Enterprise Linux 6 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 # service cman stop Change the SCSI device being used by RHCM to an HDLM device.

  • Page 292: Settings For Vcs

    3. Creating an HDLM Environment 3.16 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.

  • Page 293: Checking The Path Configuration

    3. Creating an HDLM Environment 3.17 Checking the Path Configuration HDLM functions, such as load balancing and failover, are only available for HDLM management-target devices that have more than one active path. After you install HDLM or change the hardware configuration, check the structure and statuses of the paths.

  • Page 294

    3. Creating an HDLM Environment see whether the HDLM device corresponding to the SCSI device has been created.

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

    3. Creating an HDLM Environment 3.18 Setting Up HDLM HDLM includes functions like the load balancing function, the automatic failback function, the error logging function, the audit logging function, etc. You can set up these functions by using the command's operation.

  • Page 296

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

  • Page 297

    3. Creating an HDLM Environment • for the Round Robin algorithm • for the Extended Round Robin algorithm exrr • for the Least I/Os algorithm • for the Extended Least I/Os algorithm exlio • for the Least Blocks. algorithm • for the Extended Least Blocks algorithm exlbk The type of algorithm specified by the...

  • Page 298

    3. Creating an HDLM Environment If you set the number of times that the error needs to occur to , the above condition does not need to be satisfied. The following is an example of using a command to enable automatic failback: # /opt/DynamicLinkManager/bin/dlnkmgr set -afb on -intvl 10 To enable automatic failback, specify .

  • Page 299

    3. Creating an HDLM Environment monitoring, specify . When you specify , you can use the -intvl -iemnum parameters to specify intermittent error conditions (the conditions used by the system to determine whether an intermittent error is occurring). In the parameter, -intvl specify the monitoring interval for an intermittent error.

  • Page 300

    3. Creating an HDLM Environment from 1 to 64). Table 3-59: Values for the Trace Level Setting lists and describes the possible values for the trace level setting. Table 3-59: Values for the Trace Level Setting Value Description No trace is output. Only error information is output.

  • Page 301

    3. Creating an HDLM Environment # /opt/DynamicLinkManager/bin/dlnkmgr set -elfs 1000 Specify the size of the error log file in KB. (8) Setting the Number of Error Log Files The number of the error log files (the HDLM manager log ( (n indicates dlmmgr .log...

  • Page 302

    3. Creating an HDLM Environment message will be displayed to confirm the execution, and the trace file will be temporarily deleted. By specifying both the trace file size and the number of trace files, you can collect up to 1024000 KB of trace data. The following is an example of using a command to set the number of trace files: # /opt/DynamicLinkManager/bin/dlnkmgr set -systfn 10 Specify the number of trace files by using numbers.

  • Page 303

    3. Creating an HDLM Environment Value Explanation Audit log events of the category are collected. ConfigurationAccess Audit log events of the , and categories StartStop Authentication ConfigurationAccess are all collected. This example shows how to enable the collection of audit log data: # /opt/DynamicLinkManager/bin/dlnkmgr set -audlog on -audlv 6 -category all Specify...

  • Page 304: Checking The Updated Settings

    3. Creating an HDLM Environment This example shows how to specify the audit log facility: # /opt/DynamicLinkManager/bin/dlnkmgr set -audfac local0 3.18.3 Checking the Updated Settings This chapter describes steps involved in how to check the new settings by using the command's operation after the new settings are applied.

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

    3. Creating an HDLM Environment 3.19 The Process-specific-trace Information File When HDLM is used, the dlnkmgr command logs are output to the following process-specific-trace (traces for multiple processes) information files of Hitachi Network Objectplaza Trace Library (HNTRLib2): /var/opt/ (n indicates a file number). DynamicLinkManager/log/dlnkmgr .log Table 3-63: Setting Values for the Process-specific-trace Information Files shows the...

  • Page 306: Creating A Character-type Device File For An Hdlm Device

    3. Creating an HDLM Environment 3.20 Creating a Character-Type Device File for an HDLM Device This section describes how to create a character-type device file for an HDLM device. HDLM creates only a block-type device under /dev If the OS is Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 6, use an rule file to create the character-type device file.

  • Page 307

    3. Creating an HDLM Environment Figure 3-32: Executing the raw Command In this example, the command creates as a character-type device file /dev/raw/raw1 (major number of , minor number of /dev/sddlmaa...

  • Page 308: Creating File Systems For Hdlm (when Volume Management Software Is Not Used)

    3. Creating an HDLM Environment 3.21 Creating File Systems for HDLM (When Volume Management Software Is Not Used) This section describes how to build a file system in an HDLM-managed device without using volume management software. 3.21.1 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.

  • Page 309

    3. Creating an HDLM Environment Figure 3-33: Example of Creating an ext2 File System...

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

    3. Creating an HDLM Environment 3.22 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.

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

    3. Creating an HDLM Environment In the example, the name of the logical device file of the HDLM device that corresponds to can be identified as /dev/sda sddlmaa Add the name of the logical device file of the HDLM device that was confirmed in step 1 to the file.

  • Page 312

    3. Creating an HDLM Environment Figure 3-35: Example of Executing the dlnkmgr Command's View Operation (With -drv Specified) In the example, the name of the logical device file of the HDLM device that corresponds to can be identified as /dev/sda sddlmaa In the file, change the logical device file name for a SCSI device to...

  • Page 313

    3. Creating an HDLM Environment option. Restart the host or manually mount the HDLM device. The HDLM-managed device is mounted using the logical device file name of the HDLM device.

  • Page 314: Canceling The Settings For Hdlm, Operations On Hdlm-managed Devices

    3. Creating an HDLM Environment 3.23 Canceling the Settings for HDLM Return the HDLM environment to the way it was before HDLM was installed by following the procedure flow shown in Figure 3-36: Overview of HDLM Uninstallation. Figure 3-36: Overview of HDLM Uninstallation Perform as required.

  • Page 315

    3. Creating an HDLM Environment If an HDLM-managed device is registered in an application (including cluster software, but excluding volume management software), cancel registration of the HDLM device. For details on how to cancel the Heartbeat settings, see 3.23.2 Canceling the Heartbeat Settings.

  • Page 316: Canceling The Heartbeat Settings, Canceling The Settings For Oracle Rac

    3. Creating an HDLM Environment Migrate to the SCSI devices from an environment where HDLM devices use LUKS. For details on how to cancel the LUKS settings, see 3.23.10 Canceling the LUKS Settings. 3.23.2 Canceling the Heartbeat Settings If Heartbeat is being used with SUSE LINUX Enterprise Server, the HDLM device settings must be cancelled from Heartbeat.

  • Page 317: Canceling The Settings For Rhcm

    3. Creating an HDLM Environment company with which you have a support service contract for Oracle. • When using release 10.2.0.2.0 or later of Oracle RAC 10g, the value set in the parameter, must be returned to the value that was set before DISKTIMEOUT HDLM was installed.

  • Page 318

    3. Creating an HDLM Environment # service ccsd start # service cman start # service rgmanager start (2) When Using Red Hat Enterprise Linux 5 or When Using Red Hat Enterprise Linux 6 To cancel the settings for RHCM: Stop the cluster service of RHCM. If the RHCM service is running, stop the service by executing the following command: # service rgmanager stop...

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

    3. Creating an HDLM Environment # service cman start # service rgmanager start 3.23.5 Canceling the Settings for VCS This section describes how to cancel the HDLM device settings in VCS in an environment where VCS is used. For details on how to perform operations from the VCS GUI, see the VCS documentation.

  • Page 320

    3. Creating an HDLM Environment In the following example, the configuration information is checked from domU 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 line is an HDLM device that uname phy appeared in the check in step 1.

  • Page 321: Canceling The Kvm Settings

    3. Creating an HDLM Environment If you have temporarily changed the settings so that domainU does not automatically start in step 3, restore the previous settings. 3.23.7 Canceling the KVM Settings If you are using KVM, you need to delete the HDLM device from the hardware configuration file ( domain-name ).

  • Page 322: Canceling The Settings For Lvm2

    3. Creating an HDLM Environment For details on which HDLM device correspond to which SCSI device, see 4.3.5 Displaying Corresponding Information About an HDLM Device, SCSI Device, and LDEV. Execute the following command to enable the settings in the hardware configuration file.

  • Page 323

    3. Creating an HDLM Environment Figure 3-37: Device Configuration When a Logical Volume on an HDLM Device Is Moved to a SCSI Device In Figure 3-37: Device Configuration When a Logical Volume on an HDLM Device Is Moved to a SCSI Device, , and indicate the same LU.

  • Page 324

    3. Creating an HDLM Environment # 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 325

    3. Creating an HDLM Environment enabled. Figure 3-38: Example of Editing the /etc/lvm/lvm.conf File shows an example of editing the file by adding and commenting out lines. In this example, SUSE LINUX Enterprise Server 9 is used as the OS. The shaded parts show the locations that were edited.

  • Page 326: Canceling The Md Device Settings

    3. Creating an HDLM Environment 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" using metadata type lvm2 Import the volume group.

  • Page 327

    3. Creating an HDLM Environment When md devices have been constructed by using SCSI devices, if you do not use the MULTIPATH function for the md devices, perform the procedure described in (1) Migrating to md Devices for which the MULTIPATH Function Is Not Used. If you want to use the MULTIPATH function for the md devices, perform the procedure described in (2) Migrating to md Devices for which the MULTIPATH Function Is Used.

  • Page 328

    3. Creating an HDLM Environment If necessary, back up the application data residing on the md device. If file systems have been mounted on the md device, unmount them. Check the status of the md device. Execute the following command to check the configuration of the md device: # cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sddlmaa1[0] sddlmab1[1]...

  • Page 329

    3. Creating an HDLM Environment checked in step 9, change the HDLM device names on the line to the DEVICE SCSI device names. Before the correction: DEVICE /dev/sddlmaa1 /dev/sddlmab1 After the correction: DEVICE /dev/sdh1 /dev/sdi1 When you edit the line, change only the device names. Do not change the DEVICE partition numbers.

  • Page 330

    3. Creating an HDLM Environment Calling ioctl() to re-read partition table. Syncing disks. Also perform the above operation for /dev/sddlmab 12. Execute the following command to activate the md device: # mdadm -As /dev/md0 mdadm: /dev/md0 has been started with 2 drives. 13.

  • Page 331

    3. Creating an HDLM Environment 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 (1) Migrating to md Devices for which the MULTIPATH Function Is Not Used.

  • Page 332

    3. Creating an HDLM Environment # cat /proc/mdstat Personalities : [linear] unused devices: <none> Make sure that is not displayed. md0 : active Check the correspondence with HDLM device. Execute the HDLM-configuration definition utility with the dlmcfgmgr parameter specified: # dlmcfgmgr -v HDevName Management Device Host Channel Target Lun...

  • Page 333

    3. Creating an HDLM Environment # mdadm --detail --scan | grep -w "/dev/md0" >> /etc/ mdadm.conf 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/sddlmaa1 ARRAY /dev/md0 level=linear num-devices=1 UUID=426a9f1c:9cfa6310:6aa9a80b:11ea2102 auto=yes...

  • Page 334: Canceling The Luks Settings

    3. Creating an HDLM Environment DEVICE /dev/sddlmaa1 After the correction: DEVICE /dev/sdh1 /dev/sdo1 Specify all SCSI devices that correspond to HDLM devices. When you edit the line, change only the device names. Do not change the DEVICE partition numbers. 11. Execute the following command to deactivate the md device: # mdadm -Ss /dev/md0 12.

  • Page 335: Uninstalling Hdlm

    3. Creating an HDLM Environment parameter specified to check the correspondence between the SCSI device and the HDLM device. The following shows an example of executing the utility with the dlmcfgmgr specified parameter: # dlmcfgmgr -v HDevName Management Device Host Channel Target Lun /dev/sddlmaa configured /dev/sdh /dev/sddlmab configured...

  • Page 336

    3. Creating an HDLM Environment • If you uninstall HDLM, the error logs ( /var/tmp/hdlminstlog/ ) generated during installation of HDLM are installhdlm[01-10].log not uninstalled. Delete the /var/tmp/hdlminstlog/ files as needed. installhdlm[01-10].log For details on the files, see 3.4 Knowledge installhdlm[01-10].log Required Before You Install HDLM.

  • Page 337

    3. Creating an HDLM Environment sddlmfdrv 254092 If a value other than is displayed for , perform the operation described in Used 3.23.1 Operations on HDLM-Managed Devices, and then perform steps 2 and 3 in (1) Uninstalling HDLM so that the HDLM devices can no longer be used. Execute the uninstall command.

  • Page 338

    3. Creating an HDLM Environment Make sure that the HDLM device is defined in the file. /etc/fstab Make sure that the mount points for the following HDLM management-target devices are defined so that the HDLM device will be mounted: • When is used as the boot loader: ELILO Root directory (...

  • Page 339

    3. Creating an HDLM Environment Figure 3-41: Example of Executing the dlmcfgmgr Utility with the -v Parameter Specified Figure 3-42: Example of Executing the dlmcfgmgr Utility with the -v and -udev Parameters Specified , and columns display HDLM devices, SCSI HDevName Device Udev...

  • Page 340

    3. Creating an HDLM Environment to step 7. Execute the following commands to check the device name: • For Red Hat Enterprise Linux 6 Execute the command. udevadm Specify the value below for the option. For SCSI-device-name, specify the value checked in step 3. SCSI-device-name /sys/block/ name-that-added-SCSI-device-name-and-partition-number...

  • Page 341

    3. Creating an HDLM Environment pci-0000:20:01.0-scsi-0:0 :1:0-part2 disk/by-uuid/ c230c70d-1b18-4d95-b50a-31edb3bd038c In the execution result, disk/by-id/ indicates the device name ( scsi-2000c50fffecb6ae0-part2 udev name) that corresponds to /dev/sda2 To specify the device name ( name) in the directory udev /dev/disk instead of the SCSI device, replace the SCSI device ( ) checked /dev/sda2 in step 3 with...

  • Page 342

    3. Creating an HDLM Environment installation. Edit the boot loader configuration file for SCSI startup. If you are using SUSE LINUX Enterprise Server 10, check the /boot/grub/ file instead of the file. menu.lst /etc/grub.conf The detailed procedure is explained in steps 8 to 11. Separate examples are provided for when the boot loader is LILO, when the boot loader is GRUB, when the boot loader is ELILO running on an IPF host, and when LVM2 is used.

  • Page 343

    3. Creating an HDLM Environment image=/boot/vmlinuz-2.6.18-194.el5 label=linux initrd=/boot/initrd-2.6.18-194.el5 read-only option append=" " root=/dev/sda2 • When the boot loader is GRUB Example 1 below shows an example of editing the file /etc/grub.conf (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 344

    3. Creating an HDLM Environment option initrd /initrd-2.6.18-194.el5 Example 2: Example of Editing file (When using /boot/grub/menu.lst a kernel that supports Xen on SUSE LINUX Enterprise Server 10) #default 0 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...

  • Page 345

    3. Creating an HDLM Environment prompt timeout=50 #default= HDLM_2.6.18-194.el5 default= 2.6.18-194.el5-sd image=vmlinuz-2.6.18-194.el5 label=HDLM_2.6.18-194.el5 initrd=initrd-hdlm-2.6.18-194.el5.img read-only option option append=" ramdisk_size=18245 " image=vmlinuz-2.6.18-194.el5 label=2.6.18-194.el5-sd initrd=initrd-2.6.18-194.el5.img read-only option append=" " root=/dev/sda2 • When using LVM2 An example of editing the file (the underlined sections) /etc/grub.conf is shown below.

  • Page 346

    3. Creating an HDLM Environment kernel /vmlinuz-2.6.9-11.EL ro rhgb quiet initrd /initrd-hdlm-2.6.9-11.EL.gz 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.

  • Page 347

    3. Creating an HDLM Environment image file for the SCSI device. When editing the file, be careful of the following: • When an option that depends on the user environment is specified: Be careful not to delete the option. • When the boot loader is LILO, or ELILO running on an IPF host, and an option that depends on the user environment is not specified: Comment out or delete append...

  • Page 348

    3. Creating an HDLM Environment Figure 3-44: Example of Executing the mount Command When the Boot Loader Is LILO or GRUB • When the boot loader is ELILO running on an IPF host Figure 3-45: Example of Executing the mount Command When the Boot Loader Is ELILO shows an example of executing the command.

  • Page 349

    3. Creating an HDLM Environment 18. Delete the initial RAM disk image file that was created with the dlmmkinitrd utility for supporting a boot disk. To do this, execute the following command:...

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

    3. Creating an HDLM Environment • When an IA32 host is used: # rm /boot/initrd-hdlm-2.6.18-194.el5.gz • When an IPF host is used: # rm /boot/efi/efi/redhat/initrd-hdlm-2.6.18-194.el5.gz 19. Stop HDLM that was used in a location other than the root directory. For details on how to stop HDLM, see steps 2 to 4 in 3.23.1 Operations on HDLM-Managed Devices and (1) Uninstalling HDLM.

  • Page 351

    3. Creating an HDLM Environment To uninstall HNTRLib2: Log in to Linux as the root user. Execute the following command to unregister the name of the bundled program products. # /opt/hitachi/HNTRLib2/etc/hntr2cancel "Hitachi Dynamic Link Manager" Execute the following command. # /opt/hitachi/HNTRLib2/etc/hntr2setup The HNTRLib2 setup menu will appear.

  • Page 353: Hdlm Operation

    Chapter 4. HDLM Operation This chapter describes operating procedures for HDLM, including how to operate HDLM and the HDLM manager, and how to change the configuration of the operating environment. 4.1 Notes on Using HDLM 4.2 Updating Kernel Packages and Applying OS Update Packages 4.3 HDLM Operations Using Commands 4.4 Starting and Stopping the HDLM Manager 4.5 HDLM Resident Processes...

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

    4. HDLM Operation 4.1 Notes on Using HDLM Note the following when using HDLM. 4.1.1 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 355

    4. HDLM Operation 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;...

  • Page 356: Notes When Using Red Hat Enterprise Linux As4/es4, Or Oracle Enterprise Linux 4

    4. HDLM Operation , the operation may not finish. In such a case, perform the operation again fsck after restoring the path error. The name of the HDLM device file will not be displayed on the Hardware Browser of Red Hat Enterprise Linux. The Linux functionality that adds to a SCSI device is not supported in LABEL=...

  • Page 357: Notes When Using Red Hat Enterprise Linux 5, Red Hat Enterprise Linux

    4. HDLM Operation 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 command to exclude the HDLM device from dlmcfgmgr -o management. When a device is dynamically configured by using the udev function, the messages shown below might be output to the console or syslog.

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

    4. HDLM Operation When a device is dynamically configured by using the udev function, the messages shown below might be output to the console or syslog. However, HDLM operations are not affected. Output example: scsi_id[ ]: scsi_id: unable to access parent device of '/ block/sddlma01' For a01 in the above examples, any alphanumeric character can be output.

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

    4. HDLM Operation JBD: barrier-based sync failed on sddlmaa1 - disabling barriers Before you update the OS SP, uninstall HDLM. After you have updated the OS SP, re-install HDLM. For details on HDLM installation and uninstallation, see 3.6 Installing HDLM and 3.23.11 Uninstalling HDLM.

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

    4. HDLM Operation JBD: barrier-based sync failed on sddlmaa1 - disabling barriers Before you update the OS SP, uninstall HDLM. After you have updated the OS SP, re-install HDLM. For details on HDLM installation and uninstallation, see 3.6 Installing HDLM and 3.23.11 Uninstalling HDLM.

  • Page 361

    4. HDLM Operation Unmount any devices mounted on the HDLM device. Execute the command to exclude the HDLM device from dlmcfgmgr -o management. HDLM devices cannot be used to create an md device. If you execute the command on the file system that is mounted by ext3/ sync ReiserFS, the following message is output to syslog, but there is no problem with HDLM operations.

  • Page 362

    4. HDLM Operation • A Fibre Channel switch's zone setting is changed.

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

    4. HDLM Operation 4.2 Updating Kernel Packages and Applying OS Update Packages When using Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 6, you can update kernel packages or apply OS update packages while HDLM is installed. Table 4-1: HDLM Installation Environments in Which Kernel Packages Can Be Updated or OS Update Packages Applied shows the HDLM installation environments in which kernel packages can be updated or OS update packages applied.

  • Page 364: Environment Where A Logical Volume (lvm2) On An Hdlm Device Is Used As The Boot Disk

    4. HDLM Operation Perform step 1 to 15 in 3.7.4 Upgrade Installation in an Environment Where an HDLM Device Is Used as a Boot Disk. Update the kernel package or OS update package. Execute the utility for updating system scripts. dlmupdatesysinit For details about this utility, see 7.8 dlmupdatesysinit Utility for Updating System Scripts.

  • Page 365: Hdlm Operations Using Commands, Notes On Using Commands, Viewing Path Information

    4. HDLM Operation 4.3 HDLM Operations Using Commands This section explains how to use the HDLM command. For details on the various command operations, see 6. Command Reference. 4.3.1 Notes on Using Commands • Execute the command as a user with root permissions. •...

  • Page 366

    4. HDLM Operation Check the current status of the paths. To place paths online by specifying an HBA port, CHA port, or single path check the path name or PATH_ID used to manage the path. The following example shows how to execute the command: # /opt/DynamicLinkManager/bin/dlnkmgr view -path To place paths online by specifying a SCSI device name, check the SCSI device name of the path.

  • Page 367: Viewing Lu Information

    4. HDLM Operation port, or single path check the path name or PATH_ID used to manage the path. The following is an example of executing the command: # /opt/DynamicLinkManager/bin/dlnkmgr view -path To place a path by specifying a SCSI device name, check the SCSI Offline(C) device name of the path.

  • Page 368: Device, And Ldev

    4. HDLM Operation To display LU information, execute the command's operation with the dlnkmgr view parameter specified. The following is an example of executing the command: # /opt/DynamicLinkManager/bin/dlnkmgr view -lu Product : 9500V SerialNumber : 0115 HDevName Device PathID Status 0000 sddlmac /dev/sds 000002 Online /dev/sdd 000007 Online...

  • Page 369: Initializing Statistical Information For Paths

    4. HDLM Operation The following is an example of executing the command's operation: dlnkmgr view # /opt/DynamicLinkManager/bin/dlnkmgr view -drv PathID HDevName Device LDEV 000000 sddlmaa /dev/sdag 9970/9980.15001.05B7 000001 sddlmaa /dev/sdq 9970/9980.15001.05B7 000002 sddlmab /dev/sdr 9970/9980.15001.05B0 000003 sddlmac /dev/sds 9970/9980.15001.05B1 000004 sddlmad /dev/sdt 9970/9980.15001.05B2 000005 sddlmae...

  • Page 370: Viewing And Setting Up The Operating Environment

    4. HDLM Operation Operation name = clear [y/n]:y KAPL01001-I The HDLM command completed normally. Operation name = clear, completion time = yyyy/mm/dd hh:mm:ss 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 4.3.7 Viewing and Setting Up the Operating Environment This section explains how to display and set up the HDLM operating environment.

  • Page 371

    4. HDLM Operation # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -audlog Audit Log : off Audit Log Category Audit Log Facility KAPL01001-I The HDLM command completed normally. Operation name yyyy dd hh = view, completion time = For details on the displayed items and their descriptions, see 6.7 view (Displays Information).

  • Page 372: Viewing License Information, Updating The License

    4. HDLM Operation To check whether the settings have been applied, see (1) Viewing the Operating Environment. 4.3.8 Viewing License Information This section explains how to display license information. To display license information, execute the command's operation with dlnkmgr view parameters specified.

  • Page 373: Viewing Hdlm Version Information

    4. HDLM Operation # /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. 4.3.10 Viewing HDLM Version Information This section explains how to display HDLM version information. To display HDLM version information, execute the command's dlnkmgr...

  • Page 374: Viewing Hdlm Component Information

    4. HDLM Operation 4.3.11 Viewing HDLM Component Information This section explains how to display HDLM component information. To display HDLM component information, execute the command's dlnkmgr view operation with the parameter specified. The following is an example of -sys executing the command: # /opt/DynamicLinkManager/bin/dlnkmgr view -sys x.x.x-xx HDLM Version...

  • Page 375

    4. HDLM Operation...

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

    4. HDLM Operation 4.4 Starting and Stopping the HDLM Manager If an error occurs in the system, such as in an HDLM program, you may need to manually stop or start HDLM to recover from the error. 4.4.1 Starting the HDLM Manager To start the HDLM manager, log in to Linux as a user with root permissions and then execute the following command.

  • Page 377: Stopping The Hdlm Manager

    4. HDLM Operation # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -msrv HDLM Manager Ver WakeupTime x.x.x-xx Alive 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 column shows , the HDLM manager is active. HDLM Manager Alive Use a script for confirmation:...

  • Page 378

    4. HDLM Operation When the column shows , the HDLM manager is inactive. HDLM Manager Dead 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 command's dlnkmgr...

  • Page 379: Hdlm Resident Processes

    4. HDLM Operation 4.5 HDLM Resident Processes Table 4-2: HDLM resident processes lists and describes the resident processes in HDLM. To monitor these processes, use the names below. Table 4-2: HDLM resident processes Process Description HDLM manager process .dlmmgr_exe Hitachi Command Suite Common Agent Component process hbsa_service You only need to monitor this process when HDLM is linked to Global Link...

  • Page 380: Reconfiguring The Hdlm Operating Environment, Replacing Hbas

    4. HDLM Operation 4.6 Reconfiguring the HDLM Operating Environment This section describes tasks required for reconfiguring the HDLM operating environment. The tasks described in this section are required when you perform any of the following operations: • Replace hardware devices that make up a path •...

  • Page 381

    4. HDLM Operation # /sbin/lsmod | grep acpiphp acpiphp 58713 If the module has been loaded, replace the HBAs as described in acpiphp (2) Procedure for replacing HBAs. If the module has not been loaded, acpiphp continue to step 2. Create the file.

  • Page 382

    4. HDLM Operation # /etc/sysconfig/modules/acpiphp.modules After the above command has been executed, confirm that the module acpiphp has been loaded. # /sbin/lsmod | grep acpiphp acpiphp 58713 (2) Procedure for replacing HBAs Before you can replace HBAs, the paths that pass through the HBAs to be replaced must be blocked.

  • Page 383

    4. HDLM Operation Firmware : 260803 WWPN:2400000047010270 Device:hfcldd2 [LinkUp] WWPN:2400000047010272 Device:hfcldd3 [LinkUp] The number that follows a keyword is the port WWN information of an WWPN HBA. The following steps assume that the HBAs whose WWN information is underlined above are to be replaced. Execute the operation of the command (...

  • Page 384

    4. HDLM Operation Execute the operation of the command ( offline dlnkmgr dlnkmgr offline ) to place in status all paths that pass through the HBA ports -hba Offline(C) that you identified in step 2. For the parameter, specify the host port number and the bus number by -hba separating them with a period.

  • Page 385

    4. HDLM Operation In the above figure, new paths that have been added are indicated by shading. Although the information about the old paths (underlined information) that were placed in status before the HBAs were replaced remains, this Offline(C) information will be deleted in step 8. Execute the utility ( ) to confirm that new SCSI...

  • Page 386

    4. HDLM Operation information) before the HBAs were replaced remains, this information will be deleted when step 8 is performed. Execute the utility ( ) to delete the information about dlmcfgmgr dlmcfgmgr -u the old paths and SCSI devices. In the parameter, specify an device for which old SCSI device HDevName...

  • Page 387

    4. HDLM Operation The paths existing when the HBAs were replaced remain in status. Offline(E) Execute the utility ( ) to check the HDLM device dlmcfgmgr dlmcfgmgr -v status. Because the paths existing when HBAs were replaced are in status, Offline(E) a hyphen ( ) is displayed for...

  • Page 388: Replacing A Fiber Cable

    4. HDLM Operation device for which a hyphen ( ) is displayed for HDevName Device The following shows an example of the command you execute if the HDevName value is /dev/sddlmaa # dlmcfgmgr -u /dev/sddlmaa Execute the utility ( ) to confirm that all the lines on dlmcfgmgr dlmcfgmgr -v which a hyphen (...

  • Page 389

    4. HDLM Operation Figure 4-2: System Configuration for Replacing a Fiber Cable (Explained in the Following Steps) To replace a fiber cable: Place in Offline (C) status the path that goes through the fiber cable to be replaced (path that goes through the HBA to which the fiber cable is connected). For example, to place in Offline (C) status the path that goes through the HBA with host port number and bus number...

  • Page 390

    4. HDLM Operation Figure 4-3: When the Status of the Path That Goes Through the Fiber Cable to Be Replaced Is Offline(C) Replace the fiber cable for the path that has been placed in Offline(C) status. In this example, replace the fiber cable connected to the HBA with host port number 0001 Place in Online status the path that goes through the replaced fiber cable (that is,...

  • Page 391: Replacing The Fibre Channel Switch

    4. HDLM Operation # /opt/DynamicLinkManager/bin/dlnkmgr view -path For details about the path information, see 6.7 view (Displays Information). 4.6.3 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 392

    4. HDLM Operation be replaced (path that goes through the HBA to which the Fibre Channel switch is connected). For example, to place in Offline (C) status the path that goes through the HBA with host port number and bus number , execute the following 0001 0000...

  • Page 393: Changing The Hdlm Device Configuration

    4. HDLM Operation In this example, replace the Fibre Channel switch connected to the HBA with host port number 0001 Place in Online status the path that goes through the replaced Fibre Channel switch. For example, to place in Online status the path that goes through the HBA with host port number and bus number , execute the following command:...

  • Page 394

    4. HDLM Operation management, HDLM places online all the normal paths to that HDLM device regardless of the previous status (such as ) of the Online(E) Offline(C) path. Do not execute the HDLM-configuration definition utility ( ) with the dlmcfgmgr , or parameter while the LU is in use (for example, when performing I/ O or a mount).

  • Page 395

    4. HDLM Operation • A path gets disconnected. • An LU is deleted. • A fiber cable connection is changed. • A Fibre Channel switch's zone setting is changed. If you want to delete the path whose status is indicated by a hyphen ( ), execute utility with the parameter specified.

  • Page 396

    4. HDLM Operation Table 4-3: Adding or Deleting a SCSI Device Operation Command Adding a device • When using a QLogic HBA driver on Red Hat Enterprise Linux AS4/ES4 Update 1, (for FC-SAN execute the commands in the following order: environments) driver-name # echo "scsi-qlascan"...

  • Page 397

    4. HDLM Operation Operation Command Deleting a device # dlmcfgmgr -o logical-device-file-name-of-the-relevant-HDLM-device (for FC-SAN a b c d # echo "scsi remove-single-device " > /proc/scsi/scsi environments) # dlmcfgmgr -i logical-device-file-name-of-the-relevant-HDLM-device Deleting a device a b c d # echo "scsi remove-single-device "...

  • Page 398

    4. HDLM Operation The following is an example of executing the utility: dlmcfgmgr # /sbin/dlmcfgmgr -v (3) Adding a Path to an Existing LU To add a path to an existing LU (HDLM device): Use the management program of the storage system to configure an additional path from an LU mapped with the relevant HDLM device to the relevant host.

  • Page 399

    4. HDLM Operation allocations (that is, to delete the paths) to the relevant LU from ports of the storage system. For details on canceling path allocations (deleting paths), see the manual provided with the storage system. If you want to delete an HDLM device that corresponds to the LU without restarting the host, perform steps 4 and 5.

  • Page 400

    4. HDLM Operation The following is an example of executing the utility: dlmcfgmgr logical_device_file_name_of_HDLM_device # /sbin/dlmcfgmgr -u Check or execute /var/opt/DynamicLinkManager/log/dlmcfgmgr1.log utility ( ) to make sure that the HDLM device that dlmcfgmgr dlmcfgmgr -v corresponds to the deleted LU was deleted. The following is an example of executing the utility: dlmcfgmgr...

  • Page 401

    4. HDLM Operation Perform this operation if necessary. If it is not necessary to check this, go to step 7. If the SCSI device name is not represented with a hyphen (-), to change the SCSI device name to a hyphen, wait until the path health checking has been executed or execute the following command with the AutoPATH_ID of the dlnkmgr...

  • Page 402

    4. HDLM Operation HDLM. The following is an example of executing the utility: dlmcfgmgr # /sbin/dlmcfgmgr -v If the Management status of the relevant HDLM device is represented as in the execution result, this means that the device is managed by configured HDLM.

  • Page 403

    4. HDLM Operation Refer to /var/opt/DynamicLinkManager/log/dlmcfgmgr1.log execute the utility ( ) or the view operation dlmcfgmgr dlmcfgmgr -v ) of the HDLM command to make sure that the relevant dlnkmgr view -path device is now managed by HDLM. The following is an example of executing the utility: dlmcfgmgr # /sbin/dlmcfgmgr -v...

  • Page 404

    4. HDLM Operation relevant HDLM device is restored. The following is an example of executing the utility: dlmcfgmgr # /sbin/dlmcfgmgr -v (9) Restoring the Path of an HDLM Device Started in Disconnected Status (When a Restart Is Not Required) This subsection describes how to restore the path to an HDLM device that was in disconnected status (the cable was pulled out or broken) when the host first started.

  • Page 405

    4. HDLM Operation Table 4-4: Add SCSI Devices Purpose Command Add a device (for • When using a QLogic HBA driver on Red Hat Enterprise Linux AS4/ES4 Update 1, FC-SAN execute the commands in the following order: environments) driver-name # echo "scsi-qlascan" > /proc/scsi/ driver-name # cat /proc/scsi/ View the...

  • Page 406

    4. HDLM Operation Legend: a: Host ID (Port number of the host) b: Channel number (Bus number) c: Target ID d: Lun (LU number of the host) n: host port number driver-name: xxxx (driver name in use) An example entry is shown below. When adding a device by using a QLogic HBA driver in Red Hat Enterprise Linux AS4/ES4: # echo "scsi-qlascan"...

  • Page 407: About Creating A New Hdlm Device

    4. HDLM Operation If the SCSI device name mapped with the path to the relevant HDLM device is represented with a hyphen ( ), in the execution result, this means that the path was in disconnected status. Connect the cable. If the cable is broken, replace it.

  • Page 408

    4. HDLM Operation If the SCSI device of the new path that HDLM detected is not yet registered, a new HDLM device is allocated to the path. For example, if you define a new path from the host to an LU of the storage system, a new HDLM device is allocated to the path. The lowest available alphabetical letter is allocated as the logical device file name of the HDLM device.

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

    4. HDLM Operation 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. is allocated sequentially as the HDLM recognizes a SCSI device AutoPATH_ID during start up of the host.

  • Page 411: Troubleshooting

    Chapter 5. 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. 5.1 Information Collected by the DLMgetras Utility for Collecting HDLM Error Information 5.2 Checking Error Information in Messages...

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

    5. Troubleshooting 5.1 Information Collected by the DLMgetras Utility for Collecting HDLM Error Information Immediately after an error occurs, execute the utility for collecting DLMgetras HDLM error information, since restarting the machine might delete error information before the information is collected by DLMgetras For details about the utility and the error information it collects, see...

  • Page 413: Checking Error Information In Messages

    5. Troubleshooting 5.2 Checking Error Information in Messages When you want to configure the system so that HDLM messages are output to syslog, specify for the name of the system function defined in the syslogd settings file. user In the following example, the system function name is , and messages at the user Information level or higher are output to the...

  • Page 414

    5. Troubleshooting • Host port number (hexadecimal) • Bus number (hexadecimal) • Target ID (hexadecimal) • Host LU number (hexadecimal) This path name is also the same as displayed by the command's PathName view operation. For details on the path name, see 6.7 view (Displays Information). DNum A Dev number, which is equivalent to a partition number in Linux.

  • Page 415

    5. Troubleshooting 5.3 What To Do for a Path Error When a path error is detected, HDLM performs a failover on the path and outputs the KAPL08022-E message. This message indicates that an error has occurred in the components that make up the path. Figure 5-1: Error Location When the KAPL08022-E Message Is Output indicates these components.

  • Page 416: Examining The Messages, Obtain Path Information

    5. Troubleshooting Figure 5-2: Troubleshooting Procedure When a Path Error Occurs The following shows the procedure for using the HDLM command ( ) to dlnkmgr handle a path error. 5.3.1 Examining the Messages Examine the message that is output to syslog in the host by using applications or tools for monitoring messages.

  • Page 417: Identifying The Error Path, Narrowing Down The Hardware That Might Have Caused The Error

    5. Troubleshooting 5.3.3 Identifying the Error Path Check the obtained path information to find the path with the error. In the Status column, the error path has the status Offline(E) Online(E) 5.3.4 Narrowing Down the Hardware That Might Have Caused the Error Check the , and...

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

    5. Troubleshooting 5.4 What To Do for a Program Error The following describes what to do to handle errors that occur in an HDLM program. Figure 5-3: Troubleshooting Procedure When a Program Error Occurs shows the troubleshooting procedure. Figure 5-3: Troubleshooting Procedure When a Program Error Occurs The following shows the procedure for handling a program error by using the HDLM command ( dlnkmgr...

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

    5. Troubleshooting 5.4.3 What To Do for the Program Error Follow the recommended actions for messages in 8. Messages. If the error occurs again after you thought that you had resolved the problem, use the command's operation to check the status of the HDLM program, and dlnkmgr view then do whatever is necessary to resolve the problem.

  • Page 420: What To Do For Other Errors

    5. Troubleshooting 5.5 What To Do for Other Errors When the cause of an error may be related to HDLM but is neither a path error nor an HDLM program error, execute the utility, and then report the collected DLMgetras information to the HDLM vendor or maintenance company if there is a maintenance contract for HDLM.

  • Page 421: Command Reference

    Chapter 6. Command Reference This chapter describes the HDLM command ( ) and its operations. dlnkmgr 6.1 Overview of the HDLM Command dlnkmgr 6.2 clear (Returns the Path Statistics to the Initial Value) 6.3 help (Displays the Operation Format) 6.4 offline (Places Paths Offline) 6.5 online (Places Paths Online) 6.6 set (Sets Up the Operating Environment) 6.7 view (Displays Information)

  • Page 422: Overview Of The Hdlm Command Dlnkmgr

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

  • Page 423

    6. Command Reference Notes: • Execute the command as a user with root permissions. • To specify a value that contains a space in its parameter, enclose the entire value in double quotes ( "...

  • Page 424: Clear (returns The Path Statistics To The Initial Value), Format, Parameters

    6. Command Reference 6.2 clear (Returns the Path Statistics to the Initial Value) command's operation clears the statistics (I/O count and I/O dlnkmgr clear errors) of all paths that are managed by HDLM, and returns them to their initial value. 6.2.1 Format (1) To set the path statistics to 0 /opt/DynamicLinkManager/bin/dlnkmgr clear -pdst [-s]...

  • Page 425

    6. Command Reference (2) To Display the Format of the clear Operation -help Displays the format of the operation. clear 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...

  • Page 426: Help (displays The Operation Format), Format, Parameter, Help (displays The Operation Format)

    6. Command Reference 6.3 help (Displays the Operation Format) command's operation displays the list of operations available for dlnkmgr help the HDLM command, or the format of individual operations. 6.3.1 Format operation operation /opt/DynamicLinkManager/bin/dlnkmgr help [ 6.3.2 Parameter operation Specify the HDLM command operation whose format you want to know. You can specify one of the following operations: •...

  • Page 427

    6. Command Reference # /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 { 000000 - 999999 }(Decimal)

  • Page 428: Offline (places Paths Offline), Format, Parameters, Offline (places Paths Offline)

    6. Command Reference 6.4 offline (Places Paths Offline) command's operation places online paths offline. Specify the dlnkmgr offline paths to be placed offline by specifying an HBA port, CHA port, or single path. Instead of specifying a path, you can also specify a SCSI device name. There must always be at least one online path accessing each LU.

  • Page 429

    6. Command Reference 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 operation. Enter a view period between these two parameter values.

  • Page 430

    6. Command Reference connected to the target CHA port: When the confirmation message is displayed, the user enters to continue, to cancel the operation. # /opt/DynamicLinkManager/bin/dlnkmgr offline -cha -pathid 000001 KAPL01055-I All the paths which pass the specified CHA port will be changed to the Offline(C) status. Is this OK? [y/n]:y KAPL01056-I If you are sure that there would be no problem when all the paths which pass the specified CHA are placed...

  • Page 431

    6. Command Reference device name is while confirming command operation. /dev/sde # /opt/DynamicLinkManager/bin/dlnkmgr offline -path -device /dev/sde KAPL01052-I The currently selected paths will be changed to the Offline(C) status. Is this OK? [y/n]:y KAPL01053-I If you are sure that there would be no problem when the path is placed in the Offline(C) status, enter y.

  • Page 432

    6. Command Reference AutoPATH_ID { 000000 - 999999 }(Decimal) KAPL01001-I The HDLM command completed normally. Operation name = offline, completion time = yyyy/mm/dd hh:mm:ss Reference Using the operation together with standard UNIX commands enables you to view filter the path information listed for a specific HBA port or CHA port. For details about operation, see 6.7 view (Displays Information).

  • Page 433: Online (places Paths Online), Format, Parameters, Online (places Paths Online)

    6. Command Reference 6.5 online (Places Paths Online) command's operation places offline paths online. Specify the dlnkmgr online paths to be placed online by specifying an HBA port, CHA port, or single path. Instead of specifying a path, you can also specify a SCSI device name. 6.5.1 Format (1) To place paths Online /opt/DynamicLinkManager/bin/dlnkmgr online...

  • Page 434

    6. Command Reference Specify the host port number and bus number of the target HBA port: the numbers are found in the PathName field displayed using the operation. Enter a view period between these two parameter values. For details about the operation, view see 6.7 view (Displays Information).

  • Page 435

    6. Command Reference KAPL01057-I All the paths which pass the specified CHA port will be changed to the Online status. Is this OK? [y/n]:y KAPL01061-I 2 path(s) were successfully placed Online; 0 path(s) were not. Operation name = online AutoPATH_ID -pathid Use this parameter to place a single path online.

  • Page 436

    6. Command Reference the response to the confirmation message: for example, when you want to execute the command in a shell script or batch file. Example The following example shows how to place a path, whose AutoPATH_ID is , online without asking for confirmation of command execution 000002 from the user: # /opt/DynamicLinkManager/bin/dlnkmgr online -pathid 2...

  • Page 437

    6. Command Reference target paths before you execute the operation to place online all the paths online connected to a specific HBA port or CHA port. Example 1 The following example shows how to filter and display the information on all paths that pass through the HBA port whose host port number is and bus 0004...

  • Page 438: Set (sets Up The Operating Environment), Format, Parameters, Set (sets Up The Operating Environment)

    6. Command Reference 6.6 set (Sets Up the Operating Environment) command's operation sets the HDLM operating environment. dlnkmgr 6.6.1 Format (1) To Set Up the HDLM Operating Environment /opt/DynamicLinkManager/bin/dlnkmgr set {-lb {on [-lbtype {rr|exrr|lio|exlio|lbk|exlbk}]|off} error-log-collection-level |-ellv error-log-file-size |-elfs number-of-error-log-files |-elfn trace-level |-systflv trace-file-size...

  • Page 439

    6. Command Reference Table 6-2: Default and Recommended Values Item name Default value Recommended value Load balancing The Extended Least I/Os algorithm is The recommended algorithm depends on used. the operating environment. Error log collection : Collect error information for the : Collect error information for the level Information level and higher.

  • Page 440

    6. Command Reference : The Extended Round Robin algorithm exrr : The Least I/Os algorithm : The Extended Least I/Os algorithm exlio : The Least Blocks algorithm : The Extended Least Blocks algorithm exlbk The type of algorithm specified by the -lbtype parameter remains stored in the system, even when you disable the load .

  • Page 441

    6. Command Reference Operation name = set, completion time = yyyy/mm/dd hh:mm:ss error-log-file-size -elfs Specify a value from 100 to 2,000,000 (in KB) for the size of the error log files (n indicates a file number from )). The specified files size dlmmgr .log is applied to HDLM manager logs.

  • Page 442

    6. Command Reference time before existing information will be overwritten becomes shorter. trace-file-size -systfs Specify a value from 100 to 16,000 for the size of the trace log file (in KB). By specifying both the trace file size and the number of trace files, you can collect up to 1,024,000 KB of trace files in total.

  • Page 443

    6. Command Reference The explanation for the following sub-parameter describes how to specify the checking interval. checking-interval -intvl Specify the checking interval between path health checks. Specify a value from 1 to 1440 minutes depending on the user environment When you change the checking interval, the new setting takes effect immediately.

  • Page 444

    6. Command Reference will be checked in the following way: • When the checking interval has not been specified before: Every minute (default setting) • When the checking interval has been specified before: The previously used interval The explanation for the following sub-parameter describes how to specify the interval between path status checks.

  • Page 445

    6. Command Reference : Enabled : Disabled Intermittent error monitoring can be set automatic failback is set to The default is . When you use automatic failback, we recommend that you set intermittent error monitoring to to prevent an intermittent error from reducing I/O performance.

  • Page 446

    6. Command Reference Specify the monitoring interval for an intermittent error. Use a value from 1 to 1440 minutes. The default is During intermittent error monitoring, if changes are made to the intermittent error monitoring interval setting or the setting for the number of times that an error is to occur, the error count and the elapsed time measured since monitoring has started are reset to 0.

  • Page 447

    6. Command Reference started are reset to 0. Intermittent error monitoring will then resume with the changed settings. If you set the automatic failback function to while intermittent error monitoring is , intermittent error monitoring will be disabled. Note, however, that if you use the operation to display the HDLM functionality view -sys...

  • Page 448

    6. Command Reference Setting Available operation Result of operation Set IEM to • IEM is disabled. • The error count, elapsed monitoring time, and information about paths not subject to automatic failbacks are cleared. Set AFB to The operations of AFB and IEM do not change. Change the AFB setting.

  • Page 449

    6. Command Reference -lic Specify this option for when a license is updated. The HDLM license is provided via a license key or license key file. A license key file is a file that stores the HDLM license key. If a license key file is provided: Store the license key file named directly under hdlm_license...

  • Page 450

    6. Command Reference 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: # /opt/DynamicLinkManager/bin/dlnkmgr set -lic KAPL01049-I Would you like to execute the operation? Operation name = set [y/n]: y...

  • Page 451

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

  • Page 452

    6. Command Reference for load balancing. You can specify a decimal (base 10) value from . The default is 999999 If you specify , operation is the same as when load balancing is disabled. Executes the command without displaying the message asking for confirmation of command execution from the user.

  • Page 453

    6. Command Reference [ -intvl Error-Monitor-Interval ] [ -iemnum Number-Of-Times ] | -iem | -lic | -audlog on [ -audlv AudlogLevel ] [ -category Category-Value ] | -audlog off | -audfac { Facility-Name | Facility-Number } | -lbpathusetimes Number-Of-PathUseTimes [-s] Valid value ElogLevel { 0 | 1 | 2 | 3 | 4 } (Default Value 3)

  • Page 454

    6. Command Reference Facility-Name { user | local0 - local7 } (Default Value user) Facility-Number { 1 | 16 - 23 } (Default Value 1) Number-Of-PathUseTimes { 0 - 999999 }(Times) (Default Value 32) KAPL01001-I The HDLM command completed normally. Operation name = set, completion time = yyyy/mm/dd hh:mm:ss...

  • Page 455: View (displays Information), Format, View (displays Information)

    6. Command Reference 6.7 view (Displays Information) command's operation displays HDLM program information, path dlnkmgr view information, LU information, and corresponding information about an HDLM device, SCSI device, and LDEV. 6.7.1 Format (1) To Display Program Information /opt/DynamicLinkManager/bin/dlnkmgr view -sys [-sfunc|-msrv|-adrv|-pdrv|-lic|-audlog|-lbpathusetimes] [-t] (2) To Display Path Information...

  • Page 456: Parameters (to Display Program Information)

    6. Command Reference [-srt {lu|cp}] [-t] (3) To Display LU Information To display LU information /opt/DynamicLinkManager/bin/dlnkmgr view -lu host-device-name AutoPATH_ID [-hdev |-pathid [-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 ] host-device-name AutoPATH_ID...

  • Page 457

    6. Command Reference (5) To display the format of the view operation (1) To display program information -sys [-sfunc|-msrv|-adrv|-pdrv|-lic|-audlog|-lbpathusetimes] Displays the HDLM program information. Use one of the sub-parameters (following ) to specify the program -sys information that you want to display. If you do not specify a sub-parameter, the command displays all of the program information except the information about the audit log data collection settings and the number of times the same path can be used for load balancing.

  • Page 458

    6. Command Reference Parameter and Item Description program information to be displayed Blank Support Cluster Error logging level: Elog Level • : Collects no error information. • : Collects error information at the Error level or higher. • : Collects error information at the Warning level or higher. •...

  • Page 459

    6. Command Reference Parameter and Item Description program information to be displayed Blank Reservation Status • Setting for intermittent error monitoring: Intermittent : Enabled Error Monitor : Disabled When automatic failback is , intermittent error monitoring is disabled although Intermittent Error will be shown as .

  • Page 460

    6. Command Reference Parameter and Item Description program information to be displayed License type -lic License Type • Information about the Permanent HDLM license • Temporary • Emergency License expiration: Expiration When using a permanent license: - When using a temporary license or emergency license: The license expiration period is displayed in the format: yyyy/mm/ .

  • Page 461

    6. Command Reference When you use cluster software, the settings of the cluster function and the kinds of cluster servers are not displayed. However, the cluster function will operate normally. Examples Example 1 The following example shows how to display information about the HDLM function settings.: # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -sfunc x.x.x-xx...

  • Page 462

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

  • Page 463

    6. Command Reference -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 (2) To display path information When displaying path information, if you specify either the parameter -item and also specify the...

  • Page 464

    6. Command Reference Table 6-14: Product ID displayed by the view -path operation. -iem Use this parameter to add 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.

  • Page 465

    6. Command Reference When you specify the parameter together with the parameter, the -path -item command only displays the items specified by the value of the parameter. -item When the value of the parameter is omitted, only the and the -item PathID fields are displayed.

  • Page 466

    6. Command Reference information for all the paths in ascending order of AutoPATH_IDs. These sub-parameters are: host-device-name -hdev Displays information only for the paths accessing the specified host device. Specify the name of the logical device file (minus the partition number), [aa-pap], for the HDLM device.

  • Page 467

    6. Command Reference Omits the title for each information item. Example In the following example, is selected as the display item and the IO-Count path information is sorted in ascending order of the by LUs. To display path information, by abbreviating the list items -path -c When you specify the parameter together with the...

  • Page 468

    6. Command Reference When you use the parameter, the number of characters that can be displayed in the product ID element of the field is limited to 10. When there are DskName 11 or more characters in the product ID, the 8th and following characters are abbreviated to ellipses ( The sub-parameters (following ) are:...

  • Page 469

    6. Command Reference Items of Path information Table 6-12: Path Information describes the displayed path information. The following explains the table headings: • No summary displayed: The user specifies only the parameter or the -path parameter. -path -item • Summary displayed: The user specifies the parameter.

  • Page 470

    6. Command Reference Displayed Item Description Summary summary displayed displayed Status of the displayed paths. The displayed status indicates the following: PathStatus • : All paths are available. Online • : Some paths are not available. Reduced means that some paths might have an error status, in which case you Reduced should check the status of individual paths and resolve the problem for any paths that have an error status.

  • Page 471

    6. Command Reference Displayed Item Description Summary summary displayed displayed LU number of the storage system. This number combined with the storage system name (shown in DskName identifies the LU that is accessed by a path. • For Lightning 9900 series, Lightning 9900V series, Hitachi NSC55, Hitachi Universal Storage Platform 100, Hitachi Universal Storage Platform 600, and Hitachi Universal Storage Platform 1100, indicated by a hexadecimal number.

  • Page 472

    6. Command Reference Displayed Item Description Summary summary displayed displayed Total I/O count for the path, indicated by a decimal number. The maximum value IO-Count that can be displayed is 2 - 1 (4294967295). If the total I/O count reaches the maximum value, it will re-start from 0.

  • Page 473

    6. Command Reference Legend: - : Not displayed The path information is displayed only when a value is specified for the -path parameter. -item Table 6-13: Elements of a path name Element Linux representation Host port number (example: 0000) Host ID (host port number) Bus number (example: 0000) Channel number (bus number) Target ID (example: 000000000000003A)

  • Page 474

    6. Command Reference Model names of storage Product ID systems Without the -stname parameter With the -stname parameter (Displays the following for the model name) Lightning 9900 series 9910/9960 Emulation type Lightning 9900V series 9970/9980 • Hitachi NSC55 • Hitachi Universal Storage Platform 100 •...

  • Page 475

    6. Command Reference parameter and the LU information and displayed items. To display LU information When neither the parameter is specified with the parameter, -item the information about the LU recognized by HDLM is displayed without selecting items to be displayed or displaying a summary. The sorting key is iLU and its configuration information is displayed for each LU.

  • Page 476

    6. Command Reference /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...

  • Page 477

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

  • Page 478

    6. Command Reference To display a summary of LU information -lu -c When the parameter is specified with the parameter, a summary of LU configuration information is displayed on one line. The total number of paths recognized by HDLM and the number of online paths are displayed for each LU. You cannot specify the parameter together with the -hdev...

  • Page 479

    6. Command Reference To display a summary of LU information (by selecting items to be displayed) -lu -c -item The items displayed when the option is added to the options. -item -lu -c When the value of the parameter is omitted, all the items that can be -item displayed are displayed.

  • Page 480

    6. Command Reference • Summary displayed: The user specifies the parameter or -lu -c -lu -c -item parameter. Table 6-17: LU Information Displayed item Description No summary Summary displayed displayed Model ID of the storage system Product Serial number of the storage system SerialNumber Total number of LUs managed by HDLM among the LUs in the storage system...

  • Page 481

    6. Command Reference Displayed item Description No summary Summary displayed displayed SCSI device associated with an HDLM device. If the SCSI device Device is not connected when a host starts, or the assigned LU is released, this column displays a hyphen (-). This problem might also occur when the OS is SUSE LINUX Enterprise Server 11 and one of the following problems occurs while the system is running:...

  • Page 482

    6. Command Reference Displayed item Description No summary Summary displayed displayed Status of the path Status : Online Online : Offline status caused by a command operation Offline(C) : Offline due to an error Offline(E) : Failure has occurred (If none of the paths accessing Online(E) one Dev have an status, one of those paths is changed to...

  • Page 483

    6. Command Reference Displayed item Description No summary Summary displayed displayed The displayed paths are assumed to be in an intermittent error status and checked whether those paths are to be operated for automatic failbacks. One of the following values is displayed for each path: •...

  • Page 484

    6. Command Reference - No value was specified for the parameter. (4) To display corresponding information about an HDLM device, SCSI device, and LDEV -drv 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).

  • Page 485

    6. Command Reference To display corresponding information about an HDLM device, SCSI device, and LDEV # /opt/DynamicLinkManager/bin/dlnkmgr view -drv PathID HDevName Device LDEV 000000 sddlmaa /dev/sdag 9970/9980.15001.05B7 000001 sddlmaa /dev/sdq 9970/9980.15001.05B7 000002 sddlmab /dev/sdr 9970/9980.15001.05B0 000003 sddlmac /dev/sds 9970/9980.15001.05B1 000004 sddlmad 9970/9980.15001.05B2 000005 sddlmae /dev/sdu...

  • Page 486

    6. Command Reference dlnkmgr view -lu [ -hdev HostDeviceName | -pathid AutoPATH_ID ] [-t] dlnkmgr view -lu -item [ [slpr] [pn] [cp] [clpr] [type] [ic] [ie] [dnu] [iep] [hctl] | all ] [ -hdev HostDeviceName | -pathid AutoPATH_ID ] [-t] dlnkmgr view -lu -c [-t] dlnkmgr view -lu -c -item [slpr] [-t] dlnkmgr view -drv [-t]...

  • Page 487: Utility Reference

    Chapter 7. Utility Reference This chapter explains the utilities used by HDLM. 7.1 Overview of the Utilities 7.2 DLMgetras Utility for Collecting HDLM Error Information 7.3 dlmcfgmgr Utility for Managing the HDLM Configuration 7.4 dlmmkinitrd Utility for Supporting a Boot Disk 7.5 dlmpr Utility for Clearing HDLM Persistent Reservation 7.6 dlmsetopt Utility for Setting HDLM Driver Options 7.7 dlmstart Utility for Starting HDLM...

  • Page 488: Overview Of The Utilities

    7. Utility Reference 7.1 Overview of the Utilities HDLM provides the following utilities: • The utility for collecting HDLM error information DLMgetras 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 utility, see 7.2 DLMgetras Utility for Collecting HDLM Error DLMgetras Information.

  • Page 489

    7. Utility Reference For details, see 7.7 dlmstart Utility for Starting HDLM. • The utility for collecting HDLM installation error information installgetras If an error occurred during installation, this utility collects files that contain information to be submitted to your HDLM vendor or maintenance company. For details on the utility, see 7.9 installgetras Utility for Collecting installgetras...

  • Page 490: Dlmgetras Utility For Collecting Hdlm Error Information, Format, Parameters

    7. Utility Reference 7.2 DLMgetras Utility for Collecting HDLM Error Information This utility collects information that is needed to analyze HDLM errors that have occurred, such as error logs, process-specific-trace information files, trace files, definition files, core files, and libraries. The collected information is archived in a file and saved to the directory that you specified.

  • Page 491

    7. Utility Reference Specify the output directory for the information that is to be collected by the utility for collecting HDLM error information. The collected DLMgetras information is compiled into the three files shown in Function and output in the specified directory.

  • Page 492: List Of Collected Error Information

    7. Utility Reference • The root directory ( ) cannot be specified. • When a directory is specified, the utility collects all the DLMgetras files in that directory, including files contained in the directory's subdirectories. If no files are found in a specified directory, the utility does not perform file collection for that directory and does not create a directory for it in the destination directory.

  • Page 493

    7. Utility Reference file, which is recorded by the OS and cluster commands when cluster.tar.gz utility is executed. DLMgetras • hbsa.tar.gz This file contains compressed error information of the Hitachi Command Suite products other than HDLM. This file is output only when using a Hitachi Command Suite product that is the target for collecting error information.

  • Page 494

    7. Utility Reference Files Explanation Output directory Heart Beat log file (when /var/log ha-log using SUSE LINUX Enterprise Server) 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 file.

  • Page 495

    7. Utility Reference Executed command Files Explanation VCS group status information /opt/VRTSvcs/bin/hagrp -state VCS_hagrp-state.txt VCS resource information /opt/VRTSvcs/bin/hares -display VCS_hares-display.txt VCS resource dependent /opt/VRTSvcs/bin/hares -dep VCS_hares-dep.txt information VCS resource status information /opt/VRTSvcs/bin/hares -state VCS_hares-state.txt VCS cluster status information /opt/VRTSvcs/bin/hastatus VCS_hastatus-summary.tx -summary VCS node information /opt/VRTSvcs/bin/hasys -display...

  • Page 496

    7. Utility Reference Table 7-3: Information Stored in the getras.tar.gz File Files Explanation Output directory The output destination directory utility log file getras.log DLMgetras specified when the DLMgetras utility is executed Boot loader configuration file (when using /boot/efi/efi/redhat elilo.conf Red Hat Enterprise Linux AS4/ES4(IPF) or Red Hat Enterprise Linux 5(IPF)) Boot loader configuration file (when using /boot/efi/efi/SuSE...

  • Page 497

    7. Utility Reference Files Explanation Output directory Load module information file(when using modprobe.conf.local SUSE LINUX Enterprise Server) Mount information mtab QLogic driver settings file qla*.conf md device configuration file raidtab Character-type device information (when using SUSE LINUX Enterprise Server) Start-up initialization script (when using Red rc.sysinit Hat Enterprise Linux) syslogd settings file (when using Red Hat...

  • Page 498

    7. Utility Reference Files Explanation Output directory All files Load module information file (when using /etc/modprobe.d Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 6) Oracle Cluster File System 2 settings file /etc/ocfs2 cluster.conf Audit log settings file /etc/opt/ auditlog.dat DynamicLinkManager...

  • Page 499

    7. Utility Reference Files Explanation Output directory Kernel configuration file (when using SUSE kernel LINUX Enterprise Server) Boot LVM information file (when using SUSE LINUX Enterprise Server) Character-type device information (when rawdevices using Red Hat Enterprise Linux AS4/ES4) SCSI device settings file (when using SUSE scsidev LINUX Enterprise Server) sysrq information file (when using SUSE...

  • Page 500

    7. Utility Reference Files Explanation Output directory All subdirectories and Domain-related files (when using SUSE /etc/xen/vm files LINUX Enterprise Server 10 or SUSE LINUX Enterprise Server 11) kernel-name Module dependency information /lib/modules/ modules.dep Parameter information for kernel startup /proc cmdline Kernel configuration information (when using config.gz SUSE LINUX Enterprise Server)

  • Page 501

    7. Utility Reference Files Explanation Output directory Statistics stat SWAP information swaps System's operating time information uptime Kernel version information version All subdirectories and IRQ information /proc/irq files All subdirectories and Network device information /proc/net files All subdirectories and SCSI device information /proc/scsi files All subdirectories and...

  • Page 502

    7. Utility Reference Files Explanation Output directory KVM-related log file (when using Red Hat /tmp qemu.log Enterprise Linux 5 or Red Hat Enterprise Linux 6) DHCP network information /var/lib/dhclient dhclient* Pacemaker settings file /var/lib/heartbeat/crm cib.xml All subdirectories and domain-related files (when using SUSE /var/lib/xend files LINUX Enterprise Server 10 or SUSE LINUX...

  • Page 503

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

  • Page 504

    7. Utility Reference directory is collected. The value N depends on the setting in the file. The dlmwebagent.properties default is 2. 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...

  • Page 505

    7. Utility Reference Executed command Files Explanation List of script files /bin/ls -altRZ /etc/rc.d rc_security.txt containing security context information (when using Red Hat Enterprise Linux) List of files containing /bin/ls -altRZ /opt/DynamicLinkManager DLMfilelist_securi security context ty.txt information in the /opt/ DynamicLinkManager directory (when using Red Hat Enterprise...

  • Page 506

    7. Utility Reference Executed command Files Explanation OpenAIS status /etc/init.d/openais status openais-status.txt information Trace information of /opt/DynamicLinkManager/bin/dlmgetomtrace dlmgetomtrace.dmp HDLM functions Persistent reservation /opt/DynamicLinkManager/bin/dlmpr -k dlmpr-k.txt information HDLM LU information /opt/DynamicLinkManager/bin/dlnkmgr view dlmmgr-lu.txt -lu -item slpr pn cp clpr type ic ie dnu hctl HDLM LU information /opt/DynamicLinkManager/bin/dlnkmgr view...

  • Page 507

    7. Utility Reference Executed command Files Explanation HDLM program /opt/DynamicLinkManager/bin/dlnkmgr view dlmmgr-sys.txt information -sys, /opt/DynamicLinkManager/bin/dlnkmgr view -sys -sfunc, /opt/DynamicLinkManager/bin/dlnkmgr view -sys -msrv, /opt/DynamicLinkManager/bin/dlnkmgr view -sys -adrv, /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...

  • Page 508

    7. Utility Reference Executed command Files Explanation Label information (all the /sbin/e2label e2label.txt SCSI device names and the corresponding label names are displayed in each line. If there is not a label, the hyphen (-) is displayed instead. If a Linux file system other than the ext file system is used, a label name is not...

  • Page 509

    7. Utility Reference Executed command Files Explanation Logical volume /sbin/lvs lvs.txt information (when using Red Hat Enterprise Linux 6 or SUSE LINUX Enterprise Server) Oracle Cluster File /sbin/o2cb_ctl -V o2cb_ctl-V.txt System 2 version HDLM-device HDLM device partition /sbin/parted -s print parted-s.txt information (when using Red Hat Enterprise Linux...

  • Page 510

    7. Utility Reference Executed command Files Explanation Limit values of the ulimit -a ulimit-a.txt available system resources (data segment, stack segment, and file descriptor) for the process Environment variables /usr/bin/env env.txt information Memory information /usr/bin/free free.txt Memory page size /usr/bin/getconf PAGESIZE getconfPAGESIZE.tx information Program build number...

  • Page 511

    7. Utility Reference Executed command Files Explanation Character-type device /usr/sbin/raw -qa raw-qa.txt information (when using SUSE LINUX Enterprise Server 9 or SUSE LINUX Enterprise Server System's operating time /usr/bin/uptime uptime.txt information database /usr/bin/udevinfo -d udevinfo-d.txt udev information (when using Red Hat Enterprise Linux AS4/ES4, Red Hat Enterprise Linux 5, SUSE LINUX Enterprise...

  • Page 512

    7. Utility Reference Executed command Files Explanation lvm disk information /usr/sbin/lvmdiskscan lvmdiskscan.txt (when using Red Hat Enterprise Linux AS4/ ES4 or Red Hat Enterprise Linux 5) Logical volume /usr/sbin/lvs lvs.txt information (when using Red Hat Enterprise Linux AS4/ES4 or Red Hat Enterprise Linux 5) Physical volume /usr/sbin/pvs...

  • Page 513: Dlmcfgmgr Utility For Managing The Hdlm Configuration, Format, Parameters

    7. Utility Reference 7.3 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 514

    7. Utility Reference Parameter Functionality Changes the size of the dlmcfgmgr utility log file ( -logfs dlmcfgmgr[1-2].log Specify this parameter when you do not want to display the confirmation messages during execution of the utility. When you execute this dlmcfgmgr utility with this parameter specified, the confirmation message for each HDLM device is not displayed.

  • Page 515

    7. Utility Reference Status before executing the dlmcfgmgr utility Status after executing the dlmcfgmgr utility (dlmcfgmgr -r) (dlmcfgmgr -r) /dev/sddlmaa /dev/sddlmaa /dev/sddlmab /dev/sddlmaa /dev/sddlmaa /dev/sddlmab /dev/sddlmab /dev/sddlmac /dev/sddlmaa /dev/sddlmaa /dev/sddlmac /dev/sddlmab /dev/sddlmac /dev/sddlmab /dev/sddlmaa /dev/sddlmac /dev/sddlmab /dev/sddlmac /dev/sddlmaa /dev/sddlmaa /dev/sddlmpp /dev/sddlmpp /dev/sddlmaaa /dev/sddlmaa...

  • Page 516

    7. Utility Reference HDLM device that is not managed by HDLM, that HDLM device will not be managed by HDLM. logical-device-file-name-of-the-HDLM-device -o { ...|all} Use this parameter to exclude the management-target HDLM device from being managed. You can specify one or more logical device file names of an HDLM device ( aa-pap ) as a parameter value.

  • Page 517

    7. Utility Reference immediately after execution of the utility. You can use this parameter to reset an HDLM device that must be managed again to a management target. The HDLM devices reset to a management target are displayed with the command's operation, and the HDLM device dlnkmgr...

  • Page 518

    7. Utility Reference time once it is recognized. Even if the recognized HDLM device is not available because this path is disconnected or the LU is deallocated, the path information for the unavailable HDLM device will not be deleted automatically. Because the unused HDLM device path information is preserved, newly defined LUs and added paths cannot be used in some cases.

  • Page 519

    7. Utility Reference To exclude the HDLM device from being managed without confirming sddlmaa 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 to execute the utility and to execute the utility.

  • Page 520: Log File

    7. Utility Reference 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 absolute path. This is HDevName indicated only for the first path for the relevant LU. Indicates the current management status of the HDLM device.

  • Page 521

    7. Utility Reference #dlmcfgmgr -logfs KAPL10938-I dlmcfgmgr Log File Size(KB) : 10240 Reference information If you do not specify a parameter, the syntax of the utility is displayed. dlmcfgmgr # /sbin/dlmcfgmgr KAPL10319-W usage: /sbin/dlmcfgmgr [-s] { -r | -o {special-file-name ... | all} | -i {special-file-name ...

  • Page 522

    7. Utility Reference device is executed. For example, when this utility executes an operation specified with the parameter for , and /dev/sddlmaa /dev/sddlmab /dev/ , the confirmation message KAPL10339-I is not displayed for the sddlmac processing of each device. This message is displayed once at the beginning of the operation.

  • Page 523

    7. Utility Reference cannot be used might increase. Update the HDLM device with information about unavailable SCSI devices by executing the utility with the parameter specified. dlmcfgmgr Delete the HDLM device by executing the utility with dlmcfgmgr specified in the parameter.

  • Page 524: Dlmmkinitrd Utility For Supporting A Boot Disk, Format, Parameters

    7. Utility Reference 7.4 dlmmkinitrd Utility for Supporting a Boot Disk This utility creates an initial RAM disk image file for using an HDLM device as a boot disk. 7.4.1 Format (1) For Red Hat Enterprise Linux /opt/DynamicLinkManager/bin/dlmmkinitrd [-v] [-f] fstab-name [-fstab initrd-image...

  • Page 525

    7. Utility Reference kernel-version Specify the kernel used for creating an initial RAM disk image file. Example The following shows an execution example for Red Hat Enterprise Linux 5: /opt/DynamicLinkManager/bin/dlmmkinitrd /boot/initrd- 2.6.18-194.el5-hdlm.img `uname -r` (2) For SUSE LINUX Enterprise Server 10 or SUSE LINUX Enterprise Server 11 When creating an initial RAM disk image file, you can do so without specifying the image file name and the path for the file to be created, or you can specify these parameters.

  • Page 526

    7. Utility Reference parameter. boot-directory Specify the path for the location in which the initial RAM disk image file is to be created. This parameter is used to create an initial RAM disk image file in a directory other than the default directory ( /boot Displays the format of the utility.

  • Page 527: Dlmpr Utility For Clearing Hdlm Persistent Reservation, Format, Parameters

    7. Utility Reference 7.5 dlmpr Utility for Clearing HDLM Persistent Reservation If the persistent reservation of the LU is not canceled for some reason, this utility clears the reservation key to cancel the persistent reservation. This utility can be used when the host OS is Red Hat Enterprise Linux 6. 7.5.1 Format /opt/DynamicLinkManager/bin/dlmpr {{-k | -c} [sd ] [sd...

  • Page 528

    7. Utility Reference Example To check the reservation keys, and then clear a reservation key: Execute the utility to display the reservation keys for dlmpr , and # /opt/DynamicLinkManager/bin/dlmpr -k sda sdb sdc sdd sde Reservation Key : [0xaaaaaaaaaaaaaaaa] Regist Key : [0xaaaaaaaaaaaaaaaa], Key Count : 1 Reservation Key : [0xbbbbbbbbbbbbbbbb] Regist Key : [0xaaaaaaaaaaaaaaaa], Key Count : 2 Regist Key : [0xbbbbbbbbbbbbbbbb], Key Count : 2...

  • Page 529

    7. Utility Reference - A persistent reservation has been set by the cluster software. Operation 1. Clear persistent reservation, specifying the SCSI device. 2. Execute the utility with the parameter specified to display the dlmpr PersistentReserve information for a SCSI device associated with a different path.

  • Page 530: Dlmsetopt Utility For Setting Hdlm Driver Options, Format, Parameters

    7. Utility Reference 7.6 dlmsetopt Utility for Setting HDLM Driver Options This utility changes the settings for the HDLM filter driver. Restart the host machine to apply the changed settings. Note that you do not need to restart the host machine every time you execute the utility.

  • Page 531

    7. Utility Reference command executed from another application. InquiryTimeout Specify a numeric value of -1 or in the range from 1 to 3,600. -1: This sets the timeout value to 30 seconds, which is HDLM's default value. 1 to 3,600: Timeout value (in seconds) If the following values are specified, the message KAPL12553-W is displayed and then the processing ends: •...

  • Page 532

    7. Utility Reference # /opt/DynamicLinkManager/bin/dlmsetopt -r 100000 KAPL12554-I The utility for setting HDLM driver option has started. KAPL12555-I The utility for setting HDLM driver option completed normally. KAPL12558-I Please restart the computer so that the option settings take effect. Example 2: In this example, the utility displays Help: Notes: •...

  • Page 533

    7. Utility Reference Table 7-9: Setting file names for boot loaders Boot loader File Name LILO /etc/lilo.conf GRUB For Red Hat Enterprise Linux /etc/grub.conf For SUSE LINUX Enterprise Server 10 or SUSE /boot/grub/menu.lst LINUX Enterprise Server 11 ELILO /etc/elilo.conf...

  • Page 534: Dlmstart Utility For Starting Hdlm, Format

    7. Utility Reference 7.7 dlmstart Utility for Starting HDLM You must perform the following operations after installing HDLM: • Load an HDLM alert driver and a filter driver. • Configure an HDLM device. • Start the HDLM manager. utility performs the above operations as a batch operation. dlmstart If an HDLM alert driver and a filter driver have already been loaded or the HDLM manager is already running, the relevant operation is not performed.

  • Page 535: Dlmupdatesysinit Utility For Updating System Scripts, Format

    7. Utility Reference 7.8 dlmupdatesysinit Utility for Updating System Scripts In an environment that uses Red Hat Enterprise Linux, if you update the package after installing HDLM, HDLM information in the initscripts /etc/ file. rc.d/rc.sysinit In an environment that uses SUSE LINUX Enterprise Server, if you update the , or package after installing HDLM, HDLM aaa_base...

  • Page 536: Installgetras Utility For Collecting Hdlm Installation Error Information, Format, Parameters, Error Information To Be Collected

    7. Utility Reference 7.9 installgetras Utility for Collecting HDLM Installation Error Information This utility collects the error log information needed to analyze errors that occurred during HDLM installation. The collected information is compiled in a file and output to a specified directory. The following file is output: •...

  • Page 537

    7. Utility Reference File Description Output directory All subdirectories and files Log information created /var/tmp/hdlminstlog during HDLM installation This directory is created in directory-to-which-collected-information-is-output specified when the utility was executed. installgetras...

  • Page 538: Installhdlm Utility For Installing Hdlm, Format, Parameters, Editing An Installation-information Settings File

    7. Utility Reference 7.10 installhdlm Utility for Installing HDLM You can use this utility to perform a new installation, upgrade installation, or re-installation of HDLM. The utility can also be used to perform an unattended installation. An unattended installation enables a user to install HDLM without entering information. Before you perform an unattended installation, you must define the information required for installation in the installation-information settings file.

  • Page 539

    7. Utility Reference KAPL09228-W message is output. (2) Items To Be Defined in an Installation-Information Settings File The following describes the information defined in the installation information settings file. [INSTALLATION_SETTINGS] section This section defines information that is used when the utility is installhdlm executed.

  • Page 540

    7. Utility Reference Key name Description Necessity of definition Maxim Upgrade numbe installatio installatio r of n or charac re-install ters ation Specify whether to restart the host after Optional Optional restart installation. Specify either of the following values: : Restart. : Do not restart (default).

  • Page 541

    7. Utility Reference [ENVIRONMENT_SETTINGS] section This section defines HDLM operation information. If this section is omitted, the installer will use the following values: • For a new installation, the installer uses the default values of the keys that are listed in the following Table 7-12: Keys in the [ENVIRONMENT_SETTINGS] Section.

  • Page 542

    7. Utility Reference Necessity of Maxim Key name Description definition numbe Upgrad r of installat charac installat ters ion or re-insta llation Set the level of error information that is Optional Optional error_log_level collected as error logs. You can set a level from .

  • Page 543

    7. Utility Reference Necessity of Maxim Key name Description definition numbe Upgrad r of installat charac installat ters ion or re-insta llation Specify one of the following values to Optional Optional auto_failback indicate whether to enable or disable the automatic failback function for failed paths: : Enabled (default) : Disabled Specify the interval in minutes from the time...

  • Page 544

    7. Utility Reference You can specify this key only in the following cases: • For a new installation: When is specified for the key in the installation auto_failback information settings file • For an upgrade installation or re-installation: When is specified for the key in the installation auto_failback information settings file, or when automatic failback is enabled in the...

  • Page 545: Installux.sh Utility For Hdlm Common Installer, Format, Parameters, Log File

    7. Utility Reference 7.11 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. For details about how to use this utility to install HDLM, see 3.6 Installing HDLM.

  • Page 547: Messages

    Chapter 8. Messages This chapter describes the format and meaning of the message IDs, and also the terms used in the messages and message explanations. For details on the meaning of the return codes output by HDLM when it receives a request from Global Link Manager and measures to take for them, see 8.15 Return Codes for Hitachi Command Suite Common Agent Component.

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

    8. Messages 8.1 Before Viewing the List of Messages This section explains the following information that is needed to locate messages and understand the explanations in the sections from 8.2 KAPL01001 to KAPL02000. • Format and meaning of the message IDs •...

  • Page 549

    8. Messages • HDLM driver (filter component) • HDLM alert driver • HDLM management target...

  • Page 550: Kapl01001 To Kapl02000, Kapl01001 To Kapl

    8. Messages 8.2 KAPL01001 to KAPL02000 KAPL01001-I The HDLM command completed normally. Operation name = aa...aa, completion time = bb...bb Details The HDLM command completed successfully. aa...aa: , or clear help offline online view bb...bb: Year/month/day hour:minute:second Action None. KAPL01002-I The HDLM command started.

  • Page 551

    8. Messages KAPL01005-W A parameter is invalid. Operation name = aa...aa, parameter = bb...bb Details aa...aa: , or clear online offline view bb...bb: Specified parameter Action Execute operation-name of the HDLM command ( ) to check the help dlnkmgr parameter, and then retry. For details on the operation, see 6.3 help help (Displays the Operation Format).

  • Page 552

    8. Messages Specify the parameter value, and then retry. KAPL01009-W A parameter value is invalid. Operation name = aa...aa, parameter = bb...bb, parameter value = cc...cc, Valid value = dd...dd Details aa...aa: , or offline online view bb...bb: Parameter name cc...cc: Specified parameter value dd...dd: Specifiable parameter value range Action...

  • Page 553

    8. Messages KAPL01014-W No authority to execute the HDLM command. Operation name = aa...aa Details You do not have the administrator permissions necessary to execute the HDLM command. aa...aa: , or clear offline online view Action Execute the command as a user with root permissions. KAPL01015-W The target HBA was not found.

  • Page 554

    8. Messages aa...aa: view Action Execute the view operation of the HDLM command ( dlnkmgr view -path and check the value displayed in PathName. Specify the two leftmost digits of PathName for the relevant HBA port, and then retry. For details on the view operation, see 6.7 view (Displays Information).

  • Page 555

    8. Messages Stop unnecessary applications, increase the amount of free memory, and then re-execute the HDLM command. KAPL01023-W The last Online path for the device cannot be placed Offline(C). Details The path specified for the offline operation cannot be set to Offline(C) because that is the last, available path to the LU from the host.

  • Page 556

    8. Messages To ignore this path and perform online processing for the next path, enter To cancel processing, enter aa...aa: Path ID (decimal (base-10) number) Action If you want to continue processing of the operation of the HDLM online command for other paths, enter .

  • Page 557

    8. Messages Details aa...aa: , or offline online view bb...bb: Parameter name cc...cc: Parameter value Action Execute operation-name of the HDLM command ( ) to check the help dlnkmgr parameter value, and then retry. For details on the operation, see 6.3 help help (Displays the Operation Format).

  • Page 558

    8. Messages Action If you want to execute processing, enter . If you want to terminate online processing, enter . For details on the operation, see 6.5 online (Places online Paths Online). KAPL01051-I Because no path has been selected among the currently displayed paths, the paths in the Offline(C), Offline(E), and Online(E) statuses will be changed to the Online status.

  • Page 559

    8. Messages processing, enter . For details on the operation, see 6.4 offline (Places offline Paths Offline). KAPL01054-W During the offline operation processing of the HDLM command, a path that cannot be placed in the Offline(C) status was detected. PathID = aa...aa Would you like to continue the processing of the offline operation? [y/n]: Details A path that cannot be set to Offline(C) was detected during multi-path offline...

  • Page 560

    8. Messages If you want to execute processing for the paths that meet the specified offline requirements, enter . If you want to terminate processing, enter KAPL01057-I All the paths which pass the specified aa...aa will be changed to the Online status. Is this OK? [y/n]: Details All multiple paths will place online status because the parameter...

  • Page 561

    8. Messages dd...dd: view Action Execute operation-name of the HDLM command ( ) to check the help dlnkmgr parameter and parameter value, and then retry. For details on the operation, help see 6.3 help (Displays the Operation Format). KAPL01060-I The user terminated the operation. Operation name = aa...aa Details Command processing will be aborted because was entered for a required...

  • Page 562

    8. Messages Action Use the operation of the HDLM command ( ) to check the status view dlnkmgr of the path. For details on the operation, see 6.7 view (Displays view Information). For details on the operation, see 6.5 online (Places Paths online Online).

  • Page 563

    8. Messages KAPL01072-I The emergency license was installed. The license expires on aa...aa. Details A license was renewed and is registered as an emergency license. aa...aa: Year (4 digits)/month (01-12)/day (01-31) Action Install a permanent license by the expiration day. KAPL01073-E The temporary license expired.

  • Page 564

    8. Messages None. KAPL01079-W The intermittent error monitoring function cannot be set up because automatic failback is disabled. Details The intermittent error monitoring function cannot be set up because automatic failbacks are disabled. Action Enable automatic failbacks, and then re-execute. KAPL01080-W The error monitoring interval and the number of times that the error is to occur conflict with the automatic failback checking...

  • Page 565

    8. Messages Action Make sure that the license key file is correct, and then re-execute. /var/tmp/hdlm_license KAPL01083-I There is no license key file. File name = aa...aa Details There is no license key file in the designated directory: aa...aa: /var/tmp/hdlm_license Action When the message that prompts you to enter the license key is displayed, enter the license key.

  • Page 566

    8. Messages KAPL01089-E One of the following was executed at the same time as an HDLM command set -lic operation: another set -lic operation, or an update of the license for an update installation. Action Check the license by using the HDLM command's operation.

  • Page 567

    8. Messages If you set a value that is less than the current value of the trace file size or number of trace files, all the current trace files will be deleted. To continue the operation, enter . To cancel the operation, enter Action If you want to execute the operation of the HDLM command, enter .

  • Page 568

    8. Messages aa...aa: , or clear offline online view Action 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 ( ) to collect the error DLMgetras...

  • Page 569

    8. Messages result, contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. KAPL01116-W The audit log configuration file is invalid. Restart the HDLM Manager, and execute the "dlnkmgr view -sys -audlog" command and check the setting. Details The audit log configuration file is invalid.

  • Page 570

    8. Messages contract for HDLM. KAPL01120-W A storage subsystem model ID could not be displayed. Details = aa...aa, bb...bb Details A storage system model ID could not be displayed. aa...aa: Storage recognition information bb...bb: Error code Action Execute the utility for collecting HDLM error information, and then DLMgetras contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.

  • Page 571

    8. Messages KAPL01125-E The directory does not exist. Directory name = aa...aa Details aa...aa: HDLM installation path, HDLM installation path /lib Action Reinstall HDLM. KAPL01126-E The execution file does not exist. File name = aa...aa Details aa...aa: HDLM installation path /bin/.dlnkmgr_exe Action Reinstall HDLM.

  • Page 572: Kapl03001 To Kapl04000, Kapl03001 To Kapl

    8. Messages 8.3 KAPL03001 to KAPL04000 KAPL03001-I HDLM API information - aa...aa Details This information is required for resolving problems. aa...aa: Trace information Action None. KAPL03003-E HDLM API Error information - aa...aa Details This information is required for resolving problems. aa...aa: API trace error information Action Execute the...

  • Page 573

    8. Messages aa...aa: API trace error information Action Execute the utility for collecting HDLM error information, and then DLMgetras contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the utility, see 7.2 DLMgetras DLMgetras Utility for Collecting HDLM Error Information.

  • Page 574

    8. Messages contract for HDLM. For details on the utility, see 7.2 DLMgetras DLMgetras Utility for Collecting HDLM Error Information.

  • Page 575: Kapl04001 To Kapl05000, Kapl04001 To Kapl

    8. Messages 8.4 KAPL04001 to KAPL05000 KAPL04001-I HDLM manager started. Action None. KAPL04002-E Could not start the HDLM manager. Details The HDLM manager failed to start because the current environment is unsuitable for the HDLM manager to run in. Action Execute the utility for collecting HDLM error information, and then DLMgetras...

  • Page 576

    8. Messages aa...aa: Option definition file name Action Check whether another program is currently using this file (for example, the file is being opened in a text editor), or whether the file has been inadvertently deleted. KAPL04009-E The option definition is invalid. Details HDLM manager could not start normally because some of the definitions in the option definition file were invalid.

  • Page 577

    8. Messages KAPL04012-E Could not create a communication pipe. RC = aa...aa Details HDLM manager could not start normally because it was unable to create a pipe file, which is used in communication with HDLM commands. aa...aa: OS error code(decimal (base-10) number) Action Execute the utility for collecting HDLM error information, and then...

  • Page 578

    8. Messages Details An attempt to read the log information from the alert driver failed. aa...aa: API return code (decimal (base-10) number) Action Execute the utility for collecting HDLM error information, and then DLMgetras contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.

  • Page 579

    8. Messages Utility for Collecting HDLM Error Information. KAPL04024-C A critical error occurred in the HDLM manager. (aa...aa) Details This information is required for resolving problems. aa...aa: HDLM manager trace error information Action Execute the utility for collecting HDLM error information, and then DLMgetras contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.

  • Page 580

    8. Messages Install a permanent license by the expiration day. KAPL04028-E The temporary license expired. Action Install a permanent license. KAPL04029-E The emergency license expired. Action Install a permanent license. KAPL04030-E The temporary license has already expired. Action Install a permanent license. KAPL04031-E The emergency license has already expired.

  • Page 581

    8. Messages KAPL04034-E An attempt to create the option definition file has failed. Details An attempt to re-create an option definition file ( /etc/opt/ ) using the default values has failed. DynamicLinkManager/dlmmgr.xml Action Remove unnecessary files to secure unused capacity on the file system, or check the write permissions for the directory and file.

  • Page 582

    8. Messages aa...aa: Trap ID bb...bb: Destination IP address of the trap cc...cc: Destination port number of the trap dd...dd: Community name given to the trap ee...ee: Transmission data Action None. KAPL04047-W The file does not exist. File name = aa...aa Details aa...aa: /etc/.DynamicLinkManager/Path00...

  • Page 583

    8. Messages Action Reinstall HDLM. KAPL04051-E The execution file does not exist. File name = aa...aa Details aa...aa: HDLM installation path /bin/.dlnkmgr_exe Action Reinstall HDLM. KAPL04052-E You do not have execute permission for the file. File name = aa...aa Details aa...aa: HDLM installation path /bin/.dlnkmgr_exe...

  • Page 584: Kapl05001 To Kapl06000, Kapl05001 To Kapl

    8. Messages 8.5 KAPL05001 to KAPL06000 KAPL05003-I The HDLM driver (filter component) was successfully attached to Disk (aa...aa), Partition (bb...bb). Details The path corresponding to disk aa...aa and partition bb...bb was successfully registered in the core logic. aa...aa: Disk sequence number (decimal number) bb...bb: Fixed at 0 (decimal number) Action None.

  • Page 585

    8. Messages The path corresponding to the disk aa...aa and partition bb...bb could not be registered in the core logic. aa...aa: Disk sequence number (decimal number) bb...bb: Partition number (decimal number) cc...cc: Error code (hexadecimal number) dd...dd: Filter driver management table address (hexadecimal number) Action Check whether the HDLM driver has started normally.

  • Page 586

    8. Messages of the path, execute the DLMgetras utility for collecting error information, and then contact the HDLM vendor or the maintenance company if you have a maintenance contract for HDLM. KAPL05019-I The FO processing in the path (aa...aa) finished. The I/O request was processed in the path (bb...bb).

  • Page 587

    8. Messages Details An attempt to process the requested IOCTL call has failed. aa...aa: IOCTL code (hexadecimal number) bb...bb: Error code (hexadecimal number) cc...cc: Thread ID of the process that issued the I/O Action Check the following. After the check, if the problem is not solved, execute the utility for collecting HDLM error information, and then contact your DLMgetras HDLM vendor or the maintenance company if there is a maintenance contract for...

  • Page 588

    8. Messages separated by period) aa...aa: Host ID (host port number) (decimal number) bb...bb: Channel number (bus number) (decimal number) cc...cc: Target ID (target ID) (decimal number) dd...dd: LUN (host LU number) (decimal number) Action Please perform the following steps. Note down the HCTL values of the SCSI device as shown in the error messages.

  • Page 589

    8. Messages Details aa...aa: Memory allocation retry count (decimal number) Action None. KAPL05711-I The timeout value and retry count of SCSI INQUIRY has been set. (timeout value = aa...aa, retry count = bb...bb) Details aa...aa: SCSI INQUIRY timeout value bb...bb: SCSI INQUIRY retry count Action None.

  • Page 590

    8. Messages dd...dd: Maintenance information (hexadecimal number) Action None.

  • Page 591: Kapl06001 To Kapl07000, Kapl06001 To Kapl

    8. Messages 8.6 KAPL06001 to KAPL07000 KAPL06004-E Could not allocate memory. (aa...aa:bb...bb) Details An attempt to reserve memory to save alert information has failed. aa...aa: Program line (hexadecimal number) bb...bb: Target memory size (hexadecimal number) Action Check whether the HDLM driver has started normally. If it has not started or contains an error, execute the utility for collecting HDLM error DLMgetras...

  • Page 592

    8. Messages aa...aa: IOCTL code (hexadecimal number) Action None. KAPL06010-E Could not process the IOCTL(aa...aa). (bb...bb:cc...cc) Details An IOCTL request was not processed normally. aa...aa: IOCTL code (hexadecimal number) bb...bb: Error number (hexadecimal number) cc...cc: 0 (fixed) Action Check the message of the HDLM command ( ) or HDLM manager, and dlnkmgr then take the appropriate action.

  • Page 593

    8. Messages Information. KAPL06014-E Could not write emergency information into the emergency information buffer. (aa...aa:bb...bb) Details Urgent information from the filter driver was destroyed without being written to the urgent information buffer because the attempt to reserve memory for the information failed.

  • Page 594

    8. Messages aa...aa: Name of file where error was detected. Action Reinstall an HDLM.

  • Page 595: Kapl07001 To Kapl08000, Kapl07001 To Kapl

    8. Messages 8.7 KAPL07001 to KAPL08000 KAPL07819-I Data for maintenance: aa...aa bb...bb cc...cc dd...dd. Details This message is generated by the core logic for maintenance. aa...aa: Detailed information 1 (decimal (base-10) number) bb...bb: Internal function number of the core logic (decimal (base-10) number) cc...cc: Detailed information 2 (decimal (base-10) number) dd...dd: Detailed information 3 (decimal (base-10) number) Action...

  • Page 596: Kapl08001 To Kapl09000, Kapl08001 To Kapl

    8. Messages 8.8 KAPL08001 to KAPL09000 KAPL08019-E The path (aa...aa) detected an error (bb...bb). (cc...cc) Details An error occurred in the path. The error is most likely due to a disconnected cable. aa...aa: Path identifier (hexadecimal number) bb...bb: Error code (hexadecimal number) •...

  • Page 597

    8. Messages ee...ee: Target ID (same as PathName of ) (hexadecimal number) view -path ff...ff: HLU number (same as PathName of ) (hexadecimal number) view -path gg...gg: Dev number (same as DNum of ) (decimal (base-10) view -path number) hh...hh: Host device name (same as HDevName of view -path Action There could be an error in the path.

  • Page 598

    8. Messages KAPL08027-E A path was excluded from the items subject to automatic failback. PathID = aa...aa Details A path was excluded from being subject to automatic failbacks because the system judged that an intermittent error was occurring in that path. aa...aa: Path ID (same as PathID of ) (decimal (base-10) number) view -path...

  • Page 599: Kapl09001 To Kapl10000, Kapl09001 To Kapl

    8. Messages 8.9 KAPL09001 to KAPL10000 KAPL09001-E There is no system management permission. Login with root permission and re-install HDLM. Details The current user does not have the necessary administrator permission to install HDLM. Action Login with root permission and re-install HDLM. KAPL09003-E Cannot install in this system.

  • Page 600

    8. Messages KAPL09013-E Some HDLM drivers could not be removed. Details Deleting several HDLM drivers failed because these HDLM drivers were being used for HDLM upgrade installation, re-installation, or uninstallation. Action Check whether an HDLM device is mounted. If an HDLM device has been mounted, unmount the device, and then remove the HDLM drivers again.

  • Page 601

    8. Messages maintenance contact of HDLM. KAPL09023-E A file or directory related to HDLM could not be found. Re-install HDLM. Details A target file to copy to the directory of Hitachi Command Suite products other than HDLM could not be found among the files related to HDLM. Action Re-install HDLM.

  • Page 602

    8. Messages KAPL09035-E The HDLM driver could not be loaded. Execute the dlmstart utility. For details on the dlmstart utility, refer to the HDLM User's Guide section "dlmstart (Utility for Starting HDLM)". Details The HDLM driver could not be loaded. Action Execute the utility.

  • Page 603

    8. Messages KAPL09039-E The HDLM devices could not be configured. Execute the HDLM-configuration definition utility (dlmcfgmgr) with the -r parameter specified. For details on the dlmcfgmgr utility, refer to the HDLM User's Guide section "dlmcfgmgr (HDLM-Configuration Definition Utility)". Details The HDLM devices could not be configured. Action Execute the HDLM-configuration definition utility ( ) with the...

  • Page 604

    8. Messages KAPL09045-E An attempt to create a file or directory related to HDLM has failed. Make sure that sufficient disk space exists, and then re-install HDLM. Details Installation could not be executed because an attempt to create an HDLM-related file or directory failed.

  • Page 605

    8. Messages KAPL09050-E The driver module dependencies could not be updated. Contact your HDLM vendor or the maintenance company if there is a maintenance contract of HDLM. Details Installation or uninstallation failed because the dependency information for a driver module could not be updated. Action Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM.

  • Page 606

    8. Messages KAPL09078-I The emergency license was installed. The license expires on aa...aa. Details An emergency license was installed. aa...aa: Year (4 digits)/month (01-12)/day (01-31) Action Install a permanent license by the expiration day. KAPL09079-I The permanent license has been installed. Action None.

  • Page 607

    8. Messages KAPL09083-W The emergency license expired. Action Install a permanent license. KAPL09087-E The entered license key is invalid. Renewal of the license key will now stop. Obtain a valid license key, and then re-install HDLM. Details License renewal will now stop because an invalid license key was entered. Action Obtain a valid license key, and then re-install HDLM.

  • Page 608

    8. Messages KAPL09092-I The installation was stopped because a stop request was received. Details The installation was aborted, because a stop request was received. Action Installation was terminated before all processing could be completed. If the HDLM RPM has been installed, then use the rpm command to perform uninstallation.

  • Page 609

    8. Messages Action None. KAPL09097-E A package installable on this system was not found. Please check whether HDLM is supported for this system. For details about installing the package on a supported OS, refer to the HDLM User's Guide section "Hosts and OSs Supported by HDLM". Details A suitable package for installation on this system could not be found.

  • Page 610

    8. Messages Details There is no license key file in the designated directory. aa...aa: /var/tmp/hdlm_license Action Save the correct license key file in the designated directory, and then re-execute installation. /var/tmp/hdlm_license KAPL09115-W An attempt to delete the license key file has failed. File name = aa...aa Details An attempt to delete the license key file has failed.

  • Page 611

    8. Messages 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 executed at the same time as an HDLM command set -lic operation: another set -lic operation, or an update of the license for an update installation.

  • Page 612

    8. Messages Details aa...aa: Referenced directory name Action Check the directory displayed in the message. Re-install HDLM after creating the directory displayed in the message. KAPL09147-E An attempt to create a file related to HDLM has failed. File name = aa...aa. Remove unnecessary files and secure free space on the file system.

  • Page 613

    8. Messages /media/cdrom • For SUSE LINUX Enterprise Server 9: /media/cdrom /media/cdrecorder /media/dvd /media/dvdrecorder /media/dvdram • For SUSE LINUX Enterprise Server 10 or SUSE LINUX Enterprise Server media-volume-ID /media/ Action Check the HDLM installation media, or check the current kernel. KAPL09177-I HDLM version: aa...aa Details...

  • Page 614

    8. Messages Linux 6 Kernels Supported by HDLM, Table 3-5: SUSE LINUX Enterprise Server 9 Kernels Supported by HDLM, Table 3-6: SUSE LINUX Enterprise Server 10 Kernels Supported by HDLM, Table 3-7: SUSE LINUX Enterprise Server 11 Kernels Supported by HDLM, Table 3-8: Oracle Enterprise Linux 4 Kernels Supported by HDLM, or Table 3-9: Oracle Enterprise Linux 5 Kernels Supported by HDLM.

  • Page 615

    8. Messages Details Although the aa...aa processing has ended, an error occurred during the processing. aa...aa: , or ENVIRONMENT_SETTINGS driver_config_settings installhdlm Action Review the contents of installation information settings file when KAPL01008-W or KAPL01009-W is outputted before this message. For details, see 7.10.3 Editing an Installation-Information Settings File.

  • Page 616

    8. Messages An error occurred during I/O of a file that uses. installhdlm aa...aa: Error number that indicates the executed processing (decimal (base-10) number) bb...bb: Return value of the executed processing (decimal (base-10) number) Action Make sure that sufficient unused capacity exists for the directory.

  • Page 617

    8. Messages permission, re-execute installhdlm If aa...aa is installhdlm_analysis The correct location of DVD-ROM installhdlm_analysis . Make sure that the utility you want to execute is in the HDLM_Linux/bin correct location and that you have the required permissions. If a utility is not in the correct location, copy the required files to the correct location, and then retry the operation.

  • Page 618

    8. Messages KAPL09221-W The definition of the installation information settings file includes an unusable character. Error Code = aa...aa,bb...bb, line = cc...cc Details A character that cannot be used in a non-comment line was used. 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.

  • Page 619

    8. Messages operation. KAPL09229-W The definition of the installation information settings file includes an invalid section name. Error Code = aa...aa,bb...bb, line = cc...cc Details A section that does not exist is included. aa...aa: Error number (decimal number) that specifies the executed processing bb...bb: Return value (decimal number) of the executed processing cc...cc: Line number (decimal number) of an installation information settings file.

  • Page 620

    8. Messages Specify the revised installation information settings file and then retry the operation. KAPL09232-W The composition of the definition of the installation information settings file is invalid. Error Code = aa...aa,bb...bb, line = cc...cc Details A key, key value, or equal sign ( ) is missing.

  • Page 621

    8. Messages operation. KAPL09238-W The specified file is not a normal one. Fail name = aa...aa Details A file other than a normal one (for example, a directory file or a special file.) is specified. aa...aa: Specified file name (character string) Action Specify the correct file, and then retry the operation.

  • Page 622

    8. Messages KAPL09245-E Could not delete file supporting driver update. Details Could not delete file supporting driver update. Action Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM. KAPL09267-W The file does not exist. File name = aa...aa Details aa...aa: /etc/.DynamicLinkManager/Path00...

  • Page 623

    8. Messages aa...aa: HDLM installation directory, HBsA installation directory Action Reinstall HDLM. KAPL09501-E HDLM is not installed on this system. Details An SP cannot be applied because HDLM is not installed on the system. Action Check whether HDLM has been correctly installed. KAPL09505-E aa...aa cannot be applied to the installed bb...bb.

  • Page 624

    8. Messages KAPL09510-E Service Pack aa...aa cannot be installed. A newer version has already been installed. Details A newer version is already installed. Installation of SP (aa...aa) is stopped. aa...aa: Version of SP to be installed Action You do not have to install the SP. Keep using the already installed HDLM. KAPL09511-E The RPM file for the service pack was not found.(directory = aa...aa)

  • Page 625

    8. Messages all of the DVD-ROM files. KAPL09603-E The installation will now stop because a command or utility cannot be executed. Confirm that the command or utility (aa...aa) exists, and that you have the proper permission. Details aa...aa: Name of the command or utility that cannot be executed. Action •...

  • Page 626: Kapl10001 To Kapl11000, Kapl10001 To Kapl

    8. Messages 8.10 KAPL10001 to KAPL11000 KAPL10001-W No parameter has been specified. Details No directory to which the collected information will be output has been specified. Action Check the parameters of the utility for collecting HDLM error DLMgetras information, and then retry. For details on the utility, see DLMgetras 7.2 DLMgetras Utility for Collecting HDLM Error Information.

  • Page 627

    8. Messages Action Check the parameters of the utility for collecting HDLM error DLMgetras information, and then retry. For details on the utility, see DLMgetras 7.2 DLMgetras Utility for Collecting HDLM Error Information. KAPL10005-W The number of parameters is insufficient. Details parameter exists but the file for defining the information to be collected does not exist.

  • Page 628

    8. Messages Details You do not have write permission for the specified directory, or the creation of a subdirectory of the specified directory failed. aa...aa: first parameter Action Check the following. Check whether you have access permission for the specified directory. Check whether the specified directory name is correct.

  • Page 629

    8. Messages Details Two or more file names or directory names exist in the file for defining the information to be collected. aa...aa: Line number of the file for defining information to be collected (decimal number) bb...bb: Indicated contents in a line Action After the utility for collecting HDLM error information terminates,...

  • Page 630

    8. Messages bb...bb: Indicated contents in a line Action After the utility for collecting HDLM error information terminates, DLMgetras check the contents of the file for defining the information to be collected. This file is shown in the message. If the contents of the file are incorrect, correct them and then try to collect error information again.

  • Page 631

    8. Messages Details The root directory has been specified in the first parameter. A root "/" cannot be specified in a directory to which collected information is output. Action Check the parameters of the utility for collecting HDLM error DLMgetras information, and then re-execute.

  • Page 632

    8. Messages KAPL10022-I The utility for collecting HDLM error information completed normally. Details Error information has been collected. Action None. For details on the utility, see 7.2 DLMgetras Utility for DLMgetras Collecting HDLM Error Information. KAPL10030-I A user terminated the utility for collecting HDLM error information.

  • Page 633

    8. Messages The file to collect does not exist. aa...aa: Name of file to collect Action None. KAPL10034-E The file could not be copied. Filename = aa...aa, Details = bb...bb Details Execution of the command failed. aa...aa: Name of the file you tried to copy bb...bb: command output message Action...

  • Page 634

    8. Messages the time of execution, and then contact your HDLM vendor or the maintenance company if you have a maintenance contract for HDLM. KAPL10037-W The file does not exist or does not have executable permissions. Filename = aa...aa Details There is no output file, or the user does not have execution permission.

  • Page 635

    8. Messages Managing the HDLM Configuration. KAPL10302-I /sbin/dlmcfgmgr completed normally. Details The HDLM-configuration definition utility ( ) has completed dlmcfgmgr successfully. Action None. For details on the utility, see 7.3 dlmcfgmgr Utility for dlmcfgmgr Managing the HDLM Configuration. KAPL10305-E A special file could not be created. Filename = aa...aa. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company.

  • Page 636

    8. Messages Details The configuration definition file ( /etc/opt/DynamicLinkManager/ ) could not be created. .dlmfdrv.conf Action Execute the utility for collecting HDLM error information, and then DLMgetras contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.

  • Page 637

    8. Messages aa...aa: Logical device file name of HDLM device Action None. KAPL10316-E Could not allocate memory. Size = aa...aa. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company. Details Securing of memory failed. aa...aa: Target memory size (decimal number) Action Execute the...

  • Page 638

    8. Messages | -u {special-file-name ... | all} |-logfs [log-file-size]} Details Since the parameter of the HDLM-configuration definition utility ( dlmcfgmgr was inaccurate, execution of the utility failed. For details on the dlmcfgmgr utility, see 7.3 dlmcfgmgr Utility for Managing the HDLM dlmcfgmgr Configuration.

  • Page 639

    8. Messages KAPL10322-E A file that defines HDLM-unmanaged disks could not be created. File name = aa...aa, Errno = bb...bb. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company. Details Execution of the HDLM-configuration definition utility ( ) failed dlmcfgmgr because an exclusion disk definition file (aa...aa) could not be created.

  • Page 640

    8. Messages None. KAPL10325-E A regular expression cannot be established. The files will not be deleted. Errno = aa...aa. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company. Details An HDLM device could not be deleted because the device could not be found by using a regular expression.

  • Page 641

    8. Messages KAPL10328-E The entered value is invalid. The HDLM-configuration definition utility processing will now stop. Execute the HDLM-configuration definition utility again. Details An invalid value was entered 3 or more times for the message confirming the execution of the HDLM-configuration definition utility ( dlmcfgmgr Processing is interrupted.

  • Page 642

    8. Messages Execute the utility for collecting HDLM error information, and then DLMgetras contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the utility, see 7.2 DLMgetras Utility for Collecting DLMgetras HDLM Error Information.

  • Page 643

    8. Messages information, and then contact your vendor or maintenance company. Details An internal error occurred during file operation. aa...aa: File name Action Execute the utility for collecting HDLM error information, and then DLMgetras contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.

  • Page 644

    8. Messages Execute the utility for collecting HDLM error information, and then DLMgetras contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the utility, see 7.2 DLMgetras Utility for Collecting DLMgetras HDLM Error Information.

  • Page 645

    8. Messages This message checks whether you want to change the configuration definition of an HDLM device. Action Enter to continue. Enter to cancel. KAPL10340-E Several processes failed. See the aa...aa file. Check the message output before this message. Details Some processes in the execution of the HDLM-configuration definition utility ) have failed.

  • Page 646

    8. Messages KAPL10344-I HDLM has detected and registered a new path to an already registered HDLM device. HDLM device = aa...aa, Device = bb...bb (Host: cc...cc Channel: 0 ID: dd...dd Lun: ee...ee) Details By executing the HDLM-configuration definition utility ( ), a newly dlmcfgmgr detected path has been added to the registered HDLM device.

  • Page 647

    8. Messages KAPL10346-I HDLM has unregistered an existing HDLM device. HDLM device = aa...aa Details By executing the HDLM-configuration definition utility ( ), the dlmcfgmgr registered HDLM device has been unregistered. aa...aa: Logical device file name of HDLM device Action None.

  • Page 648

    8. Messages aa...aa: Logical device file name of HDLM device Action None. For details on the utility, see 7.3 dlmcfgmgr Utility for dlmcfgmgr Managing the HDLM Configuration. KAPL10350-E The HDLM driver(s) is not loaded. Refer to the Messages section of the HDLM User's Guide for instructions to correct this problem.

  • Page 649

    8. Messages KAPL10352-W The HDLM device is in use. HDLM device = aa...aa. Stop the application using the HDLM device, unmount the HDLM device being mounted, and then execute the dlmcfgmgr utility again. Details An attempt to execute the HDLM-configuration definition utility ( dlmcfgmgr failed because the specified HDLM device (aa...aa) was using it.

  • Page 650

    8. Messages device, and re-execute the utility. For details on the dlmcfgmgr dlmcfgmgr utility, see 7.3 dlmcfgmgr Utility for Managing the HDLM Configuration. KAPL10355-E An attempt to unregister partition information for the HDLM device(s) failed. Stop the application using the HDLM device, and unmount the mounting HDLM device, and then execute the dlmcfgmgr utility again.

  • Page 651

    8. Messages (decimal number) Action Revise the configuration of the HDLM device to reduce the number of HDLM devices used, and then re-execute the utility. For details on the dlmcfgmgr utility, see 7.3 dlmcfgmgr Utility for Managing the HDLM dlmcfgmgr Configuration.

  • Page 652

    8. Messages aa...aa: HDLM device name bb...bb: SCSI device name cc...cc: Host ID (decimal number) Channel: Channel ID (fixed value: ) (decimal number) dd...dd: Target ID (decimal number) ee...ee: LUN (decimal number) Action None. For details on the utility, see 7.3 dlmcfgmgr Utility for dlmcfgmgr Managing the HDLM Configuration.

  • Page 653

    8. Messages bb...bb: SCSI device name cc...cc: Host ID (decimal number) Channel: Channel ID (fixed value: ) (decimal number) dd...dd: Target ID (decimal number) ee...ee: LUN (decimal number) Action Stop the application that uses the HDLM device, unmount the HDLM device being mounted, and then re-execute the utility.

  • Page 654

    8. Messages KAPL10365-W The LDEV for an HDLM device has changed. The processing for that HDLM device will be cancelled. HDLM device = aa...aa. Execute the HDLM-configuration definition utility (dlmcfgmgr) with the -v option, and then check the configuration of the HDLM device. Details The processing for the HDLM device was interrupted because an LDEV corresponding to an HDLM device was changed.

  • Page 655

    8. Messages KAPL10643-W A necessary parameter is not specified. Details A parameter is not specified for the utility. dlmpr Action Execute the utility to check the parameter, and then retry execution. dlmpr -h For details on the utility, see 7.5 dlmpr Utility for Clearing HDLM dlmpr Persistent Reservation.

  • Page 656

    8. Messages and then retry. For details on the utility, see 7.5 dlmpr Utility for Clearing dlmpr HDLM Persistent Reservation. KAPL10648-E An internal error occurred in the dlmpr utility. Error Code = aa...aa Details An error not caused by the user has occurred in the utility.

  • Page 657

    8. Messages Details utility has been terminated because was sent to a request. dlmpr Action None. For details on the utility, see 7.5 dlmpr Utility for Clearing HDLM dlmpr Persistent Reservation. KAPL10652-E The entered value is invalid. The operation stops. Details An invalid response was sent three times consecutively to a request.

  • Page 658

    8. Messages For details on the utility, see 7.3 dlmcfgmgr Utility for Managing dlmcfgmgr the HDLM Configuration. KAPL10922-E The version of the kernel supported by the installed HDLM does not match the currently running kernel version. Install the HDLM software that supports this kernel version. Details The version of the kernel to which installed HDLM has adjusted and the kernel that is running now is not corresponding.

  • Page 659

    8. Messages For details on the utility, see 7.2 DLMgetras Utility for Collecting DLMgetras HDLM Error Information. KAPL10935-W An internal error occurred in the file operation. File name = / etc/opt/DynamicLinkManager/hdlm_utillog.conf. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company.

  • Page 660

    8. Messages same as, the maximum number. Refer to the Messages section of the HDLM User's Guide for instructions to correct this problem. Details The number of paths in the entire system exceeded the maximum number of paths supported in HDLM. Review and, if necessary, revise the configuration. Action The maximum number of paths supported in HDLM has been exceeded.

  • Page 661

    8. Messages If it is not correct, execute the utility for collecting HDLM error DLMgetras information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the utility, see 7.2 DLMgetras Utility for Collecting DLMgetras HDLM Error Information.

  • Page 662

    8. Messages Details An error occurred during 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 utility for collecting HDLM error DLMgetras information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.

  • Page 663

    8. Messages iscsi_boot=y KAPL10949-E A necessary file was not found. File name = aa...aa Details A necessary file was not found. aa...aa: File name Action Reinstall an HDLM.

  • Page 664: Kapl11001 To Kapl12000, Kapl11001 To Kapl

    8. Messages 8.11 KAPL11001 to KAPL12000 KAPL11901-I aa...aa has started. Details The operation has started on the host. aa...aa: Operation (character string) • Get Path Information • Get Option Information • Set Option Information • Clear Data • Get HDLM Manager Status •...

  • Page 665

    8. Messages None. KAPL11903-I aa...aa has completed normally. Details The operation has completed normally on the host. aa...aa: Any of the following operations (character string) • Get Path Information • Get Option Information • Set Option Information • Clear Data •...

  • Page 666

    8. Messages • Clear Data • Get HDLM Driver Status • Get HDLM Manager Status • Get HDLM Alert Driver Status • Online • Offline • Get SNMP Trap Information • Set SNMP Trap Information • Set LU Load Balance •...

  • Page 667

    8. Messages KAPL11907-I XML reception - aa...aa Details This information is required for resolving problems. aa...aa: XML information (character string) Action None. KAPL11908-I XML transmission - aa...aa Details This information is required for resolving problems. aa...aa: XML information (character string) Action None.

  • Page 668: Kapl12001 To Kapl13000, Kapl12001 To Kapl

    8. Messages 8.12 KAPL12001 to KAPL13000 KAPL12035-E The version of the kernel supported by the installed HDLM does not match the currently running kernel version. Details The version of the kernel to which installed HDLM has adjusted and the kernel that is running now is not corresponding.

  • Page 669

    8. Messages Action If the file name displayed in the message is the file name specified in the fstab parameter of the Boot Disk Support Utility ( dlmmkinitrd Check the specified file name, specify the file name of the existing fstab file, and then re-execute the utility.

  • Page 670

    8. Messages KAPL12306-I The list of files required in the initial ramdisk image is being created. Action None. KAPL12307-I The initial ramdisk file system is being created. Action None. KAPL12308-I The initial ramdisk file system is being mounted. Mount point = aa...aa Details aa...aa: Mount point to be used...

  • Page 671

    8. Messages Action None. KAPL12314-I The compressed initial ramdisk image is being created. Action None. KAPL12315-I A compressed initial ramdisk image aa...aa was created with the ramdisk size = bb...bb KB. Details aa...aa: The created initial ramdisk image bb...bb: The ramdisk size required for the created initrd image (decimal number) Action None.

  • Page 672

    8. Messages This message is always preceded by some other specific error message. KAPL12320-E A file or directory already exists. File name = aa...aa Details aa...aa: The name of the already existing file Action To the file name of the initial RAM disk image file specified in the parameter of the Boot Disk Support Utility ( ), do not specify an existing file dlmmkinitrd...

  • Page 673

    8. Messages aa...aa: The name of the module whose insertion has failed Action Confirm that the system environments are not changed after creating the initial ramdisk image file. Check whether there is a mistake in the initial ramdisk image file specified in the config file of the boot loader.

  • Page 674

    8. Messages utility. dlmcfgmgr • Confirm that the user has write permission in the root directory ( dlnkmgr • Confirm that HDLM has been configured. • Take action according to the contents output in the log of the utility. dlmcfgmgr •...

  • Page 675

    8. Messages KAPL12327-E An invalid entry is registered in the file. File name = aa...aa Details aa...aa: The name of the file containing the invalid entry Action Take the following actions depending on the file name output, and then re-execute utility.

  • Page 676

    8. Messages None. KAPL12331-E A directory with the specified kernel version does not exist. Directory name = aa...aa Details aa...aa: The directory where the kernel module is stored For Red Hat Enterprise Linux: The name following directory is the kernel version /lib/modules/ specified with the parameter.

  • Page 677

    8. Messages KAPL12333-E An HBA that HDLM can support as a boot disk was not found in the file. File name = aa...aa Details aa...aa: The name of the file referenced by the utility for dlmmkinitrd supporting the boot disk Action Make sure that an HBA driver that can be used when the boot disk is an HDLM device is in the following file:...

  • Page 678

    8. Messages Modify the file specified in the parameter of the boot disk support fstab fstab utility ( ), or the file system of the file root partition, dlmmkinitrd /etc/fstab to a file system that can be applied when the HDLM device is used as a boot disk (ext2 or ext3).

  • Page 679

    8. Messages Action None. KAPL12344-I A compressed initial ramdisk image (aa...aa) was created. Details aa...aa: The created initial ramdisk image Action None. KAPL12345-E The version of the kernel supported by the installed HDLM does not match the currently running kernel version. Details The version of the kernel to which installed HDLM has adjusted and the kernel that is running now is not corresponding.

  • Page 680

    8. Messages Wait until the executing utility finishes, and then re-execute dlmsetopt If two or more utilities are not executing simultaneously, delete the following files, and then re-execute the utility: /etc/opt/DynamicLinkManager/.dlm_modules.conf.lock KAPL12553-W Usage: /opt/DynamicLinkManager/bin/dlmsetopt {-r retrycount | -inqt InquiryTimeout | -inqr InquiryRetry | -h} Action Refer to 7.6 dlmsetopt Utility for Setting HDLM Driver Options, and then specifying the correct argument.

  • Page 681

    8. Messages Action Restart the computer. KAPL12559-E An invalid value was specified in the parameter. Option = aa...aa, Parameter = bb...bb Details aa...aa: Option bb...bb: Specified parameter(Maximum 10 characters. If there are more than 10 characters, only 10 characters will be output followed by Action Refer to 7.6 dlmsetopt Utility for Setting HDLM Driver Options, and then specifying the correct argument.

  • Page 682

    8. Messages KAPL12563-E An attempt to create a directory has failed. Directory = aa...aa Details aa...aa: Directory that an attempt was made to create Action Make sure there is enough free disk capacity, and then re-execute the utility for setting HDLM driver option ( dlmsetopt Delete any unnecessary files in the file system, and then re-execute the utility.

  • Page 683

    8. Messages dlmdrvopt.conf • When the file contents match: Delete the /etc/opt/DynamicLinkManager/DLMSETOPT/ file. Then, re-execute the utility to make sure modprobe.conf dlmsetopt that an error does not occur. • When the file contents do not match: Overwrite the file with the /etc/modprobe.conf /etc/opt/ file, and then...

  • Page 684

    8. Messages Action Install HDLM that adjusts to the kernel that is running now. KAPL12802-E The HDLM file is invalid. File name = aa...aa Details 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 685

    8. Messages Action Install HDLM that adjusts to the kernel that is running now. KAPL12902-E The HDLM file is invalid. File name = aa...aa Details 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 686: Kapl13001 To Kapl14000, Kapl13001 To Kapl

    8. Messages 8.13 KAPL13001 to KAPL14000 KAPL13204-W The file does not exist. File name = aa...aa Details aa...aa: /etc/.DynamicLinkManager/Path00 /etc/.HBaseAgent/ Path00 Action Reinstall HDLM. KAPL13205-W You do not have read permission for the file. File name = aa...aa Details aa...aa: /etc/.DynamicLinkManager/Path00 /etc/.HBaseAgent/ Path00...

  • Page 687

    8. Messages KAPL13401-E No parameter has been specified. Details No parameter (directory to which collected information is output) has been specified. Action Check the parameters of the utility for collecting HDLM install error information, and then retry. KAPL13402-E The first parameter has not been set to a directory. Value= aa...aa Details The first directory must be set to a directory to which collected information is output.

  • Page 688

    8. Messages Action The specified directory already exists. Enter to overwrite the existing file. Enter or press any other key to terminate the utility for collecting HDLM install error information without executing it. KAPL13405-E The root directory has been specified in the first parameter. Details A root "...

  • Page 689

    8. Messages The process has been terminated by an operation such as Ctrl Action The utility for collecting HDLM install error information terminated before completion. If the directory is unnecessary, delete directory. KAPL13409-I The utility for collecting HDLM install error information completed normally.

  • Page 690

    8. Messages Action Re-execute the utility for collecting HDLM install error information. KAPL13413-W The file does not exist. File = aa...aa Details The file subject to collecting does not exist. aa...aa: Name of file to collect Action None. KAPL13414-E File = aa...aa, Details = bb...bb The file could not be copied.

  • Page 691

    8. Messages aa...aa: command output message gzip Action See the details in the message, and then remove the cause of the error. For information about the error, collect the archive in the output directory specified at the time of execution, and then contact your HDLM vendor or the maintenance company if you have a maintenance contract for HDLM.

  • Page 692

    8. Messages KAPL13504-I A symbolic link has been modified. Symbolic link name = aa...aa Details aa...aa: Name of the modified symbolic link Action None. KAPL13505-E A system script cannot be modified. File name = aa...aa Details aa...aa: File name of the system script that cannot be modified Action Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM.

  • Page 693

    8. Messages Re-execute utility as a user with root permission. Refer to dlmupdatesysinit 7.8 dlmupdatesysinit Utility for Updating System Scripts. KAPL13509-E The utility for update system scripts can be executed with the name dlmupdatesysinit only. Action Change the utility name back to , and then execute it.

  • Page 694

    8. Messages KAPL13514-W Usage: /opt/DynamicLinkManager/bin/dlmupdatesysinit Action Check for parameters, and then re-execute the utility. Refer dlmupdatesysinit to 7.8 dlmupdatesysinit Utility for Updating System Scripts. KAPL13515-E A command required by HDLM not found. Command = aa...aa Details aa...aa: File name of command Action Install a package that includes the command indicated in the message.

  • Page 695

    8. Messages Check for and, if necessary, restore the system file indicated in the message. Next, execute the utility. Refer to 7.8 dlmupdatesysinit Utility dlmupdatesysinit for Updating System Scripts. KAPL13519-E An HDLM file required for the dlmupdatesysinit utility was not found.

  • Page 696

    8. Messages Reinstall an HDLM. KAPL13601-W The audit log configuration file does not exist. Restart the HDLM Manager, and execute the "dlnkmgr view -sys -audlog" command and check the setting. Details The audit log configuration file does not exist. Action Restart the HDLM manager, execute the "...

  • Page 697

    8. Messages file. Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL13605-W An error occurred during processing to output the audit log configuration file. Details An internal parameter error occurred during output of the audit log data. Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.

  • Page 698

    8. Messages KAPL13904-I Filter driver had been loaded. Filter driver's loading was skipped. Action None. KAPL13905-I HDLM manager had started. HDLM manager's start processing was skipped. Action None. KAPL13906-I aa...aa will now start. Details aa...aa: Alert driver's loading The process related to Alert , or driver Filter driver's loading...

  • Page 699

    8. Messages file does not exist or does not /opt/DynamicLinkManager/bin/dlmmgr have executable permissions. Reinstall an HDLM. KAPL13909-W Usage: /opt/DynamicLinkManager/bin/dlmstart Action Re-execute the utility for HDLM start if necessary. Refer to 7.7 dlmstart Utility for Starting HDLM. KAPL13910-W The error occurred while processing the utility for HDLM start. Action Resolve the problem according to the message KAPL13908-W, which was output before this message.

  • Page 700

    8. Messages KAPL13913-E A command has failed. Command = aa...aa, details = bb...bb Details aa...aa: Command that failed bb...bb: Message that the command output Action When the command is /sbin/modprobe Reinstall an HDLM When the command is /bin/mknod Remove the error cause described in the message output by the command indicated in the message KAPL13913-E.

  • Page 701: Kapl15001 To Kapl16000, Kapl15001 To Kapl

    8. Messages 8.14 KAPL15001 to KAPL16000 KAPL15001-I The registered value of ReserveKey was successfully displayed. Command Line = aa...aa Details aa...aa: Name of the utility that the user executed KAPL15002-E An attempt to display the registered value of ReserveKey has failed.

  • Page 702

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

  • Page 703

    8. Messages Details aa...aa: Name of the utility that the user executed KAPL15051-E An attempt to create an initial RAM disk image file for using an HDLM device as a boot disk has failed. Command Line = aa...aa Details aa...aa: Name of the utility that the user executed KAPL15052-I The number of retries to allocate memory was successfully set.

  • Page 704

    8. Messages Details aa...aa: Name of the utility that the user executed KAPL15058-I Processing to re-register the HDLM information was successful. Command Line = aa...aa Details aa...aa: Name of the utility that the user executed KAPL15059-E Processing to re-register the HDLM information failed. Command Line = aa...aa Details aa...aa: Name of the utility that the user executed...

  • Page 705

    8. Messages cc...cc: Name of the utility that the user executed KAPL15065-E An attempt to clear ReserveKey has failed on aa...aa SCSI device(s). Command Line = bb...bb Details aa...aa: Number of SCSI devices for which ReserveKey was not cleared. bb...bb: Name of the utility that the user executed KAPL15101-I Clear operation was completed successfully.

  • Page 706

    8. Messages aa...aa: Command that the user executed KAPL15106-E Setting up the operating environment failed. Command Line = aa...aa Details aa...aa: Command that the user executed KAPL15107-I Program information was successfully displayed. Command Line = aa...aa Details aa...aa: Command that the user executed KAPL15108-E An attempt to display program information has failed.

  • Page 707

    8. Messages KAPL15404-W The HDLM Manager was executed by the user who does not have the authority.

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

    8. Messages 8.15 Return Codes for Hitachi Command Suite Common Agent Component When an operation requested of HDLM from Global Link Manager terminates abnormally, or terminates normally with a warning, HDLM outputs one of the return codes described below. 1002 Details There is no path on which the operation can be performed.

  • Page 709

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

  • Page 710

    8. Messages maintenance contract for HDLM. For details on the utility, see DLMgetras 7.2 DLMgetras Utility for Collecting HDLM Error Information. 1025 Details A parameter value is invalid. Action Refresh the host information, and then perform the operation again. If the same error occurs again, execute the utility for collecting HDLM error DLMgetras...

  • Page 711

    8. Messages HDLM Error Information. 1034 Details An attempt to acquire information about the HDLM version or SP version has failed. 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.

  • Page 712

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

  • Page 713

    8. Messages utility, see 7.2 DLMgetras Utility for Collecting HDLM Error Information.

  • Page 715: Appendixes

    Appendixes A. Notes on Linux Commands and Files B. Troubleshooting Products That Use the Weak-Modules Script C. Functional Differences Between Versions of HDLM D. Glossary...

  • Page 716: A. Notes On Linux Commands And Files, A.1 Notes On The /proc/partitions File

    A. Notes on Linux Commands and Files A. Notes on Linux Commands and Files This section provides notes on Linux commands and files. A.1 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 file.

  • Page 717: A.3 Notes On The Iostat Command

    A. Notes on Linux Commands and Files commands show little difference before and after HDLM installation. Table A-1: Examples of Linux Command Execution Times Linux Time commands Example 1 Example 2 Before HDLM After HDLM Before HDLM After HDLM installation installation installation installation...

  • Page 718: A.4 Notes On The Mkfs Command, A.5 Notes On The Fdisk Command

    A. Notes on Linux Commands and Files Figure A-2: Example of Executing the iostat Command A.4 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 command.

  • Page 719: A.6 Notes On The Sar Command, A.7 Notes On The Fdisk And Parted Commands

    A. Notes on Linux Commands and Files A.6 Notes on the sar Command Executing the command with the option does not display HDLM devices. To obtain statistics about an HDLM device, perform calculations by using the value of the SCSI device that conforms to the HDLM device. The following is an example of executing the command.

  • Page 720: A.9 Notes On The Vgrename And Lvrename Commands

    A. Notes on Linux Commands and Files SCSI device 1..n: The SCSI device names which are being managed by the above HDLM device (for example, /dev/sda) A.9 Notes on the vgrename and lvrename Commands If a logical volume is created on an md device, you can rename a volume group or a logical volume by using the command.

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

    B. Troubleshooting Products That Use the Weak-Modules Script B. Troubleshooting Products That Use the Weak-Modules Script 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 Linux...

  • Page 722

    B. Troubleshooting Products That Use the Weak-Modules Script root directory: Example when the boot loader is elilo and LVM is not used: # cat /etc/fstab /dev/sddlmaa2 ext3 defaults /dev/sddlmaa1 /boot/efi vfat defaults tmpfs /dev/shm tmpfs defaults devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs...

  • Page 723

    B. Troubleshooting Products That Use the Weak-Modules Script For device, enter the device you determined in step 1. In each of the following examples, the underlined part indicates the kernel parameter added in this step: Example when the boot loader is elilo and LVM is not used: image=vmlinuz-2.6.18-92.el5 label=linux-HDLM initrd=initrd-2.6.18-92.el5.img.hdlm...

  • Page 724

    B. Troubleshooting Products That Use the Weak-Modules Script used. Delete the kernel parameter you added in step 2 from the boot loader configuration file. If the boot loader configuration file contains any entries other than the entry for using HDLM as a boot disk, make sure that HDLM device is not specified root= as a kernel parameter, and then go to step 9.

  • Page 725

    B. Troubleshooting Products That Use the Weak-Modules Script Example when LVM is not used: 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)

  • Page 726: B.2 Uninstalling Products That Use The Weak-modules Script

    B. Troubleshooting Products That Use the Weak-Modules Script The underlined portion is a device of the volume group that indicates the root directory ( # vgdisplay -v --- Volume group --- VG Name VolGroup00 System ID --- Logical volume --- LV Name /dev/VolGroup00/LogVol00 VG Name...

  • Page 727: C. Functional Differences Between Versions Of Hdlm

    C. Functional Differences Between Versions of HDLM C. Functional Differences Between Versions of HDLM This section explains the functional differences between newer and older versions of HDLM. C.1 Functional Differences Between Version 6.2.1 and Versions Earlier Than 6.2.1 The output destination of the HDLM command operation log data has been changed from Hitachi Network Objectplaza Trace Library (HNTRLib2) integrated trace information files ( /var/opt/hitachi/HNTRLib2/spool/...

  • Page 728: C.5 Functional Differences Between Version 5.9.1 Or Later And Versions Earlier Than 5.9.1

    C. Functional Differences Between Versions of HDLM using the utility. dlmcfgmgr C.5 Functional Differences Between Version 5.9.1 or Later and Versions Earlier Than 5.9.1 In versions earlier than 5.9.1, the timeout value of is fixed. SCSI INQUIRY Therefore, depending on the connected storage system, a timeout occurs when the response for is delayed.

  • Page 729: C.8 Functional Differences Between Version 5.7.1 Or Later And Versions Earlier Than 5.7.1

    C. Functional Differences Between Versions of HDLM Table C-1: JRE/JDK Version Required for HDLM GUI Required version of JRE or JDK Earlier than HDLM 5.8 or HDLM 5.7.1 later Red Hat Enterprise Linux AS3/ES3 (IA32) JRE v1.4.2_08 JRE v1.4.2_09 Red Hat Enterprise Linux AS4/ES4 (IA32) SUSE LINUX Enterprise Server 9 (IA32) Red Hat Enterprise Linux AS3/ES3 (IPF) JDK v1.4.2_08...

  • Page 730: C.11 Functional Differences Between Version 5.6.3 Or Later And Versions Earlier Than 5.6.3

    C. Functional Differences Between Versions of HDLM C.11 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 describes the version of the JRE or JDK required to use the HDLM GUI on a host. Table C-2: JRE/JDK Version Required for HDLM GUI Required version of JRE or JDK Earlier than...

  • Page 731: D. Glossary

    D. Glossary D. 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 status recovers from an error, an Offline(E)

  • Page 732

    D. Glossary Dev (Device) A logical division of an LU that HDLM controls and operates. A Dev is equivalent to a partition in Linux. In Linux, each LU can be divided into more than one Dev. Each Dev has a Dev number. Depending on the access method, Devs are classified into two types: block devices and character devices.

  • Page 733

    D. Glossary 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. FC-SAN (Fibre Channel - Storage Area Network) A SAN using Fibre Channel. HBA (Host Bus Adapter) Device that functions as an interface connecting a host with external devices.

  • Page 734: Load Balancing

    D. Glossary 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. IP-SAN (Internet Protocol - Storage Area Network) A data transfer network that connects hosts and storage systems by using the iSCSI standard.

  • Page 735

    D. Glossary logical device file A device file in the directory. /dev 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 736

    D. Glossary owner controller is called a non-owner path. When using the Lightning 9900 series, Lightning 9900V series, Hitachi USP, Universal Storage Platform V/VM, Virtual Storage Platform, Hitachi AMS2000 series, or Hitachi SMS, all paths are owner paths. (See also: owner controller, non-owner path) path An access path from a host to a storage system.

  • Page 737: Physical Path

    D. Glossary physical path An access path from a host to an LU. A path name is used to identify a physical path. QEMU A virtual emulator available for the entire host system. (See also: KVM) 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.

  • Page 739: Index

    Index Symbols when using SUSE LINUX Enterprise Server 11 119 /proc/partitions files 692 boot loader configuration file 177 bus number 449 abbreviations defined iii active host 56 canceling adding new LU 371 md device settings 302 adding path to existing LU 374 canceling settings for HDLM 290 audit log canceling settings for Heartbeat 292...

  • Page 740

    Index collecting displaying error info. with HDLM utility information 431 (DLMgetras) 43 path information (by abbreviating the list collecting HDLM installation error information items) 431 using installgetras 43 path information (by selecting a display command item) 431 format 398 path information (without selecting items to be overview 398 displayed) 431 command of HDLM (dlnkmgr)

  • Page 741

    Index errors Global Link Manager 54 detected by HDLM 42 glossary 707 management 39 examining message 392 handling path error 391 HBA 8 failback 25 procedure for replacing 358 failover 25 replacing 356 FC-SAN 7 fdisk commands 694 HBA (Host Bus Adapter) 709 features of HDLM 4 HDev 13 fiber cable...

  • Page 742

    Index HDLM resident processes 355 installing HDLM HDLM utility 15 required knowledge 132 HDLM-configuration definition utility 489 Installing HDLM for Managing Boot Disks 172 HDLM-managed device installux.sh 521 operations on 290 integrated HDLM management 54 Heartbeat intended readers i canceling settings 292 intermittent error 710 setting 262 definition 28...

  • Page 743

    Index Linux commands and files 692 load balancing 19 narrowing down load balancing algorithms 23 hardware causing error 393 log collection level network interface card 9 values 416 NIC 72 log filter 42 node 711 logical device file 711 non-owner controller 22 logical device files non-owner path 21 for HDLM devices 17...

  • Page 744

    Index cluster software 121 process-specific-trace Information file 281 file system 123 process-specific-trace information file 41 kernel 70 product ID 446 volume manager 122 Product ID displayed by the view -path operation 449 organization of this manual i program error OS 58 what to do for 394 update packages 339 program information...

  • Page 745

    Index RHCM kernel 68 notes 266 volume manager 118 SUSE LINUX Enterprise Server 9 146 kernel 65 symbol conventions ix SAN (Storage Area Network) 713 syntax conventions x sar commands 695 syslog 41 SCSI device 713 system configuration 7 set 414 setting automatic mounting 286 setting Heartbeat 262 setting KVM 260...

  • Page 746

    Index utility for starting HDLM 510 vendor ID 446 vgrename commands 696 view 431 virtual environment 127 volume manager when using Oracle Enterprise Linux 4 120 when using Oracle Enterprise Linux 5 122 when using Red Hat Enterprise Linux 5 103 when using Red Hat Enterprise Linux 6 109 when using Red Hat Enterprise Linux AS4/ ES4 89...

Comments to this Manuals

Symbols: 0
Latest comments: