Hitachi Command Suite Dynamic Link Manager Software User Guide for Linux® Document Organization Product Version Getting Help Contents MK-92DLM113-25
© 2011-2013 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd. Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use.
Contents Preface.................................................................................................xv Intended audience...................................................................................................xvi Product version.......................................................................................................xvi Release notes..........................................................................................................xvi Document revision level.......
Automatic Failbacks...............................................................................2-20 Manual Path Switching....................................................................................2-21 Path Status Transition.....................................................................................2-22 The Online Path Status..........................................................................2-22 The Offline Path Status...............................................................
Boot Disk Environments and Hitachi Compute Blade Environments Supported by HDLM (If an FC-SAN Is Used)............................................................3-57 Related Products When Using Red Hat Enterprise Linux 6..................................3-60 Cluster Software Supported by HDLM.....................................................3-60 Volume Managers Supported by HDLM....................................................3-63 File Systems Supported by HDLM........................................
Operations Required for Devices to Be Managed by HDLM........................3-96 Checking the Volume Group...................................................................3-97 Setting in the syslogd Settings File..........................................................3-99 Setting the Mount Point (in Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 6)..............................................................................................3-100 Checking the Partition...........................
When Moving a Logical Volume Created on a SCSI Device in a Single-Path Environment to an HDLM Device....................................................................3-202 Settings for Xen..................................................................................................3-205 Settings for KVM.................................................................................................3-207 Settings for Heartbeat.............................................................................
Canceling the md Device Settings...................................................................3-241 Migrating to md Devices for which the MULTIPATH Function Is Not Used 3-241 Migrating to md Devices for which the MULTIPATH Function Is Used......3-244 Canceling the LUKS Settings..........................................................................3-248 Removing HDLM...........................................................................................3-248 Removing HDLM..........................
HDLM Resident Processes......................................................................................4-24 Reconfiguring the HDLM Operating Environment.....................................................4-25 Replacing HBAs..............................................................................................4-25 Preparation for replacing HBAs...............................................................4-26 Procedure for replacing HBAs.........................................................
help (Displays the Operation Format)....................................................................... 6-4 Format.............................................................................................................6-4 Parameter........................................................................................................6-4 offline (Places Paths Offline)....................................................................................6-6 Format........................................
To Display the Format of the delete Operation.........................................6-66 7 Utility Reference................................................................................... 7-1 Overview of the Utilities..........................................................................................7-2 DLMgetras Utility for Collecting HDLM Error Information............................................ 7-3 Format...................................................................................
Format and Meaning of Message IDs................................................................. 8-3 Terms Used in Messages and Message Explanations............................................8-3 Components That Output Messages to syslog.....................................................8-3 KAPL01001 to KAPL02000.......................................................................................8-4 KAPL03001 to KAPL04000.................................................................................
Functional Differences Between Version 5.7 or Later and Versions Earlier Than 5.7.....C-6 Functional Differences Between Version 5.6.3 or Later and Versions Earlier Than 5.6.3 .............................................................................................................................C-6 Functional Differences Between Version 5.4 or Later and Versions Earlier Than 5.4.....
xiv Hitachi Dynamic Link Manager User Guide for Linux®
Preface This document describes how to use the Hitachi Dynamic Link Manager.
Intended audience This document is intended for storage administrators who use Hitachi Dynamic Link Manager (HDLM) to operate and manage storage systems, and assumes that readers have: • Knowledge of Linux and its management functionality • Knowledge of Storage system management functionality • Knowledge of Cluster software functionality • Knowledge of Volume management software functionality Product version This document revision applies to HDLM for Linux version 7.6 or later.
Document organization The following table provides an overview of the contents and organization of this document. Click the chapter title in the left column to go to that chapter. The first page of each chapter provides links to the sections in that chapter. Chapter/Appendix Description Chapter 1, Overview of HDLM on page 1-1 Gives an overview of HDLM, and describes its features.
• Hitachi Command Suite Global Link Manager Installation and Configuration Guide, MK-95HC107 • Hitachi Command Suite Global Link Manager Messages, MK-95HC108 • Hitachi Adaptable Modular Storage Series User's Guide • Hitachi Simple Modular Storage Series User's Guide • Hitachi Unified Storage Series User's Guide • Hitachi USP Series User's Guide • Hitachi Workgroup Modular Storage Series User's Guide • Thunder9580V Series Disk Array Subsystem User's Guide • Universal Storage Platform V Serie
Conventions for storage capacity values Physical storage capacity values (for example, disk drive capacity) are calculated based on the following values: Physical capacity unit Value 1 kilobyte (KB) 1,000 (103) bytes 1 megabyte (MB) 1,000 KB or 1,0002 bytes 1 gigabyte (GB) 1,000 MB or 1,0003 bytes 1 terabyte (TB) 1,000 GB or 1,0004 bytes 1 petabyte (PB) 1,000 TB or 1,0005 bytes 1 exabyte (EB) 1,000 PB or 1,0006 bytes Logical storage capacity values (for example, logical device capacity) are ca
Comments Please send us your comments on this document to: doc.comments@hds.com. Include the document title and number, including the revision level (for example, -07), and refer to specific sections and paragraphs whenever possible. All comments become the property of Hitachi Data Systems Corporation.
1 Overview of HDLM HDLM is a software package that manages paths between a host and a storage system. HDLM is designed to distribute loads across multiple paths and will switch a given load to another path if there is a failure in the path that is currently being used, thus improving system reliability. This chapter gives an overview of HDLM and describes its features.
What is HDLM? With the widespread use of data warehousing and increasing use of multimedia data, the need for high-speed processing of large volumes of data on networks has rapidly grown. To satisfy this need, networks dedicated to the transfer of data, such as SANs, are now being used to provide access to storage systems. HDLM manages the access paths to these storage systems.
The ability to continue running operations between a host and storage system, even if there is a failure. This is also known as performing a failover. When a host is connected to a storage system via multiple paths, HDLM can automatically switch to another path if there is some sort of failure in the path that is currently being used. This allows operations to continue between a host and a storage system.
1-4 Overview of HDLM Hitachi Dynamic Link Manager User Guide for Linux®
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.
□ Collecting Audit Log Data □ Integrated HDLM management using Global Link Manager □ Cluster Support 2-2 HDLM Functions Hitachi Dynamic Link Manager User Guide for Linux®
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.
The following figure shows the configuration of an HDLM system using an FCSAN. Figure 2-1 Configuration of an HDLM System When Using an FC-SAN The following table lists the HDLM system components when using an FCSAN. Table 2-1 HDLM System Components When Using an FC-SAN Components 2-4 Description HBA A host bus adapter. This serves as a cable port on the host. FC-SAN A dedicated network that is used for data transfer between the host and storage systems. CHA A channel adapter. P A port on a CHA.
System Configuration Using an IP-SAN In an IP-SAN, LAN cables are used to connect hosts to storage systems. The cable port on the host is called a network interface card (NIC). In order to use an NIC, the iSCSI software must be installed ahead of time on the host. The cable port on the storage system is called a port (P) on a channel adapter (CHA) used for iSCSI connections. A logical unit (LU) contained in a storage system is the target of input to, or output from, the host.
Table 2-2 HDLM System Components When Using an IP-SAN Components Description iSCSI software The driver software that contains the iSCSI initiator function. NIC A network interface card that serves as a cable port on a host. The NIC is referred to as the HBA in HDLM commands. Sometimes, it is also just simply called an HBA in this manual. IP-SAN A data transfer network that connects hosts and storage systems by using the iSCSI standard. CHA A channel adapter. P A port on a CHA.
¢ • For SUSE LINUX Enterprise Server 11: open-iscsi Storage system The storage system applicable for an IP-SAN is a Hitachi AMS2000 series storage system. Restrictions on using HDLM in an IP-SAN environment The following restrictions apply when using HDLM in an IP-SAN environment: • HDLM can only be used in a cluster configuration when it is installed in a Red Hat Enterprise Linux 6 environment with RHCM. • The kdump function cannot be used.
Figure 2-3 LU Configuration Recognized by the Host After HDLM Installation The following table lists and describes the components recognized by the host. Table 2-3 LU Components Components Description HDev A Dev (partition) in an LU that the host recognizes via the HDLM driver. It is called a host device. One host device is recognized for one Dev in the storage system. HLU An LU that the host recognizes via the HDLM driver. It is called a host LU.
Figure 2-4 Configuration of the HDLM Programs The following table lists and describes the functions of these programs.
Program name Functions • Configure the HDLM operating environment • Request path health checks and automatic failbacks to be performed • Collect error log data HDLM alert driver Reports the log information collected by the HDLM driver to the HDLM manager. The driver name is sddlmadrv. HDLM driver Controls all the HDLM functions, manages paths, and detects errors. The HDLM driver consists of the following: • Core logic component Controls the basic functionality of HDLM.
Figure 2-5 Position of the HDLM Driver and HDLM Devices Logical Device Files for HDLM Devices The logical device file name of an HDLM device is different from the logical device file name of a SCSI device. When you configure the logical device file of an HDLM device for applications such as volume management software, these applications can access the LUs that HDLM manages.
Table 2-5 Example of Using the Logical Device File Name of the Device Used When the Application Accesses the LU Host status Before installing HDLM Device file name that the application uses The application uses the logical device file name for the SCSI device. Example: sda sdb After installing HDLM The application uses the logical device file name for the HDLM device.
Figure 2-6 About Alphabetic Letters Used in the Logical Device File Name About numeric values used in a logical device file name: [1-15] indicates a partition number in the applicable LU. When the HDLM configuration definition utility (dlmcfgmgr) is executed, all logical device files for partitions 1 to 15 are created. For example, if the logical device file name of an HDLM device is sddlmaa1, it indicates partition 1 on sddlmaa. To specify the entire LU, simply use sddlmaa.
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. Note that some I/O operations managed by HDLM can be distributed to each path, while others cannot.
Figure 2-8 Flow of I/O Data When the Load Balancing Function Is Used When the load balancing function is used, I/O operations are distributed via multiple paths (A, B, C, and D). This helps to prevent problems with system performance and helps prevent bottlenecks from occurring. Paths To Which Load Balancing Is Applied This subsection describes, for each type of storage system, the paths to which the load balancing function is applied.
among the remaining usable owner paths. When all owner paths cannot be used, load balancing is performed among the non-owner paths. For the example in Figure 2-9 Overview of Load Balancing on page 2-16, suppose that in the owner controller of LU0 is CHA0. When the LU is accessed, the load is balanced between the two paths A and B, which are both owner paths. When one of the paths (A) cannot be used, then the LU is accessed from the only other owner path (B).
¢ Hitachi AMS2000 series# ¢ Hitachi SMS series# ¢ HUS100 series# HUS VM #: This storage system applies when the dynamic I/O path control function is disabled.
The paths are simply selected in order from among all the connected paths. ¢ ¢ Extended Least I/Os The path that has the least number of I/Os being processed is selected from among all the connected paths. Extended Least Blocks The path that has the least number of I/O blocks being processed is selected from among all the connected paths. The following table lists and describes the features of the load balancing algorithms.
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. Two types of failovers and failbacks are available: • Automatic failovers and failbacks • Manual failovers and failbacks Failovers and failbacks switch which path is being used and also change the statuses of the paths. A path status is either online or offline. An online status means that the path can receive I/Os.
When the Lightning 9900 series, Lightning 9900V series, Hitachi USP series, Universal Storage Platform V/VM series, Virtual Storage Platform series, Hitachi AMS2000 series#, Hitachi SMS series#, HUS100 series#, or HUS VM is being used, all the paths are owner paths. This means that all the paths that are accessing the same LU are possible switching destinations. For example, in Figure 2-10 Path Switching on page 2-20, the LU is accessed using only the one path (A).
from an error, and 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 9900 series, Lightning 9900V series, Hitachi USP series, Universal Storage Platform V/VM series, Virtual Storage Platform series, Hitachi AMS2000 series#1, Hitachi SMS series#1, HUS100 series#1, or HUS VM is being used, all the paths are owner paths.
When using the Thunder 9500V series, or Hitachi AMS/WMS series, HDLM will select the next path to be used first from among the online owner paths, and then from the online non-owner paths.
• Online(D)# The paths to the primary volume (P-VOL) in an HAM environment have recovered from an error, but I/O to the P-VOL is suppressed. If an error occurs in all the paths to a secondary volume (S-VOL), the status of the P-VOL paths will be automatically changed to the Online status. To change the status to the Online(D) status, specify the -dfha parameter for the HDLM command's online operation. # The status changes to this status when using HAM (High Availability Manager).
Figure 2-11 Path Status Transitions Legend: Online operation: Online operation performed by executing the dlnkmgr command's online operation. Offline operation: Offline operation performed by executing the dlnkmgr command's offline operation. #1 When the following conditions are satisfied, a path that has been determined to have an intermittent error also becomes subject to automatic failback: ¢ ¢ ¢ All the paths connected to an LU are Online(E), Offline(E), or Offline(C).
Figure 2-12 Path Status Transitions (P-VOL in HAM environment) 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 Also when an error occurs in all the paths to an S-VOL in the Online(D) status. #2 When I/O operations are processed on an S-VOL.
If there is a path failure immediately after a path is taken offline by using either the an HDLM command, the status might change from Offline(C) to Offline(E). If an offline operation was just performed, wait about 1 minutes, check the path status by using an HDLM command, and then make sure that the status has changed to Offline(C). If it is still Offline(E), retry the offline operation.
Intermittent error monitoring can be used only when automatic failback has already been enabled. The values that can be specified for intermittent error monitoring depend on the values specified for automatic failbacks. For details on how to specify the settings, see set (Sets Up the Operating Environment) on page 6-15.
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.
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. If the conditions are changed while error monitoring is not being performed, error monitoring will start up again and use the updated conditions after any given path is recovered from an error by performing an automatic failback.
Table 2-7 When Effects of a User Changing the Intermittent Error Information User operation Changing the intermittent error monitoring settings Turning off Number of errors and time passed since error monitoring started Information about paths not subject to automatic failback Reset Reset#1 Changing the conditions for Reset#2 an intermittent error while intermittent error monitoring is being performed Inherited Turning intermittent error monitoring on by executing the set operation, (but not chang
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).
What is the Dynamic Load Balance Control Function In a system configuration in which multiple hosts and a storage system are connected, the I/O processing load tends to concentrate on the controller of the storage system, causing throughput performance of the entire system decrease. The dynamic load balance controller function evaluates such load statuses on the controller and prevents storage system performance from decreasing.
Figure 2-16 Flow of Data When Collecting Error Information Logs might be collected in layers below HDLM, such as for the SCSI driver. For more details, see the Linux documentation. Types of Collected Logs HDLM collects information on the detected error and trace information in the process-specific-trace information file, trace file, error logs, log for the dlmcfgmgr utility for managing the HDLM configuration and syslog.
The following table lists and describes the error information that can be collected in logs. Table 2-8 Types of Error Information Log name Description Output destination Process-specific- Operation logs for the HDLM command trace information are collected. file The default file path is / var/opt/ DynamicLinkManager/log/ dlnkmgr[1-2].log. Trace file Trace information on the HDLM manager is collected at the level specified by the user.
The following shows an example where the system function name is user, and messages at the info level or higher are output to the /tmp/ syslog.user.log file: user.info /tmp/syslog.user.log For details on error levels, see Filtering of Error Information on page 2-35. Filtering of Error Information Errors detected by HDLM are classified into various error levels. The following table lists and describes the error levels, in the order of most to least severe to the system.
¢ Outputs error information only ¢ Outputs trace information on program operation summaries ¢ Outputs trace information on program operation details ¢ Outputs all trace information For details on how to set the collection level, see Setting Up the HDLM Functions on page 3-215. Collecting Error Information Using the Utility for Collecting HDLM Error Information (DLMgetras) HDLM has a utility for collecting HDLM error information (DLMgetras).
Category Explanation • Startup and termination of hardware components (including micro-program) • Startup and termination of software running on storage systems, software running on SVPs (service processors), and Hitachi Command Suite products An abnormal hardware or software event, including: Failure LinkStatus • Hardware errors • Software errors (such as memory errors) An event indicating the linkage status between devices: • ExternalService Authentication AccessControl ContentAccess Conf
Category Explanation • AnomalyEvent Adding or removing software components An event indicating an abnormal state such as exceeding a threshold, including: • Exceeding a network traffic threshold • Exceeding a CPU load threshold • Reporting that the temporary audit log data saved internally is close to its maximum size limit or that the audit log files have wrapped back around to the beginning An event indicating an occurrence of abnormal communication, including: • A SYN flood attack or protocol
Category Authentication ConfigurationAccess Explanation Severity #1 Message ID Processing of the dlmstart utility was successful. 6 KAPL15062-I Processing of the dlmstart utility failed. 3 KAPL15063-E Administrator or Permission has end-user not been granted authentication to execute the HDLM command. 4 KAPL15111-W Permission has not been granted to execute HDLM utilities. 4 KAPL15010-W Permission has not been granted to start or stop the HDLM manager.
Category 2-40 Explanation Audit event Severity #1 Message ID An attempt to display program information failed. 3 KAPL15108-E An attempt to display HDLM managementtarget information was successful. 6 KAPL15109-I An attempt to display HDLM managementtarget information failed. 3 KAPL15110-E Processing of the dlmpr -k command was successful. 6 KAPL15001-I Processing of the dlmpr -k command failed. 3 KAPL15002-E Processing of the dlmpr -c command was successful.
Category Explanation Audit event Severity #1 Message ID Processing of the dlmcfgmgr -i command failed. 3 KAPL15045-E Processing of the dlmcfgmgr -v command was successful. 6 KAPL15046-I Processing of the dlmcfgmgr -v command failed. 3 KAPL15047-E Processing of the dlmcfgmgr -u command was successful. 6 KAPL15048-I Processing of the dlmcfgmgr -u command failed. 3 KAPL15049-E Processing of the dlmmkinitrd command was successful.
Category Explanation Audit event #1 Message ID Processing of the dlmupdatesysini t command was successful. 6 KAPL15058-I Processing of the dlmupdatesysini t command failed. 3 KAPL15059-E Processing of the dlmchname -o command was successful. 6 KAPL15301-I Processing of the dlmchname -o command failed. 3 KAPL15302-E Processing of the dlmchname command was successful. 6 KAPL15303-I Processing of the dlmchname command failed.
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. Requirements for Outputting Audit Log Data HDLM can output audit log data when all of the following conditions are satisfied: • The syslog daemon is active. • The output of audit log data has been enabled by using the HDLM command's set operation.
You can also filter the audit log output by specifying a severity level and type for the HDLM command's set operation. Filtering by severity: The following table lists the severity levels that can be specified.
common-identifier , common-specification-revision-number , serialnumber , message-ID , date-and-time , entity-affected , locationaffected , audit-event-type , audit-event-result , subject-ID-for-auditevent-result , hardware-identification-information , locationinformation , location-identification-information , FQDN , redundancyidentification-information , agent-information , host-sending-request , port-number-sending-request , host-receiving-request , port-numberreceiving-request , common-operation-ID , lo
Item# Explanation Port number receiving request Number of the port receiving a request Common operation ID Operation serial number in the program Log type information Fixed to BasicLog Application identification Program identification information information Reserved area This 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.
Figure 2-17 Example System Configuration Using HDLM and Global Link Manager Cluster Support HDLM can also be used in cluster configurations.
• Cluster Software Supported by HDLM on page 3-79 in Related Products When Using Oracle Unbreakable Enterprise Kernel 5 on page 3-79 HDLM uses a path of the active host to access an LU. The details of host switching depend on the application.
3 Creating an HDLM Environment This chapter explains the procedure for setting up an HDLM environment and the procedure for canceling the environment settings. Make sure that HDLM installation and function setup has been performed. Set up volume groups and cluster software according to the environment you are using.
□ Settings for Oracle RAC □ Settings for the RHCM □ Settings for VCS □ Checking the Path Configuration □ Setting Up HDLM □ The Process-specific-trace Information File □ Creating a Character-Type Device File for an HDLM Device □ Creating File Systems for HDLM (When Volume Management Software Is Not Used) □ Settings for Automatic Mounting □ Canceling the Settings for HDLM 3-2 Creating an HDLM Environment Hitachi Dynamic Link Manager User Guide for Linux®
HDLM System Requirements Check the following before installing HDLM: For the requirements for using HDLM in an HAM environment, see the release notes of HDLM.
• Table 3-2 Red Hat Enterprise Linux AS4/ES4 Kernels Supported by HDLM on page 3-5 • Table 3-3 Red Hat Enterprise Linux 5 Kernels Supported by HDLM on page 3-8 • Table 3-4 Red Hat Enterprise Linux 6 Kernels Supported by HDLM on page 3-9 • Table 3-5 SUSE LINUX Enterprise Server 10 Kernels Supported by HDLM on page 3-10 • Table 3-6 SUSE LINUX Enterprise Server 11 Kernels Supported by HDLM on page 3-12 • Table 3-7 Oracle Enterprise Linux 4 Kernels Supported by HDLM on page 3-13 • Table 3-8 Oracle
If an IP-SAN is used to connect HDLM with a storage system, HDLM is supported on the following OSs: ¢ Red Hat Enterprise Linux 5.6 ¢ Red Hat Enterprise Linux 5.6 Advanced Platform ¢ Red Hat Enterprise Linux 5.7 ¢ Red Hat Enterprise Linux 5.7 Advanced Platform ¢ Red Hat Enterprise Linux 5.8 ¢ Red Hat Enterprise Linux 5.8 Advanced Platform ¢ Red Hat Enterprise Linux 5.9 ¢ Red Hat Enterprise Linux 5.
Kernel architecture#1 Kernel 2.6.9-55.EL 2.6.9-55.ELsmp 2.6.9-55.ELhugemem 2.6.9-67.EL 2.6.9-67.ELsmp 2.6.9-67.ELhugemem 2.6.9-78.EL 2.6.9-78.ELsmp 2.6.9-78.ELhugemem 2.6.9-89.EL 2.6.9-89.ELsmp 2.6.9-89.ELhugemem 2.6.9-100.EL 2.6.9-100.ELsmp 2.6.9-100.ELhugemem 2.6.9-11.EL IPF#3 2.6.9-34.EL 2.6.9-42.EL 2.6.9-42.0.3.EL 2.6.9-55.EL 2.6.9-55.ELlargesmp 2.6.9-67.EL 2.6.9-67.ELlargesmp 2.6.9-78.EL 2.6.9-78.ELlargesmp 2.6.9-89.EL 2.6.9-89.ELlargesmp 2.6.9-100.EL 2.6.9-100.ELlargesmp EM64T/AMD64#4 2.6.9-11.
Kernel architecture#1 Kernel 2.6.9-42.ELsmp 2.6.9-42.ELlargesmp 2.6.9-42.0.3.EL 2.6.9-42.0.3.ELsmp 2.6.9-42.0.3.ELlargesmp 2.6.9-55.EL 2.6.9-55.ELsmp 2.6.9-55.ELlargesmp 2.6.9-67.EL 2.6.9-67.ELsmp 2.6.9-67.ELlargesmp 2.6.9-78.EL 2.6.9-78.ELsmp 2.6.9-78.ELlargesmp 2.6.9-89.EL 2.6.9-89.ELsmp 2.6.9-89.ELlargesmp 2.6.9-100.EL 2.6.9-100.ELsmp 2.6.9-100.ELlargesmp #1 Only kernels that are provided by OS distributors in binary format are supported.
RPM-package-version depends on the OS version you are using. Table 3-3 Red Hat Enterprise Linux 5 Kernels Supported by HDLM Kernel architecture#1 Kernel 2.6.18-8.el5 IA32#2 2.6.18-8.el5PAE 2.6.18-53.el5 2.6.18-53.el5PAE 2.6.18-92.el5 2.6.18-92.el5PAE 2.6.18-128.el5 2.6.18-128.el5PAE 2.6.18-164.el5 2.6.18-164.el5PAE 2.6.18-194.el5 2.6.18-194.el5PAE 2.6.18-238.el5 2.6.18-238.el5PAE 2.6.18-274.el5 2.6.18-274.el5PAE 2.6.18-308.el5 2.6.18-308.el5PAE 2.6.18-348.el5 2.6.18-348.el5PAE 2.6.18-8.el5 IPF#3 2.6.
Kernel architecture#1 Kernel 2.6.18-128.el5 2.6.18-164.el5 2.6.18-194.el5 2.6.18-238.el5 2.6.18-274.el5 2.6.18-308.el5 2.6.18-348.el5 #1 Only kernels that are provided by OS distributors in binary format are supported. #2 HDLM supports an environment where an IA32 kernel is installed on a system that uses an Intel CPU or AMD Opteron CPU. #3 HDLM supports an environment where an IPF kernel is installed on a system that uses an Intel CPU.
Kernel architecture#1 Kernel 2.6.32-131.0.15.el6.x86_64 2.6.32-220.el6.x86_64 2.6.32-279.el6.x86_64 2.6.32-358.el6.x86_64 #1 Only kernels that are provided by OS distributors in binary format are supported. #2 HDLM supports an environment where an IA32 kernel is installed on a system that uses an Intel CPU or AMD Opteron CPU.
Kernel architecture#1 Kernel 2.6.16.60-0.54.5-bigsmp#6 2.6.16.60-0.54.5-xenpae#6 2.6.16.60-0.85.1-default#7 2.6.16.60-0.85.1-smp#7 2.6.16.60-0.85.1-bigsmp#7 2.6.16.60-0.85.1-xenpae#7 IPF#8 2.6.16.21-0.8-default#3 2.6.16.46-0.14-default#4 2.6.16.60-0.21-default#5 2.6.16.60-0.54.5-default#6 2.6.16.60-0.85.1-default#7 EM64T/AMD64#9 2.6.16.21-0.8-default#3 2.6.16.21-0.8-smp#3 2.6.16.46-0.14-default#4 2.6.16.46-0.14-smp#4 2.6.16.60-0.21-default#5 2.6.16.60-0.21-smp#5 2.6.16.60-0.21-xen#5 2.6.16.60-0.54.
#2 HDLM supports an environment where an IA32 kernel is installed on a system that uses an Intel CPU or AMD Opteron CPU. #3 A gdb package of version 6.5-21.2 or later must be installed. #4 All of the packages of SP1 for SUSE LINUX Enterprise Server 10 must be installed. #5 All of the SP2 packages for SUSE LINUX Enterprise Server 10 must be installed. #6 All of the SP3 packages for SUSE LINUX Enterprise Server 10 must be installed.
Kernel architecture#1 Kernel 3.0.76-0.11-default 2.6.27.21-0.1.2-default EM64T/AMD64#4 2.6.27.21-0.1.2-xen 2.6.32.12-0.7.1-default 2.6.32.12-0.7.1-xen 3.0.13-0.27-default 3.0.76-0.11-default Note: This subsection describes the operating environment common to SUSE LINUX Enterprise Server 11. An HDLM device that applies EVMS functions is not supported. ¢ You cannot use DRBD functions in an environment where HDLM is installed. ¢ You cannot use HDLM in a User-Mode Linux environment.
Kernel architecture#1 Kernel 2.6.9-55.0.0.0.2.ELlargesmp 2.6.9-67.0.0.0.1.EL 2.6.9-67.0.0.0.1.ELsmp 2.6.9-67.0.0.0.1.ELlargesmp Note: Unless there is a note relating to Oracle Enterprise Linux 4 stating otherwise, for descriptions where Red Hat Enterprise Linux or Red Hat Enterprise Linux AS4/ES4 are indicated, read these as Oracle Enterprise Linux 4. #1 Only kernels that are provided by OS distributors in binary format are supported.
Kernel architecture#1 Kernel 2.6.18-274.el5PAE 2.6.18-53.el5 EM64T/AMD64#3 2.6.18-164.el5 2.6.18-194.el5 2.6.18-238.el5 2.6.18-274.el5 Note: Unless there is a note relating to Oracle Enterprise Linux 5 stating otherwise, for descriptions where Red Hat Enterprise Linux or Red Hat Enterprise Linux 5 are indicated, read these as Oracle Enterprise Linux 5. #1 Only kernels that are provided by OS distributors in binary format are supported.
Hat Enterprise Linux 5 are indicated, read these as Oracle Unbreakable Enterprise Kernel 5. #1 Only kernels that are provided by OS distributors in binary format are supported. #2 HDLM supports an environment where an IA32 kernel is installed on a system that uses an Intel CPU or AMD Opteron CPU. #3 Note the following in an EM64T/AMD64 environment: ¢ ¢ HDLM supports an environment where an EM64T/AMD64 kernel is installed on a system that uses an Intel CPU or AMD Opteron CPU.
#3 Note the following in an EM64T/AMD64 environment: ¢ ¢ HDLM supports an environment where an EM64T/AMD64 kernel is installed on a system that uses an Intel CPU or AMD Opteron CPU. In an EM64T/AMD64 environment, the RPM (Red Hat Package Manager) packages listed below are required. Install these RPM packages before installing HDLM: - libstdc++- RPM package version .i686.rpm - libgcc- RPM package version .i686.rpm - glibc- RPM package version .i686.
Storage systems that are used must have a dual controller configuration. If you use them in a HUB-connected environment, specify a unique loop ID for all the connected hosts and storage systems. For details on the microprogram version required for using HDLM, see HDLM Release Notes. For details on the settings information for storage system, see the maintenance documentation for the storage system.
Table 3-11 HDLM-Related Programs Required When Handling Intermediate Volumes Managed by Hitachi RapidXchange Kernel architecture#1 Kernel Related Programs IA32#2 2.6.32-279.el6.i File Access Library and File Conversion Utility 686 (FAL/FCU) 01-05-66/26 or later EM64T/AMD64#3 2.6.32-279.el6. x86_64 File Access Library and File Conversion Utility (FAL/FCU) 01-05-66/26 or later #1 Only kernels that are provided by OS distributors in binary format are supported.
executing the following command, are the same, the versions of HDLM are the same: # /opt/DynamicLinkManager/bin/dlnkmgr view -sys The following tables list related programs used when you configure a cluster: • Table 3-12 Cluster Software When Using Red Hat Enterprise Linux AS4 (IA32) on page 3-20 • Table 3-13 Cluster Software When Using Red Hat Enterprise Linux ES4 (IA32) on page 3-25 • Table 3-14 Cluster Software When Using Red Hat Enterprise Linux AS4/ ES4 (IPF) on page 3-30 • Table 3-15 Cluster S
Usable kernels Cluster software LifeKeeper v7 LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 LifeKeeper v7 Update4 Oracle9i RAC Release 2 (9.2.0.8.0)#1 Oracle RAC 10g Release 2 (10.1.0.5.0)#2 Oracle RAC 10g Release 2 (10.2.0.2.0)#8 Oracle RAC 10g Release 2 (10.2.0.3.0)#4 Oracle RAC 10g Release 2 (10.2.0.4.0)#5 Oracle RAC 10g Release 2 (10.2.0.5.0) + Patch 11066597#5 Oracle RAC 11g Release 1 (11.1.0.6.0)#6 Oracle RAC 11g Release 1 (11.1.0.7.0)#7 RHCM 1.0.4-0 2.6.9-34.0.2.
Usable kernels Cluster software LifeKeeper v7 Update2 LifeKeeper v7 Update3 LifeKeeper v7 Update4 Oracle9i RAC Release 2 (9.2.0.8.0)#1 Oracle RAC 10g Release 2 (10.1.0.5.0)#2 Oracle RAC 10g Release 2 (10.2.0.2.0)#8 Oracle RAC 10g Release 2 (10.2.0.3.0)#4 Oracle RAC 10g Release 2 (10.2.0.4.0)#5 Oracle RAC 10g Release 2 (10.2.0.5.0) + Patch 11066597#5 Oracle RAC 11g Release 1 (11.1.0.6.0)#6 Oracle RAC 11g Release 1 (11.1.0.7.0)#7 RHCM 1.0.11-0 2.6.9-42.0.3.EL LifeKeeper v6 2.6.9-42.0.3.
Usable kernels Cluster software Oracle RAC 10g Release 2 (10.2.0.2.0)#8 Oracle RAC 10g Release 2 (10.2.0.3.0)#4 Oracle RAC 10g Release 2 (10.2.0.4.0)#5 Oracle RAC 10g Release 2 (10.2.0.5.0) + Patch 11066597#5 Oracle RAC 11g Release 1 (11.1.0.6.0)#6 Oracle RAC 11g Release 1 (11.1.0.7.0)#7 RHCM 1.0.17-0 2.6.9-78.EL LifeKeeper v6 Update4 2.6.9-78.ELsmp LifeKeeper v7 2.6.9-78.ELhugemem LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 LifeKeeper v7 Update4 Oracle RAC 10g Release 2 (10.1.
Usable kernels Cluster software Oracle RAC 10g Release 2 (10.2.0.4.0)#5 Oracle RAC 10g Release 2 (10.2.0.5.0) + Patch 11066597#5 Oracle RAC 11g Release 1 (11.1.0.6.0)#6 Oracle RAC 11g Release 1 (11.1.0.7.0)#7 Oracle RAC 11g Release 2 (11.2.0.2.0)#9 #1 Only configurations that include Oracle Cluster Management Software using raw devices are supported. For details, see Settings for Oracle RAC on page 3-208.
#6 The following configurations are supported: ¢ ¢ ¢ Configurations that include raw devices and Oracle Clusterware Configurations that include the Automatic Storage Management (ASM) function (raw devices used) and Oracle Clusterware Configurations that include the Automatic Storage Management (ASM) function (the ASMLib kernel driver (ASMLib) is used) and Oracle Clusterware Configurations that include the Oracle Cluster File System 2 and Oracle Clusterware For details, see Settings for Oracle RAC on page
Usable kernels Cluster software LifeKeeper v7 Update3 LifeKeeper v7 Update4 Oracle RAC 10g Release 2 (10.1.0.5.0)#1 Oracle RAC 10g Release 2 (10.2.0.2.0)#2 Oracle RAC 10g Release 2 (10.2.0.3.0)#3 Oracle RAC 10g Release 2 (10.2.0.4.0)#4 Oracle RAC 10g Release 2 (10.2.0.5.0) + Patch 11066597#4 Oracle RAC 11g Release 1 (11.1.0.6.0)#5 Oracle RAC 11g Release 1 (11.1.0.7.0)#6 RHCM 1.0.0-0 2.6.9-34.EL LifeKeeper v6 2.6.9-34.ELsmp LifeKeeper v6 Update1 2.6.9-34.ELhugemem LifeKeeper v6 Update2 2.6.9-34.0.2.
Usable kernels Cluster software Oracle RAC 10g Release 2 (10.2.0.2.0)#7 Oracle RAC 10g Release 2 (10.2.0.3.0)#3 Oracle RAC 10g Release 2 (10.2.0.4.0)#4 Oracle RAC 10g Release 2 (10.2.0.5.0) + Patch 11066597#4 Oracle RAC 11g Release 1 (11.1.0.6.0)#5 Oracle RAC 11g Release 1 (11.1.0.7.0)#6 RHCM 1.0.11-0 2.6.9-55.EL LifeKeeper v6 Update2 2.6.9-55.ELsmp LifeKeeper v6 Update3 2.6.9-55.ELhugemem LifeKeeper v6 Update4 2.6.9-67.EL LifeKeeper v7 2.6.9-67.ELsmp LifeKeeper v7 Update1 2.6.9-67.
Usable kernels Cluster software 2.6.9-89.EL LifeKeeper v7 2.6.9-89.ELsmp LifeKeeper v7 Update1 2.6.9-89.ELhugemem LifeKeeper v7 Update2 LifeKeeper v7 Update3 LifeKeeper v7 Update4 Oracle RAC 10g Release 2 (10.1.0.5.0)#1 Oracle RAC 10g Release 2 (10.2.0.2.0)#7 Oracle RAC 10g Release 2 (10.2.0.3.0)#3 Oracle RAC 10g Release 2 (10.2.0.4.0)#4 Oracle RAC 10g Release 2 (10.2.0.5.0) + Patch 11066597#4 Oracle RAC 11g Release 1 (11.1.0.6.0)#5 Oracle RAC 11g Release 1 (11.1.0.7.
#3 The following configurations are supported: ¢ Configurations that include the Automatic Storage Management (ASM) function (raw devices used) and Cluster Ready Service (CRS) Configurations that include the Automatic Storage Management (ASM) function (the ASMLib kernel driver (ASMLib) is used) and Cluster Ready Service (CRS) For details, see Settings for Oracle RAC on page 3-208.
For details, see Settings for Oracle RAC on page 3-208. Table 3-14 Cluster Software When Using Red Hat Enterprise Linux AS4/ ES4 (IPF) Usable kernels 2.6.9-11.EL Cluster software Oracle RAC 10g Release 2 (10.2.0.1.0)#1 Oracle RAC 10g Release 2 (10.2.0.2.0)#1 Oracle RAC 10g Release 2 (10.2.0.3.0)#2 2.6.9-34.EL Oracle RAC 10g Release 2 (10.2.0.1.0)#1 Oracle RAC 10g Release 2 (10.2.0.2.0)#1 Oracle RAC 10g Release 2 (10.2.0.3.0)#2 RHCM 1.0.4-0 2.6.9-42.EL Oracle RAC 10g Release 2 (10.2.0.1.0)#1 2.6.9-42.
Configurations that include the Automatic Storage Management (ASM) function (the ASMLib kernel driver (ASMLib) is used) and Cluster Ready Service (CRS) For details, see Settings for Oracle RAC on page 3-208. ¢ Table 3-15 Cluster Software When Using Red Hat Enterprise Linux AS4/ ES4 (EM64T/AMD64) Usable kernels Cluster software 2.6.9-11.EL LifeKeeper v6 2.6.9-11.
Usable kernels Cluster software Oracle RAC 11g Release 1 (11.1.0.6.0)#4 Oracle RAC 11g Release 1 (11.1.0.7.0)#5 RHCM 1.0.4-0 VCS 4.1 MP3#6 2.6.9-34.0.2.EL LifeKeeper v6 2.6.9-34.0.2.ELsmp LifeKeeper v6 Update1 2.6.9-34.0.2.ELlargesmp LifeKeeper v6 Update2 LifeKeeper v6 Update3 LifeKeeper v6 Update4 LifeKeeper v7 LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 LifeKeeper v7 Update4 Oracle RAC 10g Release 2 (10.2.0.2.0)#1 Oracle RAC 10g Release 2 (10.2.0.3.
Usable kernels Cluster software VCS 4.1 MP3#6 2.6.9-42.0.3.EL LifeKeeper v6 2.6.9-42.0.3.ELsmp LifeKeeper v6 Update1 2.6.9-42.0.3.ELlargesmp LifeKeeper v6 Update2 LifeKeeper v6 Update3 LifeKeeper v6 Update4 LifeKeeper v7 LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 LifeKeeper v7 Update4 Oracle RAC 10g Release 2 (10.2.0.2.0)#1 Oracle RAC 10g Release 2 (10.2.0.3.0)#2 Oracle RAC 10g Release 2 (10.2.0.4.0)#2 Oracle RAC 10g Release 2 (10.2.0.5.
Usable kernels Cluster software Oracle RAC 10g Release 2 (10.2.0.2.0)#1 Oracle RAC 10g Release 2 (10.2.0.3.0)#2 Oracle RAC 10g Release 2 (10.2.0.4.0)#2 Oracle RAC 10g Release 2 (10.2.0.5.0) + Patch 11066597#3 Oracle RAC 11g Release 1 (11.1.0.6.0)#4 Oracle RAC 11g Release 1 (11.1.0.7.0)#5 Oracle RAC 11g Release 2 (11.2.0.2.0)#7 2.6.9-89.EL LifeKeeper v7 2.6.9-89.ELsmp LifeKeeper v7 Update1 2.6.9-89.
¢ ¢ Configurations that include raw devices and Cluster Ready Service (CRS) Configurations that include the Automatic Storage Management (ASM) function (raw devices used) and Cluster Ready Service (CRS) Configurations that include the Automatic Storage Management (ASM) function (the ASMLib kernel driver (ASMLib) is used) and Cluster Ready Service (CRS) For details, see Settings for Oracle RAC on page 3-208.
Volume Managers Supported by HDLM The following table shows the related programs when using a volume manager. Table 3-16 Volume Managers When Using Red Hat Enterprise Linux AS4/ ES4 Kernel architecture IA32 Kernel 2.6.9-11.EL Volume Manager LVM2.01.08-1.0.RHEL4 2.6.9-11.ELsmp 2.6.9-11.ELhugemem 2.6.9-34.EL LVM2.02.01-1.3.RHEL4 2.6.9-34.ELsmp LVM2.02.21-5.el4 2.6.9-34.ELhugemem 2.6.9-34.0.2.EL LVM2.02.01-1.3.RHEL4 2.6.9-34.0.2.ELsmp 2.6.9-34.0.2.ELhugemem 2.6.9-42.EL LVM2.02.06-6.0.RHEL4 2.6.
Kernel architecture Kernel 2.6.9-42.EL Volume Manager LVM2.02.06-6.0.RHEL4 2.6.9-42.0.3.EL 2.6.9-55.EL LVM2.02.21-5.el4 2.6.9-55.ELlargesmp 2.6.9-67.EL LVM2.02.27-2.el4 2.6.9-67.ELlargesmp 2.6.9-78.EL LVM2.02.21-5.el4 2.6.9-78.ELlargesmp LVM2.02.37-3.el4 2.6.9-89.EL LVM2.02.42-5.el4 2.6.9-89.ELlargesmp 2.6.9-100.EL LVM2.02.42-9.el4 2.6.9-100.ELlargesmp EM64T/AMD64 2.6.9-11.EL LVM2.01.08-1.0.RHEL4 2.6.9-11.ELsmp 2.6.9-34.EL LVM2.02.01-1.3.RHEL4 2.6.9-34.ELsmp LVM2.02.21-5.el4 2.6.9-34.
Kernel architecture Kernel Volume Manager LVM2.02.42-9.el4 2.6.9-100.EL 2.6.9-100.ELsmp 2.6.9-100.
#2 The storage system is not supported in an environment where an HDLM device is specified for the boot disk.
Kernel HBA Supported storage systems 2.6.9-89.ELhugemem 2.6.9-100.EL 2.6.9-100.ELsmp 2.6.9-100.ELhugemem Table 3-19 Operating Environments for Boot Disks When Using Red Hat Enterprise Linux AS4/ES4 (IPF) Kernel HBA 2.6.9-55.EL Supported storage systems Emulex Hitachi AMS2000/AMS/WMS/SMS series 2.6.9-55.ELlargesmp Hitachi USP series 2.6.9-67.EL HUS100 series 2.6.9-67.ELlargesmp HUS VM 2.6.9-78.EL Lightning 9900V series 2.6.9-78.ELlargesmp Thunder 9500V series 2.6.9-89.
Kernel HBA Supported storage systems 2.6.9-55.ELlargesmp 2.6.9-67.EL 2.6.9-67.ELsmp 2.6.9-67.ELlargesmp 2.6.9-78.EL 2.6.9-78.ELsmp 2.6.9-78.ELlargesmp 2.6.9-89.EL 2.6.9-89.ELsmp 2.6.9-89.ELlargesmp 2.6.9-100.EL 2.6.9-100.ELsmp 2.6.9-100.ELlargesmp The following table lists the operating environments when an HDLM device is used as a boot disk in a Hitachi Compute Blade environment.
Notes on using HDLM in a Hitachi Compute Blade environment When HDLM is used in a Hitachi Compute Blade environment, the following functions cannot be used: • HotPlug • SystemManager linkage Related Products When Using Red Hat Enterprise Linux 5 The following describes related products when Red Hat Enterprise Linux 5 is used.
Usable kernels Cluster software Oracle RAC 10g Release 2 (10.2.0.4.0)#1 Oracle RAC 10g Release 2 (10.2.0.5.0) + Patch 11066597#2 Oracle RAC 11g Release 1 (11.1.0.6.0)#3 Oracle RAC 11g Release 1 (11.1.0.7.0)#4 RHCM 2.0.60-1 2.6.18-53.el5 HA Monitor 01-54#6#7 2.6.18-53.
Usable kernels Cluster software Oracle RAC 11g Release 2 (11.2.0.2.0)#5 RHCM 2.0.84-2 2.6.18-128.el5 HA Monitor 01-54#6#7 2.6.18-128.el5PAE LifeKeeper v6 Update4 LifeKeeper v7 LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 LifeKeeper v7 Update4 LifeKeeper v7 Update5 LifeKeeper v8 LifeKeeper v8 Update1 Oracle RAC 10g Release 2 (10.2.0.4.0)#1 Oracle RAC 10g Release 2 (10.2.0.5.0) + Patch 11066597#2 Oracle RAC 11g Release 1 (11.1.0.6.0)#3 Oracle RAC 11g Release 1 (11.1.0.7.
Usable kernels Cluster software LifeKeeper v7 Update3 LifeKeeper v7 Update4 LifeKeeper v7 Update5 LifeKeeper v8 LifeKeeper v8 Update1 Oracle RAC 10g Release 2 (10.2.0.4.0)#1 Oracle RAC 10g Release 2 (10.2.0.5.0) + Patch 11066597#2 Oracle RAC 11g Release 1 (11.1.0.6.0)#3 Oracle RAC 11g Release 1 (11.1.0.7.0)#4 Oracle RAC 11g Release 2 (11.2.0.1.0)#5 Oracle RAC 11g Release 2 (11.2.0.2.0)#5 RHCM 2.0.115-34 2.6.18-238.el5 HA Monitor 01-54#6#7 2.6.18-238.
Usable kernels Cluster software Oracle RAC 11g Release 2 (11.2.0.2.0)#5 RHCM 2.0.115-85 2.6.18-308.el5 LifeKeeper v7 Update5 2.6.18-308.el5PAE LifeKeeper v8 LifeKeeper v8 Update1 Oracle RAC 10g Release 2 (10.2.0.4.0)#1 Oracle RAC 10g Release 2 (10.2.0.5.0) + Patch 11066597#2 Oracle RAC 11g Release 1 (11.1.0.6.0)#3 Oracle RAC 11g Release 1 (11.1.0.7.0)#4 Oracle RAC 11g Release 2 (11.2.0.1.0)#5 Oracle RAC 11g Release 2 (11.2.0.2.0)#5 RHCM 2.0.115-96 2.6.18-348.el5 Oracle RAC 10g Release 2(10.2.0.4.
¢ Configurations that include the Automatic Storage Management (ASM) function (the ASMLib kernel driver (ASMLib) is used) and Oracle Clusterware Configurations that include the Oracle Cluster File System 2 and Oracle Clusterware For details, see Settings for Oracle RAC on page 3-208.
Usable kernels 2.6.18-348.el5 Cluster software RHCM 2.0.115-109 Table 3-24 Cluster Software Used with Red Hat Enterprise Linux 5 (EM64T/AMD64) Usable kernels 2.6.18-8.el5 Cluster software LifeKeeper v6 Update1 LifeKeeper v6 Update2 LifeKeeper v6 Update3 LifeKeeper v6 Update4 LifeKeeper v7 LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 LifeKeeper v7 Update4 LifeKeeper v7 Update5 LifeKeeper v8 LifeKeeper v8 Update1 Oracle RAC 10g Release 2 (10.2.0.1.0)#1 Oracle RAC 10g Release 2 (10.2.0.
Usable kernels Cluster software Oracle RAC 10g Release 2 (10.2.0.3.0)#2 Oracle RAC 10g Release 2 (10.2.0.4.0)#3 Oracle RAC 10g Release 2 (10.2.0.5.0) + Patch 11066597#1 Oracle RAC 11g Release 1 (11.1.0.6.0)#4 Oracle RAC 11g Release 1 (11.1.0.7.0)#5 Oracle RAC 11g Release 1 (11.1.0.7.0) + Patch 8833297#5 RHCM 2.0.73-1 2.6.18-92.
Usable kernels Cluster software LifeKeeper v8 LifeKeeper v8 Update1 Oracle RAC 10g Release 2 (10.2.0.1.0)#1 Oracle RAC 10g Release 2 (10.2.0.3.0)#2 Oracle RAC 10g Release 2 (10.2.0.4.0)#3 Oracle RAC 10g Release 2 (10.2.0.5.0) + Patch 11066597#1 Oracle RAC 11g Release 1 (11.1.0.6.0)#4 Oracle RAC 11g Release 1 (11.1.0.7.0)#5 Oracle RAC 11g Release 1 (11.1.0.7.0) + Patch 8833297#5 Oracle RAC 11g Release 2 (11.2.0.1.0)#6 Oracle RAC 11g Release 2 (11.2.0.2.0)#7 Oracle RAC 11g Release 2 (11.2.0.3.0)#7 RHCM 2.0.
Usable kernels Cluster software LifeKeeper v8 LifeKeeper v8 Update1 Oracle RAC 10g Release 2 (10.2.0.1.0)#1 Oracle RAC 10g Release 2 (10.2.0.3.0)#2 Oracle RAC 10g Release 2 (10.2.0.4.0)#3 Oracle RAC 10g Release 2 (10.2.0.5.0) + Patch 11066597#1 Oracle RAC 11g Release 1 (11.1.0.6.0)#4 Oracle RAC 11g Release 1 (11.1.0.7.0)#5 Oracle RAC 11g Release 1 (11.1.0.7.0) + Patch 8833297#5 Oracle RAC 11g Release 2 (11.2.0.1.0)#6 Oracle RAC 11g Release 2 (11.2.0.2.0)#7 Oracle RAC 11g Release 2 (11.2.0.3.0)#7 RHCM 2.0.
Usable kernels Cluster software Oracle RAC 10g Release 2 (10.2.0.3.0)#2 Oracle RAC 10g Release 2 (10.2.0.4.0)#3 Oracle RAC 10g Release 2 (10.2.0.5.0) + Patch 11066597#1 Oracle RAC 11g Release 1 (11.1.0.6.0)#4 Oracle RAC 11g Release 1 (11.1.0.7.0)#5 Oracle RAC 11g Release 1 (11.1.0.7.0) + Patch 8833297#5 Oracle RAC 11g Release 2 (11.2.0.1.0)#6 Oracle RAC 11g Release 2 (11.2.0.2.0)#7 Oracle RAC 11g Release 2 (11.2.0.3.0)#7 RHCM 2.0.115-85 2.6.18-308.
Usable kernels Cluster software RHCM 2.0.115-109 #1 Only configurations that include the Automatic Storage Management (ASM) function (raw devices used) and Cluster Ready Service (CRS) are supported. For details, see Settings for Oracle RAC on page 3-208.
¢ ¢ Configurations that include the Automatic Storage Management (ASM) function (raw devices used) and Oracle Clusterware Configurations that include the Automatic Storage Management (ASM) function (the ASMLib kernel driver (ASMLib) is used) and Oracle Clusterware Configurations that include the Oracle Cluster File System 2 and Oracle Clusterware For details, see Settings for Oracle RAC on page 3-208.
Kernel architecture Kernel 2.6.18-128.el5 Volume manager LVM2.02.40-6.el5 2.6.18-128.el5PAE 2.6.18-164.el5 LVM2.02.46-8.el5 2.6.18-164.el5PAE 2.6.18-194.el5 LVM2.02.56-8.el5 2.6.18-194.el5PAE 2.6.18-238.el5 LVM2.02.74-5.el5 2.6.18-238.el5PAE LVM2.02.84-3.el5#1 2.6.18-274.el5 LVM2.02.84-3.el5 2.6.18-274.el5PAE LVM2.02.84-6.el5#2 2.6.18-308.el5 LVM2.02.88-7.el5 2.6.18-308.el5PAE 2.6.18-348.el5 LVM2.02.88-10.el5 2.6.18-348.el5PAE IPF 2.6.18-8.el5 LVM2.02.16-3.el5 2.6.18-53.el5 LVM2.02.
Kernel architecture Kernel Volume manager LVM2.02.84-6.el5#2 2.6.18-308.el5 LVM2.02.88-7.el5 2.6.18-348.el5 LVM2.02.88-10.el5 #1 Combination with cluster software is not supported. #2 Kernel versions 2.6.18-274.12.1 and later are supported. File Systems Supported by HDLM The following table lists the file systems supported by HDLM. Table 3-26 Supported File Systems When Using Red Hat Enterprise Linux 5 Kernel architecture IA32 Kernel File system 2.6.18-8.el5 ext2 (supplied with the OS) 2.6.
Kernel architecture Kernel 2.6.18-128.el5 ext2 (supplied with the OS) 2.6.18-164.el5 ext3 (supplied with the OS) 2.6.18-194.el5 GFS2 (supplied with the OS)# 2.6.18-238.el5 ext2 (supplied with the OS) 2.6.18-274.el5 ext3 (supplied with the OS) 2.6.18-308.el5 2.6.18-348.el5 EM64T/AMD64 File system ext4 (supplied with the OS) GFS2 (supplied with the OS)# 2.6.18-8.el5 ext2 (supplied with the OS) 2.6.18-53.el5 ext3 (supplied with the OS) 2.6.18-92.el5 2.6.18-128.
Table 3-27 Operating Environments for Hitachi Compute Blade When Using Red Hat Enterprise Linux 5 Kernel architecture Kernel IA32 2.6.18-53.el5PAE HBA hitachi 2.6.18-92.el5PAE EM64T Hitachi AMS2000/AMS/WMS/SMS series Hitachi USP series# 2.6.18-128.el5PAE IPF Supported storage systems HUS100 series 2.6.18-164.el5PAE HUS VM 2.6.18-238.el5PAE Lightning 9900V series# 2.6.18-53.el5 Thunder 9500V series 2.6.18-92.el5 Universal Storage Platform V/VM series# 2.6.18-53.
Kernel architecture Kernel HBA Supported storage systems 2.6.18-238.el5PAE# 2.6.18-274.el5# Emulex 2.6.18-274.el5PAE# QLogic 2.6.18-308.el5# 2.6.18-308.el5PAE# 2.6.18-348.el5# 2.6.18-348.el5PAE# IPF 2.6.18-8.el5 Emulex 2.6.18-53.el5 2.6.18-92.el5 2.6.18-128.el5# 2.6.18-164.el5# 2.6.18-194.el5# 2.6.18-238.el5# Brocade Emulex Emulex 2.6.18-274.el5# 2.6.18-308.el5# 2.6.18-348.el5# EM64T/AMD64 2.6.18-8.el5 Emulex QLogic 2.6.18-53.el5 Brocade 2.6.18-92.el5 Emulex 2.6.18-128.el5# QLogic 2.6.
# LUKS is not available in an environment where an HDLM device is used as a boot disk. The following table lists the operating environments when an HDLM device is used as a boot disk in a Hitachi Compute Blade environment. Table 3-29 Operating Environments for Hitachi Compute Blade and Boot Disks When Using Red Hat Enterprise Linux 5 Kernel architecture IA32 Kernel 2.6.18-53.el5PAE HBA hitachi 2.6.18-92.el5PAE 2.6.18-128.
executing the following command, are the same, the versions of HDLM are the same: # /opt/DynamicLinkManager/bin/dlnkmgr view -sys The following tables list the related programs used when creating a cluster: • Table 3-30 Cluster Software Used with Red Hat Enterprise Linux 6 (If an FC-SAN Is Used) on page 3-61 • Table 3-31 Cluster Software Used with Red Hat Enterprise Linux 6 (If an IP-SAN Is Used) on page 3-62 Table 3-30 Cluster Software Used with Red Hat Enterprise Linux 6 (If an FC-SAN Is Used) Kernel
Kernel architecture Usable kernels Cluster software Oracle RAC 11g Release 2(11.2.0.3.0)#1 RHCM 2.6.32-279.el6.x86_64 LifeKeeper v7 Update5 LifeKeeper v8 LifeKeeper v8 Update1 Oracle RAC 11g Release 2(11.2.0.3.0)#1 RHCM 2.6.32-358.el6.x86_64 Oracle RAC 11g Release 2(11.2.0.3.0)#1 RHCM #1 Only configurations that include the Automatic Storage Management (ASM) function (raw devices are used) and Oracle Grid Infrastructure are supported. The HDLM device name can be specified directly for ASM.
Volume Managers Supported by HDLM The following table shows the related programs when using a volume manager. Table 3-32 Volume Managers When Using Red Hat Enterprise Linux 6 Kernel architecture IA32 EM64T/AMD64 Kernel Volume manager 2.6.32-71.el6.i686 LVM2.02.72-8.el6 2.6.32-131.0.15.el6.i686 LVM2.02.83-3.el6 2.6.32-220.el6.i686 LVM2.02.87-6.el6 2.6.32-279.el6.i686 LVM2.02.95-10.el6 2.6.32-358.el6.i686 LVM2.02.98-9.el6 2.6.32-71.el6.x86_64 LVM2.02.72-8.el6 2.6.32-131.0.15.el6.x86_6 LVM2.
Kernel architecture Kernel File system GFS2 (supplied with the OS)# 2.6.32-220.el6.x86_64 ext2 (supplied with the OS) ext3 (supplied with the OS) ext4 (supplied with the OS) GFS2 (supplied with the OS)# xfs (supplied with the OS)# 2.6.32-279.el6.x86_64 ext2 (supplied with the OS) 2.6.32-358.el6.x86_64 ext3 (supplied with the OS) ext4 (supplied with the OS) GFS2 (supplied with the OS)# # An HDLM device cannot be used as a boot disk.
Kernel architecture Kernel Supported storage systems HBA 2.6.32-279.el6.x86_6 4# 2.6.32-358.el6.x86_6 4# # LUKS is not available in an environment where an HDLM device is used as a boot disk. Table 3-35 Operating Environments for Boot Disks When Using Red Hat Enterprise Linux 6 (If an IP-SAN Is Used) Kernel architecture IA32 Kernel 2.6.32-220.el6.i686 Supported storage systems HBA Red Hat Hitachi AMS2000 series 2.6.32-220.31.1.el6.i 686 2.6.32-279.el6.i686 2.6.32-358.el6.i686 EM64T/AMD64 2.6.
The following table lists the related programs used when creating a cluster. Table 3-36 Cluster Software When Using SUSE LINUX Enterprise Server 10 Kernel architecture IA32 Usable kernels 2.6.16.21-0.8-default 2.6.16.21-0.8-smp Cluster software Oracle RAC 10g Release 2 (10.2.0.3.0)#1 2.6.16.21-0.8-bigsmp 2.6.16.46-0.14-default Heartbeat (2.0.8-0.19)#2 2.6.16.46-0.14-smp Oracle RAC 10g Release 2 (10.2.0.3.0)#1 2.6.16.46-0.14-bigsmp Oracle RAC 11g Release 1 (11.1.0.6.0)#3 2.6.16.60-0.
Kernel architecture Usable kernels 2.6.16.60-0.54.5-default Cluster software Heartbeat (2.1.4-0.15.3)#2 2.6.16.60-0.54.5-smp 2.6.16.60-0.54.5-xen 2.6.16.60-0.85.1-default Heartbeat (2.1.4-0.24.9)#2 2.6.16.60-0.85.1-smp Oracle RAC 10g Release 2(10.2.0.3.0)#1 2.6.16.60-0.85.1-xen #1 Only configurations that include the Automatic Storage Management (ASM) function (using raw devices) and Cluster Ready Service (CRS) are supported. For details, see Settings for Oracle RAC on page 3-208.
Kernel architecture Kernel 2.6.16.60-0.85.1-default Volume manager LVM2.02.17-7.30.1 2.6.16.60-0.85.1-smp 2.6.16.60-0.85.1-bigsmp 2.6.16.60-0.85.1-xenpae IPF EM64T/AMD64 2.6.16.21-0.8-default LVM2.02.02-11.2 2.6.16.46-0.14-default LVM2.02.17-7.9 2.6.16.60-0.21-default LVM2.02.17-7.19 2.6.16.60-0.54.5-default LVM2.02.17-27.8 2.6.16.60-0.85.1-default LVM2.02.17-7.30.1 2.6.16.21-0.8-default LVM2.02.02-11.2 2.6.16.21-0.8-smp 2.6.16.46-0.14-default LVM2.02.17-7.9 2.6.16.46-0.14-smp 2.6.16.
Boot Disk Environments and Hitachi Compute Blade Environments Supported by HDLM HDLM supports Hitachi Compute Blade in any of the environments listed in Table 3-38 Operating Environments for Hitachi Compute Blade When Using SUSE LINUX Enterprise Server 10 on page 3-69. For details on OSs (kernels) that each Hitachi Compute Blade model supports, see the Hitachi Compute Blade documentation. For details on OSs (kernels) that each storage system model supports, see the storage system documentation.
Kernel architecture Kernel 2.6.16.60-0.21default 2.6.16.60-0.21-smp HBA Brocade QLogic 2.6.16.60-0.21bigsmp Lightning 9900V series Thunder 9500V series Universal Storage Platform V/VM series Virtual Storage Platform series 2.6.16.60-0.21xenpae QLogic 2.6.16.60-0.54.5default Brocade 2.6.16.60-0.54.5smp Supported storage systems QLogic 2.6.16.60-0.54.5bigsmp 2.6.16.60-0.54.5xenpae 2.6.16.60-0.85.1default QLogic 2.6.16.60-0.85.1smp 2.6.16.60-0.85.1bigsmp 2.6.16.60-0.85.1xenpae IPF 2.6.16.60-0.
Kernel architecture Kernel HBA Supported storage systems 2.6.16.60-0.85.1xen Table 3-40 Operating Environments for Hitachi Compute Blade and Boot Disks When Using SUSE LINUX Enterprise Server 10 on page 3-71 lists the operating environments when an HDLM device is used as a boot disk in a Hitachi Compute Blade environment.
Table 3-41 Volume Managers When Using SUSE LINUX Enterprise Server 11 Kernel architecture IA32 Kernel Volume manager 2.6.27.21-0.1.2-default LVM2.02.39-17.3 2.6.27.21-0.1.2-pae 2.6.27.21-0.1.2-xen 2.6.32.12-0.7.1-default LVM2.02.39-18.26.1 2.6.32.12-0.7.1-pae 2.6.32.12-0.7.1-xen 3.0.13-0.27-default LVM2.02.84-3.25.5 3.0.13-0.27-pae 3.0.76-0.11-default LVM2.02.98-0.25.3 3.0.76-0.11-pae IPF EM64T/AMD64 2.6.27.21-0.1.2-default LVM2.02.39-17.3 2.6.32.12-0.7.1-default LVM2.02.39-18.26.1 3.0.
Kernel architecture Kernel File system 2.6.27.21-0.1.2-xen ReiserFS(supplied with the OS) 2.6.32.12-0.7.1-default 2.6.32.12-0.7.1-pae 2.6.32.12-0.7.1-xen 3.0.13-0.27-default 3.0.13-0.27-pae 3.0.76-0.11-default 3.0.76-0.11-pae IPF 2.6.27.21-0.1.2-default 2.6.32.12-0.7.1-default 3.0.13-0.27-default 3.0.76-0.11-default EM64T/AMD64 2.6.27.21-0.1.2-default 2.6.27.21-0.1.2-xen 2.6.32.12-0.7.1-default 2.6.32.12-0.7.1-xen 3.0.13-0.27-default 3.0.76-0.
Kernel architecture Kernel 2.6.27.21-0.1.2-xen QLogic 2.6.32.12-0.7.1default Brocade 2.6.32.12-0.7.1-pae QLogic 2.6.32.12-0.7.1-xen 3.0.13-0.27-default Supported storage systems HBA QLogic HUS VM Lightning 9900V series Thunder 9500V series Universal Storage Platform V/VM series Virtual Storage Platform series 3.0.13-0.27-pae 3.0.76-0.11-default 3.0.76-0.11-pae IPF 2.6.27.21-0.1.2default Brocade 2.6.32.12-0.7.1default EM64T/AMD64 2.6.27.21-0.1.2default Brocade 2.6.27.21-0.1.
Kernel architecture Kernel EM64T/AMD64 Volume manager LVM2.02.21-5.el4 2.6.9-55.0.0.0.2.EL 2.6.9-55.0.0.0.2.ELsmp 2.6.9-55.0.0.0.2.ELlargesmp LVM2.02.27-2.el4 2.6.9-67.0.0.0.1.EL 2.6.9-67.0.0.0.1.ELsmp 2.6.9-67.0.0.0.1.
Kernel architecture Kernel HBA Supported storage systems 2.6.9-67.0.0.0.1.ELl argesmp Related Products When Using Oracle Enterprise Linux 5 The following describes related products when Oracle Enterprise Linux 5 is used. Cluster Software Supported by HDLM When you use HDLM in a cluster configuration, you must install the same version of HDLM on all of the nodes that make up the cluster. If different versions of HDLM are installed, the cluster system might not operate correctly.
Kernel architecture Usable kernels 2.6.18-164.el5 Cluster software HA Monitor 01-54#3#4 Oracle RAC 11g Release 2(11.2.0.2.0)#1 2.6.18-194.el5 None 2.6.18-238.el5 HA Monitor 01-54#3#4 2.6.18-274.el5 HA Monitor 01-54#3#4 Oracle RAC 11g Release 1(11.1.0.7.0)#2 #1 Only configurations that include the Automatic Storage Management (ASM) function (raw devices are used) and Oracle Clusterware are supported. For details, see Settings for Oracle RAC on page 3-208.
Kernel architecture Kernel Volume manager 2.6.18-238.el5PAE 2.6.18-274.el5 LVM2.02.84-3.el5 2.6.18-274.el5PAE EM64T/AMD64 2.6.18-53.el5 LVM2.02.26-3.el5 2.6.18-164.el5 LVM2.02.46-8.el5 2.6.18-194.el5 LVM2.02.56-8.el5 2.6.18-238.el5 LVM2.02.74-5.el5 2.6.18-274.el5 LVM2.02.84-3.el5 File Systems Supported by HDLM The following table lists the file systems supported by HDLM. Table 3-48 Supported File Systems When Using Oracle Enterprise Linux 5 Kernel architecture IA32 Kernel File system 2.
For details on the OSs (kernels) that each storage system model supports, see the storage system documentation. Table 3-49 Operating Environments for Boot Disks When Using Oracle Enterprise Linux 5 Kernel architecture IA32 Kernel 2.6.18-53.el5 HBA QLogic 2.6.18-53.el5PAE 2.6.18-164.el5 Emulex 2.6.18-164.el5PAE QLogic Supported storage systems Hitachi AMS2000/AMS/ WMS/SMS series Hitachi USP series HUS100 series HUS VM 2.6.18-194.el5 Lightning 9900V series 2.6.18-194.
Table 3-50 Cluster Software When Using Oracle Unbreakable Enterprise Kernel 5 Kernel architecture Usable kernels Cluster software IA32 2.6.32-200.13.1.el5uek Oracle RAC 11g Release 2(11.2.0.3.0)#1 EM64T/AMD64 2.6.32-100.26.2.el5 Oracle RAC 11g Release 1(11.1.0.7.0)#2 Oracle RAC 11g Release 2(11.2.0.3.0)#1 2.6.32-200.13.1.el5uek Oracle RAC 11g Release 2(11.2.0.3.
An HDLM device cannot be used as a boot disk. Boot Disk Environments Supported by HDLM HDLM supports boot disks in any of the environments listed in Table 3-52 Operating Environments for Boot Disks When Using Oracle Unbreakable Enterprise Kernel 5 on page 3-81. For details on the OSs (kernels) that each storage system model supports, see the storage system documentation.
Table 3-53 Cluster Software When Using Oracle Unbreakable Enterprise Kernel 6 Kernel architecture EM64T/AMD64 Usable kernels Cluster software 2.6.39-200.24.1.el6uek.x8 Oracle RAC 11g Release 6_64 2(11.2.0.3.0)# 2.6.39-200.29.1.el6uek.x8 Oracle RAC 11g Release 6_64 2(11.2.0.3.0)# # Only configurations that include the Automatic Storage Management (ASM) function (using raw devices) and Oracle Grid Infrastructure are supported. For details, see Settings for Oracle RAC on page 3-208.
An HDLM device cannot be used as a boot disk. Boot Disk Environments Supported by HDLM HDLM supports boot disks in any of the environments listed in Table 3-55 Operating Environments for Boot Disks When Using Oracle Unbreakable Enterprise Kernel 6 on page 3-83. For details on the OSs (kernels) that each storage system model supports, see the storage system documentation.
Disk Requirements The following table lists the disk capacity requirements for a host. Table 3-57 Disk Capacity Requirements for a Host Directory Disk capacity requirements /tmp 570 KB /var p MB#1 + q MB#2 + 4 MB#3 + u MB#4 + 20 MB#5 + v MB#6 + 45 MB (100 MB#7) /opt 168 MB /etc y MB#8 + z MB#9 + 5.5 MB (10 MB#7) /root 580 KB /sbin 500 KB #1 This size differs depending on the settings for log files (maximum size: 30 GB).
The size of each log file (dlmwebagent[1-N].log) is 9900 KB (approximately 10 MB). The size of the log files is calculated as approximately 20 MB because two log files are created by default. You can create a maximum of 16 log files depending on the setting in the dlmwebagent.properties file. If you create 16 log files, the size of the log files will be approximately 160 MB. #6 The size of the log files for the dlmcfgmgr utility.
Target Supported number Oracle Unbreakable Enterprise Kernel 5 Oracle Unbreakable Enterprise Kernel 6 Number of LUs for one port in a storage system SUSE LINUX Enterprise Server 1 to 32 Red Hat Enterprise Linux 4 1 to 512 SUSE LINUX Enterprise Server Oracle Enterprise Linux 4 Oracle Unbreakable Enterprise Kernel 5 Oracle Unbreakable Enterprise Kernel 6 Red Hat Enterprise Linux 5 1 to 4096# Red Hat Enterprise Linux 6 Oracle Enterprise Linux 5 Total number of paths (Number of LU x Number of paths pe
Table 3-59 Examples of HDLM Configuration Definition Utility Execution Times in a Large-scale HDLM Operating Environment HDLM configuration utility Execution time Description dlmcfgmgr -r 4 minutes 31 seconds Registers the path to an HDLM device. dlmcfgmgr -o all 9 minutes 34 seconds Excludes all managed HDLM devices (4,096 devices) from the management targets. dlmcfgmgr -i all 63 minutes 43 seconds Includes all unmanaged HDLM devices (4,096 devices) as management targets.
Table 3-61 Xen Hypervisor Operating Environments Supported by HDLM Kernel architecture OS SUSE LINUX Enterprise Server 10 IA32 EM64T/AMD64 SUSE LINUX Enterprise Server 11 IA32 EM64T/AMD64 • Kernel Xen hypervisor version 2.6.16.60-0.21xenpae xen-3.2.0_16718_14-0. 4 2.6.16.60-0.54.5xenpae xen-3.2.3_17040_16-0. 4.9 2.6.16.60-0.85.1xenpae xen-3.2.3_17040_34-0. 7 2.6.16.60-0.21-xen xen-3.2.0_16718_14-0. 4 2.6.16.60-0.54.5xen xen-3.2.3_17040_16-0. 4.9 2.6.16.60-0.85.1xen xen-3.2.3_17040_34-0.
Kernel architecture OS Kernel KVM version 2.6.32-131.0.15.el6 .x86_64 2.6.32-220.el6.x86 _64 2.6.32-279.el6.x86 _64 2.6.32-358.el6.x86 _64 Oracle Unbreakable Enterprise Kernel 5 EM64T/AMD64 2.6.32-100.26.2.el5 Oracle Unbreakable Enterprise Kernel 6 IA32 2.6.39-200.24.1.el6 uek.i686 EM64T/AMD64 2.6.39-200.24.1.el6 uek.x86_64 2.6.32-200.13.1.el5 uek 2.6.39-200.29.1.el6 uek.x86_64 2.6.39-200.29.2.el6 uek.
Figure 3-1 Flow of HDLM Environment Setup HDLM Installation Types This subsection describes the following types of HDLM installation: new installation, upgrade installation, and re-installation. New installation of HDLM: Installing HDLM on a server on which HDLM has not been installed is called a new installation of HDLM.
Installing a new version of HDLM without removing the existing old version is called an upgrade installation of HDLM. Re-installation of HDLM: Installing the same version of HDLM, to restore the existing version, without first removing that version is called a re-installation of HDLM.
perform another installation, the oldest file is deleted and a new log file is output. • The following information is inherited from the previous environment even when HDLM is installed during an upgrade installation or re-installation: ¢ Information for defining the configuration of an HDLM device ¢ Information for setting up HDLM functions ¢ Log information ¢ Driver configuration Notes on Creating an HDLM Environment This section provides notes on creating an HDLM environment.
HDLM command to display the path status, the target ID of the path before the change might be displayed. In addition, the HDLM device name might be changed after the host is restarted. Check the HDLM device name after the host is restarted. If the HDLM device name has been changed, reconfigure the higher-level program. However, you can avoid the above situations by setting a permanent target ID for each LU with the HBA driver persistent binding functionality.
¢ HDLM information is missing in the /etc/init.d/boot.localfs file, the /etc/init.d/boot.md file, or the /etc/init.d/lvm2 file. Confirm that the HDLM information is missing by executing the following commands: # grep Required-Start /etc/init.d/boot.localfs # grep Required-Start /etc/init.d/boot.md # grep Required-Start /etc/init.d/boot.lvm If the information in boot.hdlm is not output after command execution, HDLM information is missing.
Execute the /sbin/service command to make sure that the HAL daemon is not running. # /sbin/service haldaemon status d. Execute the dlmcfgmgr utility (dlmcfgmgr -r or dlmcfgmgr -i) to configure the HDLM device. # /sbin/dlmcfgmgr -r or # /sbin/dlmcfgmgr -i e. Start the HAL daemon. Execute the /sbin/service command to start the HAL daemon. # /sbin/service haldaemon start Make sure that the HAL daemon is running. Execute the /sbin/service command to make sure that the HAL daemon is running.
hbsasrv, HiScan, hdvmagt_account, hdvmagt_schedule, hldutil, TIC Installing HDLM The following section describes how to install HDLM for a new installation, for a re-installation, and for an upgrade installation. Depending on the procedure, the host might have to be restarted after HDLM is installed. HDLM can also be installed by performing an unattended installation, which enables a user to install HDLM without entering information. Select the procedure suitable for your environment.
If the disks to be managed by HDLM were mounted by specifying SCSI devices, unmount them. First, check the current settings. Execute the following command: # mount The current settings will be output as shown in Figure 3-2 Execution Results of the mount Command on page 3-97. Figure 3-2 Execution Results of the mount Command The shaded portion shows the SCSI device to be managed by HDLM. Execute the following command on this SCSI device to unmount it: # umount /mntpt 5.
• A physical volume is created for only one of the logical device files on any one path for each SCSI device to be managed by HDLM. In addition, a volume group is created for only the physical volume. This subsection describes how to check whether this condition exists. • The logical volume is unmounted. The following explains how to check whether the above condition exists when the volume group vg02 consists of either one physical volume or two physical volumes.
Figure 3-5 Result of Executing vgdisplay -v (When There Are Two Physical Volumes) Check the shaded portion and confirm that vg02 consists of /dev/sde and / dev/sdu, both of which have been defined for the same device to be managed by HDLM. Setting in the syslogd Settings File The log upon executing the installation is output to syslog.
Figure 3-6 Example of the Contents of the syslogd Settings File (In Red Hat Enterprise Linux) When you collect audit log data, we recommend that you use any of the extended facilities (local0 to local7) as the exclusive output destination for the data. We also recommend that you specify info as the severity level for the extended facility. This example shows how to specify the recommended settings in the /etc/syslog.conf file: local0.
¢ Store the license key file (*.plk) in the /var/tmp directory, under the name hdlm_license. /var/tmp/hdlm_license ¢ Execute the following commands to create the license key file (dlm.lic_key) in the /etc/opt/DynamicLinkManager directory. # mkdir /etc/opt/DynamicLinkManager # echo "license-key" > /etc/opt/DynamicLinkManager/dlm.lic_key 3. Insert the DVD-ROM and mount it. If the DVD-ROM was not automatically mounted, execute the mount command to mount the DVD-ROM to the fixed mount point.
# volname /dev/cdrom VOL01234 # 4. Check the version of HDLM. Execute installux.sh or the HDLM installation utility (installhdlm) stored on the HDLM DVD-ROM to check the version of HDLM that will be installed. The following example shows how to execute the command when the mount point for the DVD-ROM is /media/cdrom: ¢ When executing installux.sh # /media/cdrom/installux.
Release : : xx If HDLM Version is x.x.x.x.xxx, the installed version of HDLM is correct. x.x.x.x.xxx indicates the HDLM version that was installed. 8. If IP-SAN is used for the connection between the host and the storage system, change iscsi_boot=n, written in the /etc/opt/ DynamicLinkManager/hdlm.conf file, to iscsi_boot=y. 9. If you want to set the HDLM driver options, run the dlmsetopt utility. For details on this utility, see dlmsetopt Utility for Setting HDLM Driver Options on page 7-37.
Add the shaded line shown in the above figure. 15. Specify the settings required for using LUKS. Perform this step if your host OS uses LUKS. If HDLM manages a SCSI device that has been configured to use LUKS, the LUKS settings must be migrated from the SCSI device to an HDLM device. For details on setting up LUKS, see Settings for LUKS on page 3-182. 16. Specify the settings required for using md devices. If you want to use md devices, create them in a multi-path environment.
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(1) Reservation Status : Intermittent Error Monitor : off Dynamic I/O Path Control : off(10) HDLM Manager Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.x-xx yyyy/mm/dd hh:mm:ss 1000 HDLM Driver Ver WakeupTime Alive x.x.
2. Unmount the HDLM devices. If HDLM-managed devices have been mounted by specifying HDLM devices, unmount them. 3. Back up the HDLM-managed disks (for example, to tape). Perform this operation if necessary. Deactivating the md Devices You must deactivate any md devices that are being used before re-installing or upgrading HDLM. 1. Execute the following command to deactivate the md devices: # mdadm -S --scan 2. Execute the following command to make sure that the md devices have been deactivated.
Performing a Re-installation of HDLM The following is the procedure for a re-installation. Some preparations before installing HDLM are required. For details about such preparations, see Preparations for an Upgrade Installation or Re-installation of HDLM on page 3-105. The license key is required when you re-install HDLM after the valid license period has expired. To perform a re-installation of HDLM: 1. Log on to Linux as the root user. 2. Prepare the license key. Store the license key file (*.
Distribution Red Hat Enterprise Linux 5 Mount point /media/cdrom Red Hat Enterprise Linux 6 SUSE LINUX Enterprise Server /media/cdrom If the DVD-ROM is automatically mounted: /media/ media-volume-id # Note 1 HDLM cannot be installed if the DVD-ROM is mounted to a mount point other than the above. Note 2 To copy the DVD-ROM to a directory, and then install HDLM from that directory, copy the DVD-ROM to a directory with the same name as the mount point noted above.
5. Perform the installation. Execute installux.sh or the installhdlm utility stored on the HDLM DVD-ROM to start installation. The following shows an installation execution example for when the DVDROM mount point is /media/cdrom. ¢ When executing installux.sh # /media/cdrom/installux.sh ¢ When executing the installhdlm utility # /media/cdrom/HDLM_Linux/installhdlm 6. The KAPL09093-I message is displayed to confirm that you want to perform an upgrade installation.
set path= ( $path /opt/DynamicLinkManager/bin ) If the PATH environment variable is not set, specify an absolute path to execute commands and utilities. If you have performed steps 10, go to step 13. 12. Restart the host. Execute the following command to restart the host: # shutdown -r now A path will be established in the HDLM device and the HDLM manager will start. 13.
unused devices: Make sure that md0 : active is displayed and that the HDLM devices are displayed. 17. Specify the settings required for using the volume management software. If you performed the operations described in Deactivating the Volume Group on page 3-106 in Preparations for an Upgrade Installation or Reinstallation of HDLM on page 3-105, perform the following steps to activate the volume group: If you did not perform step 12: Go to step 18. If you performed step 12: Go to step 19.
Performing an Upgrade Installation of HDLM The following is the procedure for an upgrade installation. The preparations before installing HDLM are required. For details about the preparations before installing HDLM, see Preparations for an Upgrade Installation or Reinstallation of HDLM on page 3-105. A license key is required if you perform an upgrade installation of HDLM from a version earlier than 5.4 or if you install HDLM 5.4 or a later version after the valid license period has expired.
Distribution Mount point /media/ media-volume-id # Note 1 HDLM cannot be installed if the DVD-ROM is mounted to a mount point other than the above. Note 2 To copy the DVD-ROM to a directory, and then install HDLM from that directory, copy the DVD-ROM to a directory with the same name as the mount point noted above. If the file permissions or the directory structure differs, HDLM cannot be installed. # This refers to the volume name for the CD-ROM or other media, formatted for ISO-9660 file systems.
¢ When executing installux.sh # /media/cdrom/installux.sh ¢ When executing the installhdlm utility # /media/cdrom/HDLM_Linux/installhdlm 6. The KAPL09093-I message is displayed to confirm that you want to perform an upgrade installation. Check the HDLM version, and if it is correct, enter y. 7. Make sure that HDLM is installed. Execute the following command to display detailed information about the installed package. # rpm -qi HDLM Name : HDLM Version : x.x.x.x.
If the PATH environment variable is not set, specify an absolute path to execute commands and utilities. If you have performed steps 11, go to step 14. 13. Restart the host. Execute the following command to restart the host: # shutdown -r now A path will be established in the HDLM device and the HDLM manager will start. 14.
Make sure that md0 : active is displayed and that the HDLM devices are displayed. 18. Specify the settings required for using the volume management software. If you performed the operations described in Deactivating the Volume Group on page 3-106 in Preparations for an Upgrade Installation or Reinstallation of HDLM on page 3-105, perform the following steps to activate the volume group: If you did not perform step 13: Go to step 19. If you performed step 13: Go to step 20.
The procedure for performing an unattended installation of HDLM is described below. Note that preparations before installing HDLM are required. For details about the preparations before performing a new installation of HDLM, see Preparations for a New Installation of HDLM on page 3-96. For details about the preparations before performing a re-installation or an upgrade installation of HDLM, see Preparations for an Upgrade Installation or Re-installation of HDLM on page 3-105. 1.
the mount point noted above. If the file permissions or the directory structure differs, HDLM cannot be installed. # This refers to the volume name for the CD-ROM or other media, formatted for ISO-9660 file systems. Use the volname command to check media-volume-id. The following shows an execution example for when media-volume-id is VOL01234. # volname /dev/cdrom VOL01234 # 4. Check the version of HDLM. Execute installux.
6. Perform the installation. Execute installux.sh or the installhdlm utility stored on the HDLM DVD-ROM to start installation. The following shows an installation execution example for when the DVDROM mount point is /media/cdrom. ¢ When executing installux.sh # /media/cdrom/installux.
The Linux functionality that adds LABEL= to a SCSI device is not supported in HDLM. Do not use this functionality. An example of how to edit the /etc/fstab file is shown in the following figure: Add the shaded line shown in the above figure. 11. Specify the settings required for using LUKS. Perform this step if your host OS uses LUKS. If HDLM manages a SCSI device that has been configured to use LUKS, the LUKS settings must be migrated from the SCSI device to an HDLM device.
# mount /dev/vg01/lvol1 /mnt/lvol1 16. Specify the settings required for using virtual environments. If you are using Xen, set up Xen to use HDLM devices in domainU. If you are using KVM, register HDLM devices into the hardware configuration file. For details on operating environments for the virtual environments supported by HDLM, see Virtual Environments Supported by HDLM on page 3-87.
2. Check the HDLM devices specified in the /etc/fstab file on the replication-source host. The following is an example of the /etc/fstab file in which HDLM devices are specified: : /dev/sddlmaa1 /boot ext3 defaults 1 2 : /dev/sddlmaa3 swap swap defaults 0 0 : 3. Verify that LABEL shows the HDLM devices on the replication-source host. An example of executing the command is as follows: # /sbin/blkid -c /dev/null /dev/sddlmaa1 /dev/sddlmaa1: LABEL="/boot" TYPE="ext3" Verify that LABEL shows /boot.
An example of executing the command is as follows: # /sbin/mkswap -L SWAP-sda3 /dev/sddlmaa3 Setting up swapspace version 1, size = 4095996 KiB LABEL=SWAP-sda3, no uuid c. Execute the swapon command to enable the swap device. An example of executing the command is as follows: # /sbin/swapon /dev/sddlmaa3 d. 4. Execute the blkid command to verify that LABEL setting is applied.
For Deployment Manager, create a disk image of the replication-source host. For Compute Systems Manager: Use Compute Systems Manager to obtain a snapshot of the replicationsource host. For Deployment Manager: Use Deployment Manager to back up the replication-source host disk. 7. Restore the status of the replication-source host.
addition, execute the swapon -s command to check the devices used as swap devices. The following examples show how to use commands when the /boot line and the swap line are edited in step 4. In the execution results, HDLM devices might be output or SCSI devices might be output. When an HDLM device is output Examples of executing the commands are as follows: # /bin/mount : /dev/sddlmab1 on /boot type ext3 (rw) : /boot corresponds to /dev/sddlmab1.
Edit the /etc/fstab file based on the checked results in steps 10 and 11 (this step is performed only when SCSI devices are output in step 10).
# /opt/DynamicLinkManager/bin/dlnkmgr view -lu Product : AMS SerialNumber : 85003482 LUs : 1 iLU HDevName Device PathID Status 0115 sddlmab /dev/sda 000000 Online /dev/sdb 000001 Online KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss # The above execution results indicate that one storage system and one LU in a two-path configuration are recognized.
# /sbin/blkid -c /dev/null /dev/sddlmaa3 /dev/sddlmaa3: TYPE="swap" When the UUID setting is not configured, use the method below to configure the UUID setting. When the partition type is not swap and the file system type is ext4: a. Execute the tune2fs command to configure the UUID setting. An example of executing the command is as follows: # /sbin/tune2fs -U `/usr/bin/uuidgen` /dev/sddlmaa1 tune2fs 1.39 (29-May-2006) b. Execute the blkid command to verify that the UUID setting is configured.
: #/dev/sddlmaa1 /boot UUID=a136da75-c151-472d-ac5c-20f165f93776 defaults 1 2 : #/dev/sddlmaa3 swap UUID=898c0125-39b1-4e0d-9dad-4118de688349 0 0 : ext4 /boot defaults ext4 1 2 swap defaults 0 0 swap swap defaults a. Copy the lines for HDLM devices. b. Comment out the copy-source lines by placing a hash mark (#) at the beginning of each of the lines. c. Change the HDLM devices in the copied data to the format used for LABEL. 5. Prepare for replication on the replication-source host.
For Compute Systems Manager: Use Compute Systems Manager to input the Deployment Template information about the replication-destination host. For Deployment Manager: Use Deployment Manager to create a disk replication information file for the replication-destination host. 9. For Compute Systems Manager, distribute the Master Image to the replication-destination host. For Deployment Manager, distribute the disk image to the replicationdestination host.
/dev/sda1 on /boot type ext4 (rw) : /boot corresponds to /dev/sda1. # /sbin/swapon -s Filename Type /dev/sda3 partition swap corresponds to /dev/sda3. Size Used 4095992 0 Priority -1 11. On the replication-destination host, execute the HDLM configuration definition utility (dlmcfgmgr) with the -v parameter to check the correspondence between the HDLM devices and SCSI devices.
/dev/sddlmab3 : swap swap defaults 0 0 a. Copy the lines in which devices are specified with UUID. b. Comment out the copy-source lines by placing a hash mark (#) at the beginning of each of the lines. c. Change the devices described using UUID in the copied data to descriptions using HDLM devices. 13. Restart the replication-destination host. To apply the edited results obtained in step 12, restart the replicationdestination host by executing the following command: # /sbin/shutdown -r now 14.
Notes on Installing HDLM in a Boot Disk Environment Note the following when using HDLM on a boot disk: • The storage system for which the boot disk will be created must satisfy the following conditions: ¢ ¢ The storage system supports the boot disk functionality even if HDLM is not used. HBAs support startup from the storage system. • When you install the OS, create the root directory (/) and the /boot directory in separate partitions.
usbdevfs on /proc/bus/usb type usbdevfs (rw) /dev/sda1 on /boot type ext3 (rw) none on /dev/shm type tmpfs (rw) Confirm that the root directory is /dev/sda2, and the /boot directory is /dev/sda1. c. Using an editor such as vi, change the LABEL specification to an sd device specification. (before) LABEL=/ / LABEL=/boot ext3 /boot defaults 1 1 ext3 defaults 1 2 (after) /dev/sda2 /dev/sda1 • / ext3 defaults /boot ext3 defaults 1 1 1 2 d. Install HDLM. e.
¢ • When using Red Hat Enterprise Linux AS4/ES4 or SUSE LINUX Enterprise Server: You must first remove HDLM before updating the kernel package, and then re-install it after the update. Note that removing and re-installing HDLM might change the correspondence between HDLM devices and SCSI devices. To update the kernel package in an environment that satisfies the following conditions, you need to change the Persistent Binding setting: ¢ The host is in a Hitachi Compute Blade environment.
Upgrade Installation in an Environment Where an HDLM Device Is Used as a Boot Disk To perform an upgrade installation of HDLM in a boot disk environment that uses a SCSI device (for details, see Upgrade Installation in an Environment Where an HDLM Device Is Used as a Boot Disk on page 3-147): 1. Edit the configuration file to change the definition so that the OS will start with a SCSI device specified. In the definition before the change, the OS starts with HDLM specified.
Upgrade Installation in an Environment Where a Logical Volume (LVM2) on an HDLM Device Is Used as a Boot Disk To perform an upgrade installation of HDLM in a multi-path boot disk environment that uses a logical volume (LVM2) on an HDLM device (for details, see Upgrade Installation in an Environment Where a Logical Volume (LVM2) on an HDLM Device Is Used as a Boot Disk on page 3-166): 1. Edit the configuration file to change the definition so that the OS will start with a SCSI device specified.
Boot loader ELILO Configuration file name /etc/elilo.conf To install HDLM in a boot disk environment that uses a SCSI device, and set up the environment: 1. Log in to Linux as a user with root permissions. 2. If the OS is SUSE LINUX Enterprise Server 10 SP3 or later, specify multipath=off in the boot loader configuration file. Make sure that multipath=off has been set in the kernel line of the boot loader configuration file.
vga=0x31a \ resume=/dev/VG/swap splash=silent showopts multipath=off initrd /initrd-2.6.16.60-0.54.5-smp multipath=off is set in the underlined section. 3. Check the definition in the /etc/fstab file. Check whether LABEL is used in the /etc/fstab file. If the file contains LABEL=xxxxx, LABEL is being used.
initrd=/boot/initrd-2.6.18-194.el5 read-only append="root=LABEL=/" LABEL is set in the underlined section. For Red Hat Enterprise Linux 6, also check whether the block device names (udev names) starting with UUID= are specified as shown in the following underlined part below: : : title Red Hat Enterprise Linux (2.6.32-71.el6.i686) root (hd0,0) kernel /vmlinuz-2.6.32-71.el6.i686 ro root=UUID=55574d05-07dc-4c94-a585-5599c284d79b rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=ja_JP.
Check the underlined section. 6. If Red Hat Enterprise Linux, or SUSE LINUX Enterprise Server is being used, check the SCSI device name in the /proc/swaps file. The SCSI device name is displayed in the Filename column. 7. If the block device name or the udev name was specified in steps 3 and 4, execute the following commands to check the SCSI device: ¢ For Red Hat Enterprise Linux 6 Execute the udevadm command. Specify the block device name for -n.
11. Copy the startup configuration that has the LABEL specification, which is contained in the boot loader configuration file. The following shows an example configuration. Note that option in the example represents an option that can be specified to suit the user environment. ¢ When GRUB is used as the boot loader with Xen kernels: For details on Xen kernels, see Table 3-61 Xen Hypervisor Operating Environments Supported by HDLM on page 3-88. : : title XEN root (hd0,1) kernel /boot/xen.
title sd-Red Hat Enterprise Linux (2.6.18-194.el5) ¢ When LILO or ELILO is used as the boot loader: Change the underlined text as follows: Before: label=linux After: label=linux-sd 13. Change the specification for root contained in the boot loader configuration file from LABEL to the SCSI device, based on the LABEL and SCSI device correspondence checked in step 5. Change the specification for root contained in the configuration that you copied in step 11.
HDevName Management Device Host Channel Target /dev/sddlmaa configured /dev/sda 0 0 0 KAPL10302-I /sbin/dlmcfgmgr completed normally. Lun 0 The HDevName column indicates the HDLM device, and the Device column indicates SCSI device. 19. Create an initial RAM disk image file for HDLM. From the following, perform the procedure that corresponds to the host OS. For the initial RAM disk image file specified in the parameter, assign a name that is different from all currently used names.
#LABEL=/tmp #/dev/sda4 /dev/sddlmaa4 /tmp /tmp /tmp ext2 ext2 ext2 : : defaults defaults defaults 1 2 1 2 1 2 22. Back up the boot loader configuration file. 23. Copy the configuration contained in the boot loader configuration file, which was used for startup from the SCSI device in step 14. 24. Change the name of the configuration contained in the boot loader configuration file. Change the name of the configuration copied in step 23. Choose a name that indicates use for an HDLM device specification.
# blkid /dev/sda2 /dev/sda2: UUID="19597725-5d20-4d1d-9906-f9f891b7711a" TYPE="ext4" # c. Change the root specification in the configuration that you copied in step 23 to the UUID checked above. root=UUID=19597725-5d20-4d1d-9906-f9f891b7711a ¢ For OSs other than the above: Delete the root specification in the configuration that you copied in step 23. If you are using a Xen kernel, delete the root device specification in module.
# shutdown -h now 31. Change the configuration from a single-path configuration to a multi-path configuration. 32. Start the host. 33. Execute the mount command to check that the HDLM device is mounted.
To perform an upgrade installation of HDLM in a multi-path boot disk environment that uses an HDLM device, and set up the environment: 1. Log in to Linux as a user with root permissions. 2. Make sure that the HDLM device is specified in the definition in the /etc/ fstab file.
#/dev/sddlmaa4 /dev/sda4 5. /tmp /tmp ext2 ext2 : : defaults defaults 1 2 1 2 Copy the configuration contained in the boot loader configuration file, which was used for startup from the HDLM device. The following shows an example configuration. Note that option in the example represents an option that can be specified to suit the user environment.
Before: title Red Hat Enterprise Linux (2.6.18-194.el5) After: title sd-Red Hat Enterprise Linux (2.6.18-194.el5) ¢ 7. When LILO or ELILO is used as the boot loader: Change the underlined text as follows: Before: label=HDLM_194.EL After: label=sd-HDLM_194.EL Specify the SCSI device you checked in step 3 for root in the boot loader configuration file. Change the specification for root contained in the configuration that you copied in step 5.
default=2 ¢ When LILO or ELILO is used as the boot loader: Specify label for default. default=sd-HDLM_194.EL 11. If LILO is being used as the boot loader, execute the /sbin/lilo command to have the changes take effect. 12. Shut down the host. Execute the following command to shut down the host: # shutdown -h now 13. Change the configuration from a multi-path configuration to a single-path configuration. 14. Start the host. 15. Execute the mount command to make sure that the SCSI device is mounted.
19. Create an initial RAM disk image file for HDLM. From the following, perform the procedure that corresponds to the host OS. ¢ For Red Hat Enterprise Linux 6: a. Change hdlm_dracut=n defined in the /etc/opt/ DynamicLinkManager/hdlm.conf file to hdlm_dracut=y. b. Execute the dracut command. If the initial RAM disk image file to be created already exists, specify the -f parameter to overwrite the file. The following shows an example of executing the command: # /sbin/dracut /boot/initramfs-hdlm-2.6.
23. Edit the specification for root written in the boot loader configuration file. From the following, perform the procedure that corresponds to the host OS. ¢ For Red Hat Enterprise Linux 6: Specify the UUID of the root device for root by doing the following: a. Execute the mount command to check the name of the device mounted on the root partition (/). The following shows an example of executing the command.
25. In the boot loader configuration file, edit the settings to be used during a boot. ¢ ¢ When GRUB is the boot loader Change the default number so that a boot can be performed using the configuration copied in step 21. default=3 When LILO or ELILO is used as the boot loader: Specify label for default. default=HDLM-HDLM_194.EL 26. If LILO is used as the boot loader, execute the /sbin/lilo command to have the new settings take effect. 27. Edit the /etc/fstab file.
31. Execute the mount command to make sure that the HDLM device is mounted. The following shows an execution example for when GRUB is used as the boot loader: # mount /dev/sddlmaa2 on : : /dev/sddlmaa1 on /dev/sddlmaa4 on /dev/sddlmaa5 on /dev/sddlmaa6 on none on /dev/shm / type ext2 (rw) /boot type ext2 (rw) /tmp type ext2 (rw) /var type ext2 (rw) /usr type ext2 (rw) type tmpfs (rw) Check the underlined section. 32.
root = /dev/disk/by-id/scsi-35001862001472c70-part12 multipath=off is set in the underlined section. ¢ When GRUB is used as the boot loader with Xen kernels: For details on Xen kernels, see Table 3-61 Xen Hypervisor Operating Environments Supported by HDLM on page 3-88. : : title XEN root (hd0,0) kernel /xen-pae.gz module /vmlinuz-2.6.16.60-0.54.
as /boot/efi instead of /boot (in the line where /boot is coded), and the file system type is displayed as vfat instead of ext3.
5. If the block device name or the udev name was specified in steps 3, execute the following commands to check the SCSI device. ¢ For Red Hat Enterprise Linux 6 Execute the udevadm command. Specify the block device name for -n. # udevadm info --query name -n /dev/disk/by-uuid/ 55574d05-07dc-4c94-a585-5599c284d79b sda1 The sda1 value output is the SCSI device name corresponding to 55574d05-07dc-4c94-a585-5599c284d79b. ¢ For SUSE LINUX Enterprise Server Execute the udevinfo command.
Edit the file to disable the LABEL specification and enable the SCSI device specification. 9. Restart the host to make sure that booting from the SCSI device is possible. This completes the removal of the LABEL setting. 10. Install HDLM. To install HDLM, see Performing a New Installation of HDLM on page 3-100 perform steps 2 to 12 to create an HDLM device. You will also need to perform step 13 if you are only restarting the host.
Record the original md_component_detection value, because it is necessary for removal or upgrade installation of HDLM. 13. Create an initial RAM disk image file for HDLM. From the following, perform the procedure that corresponds to the host OS. For the initial RAM disk image file specified in the parameter, assign a name that is different from all currently used names. ¢ For Red Hat Enterprise Linux 6: a. Change hdlm_dracut=n defined in the /etc/opt/ DynamicLinkManager/hdlm.conf file to hdlm_dracut=y.
# /opt/DynamicLinkManager/bin/dlmmkinitrd KAPL12329-I The utility for supporting the boot disk started. KAPL12344-I A compressed initial ramdisk image /boot/ initrd-2.6.16.46-0.14-default.hdlm was created. KAPL12330-I The utility for supporting the boot disk completed. 14. Back up the /etc/fstab file. 15. Edit the /etc/fstab file. Change the /boot mount point that you changed in step 8 from the SCSI device to the HDLM device.
Figure 3-12 Example of Editing /etc/grub.conf file Edit the shaded portion. Figure 3-13 Example of Editing /boot/grub/menu.lst file (When using a kernel that supports Xen) Edit the shaded portion.
Figure 3-14 Example of Editing /etc/elilo.conf file Edit the shaded portion. 17. If necessary, back up the file. 18. Copy the configuration that was used for startup from the SCSI device. 19. Assign a name to the copied configuration that indicates that the configuration is used for specifying the HDLM device. ¢ ¢ If you will use GRUB as the boot loader Change title. If you will use ELILO as the boot loader Change label. 20. Edit the specification for root written in the boot loader configuration file.
root=/dev/mapper/systemvg-rootlv To specify a UUID for root: a. Execute the mount command to check the root device name. Below is an example of executing the command. The underlined part is the root device name. # mount /dev/mapper/systemvg-rootlv on / type ext4 (rw) proc on /proc type proc (rw) : : b. Execute the blkid command to check the UUID of the root device name that you checked above. Below is an example of executing the command. The underlined part is the UUID.
Execute the following command to shut down the host: # shutdown -h now 24. Change the configuration from a single-path configuration to a multi-path configuration. 25. Start the host. 26. Update the information about the volume group. Execute the following command to update the information about the volume group. # vgscan Reading all physical volumes. This may take a while... Found volume group "VolGroup00" using metadata type lvm2 27. Check the relationship between the volume group and HDLM devices.
Upgrade Installation in an Environment Where a Logical Volume (LVM2) on an HDLM Device Is Used as a Boot Disk This subsection describes how to perform an upgrade installation of HDLM in a multi-path boot disk environment that uses a logical volume (LVM2) on an HDLM device. Note that if settings are incorrect, the OS might not start. In this subsection, the procedure assumes that you are using GRUB or ELILO as the default boot loader in Red Hat Enterprise Linux, or SUSE LINUX Enterprise Server.
2. Make sure that the HDLM device is defined in the /etc/fstab file. : : /boot : : /dev/sddlmaa1 ext3 defaults 1 2 This example assumes that IA32 uses GRUB as the boot loader. When you use IPF that uses ELILO as the boot loader, the mount point is displayed as /boot/efi instead of /boot in the line where /boot is coded, and the file system type is displayed as vfat instead of ext3. 3.
7. 3-168 Edit the /etc/lvm/lvm.conf file so that the LVM2 recognizes the SCSI device, not the HDLM device. The following shows an example of editing the /etc/lvm/lvm.conf file.
Figure 3-15 Example of Editing /etc/lvm/lvm.conf file Comment out the existing filter and types lines, and add the shaded lines in the figure. In addition, set md_component_detection to its original value before installation. 8. Edit the boot loader configuration file so that the OS will start with a SCSI device specified. Edit the boot loader configuration file as shown in Figure 3-16 Example of Editing /etc/grub.conf file on page 3-169, Figure 3-17 Example of Editing /boot/grub/menu.
Edit the shaded portion. Figure 3-17 Example of Editing /boot/grub/menu.lst file (When using a kernel that supports Xen) Edit the shaded portion. Figure 3-18 Example of Editing /etc/elilo.conf file Edit the shaded portion. 9. Copy the configuration that was used for startup from the HDLM device. 10. Assign a name to the copied configuration. You can assign any name that indicates that the configuration is used for specifying the SCSI device.
11. Specify root as the name of the device mounted to / in the /etc/fstab file. If you are using a kernel that supports Xen, add the root device by using the definition conventions for the boot loader configuration file. 12. For Red Hat Enterprise Linux 6, check hdlm_dracut defined in the /etc/ opt/DynamicLinkManager/hdlm.conf file. If hdlm_dracut=y is written, change it to hdlm_dracut=n. If hdlm_dracut=y is not written, go to step 13. 13.
Reading all physical volumes. This may take a while... Found volume group "VolGroup00" using metadata type lvm2 20. Check the relationship between the volume group and HDLM devices. Execute the following command to make sure that the physical volumes that make up the volume group are not HDLM devices. 21. Perform an upgrade installation of HDLM. To perform an upgrade installation of HDLM, see Performing an Upgrade Installation of HDLM on page 3-112, perform steps 2 to 12 to create an HDLM device.
# dlmcfgmgr -v HDevName Management Device Host Channel Target /dev/sddlmaa configured /dev/sda 0 0 0 KAPL10302-I /sbin/dlmcfgmgr completed normally. Lun 0 The HDevName column indicates the HDLM device, and the Device column indicates the SCSI device. 23. Edit the /etc/lvm/lvm.conf file so that the LVM2 recognizes the HDLM device, not the SCSI device. The following shows examples of editing the /etc/lvm/lvm.conf file. Figure 3-19 Example of Editing /etc/lvm/lvm.
¢ For OSs other than the above: Execute the utility for supporting a boot disk (dlmmkinitrd). If the initial RAM disk image file to be created already exists and you are using Red Hat Enterprise Linux AS4/ES4 or Red Hat Enterprise Linux 5, specify the -f parameter to overwrite this file. If you are using SUSE LINUX Enterprise Server, this file is overwritten even if you do not specify the parameter. For details on the dlmmkinitrd utility, see dlmmkinitrd Utility for Supporting a Boot Disk on page 7-33.
¢ ¢ Execution example of the command when GRUB as the boot loader is used # rm /boot/initrd-hdlm-2.6.9-11.EL.gz Execution example of the command when IPF (with ELILO as the boot loader) is used # rm /boot/efi/efi/redhat/initrd-hdlm-2.6.9-11.EL.gz 26. Edit the /etc/fstab file. Change the /boot mount point that you changed in step 4 from the SCSI device to the HDLM device.
Figure 3-20 Example of Editing /etc/grub.conf file Edit the shaded portion. Figure 3-21 Example of Editing /boot/grub/menu.lst file (When using a kernel that supports Xen) Edit the shaded portion.
Figure 3-22 Example of Editing /etc/elilo.conf file Edit the shaded portion. 28. Copy the configuration that was used for startup from the HDLM device. 29. Assign a name to the copied configuration that indicates that the configuration is used for specifying the HDLM device after update. ¢ ¢ If you will use GRUB as the boot loader Change title. If you will use ELILO as the boot loader Change label. 30. Edit the specification for root written in the boot loader configuration file.
proc on /proc type proc (rw) : : b. Change the root specification contained in the configuration that you copied in step 28 to the root device name checked above. root=/dev/mapper/systemvg-rootlv To specify a UUID for root: a. Execute the mount command to check the root device name. Below is an example of executing the command. The underlined part is the root device name. # mount /dev/mapper/systemvg-rootlv on / type ext4 (rw) proc on /proc type proc (rw) : : Check the underlined device name. b.
Specify the position of the valid title for default. ¢ When ELILO is the boot loader Specify label for default. 33. Shut down the host. Execute the following command to shut down the host: # shutdown -h now 34. Change the configuration from a single-path configuration to a multi-path configuration. 35. Start the host. 36. Execute the mount command to make sure that the HDLM device is mounted on /boot.
Countermeasures for Unsuccessful Startup of the OS from an HDLM Device This subsection explains what actions you should take if the OS cannot be started from an HDLM device. If startup of the OS fails, either of the following happens: • An error message appears and the OS stops. • A prompt for a password for starting maintenance appears, and the OS stops. The following explains the action to be taken for each case.
When an Error Message Appears and the OS Stops The probable causes of this error are as follows: Cause 1 The initial RAM disk image file was specified incorrectly in the boot loader configuration. Cause 2 The initial RAM disk image file is corrupted. Cause 3 The startup disk was no longer recognized first because the system environment configuration was modified.
To correct the above error: 1. Enter the root user password. 2. Execute mount -o remount rw / to mount the root directory again. 3. In the /etc/fstab file, change the mount destination of root to the SCSI device. 4. Restart the host to start the OS from the SCSI device. 5.
• When using LUKS on an HDLM device, enter the HDLM device's device file name in the /etc/crypttab file's second field. Using HDLM in an LUKS Environment This subsection describes how to migrate LUKS from a SCSI device environment using LUKS to HDLM devices. To migrate from /dev/sdh to /dev/sddlmaa: 1. Check the HDLM device to be migrated from the SCSI device.
¢ If you have got a SCSI device name as the output, check the output of step 1 to confirm the HDLM device name corresponding to the SCSI device name, and change the UUID to the HDLM device name in the / etc/crypttab file's second field. The following shows an example of changing the setting in the /etc/ crypttab file's second field. Before: luks-volume1 UUID="050f9901-3ab8-4556-a091-9c6e4a404f09" /etc/ cryptpassword1 After: luks-volume1 /dev/sddlmaa /etc/cryptpassword1 4.
• If an md device has been applied to a directory that cannot be unmounted while the system is operating (such as /opt, /tmp, or /var), HDLM cannot be applied to that md device. • You cannot use the disk partition type RAID (fd). • In mdadm package versions 1.6.0-2 or earlier, you cannot manage devices whose major or minor number is 256 or greater. Use mdadm package versions 1.6.0-3 or later. • You cannot simultaneously specify SCSI devices and HDLM devices to configure an md device.
Creating an md Device This subsection explains the procedure for creating a new md device in a multi-path environment in which HDLM has been installed. During this procedure, /dev/md0 is created on /dev/sddlmaa1 and /dev/ sddlmab1. Use the following procedure to configure the environment shown in Figure 3-25 Device Configuration When Creating an md Device on an HDLM Device on page 3-186. Figure 3-25 Device Configuration When Creating an md Device on an HDLM Device To create an md device: 1.
Disk /dev/sddlmaa: 5368 MB, 5368709120 bytes 166 heads, 62 sectors/track, 1018 cylinders Units = cylinders of 10292 * 512 = 5269504 bytes Device Boot Start /dev/sddlmaa1 1 End 1018 Blocks 5238597 Id System 83 Linux Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. Syncing disks. Also perform the above operation for /dev/sddlmab. 2. Create an md device.
UUID=e39a6b15:32e48a5d:ca05f4db:25bc8af9 For details about the contents of the configuration file, see the Linux documentation or use the man command. 6. Edit the configuration file created in step 5. Edit the /etc/mdadm.conf file to add auto=yes to the ARRAY line: DEVICE /dev/sddlmaa1 /dev/sddlmab1 ARRAY /dev/md0 level=raid1 num-devices=2 UUID=e39a6b15:32e48a5d:ca05f4db:25bc8af9 auto=yes 7. Restart the host. 8. Make sure that the md device has been activated.
Figure 3-26 Device Configuration Where an md Device on a SCSI Device Is Migrated to an HDLM Device (An Environment that Uses the md Device's RAID Functionality) To migrate /dev/md0: 1. Stop all applications that are using the existing md device. 2. If necessary, back up the application data residing on the md device. 3. If file systems have been mounted on the md device, unmount them. 4. Check the status of the md device.
# mdadm --detail --scan | grep -w "/dev/md0" >> /etc/mdadm.conf For sdh1 and sdi1, specify the SCSI devices displayed in step 4. The following example shows the contents of the created configuration file: The underlined part indicates the lines added in this step. # cat /etc/mdadm.
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=e39a6b15:32e48a5d:ca05f4db:25bc8af9 auto=yes 10. Install HDLM. Perform steps 2 to 11 in Performing a New Installation of HDLM on page 3-100. 11. Check the correspondence between the HDLM devices and SCSI devices.
Disk /dev/sddlmaa: 5368 MB, 5368709120 bytes 166 heads, 62 sectors/track, 1018 cylinders Units = cylinders of 10292 * 512 = 5269504 bytes Device Boot Start End Blocks Id System /dev/sddlmaa1 1 1018 5238597 fd Linux raid autodetect Command (m for help): t Selected partition 1 Hex code (type L to list codes): 83 Changed system type of partition 1 to 83 (Linux) Command (m for help): p Disk /dev/sddlmaa: 5368 MB, 5368709120 bytes 166 heads, 62 sectors/track, 1018 cylinders Units = cylinders of 10292 * 512 = 526
how to migrate an md device for which the MULTIPATH function is used to an md device for which the LINEAR function is used. Note: Red Hat Enterprise Linux 6 cannot migrate an md device for which the MULTIPATH function is used to an md device for which the LINEAR function is used. In this procedure, the device /dev/md0 on /dev/sdo1 and /dev/sdh1 is migrated to the device /dev/md0 on /dev/sddlmaa1.
5. Specify the settings required for the md device, and then install HDLM. Perform steps 5 to 12 in When the MULTIPATH Function Is Not Being Used for md Devices on page 3-188. 6. Check the correspondence with HDLM device. Execute the HDLM-configuration definition utility dlmcfgmgr with the -v parameter specified: # dlmcfgmgr -v HDevName Management Device Host Channel Target Lun /dev/sddlmaa configured /dev/sdh 1 0 0 0 /dev/sdo 2 0 0 1 KAPL10302-I /sbin/dlmcfgmgr completed normally.
Delete the ARRAY line that includes the same name as the md device name (md0) created in step 8. In the following example, the underlined lines are to be deleted. # cat /etc/mdadm.conf DEVICE /dev/sdo1 /dev/sdh1 ARRAY /dev/md0 level=multipath num-devices=2 UUID=6b2ec21b: 06d0f50b:bbf04d32:1e00b09a auto=yes ARRAY /dev/md0 level=linear num-devices=1 UUID=426a9f1c: 9cfa6310:6aa9a80b:11ea2102 10. Edit the /etc/mdadm.
Note that, in step 17 in When the MULTIPATH Function Is Not Being Used for md Devices on page 3-188, [multipath] will be displayed until the host is restarted. However, there are no operational problems.
Figure 3-28 Device configuration When Creating a Logical Volume on an HDLM Device To create a new logical volume on an HDLM device: 1. Stop all processes and services that are using the HDLM device. 2. Create a disk partition on the HDLM device and change the system ID from Linux (83 in hexadecimal representation) to Linux LVM (8e in hexadecimal representation).
Example of executing the parted command (IA32, IPF or EM64T/AMD64): 3-198 Creating an HDLM Environment Hitachi Dynamic Link Manager User Guide for Linux®
When you use the parted command to change the partition, to let the system recognize the partitions on the HDLM device, execute the blockdev command after the parted command. 3. Edit the /etc/lvm/lvm.conf file. Edit the device section in the file as shown below to disable the SCSI device configuration and enable the HDLM device configuration: ¢ Adding and deleting filter entry information Add the following line and comment out all other filter entry information: filter = [ "a|sddlm[a-p][a-p].
Figure 3-29 Example of Editing the /etc/lvm/lvm.conf File 4. Create the physical volumes. The following example shows how to define /dev/sddlmad1 and /dev/ sddlmad2 as physical volumes: # pvcreate Physical # pvcreate Physical 5. /dev/sddlmad1 volume "/dev/sddlmad1" successfully created /dev/sddlmad2 volume "/dev/sddlmad2" successfully created Create a volume group.
6. Create the logical volume. In the following example, the command creates the logical volume (lvol1: 100 MB) by using the vg01 volume group: # lvcreate -L 100M -n lvol1 vg01 Logical volume "lvol1" created 7. Create a file system. The following example shows how to use the mke2fs command to create a file system on the lvol1 logical volume: # mke2fs /dev/vg01/lvol1 Filesystem label= OS type: Linux Block size=1024 (log=0) Fragment size=1024 (log=0) 25688 inodes, 102400 blocks 5120 blocks (5.
When Moving a Logical Volume Created on a SCSI Device in a SinglePath Environment to an HDLM Device This subsection explains the procedure for moving a logical volume created on a SCSI device in a single-path environment to an HDLM device in a multipath environment. Use the following procedure to configure the environment in Figure 3-30 Device Configuration When a Logical Volume on a SCSI Device Is Moved to an HDLM Device on page 3-202.
HDevName Management Device Host Channel /dev/sddlmaa configured /dev/sda 2 0 /dev/sddlmab configured /dev/sdb 2 0 KAPL10302-I /sbin/dlmcfgmgr completed normally. Target 0 0 Lun 0 1 3. Stop all processes and services that are using the SCSI and HDLM devices. 4. Unmount the logical volume to be moved. In the following example, the logical volume subject to the move has been mounted on /mnt/lvol1: # umount /mnt/lvol1 5. Deactivate the volume group.
Figure 3-31 Example of Editing the /etc/lvm/lvm.conf File 8. Execute the VG scan. To re-create the volume group on the HDLM device, execute the vgscan command as shown in the following example: # vgscan Reading all physical volumes. This may take a while... Found exported volume group "vg01" using metadata type lvm2 9. Import the volume group. In the following example, the command imports the vg01 volume group: # vgimport vg01 Volume group "vg01" successfully imported 10.
Execute the following command to make sure that the information about the physical volume for the target logical volume has been changed to the information about the HDLM device: # pvscan PV /dev/sddlmad1 VG vg01 lvm2 [468.00 MB / 368.00 MB free] PV /dev/sddlmad2 VG vg01 lvm2 [548.00 MB / 548.00 MB free] Total: 2 [1016.00 MB] / in use: 2 [1016.00 MB] / in no VG: 0 [0 ] 11. Activate the volume group.
# HDLM devices are listed in the HDevName column, and SCSI devices are listed in the Device column. 2. Check whether the SCSI devices can be migrated to the HDLM devices. Execute the command shown below.
Settings for KVM If you install HDLM in an environment in which KVM is used, you need to register HDLM devices into the hardware configuration file (/etc/libvirt/ qemu/domain-name.xml). For details on the hardware configuration file, see the OS documentation. To register HDLM devices by using the virsh command: 1. Execute the following command to check the domain name and operating status of the guest OS.
# virsh define /etc/libvirt/qemu/domK.xml 6. Start the guest OS. For details on how to start the guest OS, see the OS documentation. Settings for Heartbeat This section describes the procedure that the user must perform when HDLM is installed in an environment in which Heartbeat is used for SUSE LINUX Enterprise Server. To set up Heartbeat: 1. Stop the Heartbeat service in the cluster. If the Heartbeat service is running, stop it by executing the following command: # etc/init.d/heartbeat stop 2.
(number-of-paths-connected-to-Oracle-Cluster-file-System-2 x 60 seconds / 2) + 1 ¢ • If the Thunder 9500V series, Hitachi AMS2000/AMS/WMS/SMS series or HUS100 series is being used: (number-of-paths-connected-to-Oracle-Cluster-file-System-2 x 30 seconds / 2) + 1 When a host and an Oracle RAC voting disk are connected by multiple paths, HDLM performs failover processing for those paths (in the same way as for normal paths) when an I/O timeout occurs for one of the paths.
Table 3-70 Formula for Calculating DISKTIMEOUT Storage system type Number of paths connected to the voting disk Formula for obtaining the value of DISKTIMEOUT • Lightning 9900 series 3 or less You do not need to change the value of DISKTIMEOUT.
• For ASMLib 2.1.0 or later: # /usr/sbin/oracleasm configure • For ASMLib versions earlier than 2.1.0: # /etc/init.d/oracleasm configure b. Open the ASMLib configuration file (/etc/sysconfig/oracleasm). c. Change the ORACLEASM_SCANORDER line as follows: ORACLEASM_SCANORDER ="sddlm" If an ASM disk defined in an HDLM device already exists, perform this procedure, and then restart all the nodes. This step must be done to enable the settings.
# service ccsd stop 2. Change the SCSI device being used by RHCM to an HDLM device. Edit as shown below if the lower SCSI device (/dev/sda) of the HDLM device (/dev/sddlmaa) is being used as /dev/raw/raw1. # vi /etc/sysconfig/rawdevices # /dev/raw/raw1 /dev/sda /dev/raw/raw1 /dev/sddlmaa Comment out /dev/sda and add /dev/sddlmaa. 3. Restart the rawdevices service to apply the changes made in Step 2. Execute the following command to restart the service: # service rawdevices restart 4.
# shutdown -r now RHCM setup is complete. 5. Execute the following command to apply the changes made in step 2. # /sbin/start_udev 6. Start the cluster service of RHCM. Executing the following command to start the service: # service cman start # service rgmanager start Settings for VCS The following is the procedure that must be executed by the user when HDLM is installed in an environment that uses VCS. For details on how to operate the VCS GUI, see the VCS documentation. 1.
¢ ¢ Make sure that all the paths are online. Make sure that PathStatus is Online. If a path is not online, Reduced will be displayed. Make sure that for each path the combination of the CHA port (ChaPort), through which multiple paths are accessing the same LU, and the HBA port (the host port number and bus number displayed in the PathName column) is different. The digits displayed on the left of PathName indicate a host port number.
# To check the current audit log settings, execute the following command: # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -audlog Audit Log : off Audit Log Category : Audit Log Facility : KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss # Setting Up the HDLM Functions The table below summarizes the functions that can be set in HDLM. For details about each function, see Setting Up Load Balancing on page 3-216 and subsequent sections.
Function Default value Recommended value Number of files for the Error logs 2 2 File size for trace information 1000 (KB) 1000 (KB) Number of files for trace 4 information 4 Collection of audit log data The recommended value depends on the operating environment. off Set on, if you want to collect audit log data. Audit log facility user local0 to local7 # This function is applied only when Hitachi AMS2000 series, Hitachi SMS series, HUS100 series storage is used.
# /opt/DynamicLinkManager/bin/dlnkmgr set -pchk on -intvl 10 To enable path health checking, specify on. Specify off otherwise. When you specify on, you can use the -intvl parameter to specify the checking interval. The value that was specified previously will be applied if the checking interval is not specified. For example, specify the path health check as off after specifying the checking interval as 15 minutes and executing.
When intermittent error monitoring is enabled, you can specify intermittent error conditions. The default value for the intermittent error-monitoring interval is 30. The default value for the number of error occurrences is 3. The system assumes that an intermittent error has occurred if the specified number of times that the error needs to occur is reached during the specified monitoring interval (minutes).
the checking interval (in minutes) for reviewing the information about the switching of controllers performed by the storage system. Setting the Error Log Collection Level The error log (the HDLM manager log (dlmmgrn.log (n indicates a file number from 1 to 16)) collection level can be set. The following table lists and describes the values for the error log collection level setting. Table 3-72 Values for the Error Log Collection Level Setting Value Description 0 No error logs are collected.
Value Description 2 Program operation summaries are output. 3 Program operation details are output. 4 All information is output. If an error occurs, you might have to set the trace level to 1 or higher to collect any trace information. The higher this value is set, the more information that will be output. As the amount of trace information to be output increases, it will take less time to overwrite the old trace information with the new information.
By specifying both the log file size and the number of log files, you can collect up to 32000000KB (approximately 30GB) of error logs. The following is an example of using a command to set the number of error log files. # /opt/DynamicLinkManager/bin/dlnkmgr set -elfn 5 Specify the number of error log files by a number. Setting the Trace File Size Trace files for which a trace file size can be set are hdlmtrn.log (n indicates a file number from 1 to 64).
Setting Up Audit Log Data Collection If you want to collect audit log data, you must also specify the collection level for audit log data and the audit log categories. The table below lists and describes the values for the audit log collection level setting. An audit log data collection level is a severity level. The default is 6. Table 3-74 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.
Setting the Audit Log Facility The following describes how to specify the output destination for audit log data. If you want to specify the output destination for audit log data, first specify the audit log facility by using the dlnkmgr set -audfac command. Next, define the output destination of the facility in the /etc/syslog.conf file. The table below lists the values for the audit log facility setting. The default is user.
Path Health Checking : on(10) Auto Failback : on(10) Reservation Status : Intermittent Error Monitor : on(2/20) Dynamic I/O Path Control : off(10) KAPL01001-I The HDLM command completed normally.
• HDLM creates only a block-type device under /dev. • If the OS is Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 6, use an udev rule file to create the character-type device file. If the OS is Red Hat Enterprise Linux AS4/ES4 or SUSE LINUX Enterprise Server, use the raw command to create the character-type device file. The following shows the difference between these two methods: ¢ ¢ The character-type device file created by using the raw command is deleted when the host is restarted.
Creating File Systems for HDLM (When Volume Management Software Is Not Used) This section describes how to build a file system in an HDLM-managed device without using volume management software. Mounting a File System To mount an HDLM-managed device as a file system by specifying the logical device file name for an HDLM device: 1. Create a file system by using an HDLM device. If the file system already exists, skip to step 2.
Figure 3-33 Example of Creating an ext2 File System Settings for Automatic Mounting If you specify the name of a logical device file of an HDLM device at host startup, an HDLM-managed device is automatically mounted in the same way as if you had specified the name of a logical device file of a SCSI device. To mount an HDLM-managed device automatically, you need to edit the /etc/ fstab file. In this file, you can specify the name of the logical device file of the SCSI device and the mount point of its disk.
Figure 3-34 Example of Executing the dlnkmgr Command's View Operation (With -drv Specified) In the example, the name of the logical device file of the HDLM device that corresponds to /dev/sda can be identified as sddlmaa. 2. Add the name of the logical device file of the HDLM device that was confirmed in step 1 to the /etc/fstab file.
Migrating from an Environment Where a SCSI Device Is Already Set To move an already set SCSI device to an HDLM device: 1. Identify the name of the logical device file of the HDLM device to be mounted automatically. Execute the dlnkmgr command's view operation, and identify the applicable name of the logical device file of the HDLM and SCSI devices. For details on the view operation, see view (Displays Information) on page 6-30. The following is an actual example.
# /dev/sda /dev/sddlmaa /mnt/sda /mnt/sda ext2 ext2 nofail nofail 0 0 0 0 This example comments out the line for /dev/sda (logical device file name of the SCSI device) and adds a line for /dev/sddlmaa (logical device file name of the HDLM device). For IP-SAN environments, add the line if neither _netdev nor nofail is specified for the mount option. 3. Restart the host or manually mount the HDLM device. The HDLM-managed device is mounted using the logical device file name of the HDLM device.
This step enables you to keep the correspondence between LUs and the logical device file names for SCSI devices once removal is complete. 3. Cancel HDLM device registration in an application. An application uses an HDLM device when accessing an LU, so after HDLM is removed, the application cannot use the same HDLM device to access that LU. If an HDLM-managed device is registered in an application (including cluster software, but excluding volume management software), cancel registration of the HDLM device.
For details on how to cancel the LUKS settings, see Canceling the LUKS Settings on page 3-248. Canceling the Heartbeat Settings If Heartbeat is being used with SUSE LINUX Enterprise Server, the HDLM device settings must be cancelled from Heartbeat. The following is the procedure for migrating an environment in which HDLM devices have already been used for Heartbeat to an environment that uses character-type SCSI devices. 1. Stop the Heartbeat service in the cluster.
Canceling the Settings for RHCM This section describes how to cancel the HDLM device settings in RHCM in an environment where RHCM is used. If the environment is one where an HDLM device is already being used in RHCM, the following procedure must be executed in order to change to an environment that uses a character-type device of a SCSI device. Note: For Oracle Unbreakable Enterprise Kernel 5, RHCM environments are not supported.
If the RHCM service is running, stop the service by executing the following command: # service rgmanager stop # service cman stop 2. Replace the HDLM device used by RHCM with a SCSI device. Edit as shown below to use the SCSI device /dev/sda, which is the lower SCSI device of the HDLM device/dev/sddlmaa, as /dev/raw/raw1. # ACTION=="add", KERNEL=="sddlmaa", RUN+="/bin/raw /dev/raw/raw1 %N" ACTION=="add", KERNEL=="sda", RUN+="/bin/raw /dev/raw/raw1 %N" Comment out KERNEL=="sddlmaa" and add KERNEL=="sda".
Canceling the Xen Settings This subsection describes how to cancel the HDLM device settings in an environment in which Xen is being used. The following is the procedure for migrating a domainU environment that uses the HDLM device /dev/sddlmaa in a multi-path configuration to an environment that uses the SCSI device /dev/sda in a single-path configuration. 1. Check the correspondence between the HDLM and SCSI devices. Execute the HDLM configuration definition utility (dlmcfgmgr) with the -v parameter.
4. Change the multi-path configuration to a single-path configuration. 5. Specify the settings so that HDLM devices are not used in domainU. Disable the block device settings from domainU. For details, see the Linux documentation. 6. Specify the settings so that the SCSI devices are used in domainU. Set (export) the block devices to domainU. For details, see the Linux documentation.
After: For details on which HDLM device correspond to which SCSI device, see Displaying Corresponding Information About an HDLM Device, SCSI Device, and LDEV on page 4-17. 5. Execute the following command to enable the settings in the hardware configuration file. # virsh define /etc/libvirt/qemu/domK.xml 6. Start the guest OS. For details on how to start the guest OS, see the OS documentation.
Figure 3-37 Device Configuration When a Logical Volume on an HDLM Device Is Moved to a SCSI Device In Figure 3-37 Device Configuration When a Logical Volume on an HDLM Device Is Moved to a SCSI Device on page 3-238, sda1, sdb1, sdc1, and sdd1 indicate the same LU. Likewise, sda2, sdb2, sdc2, and sdd2 indicate the same LU. sddlmaa1 and sddlmaa2 indicate the HDLM devices corresponding to each LU. To move the logical volume to a SCSI device: 1.
In the following example, the command exports information about the vg01 volume group: # vgexport vg01 Volume group "vg01" successfully exported 5. If the LVM environment uses an HDLM device in a multi-path configuration, configure the path to an existing LU as a single path. Change the path to an existing LU as a single-path configuration by performing the procedure described in Deleting a Path to an Existing LU on page 4-42 in Changing the HDLM Device Configuration on page 4-36.
Figure 3-38 Example of Editing the /etc/lvm/lvm.conf File 7. Execute the vgscan command. To re-create the volume group on the HDLM device, execute the vgscan command as shown in the following example: # vgscan Reading all physical volumes. This may take a while... Found exported volume group "vg01" using metadata type lvm2 8. Import the volume group.
9. Execute the pvscan command to check that the environment has been changed successfully. The following shows an example of executing the pvscan command: # pvscan PV /dev/sda1 VG vg01 lvm2 [468.00 MB / 368.00 MB free] PV /dev/sda2 VG vg01 lvm2 [548.00 MB / 548.00 MB free] Total: 2 [1016.00 MB] / in use: 2 [1016.00 MB] / in no VG: 0 [0 ] 10. Activate the volume group.
to a SCSI Device (An Environment that Uses the md Device's RAID Functionality) on page 3-242, carry out the procedure below. To remove HDLM, carry out the steps before the removal. Figure 3-39 Device Configuration When an md Device on an HDLM Device Is Moved to a SCSI Device (An Environment that Uses the md Device's RAID Functionality) To migrate /dev/md0: 1. Stop the host and change the multi-path configuration to a single-path configuration. 2. Start the host. 3.
unused devices: Make sure that md0 : active is not displayed. 9. Check the correspondence between the HDLM devices and SCSI devices. Execute the HDLM-configuration definition utility dlmcfgmgr with the -v parameter specified: # dlmcfgmgr -v HDevName Management Device Host Channel Target Lun /dev/sddlmaa configured /dev/sdh 1 0 0 0 /dev/sddlmab configured /dev/sdi 1 0 0 1 KAPL10302-I /sbin/dlmcfgmgr completed normally.
Disk /dev/sddlmaa: 5368 MB, 5368709120 bytes 166 heads, 62 sectors/track, 1018 cylinders Units = cylinders of 10292 * 512 = 5269504 bytes Device Boot /dev/sddlmaa1 autodetect Start 1 End 1018 Blocks 5238597 Id fd System Linux raid Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. Syncing disks. Also perform the above operation for /dev/sddlmab. 12.
Figure 3-40 Device Configuration When an md Device on an HDLM Device Is Moved to a SCSI Device (An Environment that Uses the md Device's MULTIPATH Functionality) To migrate /dev/md0: 1. Deactivate the md device. Perform steps 3 to 5 in Migrating to md Devices for which the MULTIPATH Function Is Not Used on page 3-241. 2. Check the status of the md device.
# dlmcfgmgr -v HDevName Management Device Host Channel Target Lun /dev/sddlmaa configured /dev/sdh 1 0 0 0 /dev/sdo 2 0 0 1 KAPL10302-I /sbin/dlmcfgmgr completed normally. The HDevName and Device columns display HDLM devices and SCSI devices, respectively. 6. Create an md device. Based on the correspondence between the HDLM devices and SCSI devices checked in step 5, create an md device. When you specify a device name, you must also specify the partition number that is displayed in step 2.
# cat /etc/mdadm.conf DEVICE /dev/sddlmaa1 ARRAY /dev/md0 level=linear num-devices=1 UUID=426a9f1c: 9cfa6310:6aa9a80b:11ea2102 auto=yes ARRAY /dev/md0 level=multipath num-devices=2 UUID=8db667ff:e7472a25:3a84b801:025a6a57 9. Edit the /etc/mdadm.conf file to add auto=yes to the ARRAY line in the configuration file: DEVICE /dev/sdo1 /dev/sdh1 ARRAY ARRAY /dev/md0 level=multipath num-devices=2 UUID=8db667ff:e7472a25:3a84b801:025a6a57 auto=yes 10.
Note that, in step 13 in Migrating to md Devices for which the MULTIPATH Function Is Not Used on page 3-241, [linear] will be displayed until the host is restarted. However, there are no operational problems. Canceling the LUKS Settings This subsection describes how to migrate LUKS from a HDLM device environment using LUKS to SCSI devices. To migrate from /dev/sddlmaa to /dev/sdh: 1. Change the multi-path configuration to a single-path configuration. 2.
Removing HDLM Note ¢ ¢ If the system initiates path health checking or automatic failback while HDLM is being removed, an error message (KAPL04023) might be output to syslog. However, HDLM operations are not affected. If you remove HDLM, the error logs (/var/tmp/hdlminstlog/ installhdlm[01-10].log) generated during installation of HDLM are not removed. Delete the /var/tmp/hdlminstlog/ installhdlm[01-10].log files as needed. For details on the installhdlm[01-10].
If a value other than 0 is displayed for Used, perform the operation described in Operations on HDLM-Managed Devices on page 3-230, and then perform steps 2 and 3 in Removing HDLM on page 3-249 so that the HDLM devices can no longer be used. 6. Execute the remove command. Execute the following command to remove HDLM: # rpm -e HDLM 7. Make sure that the remove processing has finished. Execute the following command to make sure that the remove processing has finished.
¢ When LILO is used as the boot loader: Root directory (/), /tmp, /usr, /var, swap ¢ When LVM2 is used: /boot The following shows an example of the /etc/fstab file: /dev/sddlmaa2 3. / ext2 : : : : defaults 1 1 Execute the HDLM-configuration definition utility (dlmcfgmgr) with the -v parameter specified to check the correspondence between the HDLM device and the SCSI device. If the SCSI device name has been changed by using the udev function, specify the -udev parameter also.
If LVM2 is used in cases other than above, go to step 5. If LVM2 is not used, go to step 6. 5. When LVM2 is used, edit the /etc/lvm/lvm.conf file so that the LVM2 recognizes the SCSI device, not the HDLM device. The following shows examples of editing the /etc/lvm/lvm.conf file. Figure 3-43 Example of Editing /etc/lvm/lvm.conf file Comment out the existing filter and types lines, and add the shaded lines in the figure. In addition, set md_component_detection to its original value before installation. 6.
linear #default=HDLM_194.EL default=linux image=/boot/vmlinuz-2.6.18-194.el5 label=HDLM_194.EL initrd=/boot/initrd-hdlm-2.6.18-194.el5.gz read-only append="option ramdisk_size=18245 option" image=/boot/vmlinuz-2.6.18-194.el5 label=linux initrd=/boot/initrd-2.6.18-194.el5 read-only append="option" root=/dev/sda2 ¢ When the boot loader is GRUB Example 1 below shows an example of editing the /etc/grub.conf file (the underlined sections). Example 2 below shows an example of editing the /boot/grub/ menu.
kernel /boot/xen.gz module /boot/vmlinuz-2.6.16.60-0.21-xen vga=0x31a splash=silent showopts module /boot/initrd-2.6.16.60-0.21-xen.hdlm title XEN-sd root (hd0,1) kernel /boot/xen.gz module /boot/vmlinuz-2.6.16.60-0.21-xen root=/dev/sda2 vga=0x31a splash=silent showopts module /boot/initrd-2.6.16.60-0.21-xen ¢ When the boot loader is ELILO running on an IPF host An example of editing the /etc/elilo.conf file (the underlined sections) is shown below.
initrd /initrd-2.6.9-11.EL.img 7. Copy the configuration that was used for startup from the HDLM device. 8. Assign a name to the copied configuration. You can assign any name that indicates that the configuration is used for specifying the SCSI device. Change label if the boot loader is LILO, or ELILO running on an IPF host. If LILO is the boot loader, you must then execute /sbin/lilo command to activate the new setting. Change title if you will use GRUB as the boot loader. 9.
¢ When the boot loader is LILO or GRUB The following shows an example of executing the mount command. Figure 3-44 Example of Executing the mount Command When the Boot Loader Is LILO or GRUB ¢ When the boot loader is ELILO running on an IPF host The following shows an example of executing the mount command. Figure 3-45 Example of Executing the mount Command When the Boot Loader Is ELILO Refer to the /proc/swaps file to make sure that the specified SCSI device name is displayed in the Filename column.
18. Delete the initial RAM disk image file that was created with the dlmmkinitrd utility for supporting a boot disk or the dracut command. To do this, execute the following command: ¢ ¢ When an IA32 host is used: # rm /boot/initrd-hdlm-2.6.18-194.el5.gz When an IPF host is used: # rm /boot/efi/efi/redhat/initrd-hdlm-2.6.18-194.el5.gz 19. Stop HDLM that was used in a location other than the root directory.
# /sbin/lsmod Module : : sddlmfdrv Size 254092 Used by 0 If a value other than 0 is displayed for Used, perform the operation described in Operations on HDLM-Managed Devices on page 3-230, and then perform steps 2 and 3 in Removing HDLM on page 3-249 so that the HDLM devices can no longer be used. 21. Remove HDLM. To remove HDLM, execute the following command: # rpm -e HDLM 22. Make sure that the removal has been completed.
If HNTRLib2 is being used by another program: HNTRLib2 will not be removed, and the following message will appear. Because a bundle PP name is registered, I did not do the Uninstall. If HNTRLib2 was not removed, execute the following command to check if any programs are using it.
3-260 Creating an HDLM Environment Hitachi Dynamic Link Manager User Guide for Linux®
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.
Notes on Using HDLM Note the following when using HDLM. Notes Common to OSs The following notes are common to OSs: 4-2 • Do not activate the same volume group concurrently from multiple servers. • When a path error exists, the period of time required to return a response to the application that made an I/O request to HDLM depends on the timeout values specified for the fibre channel switch and HBA.
Figure 4-1 Overview of the Period Required to Respond to an Application's I/O Request As shown in the preceding diagram, when an HDLM device has two paths (SCSI devices), the maximum period of time required to respond to the application's I/O request is n1 + n2 seconds; where n1 indicates the timeout value specified for the path that uses SCSI device A, and n2 indicates the timeout value specified for the path that uses SCSI device B.
• If all the following conditions are satisfied, even a path in the normal status might become Offline(E) or Online(E): ¢ A storage system that has a SATA drive is being used. ¢ There is a heavy I/O load on the storage system. Path health checking is set to ON. If this problem happens, reduce the I/O load, and then return the path status to Online by performing an online operation.
block/sddlma01 For a01 in the above examples, any alphanumeric character can be output. • You cannot execute the partprobe command for HDLM devices because this command does not support HDLM devices. If you want to add a partition to or delete a partition from an HDLM device (LU), first stop all applications that are using the target HDLM device (LU) so that the HDLM device (LU) is not being used#.
For detailed procedures, see Updating Kernel Packages and Applying OS Update Packages on page 4-8. Notes When Using SUSE LINUX Enterprise Server 10 Note the following when your OS is SUSE LINUX Enterprise Server 10: • To update a kernel package or apply an OS update package, remove HDLM first. Perform the update and then install HDLM again. For detailed procedures, see Updating Kernel Packages and Applying OS Update Packages on page 4-8.
Notes When Using SUSE LINUX Enterprise Server 11 Note the following when your OS is SUSE LINUX Enterprise Server 11: • To update a kernel package or apply an OS update package, remove HDLM first. Perform the update and then install HDLM again. For detailed procedures, see Updating Kernel Packages and Applying OS Update Packages on page 4-8. • SCSI devices corresponding to an HDLM device can be removed dynamically even while the HDLM device is in use. Before doing so, perform the following operations: a.
Updating Kernel Packages and Applying OS Update Packages This section explains how to update a kernel package or apply an OS update package on a host on which HDLM is installed. The following table lists the sections you can refer to for procedures that apply to different OSs and installation environments.
Host OS HDLM installation environment See: Server on page 4-10 Logical volume When you are (LVM2) on an HDLM using a logical device volume (LVM2) on the HDLM device as a boot disk on page 4-11 in When using Red Hat Enterprise Linux AS4/ES4, Oracle Enterprise Linux 4, Oracle Enterprise Linux 5, Oracle Unbreakable Enterprise Kernel 5, Oracle Unbreakable Enterprise Kernel 6, or SUSE Linux Enterprise Server on page 4-10 Red Hat Enterprise Linux 5 Red Hat Enterprise Linux 6 Environments where an HDLM device
Host OS HDLM installation environment See: Enterprise Linux 5 or Red Hat Enterprise Linux 6 on page 4-12 When using Red Hat Enterprise Linux AS4/ES4, Oracle Enterprise Linux 4, Oracle Enterprise Linux 5, Oracle Unbreakable Enterprise Kernel 5, Oracle Unbreakable Enterprise Kernel 6, or SUSE Linux Enterprise Server If you are using Red Hat Enterprise Linux AS4/ES4, Oracle Enterprise Linux 4, Oracle Enterprise Linux 5, Oracle Unbreakable Enterprise Kernel 5, Oracle Unbreakable Enterprise Kernel 6, or SUSE
¢ Copy the files acquired from before HDLM was removed (.dlmfdrv.conf and .dlmfdrv.unconf) into the directory /etc/opt/ DynamicLinkManager. Go to step 13 to reboot the host. When you are using the HDLM device as a boot disk To update a kernel package or apply an OS update package when an HDLM device is used as the boot disk: 1. Copy the following files into a directory: ¢ /etc/opt/DynamicLinkManager/.dlmfdrv.conf ¢ /etc/opt/DynamicLinkManager/.dlmfdrv.
3. Update the kernel package or apply the OS update package. 4. Install HDLM. For details on HDLM installation, see Installing HDLM for Managing Boot Disks on page 3-132. When you install HDLM, replace step 10 in Settings for Using a Logical Volume (LVM2) on an HDLM Device as a Boot Disk on page 3-155 with the following: To install HDLM, see Performing a New Installation of HDLM on page 3-100 perform steps 2 to 10, 12, and 13 to create an HDLM device.
3. Update the kernel package or apply the OS update package. 4. Execute the dlmupdatesysinit utility for updating system scripts. For details about this utility, see dlmupdatesysinit Utility for Updating System Scripts on page 7-41. 5. Restart the host. 6. Specify the settings required for using an HDLM device as a boot disk. Perform step 17 to 32 in Upgrade Installation in an Environment Where an HDLM Device Is Used as a Boot Disk on page 3-147.
Viewing Path Information This section explains how to display path information by using an HDLM command. To display path information, execute the dlnkmgr command's view operation with the -path parameter specified. The following example shows how to execute the command: # /opt/DynamicLinkManager/bin/dlnkmgr view -path To display information only for the paths accessing the specified host device, execute the dlnkmgr command's view operation with the -path and -hdev parameters specified.
specify a SCSI device name. For details on how to specify paths, see online (Places Paths Online) on page 6-10. For example, if you want to place all the paths that pass through a specific HBA port online, execute the dlnkmgr command's online operation with the -hba parameter specified. The following is an example of executing the command: # /opt/DynamicLinkManager/bin/dlnkmgr online -hba 0010.0000 KAPL01057-I All the paths which pass the specified HBA will be changed to the Online status.
KAPL01056-I If you are sure that there would be no problem when all the paths which pass the specified HBA are placed in the Offline(C) status, enter y. Otherwise, enter n. [y/n]:y KAPL01061-I 3 path(s) were successfully placed Offline(C); 0 path(s) were not. Operation name = offline # 3. Check to see if the statuses of all the applicable paths have changed.
Displaying Corresponding Information About an HDLM Device, SCSI Device, and LDEV This subsection explains how to display corresponding information about an HDLM device, SCSI device, and LDEV by using an HDLM command. You can display corresponding information about an HDLM device, SCSI device, and LDEV by executing the dlnkmgr command's view operation with the -drv parameter specified. For details on the view operation, see view (Displays Information) on page 6-30.
2. To initialize statistical information for all the paths managed by HDLM, execute the dlnkmgr command's clear operation with the -pdst parameter specified. The following is an example of executing the command: # /opt/DynamicLinkManager/bin/dlnkmgr clear -pdst KAPL01049-I Would you like to execute the operation? Operation name = clear [y/n]:y KAPL01001-I The HDLM command completed normally. Operation name = clear, completion time = yyyy/mm/dd hh:mm:ss # 3.
# /opt/DynamicLinkManager/bin/dlnkmgr view -sys -audlog Audit Log : off Audit Log Category : Audit Log Facility : KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss # For details on the displayed items and their descriptions, see view (Displays Information) on page 6-30. Setting Up the Operating Environment To set up the HDLM operating environment, execute the dlnkmgr command's set operation.
To check whether the settings have been applied, see Viewing the Operating Environment on page 4-18. 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 is an example of executing the command: # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -lic License Type Expiration Permanent KAPL01001-I The HDLM command completed normally.
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 is an example of executing the command: # /opt/DynamicLinkManager/bin/dlnkmgr view -sys HDLM Version : x.x.
Path Health Checking : on(30) Auto Failback : on(1) Reservation Status : Intermittent Error Monitor : off Dynamic I/O Path Control : off(10) HDLM Manager Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.x-xx yyyy/mm/dd hh:mm:ss 1000 HDLM Driver Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss LicenseType Expiration Permanent KAPL01001-I The HDLM command completed normally.
executing /opt/DynamicLinkManager/bin/dlnkmgr view -sys msrv), and then start it. ¢ Even if the HDLM manager is running, Dead might be displayed when you execute /opt/DynamicLinkManager/bin/dlnkmgr view -sys msrv. If this happens, see What To Do for the Program Error on page 5-7. Important When stopping the HDLM manager, even if a message indicating that the HDLM manager has successfully stopped, it takes a few seconds more to stop processes.
# /etc/init.d/DLMManager stop Stopping DLMManager: [ OK ] Lower case characters can be used for the command name (dlmmanager). # /etc/init.d/dlmmanager stop Stopping DLMManager: [ OK ] The stop script that was set up during HDLM installation runs, and stops the HDLM manager. Use one of the following procedures to confirm that the HDLM manager has stopped: Use the dlnkmgr command's view operation: Execute the following command.
Process hbsa_service Description Hitachi Command Suite Common Agent Component# process # You only need to monitor this process when HDLM is linked to Global Link Manager. Reconfiguring the HDLM Operating Environment This section describes tasks required for reconfiguring the HDLM operating environment.
Preparation for replacing HBAs Before you replace HBAs, perform the following procedure to ensure that the acpiphp module has been loaded. To ensure that the acpiphp module has been loaded: 1. Execute the lsmod OS command. # /sbin/lsmod | grep acpiphp acpiphp 58713 0 If the acpiphp module has been loaded, replace the HBAs as described in Procedure for replacing HBAs on page 4-27. If the acpiphp module has not been loaded, continue to step 2. 2. Create the acpiphp.modules file.
Procedure for replacing HBAs Before you can replace HBAs, the paths that pass through the HBAs to be replaced must be blocked. The following procedure is used for replacing HBAs. To replace HBAs: 1. Check the WWN information of the HBAs to be replaced. Execute the following command: # /opt/hitachi/drivers/hba/hfcmgr -g Time:yyyy/mm/dd hh:mm:ss ... ...
In PathName, the leftmost number is the host port number. The number between the period to the right of the host port number and the next period is the bus number. Specify the host port number and the bus number when you place the path in the Offline(C) status in step 3. In this execution example, the host port number and the bus number corresponding to the port WWN information of the HBAs to be replaced (the underlined section) are shaded. 3.
In the above figure, new paths that have been added are indicated by shading. Although the information about the old paths (underlined information) that were placed in Offline(C) status before the HBAs were replaced remains, this information will be deleted in step 8. 7. Execute the dlmcfgmgr utility (dlmcfgmgr -v) to confirm that new SCSI devices have been added. New SCSI devices that have been added are indicated by shading in the above figure.
The following shows an example of the command you execute if the HDevName value is /dev/sddlmaa: # dlmcfgmgr -u /dev/sddlmaa 9. Execute the view operation of the dlnkmgr command (dlnkmgr view path -hbaportwwn) to confirm that all the old information for the paths that were placed in Offline(C) status has been deleted. # /opt/DynamicLinkManager/bin/dlnkmgr view -path -hbaportwwn 10. Execute the dlmcfgmgr utility (dlmcfgmgr -v) to confirm that all the old SCSI device information has been deleted.
The paths existing when the HBAs were replaced remain in Offline(E) status. 2. Execute the dlmcfgmgr utility (dlmcfgmgr -v) to check the HDLM device status. Because the paths existing when HBAs were replaced are in Offline(E) status, a hyphen (-) is displayed for Device. 3. Execute the dlmcfgmgr utility (dlmcfgmgr -u) to delete the old information about paths and SCSI devices. In the -u parameter, specify an HDevName device for which a hyphen (-) is displayed for Device in step 2.
Figure 4-2 System Configuration for Replacing a Fiber Cable (Explained in the Following Steps) To replace a fiber cable: 1. Place in Offline (C) status the path that goes through the fiber cable to be replaced (path that goes through the HBA to which the fiber cable is connected). For example, to place in Offline (C) status the path that goes through the HBA with host port number 0001 and bus number 0000, execute the following command: # /opt/DynamicLinkManager/bin/dlnkmgr offline -hba 0001.
Figure 4-3 When the Status of the Path That Goes Through the Fiber Cable to Be Replaced Is Offline(C) 2. Replace the fiber cable for the path that has been placed in Offline(C) status. In this example, replace the fiber cable connected to the HBA with host port number 0001. 3. Place in Online status the path that goes through the replaced fiber cable (that is, the path that goes through the HBA connected to the fiber cable).
Replacing the Fibre Channel Switch If there are multiple online paths for a device in an LU, you can replace a desired Fibre Channel switch while running your applications by placing offline only the path that goes through the Fibre Channel switch to be replaced, and using other paths to continue accesses. The following steps show an example procedure for replacing a Fibre Channel switch. Note that this procedure only applies for replacing a Fibre Channel switch.
Figure 4-5 When the Status of the Path That Goes Through the Fibre Channel Switch to Be Replaced Is Offline(C) 2. Replace the Fibre Channel switch for the path that has been placed in Offline(C) status. In this example, replace the Fibre Channel switch connected to the HBA with host port number 0001. 3. Place in Online status the path that goes through the replaced Fibre Channel switch.
Changing the HDLM Device Configuration This section describes the actions and procedures to change the HDLM device configuration. To set up or change (add, change or delete) an LU in a storage system, use the management program of the storage system, rather than the HDLM functionality. For more information on configuring or changing an LU, see the manual provided with the storage system.
The HAL daemon detects hardware configuration changes, for example, when a USB device or CD-ROM is inserted. • If you execute the dlmcfgmgr utility with the -v parameter specified, a hyphen (-) might be displayed in the Device column as shown below: # dlmcfgmgr -v HDevName Management Device Host Channel Target Lun /dev/sddlmaa configured /dev/sdd 3 0 0 0 /dev/sdk 3 0 1 0 /dev/sdr 4 0 0 0 4 0 1 0 KAPL10302-I /sbin/dlmcfgmgr completed normally.
Adding a New LU To add a new LU (HDLM device) to the host on which the HDLM is installed: 1. Use the management program of the storage system to allocate an LU, which is not yet allocated to the relevant host, to a port of the storage system that has a path to the relevant host and configure the path. For more information on configuring the path, see the manual provided with the storage system. 2. When you want to add an LU without restarting the host, perform step 3 and step 4.
Operation Command - SUSE LINUX Enterprise Server and a Brocade HBA driver Execute the following command: # echo "- - -" > /sys/class/scsi_host/hostn/scan Execute the following command to check whether the OS has recognized any devices: # cat /proc/scsi/scsi If the OS has not recognized any devices, execute the following commands in the order shown: # echo "1" > /sys/class/fc_host/hostn/issue_lip # echo "- - -" > /sys/class/scsi_host/hostn/scan If you are using Red Hat Enterprise Linux 5, Red Hat Enterprise
b: Channel number (bus number) c: Target ID d: Lun (host LU number) n: host port number driver-name: qlaxxxx (driver name in use) Example entries are shown below. When adding a device by using a QLogic HBA driver in Red Hat Enterprise Linux AS4/ES4: # echo "scsi-qlascan" > /proc/scsi/qla2200/1 # cat /proc/scsi/qla2200/1 # echo "scsi add-single-device 1 0 1 1" > /proc/scsi/scsi 4. Execute the HDLM-configuration definition utility (dlmcfgmgr -r).
4. Execute the HDLM-configuration definition utility (dlmcfgmgr -r). Based on the SCSI device created in step 3, the path configured in step 1 is added as a path for the HDLM device. The following is an example of executing the dlmcfgmgr utility: # /sbin/dlmcfgmgr -r 5. Restart the host on which the HDLM is installed. If you performed step 3 and step 4, the host does not have to be restarted. Go to step 6.
If you performed steps 4 and 5, you do not need to restart the host. Go to step 7. 7. Execute the dlmcfgmgr utility (dlmcfgmgr -v) or the view operation (dlnkmgr view -drv). Make sure that all the SCSI device names corresponding to the LU for which path allocations were cancelled in step 2 are represented with a hyphen (-) (optional).
the device shown in Table 4-3 Adding or Deleting a SCSI Device on page 4-38 to manually delete the SCSI device. 5. Restart the host on which the HDLM is installed. If you performed step 4, the host does not have to be restarted. Go to step 6. 6. Execute the HDLM-configuration definition utility (dlmcfgmgr -v) or the view operation of the dlnkmgr command (dlnkmgr view -drv) (optional).
8. Refer to the /var/opt/DynamicLinkManager/log/dlmcfgmgr1.log or execute the dlmcfgmgr (dlmcfgmgr -v) to check if the path mapped with the relevant HDLM device is deleted. The following is an example of executing the dlmcfgmgr utility: # /sbin/dlmcfgmgr -v Changing a Device Managed by HDLM into One Not Managed by HDLM: The following operation can be done without restarting the host. To change a device managed by HDLM into one not managed by HDLM: 1. Stop all accesses to the relevant LU. 2.
2. Execute the HDLM-configuration definition utility (dlmcfgmgr -v) to check if the device you want HDLM to manage is not being managed. If the Management status of the relevant HDLM device is represented as unconfigured in the execution result, the device is not being managed by HDLM. Perform this operation if necessary. If it is not necessary to check this, go to step 3. 3.
If the SCSI device name mapped with the path to the relevant HDLM device is represented with a hyphen (-) in the execution result, this means that the path was in disconnected status. Perform this operation if necessary. If it is not necessary to check this, go to step 2. 2. Connect the cable. If the cable is broken, replace it. 3. Restart the host on which the HDLM is installed.
2. Connect the cable. If the cable is broken, replace it. 3. Create the SCSI device for the path to be restored. Since you restore the path without restarting, the path for the SCSI device which was in disconnected status during bootup will not be created and you must execute the command for adding a device, shown in the following table, to manually create the SCSI device.
Purpose Command # echo "- - -" > /sys/class/scsi_host/hostn/scan If you are using Red Hat Enterprise Linux 5, Red Hat Enterprise Linux 6, or SUSE LINUX Enterprise Server, the devices might be automatically recognized by the OS hot plug function. If the devices are recognized, the above procedure is not necessary.
# /sbin/dlmcfgmgr -v Restoring the Path in Disconnected Status This subsection describes how to restore the path to an HDLM device that was in disconnected status (the cable was pulled out or broken). 1. Execute the HDLM-configuration definition utility (dlmcfgmgr -v) to check while the path to the relevant HDLM device was in disconnected status.
change the HDLM device name. For details about the dlmchname utility, see Chapter 7, Utility Reference on page 7-1. 1. Create a device name replacement definition file based on the current HDLM device configuration information. When the dlmchname utility is executed with the -o parameter, a device name replacement definition file (/etc/opt/DynamicLinkManager/dlmchname.conf) is created based on the current HDLM device configuration information. # /opt/DynamicLinkManager/bin/dlmchname -o 2.
# /bin/cat 3585011299 3585011299 3585011299 /etc/opt/DynamicLinkManager/dlmchname.conf 0090 sddlmad 0091 sddlmac 0092 sddlmaa To change the name of an HDLM device used as a boot disk, go to step 5. 4. Stop access to the HDLM device whose name is to be changed. To stop access to the HDLM device, perform the following operations: ¢ Unmount the HDLM device if the HDLM device is mounted. ¢ Deactivate the volume group if the HDLM device is used in an LVM. Stop applications that are using the HDLM device.
iLU HDevName Device PathID Status 0090 sddlmad /dev/sda 000004 Online /dev/sdd 000005 Online /dev/sdj 000008 Online /dev/sdg 000009 Online 0091 sddlmac /dev/sdb 000006 Online /dev/sde 000007 Online /dev/sdh 000010 Online /dev/sdk 000011 Online 0092 sddlmaa /dev/sdc 000000 Online /dev/sdf 000001 Online /dev/sdi 000002 Online /dev/sdl 000003 Online KAPL01001-I The HDLM command completed normally.
Allocation before restarting the host /dev/sddlmaa Allocation after restarting the host /dev/sddlmaa /dev/sddlmab# /dev/sddlmaa /dev/sddlmab /dev/sddlmaa /dev/sddlmab /dev/sddlmac# /dev/sddlmaa /dev/sddlmac /dev/sddlmaa /dev/sddlmab# /dev/sddlmac /dev/sddlmab /dev/sddlmac /dev/sddlmaa# /dev/sddlmab /dev/sddlmac /dev/sddlmaa : /dev/sddlmpp /dev/sddlmaa : /dev/sddlmpp /dev/sddlmaaa# /dev/sddlmaa : /dev/sddlmaap /dev/sddlmaa : /dev/sddlmaap /dev/sddlmbaa# # The newly allocated logical device file n
HDevName Lun /dev/sddlmaa 1 Management Device configured /dev/sde 2 0 0 - 0 0 0 /dev/sda 1 0 0 - 0 0 0 /dev/sdf 2 0 0 /dev/sdb 1 1 KAPL10302-I /sbin/dlmcfgmgr completed normally. 0 0 0 0 /dev/sddlmab 1 2 configured Host Channel Target To change to a status that does not display a hyphen, execute the dlmcfgmgr utility with the -u parameter specified. For details on the dlmcfgmgr utility, see dlmcfgmgr Utility for Managing the HDLM Configuration on page 7-22.
5 Troubleshooting This chapter describes how to properly use HDLM error information, and then how to resolve the problem, if an error has occurred in HDLM. The resolutions for path errors, HDLM program errors, and other types of errors are all described separately. If you need technical support, see Getting help on page xix.
Information Collected by the DLMgetras Utility for Collecting HDLM Error Information Immediately after an error occurs, execute the DLMgetras utility for collecting HDLM error information, since restarting the machine might delete error information before the information is collected by DLMgetras. For details about the DLMgetras utility and the error information it collects, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3.
The path name indicates a path. When you modify the system configuration or replace a piece of hardware, you should check the path names to identify the paths that will be affected by the change. A path name consists of the following four elements, separated by periods: ¢ Host port number (hexadecimal) ¢ Bus number (hexadecimal) ¢ Target ID (hexadecimal) Host LU number (hexadecimal) This path name is also the same as PathName displayed by the command's view operation.
Figure 5-1 Error Location When the KAPL08022-E Message Is Output The following figure shows the troubleshooting procedure when the KAPL08022-E message is output. Figure 5-2 Troubleshooting Procedure When a Path Error Occurs The following shows the procedure for using the HDLM command (dlnkmgr) to handle a path error.
Examining the Messages Examine the message that is output to syslog in the host by using applications or tools for monitoring messages. If the KAPL08022-E message is output, view the message to check the path in which the error has occurred. For details on each item displayed in messages, see Checking Error Information in Messages on page 5-2. Obtain Path Information Obtain path information. Execute the following command: # /opt/DynamicLinkManager/bin/dlnkmgr view -path -iem -hbaportwwn > pathinfo.
If any path cannot be placed online due to an error, the KAPL01039-W message will appear. To ignore such paths and to continue processing, type y. Type n to cancel processing. Check the statuses of the paths that cannot be placed online, and resolve the problem. What To Do for a Program Error The following describes what to do to handle errors that occur in an HDLM program. The following figure shows the troubleshooting procedure.
What To Do for the Program Error Follow the recommended actions for messages in Chapter 8, Messages on page 8-1. If the error occurs again after you thought that you had resolved the problem, use the dlnkmgr command's view operation to check the status of the HDLM program, and then do whatever is necessary to resolve the problem. For details on the view operation, see view (Displays Information) on page 6-30.
5-8 Troubleshooting Hitachi Dynamic Link Manager User Guide for Linux®
6 Command Reference This chapter describes the HDLM command (dlnkmgr) and its operations.
Overview of the HDLM Command dlnkmgr This section describes how to specify the HDLM command dlnkmgr and its subcommands (called operations in HDLM). Command format Enter the command using the following format: dlnkmgr operation [parameter [parameter-value]] dlnkmgr The command name. operation The type of operation entered after dlnkmgr. parameter A value required for an operation. parameter-value A value required for an operation parameter.
¢ ¢ 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 ("). 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.
# To Display the Format of the clear Operation -help Displays the format of the clear operation. Example # /opt/DynamicLinkManager/bin/dlnkmgr clear -help clear: Format dlnkmgr clear -pdst [-s] KAPL01001-I The HDLM command completed normally. Operation name = clear, completion time = yyyy/mm/dd hh:mm:ss # help (Displays the Operation Format) The dlnkmgr command's help operation displays the list of operations available for the HDLM command, or the format of individual operations.
Examples Example 1 The following example shows how to display all the operations available in the HDLM command. # /opt/DynamicLinkManager/bin/dlnkmgr help dlnkmgr: Format dlnkmgr { clear | help | offline | online | set | view | add | delete} KAPL01001-I The HDLM command completed normally. Operation name = help, completion time = yyyy/mm/dd hh:mm:ss # Example 2 The following example shows how to display the formats of multiple operations.
dlnkmgr help { clear | offline | online | set | view | add | delete} KAPL01001-I The HDLM command completed normally. Operation name = help, completion time = yyyy/mm/dd hh:mm:ss # 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, or single path. Instead of specifying a path, you can also specify a SCSI device name. There must always be at least one online path accessing each LU.
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 host port number and bus number. Specify the host port number and bus number of the target HBA port: the numbers are found in the PathName field displayed using the view operation. Enter a period between these two parameter values. For details about the view operation, see view (Displays Information) on page 6-30.
# /opt/DynamicLinkManager/bin/dlnkmgr offline -cha -pathid 000001 KAPL01055-I All the paths which pass the specified CHA port will be changed to the Offline(C) status. Is this OK? [y/n]:y KAPL01056-I If you are sure that there would be no problem when all the paths which pass the specified CHA are placed in the Offline(C) status, enter y. Otherwise, enter n. [y/n]: KAPL01061-I 2 path(s) were successfully placed Offline(C); 0 path(s) were not.
-s Executes the command without displaying the message asking for confirmation of command execution from the user. Specify this parameter if you want to skip the response to the confirmation message: for example, when you want to execute the command in a shell script or batch file.
The following example shows how to filter and display the information on all paths that pass through the HBA port whose host port number is 0004 and bus number is 0000: # /opt/DynamicLinkManager/bin/dlnkmgr view -path | grep 0004.0000 The above command will display information on all the paths that pass through the specified HBA port.
Parameters To place paths Online -path Indicates that the target of the operation is a path managed by HDLM. This parameter is optional because online is always used for paths, so it is assumed. Make sure that you specify the path to be taken online by using the -hba, -cha, -pathid, or -device parameter. If you do not specify any of these parameters, the command will place all the offline paths online.
target AutoPATH_ID is 000000, enter 000000 or 0 for the parameter value. 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 reassigned to each path of the LU when you execute the HDLMconfiguration definition utility (dlmcfgmgr). Always make sure that you use the view operation to find the current AutoPATH_ID of the target path, before executing the online operation.
The following shows an example of how to place online a path whose SCSI device name is /dev/sde while confirming command operation. # /opt/DynamicLinkManager/bin/dlnkmgr online -path -device / dev/sde KAPL01050-I The currently selected paths will be changed to the Online status. Is this OK? [y/n]:y KAPL01061-I 1 path(s) were successfully placed Online; 0 path(s) were not.
To Display the Format of the Online Operation -help Displays the format of the online operation. Example The following example shows how to display the format of the online operation: # /opt/DynamicLinkManager/bin/dlnkmgr online -help online: Format dlnkmgr online [-path] [-s] dlnkmgr online [-path] -hba HBAPortNumber.
9500V | grep 0A The above command will display information pertaining to only those paths that pass through the specified CHA port. set (Sets Up the Operating Environment) The dlnkmgr command's set operation sets the HDLM operating environment.
Parameters To Set Up the HDLM Operating Environment The table below shows the defaults and recommended values for each setting. If you change the value of the set operation, the new value takes effect immediately. Table 6-2 Default and Recommended Values Item name Load balancing Default value Recommended value on on The Extended Least I/Os algorithm is used. The recommended algorithm depends on the operating environment.
Item name Default value Recommended value extended load balancing Dynamic I/O path control# off off The checking interval is 10 minutes. The recommended checking interval depends on the operating environment. # This item is applied only when Hitachi AMS2000 series, Hitachi SMS series, or HUS100 series storage is used. -lb {on [-lbtype {rr|exrr|lio|exlio|lbk|exlbk}]|off} Enables or disables load balancing.
Value Description 2 Collects error information for the Warning or higher level. 3 Collects error information for the Information or higher level. 4 Collects error information for the Information (including maintenance information) or higher level. The higher the error log collection level value, the more log information will be output. As the amount of log information that is output increases, the amount of time before existing information will be overwritten becomes shorter.
Table 6-4 Trace Level Values Value Description 0 Does not output any trace. 1 Only outputs error information. 2 Outputs a summary of program operation. 3 Outputs details of program operation. 4 Outputs all information. The higher the error log collection level value, the more log information will be output. As the amount of log information that is output increases, the amount of time before existing information will be overwritten becomes shorter.
When you specify on, specify the checking interval of path health checking by specifying the parameter immediately following on. If you do not specify a checking interval, path health checking is executed in the following interval: ¢ When the checking interval has not been specified before: Every 30 minutes (default setting) When the checking interval has been specified before: The previously specified interval The explanation for the following sub-parameter describes how to specify the checking interval.
Operations on page 6-24 for the relationship between automatic failbacks and intermittent error monitoring. When you specify on, specify the checking interval by specifying the parameter immediately following on.
The default is off. 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. If on is specified, be sure to also specify the intermittent error monitoring interval and the number of times that the error is to occur. The system assumes that an intermittent error is occurring if the specified number of times that the error is to occur is reached during the monitoring interval.
while intermittent errors are not being monitored, the values will not change. The monitoring interval specified in this parameter is stored even though specifying -iem off disables intermittent error monitoring. Therefore, when you re-enable intermittent error monitoring and a monitoring interval is not specified, error monitoring will be performed by using the stored monitoring interval. -iemnum number-of-times-error-is-to-occur Specify the number of times the error is to occur.
Table 6-5 Relationship Between the Setting for the Automatic Failback Function and Intermittent Error Monitoring and the Executable Operations Setting AFB on IEM on Available operation Set AFB to on. The operations of AFB and IEM do not change. Change the AFB setting. AFB is performed under the new settings.#1 Set AFB to off. • AFB and IEM are disabled. • The error count, elapsed monitoring time, and information about paths not subject to automatic failback are cleared.
Setting AFB IEM off Available operation Result of operation Set AFB to on. AFB is enabled. Set AFB to off. The operations of AFB and IEM do not change. Legend: AFB: Automatic failback IEM: Intermittent error monitoring #1 When this condition is not satisfied, the KAPL01080-W message is output and an error occurs. The status of intermittent error monitoring does not change. #2 Because automatic failback is off, intermittent error monitoring is disabled.
The following table lists and describes the license key types. Table 6-6 License Key Types Type Description Permanent license key Permanent license keys are valid for using HDLM permanently. Temporary license key# Temporary license keys are used temporarily, for example, when a user needs to perform product evaluations. Temporary license keys are valid for 120 days after the installation. You cannot reuse a temporary license key.
Specifies the severity level of audit log data to be collected. The table below lists and describes the values used for this setting. The default is 6. Table 6-7 Values Indicating Audit Log Data Collection Levels Value (severity) Explanation No audit log data is collected. 0 1 2 Critical-level audit log data is collected. 3 Critical-level and Error-level audit log data is collected. 4 Critical-level, Error-level, and Warning-level audit log data is collected.
Value Corresponding facility value in the /etc/syslog.conf file local2 or 18 local2 local3 or 19 local3 local4 or 20 local4 local5 or 21 local5 local6 or 22 local6 local7 or 23 local7 -lbpathusetimes number-of-path-use-times Specifies the number of times the same path can be used for I/O operations when the Round Robin (rr), Least I/Os (lio), or Least Blocks (lbk) algorithm is used for load balancing. You can specify a decimal (base 10) value from 0 to 999999. The default is 32.
Specifies the checking interval (in minutes) for reviewing information about switching of controllers performed by the storage system which is used in the dynamic I/O path control function. Specify a value in the range from 1 to 1440. The default value is "10". -s Executes the command without displaying the message asking for confirmation of command execution from the user.
TraceLevel TraceFileSize 1000) Number-Of-TraceFiles Interval-Time (pchk) Interval-Time (afb) Error-Monitor-Interval Number-Of-Times AudlogLevel Category-Value all) Facility-Name { 0 | 1 | 2 | 3 | 4 } (Default Value 0) { 100 - 16000 }(KB) (Default Value { 2 - 64 }(Files) { 1 - 1440 }(Minute) (Default Value 4) (Default Value 30) { 1 - 1440 }(Minute) (Default Value 1) { { { { (Default Value 30) (Default Value 3) (Default Value 6) 1 - 1440 }(Minute) 1 - 99 }(Times) 0 - 7 } [ss] [a] [ca] | all } (Defaul
[-t] To display path information (by selecting a display item) /opt/DynamicLinkManager/bin/dlnkmgr view -path -item [pn] [dn] [lu] [cp] [type] [ic] [ie] [dnu] [hd] [iep] [hbaportwwn] [vid] [ha] [-hdev host-device-name] [-stname] [-srt {pn|lu|cp}] [-t] To display path information (by abbreviating the list items) /opt/DynamicLinkManager/bin/dlnkmgr view -path -c [-stname] [-srt {lu|cp}] [-t] To Display LU Information To display LU information /opt/DynamicLinkManager/bin/dlnkmgr view -lu [-hdev host-device-
To display corresponding information about an HDLM device, SCSI device, and LDEV /opt/DynamicLinkManager/bin/dlnkmgr view -drv [-t] To Display the Format of the view Operation /opt/DynamicLinkManager/bin/dlnkmgr view -help Parameters (To display program information) This section describes the parameters for the view operation, in the following order: To display program information on page 6-32 To display path information on page 6-39 To display LU information on page 6-51 To display corresponding informat
Parameter and program information to be displayed Item Description • 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.
Parameter and program information to be displayed Item Description Trace File Size(KB) Trace file size in kilobytes Number Of Trace Files Number of trace files. Path Health Checking • Settings for path health checking: on: Enabled off: Disabled • Checking interval: When the setting of the path health checking is on, the checking interval of path health checking is displayed within the parentheses following on. The time is in minutes.
Parameter and program information to be displayed Item Description • Setting status on: Enabled off: Disabled • Checking interval The parentheses following the setting status shows the checking interval for reviewing information about the switching of controllers performed by the storage system. "Minute" is used as the unit. If different settings have been specified for each storage system or LU, an asterisk (*) is added after the parentheses in which the checking interval is displayed.
Parameter and program information to be displayed Item Description When the view -sys -lic operation is executed, (ndays after) appears if there are n days left until the license period expires.
Parameter and program information to be displayed The number of times the same path can be used for extended load balancing Item Description Blocks (exlbk) algorithm is used for load balancing. If you used Global Link Manager to set the number of times the same path can be used in units of LUs, an asterisk (*) is added after the value. # When you use cluster software, the settings of the cluster function and the kinds of cluster servers are not displayed.
# Example 3 The following example shows how to display information about the HDLM alert driver: # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -adrv HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.x-xx yyyy/mm/dd hh:mm:ss 1000 KAPL01001-I The HDLM command completed normally.
# /opt/DynamicLinkManager/bin/dlnkmgr view -sys -lbpathusetimes Times Same Path Was Used : 32 KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss # Example 8 The following example shows how to display the number of times the same path can be used for extended load balancing: # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -expathusetimes Times Same ExPath Was Used : 100 KAPL01001-I The HDLM command completed normally.
-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. For details about the information displayed for product IDs, see Table 6-14 Product ID displayed by the view -path operation on page 6-49. -iem Use this parameter to add IEP to path information and display information about intermittent errors.
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. When the value of the -item parameter is omitted, only the PathID and the Status fields are displayed. The following table lists the correspondence between the display items that can be selected by using the -item parameter and the parameter values that can be specified after the -item parameter.
These sub-parameters are: -hdev host-device-name Displays information only for the paths accessing the specified host device. Specify the name of the logical device file (minus the partition number), /dev/sddlm[aa-pap], for the HDLM device. For details on logical device files for HDLM devices, see Logical Device Files for HDLM Devices on page 2-11. The host-device-name string is case-sensitive. When you specify this parameter, HDevName is displayed by default.
To display path information, by abbreviating the list items -path -c When you specify the -path parameter together with the -c parameter, the command selects certain items to be displayed, and shortens the contents of each item so that the information about each path fits into a single line on the screen. 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 Path Information on page 6-45.
For details about the information about product IDs, see Table 6-14 Product ID displayed by the view -path operation on page 6-49. -srt {lu|cp} Use this parameter to sort the path information in ascending order, according to the specified sorting key. The sorting keys are as follows: the first sorting key is the name of the storage system (DskName), the second sorting key is the value specified by the -srt parameter, and the third sorting key is AutoPATH_ID.
Table 6-12 Path Information Displayed Item No summary displayed Description Summary displayed Paths Total number of displayed paths, indicated by a decimal number. OnlinePaths Number of online paths from within the displayed paths, indicated by a decimal number. When the value of Paths equals the value of OnlinePaths, all paths are online. If the value of OnlinePaths is less than that of Paths, some paths are offline.
Displayed Item No summary displayed DskName#1 Description Summary displayed DskName Storage system name, which identifies the storage system that is accessed by a path. A storage system name consists of the following three elements, separated by periods: • Vendor ID: The name of the storage system vendor (for example, HITACHI). • Product ID: Indicates the storage system product ID, emulation type, or model ID (for example, OPEN-3).
Displayed Item No summary displayed Description Summary displayed Status of the path Status • Online: Online • Offline(C): Offline status caused by a command operation • Offline(E): Offline due to an error • Online(E): Failure has occurred (If none of the paths accessing one LU have an Online status, one of those paths is changed to the Online(E) status.) Paths that are Offline(E) or Online(E) require corrective action.
Displayed Item No summary displayed Description Summary displayed For details on logical device files for HDLM devices, see Logical Device Files for HDLM Devices on page 2-11. IEP#1 - Information about the intermittent error. This item is displayed only when you specify -iem with the -path parameter. One of the following values is displayed for each path: • Indicates that intermittent error monitoring is disabled or the monitoring time for an intermittent error is out of range.
Displayed Item No summary displayed Description Summary displayed middle two numbers are the CU number, and the last two characters are the internal LU number within the CU. When a virtual ID is not used, a hyphen (-) is displayed. PhysicalChaPort When a path is migrated using a virtual ID, displays port number of the CHA that is connected by the migrationdestination path. - When a virtual ID is not used, a hyphen (-) is displayed.
Product ID Model names of storage systems With the -stname parameter (Displays the following for the model name) Without the -stname parameter Hitachi AMS series AMS Hitachi SMS series SMS Hitachi WMS series WMS HUS100 series HUS100 Lightning 9900 series Emulation type# 9910/9960 Lightning 9900V series 9970/9980 SVS SVS USP • Hitachi NSC55 • Hitachi Universal Storage Platform 100 • Hitachi Universal Storage Platform 600 • Hitachi Universal Storage Platform 1100 • Hitachi Universal
To display LU information When displaying LU information, if the -item parameter, -c parameter, or the -c -item parameter is specified at the same time as the -lu parameter, you can add and display items and display a summary of LU information. This section describes each parameter and the LU information and displayed items.
/dev/sdj 000013 Online /dev/sdo 000018 Online 0002 sddlmae /dev/sdu 000004 Online /dev/sdf 000009 Online /dev/sdk 000014 Online /dev/sdp 000019 Online 0003 sddlmaa /dev/sdq 000000 Online /dev/sdv 000005 Online /dev/sdg 000010 Online /dev/sdl 000015 Online 0004 sddlmab /dev/sdr 000001 Online /dev/sdw 000006 Online /dev/sdh 000011 Online /dev/sdm 000016 Online KAPL01001-I The HDLM command completed normally.
Items displayed by the dlnkmgr view -lu -item command Values specified after the -item parameter HCTL hctl DPC dpc Physical-Product vid Physical-SerialNumber vid Physical-iLU vid Physical-ChaPort vid Org-Product ha Org-SerialNumber ha Org-iLU ha HaStat hastat 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.
Example 2 When using Hitachi AMS2000 series, Hitachi SMS series, or HUS100 series storage and displaying LU information with DPC added to the display items: # /opt/DynamicLinkManager/bin/dlnkmgr view -lu -item dpc Product : HUS100 SerialNumber : 9203008 LUs : 3 Dynamic I/O Path Control : on* iLU HDevName DPC PathID Status 000006 sddlmad on 000000 Online 000003 Online 000007 sddlmaa off 000001 Online 000004 Online 000008 sddlmab on 000002 Online 000005 Online KAPL01001-I The HDLM command completed normally.
The following example shows how to display a summary of LU information (without selecting items to be displayed): # /opt/DynamicLinkManager/bin/dlnkmgr view -lu -c Product S/N LUs iLU HDevName Paths OnlinePaths 9500V 0115 5 0000 sddlmac 4 4 0001 sddlmad 4 4 0002 sddlmae 4 4 0003 sddlmaa 4 4 0004 sddlmab 4 4 KAPL01001-I The HDLM command completed normally.
Items of LU information Table 6-17 LU Information on page 6-56 describes the displayed LU information. The following explains the table headings: • No summary displayed: The user specifies the -lu parameter or -lu item parameter. • Summary displayed: The user specifies the -lu -c parameter or -lu -c item parameter.
Displayed item No summary displayed Description Summary displayed internal LU number within the CU.The first character of a CU number is 0. • For the Thunder 9500V series, Hitachi AMS2000/AMS/WMS/SMS series, and HUS100 series, indicated by a decimal number. The entire value of iLU is the internal LU number within the storage system. You can identify an actual LU by referencing iLU from the storage system management program.
Displayed item No summary displayed PathID Description Summary displayed - • A fiber cable connection is changed. • A Fibre Channel switch's zone setting is changed. The AutoPATH_ID. AutoPATH_ID is assigned every time the host is restarted. When a new LU was added and the host has not been restarted, AutoPATH_ID is reassigned to each path of the LU when you execute the HDLM-configuration definition utility (dlmcfgmgr). PathName#1 - The path name, which indicates a path.
Displayed item No summary displayed Description Summary displayed Paths that are Offline(E) or Online(E) require corrective action. The appropriate action can be determined by referring to What To Do for a Path Error on page 5-3.
Displayed item No summary displayed HCTL#1 Description Summary displayed - • A value of at least 0: Indicates the number of errors that occurred during intermittent error monitoring. • *: Indicates that an intermittent error occurred (automatic failback does not check the path). SCSI device configuration information. The following information is shown in "a.b.c.
Displayed item No summary displayed Description Summary displayed - Paths Total number of the paths recognized by HDLM for the LU to be displayed. - OnlinePaths Number of available 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.
Table 6-18 To display corresponding information about an HDLM device, SCSI device, and LDEV Item PathID Description AutoPATH_ID indicated by a decimal number. AutoPATH_ID is assigned when the host is restarted. When a new LU was added and the host has not been restarted, AutoPATH_ID is re-assigned to each path of the LU when you execute the HDLM-configuration definition utility (dlmcfgmgr). HDevName Host device name.
Use this parameter to display the view operation format. Example The following example shows how to display the format of the view operation.
Parameters To Add a Path Dynamically -path Indicates that the target of the operation is a path managed by HDLM. Example # /opt/DynamicLinkManager/bin/dlnkmgr add -path KAPL01161-I This operation will change the path configuration. Do you want to continue? [y/n]:y KAPL01162-I A path was added. (path ID = 00010, storage = HITACHI.HUS100.9100163, iLU = 0030) : KAPL01159-I Paths were added.
delete (Deletes a Path Dynamically) The dlnkmgr command's delete operation batch-removes paths previously deleted from the OS from the HDLM management targets. You can execute this command dynamically without any effects on existing paths.
command for deleting the device shown in Table 4-3 Adding or Deleting a SCSI Device on page 4-38. To Display the Format of the delete Operation -help Use this parameter to display the delete operation format. Example # /opt/DynamicLinkManager/bin/dlnkmgr delete -help delete: Format dlnkmgr delete -path [-s] KAPL01001-I The HDLM command completed normally.
7 Utility Reference This chapter explains the utilities used by HDLM.
Overview of the Utilities HDLM provides the following utilities: • The DLMgetras utility for collecting HDLM error information When an error occurs, this utility collects the files that contain information to be submitted to your HDLM vendor or maintenance company. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3.
• The installgetras utility for collecting HDLM installation error information If an error occurred during installation, this utility collects files that contain information to be submitted to your HDLM vendor or maintenance company. For details on the installgetras utility, see installgetras Utility for Collecting HDLM Installation Error Information on page 7-42. • The installhdlm utility for installing HDLM This utility performs a new installation, upgrade installation, or reinstallation of HDLM.
When the host is restarted, some of the information that was collected by the DLMgetras utility will be deleted. If an error occurs, immediately execute this utility.
within the directory in which the DLMgetras utility was executed, and the files found will be collected. • Do not specify a directory that contains the directory to which the collected information is output. If you specify this directory, the DLMgetras utility will run indefinitely. • Lines beginning with the hash mark (#) are handled as comment lines. • If the hash mark (#) is encountered anywhere other than at the beginning of a line, it is assumed to be part of a path name.
This file contains cluster information. Table 7-1 Information Stored in the cluster.tar.gz File on page 7-6 shows the detailed error information stored in the cluster.tar.gz file. Table 7-2 Information Stored in the cluster.tar.gz File, which Is Recorded by the OS and HDLM Commands When the DLMgetras Utility Is Executed on page 7-7 lists and describes the detailed information stored in the cluster.tar.gz file, which is recorded by the OS and cluster commands when the DLMgetras utility is executed. • hbsa.
Output directory#1 Files /var/VRTSvcs/log Explanation ha-debug Heart Beat debug log file (when using SUSE LINUX Enterprise Server) All subdirectories and files#2 VCS log #1 Each output directory is created in the directory that is specified when the user expands the cluster.tar.gz file. #2 This information is collected only if software for which information is to be collected is installed. Table 7-2 Information Stored in the cluster.tar.
Executed command Files Explanation /opt/VRTSvcs/bin/hastatus summary VCS_hastatussummary.txt # VCS cluster status information /opt/VRTSvcs/bin/hasys display VCS_hasys-display.txt VCS node information /opt/VRTSvcs/bin/hasys state VCS_hasys-state.txt # /sbin/cluconfig -l RHCM_cluconfig-l.txt # RHCM cluster configuration information (when using Red Hat Enterprise Linux) /sbin/clustat RHCM_clustat.
Output directory#1 /boot/grub /etc Files Explanation menu.lst Boot selection list (when using SUSE LINUX Enterprise Server (IA32/ EM64T/AMD64)) grub.conf Boot loader configuration file (when using Red Hat Enterprise Linux (IA32/EM64T/AMD64)) crypttab Block device information encrypted using LUKS (when using Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 6) dracut.conf dracut settings file drbd.
Output directory#1 Files syslog.conf syslogd settings file (when using Red Hat Enterprise Linux AS4/ES4, or Red Hat Enterprise Linux 5) /etc/ais openais.conf OpenAIS settings file /etc/cron* All subdirectories and cron file files /etc/dracut.conf.d All subdirectories and dracut settings directory files /etc/hotplug blacklist Information about modules that have not been loaded by a hot plug /etc/init.d boot Script for starting and initializing (when using SUSE LINUX Enterprise Server) boot.
Output directory#1 /etc/opt/ DynamicLinkManager Files Explanation auditlog.dat Audit log settings file .dlmfdrv.conf Configuration definition file .dlmfdrv1.conf Backup files for the configuration definition file .dlmfdrv2.conf .dlmfdrv3.conf .dlmfdrv.unconf File that defines non-HDLMmanaged disks .dlmfdrv1.unconf Backup files for the file that defines non-HDLM-managed disks .dlmfdrv2.unconf .dlmfdrv3.unconf dlmchname.conf Device name replacement definition file dlmchname1.
Output directory#1 Files Explanation rawdevices Character-type device information (when using Red Hat Enterprise Linux AS4/ES4) scsidev SCSI device settings file (when using SUSE LINUX Enterprise Server) sysctl sysrq information file (when using SUSE LINUX Enterprise Server) xendomains Xen settings file (when using SUSE LINUX Enterprise Server) /etc/sysconfig/hdlmscripts All subdirectories and HDLM-related script files /etc/sysconfig/mkinitrd All subdirectories and initrd related file (when us
Output directory#1 Files Explanation drbd DRBD status information filesystems File system list interrupts Information about interruption to a processor iomem I/O memory map information ioports I/O port information kallsyms Kernel symbol information loadavg Information about average load time locks File lock information mdstat md device information meminfo Memory information misc MISC Driver information modules Load module information mounts Mount information partitions Informat
Output directory#1 Files Explanation /proc/sys/vm All subdirectories and Virtual memory parameter files information /proc/xen balloon capabilities Xen-related information (when using SUSE LINUX Enterprise Server) /tmp qemu.log KVM-related log file (when using Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 6) /var/lib/dhclient dhclient* DHCP network information /var/lib/dhcpcd dhcpcd* DHCP network information /var/lib/heartbeat/crm cib.
Output directory#1 Files Explanation dlnkmgr2.log Process-specific-trace information file hdlmtr1.log Trace file dlnkmgr1.log, : hdlmtr64.log /var/opt/ DynamicLinkManager/log/ mmap dlnkmgr.mm Process-specific-trace related file hdlmtr.
Executed command 7-16 Files Explanation /bin/ls -altR /etc/init.d init.txt List of script files (when using SUSE LINUX Enterprise Server) /bin/ls -altR /opt/ DynamicLinkManager DLMfilelist.txt List of files in the following directories: • /opt/ DynamicLinkManager • /var/opt/ DynamicLinkManager/log /bin/ls -altRZ /dev dev_dsk_security.
Executed command Files Explanation /bin/rpm -V HDLM rpm-V.txt HDLM package revised information /bin/uname -a uname-a.txt OS version /etc/init.d/drbd status drbd-status.txt DRBD status information /etc/init.d/o2cb status o2cb-status.txt o2cb status information /etc/init.d/openais status openais-status.txt OpenAIS status information /opt/DynamicLinkManager/ bin/dlmgetomtrace dlmgetomtrace.dmp Trace information of HDLM functions /opt/DynamicLinkManager/ bin/dlmpr -k dlmpr-k.
Executed command Files Explanation /opt/DynamicLinkManager/ bin/dlnkmgr view -sys audlog, /opt/DynamicLinkManager/ bin/dlnkmgr view -sys lbpathusetimes, /opt/DynamicLinkManager/ bin/dlnkmgr view -sys expathusetimes 7-18 /sbin/blkid blkid.txt Block device attribute information (when using Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 6) /sbin/chkconfig --list chkconfig.txt Service settings /sbin/cryptsetup luksDump device-file cryptsetupluksDump.
Executed command Files Explanation Enterprise Linux 6, or SUSE LINUX Enterprise Server 11) /sbin/lilo/usr/bin/udevinfo -d -t lilo-t.txt Boot loader information (when using IA32, EM64T, or AMD64) /sbin/lsmod lsmod.txt List of load modules /sbin/lspci -v lspci-v.txt PCI information /sbin/lvmdiskscan lvmdiskscan.txt lvm disk information (when using Red Hat Enterprise Linux 6 or SUSE LINUX Enterprise Server) /sbin/lvs lvs.
Executed command Files Explanation segment, stack segment, and file descriptor) for the process 7-20 /usr/bin/env env.txt Environment variables information /usr/bin/free free.txt Memory information /usr/bin/getconf PAGESIZE getconfPAGESIZE.txt Memory page size information /usr/bin/ident dlnkmgr dlmmgr DLMgetras libdlm.so libhdlmhcc-* libhdlmhccmp-* dlmcfgmgr sddlmadrv.ko sddlmfdrv.ko whatlist.txt Program build number (dlnkmgr, dlmmgr, DLMgetras, libdlm.
Executed command Files Explanation Enterprise Linux 5 or Red Hat Enterprise Linux 6) /usr/sbin/clvmd -V clvmd-V.txt clvmd version /usr/sbin/crm_resource -L crm_resource-L.txt Pacemaker resource list /usr/sbin/getsebool -a getsebool-a.txt Security control values for daemon execution (Boolean values in SELinux) (when using Red Hat Enterprise Linux) /usr/sbin/lsscsi lsscsi.txt SCSI device list information (when using SUSE LINUX Enterprise Server) /usr/sbin/lvmdiskscan lvmdiskscan.
dlmcfgmgr Utility for Managing the HDLM Configuration For management by HDLM, the HDLM-configuration definition utility obtains the SCSI device information stored by Linux by detecting the information on the path between the host and storage system to register in HDLM, and then creates, updates, or deletes the HDLM devices. Also, this utility sets an HDLM device as a management target or excludes it from being managed.
-s Specify this parameter when you do not want to display the confirmation messages during execution of the dlmcfgmgr utility. When you execute this utility with this parameter specified, the confirmation message for each HDLM device is not displayed. Use this parameter when you want to skip a response to the confirmation message (to eliminate the manual intervention). For example, use this parameter when executing a command using a shell script or batch file.
Status before executing the dlmcfgmgr utility (dlmcfgmgr -r) Status after executing the dlmcfgmgr utility (dlmcfgmgr -r) /dev/sddlmac /dev/sddlmaa : /dev/sddlmpp /dev/sddlmaa : /dev/sddlmpp /dev/sddlmaaa# /dev/sddlmaa : /dev/sddlmaap /dev/sddlmaa : /dev/sddlmaap /dev/sddlmbaa# # A newly assigned logical device file name of the HDLM device Every time the host starts, the dlmcfgmgr utility (dlmcfgmgr -r) is automatically executed.
from being managed immediately after execution of the utility, except when the specified HDLM device is in use. If the specified HDLM device is in use, an error occurs. You can use this parameter to exclude the HDLM devices that are no longer required to be managed by HDLM. The excluded HDLM devices are not displayed with the dlnkmgr command's view operation and the HDLM device files for these devices are not created. Therefore, these devices become unavailable to the user.
You can specify one or more logical device file names of an HDLM device (/dev/sddlm[aa-pap]) as a value of the -u parameter. For details on logical device files for HDLM devices, see Logical Device Files for HDLM Devices on page 2-11. Specifying the -u parameter without the parameter value cases an error. If all the HDLM devices are the target, specify all. Specifying all together with a logical device file name of an HDLM device causes an error.
In response to the confirmation message, enter y to execute the utility and n not to execute the utility. Example 2: To exclude the HDLM device sddlmaa from being managed without confirming the execution of the utility: Example 3: To delete the information for all the unavailable paths and unregister the path information from HDLM after confirming the execution of the utility: In response to the confirmation message, enter y to execute the utility and n not to execute the utility.
Table 7-7 Information for the Management Status and Configuration Information of an HDLM Device Item Description HDevName Indicates the logical device file name of the HDLM device, using an absolute path. This is indicated only for the first path for the relevant LU. Management Indicates the current management status of the HDLM device. configured: indicates that the HDLM device is to be managed. unconfigured: indicates that the HDLM device is excluded from being managed.
# Reference information If you do not specify a parameter, the syntax of the dlmcfgmgr utility is displayed. # /sbin/dlmcfgmgr KAPL10319-W usage: /sbin/dlmcfgmgr [-s] { -r | -o {special-file-name ... | all} | -i {special-file-name ... | all} | -v [-udev] | -u {special-file-name ...
all the specified HDLM devices (/dev/sddlmaa, /dev/sddlmab, and /dev/ sddlmac) is executed continuously. • a. Execute the dlmcfgmgr utility with the -i parameter specified. b. Execute the dlmcfgmgr utility with -r parameter specified. • If you execute the dlmcfgmgr utility with the -i parameter specified, the HDLM device that is not a management target can be changed to a managed status.
• a. Delete the SCSI device you just added. b. Dynamically add the SCSI device once again. c. Execute the online operation to place the device path online. d. Execute the dlmcfgmgr utility with the -r parameter specified. If you execute the dlmcfgmgr utility with the -r parameter specified while all paths connecting to the HDLM device are disconnected, the HDLM partition information will be lost from /proc/partitions. To restore the HDLM partition information, follow these steps: a.
• For disks, such as system disks, that cannot be placed in offline during system operation, execute the HDLM device name replacement utility with the -f parameter specified, and then restart the host to change the name. If an HDLM device name is changed with the -f parameter specified, the following restrictions are applied until the host restarts: ¢ An error occurs if the dlmcfgmgr utility is executed. ¢ The HDLM device name before the change is used in I/Os.
dlmmkinitrd Utility for Supporting a Boot Disk This utility creates an initial RAM disk image file for using an HDLM device as a boot disk. Note that, for Red Hat Enterprise Linux 6, the dlmmkinitrd utility is not installed. To create an initial RAM disk image file in Red Hat Enterprise Linux 6, use the dracut command.
Specify the kernel used for creating an initial RAM disk image file. Example The following shows an execution example for Red Hat Enterprise Linux 5: /opt/DynamicLinkManager/bin/dlmmkinitrd /boot/initrd- 2.6.18-194.el5hdlm.img `uname -r` For SUSE LINUX Enterprise Server When creating an initial RAM disk image file, you can do so without specifying the image file name and the path for the file to be created, or you can specify these parameters.
-h Displays the format of the dlmmkinitrd utility. dlmpr Utility for Clearing HDLM Persistent Reservation If the persistent reservation of the LU is not canceled for some reason, this utility clears the reservation key to cancel the persistent reservation. This utility can be used when one of the following OSs is used for the host OS: • Red Hat Enterprise Linux 5 • Red Hat Enterprise Linux 6 • Oracle Unbreakable Enterprise Kernel 5 Format /opt/DynamicLinkManager/bin/dlmpr {{-k | -c} [sdn] [sdn] ...
Example To check the reservation keys, and then clear a reservation key: 1. Execute the dlmpr utility to display the reservation keys for sda, sdb, sdc, sdd, sde, and sdf.
dlmsetopt Utility for Setting HDLM Driver Options This utility changes the settings for the HDLM filter driver. Restart the host machine to apply the changed settings. Note that you do not need to restart the host machine every time you execute the dlmsetopt utility. If you execute the dlmsetopt utility more than once, restart the host after you have finished specifying all settings. Restarting the host enables all the changed settings.
1 to 3,600: Timeout value (in seconds) If the following values are specified, the message KAPL12553-W is displayed and then the processing ends: • 0 • Value of -1 or less • Value more than 3,600 • Non-numeric value. -inqr Specify the number of retries of the SCSI INQUIRY command. In HDLM, the default number of retries is 1. Note that the number of retries specified by using the -inqr parameter only applies to the SCSI INQUIRY command executed from HDLM.
Example Example 1: In this example, the utility sets the retry count to 100000: # /opt/DynamicLinkManager/bin/dlmsetopt -r 100000 KAPL12554-I The utility for setting HDLM driver option has started. KAPL12555-I The utility for setting HDLM driver option completed normally. KAPL12558-I Please restart the computer so that the option settings take effect.
• If you use the dlmsetopt utility in an environment where an HDLM device is used for the boot disk, after changing the settings, you need to recreate the initial RAM disk image file. To re-create the file, use the dracut command for Red Hat Enterprise Linux 6, and the dlmmkinitrd utility for supporting a boot disk for other OSs. If you change the name of the initial RAM disk image file, change the settings file for the boot loader so that the re-created initial RAM disk image file is used during boot-up.
• If you execute the dlmstart utility, do not change the settings of the sysfs interface that handles SCSI devices after an HDLM device is configured. dlmupdatesysinit Utility for Updating System Scripts In an environment that uses Red Hat Enterprise Linux, if you update the initscripts package after installing HDLM, HDLM information in the /etc/ rc.d/rc.sysinit file.
installgetras Utility for Collecting HDLM Installation Error Information This utility collects the error log information needed to analyze errors that occurred during HDLM installation. The collected information is compiled in a file and output to a specified directory. The following file is output: • installgetras.tar.gz This is a compressed file that contains information related to HDLM installation processing.
This directory is created in directory-to-which-collected-information-isoutput specified when the installgetras utility was executed. installhdlm Utility for Installing HDLM You can use this utility to perform a new installation, upgrade installation, or re-installation of HDLM. The utility can also be used to perform an unattended installation. An unattended installation enables a user to install HDLM without entering information.
• To enter a comment line, specify a hash mark (#) at the beginning of the line. • If a specified value is not allowed for the key setting, the KAPL09212-E and KAPL09228-W message is output. Items To Be Defined in an Installation-Information Settings File The following describes the information defined in the installation information settings file. [INSTALLATION_SETTINGS] section This section defines information that is used when the installhdlm utility is executed.
Necessity of definition Key name Description New installati on driver_config Specify either of the following values Optional to indicate whether to load the HDLM driver and configure the HDLM device: Maxim um Upgrade numbe installati r of on or re- charac installati ters on Optional 1 Optional 1 y: Load the HDLM driver and configure the HDLM device (default). n: Do not load the HDLM driver and configure the HDLM device. restart Specify whether to restart the host after installation.
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. [ENVIRONMENT_SETTINGS] section This section defines HDLM operation information. If this section is omitted, the installer will use the following values: • For a new installation, the installer uses the default values of the keys that are listed in the following Table 7-12 Keys in the [ENVIRONMENT_SETTINGS] Section on page 7-46 .
Necessity of definition Key name#1 Description#2 New installa tion Maxim Upgrad um e numbe installa r of tion or charac reters installa tion operations when the Round Robin (rr), Least I/Os (lio), or Least Blocks (lbk) algorithm is used for load balancing. You can specify a value from 0 to 999999. The default is 32.
Necessity of definition Key name#1 path_health_check Description#2 New installa tion Maxim Upgrad um e numbe installa r of tion or charac reters installa tion Optional Optional 3 Optional Optional 4 Optional Optional 3 Specify the interval in minutes from Optional the time the previous path status check finished until the time the next path status check started. Optional 4 Optional Optional 3 Specify the interval in minutes that Optional monitoring for intermittent errors is performed.
Necessity of definition Key name#1 Description#2 New installa tion Maxim Upgrad um e numbe installa r of tion or charac reters installa tion control function by using the values below. Note that, if this function is set, the setting for each storage system or LU is cleared.
The following shows an example of an edited installation information settings file. [INSTALLATION_SETTINGS] licensekeyfile=/var/tmp/hdlm_license licensekey=/etc/opt/DynamicLinkManager/dlm.
Specify this parameter to perform an unattended installation for HDLM. Specify an installation-information settings file for this parameter. For details about installation-information settings files, see Editing an Installation-Information Settings File on page 7-43. Log file The installux.sh utility outputs execution information to the log file /var/ tmp/hdlm_installux_sh.log. If the hdlm_installux_sh.log log file already exists, the utility appends execution information onto the end of the log file.
7-52 Utility Reference Hitachi Dynamic Link Manager User Guide for Linux®
8 Messages This chapter describes the format and meaning of the message IDs, and also the terms used in the messages and message explanations. For details on the meaning of the return codes output by HDLM when it receives a request from Global Link Manager and measures to take for them, see Return Codes for Hitachi Command Suite Common Agent Component on page 8-153.
□ KAPL15001 to KAPL16000 □ Return Codes for Hitachi Command Suite Common Agent Component 8-2 Messages Hitachi Dynamic Link Manager User Guide for Linux®
Before Viewing the List of Messages This section explains the following information that is needed to locate messages and understand the explanations in the sections from KAPL01001 to KAPL02000 on page 8-4. • Format and meaning of the message IDs • Terms used in the messages and message explanations The information is explained below. Format and Meaning of Message IDs Each message has a message ID. The following table shows the format and meaning of message IDs.
• HDLM management target KAPL01001 to KAPL02000 Message ID KAPL01001-I Message Text The HDLM command completed normally. Operation name = aa...aa, completion time = bb...bb Explanation Details The HDLM command completed successfully. aa...aa: clear, help, offline, online, set, or view bb...bb: Year/month/day hour:minute:second Action None. KAPL01002-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.
Message ID Message Text Explanation operation, see help (Displays the Operation Format) on page 6-4. KAPL01006-W A necessary parameter is not specified. Operation name = aa...aa Details The specified operation does not contain the necessary parameter. aa...aa: clear, set, offline, or view Action Execute help operation-name of the HDLM command (dlnkmgr) to check the parameter. Specify the correct parameter, and then retry.
Message ID Message Text Explanation Action Execute the view operation of the HDLM command (dlnkmgr) to check whether the HDLM manager has started. Start the HDLM manager if it has not started, and then retry the HDLM command. For details on the view operation, see view (Displays Information) on page 6-30. KAPL01013-E An error occurred in internal processing of the HDLM command. Operation name = aa...aa details = bb...bb Details An error unrelated to a user operation occurred during command processing.
Message ID Message Text Explanation path) and check the value displayed in PathName. Use the two leftmost digits of PathName for the relevant HBA port, and then retry. For details on the view operation, see view (Displays Information) on page 6-30. KAPL01016-W The target CHA port was not found. Operation name = aa...aa Details The path ID indicated by -pathid and required by the -cha parameter is not an object of HDLM management. aa...
Message ID Message Text Explanation HDLM operating environment have not finished. Action ¢ offline/online operation Use the view operation of the HDLM command (dlnkmgr) to check the settings, and then retry. For details on the view operation, see view (Displays Information) on page 6-30. ¢ view operation Refer to Chapter 3, Creating an HDLM Environment on page 3-1. Creating an HDLM Environment or Reconfiguring the HDLM Operating Environment on page 4-25, and then configure any paths that exist.
Message ID Message Text Explanation view (Displays Information) on page 6-30. KAPL01024-W The specified parameters cannot Details be specified at the same time. aa...aa: clear, offline, online, Operation name = aa...aa, set, or view parameters = bb...bb bb...bb: Parameters that cannot be specified at the same time Action Execute help operation of the HDLM command (dlnkmgr) to check which parameters can be specified at the same time, and then retry.
Message ID KAPL01041-E Message Text Explanation The entered value is invalid. The Details operation stops. Operation Command processing will be name = aa...aa aborted because an incorrect value was entered three times in a row for a request. aa...aa: clear, offline, online, or set Action Check the correct value, and then re-execute the HDLM command. KAPL01044-W A duplicate parameter value is specified. Operation name = aa...aa, parameter = bb...bb, parameter value = cc...cc Details aa...aa: view bb...
Message ID Message Text Explanation Action If you want to execute the operation, enter y. If you want to terminate processing, enter n. For details on the clear operation, see clear (Returns the Path Statistics to the Initial Value) on page 6-3. For details on the set operation, see set (Sets Up the Operating Environment) on page 6-15. KAPL01050-I The currently selected paths will Details be changed to the Online status. The online operation will be Is this OK? [y/n]: started.
Message ID Message Text Explanation If you want to execute the offline processing, enter y. If you want to terminate processing, enter n. For details on the offline operation, see offline (Places Paths Offline) on page 6-6. 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.
Message ID Message Text Explanation y. If you want to terminate processing, enter n. 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 all the paths to Offline(C). To set all the paths to Offline(C), enter y. To cancel the operation, enter n. aa...
Message ID Message Text specify parameter bb...bb and parameter value cc...cc. Operation name = dd...dd Explanation A parameter value is conflicting with the value of another parameter. aa...aa: Parameter name bb...bb: Parameter name cc...cc: Parameter value dd...dd: view or set Action Execute help operation-name of the HDLM command (dlnkmgr) to check the parameter and parameter value, and then retry. For details on the help operation, see help (Displays the Operation Format) on page 6-4.
Message ID Message Text Explanation path has already been set to Online/Online(S)/Online(D)/ Offline(C). aa...aa: Online, Online(S), Online(D) or Offline(C) Action Use the view operation of the HDLM command (dlnkmgr) to check the status of the path. For details on the view operation, see view (Displays Information) on page 6-30. For details on the online operation, see online (Places Paths Online) on page 6-10. For details on the offline operation, see offline (Places Paths Offline) on page 6-6.
Message ID KAPL01072-I Message Text The emergency license was installed. The license expires on aa...aa. Explanation Details A license was renewed and is registered as an emergency license. aa...aa: Year (4 digits)/month (01-12)/day (01-31) Action Install a permanent license by the expiration day. KAPL01073-E The temporary license expired. Details The temporary license has expired. Register a permanent license. Action Register a permanent license. KAPL01074-E The emergency license expired.
Message ID Message Text Explanation interval, and the number of times the error needs to occur. Action Set the intermittent errormonitoring interval to a value that is equal to or greater than (automatic-failback-checkinginterval x number-of-times-erroris-to-occur-for-intermittent-errormonitoring). KAPL01081-E The license key file is invalid. File name = aa...aa Details The format of the license key file is invalid. aa...
Message ID Message Text Explanation Details KAPL01088-W The specified parameter values cannot be specified at the same aa...aa: view time. Operation name = aa...aa, bb...bb: Parameter name parameter = bb...bb, parameter values = cc...cc cc...cc: Parameter values that cannot be specified at the same time Action Execute help operation-name of the HDLM command (dlnkmgr) to check which parameter can be specified, and then retry.
Message ID Message Text Explanation 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. KAPL01097-W All the current trace files will be deleted.
Message ID KAPL01112-E Message Text An attempt to connect to the HDLM driver has failed. Operation name = aa...aa Explanation Details HDLM driver information must be collected to execute the given HDLM command, but the HDLM driver cannot be accessed. aa...aa: clear, offline, online, set, or view Action If you did not perform HDLM configuration, Perform HDLM configuration.
Message ID Message Text command and check whether a normal result is displayed. Explanation Action If the dlnkmgr view -sys audlog command does not display a normal result, contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. KAPL01116-W The audit log configuration file is Details invalid. Restart the HDLM The audit log configuration file is Manager, and execute the invalid. "dlnkmgr view -sys -audlog" command and check the setting.
Message ID Message Text Explanation Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL01122-W The file does not exist. File name = aa...aa Details aa...aa: / etc/.DynamicLinkManager/ Path00 Action Reinstall HDLM.
Message ID KAPL01127-E Message Text You do not have execute permission for the file. File name = aa...aa Explanation Details aa...aa: /HDLM installation path/bin/.dlnkmgr_exe Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see clear (Returns the Path Statistics to the Initial Value) on page 6-3.
Message ID Message Text Explanation None. KAPL01134-I The target paths are already Online or Online(S). Details The specified paths are already in the Online or Online(S) status as a result of an online operation. Action Check path status by using the view operation.. For details on the view operation, see view (Displays Information) on page 6-30. For Online(S) paths: To change the status of a path from Online(S) to Online, reexecute the HDLM command using the -hapath parameter.
Message ID Message Text Explanation Use the view operation of the HDLM command (dlnkmgr) to check the setting for the host, storage, and LUs. For details on the view operation, see view (Displays Information) on page 6-30. KAPL01158-E Dynamic I/O path control cannot Details be applied to the specified aa...aa: on or off storage. Action Use the view operation of the HDLM command (dlnkmgr) to check the path ID. For details on the view operation, see view (Displays Information) on page 6-30.
Message ID Message Text Explanation - Check whether the paths to be deleted have been disconnected from the system. - Use the view operation of the HDLM command (dlnkmgr) to check whether the paths have already been deleted from HDLM. KAPL01161-I This operation will change the path configuration. Do you want to continue? [y/n]: Details This message confirms whether to perform a path configuration change by using an add operation or delete operation.
Message ID Message Text Explanation This message indicates that a delete operation succeeded. aa...aa: number of paths deleted bb...bb: year (4 digits)/month/ date hour:minute:second Action Use the view operation of the HDLM command (dlnkmgr) to verify that the paths were deleted. KAPL01165-I A path was deleted. (path ID = Details aa...aa, storage = bb...bb, iLU = This message displays information cc...cc) about a path deleted as the result of a delete operation. aa...aa: path ID of the deleted path bb.
Message ID Message Text Explanation executing the view operation of the HDLM command dlnkmgr. KAPL01168-I Details All P-VOL paths that are connected to the LU that has the All paths for each specified LU will specified path ID will be set to be set to Online or Online(D). To Online(D). Is this OK? [y/n]: continue, enter y. To cancel the operation, enter n. Note: All paths of the LU, including non-P-VOL paths, will be set to Online or Online(D).
Message ID Message Text Explanation bb...bb: Online(D) or Online(S)/ Online(D) Action Check path status by using the view operation. For Online(S) or Online(D) paths: To change the status of a path from Online(S) or Online(D) to Online, reexecute the HDLM command with the -hapath parameter specified. KAPL01172-I There are no Online(S)/ Online(D) paths among the target paths.
Message ID KAPL03004-C Message Text A critical error occurred in the HDLM API. (aa...aa) Explanation Details This information is required for resolving problems. aa...aa: API trace error information Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3.
Message ID KAPL03008-E Message Text An error occurred during log input to the HDLM alert driver. (aa...aa) Explanation Details This information is required for resolving problems. aa...aa: API trace error information Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3.
Message ID Message Text Explanation the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL04003-E The startup parameter is invalid. Details The HDLM manager internal parameter is invalid. Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Message ID Message Text Explanation If the same error occurs, re-install HDLM. For details on the view operation, see view (Displays Information) on page 6-30. For details on the set operation, see set (Sets Up the Operating Environment) on page 6-15. KAPL04010-E Could not open the error log file. Details HDLM manager cannot start normally (unable to open the error log file /var/opt/ DynamicLinkManager/log/ dlmmgr[1-16].log).
Message ID Message Text Explanation 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 DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL04014-E Output is impossible via the communication pipe. RC = aa...
Message ID Message Text Explanation aa...aa: HDLM manager trace information Action None. KAPL04022-W HDLM manager warning information - aa...aa Details This information is required for resolving problems. aa...aa: HDLM manager trace warning information Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Message ID Message Text Explanation HDLM Error Information on page 7-3. KAPL04025-C A memory shortage occurred in the HDLM manager. Details There was not enough memory to run the HDLM manager processes. Action To increase the amount of free memory, terminate unnecessary applications or restart the host. KAPL04026-I The temporary license is valid. The license expires in aa...aa days on (bb...bb). Details aa...aa: Expiration day bb...
Message ID Message Text Explanation of the options can be read, those values can be used. As for any remaining values, the default values will be used. Action For any non-default options, use the dlnkmgr set operation to set the options again. For details on the set operation, see set (Sets Up the Operating Environment) on page 6-15. KAPL04034-E An attempt to create the option definition file has failed. Details An attempt to re-create an option definition file (/etc/opt/ DynamicLinkManager/ dlmmgr.
Message ID Message Text Explanation dd...dd: Community name given to the trap ee...ee: Transmission data Action None. KAPL04047-W The file does not exist. File name = aa...aa Details aa...aa: / etc/.DynamicLinkManager/ Path00 Action Reinstall HDLM. KAPL04048-W You do not have read permission for the file. File name = aa...aa Details aa...aa: / etc/.
Message ID Message Text Explanation Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL04053-W The option definition file was recovered from a work file. KAPL04054-I Action Execute the dlnkmgr view -sys command to check whether the settings are recovered.
Message ID Message Text attached to Disk (aa...aa), Partition (bb...bb). Explanation The path corresponding to disk aa...aa and partition bb...bb was successfully registered in the core logic. aa...aa: Disk sequence number (decimal number) bb...bb: Fixed at 0 (decimal number) Action None. KAPL05008-E KAPL05011-E Could not allocate memory. (aa...aa:bb...bb) Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company.
Message ID Message Text Explanation 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 Details registered as the path (bb...bb). The HDLM filter driver was successfully attached and registered as a path. aa...
Message ID Message Text Explanation None. KAPL05020-I Processing of IOCTL(aa...aa) will Details now start. An IOCTL request was received. aa...aa: IOCTL code (hexadecimal number) Action None. KAPL05021-I Processing of IOCTL(aa...aa) completed normally. Details The processing for the requested IOCTL operation was successful. aa...aa: IOCTL code (hexadecimal number) Action None. KAPL05023-E Could not process the Details IOCTL(aa...aa). (bb...bb:cc...
Message ID Message Text Explanation check the application that sent the IOCTL system call. KAPL05701-I HDLM version aa...aa Build bb...bb cc...cc dd...dd ee...ee Details The version of HDLM is shown. aa...aa: HDLM version (character string) bb...bb: HDLM build number (decimal number) cc...cc: Days-and-months A.D (character string) dd...dd: Time in seconds (character string) ee...
Message ID Message Text Explanation # dlmcfgmgr -u logicaldevice-file-name-of-theHDLM-device d. Reconfigure the HDLM by using the following command: # dlmcfgmgr -r KAPL05708-E The system retried to allocate memory aa...aa times, but the retries failed. (bb...bb:cc...cc) Details aa...aa: Memory allocation retry count (decimal number) bb...bb: File ID, line number (hexadecimal number) cc...
Message ID Message Text Explanation Action None. KAPL05714-I The registration status of the reservation key was checked. Details The registration status of the reservation key was checked. Action None. KAPL05819-I Data for maintenance: aa...aa bb...bb cc...cc dd...dd. Details The filter driver outputs this message for maintenance. aa...aa: Maintenance information (hexadecimal number) bb...bb: Maintenance information (hexadecimal number) cc...cc: Maintenance information (hexadecimal number) dd...
Message ID KAPL06007-I Message Text IOCTL processing (aa...aa) will now start. Explanation Details The IOCTL request aa...aa was accepted. aa...aa: IOCTL code (hexadecimal number) Action None. KAPL06008-I IOCTL processing (aa...aa) completed normally. Details The IOCTL request aa...aa was processed normally. aa...aa: IOCTL code (hexadecimal number) Action None. KAPL06009-I Invalid IOCTL(aa...aa) was received. The processing is canceled. Details A request having an invalid IOCTL code aa...
Message ID KAPL06013-E Message Text Could not write log information into the log buffer. (aa...aa:bb...bb) Explanation Details Log information from the filter driver was destroyed without being written to a log buffer because the attempt to reserve memory for the log information failed. aa...aa: Message code (hexadecimal number) bb...bb: Buffer size (hexadecimal number) Action Check whether any other error occurred. The information that could not be written is discarded.
Message ID Message Text Explanation If the actual memory size is sufficient, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3.
Message ID Message Text Explanation dd...dd: Detailed information 3 (decimal (base-10) number) Action None. KAPL07824-I The owner controller of the LU connected to the path (aa...aa) was changed to (bb...bb). Details The owner controller of the LU connected to the path with the ID shown in the message was changed. aa...aa: Path ID of the changed LU. (same as PathID of view path) (Decimal number) bb...bb: Owner controller ID after the change. (Hexadecimal number) Action None.
Message ID Message Text Explanation ¢ When a path error is detected through an I/O error Displays the OS error code. cc...cc: 0x00000000 (fixed) Action Check the path in which the error was detected. KAPL08022-E A path error occurred. ErrorCode = aa...aa, PathID = bb...bb, PathName = cc...cc.dd...dd.ee...ee.ff...ff, DNum = gg...gg, HDevName = hh...hh Details A physical or logical error occurred in the path. aa...
Message ID Message Text Explanation online command or auto failback. To bring the path online, execute the dlmcfgmgr utility (dlmcfgmgr -r). KAPL08023-I A path was recovered. PathID = aa...aa, PathName = bb...bb.cc...cc.dd...dd.ee...ee, DNum = ff...ff, HDevName = gg...gg Details aa...aa: Path ID (same as PathID of view -path) (decimal (base-10) number) bb...bb: Host port number (same as PathName of view -path) (hexadecimal number) cc...
Message ID Message Text Explanation 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 What To Do for a Path Error on page 5-3 and switch the path shown in the message into Online. KAPL08032-I A path was recovered. (PathID = aa...aa) Details The path has changed to an online status. aa...
Message ID Message Text Explanation HDLM cannot be installed on this system. Action See Hosts and OSs Supported by HDLM on page 3-3 and install HDLM in a supported OS system. KAPL09005-E Details Could not stop the HDLM manager. Stop it manually, and An attempt to stop the HDLM then try the installation program manager service failed. or the remove program again. Action Stop the HDLM manager manually, and then re-execute the installation program or the remove program.
Message ID KAPL09020-E Message Text An attempt to remove Hitachi Network Objectplaza Trace Library 2 failed. Explanation Details An attempt to remove HNTRLib2 has failed. Action Manually remove HNTRLib2. If the attempt to remove HNTRLib2 fails again, contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM. KAPL09021-E An attempt to register the bundle PP name of Hitachi Network Objectplaza Trace Library 2 failed.
Message ID KAPL09028-E Message Text An attempt to install Hitachi Network Objectplaza Trace Library 2 failed. Explanation Details An attempt to install HNTRLib2 failed. Action Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM. KAPL09035-E The HDLM driver could not be loaded. Execute the dlmstart utility. For details on the dlmstart utility, refer to the HDLM User's Guide section "dlmstart (Utility for Starting HDLM)".
Message ID Message Text section "dlmcfgmgr (HDLMConfiguration Definition Utility)". KAPL09040-E The file could not be edited. File name = aa...aa Explanation the -r parameter specified. For details on the dlmcfgmgr utility, see dlmcfgmgr Utility for Managing the HDLM Configuration on page 7-22. Details An attempt to edit a file has failed. aa...aa: File name Action Make sure you can edit the file aa...aa. KAPL09043-I The installation of aa...aa completed successfully. Details HDLM was installed. aa..
Message ID Message Text Explanation Remove HDLM, and then reexecute the installation program. KAPL09049-W An attempt to delete a file or directory related to HDLM has failed. Name = aa...aa Details An attempt to delete a HDLMrelated file or directory has failed. aa...aa: File name or a directory name Action Delete the file or directory shown in aa...aa. KAPL09050-E The driver module dependencies Details could not be updated.
Message ID Message Text Explanation Install a permanent license by the expiration day. KAPL09079-I The permanent license has been Action installed. None. KAPL09080-I The temporary license has been installed. The license expires on aa...aa. Details The temporary license has been installed. aa...aa: Year (4 digits)/month (01-12)/day (01-31) Action Install a permanent license by the expiration day. KAPL09081-I The emergency license has been Details installed.
Message ID KAPL09092-I Message Text Explanation vendor or the maintenance company if there is a maintenance contract of HDLM. Action The installation was stopped because a stop request was received. Details Contact your HDLM vendor or the maintenance company if there is a maintenance contract of HDLM. The installation was aborted, because a stop request was received. Action Installation was terminated before all processing could be completed.
Message ID Message Text section "Hosts and OSs Supported by HDLM". KAPL09098-E Explanation package on a supported OS, see Hosts and OSs Supported by HDLM on page 3-3. An attempt to install aa...aa has Details failed. Code = bb...bb An attempt to install aa...aa has failed. aa...aa: Program name bb...bb: Code (decimal number). Action Please re-install HDLM after checking the error information and resolving the problems. KAPL09106-E An invalid parameter has been specified.
Message ID Message Text Explanation /var/tmp/hdlm_license KAPL09116-W The command could not be installed. (command = aa...aa) Details The output HDLM command cannot be used. aa...aa: Command name Action The output command can be executed by using a different name. If you want to use the output name, use the output command to overwrite or reinstall. KAPL09121-E aa...aa is not present at bb...bb. Details aa...aa: Installer name bb...bb: Installer path Action Install HDLM from the DVD-ROM.
Message ID Message Text Explanation Wait a while, and then reperform the installation or remove. KAPL09143-E Details HDLM aa...aa cannot be performed. Error Code = bb...bb HDLM cannot be installed or removed. aa...aa: "installation" or "remove" bb...bb: Internal code (decimal number) Action Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. KAPL09146-E A directory required by HDLM Details not found. Directory = aa...aa. aa...
Message ID Message Text Explanation /media/cdrecorder ¢ For Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 6: /media/cdrom ¢ For SUSE LINUX Enterprise Server: /media/media-volume-ID Action Check the HDLM installation media, or check the current kernel. KAPL09177-I HDLM version: aa...aa Details aa...aa: The version of HDLM to be installed. Action None. KAPL09191-W The installation information settings file does not exist.
Message ID Message Text Explanation or Table 3-9 Oracle Unbreakable Enterprise Kernel 5 Kernels Supported by HDLM on page 3-15. Action Make sure that the currently running OS is supported. KAPL09210-I aa...aa will now start. Details aa...aa has just started. aa...aa: installhdlm, installhdlm_analysis, ENVIRONMENT_SETTINGS, driver_config_settings, or dlmcfgmgr Action None. KAPL09211-I aa...aa completed successfully. Details aa...aa completed successfully. aa...
Message ID Message Text Explanation When a message except for the above was outputted, perform the action indicated in that error message. KAPL09215-E The system environment is invalid. Error Code = aa...aa Details The system environment is not valid as an environment for executing the installhdlm utility. aa...
Message ID Message Text Explanation amount of capacity, and then retry the operation. For details about the required unused capacity. For details about the required unused capacity, see Disk Requirements on page 3-84 in Memory and Disk Capacity Requirements on page 3-83. 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...
Message ID Message Text Explanation The correct location of installhdlm_analysis is / DVD-ROM/HDLM_Linux/bin. Make sure that the utility you want to execute is in the correct location and that you have the required permissions. If a utility is not in the correct location, copy the required files to the correct location, and then retry the operation. If you do not have a required permission, grant required permissions to yourself, and then retry the operation. If aa...
Message ID Message Text Explanation Specify the revised installation information settings file, and then retry the operation. KAPL09221-W The definition of the installation Details information settings file includes A character that cannot be used in an unusable character. Error a non-comment line was used. Code = aa...aa,bb...bb, line = aa...aa: Error number (decimal cc...cc number) that specifies the executed processing bb...bb: Return value (decimal number) of the executed processing cc...
Message ID Message Text Explanation Specify the revised installation information settings file and then retry the operation. KAPL09229-W The definition of the installation Details information settings file includes A section that does not exist is an invalid section name. Error included. Code = aa...aa,bb...bb, line = aa...aa: Error number (decimal cc...cc number) that specifies the executed processing bb...bb: Return value (decimal number) of the executed processing cc...
Message ID Message Text Explanation Specify the revised installation information settings file and then retry the operation. KAPL09232-W The composition of the definition Details of the installation information A key, key value, or equal sign (=) settings file is invalid. Error is missing. Code = aa...aa,bb...bb, line = aa...aa: Error number (decimal cc...cc number) that specifies the executed processing bb...bb: Return value (decimal number) of the executed processing cc...
Message ID Message Text Explanation A file other than a normal one (for example, a directory file or a special file.) is specified. aa...aa: Specified file name (character string) Action Specify the correct file, and then retry the operation. KAPL09239-I The system will now restart. Details The host will restart because restart was specified in the installation information settings file. Action None. KAPL09240-I There is no license key file. File Details name = aa...
Message ID Message Text KAPL09268-W You do not have read permission for the file. File name = aa...aa Explanation Details aa...aa: / etc/.DynamicLinkManager/ Path00, /etc/.HBaseAgent/ Path00 Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3.
Message ID Message Text Explanation An upgrade installation or reinstallation cannot be performed on an already installed HDLM or SP. When installing HDLM: First remove the installed HDLM or SP, and then perform a new installation. When installing a SP: Obtain, and then install an SP or corrected version that can be applied to the installed version of HDLM. KAPL09509-E Service Pack aa...aa cannot be installed. The same version has already been installed.
Message ID Message Text Explanation DVD-mount-point/HDLM_Linux/ installhdlm KAPL09602-E The installation will now stop because a file or directory is missing. Confirm that the file or directory (aa...aa) exists. Details aa...aa: Name of the missing file or directory Action If an installation is performed from the DVD-ROM, confirm that the DVD-ROM is not damaged. If an installation is performed by using files copied from the DVDROM, re-copy all of the DVD-ROM files.
KAPL10001 to KAPL11000 Message ID Message Text KAPL10001-W No parameter has been specified. Explanation Details No directory to which the collected information will be output has been specified. Action Check the parameters of the DLMgetras utility for collecting HDLM error information, and then retry. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL10002-W Too many parameters have been specified.
Message ID Message Text Explanation retry. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. 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. The number of parameters is insufficient. Action Check the parameters of the DLMgetras utility for collecting HDLM error information, and then retry.
Message ID Message Text Explanation or the creation of a subdirectory of the specified directory failed. aa...aa: first parameter Action Check the following. a. Check whether you have access permission for the specified directory. b. Check whether the specified directory name is correct. c. Check that the disk has sufficient unused capacity. Details KAPL10009-W The specified directory already exists. Do you want to overwrite The specified directory already it? [y/n]: exists.
Message ID Message Text Explanation 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.
Message ID Message Text Explanation KAPL10013-W You lack read permission for the Details specified file. Line = aa...aa, You lack read permission for the Value = bb...bb specified file in the file for defining information to be collected. aa...aa: Line number of the file for defining information to be collected (decimal number) bb...
Message ID Message Text KAPL10015-W The file format is invalid. Value = aa...aa Explanation Details The file format is invalid. The file format in the file for defining information to be collected is not a text file. aa...aa: Third parameter Action After the DLMgetras utility for collecting HDLM error information terminates, check whether the file for defining the information to be collected is a text file. The file is shown in the message.
Message ID Message Text Explanation None. KAPL10021-I Details Processing terminated before completion because a signal was The process has been terminated received. by an operation such as Ctrl + c. Action The utility for collecting HDLM error information terminated before completion. If the directory is unnecessary, delete directory. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3.
Message ID Message Text Explanation Re-execute the DLMgetras utility. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL10033-W The file does not exist. Filename Details = aa...aa The file to collect does not exist. aa...aa: Name of file to collect Action None. KAPL10034-E The file could not be copied. Filename = aa...aa, Details = bb...bb Details Execution of the cp command failed. aa...aa: Name of the file you tried to copy bb...
Message ID Message Text Explanation 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. KAPL10037-W The file does not exist or does not have executable permissions. Filename = aa...aa Details There is no output file, or the user does not have execution permission. aa...aa: file name Action Make sure the specified file exists and the user has execution permission.
Message ID Message Text Explanation Utility for Managing the HDLM Configuration on page 7-22. KAPL10305-E A special file could not be created. Filename = aa...aa. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company. Details A logical device file for an HDLM device cannot be created. aa...
Message ID Message Text KAPL10309-W The HDLM management-target disk does not exist. Check the system configuration. Explanation Details The HDLM management-target device does not exist. Action Check the system configuration. KAPL10312-I HDLM has created an HDLM device special file. Device = aa...aa Details A logical device file for an HDLM device has been created. aa...aa: Logical device file name of HDLM device Action None. KAPL10313-I HDLM has deleted an HDLM device special file. Device = aa...
Message ID Message Text then contact your vendor or maintenance company. Explanation aa...aa: Line number in which the error occurred (decimal number) bb...bb: Error number (errno) (decimal number) cc...cc: Detailed information (optional) Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Message ID Message Text KAPL10321-W The specified HDLM device is invalid. Device = aa...aa. Specify a valid logical device file name of an HDLM device, and then execute the dlmcfgmgr utility. Explanation Details Executing the HDLM-configuration definition utility (dlmcfgmgr) failed because the logical device file name of the HDLM device was incorrect. aa...
Message ID KAPL10324-I Message Text The device configuration of the system has changed. Device = aa...aa Explanation Details The device composition of a system to a device (aa...aa) was changed. aa...aa: HDLM device name Action None. KAPL10325-E A regular expression cannot be established. The files will not be deleted. Errno = aa...aa. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company.
Message ID KAPL10328-E Message Text Explanation The entered value is invalid. The Details HDLM-configuration definition An invalid value was entered 3 or utility processing will now stop. more times for the message Execute the HDLM-configuration confirming the execution of the definition utility again. HDLM-configuration definition utility (dlmcfgmgr). Processing is interrupted. Action Re-execute the dlmcfgmgr utility.
Message ID KAPL10331-E Message Text The registering of the block device driver for HDLM failed. Errno = aa...aa. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company. Explanation Details An attempt to register the block device driver of HDLM has failed. aa...
Message ID KAPL10334-E Message Text Ioctl aa...aa failed with errno = bb...bb. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company. Explanation Details An attempt to issue an IOCTL call has failed. aa...aa: IOCTL name bb...bb: Error number (decimal number) Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Message ID Message Text Explanation None. KAPL10338-W A directory cannot be deleted. Directory = aa...aa. Manually delete the directory aa...aa Details An attempt to delete a directory has failed. aa...aa: Directory name Action Delete the directory shown in Directory. KAPL10339-I This operation will change the configuration of HDLM devices. Do you want to continue? [y/n]: Details This message checks whether you want to change the configuration definition of an HDLM device. Action Enter y to continue.
Message ID Message Text Explanation aa...aa: Logical device file name of HDLM device Action None. For details on the dlmcfgmgr utility, see dlmcfgmgr Utility for Managing the HDLM Configuration on page 7-22. KAPL10344-I HDLM has detected and Details registered a new path to an By executing the HDLMalready registered HDLM device. configuration definition utility HDLM device = aa...aa, Device (dlmcfgmgr), a newly detected = bb...bb (Host: cc...cc path has been added to the Channel: 0 ID: dd...
Message ID KAPL10346-I Message Text HDLM has unregistered an existing HDLM device. HDLM device = aa...aa Explanation Details By executing the HDLMconfiguration definition utility (dlmcfgmgr), the registered HDLM device has been unregistered. aa...aa: Logical device file name of HDLM device Action None. For details on the dlmcfgmgr utility, see dlmcfgmgr Utility for Managing the HDLM Configuration on page 7-22. KAPL10347-I The HDLM device is no longer under management. HDLM device = aa...
Message ID Message Text Explanation Utility for Managing the HDLM Configuration on page 7-22. KAPL10350-E The HDLM driver(s) is not loaded. Refer to the Messages section of the HDLM User's Guide for instructions to correct this problem. Details An attempt to execute the HDLMconfiguration definition utility (dlmcfgmgr) failed because the HDLM driver was not loaded. Action Carry out the following process: a.
Message ID Message Text Explanation device being mounted, and then re-execute the dlmcfgmgr utility. For details on the dlmcfgmgr utility, see dlmcfgmgr Utility for Managing the HDLM Configuration on page 7-22. KAPL10353-W An error occurred while a backup of the HDLM files was being acquired. File name = aa...aa. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company. Details An error occurred during acquisition of the HDLM file (aa...aa) backup.
Message ID Message Text Explanation see dlmcfgmgr Utility for Managing the HDLM Configuration on page 7-22. KAPL10356-E An unused major number could Details not be released. Major number An attempt to release an intact = aa...aa. Refer to the Messages major number (aa...aa) has failed. section of the HDLM User's aa...aa: Major number (decimal Guide for instructions to correct number) this problem. Action Restart the host.
Message ID Message Text Explanation Check that the logical device file name of the HDLM device is correct, and then re-execute the dlmcfgmgr utility. For details on the dlmcfgmgr utility, see dlmcfgmgr Utility for Managing the HDLM Configuration on page 7-22. KAPL10359-E Multiple instances of the HDLMconfiguration definition utility cannot be executed concurrently. Wait until the running dlmcfgmgr utility ends, and then try the dlmcfgmgr utility again.
Message ID Message Text Explanation bb...bb: SCSI device name cc...cc: Host ID (decimal number) Channel: Channel ID (fixed value: 0) (decimal number) dd...dd: Target ID (decimal number) ee...ee: LUN (decimal number) Action None. For details on the dlmcfgmgr utility, see dlmcfgmgr Utility for Managing the HDLM Configuration on page 7-22. KAPL10362-W HDLM has detected an active path that cannot be deleted. HDLM device = aa...aa, Device = bb...bb (Host: cc...cc Channel: 0 ID: dd...dd Lun: ee...ee).
Message ID Message Text Explanation company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL10364-I The LDEV for an HDLM device has changed. HDLM will now change the configuration. HDLM device = aa...aa Details The configuration has been modified because an LDEV corresponding to an HDLM device was changed. aa...aa: Logical device file name of an HDLM device Action None.
Message ID Message Text Explanation aa...aa: Logical device file name for the HDLM management-target device Action None. KAPL10643-W A necessary parameter is not specified. Details A parameter is not specified for the dlmpr utility. Action Execute the dlmpr -h utility to check the parameter, and then retry execution. For details on the dlmpr utility, see dlmpr Utility for Clearing HDLM Persistent Reservation on page 7-35.
Message ID Message Text Explanation dlmpr Utility for Clearing HDLM Persistent Reservation on page 7-35. KAPL10648-E An internal error occurred in the Details dlmpr utility. Error Code = An error not caused by the user aa...aa has occurred in the dlmpr utility. aa...aa: Error number (character string) Action When the error code is 1: Make sure that there is sufficient memory. When the error code is 2: Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Message ID KAPL10652-E Message Text Explanation The entered value is invalid. The Details operation stops. An invalid response was sent three times consecutively to a request. Action Re-execute the dlmpr utility. For details on the dlmpr utility, see dlmpr Utility for Clearing HDLM Persistent Reservation on page 7-35. 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.
Message ID KAPL10923-E Message Text The HDLM file is invalid. File name = aa...aa. Reinstall the HDLM software. Explanation Details A file necessary for processing HDLM cannot be found. Alternatively, the content of a file is invalid. aa...aa: Name of file where error was detected. Action Reinstall an HDLM. KAPL10934-W A file could not be opened. File name = /etc/opt/ DynamicLinkManager/ hdlm_utillog.conf, Errno = aa...aa.
Message ID Message Text Explanation For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL10936-W The file format is invalid. File name = /etc/opt/ DynamicLinkManager/ hdlm_utillog.conf. Refer to the Messages section of the HDLM User's Guide for instructions to correct this problem. Details The format of the settings file for the HDLM utility log (/etc/opt/ DynamicLinkManager/ hdlm_utillog.conf) is invalid.
Message ID Message Text KAPL10939-W An error occurred during processing to read a file. File name = aa...aa Explanation Details An error occurred during processing to read a file. aa...aa: File name Action Follow the instructions in the message that was output before this message. KAPL10940-W The maximum wait time has been reached. Maximum wait time = aa...aa, Checking interval = bb...bb Details The maximum wait time has been reached. aa...aa: Maximum wait time bb...
Message ID Message Text Explanation Action Confirm that the configuration for HDLM devices is correct. If it is not correct, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL10943-W An error occurred during processing to read a file in the (aa...aa) function.
Message ID Message Text Explanation ¢ For FC-SAN: iscsi_boot=n ¢ For IP-SAN: iscsi_boot=y KAPL10949-E A necessary file was not found. File name = aa...aa Details A necessary file was not found. aa...aa: File name Action Reinstall an HDLM. KAPL10950-E An error occurred during creation of an HDLM temporary file. File name = aa...aa. Refer to the Messages section of the HDLM User's Guide for instructions to correct this problem. Details An error occurred during creation of an HDLM temporary file.
KAPL11001 to KAPL12000 Message ID KAPL11901-I Message Text aa...aa has started. Explanation Details The operation has started on the host. aa...
Message ID Message Text Explanation ¢ Get Option Information ¢ Set Option Information ¢ Clear Data ¢ Get HDLM Driver Status ¢ ¢ Get HDLM Manager Status Get HDLM Alert Driver Status ¢ Online ¢ Offline ¢ Get SNMP Trap Information ¢ Set SNMP Trap Information ¢ ¢ Set LU Load Balance Get Path Status Log Information ¢ Get Local Time ¢ Add Path Information ¢ Delete Path Information ¢ Set Storage Identification Information Action None. KAPL11904-E aa...aa has completed abnormally.
Message ID Message Text Explanation ¢ Set Storage Identification Information bb...bb: Error status returned from the API (character string) Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if you have a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL11905-E An unexpected error occurred.
Message ID Message Text Explanation Action None. KAPL12001 to KAPL13000 Message ID KAPL12035-E Message Text Explanation The version of the kernel Details supported by the installed The version of the kernel to which HDLM does not match the installed HDLM has adjusted and the currently running kernel kernel that is running now is not version. corresponding. There is a possibility of installing the package of the kernel after installing HDLM.
Message ID Message Text Explanation /etc/dracut.conf.d/hdlmdracut.conf If the file name displayed in the message is another file name The OS (kernel) or the HBA driver may not be installed correctly. Confirm sure the existence of the files. For dlmmkinitrd: If the file name displayed in the message is the file name specified in the fstab parameter of the Boot Disk Support Utility (dlmmkinitrd) Check the specified file name, specify the file name of the existing fstab file, and then reexecute the utility.
Message ID Message Text Explanation • /lib/modules/kernelversion/kernel/drivers/ DynamicLinkManager/ sddlmadrv.ko If the file name displayed in the message is another file name The OS (kernel) or the HBA driver may not be installed correctly. Confirm sure the existence of the files. KAPL12305-I The utility for supporting Action the boot disk was stopped Retry the dlmmkinitrd utility for by the user. supporting the boot disk.
Message ID Message Text Explanation None. KAPL12316-I The SCSI root partition is aa...aa Details aa...aa: The SCSI device partition on which the root is mounted Action None. Action KAPL12318-W For Red Hat Enterprise Linux AS4/ES4 or Red Hat Confirm the parameters specified when Enterprise Linux 5: the dlmmkinitrd utility for supporting Usage: /opt/ the boot disk was executed, and then DynamicLinkManager/ retry.
Message ID Message Text Explanation device, or specify settings so that HDLM manages the device that is listed next to the root partition specified in the /etc/ fstab file. KAPL12322-I Execution of linuxrc started. Details Execution of linuxrc started. Action None. KAPL12323-I The insertion of the module was started. Module name = aa...aa Details The insertion of the module was started. aa...aa: The name of the module being inserted Action None. KAPL12324-E The module could not be inserted.
Message ID Message Text Explanation Confirm that there is enough unused capacity and that the user has write permission in the root directory (/). dlmcfgmgr: • Confirm that the version of the OS has not changed since you made the initial ramdisk image file. • Take action according to the contents output in the log of the dlmcfgmgr utility. • Confirm that the user has write permission in the root directory (/). dlnkmgr: • Confirm that HDLM has been configured.
Message ID Message Text Explanation Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. For dlmmkinitrd: Perform the following confirmation corresponding to the output command, and then retry.
Message ID Message Text Explanation • Confirm that the user has write permission in the root directory (/). gzip: Confirm that that the unused capacity is sufficient at the creation destination of the initial ramdisk image file. mke2fs or touch: Confirm that the user has write permission in the root directory (/). mkdir: Confirm that there is enough unused capacity and that the user has write permission in the following directory: • /etc/opt/ DynamicLinkManager. • /opt/DynamicLinkManager.
Message ID Message Text Explanation Collecting HDLM Error Information on page 7-3. KAPL12327-E An invalid entry is registered in the file. File name = aa...aa Details aa...aa: The name of the file containing the invalid entry Action For dracut command: Take the following actions depending on the file name output, and then reexecute the dracut command. In the case of /etc/lvm/lvm.
Message ID Message Text Explanation Install an HBA driver, which is supported as a boot disk by HDLM. Or use an HBA, which is supported as a boot disk by HDLM. In the case of /etc/sysconfig/ kernel file The OS environment is incorrect. Add the names of the HBA drivers that have to be included in the initial RAM disk image into the INITRD_MODULES= line of the / etc/sysconfig/kernel file. KAPL12328-I Execution of linuxrc completed. Details Execution of linuxrc completed. Action None.
Message ID Message Text Explanation For the details of the parameter, see dlmmkinitrd Utility for Supporting a Boot Disk on page 7-33. If the problem is not solved, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3.
Message ID Message Text Explanation the root partition setting in the /etc/ fstab file and then retry the operation. KAPL12335-E A file system that HDLM can support as a boot disk was not found in the file. File name = aa...aa Details aa...
Message ID Message Text Explanation HDLM devices management targets that are not management targets before using them again. If one or more associations are not correct, execute the DLMgetras utility for collecting error information, and then contact your HDLM vendor or your maintenance company, if you have an HDLM maintenance contract. KAPL12341-I Execution of bootup script Action started. None. KAPL12342-I Execution of bootup script Action completed. None.
Message ID Message Text Explanation maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL12351-I The collection of files for HDLM started. Details The collection of files for HDLM started. Action None. KAPL12352-I The collection of files for HDLM completed. Details The collection of files for HDLM completed. Action None.
Message ID Message Text utility to collect error information, and then contact your vendor or maintenance company. Explanation cc...cc: Error number (errno) (decimal number) Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3.
Message ID Message Text Explanation b. /etc/opt/ DynamicLinkManager/.dlmfdrv.unc onf c. /etc/opt/DynamicLinkManager/ dlmchname.conf bb...bb: Internal code (decimal number) cc...cc: Error number (errno) (decimal number) Action Verify that the root directory (/) has enough unused capacity. If it has enough unused capacity, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Message ID Message Text DLMgetras utility to collect error information, and then contact your vendor or maintenance company. Explanation Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL12371-E A file could not be opened. File name = aa...aa, Code = bb...
Message ID Message Text Explanation aa...aa: Incorrect storage system serial number and LU number is number and LU number incorrect in the device name change definition Action file. Incorrect value = If the value entered for the storage aa...aa system serial number and LU number is incorrect, the incorrect value is displayed. Correct the number, and then re-execute the utility for changing HDLM device names (dlmchname). KAPL12377-I The utility for changing HDLM device names started: aa...aa Details aa.
Message ID KAPL12386-E Message Text Explanation An internal error occurred Details in the utility for changing aa...aa: File name HDLM device names. File bb...bb: Internal code (decimal number) name = aa...aa, Code = bb...bb, Errno = cc...cc. cc...cc: Error number (errno) (decimal Execute the DLMgetras number) utility to collect error Action information, and then Execute the DLMgetras utility for contact your vendor or collecting HDLM error information, and maintenance company.
Message ID Message Text dlmchname.conf file. Duplicated entry = aa...aa Explanation Review the entries in the device name change definition file (dlmchname.conf) and re-execute the utility for changing HDLM device names (dlmchname). For details on this utility, see dlmchname HDLM Device Name Replacement Utility on page 7-31. KAPL12393-E Details The file format of the device name definition file aa...aa: The incorrect line in the device is invalid. Incorrect line = name definition file (dlmchname.
Message ID Message Text Explanation /etc/opt/ DynamicLinkManager/.dlm_modules.co nf.lock Action KAPL12553-W Usage: /opt/ DynamicLinkManager/bin/ Refer to dlmsetopt Utility for Setting dlmsetopt {-r retrycount | HDLM Driver Options on page 7-37, and -inqt InquiryTimeout | then specifying the correct argument. inqr InquiryRetry | -prsup Then, re-execute the dlmsetopt utility. ReserveStatus | -h} KAPL12554-I KAPL12555-I The utility for setting HDLM driver option has started.
Message ID Message Text Explanation specify the correct argument, and then re-execute the dlmsetopt utility. KAPL12561-E An invalid option was specified. Option = aa...aa Details aa...aa: Option Action Refer to dlmsetopt Utility for Setting HDLM Driver Options on page 7-37, specify the correct argument, and then re-execute the dlmsetopt utility. KAPL12562-E A necessary file or directory was not found. File or directory name = aa...aa Details aa...
Message ID Message Text Explanation processes, and then re-execute the dlmsetopt utility. KAPL12566-E The utility for setting HDLM driver option was executed and ended abnormally last time. Action Compare the contents of the /etc/ modprobe.conf file and the /etc/opt/ DynamicLinkManager/DLMSETOPT/ modprobe.conf file. According to the result, perform the following procedures: The /etc/opt/DynamicLinkManager/ DLMSETOPT/modprobe.
Message ID Message Text Explanation A file necessary for processing HDLM cannot be found. Alternatively, the content of a file is invalid. aa...aa: Name of file where error was detected. Action Reinstall an HDLM. KAPL12801-E The version of the kernel Details supported by the installed The version of the kernel to which HDLM does not match the installed HDLM has adjusted and the currently running kernel kernel that is running now is not version. corresponding.
Message ID Message Text Explanation installing the package of the kernel after installing HDLM. Action Install HDLM that adjusts to the kernel that is running now. KAPL12902-E The HDLM file is invalid. File name = aa...aa Details A file necessary for processing HDLM cannot be found. Alternatively, the content of a file is invalid. aa...aa: Name of file where error was detected. Action Reinstall an HDLM. KAPL13001 to KAPL14000 Message ID Message Text KAPL13204-W The file does not exist.
Message ID Message Text Explanation Reinstall HDLM. KAPL13207-E The directory does not exist. Directory name = aa...aa Details aa...aa: /HDLM installation directory, /HBsA installation directory Action Reinstall HDLM. KAPL13401-E No parameter has been specified. Details No parameter (directory to which collected information is output) has been specified. Action Check the parameters of the utility for collecting HDLM install error information, and then retry.
Message ID Message Text Explanation existing file. Enter n or press any other key to terminate the utility for collecting HDLM install error information without executing it. KAPL13405-E The root directory has been specified in the first parameter. Details A root "/" cannot be specified in a directory to which collected information is output. Action Check the parameters of the utility for collecting HDLM install error information, and then retry.
Message ID KAPL13410-I Message Text A user terminated the utility for collecting HDLM install error information. Explanation Details The processing of the utility for collecting HDLM install error information has been terminated as n was sent to a confirmation. Action None. KAPL13411-W The entered value is invalid. Continue operation? [y/n]: Details A value other than y or n has been entered for a [y/n] request. Enter y or n. Action Enter y or n. KAPL13412-E The entered value is invalid.
Message ID Message Text Explanation 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 your maintenance company if you have a maintenance contract for HDLM. KAPL13416-E An attempt to compress the install error information failed. Details = aa...aa Details Execution of the gzip command failed. aa...
Message ID KAPL13504-I Message Text A symbolic link has been modified. Symbolic link name = aa...aa Explanation Details aa...aa: Name of the modified symbolic link Action None. KAPL13505-E A system script cannot be modified. File name = aa...aa Details aa...aa: File name of the system script that cannot be modified Action Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM. KAPL13506-E Modification of a system script has failed. File name = aa...
Message ID Message Text Explanation KAPL13510-E Action Multiple instances of the utility for update system scripts cannot Check the execution result of the be executed concurrently. executing dlmupdatesysinit utility. Re-execute the dlmupdatesysinit utility if necessary. Refer to dlmupdatesysinit Utility for Updating System Scripts on page 7-41.
Message ID Message Text Explanation Updating System Scripts on page 7-41. KAPL13516-E A file required by HDLM not found. File name = aa...aa Details aa...aa: file name Action Check for and, if necessary, restore the file indicated in the message. Next, execute the dlmupdatesysinit utility. Refer to dlmupdatesysinit Utility for Updating System Scripts on page 7-41. KAPL13517-E A directory required by HDLM not found. Directory name = aa...aa Details aa...
Message ID Message Text Explanation Remove the error cause described in the message output by the command indicated in the message KAPL134521-E. Next, reexecute the dlmupdatesysinit utility. Refer to dlmupdatesysinit Utility for Updating System Scripts on page 7-41. KAPL13522-E The HDLM file is invalid. File name = aa...aa Details A file necessary for processing dlmupdatesysinit utility cannot be found. Alternatively, the content of a file is invalid. aa...aa: Name of file where error was detected.
Message ID Message Text KAPL13604-W An error occurred during processing to read the audit log configuration file. Explanation 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.
Message ID KAPL13907-I Message Text aa...aa completed successfully. Explanation Details aa...aa: Alert driver's loading, The process related to Alert driver, Filter driver's loading, dlmcfgmgr, or DLMManager Action None. KAPL13908-W An error occurred in processing of module. Module = aa...aa Details In processing of the utility for HDLM start, an error occurred at Module aa...aa. aa...aa: Module name at which the error occurred. Action If aa...
Message ID Message Text Explanation executable permissions. Reinstall an HDLM. When the error code is 3: /etc/init.d/DLMManager file does not exist or does not have executable permissions. Reinstall an HDLM. KAPL13912-E An invalid parameter was specified. Parameter = aa...aa Details aa...aa: Specified parameter Action Re-execute the utility for HDLM start if necessary. Refer to dlmstart Utility for Starting HDLM on page 7-40. KAPL13913-E A command has failed. Command = aa...aa, details = bb...
Message ID Explanation An attempt to display the registered value of ReserveKey has failed. Command Line = aa...aa Details KAPL15010-W The HDLM utility was executed by the user who does not have the authority. Command Line = aa...aa Details KAPL15002-E aa...aa: Name of the utility that the user executed aa...aa: Name of the utility that the user executed KAPL15040-I Details Creation of the HDLM configuration file and addition of aa...aa: Name of the utility that HDLM devices succeeded.
Message ID Message Text Explanation has failed. Command Line = aa...aa KAPL15050-I An initial RAM disk image file for Details using an HDLM device as a boot aa...aa: Name of the utility that disk was successfully created. the user executed Command Line = aa...aa KAPL15051-E An attempt to create an initial RAM disk image file for using an HDLM device as a boot disk has failed. Command Line = aa...aa Details The number of retries to allocate memory was successfully set. Command Line = aa...
Message ID KAPL15062-I KAPL15063-E KAPL15064-I Message Text Explanation Processing to start HDLM was successful. Command Line = aa...aa Details Processing to start HDLM failed. Command Line = aa...aa Details ReserveKey was cleared successfully on aa...aa SCSI device(s) and failed on bb...bb SCSI device(s). Command Line = cc...cc Details aa...aa: Name of the utility that the user executed aa...aa: Name of the utility that the user executed aa...
Message ID KAPL15106-E KAPL15107-I KAPL15108-E KAPL15109-I KAPL15110-E Message Text Setting up the operating environment failed. Command Line = aa...aa Details Program information was successfully displayed. Command Line = aa...aa Details An attempt to display program information has failed. Command Line = aa...aa Details Information about HDLMmanagement targets was successfully displayed. Command Line = aa...aa Details An attempt to display information about HDLMmanagement targets has failed.
Message ID Message Text KAPL15120-W Deletion of path(s) failed. Command Line = aa...aa Explanation Details aa...aa: Command that the user executed KAPL15301-I Details Creation of the device name change definition file succeeded. aa...aa: Command that the user Command Line = aa...aa executed KAPL15302-E Creation of the device name change definition file failed. Command Line = aa...aa Details Processing to change the HDLM device name succeeded. Command Line = aa...
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. Return Code 1002 Explanation Details There is no path on which the operation can be performed. Action Refresh the host information, check the path status, and then perform the operation again. 1003 Details No path was detected.
Return Code Explanation To bring the path online, execute the dlmcfgmgr utility (dlmcfgmgr -r). 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. 1019 Details An error occurred during HDLM internal processing.
Return Code Explanation Refresh the host information, check the path status, and then perform the operation again. 1027 Details The error monitoring interval and the number of times that the error needs to occur are conflicting with the automatic failback-checking interval. Action Set the intermittent error-monitoring interval to a value that is equal to or greater than (automatic-failback-checkinginterval x number-of-times-error-is-to-occur-forintermittent-error-monitoring).
Return Code Explanation HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. 1037 Details A parameter is invalid. Action Refresh the host information, and then perform the operation again. If the same error occurs again, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or maintenance company if you have a maintenance contract for HDLM.
A Notes on Linux Commands and Files This section provides notes on Linux commands and files.
Notes on the /proc/partitions File The HDLM device and each partition of the HDLM device that is recognized by Linux and can be used are recorded in the /proc/partitions file. The / proc/partitions file records the I/O statistics per device; however, it does not record the I/O statistics of the HDLM device. The I/O statistics are always 0. If you are going to obtain statistics about an HDLM device, perform calculations by using the value recorded for the SCSI device that corresponds to the HDLM device.
Table A-1 Examples of Linux Command Execution Times Time Linux commands Example 1#1 Before HDLM installation After HDLM installation Example 2#2 Before HDLM installation After HDLM installation lvmdiskscan 6.1 sec 19.6 sec 3.8 sec 10.6 sec pvscan 2.6 sec 12.6 sec 1.5 sec 5.2 sec #1 CPU: Pentium III 1.4 GHz x 2 Memory: 1 GB Connection between host and storage systems: 64 LU x 2 paths (total 128 paths) #2 CPU: Xeon 2.
Notes on the mkfs Command If you are going to create a file system for an HDLM device, specify the name of a logical device file of the HDLM device for the mkfs command. However, if a file system is created for a SCSI device that is already in use, the applicable HDLM device will be created with a file system even without creating a new file system by using the mkfs command.
Notes on the fdisk and parted Commands When creating partitions on an HDLM device, only use the fdisk command or the parted command. If partitions have been created on an HDLM device using the fdisk or parted command, some of the partitions created by the fdisk command might not be visible to the parted command. Likewise, some of the partitions created by the parted command might not be visible to the fdisk command.
A-6 Notes on Linux Commands and Files Hitachi Dynamic Link Manager User Guide for Linux®
B Troubleshooting Products That Use the Weak-Modules Script This section explains how to deal with errors that are caused by installing or removing products that use the weak-modules script.
Overview If you use an HDLM device as a boot disk in Red Hat Enterprise Linux 5 and attempt to install or remove a product that uses the weak-modules script, the following message might be output, and installation or removal of that product might fail: grubby fatal error: unable to find a suitable template Therefore, when using an HDLM device as a book disk in Red Hat Enterprise Linux 5, execute the following commands before installing or removing a product that uses the weak-modules script: Before install
proc /dev/sddlmaa3 # /proc swap proc swap defaults defaults 0 0 0 0 Example when the boot loader is grub and LVM is used: # cat /etc/fstab /dev/VolGroup00/LogVol00 /dev/VolGroup00/LogVol02 /dev/VolGroup00/LogVol04 /dev/VolGroup00/LogVol03 /dev/sda1 /dev/sddlmaa1 tmpfs devpts sysfs proc /dev/VolGroup00/LogVol01 # 2.
Perform installation according to the documentation for relevant products (packages). 4. Back up the currently used initial RAM disk image file for HDLM. 5. Execute the dlmmkinitrd utility (utility for supporting a boot disk) with the -f parameter specified to create an initial RAM disk image file for HDLM. For the parameter, specify the initial RAM disk image file name that is currently used. 6. Delete the kernel parameter you added in step 2 from the boot loader configuration file.
The underlined portion is the device that indicates the root directory (/).
Removing Products That Use the Weak-Modules Script To remove a product that uses the weak-modules script: 1. Add a parameter to the boot loader configuration file. Perform steps 1 and 2 in Installing Products That Use the Weak-Modules Script on page B-2. 2. Remove other products that use the weak-modules script. Perform removal according to the documentation for relevant products (packages). 3.
C Functional Differences Between Versions of HDLM This section explains the functional differences between newer and older versions of HDLM. □ Functional Differences Between Version 7.6 and Versions Earlier Than 7.6 □ Functional Differences Between Version 7.2 and Versions Earlier Than 7.2 □ Functional Differences Between Version 6.2.1 and Versions Earlier Than 6.2.1 □ Functional Differences Between Version 6.1 and Versions Earlier Than 6.1 □ Functional Differences Between Version 6.
□ Functional Differences Between Version 5.7.0-01 or Later and Versions Earlier Than 5.7.0-01 □ Functional Differences Between Version 5.7 or Later and Versions Earlier Than 5.7 □ Functional Differences Between Version 5.6.3 or Later and Versions Earlier Than 5.6.3 □ Functional Differences Between Version 5.4 or Later and Versions Earlier Than 5.
Functional Differences Between Version 7.6 and Versions Earlier Than 7.6 For FC-SAN environments, the number of paths in the Offline(E) status no longer increases if the server is restarted when no system (path) configuration has been changed and no path error has occurred. For IP-SAN environments, there are no functional differences. Functional Differences Between Version 7.2 and Versions Earlier Than 7.
• In a new installation of HDLM, the default value for the automatic failback function has been changed from off to on. Functional Differences Between Version 5.9.4 or Later and Versions Earlier Than 5.9.4 • The maximum number of LUs for one port for one storage that was guaranteed in HDLM for each storage system is now guaranteed for each OS. • The maximum number of LUs guaranteed in HDLM has been changed to 512. Therefore, the naming rules for HDLM logical device files have also been changed.
Functional Differences Between Version 5.9 or Later and Versions Earlier Than 5.9 The function for operating HDLM from the HDLM GUI or HDLM Web GUI is no longer supported. Functional Differences Between Version 5.8 or Later and Versions Earlier Than 5.8 The following table describes the version of the JRE or JDK required to use the HDLM GUI on a host. Table C-1 JRE/JDK Version Required for HDLM GUI OS Required version of JRE or JDK Earlier than HDLM 5.7.1 HDLM 5.8 or later JRE v1.4.2_08 JRE v1.4.
Functional Differences Between Version 5.7.0-01 or Later and Versions Earlier Than 5.7.0-01 In versions earlier than 5.7.0-01, when an I/O request is sent to a path in the Online(E) status despite all paths being disconnected, the status of the path is changed to Offline(E) and another path is placed in the Online(E) status. In version 5.7.0-01 or later, even if an I/O request is sent to a path in the Online(E) status, the status of the path does not change.
• The permission for the trace log directory /var/opt/hitachi/HNTRLib2/ spool has been changed to 755, and the permission for the log file /var/ opt/hitachi/HNTRLib2/spool/hntr2X.log has been changed to 644. • License keys that worked with versions 04-00, 05-02, and 05-03 are no longer valid with version 5.4.
C-8 Functional Differences Between Versions of HDLM Hitachi Dynamic Link Manager User Guide for Linux®
Acronyms and abbreviations The following acronyms and abbreviations might be used in this guide.
CU Control Unit D DBMS Database Management System Dev Device DMI Desktop Management Interface DNS Domain Name Server DRBD Distributed Replicated Block Device E ELILO Extensible Firmware Interface Linux Loader EM64T Extended Memory 64 Technology EUC Extended UNIX Code EVMS Enterprise Volume Management System ext Extended File System F FC # Fibre Channel A B C D E F G H I J K L M N O P Q R S Acronyms-2 Hitachi Dynamic Link Manager User Guide for Linux® T U V W X Y Z
FC-SP Fibre Channel Security Protocol FO Failover FQDN Fully Qualified Domain Name G GMT Greenwich Mean Time GRUB GRand Unified Bootloader GUI Graphical User Interface H HBA Host Bus Adapter HDev Host Device HLU Host Logical Unit HTTP Hypertext Transfer Protocol I I/O Input/Output IA32 Intel Architecture 32 # A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Acronyms-3 Hitachi Dynamic Link Manager User Guide for Linux®
IDE Integrated Drive Electronics IP Internet Protocol IPC Inter Process Communication IPF Itanium® Processor Family IRQ Interrupt ReQuest iSCSI Internet Small Computer System Interface K KVM Kernel-based Virtual Machine L LAN Local Area Network LDAP Lightweight Directory Access Protocol LDEV Logical Device LILO Linux Loader LU Logical Unit LUN Logical Unit Number # A B C D E F G H I J K L M N O P Q R S Acronyms-4 Hitachi Dynamic Link Manager User Guide for Linux® T U V W X Y
LVM Logical Volume Manager M md Multiple Devices N NAS Network Attached Storage NIC Network Interface Card NTP Network Time Protocol O OS Operating System P P Port PCI Peripheral Component Interconnect R RADIUS Remote Authentication Dial in User Service # A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Acronyms-5 Hitachi Dynamic Link Manager User Guide for Linux®
S SAN Storage Area Network SCSI Small Computer System Interface SLPR Storage Logical Partition SMTP Simple Mail Transfer Protocol SNMP Simple Network Management Protocol SP Service Pack SSL Secure Sockets Layer SVP Service Processor U UUID Universally Unique Identifier V VG Volume Group W WWN World Wide Name # A B C D E F G H I J K L M N O P Q R S Acronyms-6 Hitachi Dynamic Link Manager User Guide for Linux® T U V W X Y Z
Glossary This glossary explains the terms used in this manual. A automatic failback A function for checking the status of paths at regular intervals, and automatically placing the status of a path recovered from an error into the Online status. If a path with an Offline(E) or Online(E) status recovers from an error, an automatic failback will place the path Online.
CLPR(Cache Logical Partition) A function supported by the Hitachi USP series, Universal Storage Platform V/VM series, Virtual Storage Platform series, Hitachi AMS2000/AMS/WMS/SMS series, HUS100 series, and HUS VM for logically splitting up a cache. This function can split up a cache into parity groups in the storage system, so that other parity groups do not affect the cache performance.
F failback A function for placing the status of a path recovered from an error into the Online status, and then switching the access path to the path that was just recovered. failover A function for switching to another normal path if there is an error in the current access path, thereby enabling the system to continue to operate. FC-SAN (Fibre Channel - Storage Area Network) A SAN using Fibre Channel.
host device name A name assigned to a host device. A name of the logical device file for an HDLM device is assigned to a host device name. host LU An LU that a host recognizes. The actual HDev entity is a Dev in the storage system. Each host LU has a host LU number. (See also: LU, host LU number, host device) host LU number A number assigned to a host LU. The host LU number is part of a path name. (See also: host LU, path name) hypervisor Software that enables host virtualization.
- The The The The The Extended Round Robin algorithm Least I/Os algorithm Extended Least I/Os algorithm Least Blocks algorithm Extended Least Blocks algorithm logical device file A device file in the /dev directory. Note that the term logical device here is different from LDEV. LU (Logical Unit) A logical unit that is a logical volume defined in the storage system, and with which the host can perform input or output operations. (See also: host LU) N node A server in a cluster.
owner path A path that passes through an owner controller for an LU in the Thunder 9500V series, or Hitachi AMS/WMS series. A path that passes through a controller other than an owner controller is called a non-owner path. When using the Lightning 9900 series, Lightning 9900V series, Hitachi USP series, Universal Storage Platform V/VM series, Virtual Storage Platform series, Hitachi AMS2000 series#, Hitachi SMS series#, HUS100 series#, or HUS VM, all paths are owner paths.
Q QEMU A virtual emulator available for the entire host system. (See also: KVM) R reservation The reservation function enables a host to declare that it has exclusive rights to use a particular LU, and prevents other hosts from accessing that LU. Access permission for an LU that has been reserved is given only to the host that issued the reservation, so the LU cannot be accessed from multiple paths (coming from multiple hosts) simultaneously. However, because of this, load balancing is not possible.
# A B C D E F G H I J K L M N O P Q R S Glossary-8 Hitachi Dynamic Link Manager User Guide for Linux® T U V W X Y Z
Index Symbols /proc/partitions files A-2 A active host 2-48 add 6-63 adding new LU 4-38 adding path to existing LU 4-40 audit log categories and audit events that HDLM can output 2-38 collecting data 2-36 data format 2-44 automatic failback 2-20, 6-20, Glossary-1 automatic failover 2-19 automatic path switching 2-19 AutoPATH_ID 2-3, Glossary-1 B boot disk environment Glossary-1 when using Oracle Enterprise Linux 4 3-75 when using Oracle Enterprise Linux 5 3-78, 3-79 when using Oracle Unbreakable Enterpri
when using Oracle Enterprise Linux 5 3-76 when using Oracle Unbreakable Enterprise Kernel 5 3-79 when using Oracle Unbreakable Enterprise Kernel 6 3-81 when using Red Hat Enterprise Linux 5 3-42 when using Red Hat Enterprise Linux 6 3-60 when using Red Hat Enterprise Linux AS4/ES4 3-19 when using SUSE LINUX Enterprise Server 10 3-65 coding file that defines information to be collected rules for 7-4 collecting error info.
Error 2-35 Information 2-35 Warning 2-35 error log 2-34 error log collection level 6-17 error log file number of 6-18 error log file size 6-18 error path identifying 5-5 Error-level errors 2-35 ErrorCode 5-2 errors detected by HDLM 2-35 management 2-32 examining message 5-5, 5-6 F failback 2-19, Glossary-3 failover 2-18, Glossary-3 FC-SAN 2-3, 2-4, Glossary-3 fdisk commands A-4, A-5 features of HDLM 1-2 fiber cable replacing 4-31 Fibre Channel switch replacing 4-34 file for defining information to be coll
HDLM installation type new installation of HDLM 3-90 re-installation of HDLM 3-91 upgrade installation of HDLM 3-90 HDLM management-target devices 2-3 HDLM manager 2-9, Glossary-3 starting 4-22 stopping 4-23 HDLM resident processes 4-24 HDLM utility 2-9 HDLM-configuration definition utility 7-22 HDLM-managed device operations on 3-230 Heartbeat canceling settings 3-232 setting 3-208 help 6-4 Hitachi Compute Blade environment when using Red Hat Enterprise Linux 5 3-57, 3-58, 3-60 when using Red Hat Enterpri
knowledge required before you install HDLM 3-91 KVM setting 3-207 KVM (Kernel-based Virtual Machine) Glossary-4 KVM operating environments supported by HDLM 3-88 L LDEV (Logical Device) Glossary-4 Linux commands A-2 Linux commands and files A-1 load balancing 2-14, 6-17, Glossary-4 load balancing algorithms 2-17 log collection level values 6-17 log filter 2-35 logical device file Glossary-5 logical device files for HDLM devices 2-11 logical unit 2-3 logs types collected 2-33 LU 2-4 configuration 2-7 LU (Lo
Operation name operations 6-2 8-3 displaying format 6-4 of the HDLM command 6-2 Oracle Enterprise Linux 4 boot disk environment 3-75 file system 3-75 kernel 3-13 volume manager 3-74 Oracle Enterprise Linux 5 boot disk environment 3-78 cluster software 3-76 file system 3-78 kernel 3-14 volume manager 3-77 Oracle Unbreakable Enterprise Kernel 5 boot disk environment 3-81 cluster software 3-79 file system 3-80 kernel 3-15 volume manager 3-80 Oracle Unbreakable Enterprise Kernel 6 boot disk environment 3-83 c
kernel 3-9 volume manager 3-63 Red Hat Enterprise Linux AS4/ES4 3-101 boot disk environment and Hitachi Compute Blade environment 3-38 cluster software 3-19 file system 3-38 kernel 3-5 volume manager 3-36 related products related products when using Oracle Enterprise Linux 5 3-76 related products when using Oracle Unbreakable Enterprise Kernel 5 3-79 related products when using Oracle Unbreakable Enterprise Kernel 6 3-81 replacing fiber cable 4-31 Fibre Channel switch 4-34 HBA 4-25, 4-27 reservation Glossa
for setting HDLM driver options for starting HDLM 7-40 7-37 for supporting boot disk 7-33 for updating system scripts 7-41 HDLM device name replacement utility 7-31 installing HDLM 7-43 installux.
Hitachi Dynamic Link Manager User Guide for Linux®
Hitachi Data Systems Corporate Headquarters 2845 Lafayette Street Santa Clara, California 95050-2639 U.S.A. www.hds.com Regional Contact Information Americas +1 408 970 1000 info@hds.com Europe, Middle East, and Africa +44 (0)1753 618000 info.emea@hds.com Asia Pacific +852 3189 7900 hds.marketing.apac@hds.
