Hitachi Dynamic Link Manager Software User's Guide (for AIX(R)) 3000-3-F01-50(E)
Relevant program products Hitachi Dynamic Link Manager version 6.6 For details about applicable OSs, see the Release Notes. Trademarks AIX is a trademark of International Business Machines Corporation in the United States, other countries, or both. AIX 5L is a trademark of International Business Machines Corporation in the United States, other countries, or both. GPFS is a trademark of International Business Machines Corporation in the United States, other countries, or both.
Summary of Amendments The following table lists changes in this manual (3000-3-F01-50(E)) and product changes related to this manual. Changes Location in this manual Virtual Storage Platform has been added as a storage system supported by HDLM. 1.1, 2.6.1, 2.7.1, 2.7.2, 3.1.1, 3.1.2, 3.10.2, 3.11, 3.12.1, 3.14.2, 3.14.5, 6.7.2, Appendix C A logical device file name can now be changed by using the rendev command. 2.
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.
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 about viewing messages output by HDLM. It also lists and explains the HDLM messages and shows the actions to be taken in response to each message. A. Functional Differences Between Versions of HDLM Appendix A explains the differences in functionality between HDLM versions. C.
Abbreviation Full name or meaning Global Link Manager Hitachi Global Link Manager GPFS General Parallel File System HACMP High Availability Cluster Multi-Processing A generic term for: • HACMP 5.4 • HACMP 5.4.1 • PowerHA 5.5 • PowerHA 6.1 • PowerHA 7.
Abbreviation Full name or meaning Hitachi WMS Hitachi Workgroup Modular Storage series 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 A generic term for: • HP XP128 • HP XP1024 • HP XP10000 • HP XP12000 • HP XP20000 • HP XP24000 JDKTM JavaTM 2 SDK, Standard
Abbreviation Full name or meaning Universal Storage Platform V/VM A generic term for: • Hitachi Universal Storage Platform V • Hitachi Universal Storage Platform VM • HP XP20000 • HP XP24000 UNIX A generic term for: • AIX • HP-UX • Linux • Solaris VCS Veritas Cluster Server Virtual Storage Platform A generic term for: • Hitachi Virtual Storage Platform • HP StorageWorks P9500 Disk Array VxVM Veritas Volume Manager This manual also uses the following abbreviations.
Abbreviation Full name or meaning FO Failover GMT Greenwich Mean Time GUI Graphical User Interface HBA Host Bus Adapter HDev Host Device HLU Host Logical Unit HTTP Hypertext Transfer Protocol I/O Input/Output IP Internet Protocol iSCSI Internet Small Computer System Interface LAN Local Area Network LDAP Lightweight Directory Access Protocol LDEV Logical Device LPAR Logical Partition LU Logical Unit LUN Logical Unit Number LVM Logical Volume Manager MPIO Multipath I/O NA
Abbreviation Full name or meaning RADIUS Remote Authentication Dial in User Service SAN Storage Area Network SCSI Small Computer System Interface SLPR Storage Logical Partition SMIT System Management Interface Tool SMTP Simple Mail Transfer Protocol SNMP Simple Network Management Protocol SP Service Pack SSL Secure Sockets Layer SVP Service Processor VG Volume Group WWN World Wide Name Conventions: Diagrams This manual uses the following conventions in diagrams: vii
Conventions: Fonts and Symbols Font and symbol conventions are classified as: • General font conventions • Conventions in syntax explanations These conventions are described below. General Font Conventions The following table lists the general font conventions: Font viii 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.
Font Convention Code font A code font indicates text that the user enters without change, or text (such as messages) output by the system. For example: • At the prompt, enter dir. • Use the send command to send mail. • The following message is displayed: The password is incorrect. Code examples and messages appear as follows (though there may be some exceptions, such as when the code is part of a diagram): MakeDatabase ... StoreDatabase temp DB32 In examples of coding, an ellipsis (...
Conventions: KB, MB, GB, and TB This manual uses the following conventions: • 1 KB (kilobyte) is 1,024 bytes. • 1 MB (megabyte) is 1,0242 bytes. • 1 GB (gigabyte) is 1,0243 bytes. • 1 TB (terabyte) is 1,0244 bytes.
Contents Preface i Intended Readers ........................................................................................................i Organization of This Manual .....................................................................................i Related Publications..................................................................................................ii Conventions: Abbreviations ......................................................................................
2.10.4 Collecting installation error information using the utility for collecting HDLM installation error information (dlmgetrasinst) ................................. 43 2.11 Collecting Audit Log Data..................................................................................... 44 2.11.1 Categories and Audit Events that HDLM Can Output to the Audit Log.... 45 2.11.2 Requirements for Outputting Audit Log Data ............................................ 48 2.11.
3.8 Setting up Integrated Traces ...................................................................................147 3.8.1 Notes on Using the Hitachi Network Objectplaza Trace Library ...............147 3.8.2 Displaying the Hitachi Network Objectplaza Trace Library setup menu ...148 3.8.3 Changing the Size of Integrated Trace Files ...............................................148 3.8.4 Changing the Number of Integrated Trace Files .........................................149 3.8.
4.2.5 Displaying the Correspondences Between hdisks, OS Management Path IDs, and LDEVs ................................................................................................. 185 4.2.6 Initializing Statistical Information for Paths............................................... 186 4.2.7 Viewing and Setting Up the Operating Environment ................................. 187 4.2.8 Viewing License Information ..................................................................... 189 4.2.
6.4 6.5 6.6 6.7 6.3.1 Format .........................................................................................................232 6.3.2 Parameter.....................................................................................................232 offline (Places Paths Offline)..................................................................................235 6.4.1 Format .........................................................................................................235 6.4.
7.10.1 Format....................................................................................................... 333 7.10.2 Parameters ................................................................................................ 333 7.11 dlmrmdev Utility for Deleting HDLM Drivers.................................................... 334 7.11.1 Format....................................................................................................... 334 7.11.2 Parameters..............................
B.3 Changing the HDLM Environment Configuration and Operation Procedures by Changes to the Logical Device Files.............................................................472 B.4 Migrating Reservation Control Settings ........................................................473 B.5 Support for a Boot Disk Environment ...........................................................473 B.6 About Settings when Upgrading the OS........................................................474 B.
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. This chapter gives an overview of HDLM and describes its features. 1.1 What is HDLM? 1.
1. Overview of HDLM 1.1 What is HDLM? The widespread use of data warehousing and increasing use of multimedia data have increased the need for high-speed processing of large volumes of data on networks. To satisfy this need, networks dedicated to data transfer, such as a SAN, are now being used to provide access to storage systems. The HDLM software manages access paths to storage systems. HDLM uses MPIO functionality supported by AIX 5L V5.2 or later.
1.
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. This prevents one, loaded down path from affecting the processing speed of the entire system. For details on load balancing, see 2.6 Distributing a Load Using Load Balancing.
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. After that, the rest of the chapter focus on describing all the HDLM functions, including the main ones: load distribution across paths and path switching. 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.
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 are from the storage systems listed in Section 1.
2. HDLM Functions 2.2 System Configuration HDLM manages routes between a host and a storage system by using the SCSI driver. The host and storage systems are connected using SAN with fiber cables. The cable port on the host is a host bus adapter (HBA). The cable port on the storage system is a port (P) on a channel adapter (CHA). A logical unit (LU) contained in a storage system is the target of input to, or output from, the host. An area in an LU is called a Dev.
2. HDLM Functions Figure 2-1: HDLM System Configuration Table 2-1: HDLM System Components lists the HDLM system components. Table 2-1: HDLM System Components Components 8 Description HBA A host bus adapter. This serves as a cable port on the host. SAN A dedicated network that is used for data transfer between the host machine and storage systems. CHA A channel adapter. P A port on a CHA. This serves as a cable port on a storage system.
2. HDLM Functions Components Path Description A route that connects a host and a Dev.
2. HDLM Functions 2.3 LU Configuration On a system using HDLM, the logical device file for the HDLM management-target device is used to access the target LU. An LU recognized by a host after HDLM installation, is called a host LU (HLU). The areas in a host LU that correspond to the Dev in a storage system LU are called host devices (HDev). An LU in the storage system corresponds one-to-one with a host LU, a host device, or an hdisk.
2. HDLM Functions Table 2-2: Components recognized by the host Components Description HLU An LU that the host recognizes via the HDLM driver. It is called a host LU. No matter how many paths exist, one host LU is recognized for one LU in the storage system. HDev A Dev in an LU that the host recognizes via the HDLM driver. It is called a host device. No matter how many paths exist, one host device is recognized for one Dev in the storage system.
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-3: Configuration of the HDLM Programs configuration of the HDLM programs. Figure 2-3: Configuration of the HDLM Programs Table 2-3: Functionality of HDLM Programs lists and describes the functions of these programs.
2.
2. HDLM Functions 2.5 Position of the HDLM Driver and hdisk The HDLM driver is positioned above the SCSI driver and is an add-in module of MPIO driver located in the AIX standard hdisk. Each application on the host uses the hdisk (logical device file) created by HDLM, to access LUs in the storage system. Figure 2-4: Position of the HDLM Driver and hdisk shows the position of the HDLM driver and hdisk. The logical device file name can be changed by using the rendev command.
2. HDLM Functions 2.6 Distributing a Load Using Load Balancing When the system contains multiple paths to a single LU, HDLM can distribute the load across the paths by using multiple paths to transfer the I/O data. This function is called load balancing, and it prevents a single, heavily loaded path from affecting the performance of the entire system. Figure 2-5: Flow of I/O Data When the Load Balancing Function Is Not Used shows the flow of I/O data when the load balancing function is not used.
2. HDLM Functions When the load balancing function is not being used, I/O operations converge on one physical path (A). The load on the physical path (A) will cause a bottleneck, which might cause deterioration of the whole system's performance. Figure 2-6: Flow of I/O Data When the Load Balancing Function Is Used When the load balancing function is being used, I/O operations are distributed via physical paths (A), (B), (C), and (D).
2. HDLM Functions (1) When Using the Thunder 9500V Series, or Hitachi AMS/WMS Series When HDLM performs load balancing, it differentiates between load balancing among owner paths and among non-owner paths. An owner path is a path that passes through the owner controller for a target LU. When you set up an LU, you have to specify which CHA to be used as the owner controller for the LU. Because different LUs might have different owner controllers, different LUs might also have different owner paths.
2. HDLM Functions Figure 2-7: Overview of load balancing (2) When Using the Lightning 9900V Series, Hitachi USP, Universal Storage Platform V/VM, Virtual Storage Platform, Hitachi AMS2000 Series, or Hitachi SMS All online paths are owner paths. Therefore, for the example in Figure 2-6: Flow of I/O 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. HDLM Functions • The Extended Least Blocks algorithm The above algorithms are divided into two categories, which differ in their processing method. The following describes both of these processing methods: The Round Robin, Least I/Os, and Least Blocks algorithms These algorithms select which path to use every time a certain number of I/Os are issued. The path that is used is determined by the following: • Round Robin The paths are simply selected in order from among all the connected paths.
2. HDLM Functions Table 2-4: Features of the Load Balancing Algorithms Algorithm type Algorithm features • Round Robin# • Least I/Os • Least Blocks These types of algorithms are most effective when a lot of discontinuous, non-sequential I/Os are issued.
2. HDLM Functions 2.7 Performing Failovers and Failbacks Using Path Switching When the system contains multiple paths to an LU and an error occurs on the path that is currently being used, HDLM can switch to another functional path, so that the system can continue operating. This is called a failover. If a path in which an error has occurred recovers from the error, HDLM can then switch back to that path. This is called a failback.
2. HDLM Functions For details on error levels, see 2.10.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. For example, in Figure 2-8: Path switching, the owner controller of an LU is CHA0, and access to the LU is made via only one path (A).
2. HDLM Functions Figure 2-8: Path switching (2) Priority of Switching Destination Paths Priority of paths varies depending on the architecture of the host machine. If the architecture of the host is CHRP, the switching destination path is selected based on four keys. First, the path with the smallest path priority number (first key) is selected.
2. HDLM Functions This sub-section explains these keys. Path priority number This number indicates the priority level set for each path. Priority levels can be set from 1 to 255. The lower the number, the higher the priority. The default is 1. The priority level is set by using OS commands. The following shows an example of the procedure for setting the path priority number. 1.
2. HDLM Functions node_name 0x50060e8005271720 FC Node Name False state Enabled N/A True priority 5 N/A True Slot number This number indicates the position of the slot where an HBA is mounted. You can find the order of the slot numbers by comparing their physical location code. The following describes how to obtain the physical location code. 1. Execute the following command to find hdisk, based on AutoPATH_ID. # /usr/DynamicLinkManager/bin/dlnkmgr view -drv PathID HDevName OSPathID LDEV 2.
2. HDLM Functions The obtained physical location code is in the Uaa.bb-Pcc-Idd format. The first letters, Uaa.bb, depend on the model of the host. HDLM selects the path with the lowest value for aabbccdd. When the physical location code is in another format, the priority of paths is not decided. Note that the top priority path does not change because of, for example, restarting a computer in the same environment. Note Depending on the HBA, you need to repeat steps 2 and 3.
2. HDLM Functions then HDLM automatically places the recovered path online while a non-owner path is in use, the path will be automatically switched over from the non-owner path to the owner path that just recovered from the error. When the Lightning 9900V series, Hitachi USP, Universal Storage Platform V/VM, Virtual Storage Platform, Hitachi AMS2000 series, or Hitachi SMS is being used, all the paths are owner paths.
2. HDLM Functions other paths that run through the same physical path are switched. Executing the online operation places the offline path online. For details on the online operation, see 6.5 online (Places Paths Online). After the path status is changed to online (by executing the online operation), HDLM selects the path to use in the same way as for automatic path switching.
2. HDLM Functions • Offline(E) The status indicating that an I/O could not be issued on a given path, because an error occurred on the path. The (E) means error.
2. HDLM Functions Figure 2-9: Path status transitions Legend: Online operation: Online operation performed by executing the dlnkmgr command's online operation. Offline operation: Offline operation performed by executing the dlnkmgr command's offline operation. #1 When no Online or Offline(E) paths exist among the paths that access the same LU.
2. HDLM Functions 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. #3 This path is deleted when the AIX chdev command is executed on an hdisk where an Online or Offline(E) path exists. To restore the deleted path, remove the cause of the error and then execute the AIX mkdev -l hdisk-name or cfgmgr command.
2. HDLM Functions 2.8 Monitoring intermittent errors (functionality when automatic failback is used) An intermittent error refers to an error that occurs irregularly because of something like a loose cable. In such a case, I/O performance might decrease while an automatic failback is being performed to repair an intermittent error. This is because the automatic failback operation is being performed repeatedly (because the intermittent error keeps occurring).
2. HDLM Functions 2.8.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.
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. If an error occurs on the path again at a later time, error monitoring will resume when the path is recovered from the error via an automatic failback.
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. As such, the error monitoring will not finish, and it will start over by using the new conditions.
2. HDLM Functions path, check the IEP item displayed when the dlnkmgr command's view -path operation is executed with the -iem parameter. If a numerical value of 0 or greater is displayed in the Intermittent Error Path item, then intermittent error monitoring is being performed.
2. HDLM Functions #1 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).
2. HDLM Functions 2.9 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 is not detected unless I/O is performed because the system only checks the path status when I/O is performed. With path health checking, however, the system checks the status of online paths at regular intervals regardless of whether I/O is performed.
2. HDLM Functions 2.10 Error management For troubleshooting purposes, HDLM collects information and stores it into log files. The error information to be collected can be filtered out by error level, and then stored into the log files. Figure 2-13: Flow of Data When Collecting Error Information shows the flow of data when collecting error information.
2. HDLM Functions Figure 2-13: Flow of Data When Collecting Error Information Logs might be collected in layers below HDLM, such as for the HBA driver. For more details, see the AIX documentation.
2. HDLM Functions 2.10.1 Types of Collected Logs HDLM collects information on the detected error and trace information in the integrated trace file, trace file, error logs, HDLM utility's log file, and syslog. You can use the error information to examine the status of an error and analyze the cause of the error. Table 2-7: Types of error information describes the types of error information.
2. HDLM Functions Log name Description HDLM configurat ion log HDLM configuration log is an operation log of the configuration processing for the HDLM driver. Output destination /var/DynamicLinkManager/ log/dlmconfig[1-2].log # When you want to configure the system so that HDLM messages are output to syslog, specify user for the facility in the /etc/syslog.conf file.
2. HDLM Functions • Collects no error information. • Collects error information at the Error level and higher. • Collects error information at the Warning level and higher. • Collects error information at the Information level and higher. • Collects error information at the Information level and higher (including maintenance information).
2. HDLM Functions 2.11 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.
2.
2. HDLM Functions Table 2-10: Categories and Audit Events that Can Be Output to the Audit Log Category Explanation Audit event Severity Message ID #1 StartStop Startup and termination of the software Startup of the HDLM manager was successful. 6 KAPL15401-I Startup of the HDLM manager failed. 3 KAPL15402-E The HDLM manager stopped.
2. HDLM Functions Category Explanation Audit event Severity Message ID #1 Setup of the operating environment was successful. 6 KAPL15105-I Setup of the operating environment failed. 3 KAPL15106-E An attempt to display program information was successful. 6 KAPL15107-I An attempt to display program information failed. 3 KAPL15108-E An attempt to display HDLM management-target information was successful. 6 KAPL15109-I An attempt to display HDLM management-target information failed.
2. HDLM Functions Category Explanation Audit event Message ID Severity #1 Processing of the 6 KAPL15082-I 3 KAPL15083-E dlmchpdattr -a command was successful. Processing of the dlmchpdattr -a command failed. #1 The severity levels are as follows: 3: Error, 4: Warning, 6: Informational #2 If you use Ctrl + C to cancel the DLMgetras utility for collecting HDLM error information, audit log data indicating that the DLMgetras utility has terminated will not be output.
2. HDLM Functions For details on how to enable syslog, see 2.11.3 Destination and Filtering of Audit Log Data or the AIX documentation. • 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 set operation differs from the severity specified by the configuration file /etc/syslog.
2. HDLM Functions Severity Audit log data to output 7 Correspondence with syslog severity levels Debug 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.7.2 Setting Up the HDLM Functions. 2.11.
2. HDLM Functions Table 2-12: Items Output in the Message Section Explanation Item# Common identifier Fixed to CELFSS Common specification revision number Fixed to 1.1 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-mm-ddThh:mm:ss.
2. HDLM Functions Item# Explanation Application identification information Program identification information 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.
2. HDLM Functions 2.12 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.
2.
2. HDLM Functions 2.13 Cluster support HDLM can also be used in cluster configurations. HDLM supports the cluster software listed below. • GPFS • HACMP • Oracle RAC 10g • Oracle RAC 11g • VCS HDLM uses a path of the active host to access an LU. The details of host switching depend on the application.
Chapter 3. Creating an HDLM Environment This chapter describes the procedures for creating an HDLM environment and for canceling the setup. Make sure that HDLM is installed and its functions have been set up. The volume groups and cluster software programs must be set up appropriately for your system environment. Note that, in the required procedures and notes, there are differences between HDLM version 5.8.1 or earlier, and HDLM version 5.9 or later. For details, see B. Differences Between HDLM Version 5.
3. Creating an HDLM Environment 3.1 HDLM System Requirements Check the following before installing HDLM. For OS patches and software provided by OS vendors, download them from the Web site of the appropriate OS vendor. 3.1.1 Host and OS Support for HDLM You can install HDLM on hosts running the OSs shown in Table 3-1: Applicable OSs for the Host. Table 3-1: Applicable OSs for the Host OS Kernel AIX 5L V5.
3. Creating an HDLM Environment OS AIX V7.1 (Virtual I/O Server)#3 Kernel ioslevel 2.1.0.xx to 2.2.0.xx (where xx is a number) #1 Every SP is applicable, unless otherwise specified. #2 To set up a boot disk environment that uses Thunder 9500V series, Hitachi AMS/ TMS/WMS series, or Hitachi SMS, use SP2 or a later service pack. #3 An environment in which the Secure by Default functionality is enabled during installation of the OS is not supported.
3. Creating an HDLM Environment HTC_ODM 5.0.52.1 or later If you are using the following storage systems, use HTC_ODM 5.0.52.
3. Creating an HDLM Environment • HP XP128/HP XP1024/HP XP10000/HP XP12000/HP XP20000/HP XP24000 • Thunder 9500V series • Lightning 9900V series • Hitachi AMS2000/AMS/WMS/SMS series • Hitachi NSC55 • Hitachi Universal Storage Platform 100 • Hitachi Universal Storage Platform 600 • Hitachi Universal Storage Platform 1100 • Hitachi Virtual Storage Platform • P9500 • SVS The applicable storage systems require a dual controller configuration.
3. Creating an HDLM Environment 3.1.3 Cluster Software Supported by HDLM The HDLM-related programs required when you combine cluster configurations are listed in Table 3-3: HDLM-Related Programs When Combining Cluster Configurations. Table 3-3: HDLM-Related Programs When Combining Cluster Configurations OS AIX 5L V5.3 Related Programs • HACMP 5.4 IY84920 • HACMP 5.4.1 • PowerHA 5.5 • PowerHA 6.1 • Oracle RAC 10g 10.1.0.5.
3. Creating an HDLM Environment OS Related Programs AIX 5L V5.3 (Virtual I/ O Server)#5 • HACMP 5.4 Client APAR: IY84920 Client: Technology Level 05 or later Server: ioslevel 1.5.1.1 to 1.5.2.1 • HACMP 5.4.1 Client: Technology Level 05 or later Server: ioslevel 1.5.1.1 to 2.2.0.xx (where xx is a number) • PowerHA 5.5 Client: Technology Level 07 or later Server: ioslevel 1.5.1.1 to 2.2.0.xx (where xx is a number) • PowerHA 6.1 Client: Technology Level 07 or later Server: ioslevel 2.1.0.0 to 2.2.0.
3. Creating an HDLM Environment OS Related Programs AIX V6.1 (Virtual I/O Server)#5 • HACMP 5.4.1 Client: Apply SP1 or later without using a Technology Level or with Technology Level 01 or later Server: ioslevel 1.5.1.1 to 2.2.0.xx (where xx is a number) • PowerHA 5.5 Client: Technology Level 02 or later Server: ioslevel 1.5.1.1 to 2.2.0.xx (where xx is a number) • PowerHA 6.1 Client: Technology Level 02 or later Server: ioslevel 2.1.0.0 to 2.2.0.xx (where xx is a number) • PowerHA 7.
3. Creating an HDLM Environment usePersistentReserve option to no in the GPFS cluster configuration information. #4 VxVM is not supported. #5 PowerVM Live Partition Mobility is supported only in an environment that uses the HDLM device as a virtual SCSI device. However, PowerVM Live Partition Mobility is not supported if the HDLM device used is an NPIV-based virtual HBA.
3. Creating an HDLM Environment Directory Disk capacity requirement p MB#1 +4MB + 2 MB + q MB#2 + 19 MB + 200 KB#3 /var #1 This value depends on the error log file settings. The maximum is 30,000 MB. p = (s x m) / 1024 (in MB), where: s is the size of the error log file (units: KB, default is 9,900), and m is the number of error log files (default is 2). The resulting fraction will be rounded up. #2 This value depends on the trace file settings. The maximum is 1000 MB.
3. Creating an HDLM Environment #1 The maximum number of LUs that can be recognized by a CHA port is 256. #2 If the reservation policy is PR_exclusive, and the Thunder 9500V series, or Hitachi AMS2000/AMS/WMS/SMS series is used, the number of supported paths to an LU is 1 to 32. For details on reservation policy, see 3.9 About the Reservation Policy.
3. Creating an HDLM Environment 3.2 Flow for Creating an HDLM Environment Set up the environment to use HDLM as follows.
3. Creating an HDLM Environment 3.3 Types of HDLM Installation This section describes the following HDLM installation types: new installation, upgrade installation, migration, and re-installation. New installation of HDLM Installing HDLM on a server where HDLM has not yet been installed is called a new installation.
3. Creating an HDLM Environment 3.4 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.4.1 Notes on Installing HDLM Install HDLM on the boot disk. To install HDLM, a license key is required. For more details, see the Notification of Software License Key provided with this package. Install HDLM in a multi-user mode environment.
3. Creating an HDLM Environment Re-installation in 3.5.5 Performing an Upgrade Installation or Re-installation of HDLM. If you upgrade or re-install HDLM before you resolve a path failure, LU reservations might persist without being released. In such a case, use the utility for clearing HDLM persistent reservations (dlmpr) to release the LU reservation, if necessary. Performing an upgrade installation or re-installation might change the physical volume (hdisk name).
3. Creating an HDLM Environment HDLM Drivers. 2. Execute the following command to reconfigure the HDLM device: # cfgmgr When the NPIV option is set to on, HBA adapter number and bus number for PathName, which are output by HDLM command view operations, are changed to adapter type and adapter number respectively.
3. Creating an HDLM Environment When you migrate from HDLM 05-00 or later Trace files before the migration: /var/opt/hitachi/HNTRLib2/spool/ hntr2n.log (n indicates a file number) Integrated trace files after the migration: /var/opt/hitachi/HNTRLib2/ spool/hntr2n.log (n indicates a file number) Trace files after the migration: /var/DynamicLinkManager/log/ hdlmtrn.log (n indicates a file number) 3.4.6 Notes on Storage Systems Do not change the vendor ID or product ID of a storage system.
3. Creating an HDLM Environment # /usr/DynamicLinkManager/bin/dlnkmgr view -sys When you use HACMP, GPFS, Oracle RAC 10g, Oracle RAC 11g, or VCS, settings such as script registration or the reservation policy setting are required. For details about the settings used for each cluster, see the following: For HACMP: 3.10 Settings for Using HACMP. For GPFS: 3.11 Settings for Using GPFS. For Oracle RAC 10g or Oracle RAC 11g: 3.12 Settings for Using Oracle RAC 10g or Oracle RAC 11g. For VCS: 3.
3. Creating an HDLM Environment 3.5 Installing HDLM When you install HDLM, Hitachi Network Objectplaza Trace Library will also be installed. The file path of the integrated trace information file of Hitachi Network Objectplaza Trace Library is /var/opt/hitachi/HNTRLib2/spool/ hntr2n.log, where n is the number of the integrated trace information file. 3.5.1 Available Installation Methods To install HDLM, use one of the following procedures: Use installux.sh. By using installux.
3. Creating an HDLM Environment where the replication is created is called an alternate disk. In addition to installing HDLM on a typical host, you can install it in the following environments: Boot disk You can install HDLM on a virtual I/O server. A virtual I/O server is a system that enables multiple client logical partitions to share one resource. HACMP environments HACMP is IBM's HA cluster software that runs on AIX.
3. Creating an HDLM Environment # Only upgrade installations and re-installations are supported. Table 3-8: Combination of Installation Methods that Are Available in an HACMP Environment and the Supported Installation Environments Installation method Installation environment Host Virtual I/O server Local boot disk environment Boot disk environment Local boot disk environment Boot disk environment installux.
3. Creating an HDLM Environment Installation on alternate disks (3) When Installing HDLM on Alternate Disks in 3.5.5 Performing an Upgrade Installation or Re-installation of HDLM To use SMIT, see the AIX documentation. (2) When Performing a Migration of HDLM Table 3-9: Combination of Available Migration Methods and Migration Environments lists the combinations of available migration methods and target environments.
3. Creating an HDLM Environment Table 3-10: Combinations of Migration Methods Available in an HACMP Environment and the Migration Environments Migration method Migration environment Host Virtual I/O server Local boot disk environment Boot disk environment Local boot disk environment #1 Boot disk environment installux.
3. Creating an HDLM Environment described in the following sub-sections on all hosts that comprise the cluster. (1) Perform Operations for HDLM Management-Target Devices If you have already defined physical volumes and have been running the HDLM management-target devices, perform the following procedure: 1. Terminate the processes of all applications that are accessing the HDLM management-target devices. 2. If necessary, back up all HDLM management-target devices to a medium such as tape. 3.
3. Creating an HDLM Environment (2) Set Up the Hardware Check the topology (Fabric, AL, etc.) and perform setup as appropriate. 1. Set up the storage system. For details on how to set up the storage system, see the maintenance documentation for the storage system. If you are using HACMP, see also 3.10.1 Storage System Settings of 3.10 Settings for Using HACMP. 2. Set up the Fibre Channel switches. For details on how to set up a Fibre Channel switch, see the documentation for the Fibre Channel switch.
3. Creating an HDLM Environment 2. Switch the kernel mode. When AIX is running, change the symbolic link for /usr/lib/boot/unix and /unix to switch the current kernel mode to the desired mode. • The path for the 64-bit kernel mode /usr/lib/boot/unix_64 • The path for the 32-bit kernel mode /usr/lib/boot/unix_up (for a uni-processor) /usr/lib/boot/unix_mp (for a multi-processor) 3. Execute the bosboot command. # bosboot -ad /dev/ipldevice 4. Restart the system. # shutdown -Fr 5.
3. Creating an HDLM Environment 1. Log in to AIX as the root user. If you are using a virtual I/O server, see the virtual I/O server documentation to log in to AIX. 2. If there is no directory for mounting the DVD-ROM, make the directory. # mkdir /cdrom cdrom is the desired directory name. Hereafter, cdrom is used for purposes of explanation. 3. Mount the DVD-ROM. # mount -r -v cdrfs /dev/cd0 /cdrom The /dev/cd0 part depends on the system. 4.
3. Creating an HDLM Environment 6. Execute the following command to make sure that the hdisk recognized as the device to be managed by HDLM has been deleted: # lsdev -Cc disk 7. Prepare the license key or license key file. • When only the license key has been provided Create the /var/DLM directory, and then, in this directory, create the license key file (dlm.lic_key). The following shows an example when the license key is 123456789ABCDEF: # mkdir /var/DLM # echo "123456789ABCDEF" > /var/DLM/dlm.
3. Creating an HDLM Environment installation of HDLM continues, but installation of HDLM components has failed. After installing HDLM, resolve the problem according to the KAPL09241-W message if necessary. 9. Execute the following command to make sure that the package is installed. # lslpp -la DLManager.mpio.rte Make sure that the fileset item in the output listing contains DLManager.mpio.rte, and all the displayed statuses are COMMITTED.
3. Creating an HDLM Environment 15. Change the fc_err_recov setting of the parent device (fscsin) to fast_fail. # chdev -l fscsin -a fc_err_recov=fast_fail 16. Verify that the settings for the parent device (fscsin) are enabled. Also, verify that the fc_err_recov setting has been changed to fast_fail. # lsattr -El fscsin fc_err_recov fast_fail FC Fabric Event Error RECOVERY Policy TRUE 17. Repeat steps 14 to 16 for each parent device (fscsin) being used. 18. Enable the defined parent device (fscsin).
3. Creating an HDLM Environment hdisk3 hdisk4 ... Available 1H-08-02 Available 1H-08-02 Hitachi Disk Array (Fibre) Hitachi Disk Array (Fibre) Make sure that the status of all displayed hdisks is Available. hdisks 0 to 2 are the physical device file names for the host's internal disks. hdisk 3 and the following are the logical device file names that correspond to physical volumes in the storage system. 22.
3. Creating an HDLM Environment x.x.x-xx is the installed version of HDLM. 24. From the execution result of the view operation, check that the programs are running properly. If HDLM Manager, HDLM Alert Driver, and HDLM Driver are all Alive, all programs are running correctly. If you are not using a virtual I/O server, go to step 28. 25. If you are using a virtual I/O server, define an hdisk as a virtual target device.
3. Creating an HDLM Environment 30. Check the path configuration according to the procedure described in 3.6 Checking the Path Configuration. (2) When Installing HDLM in a Boot Disk Environment To perform a new installation of HDLM: 1. Use a single-path configuration for host and storage systems. 2. Log in to AIX as the root user. If you are using a virtual I/O server, see the virtual I/O server documentation to log in to AIX. 3. If there is no directory for mounting the DVD-ROM, make the directory.
3. Creating an HDLM Environment The KAPL10529-I message is displayed. If the KAPL10529-I message is not displayed, the HDLM management-target device has not been deleted. Make sure that no processes, services, file systems, or volume groups are using any HDLM management-target paths, and then re-execute the above utility. Note that an hdisk recognized as a boot disk will not be deleted. 7.
3. Creating an HDLM Environment or # installp -aXgd /directory-copied-from-DVD-ROM/HDLM_AIX all Even though a message asking you to restart the host is displayed during installation, you do not have to restart the host. If the KAPL09172-E message is displayed, the hdisk for the device that is managed by HDLM still remains. Re-execute the procedure starting from step 6. During installation, the KAPL09241-W message might be output.
3. Creating an HDLM Environment The following procedure assumes that hdisk10 is recognized as a boot disk: 16. Check the current boot disk list: # bootlist -m normal -o hdisk10 blv=hd5 hdisk0 blv=hd5 hdisk1 blv=hd5 ... 17. Specify boot disks that are suitable for your host environment: # bootlist -m normal hdisk10 hdisk0 hdisk1 18.
3. Creating an HDLM Environment 21. Verify that the settings for the parent device (fscsin) are enabled. Also, verify that the fc_err_recov setting has been changed to fast_fail. # lsattr -El fscsin fc_err_recov fast_fail FC Fabric Event Error RECOVERY Policy TRUE 22. Enable the defined parent device (fscsin). # cfgmgr -l fscsin 23. Repeat steps 19 to 22 for each parent device (fscsin) being used. 24.
3. Creating an HDLM Environment Make sure that the status of all displayed hdisks is Available. hdisks 0 to 2 are the physical device file names for the host's internal disks. hdisk 3 and the following are the logical device file names that correspond to physical volumes in the storage system. After executing the lspv command, if there is no hdisk other than the one that constitutes rootvg, re-execute the procedure starting from step 14. 27.
3. Creating an HDLM Environment x.x.x-xx is the installed version of HDLM. 29. From the execution result of the view operation, check that the programs are running properly. If HDLM Manager, HDLM Alert Driver, and HDLM Driver are all Alive, all programs are running correctly. If you are not using a virtual I/O server, go to step 33. 30. If you are using a virtual I/O server, define an hdisk as a virtual target device.
3. Creating an HDLM Environment When using HDLM in a cluster configuration, make sure to perform the operations described in the following sub-sections on all hosts that comprise the cluster. (1) Stop Applications HDLM manager stops during an upgrade installation or re-installation, so stop any applications that require HDLM manager operations before you start the upgrade installation or re-installation. (2) Perform Operations for HDLM Management-Target Device 1.
3. Creating an HDLM Environment # varyoffvg volume-group-name 3.5.5 Performing an Upgrade Installation or Re-installation of HDLM This subsection explains how to perform an upgrade installation from an earlier version, or how to re-install HDLM. Because HDLM version 5.8.1 or earlier cannot be upgraded to HDLM version 5.9 or later, migration is necessary. For details about migration, see 3.5.6 Migrating from HDLM Version 5.8.1 or Earlier to Version 5.9 or Later.
3. Creating an HDLM Environment When dlmrmdev is executed, a message is displayed asking you to continue processing. Enter y to continue processing. To inherit the existing hdisk configuration when the version of the installed HDLM is earlier than 6.2: # /directory-in-which-the-DVD-ROM-is-mounted/HDLM_AIX/hdlmtool/ dlmrmdev -e -A KAPL10528-I The volume group will be made inactive, and the file system that is using HDLM will be unmounted.
3. Creating an HDLM Environment hdisk7 deleted hdisk8 deleted hdisk9 deleted hdisk10 deleted KAPL09012-I All HDLM drivers were removed. • When the existing hdisk configuration has been successfully inherited, the KAPL10531-I message is displayed. If the KAPL10531-I message is not displayed, make sure that no processes, services, file systems, or volume groups are using any HDLM management-target paths, and then perform step 3 again.
3. Creating an HDLM Environment /DVD-ROM-mounted-directory/HDLM_AIX/hdlmtool/dlmrmdev • Deleting an existing hdisk When an existing hdisk is successfully deleted, the KAPL09012-I message is displayed. If the KAPL09012-I message is not displayed, make sure that no processes, services, file systems, or volume groups are using any HDLM management-target paths, and then re-execute the procedure of step 7.
3. Creating an HDLM Environment # echo "123456789ABCDEF" > /var/DLM/dlm.lic_key • When the license key file has been provided Store the license key file directly under the /var/tmp/ directory by using the hdlm_license name. /var/tmp/hdlm_license Note that the hdlm_license and dlm.lic_key files are deleted after installation finishes successfully. 10. Insert the HDLM DVD-ROM into the DVD-ROM drive.
3. Creating an HDLM Environment 12. For a re-installation, execute the following command: • When installing HDLM from the DVD-ROM # /directory-in-which-the-DVD-ROM-is-mounted/installux.sh or # installp -aXFd /directory-in-which-the-DVD-ROM-is-mounted/ HDLM_AIX all • When installing HDLM from the directory to which the DVD-ROM was copied # /directory-copied-from-DVD-ROM/installux.
3. Creating an HDLM Environment 15. Execute the following command and verify that the status of the hdisks is Available: # lsdev -Cc disk hdisk0 Available hdisk1 Available hdisk2 Available hdisk3 Available hdisk4 Available ... 1S-08-00-8,0 1S-08-00-9,0 1S-08-00-10,0 1H-08-02 1H-08-02 16 Bit LVD SCSI Disk Drive 16 Bit LVD SCSI Disk Drive 16 Bit LVD SCSI Disk Drive Hitachi Disk Array (Fibre) Hitachi Disk Array (Fibre) Make sure that all the displayed HDLM-related devices are Available.
3. Creating an HDLM Environment Alive x.x.x-xx yyyy/mm/dd hh:mm:ss 4000 HDLM Driver Ver WakeupTime x.x.x-xx yyyy/mm/dd hh:mm:ss Alive License Type Expiration Permanent KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss Even when cluster software is being used, the name of the cluster software is not displayed in Support Cluster. However, the cluster support function is operating normally. 19.
3. Creating an HDLM Environment # cfgmgr 23. Execute the following command in the client logical partition to confirm that the physical volume has been recognized as hdisk. If the following message is displayed, then the physical volume (hdisk) was recognized correctly.
3. Creating an HDLM Environment (2) When Installing HDLM in a Boot Disk Environment 1. Log in to AIX as a user with root permissions. If you are using a virtual I/O server, see the virtual I/O server documentation to log in to AIX. 2. Back up the HDLM settings. If an upgrade installation or re-installation fails, AIX automatically uninstalls HDLM, and the HDLM settings are deleted. Perform this step so that a copy of the HDLM settings is available in this case.
3. Creating an HDLM Environment hdisk configuration, use the dlmrmdev utility that is included in the installation DVD-ROM of the HDLM version to be installed. /DVD-ROM-mounted-directory/HDLM_AIX/hdlmtool/dlmrmdev • Deleting an existing hdisk When an existing hdisk is successfully deleted, the KAPL09012-I message is displayed.
3. Creating an HDLM Environment • When only the license key has been provided Create the /var/DLM directory, and then, in this directory, create the license key file (dlm.lic_key). The following shows an example when the license key is 123456789ABCDEF: # mkdir /var/DLM # echo "123456789ABCDEF" > /var/DLM/dlm.lic_key • When the license key file has been provided Store the license key file directly under the /var/tmp/ directory by using the hdlm_license name.
3. Creating an HDLM Environment procedure in step 6. If an upgrade installation ends with an error, HDLM might be uninstalled. In this case, proceed to step 13. During installation, the KAPL09241-W message might be output. In this case, installation of HDLM continues, but installation of HDLM components has failed. After installing HDLM, resolve the problem according to the KAPL09241-W message if necessary. 11.
3. Creating an HDLM Environment Make sure that the fileset item in the output listing contains DLManager.mpio.rte, and all the displayed statuses are COMMITTED. If one or more of the displayed statuses are BROKEN, uninstall HDLM, and then proceed to step 13 to perform a new installation of HDLM. 13. If HDLM was not upgraded or re-installed properly, perform a new installation of HDLM.
3. Creating an HDLM Environment The files beginning at hdisk3 are the names of the logical device files corresponding to the storage system's physical volumes. After executing the lspv command, if there is no hdisk other than the one that constitutes rootvg, re-execute the procedure starting from step 14. 16. Execute the dlnkmgr command's view operation to check the status of each program: # /usr/DynamicLinkManager/bin/dlnkmgr view -sys HDLM Version : x.x.
3. Creating an HDLM Environment running properly. If HDLM Manager, HDLM Alert Driver, and HDLM Driver are all Alive, all programs are running correctly. If you are not using a virtual I/O server, the upgrade installation or re-installation of HDLM is complete. For details about the files to be inherited after the upgrade installation or re-installation of HDLM, see Table 3-12: List of Files Inherited During an Upgrade Installation or Re-installation. 19.
3. Creating an HDLM Environment Table 3-12: List of Files Inherited During an Upgrade Installation or Re-installation File Description /usr/DynamicLinkManager/config/dlmmgr.xml File for setting up HDLM functionality /var/DynamicLinkManager/log/dlmmgr[1-16].log Log files of HDLM Manager /var/DynamicLinkManager/log/dlminquiry[1-2].log Log files of HDLM Inquiry information /usr/DynamicLinkManager/config/dlmwebagent.
3. Creating an HDLM Environment key file (dlm.lic_key). The following shows an example when the license key is 123456789ABCDEF: # mkdir /var/DLM # echo "123456789ABCDEF" > /var/DLM/dlm.lic_key • When the license key file has been provided Store the license key file directly under the /var/tmp/ directory by using the hdlm_license name. /var/tmp/hdlm_license Note that the hdlm_license and dlm.lic_key files are deleted after installation finishes successfully. 3. Insert the DVD-ROM into the DVD-ROM drive.
3. Creating an HDLM Environment 5. For a re-installation, execute the following command: • When installing HDLM on an alternate disk from the DVD-ROM # alt_disk_copy -d hdisk-name hdisk-name ... -I aXF -w DLManager.mpio.rte -l / directory-in-which-the-DVD-ROM-is-mounted/HDLM_AIX • When installing HDLM onto an alternate disk from the directory to which the DVD-ROM was copied # alt_disk_copy -d hdisk-name hdisk-name ... -I aXF -w DLManager.mpio.
3. Creating an HDLM Environment HDLM Alert Driver Ver WakeupTime ElogMem Size x.x.x-xx yyyy/mm/dd hh:mm:ss 4000 Alive HDLM Driver Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss License Type Expiration Permanent KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss Even when cluster software is being used, the name of the cluster software is not displayed in Support Cluster. However, the cluster support function is operating normally. 7.
3. Creating an HDLM Environment File Description /var/DynamicLinkManager/log/hdlmtr[1-64].log Trace files /var/DynamicLinkManager/log/dlmconfig[1-2].log Configuration log file /var/DynamicLinkManager/log/mmap/hdlmtr.mm Trace management file /var/DynamicLinkManager/log/dlmwebagent[1-16].log Hitachi Command Suite Common Agent Component log files /var/DynamicLinkManager/log/dlmutil[1-2].log HDLM utility's log file /var/DynamicLinkManager/log/mmap/dlmutil.
3. Creating an HDLM Environment unique_id : off HDLM Subclass : node KAPL10800-I The dlmodmset utility completed normally. # If the unique_id value is on, the unique_id method is being used. If it is off, the PVID method is being used. If the unique_id method is being used, proceed to step 8. 3. Execute the following command to activate the volume group that is using the virtual SCSI disk of the HDLM management-target hdisk: # varyonvg volume-group-name 4.
3. Creating an HDLM Environment O server: $ rmdev -dev vtscsin 10. Insert the DVD-ROM. 11. If there is no directory for mounting the DVD-ROM, make the directory. # mkdir /cdrom cdrom is the desired directory name. Hereafter, cdrom is used for purposes of explanation. 12. Mount the DVD-ROM. # mount -r -v cdrfs /dev/cd0 /cdrom The /dev/cd0 part depends on the system. 13. Back up the HDLM settings.
3. Creating an HDLM Environment Because HDLM version 5.9 or later requires deletion of hdisk, do not attempt to perform device configuration (cfgmgr command) before performing step 17. 16. Perform a new installation of HDLM version 5.9 or later. Perform steps 4 to 9 of (1) When Installing HDLM in a Local Boot Disk Environment in 3.5.3 Performing a New Installation of HDLM. Note that you do not have to perform steps 2 to 3. 17.
3. Creating an HDLM Environment # /usr/DynamicLinkManager/bin/dlmrmdev Check the file names for odm-environment-settings-file-name and set-environment-setting-file-name, and then perform this procedure again from step 17, specifying the correct file names in the command. 21. Delete the odm environment settings file and the set environment settings file.
3. Creating an HDLM Environment To upgrade or re-install HDLM in an environment that uses HACMP and a local boot disk: 1. Log in to AIX as the root user. If you are using a virtual I/O server, see the virtual I/O server documentation to log in to AIX. 2. Stop HACMP on the standby host. 3. Upgrade or re-install HDLM on the standby host. To do so, perform steps 2 through 23 in (1) When Installing HDLM in a Local Boot Disk Environment of 3.5.
3. Creating an HDLM Environment 6. Upgrade or re-install HDLM on the active host. To do so, perform steps 2 through 21 in (2) When Installing HDLM in a Boot Disk Environment of 3.5.5 Performing an Upgrade Installation or Re-installation of HDLM on the active host. 7. Start HACMP on the active host. (3) Migrating HDLM in an HACMP Environment When HDLM version 5.8.1 or earlier is migrated to HDLM version 5.
3. Creating an HDLM Environment # Name of the node being used. 6. Stop HACMP on the active host. Specify takeover as the shutdown mode. 7. Migrate HDLM on the active host. To do so, perform steps 10 to 26 in 3.5.6 Migrating from HDLM Version 5.8.1 or Earlier to Version 5.9 or Later on the active host. 8. Start HACMP on the active host. When HACMP starts, a warning message may be output, stating that the custom disk method file (/usr/DynamicLinkManager/cluster/ dlm_hacmp_gdisk_check) does not exist.
3. Creating an HDLM Environment 3.5.8 Performing an Unattended Installation of HDLM This subsection explains how to install HDLM using the installhdlm utility. The unused capacity required to execute the installhdlm utility is as follows: • /tmp directory 100 KB • Any log output directory that can be specified by users (the default directory is / var/tmp) 200 KB (1) When Installing HDLM in a Local Boot Disk Environment To install HDLM in a local boot disk environment: 1. Log in to AIX as the root user.
3. Creating an HDLM Environment The /dev/cd0 part depends on the system. 5. If you are using a copy of the installhdlm utility that you have placed in a separate directory to install HDLM, make sure you copy the necessary files from the /cdrom/HDLM_AIX/hdlmtool/instutil directory.
3. Creating an HDLM Environment • When only the license key has been provided Create the /var/DLM directory, and then, in this directory, create the license key file (dlm.lic_key). The following shows an example when the license key is 123456789ABCDEF: # mkdir /var/DLM # echo "123456789ABCDEF" > /var/DLM/dlm.lic_key • When the license key file has been provided Store the license key file directly under the /var/tmp/ directory by using the hdlm_license name.
3. Creating an HDLM Environment # /cdrom/HDLM_AIX/hdlmtool/instutil/installhdlm -f / any-directory/installation-information-settings-file Even though a message asking you to restart the host is displayed during installation, you do not have to restart the host. When installation is successful, the KAPL09211-I message is output. During installation, the KAPL09241-W message might be output. In this case, installation of HDLM continues, but installation of HDLM components has failed.
3. Creating an HDLM Environment 2. Log in to AIX as the root user. If you are using a virtual I/O server, see the virtual I/O server documentation to log in to AIX. 3. Insert the DVD-ROM. If you are installing HDLM from a directory in which files on the DVD-ROM are copied, make sure that the file organization has not been changed.
3. Creating an HDLM Environment For a new installation, proceed to step 8. 7. If you are upgrading or re-installing HDLM, back up the HDLM settings. If an upgrade installation or re-installation fails, AIX automatically uninstalls HDLM, and the HDLM settings are deleted. Perform this step so that a copy of the HDLM settings is available in this case. If an upgrade installation or re-installation fails, perform a new installation, and then re-execute setup to reflect the settings that have been backed up.
3. Creating an HDLM Environment 9. Create an installation information settings file. To use the sample file, copy it from the DVD-ROM to a directory on the hard disk. # cp -p /cdrom/HDLM_AIX/hdlmtool/instutil/ sample_installhdlm.conf /any-directory You can change the sample_installhdlm.conf file name. The following shows an example of copying the sample_installhdlm.conf file, and then changing the file name to install_set.conf: # cp -p /cdrom/HDLM_AIX/hdlmtool/instutil/ sample_installhdlm.
3. Creating an HDLM Environment # /cdrom/installux.sh -f /any-directory/ installation-information-settings-file To execute installhdlm: # /cdrom/HDLM_AIX/hdlmtool/instutil/installhdlm -f / any-directory/installation-information-settings-file Even though a message asking you to restart the host is displayed during installation, you do not have to restart the host. During installation, the KAPL09241-W message might be output.
3. Creating an HDLM Environment 14. Delete the created mount directory. # rm -r /cdrom 15. Delete the installation information settings file. # rm -r /directory-containing-the-installation-information-settings-file 16. Perform the procedure appropriate for the installation type. If you are performing a new installation, perform steps 15 to the end of the procedure described in (2) When Installing HDLM in a Boot Disk Environment of 3.5.3 Performing a New Installation of HDLM.
3. Creating an HDLM Environment 3.6 Checking the Path Configuration HDLM functions, such as load balancing and failover, are only available for HDLM management-target devices that have more than one active path. After you install HDLM or change the hardware configuration, check the structure and statuses of the paths. To check the path information, use the dlnkmgr command's view operation. The following describes how to check path information by using the dlnkmgr command's view operation.
3. Creating an HDLM Environment # lsdev -Cc disk > redirect-destination-file-2 2. Open both redirect-destination-file-1 and redirect-destination-file-2. 3. Make sure that all hdisk name displayed in the HDevName column in redirect-destination-file-1 are the same with hdisk name displayed on the Hitachi Disk Array (Fibre) row in redirect-destination-file-2.
3. Creating an HDLM Environment 3.7 Setting up HDLM HDLM includes functions like the load balancing function, the automatic failback function, the error logging function, the audit logging function, etc. You can set up these functions by using the dlnkmgr command's set operation. The following subsections describe these setup methods. 3.7.1 Checking the Current Settings This chapter describes how to check the HDLM function settings before any changes are made by using the dlnkmgr command's view operation.
3. Creating an HDLM Environment Table 3-14: The Recommended and Default Values of Each Function Function Load-balancing Path health checking Automatic failback Default value on on The Extended Least I/Os algorithm is used. The recommended algorithm depends on the operating environment. on on 30-minute check interval The recommended checking interval depends on the operating environment. on The recommended checking interval depends on the operating environment.
3. Creating an HDLM Environment Set it to on to enable load balancing. Otherwise, set it to off. When you set on, specify one of the following algorithm values after the -lbtype option: • rr for the Round Robin algorithm • exrr for the Extended Round Robin algorithm • lio for the Least I/Os algorithm • exlio for the Extended Least I/Os algorithm • lbk for the Least Blocks.
3. Creating an HDLM Environment If this happens, change any of the following settings: the checking interval for automatic failbacks, the intermittent error-monitoring interval, or the number of times that the error needs to occur. If you set the number of times that the error needs to occur to 1, the above condition does not need to be satisfied.
3. Creating an HDLM Environment on specifies that intermittent error monitoring is to be used. To disable intermittent error monitoring, specify off. When you set this parameter to on, you can specify intermittent error conditions by using the -intvl and -iemnum parameters. Specify the monitoring interval for an intermittent error in the -intvl parameter, and the number of times that the error needs to occur in the -iemnum parameter.
3. Creating an HDLM Environment You can set up the trace level for a trace file hdlmtrn.log (n indicates a file number from 1 to 64). Table 3-16: Values for the Trace Level Setting lists and describes the possible values for the trace level setting. Table 3-16: Values for the Trace Level Setting Value Description 0 No trace is output. 1 Only error information is output. 2 Program operation summaries are output. 3 Program operation details are output. 4 All information is output.
3. Creating an HDLM Environment size. # /usr/DynamicLinkManager/bin/dlnkmgr set -elfs 1000 Specify the size of the error log file in kilobytes. (8) Setting the Number of Error Log Files The number of the error log files (the HDLM manager log (dlmmgrn.log (n indicates a file number from 1 to 16))) can be set. You can specify a value from 2 to 16 for the number of error log files (log files for the HDLM manager).
3. Creating an HDLM Environment (10) Setting the Number of Trace Files You can set the number of the trace files. Trace files for which the number of files can be set are hdlmtrn.log (n indicates a file number from 1 to 64). For the number of the trace files, you can specify a value from 2 to 64. If you specify a value smaller than the value that has already been specified, the KAPL01097-W message will be displayed to confirm the execution, and the trace file will be temporarily deleted.
3. Creating an HDLM Environment Value (severity) Explanation 7 Table 3-18: Values Indicating Audit Log Data Categories describes the values that indicate audit log data categories. The default is all. Table 3-18: Values Indicating Audit Log Data Categories Value Explanation ss Audit log events of the StartStop category are collected. a Audit log events of the Authentication category are collected. ca Audit log events of the ConfigurationAccess category are collected.
3. Creating an HDLM Environment Value Corresponding facility value in the /etc/syslog.conf file local1 or 17 local1 local2 or 18 local2 local3 or 19 local3 local4 or 20 local4 local5 or 21 local5 local6 or 22 local6 local7 or 23 local7 This example shows how to specify the audit log facility: # /usr/DynamicLinkManager/bin/dlnkmgr set -audfac local0 3.7.
3. Creating an HDLM Environment # /usr/DynamicLinkManager/bin/dlnkmgr view -sys -audlog Audit Log : on(6) Audit Log Category : all Audit Log Facility : local0 KAPL01001-I The HDLM command completed normally.
3. Creating an HDLM Environment 3.8 Setting up Integrated Traces When HDLM is used, the dlnkmgr command logs are output to the integrated trace information files of Hitachi Network Objectplaza Trace Library (HNTRLib2) (/var/ opt/hitachi/HNTRLib2/spool/hntr2n.log (n indicates a file number)). If a lot of integrated trace information is output, the older information might end up getting deleted in a very short amount of time.
3. Creating an HDLM Environment If HNTRLib2 has already been installed on a host when you install HDLM, the settings in the trace library will be inherited. If a different Hitachi product is using HNTRLib2 when you attempt to uninstall HDLM, HNTRLib2 will not be uninstalled 3.8.2 Displaying the Hitachi Network Objectplaza Trace Library setup menu To display the Hitachi Network Objectplaza Trace Library setup menu: 1. Log on as a root user. 2.
3. Creating an HDLM Environment 1. In the Hitachi Network Objectplaza Trace Library setup menu, type 1 and then press the Enter key. A screen to set the size of the integrated trace file will appear. The current value is displayed in Current Size (KB). 2. Enter the desired size in New Size (KB). The specifiable range is between 8 KB and 8192 KB, with a default of 256. Set this to a value larger than that set in step 2 of 3.8.5 Changing the Buffer Size Per Monitoring Interval Duration.
3. Creating an HDLM Environment 2. Enter the desired number in New Number (KB). You can specify a value from 1 to 16. The default is 4. The value set here becomes the maximum of n in /var/opt/hitachi/HNTRLib2/spool/hntr2n.log. The recommended value for integrated trace collection is 8. If you do not want to change the number of integrated trace files, leave New Number (KB) blank, type !, and then press the Enter key to return to the Hitachi Network Objectplaza Trace Library setup menu. 3.
3. Creating an HDLM Environment 4. In the Hitachi Network Objectplaza Trace Library setup menu, type 5 and then press the Enter key. A screen to set the monitoring interval will appear. The current value is displayed in Current Span (sec). 5. Enter the desired interval in New Span (sec). The specifiable range is between 1 second and 300 seconds, with a default of 10. We recommend setting a value of 5 when collecting an integrated trace.
3. Creating an HDLM Environment 2. Enter a desired interval in New Span (sec). The specifiable range is between 0 and 3600 seconds, with a default of 0. We recommend setting a value of 0. To leave the monitoring interval as is, leave New Span (sec) blank, type ! and press the Enter key. You will be returned to the Hitachi Network Objectplaza Trace Library setup menu.
3. Creating an HDLM Environment When you specify a monitoring interval of 0 in 6: Lookout span, the value set in New Max (sec) will be disregarded. Also, when you specify a value of 0 for New Max (sec), even if you specify the monitoring interval in 6: Lookout span, the maximum number of messages output will not be adjusted. To leave the maximum number of messages output as is, leave New Max (sec) blank, enter ! and press the Enter key.
3. Creating an HDLM Environment Hitachi Dynamic Link Manager # 3. Stop the programs that are using HNTRLib2. If programs other than HDLM are displayed in step 2, stop the programs, and then go to step 4. You do not need to stop the HDLM manager. If you do not know how to stop and start programs other than HDLM, do not perform the following steps, and restart the host. 4. Execute the following command to stop the integrated trace collection process: # /opt/hitachi/HNTRLib2/bin/hntr2kill 5.
3. Creating an HDLM Environment 3.9 About the Reservation Policy The reservation policy settings are explained in the following table. Table 3-21: Reservation Policy Settings Setting Description no_reserve Ignores a reservation request and does not reserve an LU.
3. Creating an HDLM Environment 3.10 Settings for Using HACMP To use HACMP, install HDLM on all hosts comprising the cluster, configure the hdisks, set up the storage system (if using Thunder 9500V series, or Hitachi AMS/ WMS series devices), and register the HDLM script for HACMP. Also, set up the same reservation policy in all of the hdisks that are shared by multiple hosts in the cluster. 3.10.
3. Creating an HDLM Environment Choose the following sequence of menu items to display this window: Communications Applications and Services, HACMP for AIX, Extended Configuration, Extended Resource Configuration, HACMP Extended Resource Configuration, Configure Custom Disk Methods, and finally choose Add Custom Disk Methods. 2.
3. Creating an HDLM Environment 3.10.3 Setting the Reservation Policy When you use HACMP, we usually recommend that you set the reserve_policy attribute to PR_exclusive. However, when a virtual I/O function is applied in order to use HACMP in a client partition, use the following procedure to check, in the virtual I/O server partition, the settings for the reserve_policy attribute of the hdisk. If reserve_policy is set to PR_exclusive, change its value to no_reserve. 1.
3. Creating an HDLM Environment 3.11 Settings for Using GPFS To use GPFS or GPFS+RVSD, carry out the following procedure before starting GPFS or GPFS+RVSD: 1. To use GPFS+RVSD, add the following lines to the last line in the /etc/vsd/ oemdisktypes.
3. Creating an HDLM Environment 3.12 Settings for Using Oracle RAC 10g or Oracle RAC 11g 3.12.1 Settings for MISSCOUNT and DISKTIMEOUT When a host and an Oracle RAC voting disk are connected by multiple paths, HDLM performs failover processing for those paths (in the same way as for normal paths) when an I/O timeout occurs for one of the paths.
3. Creating an HDLM Environment Table 3-25: Formula for Calculating DISKTIMEOUT Storage system type • Hitachi AMS2000/AMS/WMS/ SMS series • Thunder 9500V series • • • • Hitachi USP Lightning 9900V series Universal Storage Platform V/VM Virtual Storage Platform Number of paths connected to the voting disk Formula for obtaining the value of DISKTIMEOUT 6 or less You do not need to change the value of DISKTIMEOUT.
3. Creating an HDLM Environment 4. Execute the following command to display all the activated volume groups. # lsvg -o 5. Among the displayed volume groups, inactivate the volume groups used by HDLM. # varyoffvg volume-group-name 6. Execute the chdev command to change the reserve_policy attribute to no_reserve. # chdev -l hdisk-name -a reserve_policy=no_reserve 7. Confirm that the setting was changed to no_reserve.
3. Creating an HDLM Environment 3.13 Settings for Using VCS To use VCS, install HDLM on all of the hosts that comprise the cluster, and then configure the HDLM devices. Also, carry out the following procedure before starting VCS: 1. Specify the settings for starting the preonline script when VCS starts. When you have specified the settings for starting the preonline script, go to step 2. For details on the setting method, see the VCS documentation.
3.
3. Creating an HDLM Environment 3.14 Uninstalling HDLM This section explains how to return the HDLM environment to the way it was before HDLM was installed, and describes each step of the process. 3.14.1 Preparations for HDLM Uninstallation Back up all HDLM management-target devices onto a medium such as a tape. Uninstall HDLM in a multi-user mode environment. When uninstalling HDLM on a host where version 5.
3. Creating an HDLM Environment 3. Execute the following command for the file system used to configure volume groups in the client logical partition: # mount file-system-mount-point 4. Execute the following command to back up the volume group in the client logical partition: # savevg -i -f any-file-name-or-device-volume-name volume-group-name 5. Execute the following command to unmount the file system in the client logical partition: # umount file-system-mount-point 6.
3. Creating an HDLM Environment for confirmation that processing is to continue. Enter y for this message to continue processing. # /usr/DynamicLinkManager/bin/dlmrmdev -A KAPL10528-I The volume group will be made inactive, and the file system that is using HDLM will be unmounted. Is this OK? [y/n]:y hdisk3 deleted KAPL09012-I All HDLM drivers were removed. • If you executed this step, proceed to step 16. • If you did not execute this step, proceed to the following step. 11.
3. Creating an HDLM Environment # lsdev -Cc disk 16. If GPFS + RVSD was used, delete the setting information from /etc/vsd/ oemdisktypes.
3. Creating an HDLM Environment If you are not using a virtual I/O server, uninstallation of HDLM is complete and you do not need to perform the remaining steps. If the KAPL09022-E message is displayed, the hdisks recognized as the devices to be managed by HDLM still remain. Re-execute the procedure starting from step 14. 21. If you are using a virtual I/O server, define an hdisk as a virtual target device.
3. Creating an HDLM Environment 2. Execute the following command to activate the volume group that is using the virtual SCSI disk of the HDLM management-target hdisk: # varyonvg volume-group-name 3. Execute the following command to mount the file system used to configure volume groups in the client logical partition: # mount file-system-mount-point 4.
3. Creating an HDLM Environment # shutdown -F 10. Configure the host and storage system so that only a single path connects the host to the storage system (single-path configuration). 11. Start the host. 12. Execute the following command to unmount the file system used by HDLM: # umount file-system-mount-point 13. Execute the following command to inactivate volume groups other than rootvg: # varyoffvg volume-group-name 14.
3. Creating an HDLM Environment If the KAPL13108-E message is displayed, the hdisk for the device that is managed by HDLM still remains. Re-execute the procedure starting from step 14. If the KAPL13110-E message is displayed, the multi-path configuration still remains. Re-execute the procedure starting from step 9. 17. Restart the host. # shutdown -Fr 18. If GPFS + RVSD was used, delete the setting information from the /etc/vsd/ oemdisktypes.lst file.
3. Creating an HDLM Environment # # # # rm /opt/VRTSvcs/bin/triggers/preonline haconf -makerw hagrp -modify service-group PreOnline 0 haconf -dump -makero 22. Execute the following command: # installp -u DLManager.mpio 23. Change the boot device list, according to the host environment you are using. If you are not using a virtual I/O server, uninstallation of HDLM is complete and you do not need to perform the remaining steps. 24.
3. Creating an HDLM Environment 3.14.3 Uninstalling Hitachi Network Objectplaza Trace Library (HNTRLib2) When you uninstall HDLM, if the KAPL09019-E or KAPL09020-E message is output, follow the directions below to uninstall HNTRLib2. To uninstall HNTRLib2: 1. Log in to AIX as the root user. 2. Execute the following command to unregister the name of the bundled program products. # /opt/hitachi/HNTRLib2/etc/hntr2cancel "Hitachi Dynamic Link Manager" 3. Execute the following command.
3. Creating an HDLM Environment than HDLM are using HNTRLib2, contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. Note If the log output directory set in HNTRLib2 was not the default directory, the log files will not be deleted during uninstallation. In this case, delete these files after uninstallation. 3.14.
3. Creating an HDLM Environment log files will not be deleted during uninstallation. In this case, delete these files after uninstallation. • Even if you attempt to uninstall HNTRLib2 when HNTRLib is installed, HNTRLib will not be uninstalled. If no other programs are using HNTRLib, delete it manually. 3.14.5 Canceling Cluster Software (HACMP) Settings When HACMP is used, delete the custom disk method. The following deletion procedure assumes that HACMP5.4 is used.
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. Some of the cautionary notes in 4.1 Notes on Using HDLM are different for HDLM 5.8.1 or earlier and HDLM 5.9 or later. In addition, the contents of 4.5 Changing the Configuration of the HDLM Operating Environment have changed. For details, see B. Differences Between HDLM Version 5.9 or Later and Version 5.8.
4. HDLM Operation 4.1 Notes on Using HDLM This section provides notes on using HDLM and using the environment in which HDLM is installed. Make sure that you read this section. 4.1.1 Displaying Path Information The AutoPATH_ID that is displayed during the HDLM dlnkmgr command's view operation differs depending on the order in which paths are detected when the host starts. For this reason, you should always use the path name to specify a path. 4.1.
4. HDLM Operation message, you can suspend the command. 4.1.3 Storage System Start up the storage system before you start up the hosts, so that AIX can detect the storage system. To delete an LU from the storage system, you must delete the hdisk first, and then you can delete the LU. If you change the storage system's owner controller for the LU, you must re-configure the hdisk or restart the server. 4.1.
4. HDLM Operation 4.1.6 Notes on Enabling Both Primary and Secondary Volumes to Be Viewed From the Same Server To enable both primary and secondary volumes to be viewed from the same server, operate the disks according to the following steps: 1. Create a pair of the primary volume and the secondary volume (paircreate). 2. Split the pair (pairsplit). 3. Enable the secondary volume to be recognized as a volume group (recreatevg).
4. HDLM Operation To cancel the reservation for the LU, execute the dlmpr utility from a host that can access this LU. For details on this utility, see 7.9 dlmpr Utility for Clearing HDLM Persistent Reservation. 4.1.9 Notes on Replicating a System You can use the OS's mksysb command to back up hosts that include HDLM-managed devices.
4. HDLM Operation 4.2 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.2.1 Notes on Using Commands Execute the command as a user with root permissions. To specify a parameter value containing one or more spaces, enclose the entire value in double quotation marks ("). 4.2.2 Viewing Path Information This section explains how to display path information by using an HDLM command.
4. HDLM Operation (1) Changing the Status of Paths to Online To change the status of paths to online: 1. Check the current status of the paths. To change the status of the path for each HBA port, CHA port, or path to online, first check the path name or AutoPATH_ID.
4. HDLM Operation (2) Changing the Status of Paths to Offline(C) To change the status of paths to Offline(C): 1. Check the current status of the paths. To change the status of the path for each HBA port, CHA port, or path to Offline(C), first check the path name or AutoPATH_ID. To change the path status to Offline(C) by specifying a host device name, first check the host device name for the path and the OS management path ID.
4. HDLM Operation # /usr/DynamicLinkManager/bin/dlnkmgr view -path 4.2.4 Viewing LU Information This section explains how to display LU information by using an HDLM command. To display LU information, execute the dlnkmgr command's view operation with the -lu parameter specified.
4. HDLM Operation You display this information by executing the HDLM command's view operation with the -drv parameter specified. For details on the view operation, see 6.7 view (Displays Information). The execution result of this operation is displayed on a single line for each path. The following shows an example in which the view operation is executed: # /usr/DynamicLinkManager/bin/dlnkmgr view -drv PathID HDevName OSPathID LDEV 000000 hdisk0 00000 9500V.0051.0005 000001 hdisk1 00000 9500V.0051.
4. HDLM Operation name = clear, completion time = yyyy/mm/dd hh:mm:ss # 3. Check to see whether the statistical information for all the paths has been initialized. The following shows how to execute the command: # /usr/DynamicLinkManager/bin/dlnkmgr view -path 4.2.7 Viewing and Setting Up the Operating Environment This section explains how to display and set up the HDLM operating environment.
4. HDLM Operation Audit Log Facility : KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss # For details on the displayed items and their descriptions, see 6.7 view (Displays Information). (2) Setting Up the Operating Environment To set up the HDLM operating environment, execute the dlnkmgr command's set operation.
4. HDLM Operation To check whether the settings have been applied, see (1) Viewing the Operating Environment. 4.2.8 Viewing License Information This section explains how to display license information. To display license information, execute the dlnkmgr command's view operation with the -sys and -lic parameters specified. The following shows an example in which the command is executed.
4. HDLM Operation KAPL01049-I Would you like to execute the operation? Operation name = set [y/n]: y KAPL01071-I A permanent license was installed. # 4.2.10 Viewing HDLM Version Information This section explains how to display HDLM version information. To display HDLM version information, execute the dlnkmgr command's view operation with the -sys parameter specified. The following shows an example in which the command is executed: # /usr/DynamicLinkManager/bin/dlnkmgr view -sys HDLM Version : x.x.
4. HDLM Operation which the command is executed: # /usr/DynamicLinkManager/bin/dlnkmgr view -sys HDLM Version : x.x.x-xx Service Pack Version : Load Balance : on(extended lio) Support Cluster : Elog Level : 3 Elog File Size (KB) : 9900 Number Of Elog Files : 2 Trace Level : 0 Trace File Size(KB) : 1000 Number Of Trace Files : 4 Path Health Checking : on(30) Auto Failback : on(60) Intermittent Error Monitor : off HDLM Manager Ver WakeupTime Alive x.x.
4. HDLM Operation 4.3 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.3.1 Starting the HDLM Manager To start the HDLM manager, log in to AIX as a user with root permissions and then execute the following command. # startsrc -s DLMManager Lower case characters can be used for the command name (dlmmanager).
4. HDLM Operation The stop script that was set up during HDLM installation runs, and stops the HDLM manager. Use the following dlnkmgr command's view operation to confirm that the HDLM manager has stopped. # /usr/DynamicLinkManager/bin/dlnkmgr view -sys -msrv HDLM Manager Ver WakeupTime Dead KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss # When the HDLM Manager column shows Dead, the HDLM manager is inactive.
4. HDLM Operation 4.4 HDLM Resident Processes Table 4-1: HDLM resident processes lists and describes the resident processes in HDLM. To monitor these processes, use the names below. Table 4-1: HDLM resident processes Process Description dlmmgr HDLM manager process hbsa_service Hitachi Command Suite Common Agent Component# process hntr2mon Hitachi Network Objectplaza Trace Library (HNTRLib2) process # You only need to monitor this process when HDLM is linked to Global Link Manager.
4. HDLM Operation 4.5 Changing the Configuration of the HDLM Operating Environment This chapter describes the procedures for changing the configuration of an HDLM operating environment. 4.5.1 Changing an HDLM Management-Target Device This subsection explains how to add and delete HDLM management-target devices and how to change their attributes.
4. HDLM Operation # /usr/DynamicLinkManager/bin/dlnkmgr view -path If you deleted all devices, check that the following message appears: KAPL01019-W The target path was not found. Operation name = view If you deleted a specific device, check that the deleted device (hdisk name) is no longer displayed. (3) Changing an HDLM Management-Target Device Note If you execute the chdev command while a path is in error status, that path will be deleted.
4. HDLM Operation instead of the dlmchpdattr utility to change the values actually used. The following explains how to use the dlmchpdattr utility to change default hdisk values, and apply them as the actually used values. If you execute the dlmchpdattr utility with the -A parameter specified, after the default values are changed, hdisks will be automatically reconfigured.
4. HDLM Operation 5. Execute the following command to make sure that the status of the hdisks recognized as HDLM-managed devices is Available. # lsdev -Cc disk hdisk0 Available hdisk1 Available hdisk2 Available hdisk3 Available hdisk4 Available ...
4. HDLM Operation either step 2 or 6, any changed values will not be applied, even though the lsattr command execution results will show that the changed values were applied. To apply the changed values, perform step 2, and then perform step 10 for a local boot disk environment, or perform step 12 for a boot disk environment. To manually reconfigure an hdisk: 1. Log in to AIX as a user with root permissions. Reconfigure the HDLM device.
4. HDLM Operation If the command terminates normally, the KAPL10531-I message is displayed. If the KAPL10531-I message is not displayed, make sure that HDLM-managed paths are not being used by a process, service, file system, or volume group, and then perform step 6 again. 7. Execute the following command to make sure that the status of the hdisks recognized as HDLM-managed devices is Defined.
4. HDLM Operation • If the execution environment is a boot disk environment: Proceed to step 11. 10. Execute the following command to change the hdisk status to Available. # cfgmgr After executing the command, proceed to step 13. 11. Execute the utility for clearing HDLM persistent reservation (dlmpr) for all hdisks comprising rootvg. # dlmpr -c name-of-HDLM-device-comprising-rootvg A message is displayed to confirm whether processing should continue. Enter y to continue processing.
4. HDLM Operation Make sure that the changed default value is reflected in the value actually used. # lsattr -El hdisk-name | grep reserve_policy reserve_policy no_reserve Reserve Policy TRUE 15. Activate the volume group used by HDLM. # varyonvg volume-group-name 16. Mount the file system used by HDLM. # mount file-system-mount-point 4.5.3 Changing a Path This subsection explains how to add and delete paths.
4. HDLM Operation # bootlist -m normal hdisk0 hdisk1 4. Make sure that the boot disk is configured with the specified number of paths. The following shows an example of executing the command: # bootlist -m normal -o hdisk0 blv=hd5 hdisk0 blv=hd5 hdisk1 blv=hd5 ... (3) Deleting a Path (of a Volume Group Other than rootvg) The following shows an example of deleting a path of a volume group other than rootvg. 1.
4. HDLM Operation # lspath -Hl hdisk10 -F "name path_id parent connection" name path_id parent connection hdisk10 hdisk10 hdisk10 0 1 2 fscsi4 50060e800436e240,6a000000000000 fscsi4 50060e800436e250,6a000000000000 fscsi5 50060e800436e240,6a000000000000 Search for lines in which the path_id item matches OS-management-path-ID. If matching lines are found, check the parent and connection entries.
4. HDLM Operation The following shows an example of executing the command: # bootlist -m normal hdisk0 hdisk1 4. Make sure that the boot disk is configured with the specified number of paths. The following shows an example of executing the command: # bootlist -m normal -o hdisk0 blv=hd5 hdisk1 blv=hd5 ... 4.5.
4. HDLM Operation Lun Reset Online(E) IO Block NPIV Option : off : on : off Check the NPIV Option line. 3. Place in Offline (C) status the path that goes through the HBA to be replaced. Depending on the NPIV option setting for the dlmodmset utility checked in step 2, execute one of the following commands: • If the NPIV option is set to off: Specify the HBA adapter number and bus number, and then execute the command shown below.
4. HDLM Operation HBA to the LUN security. 6. Execute the following command: # diag Note For details on the operations after executing the diag command, see the AIX documentation. Steps 7 to 14 below provide an example of the execution procedure for AIX V6.1 (Technology Level 02). 7. From the displayed menu, choose Task Selection. The Task Selection List window appears. 8. Choose Hot Plug Task. The Hot Plug Task window appears. 9. Choose PCI Hot Plug Manager. The PCI Hot Plug Manager window appears.
4. HDLM Operation 12. Go back to the PCI Hot Plug Manager window, select Replace/Remove a PCI Hot Plug Adapter. Select the HBA to be replaced. 13. Select Replace in the input field. 14. When the following message is displayed, replace the HBA: When you finish replacing the HBA, connect the cable and press Enter. 15.
4. HDLM Operation procedure when all the following conditions are satisfied#, the volume group cannot be activated after the host is restarted: • The host was shut down while a volume group was active, and the volume group consisted of hdisks that had paths going through the HBAs to be replaced. • The hdisk reservation policy for the hdisks that make up the volume group has been set to PR_exclusive.
4. HDLM Operation For details on path information, see 6.7 view (Displays Information). 7. Execute the utility for clearing HDLM persistent reservation (dlmpr) to clear the reservation of LUs comprising the applicable volume group: # /usr/DynamicLinkManager/bin/dlmpr -c hdisk-name hdisk-name ... 8.
4. HDLM Operation hdisk10 blv=hd5 hdisk0 blv=hd5 hdisk1 blv=hd5 ... 4.5.5 Replacing a Fiber Cable If there are multiple active paths for an LU, you can replace a desired cable while running your applications by placing offline only the path that goes through the cable to be replaced and using other paths to continue access. Note The following procedure is only for replacing a fiber cable. To replace a fiber cable: 1.
4. HDLM Operation • If the NPIV option is set to on: Use the fscsi number to execute the command below. The following example shows how to place the path in Offline (C) status when the path goes through fscsi number 1 (fscsi1): # /usr/DynamicLinkManager/bin/dlnkmgr offline -hba 00.01 3. Replace the cable. Note If you change the port on the Fibre Channel switch or on the storage system, the path configuration will be changed.
4. HDLM Operation # /usr/DynamicLinkManager/bin/dlnkmgr view -path For details about path information, see 6.7 view (Displays Information). 4.5.6 Replacing a Fibre Channel Switch If there are multiple active paths for 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 by using other Fibre Channel switches to continue access.
4. HDLM Operation Check the NPIV Option line. 3. Place in Offline (C) status the path that goes through the Fibre Channel switch to be replaced. Depending on the NPIV option setting for the dlmodmset utility checked in step 2, execute one of the following commands: • If the NPIV option is set to off: Specify the HBA adapter number and bus number, and then execute the command shown below.
4. HDLM Operation 6. Delete the HBA device associated with the Fibre Channel switch that is to be replaced. # rmdev -dl fscsin -R 7. Replace the Fibre Channel switch. 8. Execute the following command to reconfigure the HBA device: # cfgmgr -l fcsn fcsn indicates the name of the parent device that was acquired in step 5; n indicates the instance number of the fcs device. 9.
Chapter 5. Troubleshooting This chapter describes how to check HDLM error information, and how to take action if an error occurs in HDLM. Descriptions of the actions are separated into those for path errors, HDLM program errors, and other types of errors. 5.1 Information Collected by the DLMgetras Utility for Collecting HDLM Error Information 5.2 Checking error information in messages 5.3 What To Do for a Path Error 5.4 What To Do for a Program Error 5.
5. Troubleshooting 5.1 Information Collected by the DLMgetras Utility for Collecting HDLM Error Information Immediately after an error occurs, execute the DLMgetras utility for collecting HDLM error information, since restarting the machine might delete error information before the information is collected by DLMgetras. For details about the DLMgetras utility and the error information it collects, see 7.2 DLMgetras Utility for Collecting HDLM Error Information.
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 user for the name of the system function defined in the /etc/syslog.conf file. In the following example, the system function name is user, and messages at the Information level or higher are output to the /etc/syslog.conf file: user.info /tmp/syslog.user.log You can check path errors by referring to the KAPL08xxx messages that are output to syslog.
5. Troubleshooting The path name, which indicates a path. When you modify the system configuration or replace a hardware item, you should check the path names to identify the paths that will be affected by the change.
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.
5. Troubleshooting Figure 5-2: Troubleshooting procedure when a path error occurs The following shows the procedure for using the HDLM command (dlnkmgr) to handle a path error. 5.3.1 Examining the messages Examine the message that is output to syslog in the management-target host by using applications or tools for monitoring messages. If the KAPL08022-E message is output, view the message to check the path in which the error occurs. For details on each item displayed in the message, see 5.
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) or Online(E). 5.3.4 Narrowing Down the Hardware That Might Have Caused the Error Check the DskName , iLU , ChaPort , and HBAPortWWN columns of the path with the error to narrow down the hardware that may be the cause of the error.
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). 5.4.1 Examining the Messages Examine the message that is output to syslog in the host.
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 dlnkmgr command's view operation to check the status of the HDLM program, and then do whatever is necessary to resolve the problem. For details on the view operation, see 6.7 view (Displays Information).
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 DLMgetras utility to collect the HDLM error information, and then report the collected information to the HDLM vendor or maintenance company. For details about the DLMgetras utility and the information it collects, see 7.2 DLMgetras Utility for Collecting HDLM Error Information.
Chapter 6. Command Reference This chapter describes the HDLM command (dlnkmgr) and its operations. 6.1 6.2 6.3 6.4 6.5 6.6 6.
6. Command Reference 6.1 Overview of the HDLM Command dlnkmgr This section describes command formats and operations used for HDLM. Command format Enter the command using the following format: dlnkmgr operation-name [parameter [parameter-value]] dlnkmgr The command name. operation-name The type of operation entered after dlnkmgr. parameter A value required for an operation. parameter-value A value required for a parameter.
6. Command Reference • 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 (").
6. Command Reference 6.2 clear (Returns the Path Statistics to the Initial Value) The dlnkmgr command's clear operation clears the statistics (I/O count and I/O errors) of all paths that are managed by HDLM, and returns them to their initial value. 6.2.1 Format (1) To Set the Path Statistics to 0 /usr/DynamicLinkManager/bin/dlnkmgr clear -pdst [-s] (2) To Display the Format of the Clear Operation /usr/DynamicLinkManager/bin/dlnkmgr clear -help 6.2.
6. Command Reference (2) To Display the Format of the Clear Operation -help Displays the format of the clear operation. Example # /usr/DynamicLinkManager/bin/dlnkmgr clear -help clear: Format dlnkmgr clear -pdst [-s] KAPL01001-I The HDLM command completed normally.
6. Command Reference 6.3 help (Displays the Operation Format) The dlnkmgr command's help operation displays the list of operations available for the HDLM command, or the format of individual operations. 6.3.1 Format /usr/DynamicLinkManager/bin/dlnkmgr help [operation] [operation] ... 6.3.2 Parameter operation Specify the HDLM command operation whose format you want to know.
6. Command Reference # /usr/DynamicLinkManager/bin/dlnkmgr help online offline help online: Format dlnkmgr online [-path] [-s] dlnkmgr online [-path] { -hba HBAPortNumber.
6. Command Reference Format dlnkmgr help { clear | offline | online | set | view } KAPL01001-I The HDLM command completed normally.
6. Command Reference 6.4 offline (Places Paths Offline) The dlnkmgr command's offline operation places online paths offline. Specify the paths to be placed offline by specifying an HBA port, CHA port, single path, or host device. There must always be at least one online path accessing each LU. Placing too many paths offline might prevent paths from being able to switch if an error occurs. Before placing a path offline, use the view operation to check how many online paths remain.
6. Command Reference -hba HBA-adapter-number.bus-number Or -hba adapter-type.adapter-number Use this parameter to place offline, at one time, all the paths that pass through a specific HBA port. The command will place offline all the paths connected to the HBA port that has the specified HBA-adapter-number.bus-number or adapter-type.adapter-number.
6. Command Reference Example The following example shows how to place offline all paths connected to the HBA port whose HBA-port-ID is 00001. # /usr/DynamicLinkManager/bin/dlnkmgr offline -hbaid 00001 KAPL01102-I All the paths which pass the specified HBA port will be changed to the Offline(C) status. Is this OK? [y/n]:y KAPL01103-I If you are sure that there would be no problem when all the paths which pass the specified HBA port are placed in the Offline(C) status, enter y. Otherwise, enter n.
6. Command Reference 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 port are placed in the Offline(C) status, enter y. Otherwise, enter n. [y/n]:y KAPL01061-I 2 path(s) were successfully placed Offline(C); 0 path(s) were not. Operation name = offline # -chaid CHA-port-ID Use this parameter to place offline, at one time, all paths that pass through a specific CHA port.
6. Command Reference AutoPATH_IDs are re-assigned every time the host is restarted. When you want to add a new LU without restarting the host, AutoPATH_IDs are re-assigned to each path of the LU when you execute the cfgmgr command. Always make sure that you use the view operation to find the current AutoPATH_ID of the target path, before executing the offline operation. -hdev host-device-name -ospathid OS-management-path-ID Use this parameter to place offline path connected to the specified host device.
6. Command Reference The following example shows how to place a path, whose AutoPATH_ID is 000001, offline without asking for confirmation of command execution from the user: # /usr/DynamicLinkManager/bin/dlnkmgr offline -pathid 1 -s KAPL01061-I 1 path(s) were successfully placed Offline(C); 0 path(s) were not. Operation name = offline # (2) To Display the Format of the Offline Operation -help Displays the format of the offline operation.
6. Command Reference 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 HBA adapter number is 04 and bus number is 01. # /usr/DynamicLinkManager/bin/dlnkmgr view -path | grep 04.01 The above command will display information on all the paths that pass through the specified HBA port.
6. Command Reference 6.5 online (Places Paths Online) The dlnkmgr command's online operation places offline paths online. Specify the paths to be placed online by specifying an HBA port, CHA port, single path, or host device. 6.5.1 Format (1) To Place Paths Online /usr/DynamicLinkManager/bin/dlnkmgr online [-path] [-hba HBA-adapter-number.bus-number-or-adapter-type.
6. Command Reference -hba adapter-type.adapter-number Use this parameter to place online, at one time, all the paths that pass through a specific HBA port. The command will place online all the paths connected to the HBA port that has the specified HBA-adapter-number.bus-number or adapter-type.adapter-number. Specify the HBA adapter number and bus number, or adapter type and adapter number, of the target HBA port: the numbers are found in the PathName field displayed using the view operation.
6. Command Reference port will be changed to the Online status. Is this OK? [y/n]:y KAPL01061-I 15 path(s) were successfully placed Online; 0 path(s) were not. Operation name = online # -cha -pathid AutoPATH_ID Use this parameter to place online, at one time, all the paths that pass through a specific CHA port. The command will place online all the paths that pass through the CHA port to which the path with the specified AutoPATH_ID is connected.
6. Command Reference # /usr/DynamicLinkManager/bin/dlnkmgr view -cha For details about how to execute the view operation to display the CHA port IDs, see (5) To Display CHA Port Information in 6.7.2 Parameters. Example The following example shows how to place online all paths connected to the CHA port whose CHA-port-ID is 00001. # /usr/DynamicLinkManager/bin/dlnkmgr offline -chaid 00001 KAPL01104-I All the paths which pass the specified CHA port will be changed to the Online status.
6. Command Reference # /usr/DynamicLinkManager/bin/dlnkmgr view -lu For details on how to execute the view operation and display the host device name and OS management path ID, see (3) To Display LU Information in 6.7.2 Parameters. Only one set of values can be specified for the -hdev parameter. This parameter is not case sensitive. Example The following shows an example of placing online path for which the host device name is hdisk0 and OS management path ID is 00001 while confirming command operation.
6. Command Reference # /usr/DynamicLinkManager/bin/dlnkmgr online -help online: Format dlnkmgr online [-path] [-s] dlnkmgr online [-path] { -hba HBAPortNumber.
6. Command Reference The following example shows how to filter and display the information on all paths that pass through the CHA port 0A of the Thunder 9500V series: # /usr/DynamicLinkManager/bin/dlnkmgr view -path -stname | grep 9500V | grep 0A The above command will display information pertaining to only those paths that pass through the specified CHA port.
6. Command Reference 6.6 set (Sets Up the Operating Environment) The dlnkmgr command's set operation sets the HDLM operating environment. 6.6.
6. Command Reference Table 6-2: Default and Recommended Values Item name Load balancing Default value Recommended value on on The Extended Least I/Os algorithm is used. The recommended algorithm depends on the operating environment. Error log collection level 3: Collect error information for the 3: Collect error information for the Information level and higher. Information level and higher.
6. Command Reference rr: The Round Robin algorithm exrr: The Extended Round Robin algorithm lio: The Least I/Os algorithm exlio: The Extended Least I/Os algorithm lbk: The Least Blocks algorithm exlbk: The Extended Least Blocks algorithm The type of algorithm specified by the -lbtype parameter remains stored in the system, even when you disable the load balancing function by specifying -lb off.
6. Command Reference KAPL01001-I The HDLM command completed normally. Operation name = set, completion time = yyyy/mm/dd hh:mm:ss # -elfs error-log-file-size Specify a value from 100 to 2000000 (KB) for the size of the error log files (dlmmgrn.log (n indicates a file number from 1 to 16)). The specified value is used for HDLM manager logs. By specifying both the log file size and the number of log files, you can collect up to 32,000,000KB (approximately 30 GB) of error logs in total.
6. Command Reference time before existing information is overwritten becomes shorter. -systfs trace-file-size Specify the size of the trace file in kilobytes. Specify a value from 100 to 16000. When combined with the specification for the number of trace files, the maximum size of the trace files that can be collected is 1024000KB.
6. Command Reference The previously specified interval The explanation for the following sub-parameter describes how to specify the checking interval. -intvl checking-interval 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.
6. Command Reference When you specify on, specify the checking interval by specifying the parameter immediately following on.
6. Command Reference number-of-times-error-is-to-occur] | off } Enables or disables intermittent error monitoring. on: Enabled off: Disabled Intermittent error monitoring can be enabled only when automatic failback is set to on. When you use automatic failback, we recommend that you set intermittent error monitoring to on to prevent an intermittent error from reducing I/O performance.
6. Command Reference The following shows the sub-parameters that should be specified: the error monitoring interval and the number of times that the error is to occur: -intvl error-monitoring-interval Specify the monitoring interval for an intermittent error. Use a value from 1 to 1440 minutes. The default is 210.
6. Command Reference when -iem off is specified and intermittent error monitoring is disabled. Therefore, when you re-enable intermittent error monitoring without specifying the number of times, the error monitoring will be executed using the value stored in the system.
6. Command Reference Setting AFB Available operation IEM off off Result of operation on#2 off Set IEM to on. • When a path is being monitored (during a period of conditional intermittent error monitoring), the value of the error count and the elapsed monitoring time are reset to 0, and then intermittent error monitoring will restart. • When a path is not being monitored, nothing changes. Change the IEM settings.
6. Command Reference #2 Because automatic failback is off, intermittent error monitoring is disabled. Example The following example shows how to monitor for intermittent errors. # /usr/DynamicLinkManager/bin/dlnkmgr set -iem on -intvl 20 -iemnum 2 KAPL01049-I Would you like to execute the operation? Operation name = set [y/n]: y KAPL01001-I The HDLM command completed normally. Operation name = set, completion time = yyyy/mm/dd hh:mm:ss # -lic Specify this option for when a license is updated.
6. Command Reference Type Description Temporary license key# Temporary license key are used temporarily, for example, when a user needs to perform product evaluations. Temporary licenses keys are valid for 120 days after the installation. You cannot reuse a temporary license key. Emergency license key Emergency license keys are used temporarily, for example, when waiting for issuing a permanent license key to be issued. Emergency licenses keys are valid for 30 days after they are entered.
6. Command Reference Specifies the severity level of audit log data to be collected. Table 6-7: Values Indicating Audit Log Data Collection Levels describes the values that indicate audit log data collection levels. The default is 6. Table 6-7: Values Indicating Audit Log Data Collection Levels Value (severity) 0 Explanation No audit log data is collected. 1 2 Critical-level audit log data is collected. 3 Critical-level and Error-level audit log data is collected.
6. Command Reference Table 6-9: Values of the Audit Log Facility Value Corresponding facility value in the /etc/syslog.conf file user or 1 user local0 or 16 local0 local1 or 17 local1 local2 or 18 local2 local3 or 19 local3 local4 or 20 local4 local5 or 21 local5 local6 or 22 local6 local7 or 23 local7 -s Executes the command without displaying the message asking for confirmation of command execution from the user.
6.
6. Command Reference (pchk) Interval-Time { 1 - 1440 }(Minute) (Default Value 60) Error-Monitor-Interval { 1 - 1440 }(Minute) (Default Value 210) Number-Of-Times { 1 - 99 }(Times) (Default Value 3) AudlogLevel { 0 - 7 } (Default Value 6) Category-Value { [ss] [a] [ca] | (afb) all } (Default Value all) Facility-Name { user | local0 - local7 } Facility-Number { 1 | 16 - 23 } (Default Value user) (Default Value 1) KAPL01001-I The HDLM command completed normally.
6. Command Reference 6.7 view (Displays Information) The view option displays HDLM program information, path information, LU information, HBA port information, CHA port information, and the correspondences between hdisks, OS management path IDs, and LDEVs. 6.7.
6.
6. Command Reference (1) To Display Program Information (2) To Display Path Information (3) To Display LU Information (4) To Display HBA Port Information (5) To Display CHA Port Information (6) To Display the Correspondences Between hdisks, OS Management Path IDs, and LDEVs (7) To Display the Format of the View Operation (1) To Display Program Information -sys [-sfunc|-msrv|-adrv|-pdrv|-lic|-audlog] Displays the HDLM program information.
6. Command Reference Parameter and program information to be displayed Item Description Load Balance Settings for load balancing • Setting status: on: Enabled off: Disabled • Algorithm When the setting status of load balancing is on, one of the following types of algorithms is used for load balancing is displayed in the parentheses following on.
6. Command Reference Parameter and program information to be displayed -msrv Item Path Health Checking • Settings for path health checking: on: Enabled off: Disabled • Checking interval: When the setting of the path health checking is on, the checking interval of path health checking is displayed within the parentheses following on. The time is in minutes.
6.
6. Command Reference Parameter and program information to be displayed Item Description Audit Log Category The categories of audit log data to be output are displayed. When more than one category is displayed, commas (,) are used as separators. ss: StartStop a: Authentication ca: ConfigurationAccess If all the above categories are specified, all is displayed. If the collection of audit log data is disabled, a hyphen (-) is displayed. Audit Log Facility The name of the audit log facility is displayed.
6. Command Reference # Example 2 The following example shows how to display information about the HDLM manager. # /usr/DynamicLinkManager/bin/dlnkmgr view -sys -msrv HDLM Manager Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss # Example 3 The following example shows how to display information about the HDLM alert driver.
6. Command Reference Example 6 The following example shows how to display information about the audit log settings: # /usr/DynamicLinkManager/bin/dlnkmgr view -sys -audlog Audit Log : off Audit Log Category : Audit Log Facility : KAPL01001-I The HDLM command completed normally.
6. Command Reference Use this parameter to display the model ID of the storage system in the product ID element of the DskName field. When this parameter is omitted, the command displays the product ID or emulation type of the storage system instead. For details about the information displayed for product IDs, see Table 6-14: Product ID Displayed by the View -Path Operation. -iem Use this parameter to add IEP to path information and display information about intermittent errors.
6. Command Reference Parameters to display path information by selecting a display item: -path -item When you specify the -path parameter together with the -item parameter, the command only displays the items specified by the value of the -item parameter. If you specify no value for the -item parameter, only the PathID and the Status fields are displayed.
6. Command Reference Selectable items Sub-parameters IO-Errors ie DNum dnu HDevName hd IEP iep # Because both PathID and Status are always displayed, you do not have to specify any parameters. In the sub-parameters following -path -item, you can list the paths (-hdev) and sort the list (-srt). If you omit both parameters, the command displays information for all the paths in ascending order of AutoPATH_IDs.
6. Command Reference storage system (DskName), the second sorting key is the value specified by the -srt parameter, and the third sorting key is AutoPATH_ID. The available parameter values to specify the second sorting key are: • pn: Path name • lu: LU number of the storage system • cp: Port number of the CHA When the -srt parameter is omitted, the path information is listed in ascending order of AutoPATH_IDs.
6. Command Reference To display a summary of path information -path -c If the -c parameter is specified at the same time as the -path parameter, only PathID, DskName, iLU, CP, Status, and Type are displayed for the path information. The displayed contents are also shortened, so that each path information item is displayed on a single line. The items that are displayed are PathID, DskName, iLU, CP, Status, and Type. For details on what is displayed for each item, see Table 6-12: Displayed Path Information.
6. Command Reference 11 or more characters in the product ID, the 8th and following characters are abbreviated to ellipses (...). The sub-parameters (following -path -c) are: -stname Use this parameter to display the model ID of the storage system in the product ID element of the DskName field. When this parameter is omitted, the command displays the product ID or emulation type of the storage system instead.
6. Command Reference Displayed path information Table 6-12: Displayed Path Information describes the displayed path information. The following explains the table headings: • No summary displayed: The user specifies only the -path parameter or the-path -item parameter. • Summary displayed: The user specifies the -path -c parameter. Table 6-12: Displayed Path Information Displayed Item No summary displayed Description Summary displayed Paths Total number of displayed paths, indicated by a decimal (i.e.
6. Command Reference Displayed Item No summary displayed Description Summary displayed PathStatus Status of the displayed paths. The displayed status indicates the following: • Online: All paths are available. • Reduced: Some paths are not available. Reduced means that some paths might have an error status, in which case you should check the status of individual paths and resolve the problem for any paths that have an error status.
6. Command Reference Displayed Item No summary displayed Description Summary displayed iLU# iLU 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 the Lightning 9900V series, Hitachi Universal Storage Platform 100, Hitachi Universal Storage Platform 600, Hitachi Universal Storage Platform 1100, or Hitachi NSC55, indicated by a hexadecimal number.
6. Command Reference Displayed Item No summary displayed Description Summary displayed IO-Count# - Total I/O count for the path, indicated by a decimal number. The maximum value that can be displayed is 232 - 1 (4294967295). If the total I/O count reaches the maximum value, it will re-start from 0. To reset the IO-Count value to 0, execute the dlnkmgr command's clear operation. Executing the clear operation also resets the number of I/O errors (IO-Errors) to 0.
6. Command Reference # The path information is displayed only when a value is specified for the -path -item parameter.
6.
6. Command Reference When a summary is displayed by specifying the -path -c parameter and there are 11 or more characters in the summary string, any characters after the 9th character are not displayed,and ellipsis (...) are displayed instead. (3) To Display LU Information When displaying LU information, if the -item parameter, -c parameter, or the -c -item parameter is specified at the same time as the -lu parameter, you can add and display items and display a summary of LU information.
6.
6. Command Reference Item that can be added Subsequent parameter ChaPort cp CLPR clpr Type type IO-Count ic IO-Errors ie DNum dnu IEP iep VG vg All items are displayed all In the sub-parameters, -hdev or -pathid, you can filter the LU information to be displayed. If you omit both parameters, the command displays the information about all the LUs recognized by HDLM. For details on the contents of each displayed item, see Table 6-17: Displayed LU Information.
6. Command Reference To display a summary of LU information -lu -c When the -c parameter is specified with the -lu parameter, a summary of LU configuration information is displayed on one line. The total number of paths recognized by HDLM and the number of online paths are displayed for each LU.
6. Command Reference You cannot specify the -c parameter together with the -hdev or -pathid parameter. For details on the contents of each display item, see Table 6-17: Displayed LU Information. -t Does not display the title for each information item.
6. Command Reference Table 6-16: Items That Can Be Added by Using the -lu -c -item Parameter and Sub-parameters Item that can be added Sub-parameter SLPR slpr VG vg All items all The sub-parameter is: -t Omits the title for each information item. Example The following example describes how to add and display a summary of SLPR and VG. Displayed LU information Table 6-17: Displayed LU Information describes the displayed LU information.
6. Command Reference Table 6-17: Displayed LU Information Displayed item No summary displayed Summary displayed Model ID of the storage system Product Serial number Description S/N Serial number of the storage system LUs Total number of LUs managed by HDLM among the LUs in the storage system iLU LU number in the storage system This number combined with the storage system name (shown in DskName) identifies the LU that is accessed by a path.
6. Command Reference Displayed item No summary displayed Description Summary displayed PathName#1 - The path name, which indicates a path. When you modify the system configuration or replace a hardware item, you should check the path names to identify the path that will be affected by the change.
6. Command Reference Displayed item No summary displayed Description Summary displayed IO-Count#1 - Total I/O count for a path. The maximum value that can be displayed is 232 - 1 (4294967295). If the total I/O count reaches the maximum value, it is reset, and the count is re-started from 0. To reset the IO-Count value to 0, execute the dlnkmgr command's clear operation. Executing the clear operation also resets the number of I/O errors (IO-Errors) to 0. For details about the clear operation, see 6.
6. Command Reference Legend: -: Not displayed #1 This information is displayed when one of the following conditions exist: - The user selected the item to be displayed by using the -lu -item parameter. - all was specified. - No value was specified for the parameter. #2 This information is displayed when one of the following conditions exist: - The user selected the item to be displayed by using the -lu -c -item parameter. - all was specified. - No value was specified for the parameter.
6. Command Reference Item Description Number of online paths in the displayed paths, indicated by a decimal number. When the value of Paths equals the value of OnlinePaths, all paths are online. If the value of OnlinePaths is less than that of Paths, some paths are offline. In this case, you should check the offline paths and take appropriate action for any path that has an error status. OnlinePaths Example # /usr/DynamicLinkManager/bin/dlnkmgr view -hba HbaID Port.
6. Command Reference Item Description ChaPort Port number of the CHA, which identifies the CHA port that is mounted on the storage system. You can identify an actual CHA port by referencing this number from the storage system management program. IO-Count Total I/O count for the displayed paths, indicated by a decimal number. The maximum value that can be displayed is 232 - 1 (4294967295). If the total I/O count reaches the maximum value, it is reset, and the count is re-started from 0.
6. Command Reference and information about the LDEVs in a storage system (identified by the storage system model ID, serial number, and LU number, separated by periods). For details on the contents of each display item, see Table 6-20: Items Displayed as the Correspondences Between hdisks, OS Management Path IDs, and LDEVs. -t Does not display the title for each information item.
6. Command Reference (7) To Display the Format of the View Operation -help Use this parameter to display the view operation format. Example The following example shows how to display the format of the view operation.
6. Command Reference KAPL01001-I The HDLM command completed normally.
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 dlmchpdattr Utility for Changing HDLM Default Settings 7.4 dlmgetrasinst Utility for Collecting HDLM Installation Error Information 7.5 dlminstcomp Utility for HDLM Component Installation 7.6 dlmmigsts Utility for Assisting HDLM Migration 7.7 dlmodmset Utility for Setting the HDLM Execution Environment ODM 7.
7. Utility Reference 7.1 Overview of the Utilities HDLM provides the following utilities: • The DLMgetras utility for collecting HDLM error information When an error occurs, this utility collects the files that contain information to be submitted to your HDLM vendor or maintenance company. For details about the DLMgetras utility, see 7.2 DLMgetras Utility for Collecting HDLM Error Information.
7. Utility Reference that includes HDLM-managed devices. For details about the dlmpostrestore utility, see 7.8 dlmpostrestore Utility for HDLM Restoration Support. • The dlmpr utility for clearing HDLM persistent reservation The persistent reservation of a logical unit (LU) may not be canceled due to some reason when multiple hosts share a volume group rather than making up a cluster configuration using HACMP. In this case, this utility clears the Reservation Key to cancel the persistent reservation.
7. Utility Reference number of LUs and paths. Table 7-1: Examples of the Starting Time of the Host and the Execution Time of the Utilities lists examples of the starting time of the host and the execution time of the HDLM utilities.
7. Utility Reference The number of LUs is 256.
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: information such as error logs, integrated trace files, trace files, definition files, core files, system crash dump files, and libraries. The collected information is archived in a file and saved to the directory that you specified.
7. Utility Reference Specify the output directory for the information that is to be collected by the DLMgetras utility for collecting HDLM error information. The collected information is compiled into two files shown in Function and output in the specified directory. -f file-that-defines-information-to-be-collected Use this parameter when you want to specify certain directories or files to be collected.
7. Utility Reference 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. • Set up the specified file or directory so that it can be read by users with root permissions. The DLMgetras utility can only obtain information for a file or directory that can be read.
7. Utility Reference This file is output only when using the Hitachi Command Suite products that is the target for collecting error information. • getras.tar.Z This file contains HDLM information and system information. When you execute the DLMgetras utility, specifying the file that defines information to be collected, the getras.tar.Z file contains the information stored in the file that defines information to be collected. Table 7-2: Information Stored in the getras.tar.
7. Utility Reference Files Output directory#1 Explanation opt/hitachi/HNTRLib2/mmap hntr2mmap.mm Memory mapped file (HNTRLib2) integrated-trace-file-output-direct ory-specified-in-the-Hitachi-Netw ork-Objectplaza-Trace-Library-ut ility (Default: var/opt/hitachi/ HNTRLib2/spool) integrated-trace-file-prefix -specified-in-the-Hitachi-N etwork-Objectplaza-TraceLibrary-utility2[1-64].l Integrated trace file (HNTRLib2) opt/hitachi/HNTRLib/mmap hntrmmap.
7. Utility Reference Files Output directory#1 Explanation bootinfo.txt Information about the operation mode of the kernel (32/64 bit) and multi-CPU support bootlist-v.txt List of boot devices Config_Rules.txt Information of Object Database Manager crontab.txt crontab information CuAt.txt Information of Object Database Manager CuDv.txt Information of Object Database Manager CuDvDr.txt Information of Object Database Manager CuPath.txt Information of Object Database Manager CuPathAt.
7. Utility Reference Files Output directory#1 314 Explanation env.txt Environment variable file errpt-a.txt Error log edit file genkex.txt Information of loaded drivers hacmp.txt Information on the HACMP configuration histfile_xxxxx File specified in the HISTFILE environment variable iotool.txt Driver information lscfg.txt Firmware version of HBA etc lsdev-C.txt Kernel parameter value lsdev-proc.txt CPU information lsfs.txt File system information lslpp.
7. Utility Reference Files Output directory#1 usr/sbin Explanation ulimit-a.txt Limits on system resources (data segments, stack segments, file descriptors) that are available to processes uname-a.txt Information on the AIX version unix UNIX file whatlist.txt Information output by the what command kdb_64 Kernel debugger kdb_mp#3 kdb_up#3 etc/VRTSvcs/conf/config main.
7. Utility Reference 7.3 dlmchpdattr Utility for Changing HDLM Default Settings This utility changes the default value for the hdisk attribute. By changing the default value, the attribute value set for an hdisk can be changed in the following cases: • When a new hdisk is configured. • When the chdev command is used to set as defined, and then reconfigure, an existing individual hdisk for which the attribute value has not changed. • When deleting an existing hdisk#, and then reconfiguring it.
7. Utility Reference multiple pairs, separate them by using a space, and enclose the list of pairs in double quotation marks ("). Table 7-3 shows the attribute names and values that can be specified in the dlmchpdattr utility. Table 7-3: Attribute names and values that can be specified in dlmchpdattr Attribute names that can be specified in dlmchpdattr Values that can be specified reserve_policy Specifies the reservation policy to be used.
7. Utility Reference -o Displays the current value set for the reservation policy. -h Displays the format of the dlmchpdattr utility. Notes • Before you execute the dlmchpdattr utility, stop all application processes that access HDLM-managed devices. • Before you execute the dlmchpdattr utility, make sure that no path errors are occurring. If there are any errors, the dlmchpdattr utility might end with an error.
7. Utility Reference 7.4 dlmgetrasinst Utility for Collecting HDLM Installation Error Information This utility collects information that is needed to analyze errors that have occurred for some reason during installation of HDLM. The collected information is archived in a file and saved to the directory that you specified. The following files are output: • getrasinst.tar.Z This file contains compressed system information.
7. Utility Reference 7.4.3 List of Collected Error Information Table 7-4: Information Stored in the getrasinst.tar.Z File shows the error information collected by the dlmgetrasinst utility. Table 7-4: Information Stored in the getrasinst.tar.Z File Files Output directory# Explanation Directly under the directory to which collected information is output getrasinst.log dlmgetrasinst utility log file etc filesystems Mount information of the file system inittab inittab file syslog.
7. Utility Reference Files Output directory# Explanation CuVPD.txt Information of Object Database Manager disk.txt List of disks in the /dev directory dlmls-la.txt HDLM directory information file env.txt Environment variable file errpt-a.txt Error log edit file genkex.txt Information of loaded drivers histfile_XXXXX File specified in the HISTFILE environment variable lscfg.txt Firmware version of HBA etc lsdev-C.txt Kernel parameter value lsdev-proc.txt CPU information lsfs.
7. Utility Reference Files Output directory# Explanation ulimit-a.txt Limits on system resources (data segments, stack segments, file descriptors) that are available to processes uname-a.txt Information on the AIX version rootvginfo.txt rootvg information # An output directory is created in the specified directory when you open the getrasinst.tar.
7. Utility Reference 7.5 dlminstcomp Utility for HDLM Component Installation This utility complements HDLM installation. Execute this utility when both of the following conditions are satisfied: • Linkage with Global Link Manager is used • When HDLM is installed, the KAPL09241-W message is output# # Execute this utility after installing the JDK. For details about the JDK version to be installed, see the JDK required for linkage with Global Link Manager section in 3.1.1 Host and OS Support for HDLM. 7.5.
7. Utility Reference 7.6 dlmmigsts Utility for Assisting HDLM Migration This utility saves HDLM program information and the HDLM execution environment ODM settings, making it possible to inherit settings information when migrating from HDLM version 5.8.1 or earlier to version 5.9. Execute this utility from the HDLM version 5.9 installation DVD-ROM. 7.6.
7. Utility Reference -odm odm-environment-settings-file-name Specifies the file name in which the ODM environment settings are defined. Specify the file path. Specify a file name different from set-environment-settings-file-name. -set set-environment-settings-file-name Specifies the file name in which the set operation environment settings are defined. Specify the file path. Specify a file name different from odm-environment-settings-file-name.
7. Utility Reference 7.7 dlmodmset Utility for Setting the HDLM Execution Environment ODM This utility sets ODM to define HDLM operations. 7.7.1 Format /usr/DynamicLinkManager/bin/dlmodmset {{-r {on | off} | -i {on | off } | -v {on | off }} [-s] | -h | -o } 7.7.2 Parameters -r { on | off } Enables or disables the LUN RESET option. on: Enable off: Disable The default is off. To use GPFS, specify on. You do not need to reconfigure the hdisk or restart the host when you change this parameter.
7. Utility Reference parameter. Note When this parameter is set to on, I/O access to the Online(E) path will be suppressed, so I/O success will automatically change the path to the Online status. To recover the path, use an online command or the auto failback function. -v { on | off } Enables or disables the NPIV option. on: Enable off: Disable The default is off. To use HDLM in a client partition to which a virtual HBA is applied by using the NPIV functionality of the virtual I/O server, specify on.
7.
7. Utility Reference 7.8 dlmpostrestore Utility for HDLM Restoration Support This utility updates HDLM information to match that of the target system environment when a system replication (clone) is created from a mksysb image that includes HDLM-managed devices. 7.8.1 Format /usr/DynamicLinkManager/bin/dlmpostrestore [-s | -h] 7.8.2 Parameters -s Suppresses display of a confirmation message when the utility executes. -h Displays the format of the dlmpostrestore utility.
7. Utility Reference 7.9 dlmpr Utility for Clearing HDLM Persistent Reservation The persistent reservation of a logical unit (LU) may not be canceled due to some reason when multiple hosts share a volume group rather than making up a cluster configuration. In this case, this utility clears the Reservation Key to cancel the persistent reservation. 7.9.1 Format /usr/DynamicLinkManager/bin/dlmpr {{-k | -c} [hdisk-name] [hdisk-name] ... [-a] | -h} 7.9.
7. Utility Reference Specify the hdisk for which you want to display or clear the Reservation Key. You can specify more than one volume. If you omit this parameter, the utility assumes all hdisks. -a When multiple hdisks are specified, even if an error occurs during processing, the processing continues for all hdisks. -h Displays the format of the dlmpr utility.
7. Utility Reference In the following example, the utility displays Help: # /usr/DynamicLinkManager/bin/dlmpr -h Usage : dlmpr {{ -k | -c } [hdisk-name...
7. Utility Reference 7.10 dlmpreuninst Utility for Executed Before Uninstalling HDLM This utility excludes the hdisk recognized as a boot disk from being an HDLM management target. In a boot disk environment, before you uninstall HDLM you must exclude the hdisk recognized as a boot disk from being an HDLM management target. 7.10.1 Format /usr/DynamicLinkManager/bin/dlmpreuninst [-h | -s] 7.10.2 Parameters -h Displays the format of the dlmpreuninst utility.
7. Utility Reference 7.11 dlmrmdev Utility for Deleting HDLM Drivers This utility deletes hdisks or changes the status of hdisks to Defined according to the parameter settings. When all the hdisks recognized as HDLM management-target devices have been successfully deleted or changed to Defined, the HDLM manager stops. Note that the hdisk recognized as a boot disk will not be deleted or changed to Defined. 7.11.1 Format /usr/DynamicLinkManager/bin/dlmrmdev [[-e | -f] [-A [-s]] | -h] 7.11.
7. Utility Reference inactivates the volume group used by HDLM, and deletes all the hdisks recognized as HDLM management-target devices: # /usr/DynamicLinkManager/bin/dlmrmdev -A KAPL10528-I The volume group will be made inactive, and the file system that is using HDLM will be unmounted. Is this OK? [y/n]:y hdisk3 is deleted KAPL09012-I All HDLM drivers were removed.
7. Utility Reference 7.12 installhdlm Utility for Installing HDLM This utility is used to execute an unattended installation when a new installation, upgrade installation, or re-installation of HDLM is being performed. You can perform an unattended installation even when you are installing HDLM in a boot disk environment. Before you perform an unattended installation, you must define the information that is required during the installation in the installation information settings file.
7. Utility Reference Table 7-5: Keys in the [INSTALLATION_SETTINGS] Section Key name#1 Necessity of definition Description#2 New installat ion Upgrade installatio n or re-installa tion Maximu m number of charact ers installfile_location Specify the absolute path name of the directory in which the DVD-ROM is mounted or copied. The default is /dev/cd0. Optional Optional 60 logdir Specify the absolute path name of the directory in which the file that contains log information is output.
7. Utility Reference Key name#1 Necessity of definition Description#2 New installat ion Upgrade installatio n or re-installa tion Maximu m number of charact ers driver_config Specify one of the following values to indicate whether to configure the HDLM driver: y: Configure the HDLM driver (default). n: Do not configure the HDLM driver. In a boot disk environment, the HDLM driver is not configured, regardless of the value specified here.
7. Utility Reference If none of these files exist when you attempt to perform a new installation, unattended installation ends with an error. #4 When you perform a new installation of HDLM, or when you perform an upgrade installation while the license is expired, prepare the license key or the license key file. [DISK_DEFAULT_SETTINGS] section This section defines operation information for the HDLM default settings modification utility (dlmchpdattr). This section can be omitted.
7. Utility Reference Enter one key and one setting per line. #2 If the value is not of an allowable type, an error will occur. [ODM_SETTINGS] section Defines information used when the dlmodmset utility is executed. This section is optional. If this section name is omitted, or if any of the keys in the section are not defined, setup by means of the dlmodmset utility will not be executed. For details about the dlmodmset utility, see 7.7 dlmodmset Utility for Setting the HDLM Execution Environment ODM.
7. Utility Reference • For a new installation: The default value will be used. • For an upgrade installation or re-installation: The previous setting will be inherited. #1 Enter one key and one setting per line. #2 If the value is not of an allowable type, an error will occur. For details about the functions set by these keys, see 7.7 dlmodmset Utility for Setting the HDLM Execution Environment ODM.
7.
7. Utility Reference Key name#1 Description#2 Necessity of definition New installat ion Upgrad e installat ion or re-insta llation Maxim um numbe r of charac ters path_health_check Specify one of the following values to indicate whether to enable or disable the path health check function: on: Enabled (default) off: Disabled Optional Optional 3 path_health_check_in terval Specify the interval in minutes at which the path health check is performed. You can specify a check interval from 1 to 1440.
7. Utility Reference Optional: If a key and its setting are not specified, one of the following values will be used: • For a new installation The default value will be used. • For an upgrade installation or re-installation: The previous setting will be inherited. Note: Setting of audit logs is not supported. #1 Enter one key and one setting per line. #2 If the value is not of an allowable type, an error will occur. For details about the functions set by these keys, see 6.
7.
7. Utility Reference Therefore, delete the original installhdlm.log manually if it is no longer required. • If the installhdlm.log file cannot be output for some reason, such as there being insufficient capacity on the output disk, a message is output to this effect immediately before the installhdlm utility ends.
7. Utility Reference 7.13 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.5.3 Performing a New Installation of HDLM, 3.5.5 Performing an Upgrade Installation or Re-installation of HDLM, or 3.5.
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.14 Return Codes for Hitachi Command Suite Common Agent Component. 8.1 Before Viewing the List of Messages 8.2 KAPL01001 to KAPL02000 8.3 KAPL03001 to KAPL04000 8.4 KAPL04001 to KAPL05000 8.
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 • Terms used in the messages and message explanations This information is explained below. 8.1.1 Format and Meaning of Message IDs Each message has a message ID. The following shows the format and meaning of message IDs.
8. Messages 8.1.
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: clear, help, offline, online, set,or view bb...bb: Year/month/day hour:minute:second Action None. KAPL01002-I The HDLM command started. Operation name = aa...aa Details The HDLM command was executed. aa...aa: clear, offline, online, set, or view Action None. KAPL01003-W No operation name is specified.
8. Messages KAPL01005-W A parameter is invalid. Operation name = aa...aa, parameter = bb...bb Details aa...aa: clear, set, online, offline, or view bb...bb: Specified parameter Action Execute help operation-name of the HDLM command (dlnkmgr) to check the parameter, and then retry. For details on the help operation, see 6.3 help (Displays the Operation Format). KAPL01006-W A necessary parameter is not specified. Operation name = aa...
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: offline, online, set, or view bb...bb: Parameter name cc...cc: Specified parameter value dd...dd: Specifiable parameter value range Action Specify a correct value for the parameter, and then retry. KAPL01012-E Could not connect the HDLM manager. Operation name = aa...
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: clear, offline, online, set, or view Action Execute the command as a user with root permissions. KAPL01015-W The target HBA was not found. Operation name = aa...aa Details No path was found with the port number and path number, or the adapter type and adapter number, specified for the -hba parameter. aa...
8. Messages -cha), and check the target CHA port and the CHA ID of that CHA port. Then, specify the applicable CHA ID, and retry the operation. For details about the view operation, see 6.7 view (Displays Information). KAPL01018-W The target device was not found. Operation name = aa...aa Details The specified host device name could not be found. aa...aa: view Action Execute the view operation of the HDLM command (dlnkmgr view -path) to check the value displayed in HDevName.
8. Messages the DLMgetras utility, see 7.2 DLMgetras Utility for Collecting HDLM Error Information. KAPL01021-E Cannot execute the HDLM command due to insufficient memory. Details Memory required for HDLM command processing could not be allocated. Action Terminate unneeded applications to increase the amount of free memory, and then retry. KAPL01023-W The last Online path for the device cannot be placed Offline(C).
8. Messages KAPL01039-W During the online operation processing of the HDLM command, a path that cannot be placed in the Online status was detected. PathID = aa...aa Would you like to continue the processing of the online operation? [y/n]: Details A path that cannot be placed Online was detected during multipath online processing. To ignore this path and perform online processing for the next path, enter y. To cancel processing, enter n. aa...
8. Messages bb...bb: Parameter name cc...cc: Duplicate parameter value Action Delete the duplicate parameter value, and then retry. KAPL01045-W Too many parameter values are specified. Operation name = aa...aa, parameters = bb...bb, parameter value = cc...cc Details aa...aa: offline, online, set, or view bb...bb: Parameter name cc...cc: Parameter value Action Execute help operation-name of the HDLM command (dlnkmgr) to check the parameter value, and then retry. For details on the help operation, see 6.
8. Messages Statistics to the Initial Value). For details on the set operation, see 6.6 set (Sets Up the Operating Environment). KAPL01050-I The currently selected paths will be changed to the Online status. Is this OK? [y/n]: Details The online operation will be started. To continue the online operation, enter y. To cancel the operation, enter n. Action If you want to execute online processing, enter y. If you want to terminate processing, enter n. For details on the online operation, see 6.
8. Messages KAPL01053-I If you are sure that there would be no problem when the path is placed in the Offline(C) status, enter y. Otherwise, enter n. [y/n]: Details The offline operation will be started. To continue the offline operation, enter y. To cancel the operation, enter n. Action If you want to execute offline processing, enter y. If you want to terminate processing, enter n. For details on the offline operation, see 6.4 offline (Places Paths Offline).
8. Messages KAPL01056-I If you are sure that there would be no problem when all the paths which pass the specified aa...aa are placed in the Offline(C) status, enter y. Otherwise, enter n. [y/n]: Details This message re-asks the user whether they want to set place all the paths to Offline(C). To set all the paths to Offline(C), enter y. To cancel the operation, enter n. aa...aa: CHA port, HBA Action If you want to execute offline processing for the paths that meet the specified requirements, enter y.
8. Messages see 6.3 help (Displays the Operation Format). KAPL01059-W Cannot specify the parameter aa...aa at the same time if you specify parameter bb...bb and parameter value cc...cc. Operation name = dd...dd Details A parameter value is conflicting with the value of another parameter. bb...bb: Parameter name cc...cc: Parameter value aa...aa: Parameter name dd...dd: view or set Action Execute help operation-name of the HDLM command (dlnkmgr) to check the parameter and parameter value, and then retry.
8. Messages dd...dd: online, or offline Action None. For details on the online operation, see 6.5 online (Places Paths Online). For details on the offline operation, see 6.4 offline (Places Paths Offline). KAPL01063-I The target path(s) are already aa...aa. Details As a result of a previous online/offline operation, the specified path has already been set to Online/Offline(C). aa...aa: Online or Offline(C) Action Use the view operation of the HDLM command (dlnkmgr) to check the status of the path.
8. Messages was entered three times in a row. Action Obtain a valid license key, and then retry. KAPL01071-I The permanent license was installed. Details The license was renewed and is registered as a permanent license. Action None. 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.
8. Messages The license information file is missing. Action Re-install HDLM. KAPL01076-I The permanent license has been installed. Details You need not install a license because a permanent license has already been installed. Action None. KAPL01078-W The operation terminated because the path configuration changed during execution of the HDLM command. Operation name = aa...aa Details aa...aa: offline, online, view Action After the processing to change the path configuration has finished, retry.
8. Messages Set the intermittent error-monitoring interval to a value that is equal to or greater than (automatic-failback-checking-interval x number-of-times-error-is-to-occur-for-intermittent-error-monitoring). KAPL01081-E The license key file is invalid. File name = aa...aa Details The format of the license key file is invalid. aa...aa: /var/tmp/hdlm_license Action Save the correct license key file in the designated, and then re-execute.
8. Messages KAPL01084-W An attempt to delete the license key file has failed. File name = aa...aa Details aa...aa: /var/tmp/hdlm_license Action If a license key file exists, delete it. aa...aa: /var/tmp/hdlm_license KAPL01088-W The specified parameter values cannot be specified at the same time. Operation name = aa...aa, parameter = bb...bb, parameter values = cc...cc Details aa...aa:view bb...bb: Parameter name cc...
8. Messages KAPL01095-E An attempt to acquire the HDLM version information has failed. details = aa...aa Details aa...aa: Code showing the reason for the error Action Re-execute the command. If the same error occurs again, execute the DLMgetras utility for collecting HDLM error information, acquire the error information, and then contact your HDLM vendor or the company for which you have a service contract. KAPL01096-E An attempt to acquire the Service Pack version information has failed. details = aa..
8. Messages None. KAPL01101-W The target HBA port was not found. Operation name = aa...aa Details The HBA having the HBA_ID specified in the -hbaid parameter could not be found. aa...aa: offline, online Action Use the view operation of the HDLM command (dlnkmgr view -hba) to check the target HBA port and the HBA_ID of the target HBA port. After that, specify the appropriate HBA_ID, and then retry. KAPL01102-I All the paths which pass the specified aa...aa port will be changed to the Offline(C) status.
8. Messages Details Multiple paths will be collectively placed Online because the -hbaid or -chaid parameter was specified. To collectively place multiple paths Online, enter y. To not collectively place them Online, enter n. aa...aa: CHA, HBA Action If you want to execute the Online processing for the paths which pass the specified target, enter y. If you want to terminate the processing, enter n. KAPL01112-E An attempt to connect to the HDLM driver has failed. Operation name = aa...
8. Messages Restart the HDLM Manager, and execute the dlnkmgr view -sys -audlog command, and then specify the desired setting by using the dlnkmgr set -audlog command or the dlnkmgr set -audfac command as necessary. KAPL01115-W The audit log configuration file cannot be opened. Execute the "dlnkmgr view -sys -audlog" command and check whether a normal result is displayed. Details The audit log configuration file cannot be opened.
8. Messages Action Contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. KAPL01119-W An error occurred during processing to output the audit log configuration file. Details An internal parameter error when the audit-log data was output. Action Contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. KAPL01120-W A storage subsystem model ID could not be displayed. Details = aa...aa, bb...
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...
8. Messages aa...aa: API trace error information Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see 7.2 DLMgetras Utility for Collecting HDLM Error Information. KAPL03007-E An error occurred during communication with the HDLM manager. (aa...aa) Details This information is required for resolving problems. aa...
8. Messages contract for HDLM. For details on the DLMgetras utility, see 7.2 DLMgetras Utility for Collecting HDLM Error Information.
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 DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see 7.
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.
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 DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see 7.
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 DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see 7.2 DLMgetras Utility for Collecting HDLM Error Information. KAPL04021-I HDLM manager information - aa...
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 DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see 7.
8. Messages 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. Action Install a permanent license. KAPL04032-C A fatal error occurred in HDLM. The system environment is invalid Details A part of the HDLM configuration file is missing.
8. Messages KAPL04034-E An attempt to create the option definition file has failed. Details An attempt to re-create an option definition file (/usr/DynamicLinkManager/ config/dlmmgr.xml) using the default values has failed. Action Remove unnecessary files and secure unused capacity on the file system, Check the write permissions for the directory and file. KAPL04035-I The path health check will now start. Total number of paths = aa...aa Details aa...aa: Total number of paths Action None.
8. Messages Details All the paths that path health checking examined are fine. aa...aa: Start or stop Action None. KAPL04045-I HDLM SNMP TRAP was sent. Trap ID = aa...aa, IP Address = bb...bb, Port Number= cc...cc, Community = dd...dd, Trap Data = ee...ee Details SNMP TRAP was sent. aa...aa: Trap ID bb...bb: Destination IP address of the trap cc...cc: Destination port number of the trap dd...dd: Community name given to the trap ee...ee: Transmission data Action None.
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: Disk sequence number) and Partition (bb...bb: Fixed at 0) was successfully registered in the core logic. Action None. KAPL05008-E Could not allocate memory. (aa:bb) Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company.
8. Messages cc...cc: Error code (hexadecimal number) dd...dd: Filter driver management table address (hexadecimal number) Action Check whether the HDLM driver has started normally. If it has not started or contains an error, contact your HDLM vendor or the maintenance company, if there is a maintenance contract for HDLM, and report the error and detail code. KAPL05014-I The device object (aa...aa) was registered as the path (bb...bb). Details The path (bb...
8. Messages Action None. KAPL05023-E Could not process the IOCTL(aa). (aa:cc) Check the message of the HDLM command or the HDLM manager, and then take the appropriate action. If you do not know the appropriate action, execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company. Refer to the HDLM User's Guide for instructions how to execute the DLMgetras utility. Details Processing corresponding to the requested IOCTL (aa...
8. Messages Details The filter driver outputs this message for maintenance. aa...aa: Device minor number bb...bb: Message output location information cc...cc: Detailed information 1 dd...dd: Detailed information 2 Action None.
8. Messages 8.6 KAPL06001 to KAPL07000 KAPL06003-I Initialization of the HDLM alert driver (aa...aa) was successful. Details Initialization of the alert driver (aa...aa: alert driver management table address (hexadecimal number)) completed normally. Action None. 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...
8. Messages processed by the alert driver. bb...bb: error code (hexadecimal number) cc...cc: 0 (fixed) Action Check the message of the HDLM command (dlnkmgr) or HDLM manager, and then take the appropriate action. If you do not know the appropriate action, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM and report the error and detail code.
8. Messages When a log output request was made from the filter driver, the log information was discarded because of a memory allocation failure. Alternatively, although an emergency message (such as a path error message) detected by the core logic was generated as an output message, its log information was discarded by the HDLM alert driver. aa...aa: Message code (hexadecimal number) bb...bb: Buffer size (hexadecimal number) Action Check whether any other error occurred.
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 None.
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) • When the path error is detected by a path health checking or the online operation Displays 0x000F0000 (Fixed). • When a path error is detected through an I/O error The OS error code is displayed. cc...
8. Messages ee...ee: Target ID (hexadecimal number) ff...ff: Host LU number (same as PathName of view -path) (hexadecimal number) gg...gg: Dev number (same as DNum of view -path) (decimal number) hh...hh: Host device name Action There could be an error in the path. See 5.3 What To Do for a Path Error and restore the path displayed in the message to running status. KAPL08023-I A path was recovered. PathID = aa...aa, PathName = bb...bb.cc...cc.dd...dd.ee...ee, DNum = ff...ff, HDevName = gg...
8. Messages to the target LU. 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 view -path) (decimal (base-10) number) Action An intermittent error has occurred. Check the path for any possible problems. For details on what to do, see 5.
8. Messages 8.9 KAPL09001 to KAPL10000 KAPL09003-E Cannot install in this system. Install HDLM on a supported OS. Details HDLM cannot be installed on this system. Action See 3.1.1 Host and OS Support for HDLM and install HDLM on a supported OS. KAPL09011-E Cannot find a license key file "/var/DLM/dlm.lic_key". Details The license key file/var/DLM/dlm.lic_key is not in the specified directory. Action Create a license key file, and re-execute the installation program.
8. Messages Action Manually cancel the PP name registration, and then uninstall Hitachi Network Objectplaza Trace Library 2. If the attempt to cancel the registration of the PP name and to uninstall Hitachi Network Objectplaza Trace Library 2 fails again, contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM. KAPL09020-E An attempt to uninstall Hitachi Network Objectplaza Trace Library 2 failed. Details An attempt to uninstall HNTRLib2 has failed.
8. Messages 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. KAPL09024-E An attempt to copy a file or directory related to HDLM has failed. Refer to the Messages section of the HDLM User's Guide for instructions to correct this problem. Details An attempt to copy a file related to HDLM to the directory of Hitachi Command Suite products other than HDLM has failed.
8. Messages Details An attempt to install HNTRLib2 failed. Action Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM. KAPL09029-E This version of HDLM cannot be updated by installation. Uninstall the already installed version of HDLM. Action Uninstall the HDLM that has already been installed. KAPL09047-E Downgrading from aa...aa to bb...bb is not supported. Details Downgrade installation is not supported. aa...aa: DLManager.mpio.
8. Messages KAPL09077-I The temporary license was installed. The license expires on aa...aa. Details A temporary license was installed. aa...aa: Year (4 digits)/month (01-12)/day (01-31) Action Install a permanent license by the expiration day. 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.
8. Messages aa...aa: Year (4 digits)/month (01-12)/day (01-31) Action Install a permanent license by the expiration day. KAPL09082-W The temporary license expired. Action Enter a permanent license key. KAPL09083-W The emergency license expired. Action Install a permanent license. KAPL09087-E The entered license key is invalid. Renewal of the license key will now stop. Obtain a valid license key, and then re-install HDLM.
8. Messages KAPL09091-E A fatal error occurred in HDLM. The system environment is invalid. Contact your HDLM vendor or the maintenance company if there is a maintenance contract of HDLM. Details A part of the HDLM configuration file is missing. Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract of HDLM. KAPL09100-E Installation is not possible because aa...aa is already installed.
8. Messages There is no HDLM-installable license key in the license key file. aa...aa: /var/tmp/hdlm_license Action Make sure that the license key file is correct, and then re-install HDLM. /var/tmp/hdlm_license KAPL09114-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.
8. Messages use the output name, use the output command to overwrite or re-install. 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. Action Check the license by using the HDLM command's view -sys -lic operation. Then, if necessary, update the license by using the set -lic operation during or after installation.
8. Messages KAPL09171-E An internal error occurred in the installation of the HDLM. Error Code = aa...aa bb...bb Details A system-based error, not caused by the user, occurred during installation of HDLM processing. aa...aa:The error number which specifies the performed processing (decimal number) bb...bb:Return value of the executed processing (decimal number) Action If the error code is 3,nnnn: ODM is being used. Wait a while, and then try again.
8. Messages None. KAPL09187-W No parameter is specified. Details No installation-information settings file has been specified in the installhdlm utility for installing HDLM. Action Make sure that an actual installation-information settings file for the installhdlm utility is appropriate, and then try again. KAPL09188-W Too many parameters are specified. Details More than two parameters have been specified for the installhdlm utility for installing HDLM.
8. Messages KAPL09210-I aa...aa will now start. Details aa...aa has just started. aa...aa: installhdlm, installp, cfgmgr, dlmodmset, dlnkmgr, or dlmrmdev Action None. KAPL09211-I aa...aa completed successfully. Details aa...aa completed successfully. aa...aa: installhdlm, installp, cfgmgr, dlmodmset, dlnkmgr, or dlmrmdev Action None. KAPL09212-E aa...aa ended abnormally. Details aa...aa ended abnormally. aa...
8. Messages Check the error message that was output just before this message, and then perform the action indicated in that error message. KAPL09214-W A parameter is invalid. parameter = aa...aa Details A parameter is invalid. aa...aa: The specified parameter (character string) Action Specify the -h parameter for the installhdlm utility, confirm the parameter that should be specified, and then retry the operation. KAPL09215-E The system environment is invalid. Error Code = aa...
8. Messages If the error code is 6: You do not have write permission for the file system of the /var/tmp or / var/DLM directory. Make sure you have access permissions for the storage location of these directories. If the error code is 7: There is not enough unused capacity for the file system of the /var/tmp or /var/DLM directory. Make sure there is enough unused capacity for these directories.
8. Messages required, see 3.5.8 Performing an Unattended Installation of HDLM. KAPL09217-E An error occurred during reading of the installation information settings file. Error Code = aa...aa,bb...bb Details An error occurred while reading the installation information settings file. aa...aa: Error number (decimal number) that specifies the executed processing bb...
8. Messages KAPL09219-E An internal error occurred in the installhdlm_analysis. Error Code = aa...aa,bb...bb Details An internal error occurred in the installhdlm_analysis. aa...aa: Error number (decimal number) that specifies the executed processing bb...bb: Return value (decimal number) of the executed processing Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL09220-W The composition of the installation information settings file is invalid.
8. Messages KAPL09227-W The definition of the installation information settings file includes an invalid key. Error Code = aa...aa,bb...bb, line = cc...cc Details A key that does not exist is included. aa...aa: Error number (decimal number) that specifies the executed processing bb...bb: Return value (decimal number) of the executed processing cc...cc: Line number (decimal number) of an installation information settings file.
8. Messages operation. KAPL09230-W The definition of the installation information settings file includes a duplicated section name. Error Code = aa...aa,bb...bb, line = cc...cc Details A duplicated section name is included. aa...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.
8. Messages Specify the revised installation information settings file and then retry the operation. KAPL09233-W The definition of the installation information settings file is too long. Error Code = aa...aa,bb...bb, line = cc...cc Details The length of a single line of the definition exceeds 1023 characters. aa...aa: Error number (decimal number) that specifies the executed processing bb...bb: Return value (decimal number) of the executed processing cc...
8. Messages If the error code is 2: You do not have write permission for the log file destination directory. Modify your access permissions as necessary, and then retry the operation. If the error code is 3: You do not have write permission for the file system of the log file. Modify your access permissions as necessary, and then try again. If the error code is 4: You do not have write permission for the installhdlm.log file. Modify your access permissions as necessary, and then retry the operation.
8. Messages If the status of HDLM is not COMMITTED: Perform uninstallation or cleanup according to the displayed status. If an uninstallation or cleanup attempt fails, contact either your HDLM vendor or the maintenance company (if an HDLM maintenance contract exists). 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...
8. Messages If the error code is 200: Execute dlminstcomp utility. If any other error code is output: Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL09242-E No usable JDK or JRE exists. Details No prerequisite JDK version is installed in the system. Action Install a prerequisite JDK version, and then re-execute dlminstcomp utility. KAPL09243-I dlminstcomp completed successfully. Details dlminstcomp utility completed successfully. Action None.
8. Messages Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL09248-W A parameter is invalid. parameter = aa...aa Details An invalid parameter is specified. aa...aa: The specified parameter (character string) Action With the -h parameter specified, execute the dlminstcomp utility. Make sure that the format of the utility is correct, and then re-execute it. KAPL09504-E The language environments of HDLM and the Service Pack are different.
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 When the output information is an HDLM utility: • If an installation is performed from the DVD-ROM, confirm that the DVD-ROM is not damaged.
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 DLMgetras utility for collecting HDLM error information, and then retry. For details on the DLMgetras utility, see 7.2 DLMgetras Utility for Collecting HDLM Error Information. KAPL10002-W Too many parameters have been specified. Details Four or more parameters have been specified.
8. Messages Action Check the parameters of the DLMgetras utility for collecting HDLM error information, and then retry. For details on the DLMgetras utility, see 7.2 DLMgetras Utility for Collecting HDLM Error Information. KAPL10005-W The number of parameters is insufficient. Details The -f parameter exists but the file for defining the information to be collected does not exist. Action Check the parameters of the DLMgetras utility for collecting HDLM error information, and then retry.
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. 1. Check whether you have access permission for the specified directory. 2. Check whether the specified directory name is correct. 3. Check that the disk has sufficient unused capacity. KAPL10009-W The specified directory already exists.
8. Messages 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 DLMgetras utility for collecting HDLM error information terminates, check the contents of the file for defining the information to be collected. This file is shown in the message.
8. Messages number) bb...bb: Indicated contents in a line Action After the DLMgetras utility for collecting HDLM error information terminates, check the contents of the file for defining the information to be collected. This file is shown in the message. If the contents of the file are incorrect, correct them and then try to collect error information again. The DLMgetras will ignore the specified file and continue processing. For details on the DLMgetras utility, see 7.
8. Messages KAPL10016-W The root directory has been specified in the first parameter. Details A root "/" cannot be specified in a directory to which collected information is output. Action Check the parameters of the DLMgetras utility for collecting HDLM error information, and then re-execute. For details on the DLMgetras utility, see 7.2 DLMgetras Utility for Collecting HDLM Error Information. KAPL10017-W You lack privileges for executing the utility for collecting HDLM error information.
8. Messages utility, see 7.2 DLMgetras Utility for Collecting HDLM Error Information. KAPL10022-I The utility for collecting HDLM error information completed normally. Details Error information has been collected. Action None. For details on the DLMgetras utility, see 7.2 DLMgetras Utility for Collecting HDLM Error Information. KAPL10030-I A user terminated the utility for collecting HDLM error information.
8. Messages Details No file to collect information exists. aa...aa: File to collect Action None. KAPL10034-E The file could not be copied. Filename = aa...aa, Details = bb...bb Details Execution of the cp command failed. aa...aa: File name you tried to copy bb...bb: cp command output message Action An error occurred while the information collection file was being copied. The error might be a result of an unstable user environment. Check the system configuration.
8. Messages 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. KAPL10049-I Error information collection command = aa...aa, Return value = bb...bb, Execution time = cc...cc Details A command was executed to collect information targeted for collection. aa...
8. Messages Details aa...aa: failed file system (character string) Action Make sure of the status of the failed file system and then re-execute the program. Unmount the failed file system manually and re-execute the program. For details on the dlmrmdev utility, see 7.11 dlmrmdev Utility for Deleting HDLM Drivers. KAPL10524-E An attempt to inactivate the volume group has failed. (volume group = aa...aa) Details An attempt to inactivate the volume group has failed. aa...
8. Messages Action None. KAPL10527-I An attempt to inactivate the volume group has succeeded. (volume group = aa...aa) Details aa...aa: volume group succeeded (character string) Action None. KAPL10528-I The volume group will be made inactive, and the file system that is using HDLM will be unmounted. Is this OK? [y/n]: Details Notice unmount of the file system used by HDLM or inactivation of the volume group to prompt the users to make sure of the status.
8. Messages None. KAPL10532-E The status of one or more HDLM drivers could not be changed to "Defined". Action Check the hdisk status and re-execute the dlmrmdev utility. KAPL10551-I The dlmpostrestore utility completed successfully. Action None. KAPL10552-I Executing the dlmpostrestore utility will reconfigure the device. Is this OK? [y/n] : Details Executing the dlmpostrestore utility will reconfigure the device. Action To execute dlmpostrestore utility, enter y.
8. Messages Details Executing the dlmpostrestore utility will reboot the host. Action To execute dlmpostrestore utility, enter y. If you do not want to execute dlmpostrestore utility, enter n. KAPL10556-W The entered value is invalid. Re-enter. [y/n]: Details A value other than y or n has been entered for a [y/n] request. Action Enter either y or n. KAPL10557-I The user stopped the operation. Details The dlmpostrestore utility has been terminated because n was sent to a request. Action None.
8. Messages Action If the error code is 3.1: Confirm that all of the processes and services that use HDLM managed paths have stopped. After confirming that all the processes and services have stopped, restart them. Any other error code: Contact your HDLM vendor or the maintenance company, if you have an HDLM maintenance contract. KAPL10560-E The system environment is invalid. Error Code = aa...aa Details The system environment is not valid as an environment for executing the dlmpostrestore utility. aa.
8. Messages KAPL10573-W A parameter is invalid. parameter = aa...aa Details An invalid parameter is specified. aa...aa: The specified parameter Action With the -h parameter specified, execute the dlmchpdattr utility. Make sure that the format of the utility is correct, and then re-execute it. KAPL10574-W The specified parameters cannot be specified at the same time. parameter = aa...aa Details aa...aa: The specified parameter Action With the -h parameter specified, execute the dlmchpdattr utility.
8. Messages Action With the -h parameter specified, execute the dlmchpdattr utility. Make sure that the format of the utility is correct, and then re-execute it. KAPL10578-W An attribute value is invalid. attribute value = aa...aa Details An invalid attribute value is specified. aa...aa: The specified attribute Action With the -h parameter specified, execute the dlmchpdattr utility. Make sure that the format of the utility is correct, and then re-execute it.
8. Messages Details The dlmchpdattr utility has been stopped because an invalid response was sent three times consecutively to a request. Action To execute dlmchpdattr utility again, enter either "y" or "n". KAPL10583-E An internal error occurred in the dlmchpdattr utility. Error Code = aa...aa,bb...bb Details A system-based error, not caused by the user, occurred during dlmchpdattr utility processing. aa...aa: Error number (decimal number) bb...
8. Messages execution permissions for the dlmrmdev utility. Check the status of the dlmrmdev utility. If the error code is 6,2 or 7,-1: The bosboot command is not in the default location, or the user does not have execution permissions for the bosboot command. Check the status of the bosboot command. If the error code is 9,2 or 10,-1: The dlmpr utility is not in the default location, or the user does not have execution permissions for the dlmpr utility. Check the status of the dlmpr utility.
8. Messages aa...aa: Specified parameter value Action Specify an ODM that has been installed, and then retry the operation. KAPL10588-W A duplicate attribute has been specified. attribute = aa...aa Details A duplicate attribute has been specified. aa...aa: Specified attribute Action Delete the duplicate attribute, and then retry the operation. KAPL10641-I Reservation Key will now be cleared. Is this OK? [y/n]: Details Enter y to clear and n to not clear the Reservation Key. Action Enter y or n.
8. Messages KAPL10644-W The specified parameters cannot be specified at the same time. parameter = aa...aa Details The specified parameters cannot be specified for the dlmpr utility at the same time. aa...aa: specified parameter (character string) Action Execute the dlmpr -h utility to check the parameter, and then retry execution. For details on the dlmpr utility, see 7.9 dlmpr Utility for Clearing HDLM Persistent Reservation. KAPL10645-W A parameter value is invalid. parameter = aa...
8. Messages Action If a message with Error Code = 35 is output, check for the hdisk was deleted. If the hdisk was deleted, recover the state of the hdisk and then retry. If the KAPL10648-E message has been issued but the hdisk was not deleted, contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. If a message with Error Code = 36 is output, check for a path error. If there is a path error, restore the path status and then retry.
8. Messages The dlmpr utility has been terminated because n was sent to a request. Action None. KAPL10652-E The entered value is invalid. The operation stops. Details An invalid response was sent three times consecutively to a request. Action Re-execute the dlmpr utility. KAPL10653-W The entered value is invalid. Please re-enter it [y/n]: Details A value other than y or n has been entered for a [y/n] request. Action Enter y or n. KAPL10665-I The dlmpr utility completed.
8. Messages Details The dlmodmset utility completed normally. Action None. For details on the dlmodmset utility, see 7.7 dlmodmset Utility for Setting the HDLM Execution Environment ODM. KAPL10801-W No parameter has been specified. operation = aa...aa Details No parameter has been specified. aa...aa: Specified operation (character string) Action Execute help of the dlmodmset utility to check the parameters that can be specified, and then retry. For details on the dlmodmset utility, see 7.
8. Messages Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the dlmodmset utility, see 7.7 dlmodmset Utility for Setting the HDLM Execution Environment ODM. KAPL10805-I The setup of the HDLM execution environment ODM will be changed. aa...aa = bb...bb. Is this OK? [y/n]: Details We recommend that you report the setup of the HDLM execution environment ODM that you want to change to the user for confirmation. aa...
8. Messages Details No operation has been specified. Action Execute help of the dlmodmset utility to check the operations that can be specified, and then retry. For details on the dlmodmset utility, see 7.7 dlmodmset Utility for Setting the HDLM Execution Environment ODM. KAPL10810-W An operation is invalid. operation = aa...aa Details The specified operation is invalid. aa...
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 • Get HDLM Driver Status • Get HDLM Alert Driver Status • Get SNMP Trap Information • Set SNMP Trap Information • Set LU Load Balance • Get Path Status Log Information • Get Local Time Action None. KAPL11902-I aa...aa has started.
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 • 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 • Get Path Status Log Information • Get Local Time Action None.
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 • Get Path Status Log Information bb...bb: Error status returned from API (character string) Action Execute the DLMgetras utility for collecting HDLM error information to collect the error information, and then contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM.
8. Messages None. KAPL11907-I XML reception - aa...aa Details This information is required for resolving problems. aa...aa: XML information Action None. KAPL11908-I XML transmission - aa...aa Details This information is required for resolving problems. aa...aa: XML information Action None.
8. Messages 8.12 KAPL13001 to KAPL14000 KAPL13001-I The dlmmigsts utility completed successfully. Action None. KAPL13002-E The dlmmigsts utility ended abnormally. Action Refer to action of the message outputted just before this message. KAPL13003-I The specified file already exists. Do you want to overwrite it? [y/n]: Action To overwrite the specified file, enter y. To stop execution, enter n. KAPL13004-W The entered value is invalid. Re-enter. [y/n]: Action Enter either y or n.
8. Messages utility, see 7.6 dlmmigsts Utility for Assisting HDLM Migration. KAPL13008-W A parameter is invalid. parameter = aa...aa Details aa...aa: Parameter (character string) Action Specify the -h option in the HDLM migration support utility, confirm the option that should be specified, and then re-execute. For details about the dlmmigsts utility, see 7.6 dlmmigsts Utility for Assisting HDLM Migration. KAPL13009-W No parameter value has been specified. parameter = aa...aa Details aa...
8. Messages KAPL13012-W Too many parameters have been specified. Action Specify the -h option in the HDLM migration support utility, confirm the option that should be specified, and then re-execute. For details about the dlmmigsts utility, see 7.6 dlmmigsts Utility for Assisting HDLM Migration. KAPL13013-E The directory for storing the specified file could not be created. Filename = aa...aa Details aa...
8. Messages Migration. For details on the dlmodmset utility, see 7.7 dlmodmset Utility for Setting the HDLM Execution Environment ODM. If parameter = -set, execute dlnkmgr set one after another, or specify the modified dlnksetfile in dlmmigsts again, and then re-execute. KAPL13016-E The backup operation cannot be performed because DLManager.rte is not installed. Action Execute the dlmmigsts utility in an environment where DLManager.rte is installed.
8. Messages KAPL13021-E The file dlnksetfile was not restored. Action Check file name, and then try again. KAPL13101-I The dlmpreuninst utility completed successfully. Action None. KAPL13102-I HDLM can now be uninstalled. Action None. KAPL13103-I HDLM can be uninstalled after rebooting the host. Action None. KAPL13104-I The settings will be changed so that the HDLM driver is not configured on the hdisk. Is this OK? [y/n] Action To execute dlmpreuninst, enter y.
8. Messages KAPL13107-I The user stopped the operation. Details The dlmpreuninst utility has been terminated because n was sent to a request. Action None. KAPL13108-E An internal error occurred in the dlmpreuninst utility. Error Code = aa...aa, bb...bb Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company. Refer to the HDLM User's Guide for instructions how to execute the DLMgetras utility.
8. Messages Execute the dlmrmdev command, and then re-execute the dlmpreuninst. For details about the dlmrmdev utility, see 7.11 dlmrmdev Utility for Deleting HDLM Drivers.For details about the dlmpreuninst utility, see 7.10 dlmpreuninst Utility for Executed Before Uninstalling 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.
8. Messages Details An internal error occurred during processing to read the audit log configuration 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.
8. Messages 8.13 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. Command Line = aa...aa Details aa...aa: Name of the utility that the user executed KAPL15005-I Information of HDLM execution environment ODM was successfully displayed. Command Line = aa...aa Details aa...
8. Messages aa...aa: Name of the utility that the user executed KAPL15060-I DLMgetras was invoked. Command Line = aa...aa Details aa...aa: Name of the utility that the user executed KAPL15061-I DLMgetras successfully executed. Command Line = aa...aa Details aa...aa: Name of the utility that the user executed KAPL15080-I The information about the HDLM default configuration ODM was displayed successfully. Command Line = aa...aa Details aa...
8. Messages Details aa...aa: Name of the utility that the user executed KAPL15101-I Clear operation was completed successfully. Command Line = aa...aa Details aa...aa: Command that the user executed KAPL15102-E Clear operation has failed. Command Line = aa...aa Details aa...aa: Command that the user executed KAPL15103-I aa...aa path(s) were successfully placed bb...bb. cc...cc path(s) were not. Command Line = dd...dd Details aa...aa: Number of paths that were successfully placed online or offline bb.
8. Messages 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. Command Line = aa...aa Details aa...aa: Command that the user executed KAPL15109-I Information about HDLM-management targets was successfully displayed. Command Line = aa...aa Details aa...
8. Messages 8.14 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. Action Refresh the host information, check the path status, and then perform the operation again. 1003 Details No path was detected.
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. Action Update the host information, and then check the path status. 1017 Details The target path(s) are already Offline(C). Action Update the host information, and then check the path status.
8. Messages maintenance contract for HDLM. For details on the DLMgetras utility, see 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 DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or maintenance company if you have a maintenance contract for HDLM.
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. For details on the DLMgetras utility, see 7.2 DLMgetras Utility for Collecting HDLM Error Information.
8. Messages Refresh the host information, and then perform the operation again. If the same error occurs again, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or maintenance company if you have a maintenance contract for HDLM. For details on the DLMgetras utility, see 7.2 DLMgetras Utility for Collecting HDLM Error Information. 1041 Details An attempt to communicate with the HDLM manager has failed.
8. Messages utility, see 7.2 DLMgetras Utility for Collecting HDLM Error Information.
Appendixes A. Functional Differences Between Versions of HDLM B. Differences Between HDLM Version 5.9 or Later and Version 5.8.1 or Earlier C.
A. Functional Differences Between Versions of HDLM A. Functional Differences Between Versions of HDLM This section explains the functional differences between newer and older versions of HDLM. A.1 Functional Differences Between Version 6.2 and Versions Earlier than 6.2 In HDLM version 6.1.0 or earlier, when you create a system replication (clone) on another LPAR or host from an mksysb image by using the mksysb command provided by the OS, you needed to uninstall HDLM before executing the mksysb command.
B. Differences Between HDLM Version 5.9 or Later and Version 5.8.1 or Earlier B. Differences Between HDLM Version 5.9 or Later and Version 5.8.1 or Earlier HDLM version 5.9 or later supports MPIO used by AIX 5L V5.2 or later, which has improved compatibility with the OS. The items explained in the following subsections represent the changes from HDLM version 5.8.1 or earlier. B.1 Add-in HDLM Driver Module HDLM version 5.9 or later supports MPIO used by AIX 5L V5.2 or later.
B. Differences Between HDLM Version 5.9 or Later and Version 5.8.1 or Earlier B.2 Simplifying the HDLM Environment Configuration and Operation Procedures by Changes to the Logical Device Files The logical device files that can be controlled by the HDLM driver have been unified from HDLM devices (dlmfdrvn) to the hdisk provided by the OS. Therefore, logical device files controlled by HDLM can be configured by AIX's standard cfgmgr command.
B. Differences Between HDLM Version 5.9 or Later and Version 5.8.1 or Earlier • 4.6.1 Notes on changing the configuration of the HDLM operating environment • 4.6.6 Changing the configuration of an HDLM device • 4.6.7 Reconfiguring an HDLM device without changing its name Eliminating the rc.shutdown file HDLM version 5.8.1 or earlier provided an rc.shutdown file in order to avoid having physical volumes already defined when a host is started. Because this situation does not occur in HDLM version 5.
B. Differences Between HDLM Version 5.9 or Later and Version 5.8.
B. Differences Between HDLM Version 5.9 or Later and Version 5.8.1 or Earlier • Settings when GPFS is used • Replacement of HBA • Changing HDLM management-target devices • Replacement of fiber cables • Replacement of fibre channel switches # An update installation refers to upgrading HDLM whose version is 5.9 or later. Therefore, it does not include a migration from HDLM version 5.8.1 or earlier to HDLM version 5.9 or later. It also does not include a migration from HDLM version 5.
B. Differences Between HDLM Version 5.9 or Later and Version 5.8.1 or Earlier The dlmpreuninst utility excludes, before you uninstall HDLM, the hdisk recognized as a boot disk from being an HDLM management-target device. B.6 About Settings when Upgrading the OS (1) Eliminating Settings when Upgrading the OS There is no required procedure in HDLM for when the OS is upgraded, so the explanation in (1) Settings for an OS Upgrade in 4.6.
C. Glossary C. Glossary This glossary explains the terms used in this manual. A automatic failback A function for checking the status of paths at regular intervals, and automatically placing the status of a path recovered from an error into the Online status. If a path with an Offline(E) or Online(E) status recovers from an error, an automatic failback will place the path Online.
C. Glossary D Dev (Device) A logical division of an LU that HDLM controls and operates. A Dev is equivalent to a logical volume in AIX. In an AIX environment, each LU has only one Dev. Each Dev has a Dev number. Depending on the access method, Devs are classified into two types: block devices and character devices. (See also: Dev number) Dev number A number that is assigned to a device within an LU. The device numbers are assigned sequentially from 0. A Dev number is called a logical volume number in AIX.
C. Glossary configurations where the host and storage units are connected via a FC connection. HDLM alert driver A program that receives information about an error detected by the HDLM driver, and then reports the error information to the HDLM manager. HDLM driver A program that controls all the HDLM functions, manages paths, and detects errors. HDLM manager A program that manages error information. The HDLM manager receives error information from the HDLM alert driver and then collects error logs.
C. Glossary LU. HDLM uses this value to identify a particular LU. load balancing A function for distributing the load across all the paths that are accessing the logical areas within an LU. To distribute the load, load balancing uses multiple paths to perform I/O operations.
C. Glossary (See also: owner path, non-owner controller) O ODM (Object Data Manager) An AIX-dedicated database for managing system information. HDLM uses ODM to add or delete drivers. owner controller A controller that has been set as an owner controller for an LU. Owner controllers are only in the Thunder 9500V series, or Hitachi AMS/WMS series. A controller other than an owner controller is called a non-owner controller.
C. Glossary path name The path name consisting of the following four elements, separated by periods: • HBA adapter number or adapter type (character string) • Bus number or adapter number (character string) • Target ID (hexadecimal number) • Host LU number (hexadecimal number) A path name is used to identify a path.
C. Glossary slot number A value indicating the location of a slot on which a HBA is mounted. SLPR (Storage Logical Partition) A function supported by Hitachi USP, Universal Storage Platform V/VM, and Virtual Storage Platform for logically splitting up a storage system. This function splits up the resources, such as ports, CLPR, and volumes, in the storage system, so that the user can manage each resource independently.
Index A abbreviations defined ii active host 55 adapter number 285 adapter type 285 adapter number 72 adapter type 72 audit log categories and audit events that HDLM can output 45 collecting data 44 data format 50 automatic failback 26, 254, 475 automatic failover 21 automatic path switching 21 AutoPATH_ID 7, 475 B base 10 281 boot disk environment 475 buffer size 147 changing the buffer size per monitoring interval duration 150 bus number 285 C CHA 8 CHA (Channel Adapter) 475 changing HDLM default settin
Index Displayed program information 268 displaying information 266 LU information 287 path information 266, 274 path information (by selecting a display item) 266 program information 266, 268 summary of path information 266 dlmchpdattr 316 DLMgetras 224, 226 dlmgetras 308 dlmgetrasinst 319 dlminstcomp 323 dlmmigsts 324 dlmodmset 326 dlmpostrestore 329 dlmpr 330 dlmpreuninst 333 dlmrmdev 334 dlnkmgr 227 DNum 220 E emulation type 476 Error 42 error information 41, 43 checking in messages 219 collecting with
Index path error 221 HBA 8 host bus adapter replacing 205 HBA (Host Bus Adapter) 476 HBA adapter number 285 HDev 11 HDevName 220 HDLM features 4 functions 5 installing 75 Migrating 117 migration of 69 new installation 82 new installation of 69 overview 1 preparations for an upgrade installation or reinstallation of 95 preparations for new installation of 79 program information 268 re-installation of 69 setup 136 system configuration 7 type of installation 69 uninstalling 165 upgrade installation of 69 Upgr
Index definition 27 I/O count 230 errors 230 K KB meaning x kernel mode switching 81 L LB 350 LDEV (Logical Device) 477 load balancing 4, 15, 250, 478 load balancing algorithms 18 load distribution using load balancing 15 log filter 42 logging level values 251 logical device file 478 logical unit 7 logical unit ID 285 logical volume number 476 LU 8 configuration 10 LU (Logical Unit) 478 LUN 285 M manual path switching 27 MB meaning x message examining 222, 224 message level 350 Messages 349 messages adj
Index commands 228 HDLM 1 owner controller 17, 479 owner path 17, 479 P P 8 path 7, 479 checking the configuration 134 path error handling 221 path health checking 4, 38, 253, 479 path information obtaining 222 path name 480 path priority number 24 path status transition 28 path switching automatically 21 manually 27 PathID 219 PathName 219 Paths to which load balancing is applied 16 PCI bus number 285 Performing Failovers and Failbacks Using Path Switching 21 persistent reservation 480 placing a path or
Index system configuration 7 T taking actions for hardware error 223 program error 224, 225 target ID 285 TB meaning x trace file 41 trace file size 253 trace level values 252 types of collected logs 41 types of error information 41 U unattended installation installation-information settings file 336 log file 345 uninstallation HDLM 165 uninstalling Hitachi Network Objectplaza Trace Library (HNTRLib) 175 Hitachi Network Objectplaza Trace Library (HNTRLib2) 174 upgrade installation 69 utilities dlmmigsts
