Hitachi Command Suite Dynamic Link Manager Software User Guide (for Linux(R)) Document Organization Product Version Getting Help Contents MK-92DLM113-18
© 2011 Hitachi, Ltd., Hitachi Data Systems Corporation. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd. (hereinafter referred to as "Hitachi") and Hitachi Data Systems Corporation (hereinafter referred to as "Hitachi Data Systems").
Contents Preface.................................................................................................xiii Intended audience...................................................................................................xiv Product version.......................................................................................................xiv Release notes..........................................................................................................xiv 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...............................................................
File Systems Supported by HDLM...........................................................3-49 Boot Disk Environments Supported by HDLM (If an FC-SAN Is Used)........3-50 Related Products When Using SUSE LINUX Enterprise Server 9..........................3-50 Cluster Software Supported by HDLM.....................................................3-50 Volume Managers Supported by HDLM....................................................3-50 File Systems Supported by HDLM.........................................
Deactivating the Volume Group..............................................................3-85 Setting Up Xen......................................................................................3-86 Performing a Re-installation of HDLM...............................................................3-86 Performing an Upgrade Installation of HDLM....................................................3-91 Unattended Installation of HDLM.....................................................................
Setting Up Load Balancing....................................................................3-185 Setting Up Path Health Checking...........................................................3-186 Setting Up the Automatic Failback Function...........................................3-186 Setting Up Intermittent Error Monitoring...............................................3-187 Setting the Error Log Collection Level....................................................3-188 Setting the Trace Level..............
Notes When Using SUSE LINUX Enterprise Server 9............................................4-5 Notes When Using SUSE LINUX Enterprise Server 10..........................................4-6 Notes When Using SUSE LINUX Enterprise Server 11..........................................4-7 Updating Kernel Packages and Applying OS Update Packages....................................4-8 Environment Where an HDLM Device Is not Used as the Boot Disk.......................
5 Troubleshooting....................................................................................5-1 Information Collected by the DLMgetras Utility for Collecting HDLM Error Information. 5-2 Checking Error Information in Messages................................................................... 5-2 What To Do for a Path Error.................................................................................... 5-3 Examining the Messages....................................................................
To Display Program Information.............................................................6-28 To Display Path Information...................................................................6-28 To Display LU Information......................................................................6-29 To display corresponding information about an HDLM device, SCSI device, and LDEV....................................................................................................
Parameters.....................................................................................................7-48 Log file...........................................................................................................7-48 8 Messages............................................................................................. 8-1 Before Viewing the List of Messages.........................................................................8-3 Format and Meaning of Message IDs.....................
Functional Differences Between Version 5.7.1 or Later and Versions Earlier Than 5.7.1 .............................................................................................................................C-5 Functional Differences Between Version 5.7.0-01 or Later and Versions Earlier Than 5.7.0-01.................................................................................................................C-5 Functional Differences Between Version 5.7 or Later and Versions Earlier Than 5.7.....
Preface This document describes how to use the Hitachi Dynamic Link Manager.
Intended audience This manual is intended for system administrators who use Hitachi Dynamic Link Manager (HDLM) to operate and manage storage systems. The readers of this manual must have a basic knowledge of the following areas: • Linux and its management functionality • Storage system management functionality • Cluster software functionality • Volume management software functionality Product version This document revision applies to HDLM for Linux version 7.2 or later.
Chapter Description HDLM manager. This chapter also describes how to configure an environment to properly operate HDLM, such as changing the HDLM management-target devices that connect paths or replacing the hardware that makes up a path. 5 Troubleshooting on page 5-1 Explains how to troubleshoot a path error, HDLM failure, or any other problems that you might encounter. 6 Command Reference on page 6-1 Describes all the HDLM commands. 7 Utility Reference on page 7-1 Describes the HDLM utilities.
Document conventions Font and symbol conventions are classified as: • General font conventions • Conventions in syntax explanations These conventions are described below. General Font Conventions The following table lists the general font conventions: Font Bold Italics Convention Bold type indicates text on a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels.
Example font or symbol Convention StoreDatabase Code-font characters must be entered exactly as shown. database-name This font style marks a placeholder that indicates where appropriate characters are to be entered in an actual command. SD Bold code-font characters indicate the abbreviation for a command. perm Underlined characters indicate the default value. [ ] Square brackets enclose an item or set of items whose specification is optional.
Logical capacity unit Value 1 KB 1,024 (210) bytes 1 MB 1,024 KB or 1,0242 bytes 1 GB 1,024 MB or 1,0243 bytes 1 TB 1,024 GB or 1,0244 bytes 1 PB 1,024 TB or 1,0245 bytes 1 EB 1,024 PB or 1,0246 bytes Getting help The Hitachi Data Systems customer support staff is available 24 hours a day, seven days a week. If you need technical support, log on to the Hitachi Data Systems Portal for contact information: https://hdssupport.hds.com Comments Please send us your comments on this document: doc.
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.
HDLM Features HDLM features include the following: The ability to distribute a load across multiple paths. This is also known as load balancing. When a host is connected to a storage system via multiple paths, HDLM can distribute the load across all the paths. This prevents one, loaded down path from affecting the processing speed of the entire system. For details on load balancing, see Distributing a Load Using Load Balancing on page 2-13.
1-4 Overview of HDLM Hitachi Dynamic Link Manager User Guide (for Linux(R))
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.
□ Integrated HDLM management using Global Link Manager □ Cluster Support 2-2 HDLM Functions Hitachi Dynamic Link Manager User Guide (for Linux(R))
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.
Figure 2-1 Configuration of an HDLM System When Using an FC-SAN Table 2-1 HDLM System Components When Using an FC-SAN on page 2-4 lists the HDLM system components when using an FC-SAN. Table 2-1 HDLM System Components When Using an FC-SAN Components Description 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.
The cable port on the storage system is called a port (P) on a channel adapter (CHA) used for iSCSI connections. A logical unit (LU) contained in a storage system is the target of input to, or output from, the host. You can divide an LU into multiple areas. Each area after the division is called a Dev. The Dev is equivalent to a partition. A route that connects a host and an LU is called a physical path, and a route that connects a host and a Dev is called a path.
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.
Restrictions on using HDLM in an IP-SAN environment The following restrictions apply when using HDLM in an IP-SAN environment: • Use of HDLM in cluster configurations or boot disk environments is not supported. • The kdump function cannot be used. LU Configuration After you have properly installed HDLM, the LU configuration will change as follows: Before the installation of HDLM: The host recognizes that a SCSI device is connected to each path.
Figure 2-3 LU Configuration Recognized by the Host After HDLM Installation Table 2-3 LU Components on page 2-8 lists the components recognized by the host. Table 2-3 LU Components Components Description HDev A Dev (partition) in an LU that the host recognizes via the HDLM driver. 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 Table 2-4 Functionality of HDLM Programs on page 2-9 lists and describes the functions of these programs.
Program name HDLM manager Functions Provides the HDLM manager, which enables you to: • Configure the HDLM operating environment • Request path health checks and automatic failbacks to be performed • Collect error log data HDLM alert driver Reports the log information collected by the HDLM driver to the HDLM manager. The driver name is sddlmadrv. HDLM driver Controls all the HDLM functions, manages paths, and detects errors.
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. 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. Note that HDLM creates block device files. The system dynamically selects the major number of the block device that this file uses.
function is used. Both figures show examples of I/O operations being issued for the same LU by multiple applications. Figure 2-7 Flow of I/O Data When the Load Balancing Function Is Not Used When the load balancing function is not used, I/O operations converge onto a single path (A). The load on that one path (A) will cause a bottleneck, which might cause problems with system performance.
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).
• The Least I/Os algorithm • The Extended Least I/Os algorithm • The Least Blocks algorithm • The Extended Least Blocks algorithm The above algorithms are divided into two categories, which differ in their processing method. The following describes both of these processing methods: The Round Robin, Least I/Os, and Least Blocks algorithms These algorithms select the path to use each time a certain number of I/ Os are issued.
Table 2-6 Features of the Load Balancing Algorithms Algorithm type • Round Robin# • Least I/Os • Least Blocks • Extended Round Robin • Extended Least I/Os • Extended Least Blocks Algorithm features These types of algorithms are most effective when a lot of discontinuous, non-sequential I/Os are issued.
• An error occurred on the path. • A user executed the HDLM command's offline operation. For details on the offline operation, see offline (Places Paths Offline) on page 6-5. For details on path statuses and the transitions of those statuses, see Path Status Transition on page 2-22. Automatic Path Switching The following describes the automatic failover and failback functions, which automatically switch a path.
Figure 2-10 Path Switching Automatic Failbacks When a path recovers from an error, HDLM can automatically place the recovered path back online. This function is called the automatic failback function. In order to use the automatic failback function, HDLM must already be monitoring error recovery on a regular basis. 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.
When intermittent errors# occur on paths and you are using the automatic failback function, the path status might frequently alternate between the online and offline statuses. In such a case, because the performance of I/Os will most likely decrease, if there are particular paths in which intermittent errors might be occurring, we recommend that you set up intermittent error monitoring so you can detect these paths, and then remove them from those subject to automatic failbacks.
use is not switched even if you change the path status to online by using the online operation. Path Status Transition Each of the online and offline statuses described in Performing Failovers and Failbacks Using Path Switching on page 2-18 is further subdivided into two statuses. The following explains the two online path statuses and the two offline statuses. The Online Path Status The online path statuses are as follows: • Online I/Os can be issued normally.
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).
If an error occurs in the only available online path for an LU, the status of the path will change to Online(E). If you are using the automatic failback function, after the path has recovered from the error, HDLM will automatically place the path online. When you are using intermittent error monitoring, the path in which the intermittent error occurred is not automatically placed online when the path recovers from the error. In such a case, place the path online manually.
number of times that the error needs to occur. If an error occurs on a particular path the specified number of times within the specified errormonitoring interval, then an intermittent error will occur on the path. For example, if you specify 30 for the error monitoring interval and 3 for the number of times that the error needs to occur, the path is determined to have an intermittent error if an error occurs 3 or more times in 30 minutes.
Figure 2-12 Action What Will Happen When an Intermittent Error Occurs on a Path When an Intermittent Error Does Not Occur If an error does not occur on a path a specified number of times within a specified interval, an intermittent error will not occur. In such a case, the error monitoring will finish when the specified error-monitoring interval finishes, upon which the number of errors is reset to 0.
As shown inFigure 2-13 What Will Happen When an Intermittent Error Does Not Occur on a Path on page 2-26 , normally, the count for the number of times that an error occurs is started after the path is first recovered from an error by using the automatic failback function.
When a User Changes the Intermittent Error Information The following might be reset when a user changes any of the values set for the intermittent error or the path status: the number of errors that have already been counted during error monitoring, the amount of time that has passed since error monitoring has started, and the information about whether an intermittent error has occurred.
User operation Placing the path Online while intermittent error monitoring is being performed Number of errors and time passed since error monitoring started Information about paths not subject to automatic failback Inherited (Not applicable) If a path has been removed from the paths subject to automatic monitoring, that path is no longer monitored.
For example, in a normal state, I/O operations are not performed on the paths coming from the standby host in the cluster configuration or on nonowner paths (that is, some of the paths that access a Thunder 9500V series and Hitachi AMS/WMS series storage system). Because of this, for the standby host or for a host connected to non-owner paths, we recommend that you use path health checking to detect errors.
Figure 2-15 Flow of Data When Collecting Error Information Logs might be collected in layers below HDLM, such as for the SCSI driver. For more details, see the Linux documentation. Types of Collected Logs HDLM collects information on the detected error and trace information in the process-specific-trace information file, trace file, error logs, log for the dlmcfgmgr utility for managing the HDLM configuration and syslog.
Table 2-8 Types of Error Information on page 2-32 describes the types of error information. Table 2-8 Types of Error Information Log name Description Output destination Process-specific- Operation logs for the HDLM command 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-33. Filtering of Error Information Errors detected by HDLM are classified into various error levels. Table 2-9 Error Levels on page 2-33 lists the error levels, in the order of most to least severe.
¢ Outputs error information only ¢ Outputs trace information on program operation summaries ¢ Outputs trace information on program operation details ¢ Outputs all trace information For details on how to set the collection level, see Setting Up the HDLM Functions on page 3-184. 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-38 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 Severity #1 Message ID Processing of the dlmupdatesysini t command was successful. 6 KAPL15058-I Processing of the dlmupdatesysini t command failed. 3 KAPL15059-E #1 The severity levels are as follows: 3: Error, 4: Warning, 6: Informational #2 If you use Ctrl + C to cancel the DLMgetras utility for collecting HDLM error information, audit log data indicating that the DLMgetras utility has terminated will not be output.
Destination and Filtering of Audit Log Data Audit log data is output to syslog. Because HDLM messages other than audit log data are also output to syslog, we recommend that you specify the output destination that is used exclusively for audit log data. For example, to change the output destination of audit log data to /usr/ local/audlog, specify the following two settings: Specify the following setting in the /etc/syslog.conf file: • local0.
Audit Log Data Formats The following describes the format of audit log data: Format of audit log data output to syslog: ¢ priority ¢ date-and-time ¢ host-name ¢ program-name ¢ [process-ID] ¢ message-section The following shows the format of message-section and explains its contents.
Item# Explanation Hardware identification information Hardware model name or serial number Location information Hardware component identification information Location identification information Location identification information FQDN Fully qualified domain name Redundancy identification information Redundancy identification information Agent information Agent information Host sending request Name of the host sending a request Port number sending request Number of the port sending a request
to perform system-wide load balancing, and centrally manage the system by collecting HDLM failure information in Global Link Manager. Global Link Manager collects and manages information about paths from instances of HDLM installed on multiple hosts. Even if multiple users manage these hosts, they can control and view this centralized information from client computers.
Software Supported by HDLM (If an FC-SAN Is Used) on page 3-49 in Related Products When Using Red Hat Enterprise Linux 6 on page 3-48, Cluster Software Supported by HDLM on page 3-50 in Related Products When Using SUSE LINUX Enterprise Server 9 on page 3-50, Cluster Software Supported by HDLM on page 3-51 in Related Products When Using SUSE LINUX Enterprise Server 10 on page 3-51, or Cluster Software Supported by HDLM on page 3-61 in Related Products When Using Oracle Enterprise Linux 5 on page 3-61.
2-46 HDLM Functions Hitachi Dynamic Link Manager User Guide (for Linux(R))
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(R))
HDLM System Requirements Check the following before installing HDLM: Hosts and OSs Supported by HDLM HDLM supports hosts on which OSs listed in Table 3-2 Red Hat Enterprise Linux AS4/ES4 Kernels Supported by HDLM on page 3-4, Table 3-3 Red Hat Enterprise Linux 5 Kernels Supported by HDLM on page 3-7, Table 3-4 Red Hat Enterprise Linux 6 Kernels Supported by HDLM on page 3-8, Table 3-5 SUSE LINUX Enterprise Server 9 Kernels Supported by HDLM on page 3-9, Table 3-6 SUSE LINUX Enterprise Server 10 Kernels Sup
# The following shows the meaning of the execution result of the uname command: i686: IA32 architecture ia64: IPF architecture x86_64: AMD64/EM64T architecture 2. Execute the following command to check the vendor of the CPU you are using: # cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 37 model name : AMD Opteron(tm) Processor 252 stepping : 1 : : # Check the vendor_id line. AuthenticAMD is displayed for AMD CPUs, and GenuineIntel is displayed for Intel CPUs.
Kernel architecture#1 Kernel 2.6.9-34.EL 2.6.9-34.ELsmp 2.6.9-34.ELhugemem 2.6.9-34.0.2.EL 2.6.9-34.0.2.ELsmp 2.6.9-34.0.2.ELhugemem 2.6.9-42.EL 2.6.9-42.ELsmp 2.6.9-42.ELhugemem 2.6.9-42.0.3.EL 2.6.9-42.0.3.ELsmp 2.6.9-42.0.3.ELhugemem 2.6.9-55.EL 2.6.9-55.ELsmp 2.6.9-55.ELhugemem 2.6.9-67.EL 2.6.9-67.ELsmp 2.6.9-67.ELhugemem 2.6.9-78.EL 2.6.9-78.ELsmp 2.6.9-78.ELhugemem 2.6.9-89.EL 2.6.9-89.ELsmp 2.6.9-89.ELhugemem 2.6.9-100.EL 2.6.9-100.ELsmp 2.6.9-100.ELhugemem IPF#3 2.6.9-11.EL 2.6.9-34.EL 2.6.9-42.
Kernel architecture#1 Kernel 2.6.9-89.ELlargesmp 2.6.9-100.EL 2.6.9-100.ELlargesmp EM64T/AMD64#4 2.6.9-11.EL 2.6.9-11.ELsmp 2.6.9-34.EL 2.6.9-34.ELsmp 2.6.9-34.ELlargesmp 2.6.9-34.0.2.EL 2.6.9-34.0.2.ELsmp 2.6.9-34.0.2.ELlargesmp 2.6.9-42.EL 2.6.9-42.ELsmp 2.6.9-42.ELlargesmp 2.6.9-42.0.3.EL 2.6.9-42.0.3.ELsmp 2.6.9-42.0.3.ELlargesmp 2.6.9-55.EL 2.6.9-55.ELsmp 2.6.9-55.ELlargesmp 2.6.9-67.EL 2.6.9-67.ELsmp 2.6.9-67.ELlargesmp 2.6.9-78.EL 2.6.9-78.ELsmp 2.6.9-78.ELlargesmp 2.6.9-89.EL 2.6.9-89.ELsmp 2.6.
#3 HDLM supports an environment where an IPF kernel is installed on a system that uses an Intel CPU. #4 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.i386.rpm ¢ - libgcc-RPM-package-version.
Kernel architecture#1 Kernel 2.6.18-238.el5 2.6.18-274.el5 EM64T/AMD64#4 2.6.18-8.el5 2.6.18-53.el5 2.6.18-92.el5 2.6.18-128.el5 2.6.18-164.el5 2.6.18-194.el5 2.6.18-238.el5 2.6.18-274.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 processor. #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 #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 processor. #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.
¢ ¢ ¢ ¢ Among the functions for SUSE LINUX Enterprise Server, HDLM only supports CFQ, and the default I/O scheduler functionality. An HDLM device that applies EVMS functions is not supported. You cannot use DRBD functions in an environment where HDLM is installed. You cannot use HDLM in a User-Mode Linux environment. #1 Only kernels that are provided by OS distributors in binary format are supported.
Kernel architecture#1 Kernel 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.5-default#6 2.6.16.60-0.54.5-smp#6 2.6.16.60-0.54.5-xen#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.
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. #7 All of the SP4 packages for SUSE LINUX Enterprise Server 10 must be installed. #8 HDLM supports an environment where an IPF kernel is installed on a system that uses an Intel CPU.
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. ¢ #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 processor. #3 HDLM supports an environment where an IPF kernel is installed on a system that uses an Intel CPU.
HDLM supports an environment where an EM64T/AMD64 kernel is installed on a system that uses an Intel CPU or AMD Opteron CPU. ¢ In an EM64T/AMD64 environment, the RPM (Red Hat Package Manager) packages listed below are required. Install these RPM packages before installing HDLM: - libstdc++- RPM package version .i386.rpm ¢ - libgcc- RPM package version .i386.rpm - glibc- RPM package version .i686.rpm RPM package version depends on the OS version you are using.
RPM package version depends on the OS version you are using. Storage Systems Supported by HDLM The following shows the storage systems that HDLM supports.
¢ ¢ ¢ ¢ ¢ ¢ Boot Disk Environments and BladeSymphony Environments Supported by HDLM (If an FC-SAN Is Used) on page 3-46 in Related Products When Using Red Hat Enterprise Linux 5 on page 3-36 Boot Disk Environments Supported by HDLM (If an FC-SAN Is Used) on page 3-50 in Related Products When Using Red Hat Enterprise Linux 6 on page 3-48 Boot Disk Environments and BladeSymphony Environments Supported by HDLM on page 3-55 in Related Products When Using SUSE LINUX Enterprise Server 10 on page 3-51 Boot D
Table 3-10 Cluster Software When Using Red Hat Enterprise Linux AS4 (IA32) Usable kernels Cluster software 2.6.9-11.EL LifeKeeper v6 2.6.9-11.ELsmp LifeKeeper v6 Update1 2.6.9-11.ELhugemem LifeKeeper v6 Update2 LifeKeeper v6 Update3 LifeKeeper v6 Update4 LifeKeeper v7 LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 Oracle9i RAC Release 2 (9.2.0.8.0)#1 Oracle RAC 10g Release 2 (10.1.0.5.0)#2 Oracle RAC 10g Release 2 (10.2.0.2.0)#3 Oracle RAC 10g Release 2 (10.2.0.3.
Usable kernels Cluster software LifeKeeper v6 Update4 LifeKeeper v7 LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 Oracle RAC 10g Release 2 (10.1.0.5.0)#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 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-42.EL LifeKeeper v6 2.6.9-42.ELsmp LifeKeeper v6 Update1 2.6.9-42.
Usable kernels Cluster software Oracle RAC 10g Release 2 (10.2.0.3.0)#4 Oracle RAC 10g Release 2 (10.2.0.4.0)#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-55.EL LifeKeeper v6 2.6.9-55.ELsmp LifeKeeper v6 Update1 2.6.9-55.ELhugemem LifeKeeper v6 Update2 2.6.9-67.EL LifeKeeper v6 Update3 2.6.9-67.ELsmp LifeKeeper v6 Update4 2.6.9-67.
Usable kernels Cluster software 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-178. #2 Only configurations that include the Automatic Storage Management (ASM) function (the ASMLib kernel driver (ASMLib) is used) and Cluster Ready Service (CRS) are supported. For details, see Settings for Oracle RAC on page 3-178.
¢ ¢ 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-178.
Usable kernels Cluster software Oracle RAC 10g Release 2 (10.2.0.4.0)#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.EL LifeKeeper v6 Update3 2.6.9-34.0.2.ELsmp LifeKeeper v6 Update4 2.6.9-34.0.2.ELhugemem LifeKeeper v7 LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 Oracle RAC 10g Release 2 (10.1.0.5.
Usable kernels Cluster software 2.6.9-67.ELsmp LifeKeeper v6 Update4 2.6.9-67.ELhugemem LifeKeeper v7 LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 Oracle RAC 10g Release 2 (10.1.0.5.0)#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 11g Release 1 (11.1.0.6.0)#5 Oracle RAC 11g Release 1 (11.1.0.7.0)#6 RHCM 1.0.17-0 2.6.9-78.EL LifeKeeper v6 Update4 2.6.9-78.ELsmp LifeKeeper v7 2.6.9-78.
¢ Configurations that include raw devices and Cluster Ready Service (CRS) Configurations that include the Automatic Storage Management (ASM) function (raw devices used) and Cluster Ready Service (CRS) When 2.6.9-11.ELsmp is used for the kernel, the following configuration is also supported: ¢ Configurations that include the Automatic Storage Management (ASM) function (the ASMLib kernel driver (ASMLib) is used) and Cluster Ready Service (CRS) For details, see Settings for Oracle RAC on page 3-178.
The following configurations are supported: ¢ Configurations that include raw devices and Cluster Ready Service (CRS) Configurations that include the Automatic Storage Management (ASM) function (raw devices used) and Cluster Ready Service (CRS) For details, see Settings for Oracle RAC on page 3-178. ¢ #8 Only configurations that include the Automatic Storage Management (ASM) function (using raw devices) and Oracle Clusterware are supported. For details, see Settings for Oracle RAC on page 3-178.
For details, see Settings for Oracle RAC on page 3-178.
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)#2 Oracle RAC 11g Release 1 (11.1.0.6.0)#3 Oracle RAC 11g Release 1 (11.1.0.7.0)#4 RHCM 1.0.4-0 VCS 4.1 MP3#5 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 Oracle RAC 10g Release 2 (10.2.0.2.
Usable kernels Cluster software LifeKeeper v6 Update3 LifeKeeper v6 Update4 LifeKeeper v7 LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 Oracle RAC 10g Release 2 (10.2.0.2.0)#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 11g Release 1 (11.1.0.6.0)#3 Oracle RAC 11g Release 1 (11.1.0.7.0)#4 RHCM 1.0.11-0 2.6.9-55.EL LifeKeeper v6 2.6.9-55.ELsmp LifeKeeper v6 Update1 2.6.9-55.ELlargesmp LifeKeeper v6 Update2 2.6.9-67.
Usable kernels 2.6.9-100.ELlargesmp Cluster software Oracle RAC 10g Release 2 (10.2.0.4.0)#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.2.
The following functions are not supported: ¢ I/O fencing function provided by VCS ¢ DiskReservation function provided by VCS ¢ Linkage with VxVM and VxFS #6 Only configurations that include the Automatic Storage Management (ASM) function (using raw devices) and Oracle Clusterware are supported. For details, see Settings for Oracle RAC on page 3-178.
Kernel architecture Kernel Volume Manager 2.6.9-78.ELhugemem 2.6.9-89.EL LVM2.02.42-5.el4 2.6.9-89.ELsmp 2.6.9-89.ELhugemem 2.6.9-100.EL LVM2.02.42-9.el4 2.6.9-100.ELsmp 2.6.9-100.ELhugemem IPF 2.6.9-11.EL LVM2.01.08-1.0.RHEL4 2.6.9-34.EL LVM2.02.01-1.3.RHEL4 LVM2.02.21-5.el4 2.6.9-42.EL LVM2.02.06-6.0.RHEL4 2.6.9-42.0.3.EL 2.6.9-55.EL LVM2.02.21-5.el4 2.6.9-55.ELlargesmp 2.6.9-67.EL LVM2.02.27-2.el4 2.6.9-67.ELlargesmp 2.6.9-78.EL LVM2.02.21-5.el4 2.6.9-78.ELlargesmp LVM2.02.37-3.
Kernel architecture Kernel Volume Manager 2.6.9-55.ELlargesmp LVM2.02.27-2.el4 2.6.9-67.EL 2.6.9-67.ELsmp 2.6.9-67.ELlargesmp 2.6.9-78.EL LVM2.02.21-5.el4 2.6.9-78.ELsmp LVM2.02.37-3.el4 2.6.9-78.ELlargesmp LVM2.02.42-5.el4 2.6.9-89.EL 2.6.9-89.ELsmp 2.6.9-89.ELlargesmp LVM2.02.42-9.el4 2.6.9-100.EL 2.6.9-100.ELsmp 2.6.9-100.
Kernel architecture Kernel HBA Supported storage systems 2.6.9-55.EL 2.6.9-78.EL EM64T 2.6.9-11.ELsmp 2.6.9-34.ELsmp 2.6.9-55.ELsmp 2.6.9-78.ELsmp #1 The XP series is not supported. #2 The storage system is not supported in an environment where an HDLM device is specified for the boot disk.
Kernel 2.6.9-55.ELsmp HBA Supported storage systems QLogic 2.6.9-55.ELhugemem 2.6.9-67.EL 2.6.9-67.ELsmp 2.6.9-67.ELhugemem 2.6.9-78.EL 2.6.9-78.ELsmp 2.6.9-78.ELhugemem 2.6.9-89.EL 2.6.9-89.ELsmp 2.6.9-89.ELhugemem 2.6.9-100.EL 2.6.9-100.ELsmp 2.6.9-100.ELhugemem Table 3-17 Operating Environments for Boot Disks When Using Red Hat Enterprise Linux AS4/ES4 (IPF) Kernel HBA 2.6.9-55.EL Emulex 2.6.9-55.ELlargesmp Supported storage systems Hitachi AMS2000/AMS/WMS/SMS series Hitachi USP 2.6.9-67.
Kernel HBA Supported storage systems 2.6.9-34.0.2.ELsmp 2.6.9-34.0.2.ELhugemem 2.6.9-42.EL 2.6.9-42.ELsmp 2.6.9-42.ELlargesmp 2.6.9-42.0.3.EL 2.6.9-42.0.3.ELsmp 2.6.9-42.0.3.ELlargesmp 2.6.9-55.EL Emulex 2.6.9-55.ELsmp QLogic 2.6.9-55.ELlargesmp 2.6.9-67.EL 2.6.9-67.ELsmp 2.6.9-67.ELlargesmp 2.6.9-78.EL 2.6.9-78.ELsmp 2.6.9-78.ELlargesmp 2.6.9-89.EL 2.6.9-89.ELsmp 2.6.9-89.ELlargesmp 2.6.9-100.EL 2.6.9-100.ELsmp 2.6.9-100.
Kernel architecture Kernel HBA Supported storage systems 2.6.9-55.EL 2.6.9-78.EL EM64T 2.6.9-11.ELsmp 2.6.9-34.ELsmp 2.6.9-55.ELsmp 2.6.9-78.ELsmp # The HP XP series is not supported.
Enterprise Linux 5 (EM64T/AMD64) on page 3-39 list the related programs used when creating a cluster. Table 3-20 Cluster Software Used with Red Hat Enterprise Linux 5 (IA32) Usable kernels Cluster software 2.6.18-8.el5 LifeKeeper v6 Update1 2.6.18-8.el5PAE LifeKeeper v6 Update2 LifeKeeper v6 Update3 LifeKeeper v6 Update4 LifeKeeper v7 LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 Oracle RAC 10g Release 2 (10.2.0.4.0)#1 Oracle RAC 11g Release 1 (11.1.0.6.
Usable kernels Cluster software LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 Oracle RAC 10g Release 2 (10.2.0.4.0)#1 Oracle RAC 11g Release 1 (11.1.0.6.0)#2 Oracle RAC 11g Release 1 (11.1.0.7.0)#3 Oracle RAC 11g Release 2 (11.2.0.1.0)#4 Oracle RAC 11g Release 2 (11.2.0.2.0)#4 RHCM 2.0.98-1 2.6.18-164.el5 LifeKeeper v6 Update4 2.6.18-164.el5PAE LifeKeeper v7 2.6.18-194.el5 LifeKeeper v7 Update1 2.6.18-194.el5PAE LifeKeeper v7 Update2 2.6.18-238.el5 2.6.18-238.
¢ Configurations that include the Automatic Storage Management (ASM) function (the ASMLib kernel driver (ASMLib) is used) and Oracle Clusterware Configurations that include the Oracle Cluster File System 2 and Oracle Clusterware For details, see Settings for Oracle RAC on page 3-178.
Usable kernels Cluster software LifeKeeper v6 Update3 LifeKeeper v6 Update4 LifeKeeper v7 LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 Oracle RAC 10g Release 2 (10.2.0.1.0)#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 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.60-1 2.6.18-53.
Usable kernels Cluster software 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 RHCM 2.0.84-2 2.6.18-128.el5 LifeKeeper v6 Update4 LifeKeeper v7 LifeKeeper v7 Update1 LifeKeeper v7 Update2 LifeKeeper v7 Update3 Oracle RAC 10g Release 2 (10.2.0.1.0)#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 11g Release 1 (11.1.0.6.0)#4 Oracle RAC 11g Release 1 (11.1.0.7.
Usable kernels Cluster software 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 #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-178.
¢ ¢ ¢ 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 3-178.
Kernel architecture Kernel Volume manager 2.6.18-194.el5 LVM2.02.56-8.el5 2.6.18-194.el5PAE 2.6.18-238.el5 LVM2.02.74-5.el5 2.6.18-238.el5PAE LVM2.02.84-3.el5# 2.6.18-274.el5 LVM2.02.84-3.el5 2.6.18-274.el5PAE IPF 2.6.18-8.el5 LVM2.02.16-3.el5 2.6.18-53.el5 LVM2.02.26-3.el5 2.6.18-92.el5 LVM2.02.32-4.el5 2.6.18-128.el5 LVM2.02.40-6.el5 2.6.18-164.el5 LVM2.02.46-8.el5 2.6.18-194.el5 LVM2.02.56-8.el5 2.6.18-238.el5 LVM2.02.74-5.el5 LVM2.02.84-3.el5# EM64T/AMD64 2.6.18-274.el5 LVM2.
Kernel architecture Kernel File system 2.6.18-53.el5 2.6.18-53.el5PAE 2.6.18-92.el5 2.6.18-92.el5PAE 2.6.18-128.el5 ext2 (supplied with the OS) 2.6.18-128.el5PAE ext3 (supplied with the OS) 2.6.18-164.el5 GFS2 (supplied with the OS)# 2.6.18-164.el5PAE 2.6.18-194.el5 2.6.18-194.el5PAE IPF 2.6.18-238.el5 ext2 (supplied with the OS) 2.6.18-238.el5PAE ext3 (supplied with the OS) 2.6.18-274.el5 ext4 (supplied with the OS) 2.6.18-274.el5PAE GFS2 (supplied with the OS)# 2.6.18-8.
Boot Disk Environments and BladeSymphony Environments Supported by HDLM (If an FC-SAN Is Used) HDLM supports BladeSymphony in any of the environments listed in Table 3-25 Operating Environments for BladeSymphony When Using Red Hat Enterprise Linux 5 on page 3-46. For details on OSs (kernels) that each BladeSymphony model supports, see the BladeSymphony documentation. For details on OSs (kernels) that each storage system model supports, see the storage system documentation.
Kernel architecture Kernel Supported storage systems HBA 2.6.18-92.el5PAE Virtual Storage Platform 2.6.18-128.el5# 2.6.18-128.el5PAE# 2.6.18-164.el5# 2.6.18-164.el5PAE# 2.6.18-194.el5# 2.6.18-194.el5PAE# 2.6.18-238.el5# 2.6.18-238.el5PAE# IPF 2.6.18-274.el5# Emulex 2.6.18-274.el5PAE# QLogic 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# Brocade Emulex 2.6.18-238.el5# EM64T/AMD64 2.6.18-274.el5# Emulex 2.6.18-8.el5 Emulex QLogic 2.6.
environments when an HDLM device is used as a boot disk in a BladeSymphony environment. Table 3-27 Operating Environments for BladeSymphony and Boot Disks When Using Red Hat Enterprise Linux 5 Kernel architecture IA32 Kernel 2.6.18-53.el5PAE 2.6.18-92.el5PAE 2.6.18-128.el5PAE 2.6.18-164.el5PAE 2.6.18-238.el5PAE IPF 2.6.18-53.el5 HBA hitachi Supported storage systems Hitachi AMS2000/AMS/WMS/ SMS series Hitachi USP# Thunder 9500V series Universal Storage Platform V/ VM# Virtual Storage Platform# 2.6.
Cluster Software Supported by HDLM (If an FC-SAN Is Used) When you use HDLM in a cluster configuration, you must install the same version of HDLM on all the nodes that comprise the cluster. If different versions of HDLM are installed, the cluster system may not operate correctly.
Boot Disk Environments Supported by HDLM (If an FC-SAN Is Used) HDLM supports boot disks in any of the environments listed in Table 3-30 Operating Environments for Boot Disks When Using Red Hat Enterprise Linux 6 on page 3-50. For details on OSs (kernels) that each storage system model supports, see the storage system documentation. Table 3-30 Operating Environments for Boot Disks When Using Red Hat Enterprise Linux 6 Kernel architecture IA32 Kernel 2.6.32-71.el6.i686# 2.6.32-131.0.15.el6.
Notes on using a volume manager Note the following when using a volume manager: • Although disk partitioning and system backup functions are supported for disks in a YaST2 system, the combination of YaST2 and LVM is not supported. • When you execute an LVM-related command such as pvscan or vgscan, a CD-ROM IOCTL command might be sent to each device in the OS. The IOCTL is available only for SCSI devices.
Table 3-31 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.21-default Heartbeat (2.1.3-0.9)#2 2.6.16.60-0.21-smp 2.6.16.60-0.
Kernel architecture Usable kernels Cluster software 2.6.16.60-0.54.5-smp 2.6.16.60-0.54.5-xen 2.6.16.60-0.85.1-default Heartbeat (2.1.4-0.24.9)#2 2.6.16.60-0.85.1-smp 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-178. #2 Heartbeat can also use together with Oracle Cluster File System 2.
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.
¢ The system is started. ¢ You execute the utility for supporting a boot disk (dlmmkinitrd).
Table 3-34 Operating Environments for Boot Disks When Using SUSE LINUX Enterprise Server 10 Kernel architecture IA32 Kernel 2.6.16.46-0.14default HBA Supported storage systems QLogic Hitachi AMS2000/AMS/WMS/SMS series 2.6.16.46-0.14-smp Hitachi USP 2.6.16.46-0.14bigsmp Lightning 9900V series 2.6.16.60-0.21default 2.6.16.60-0.21-smp Thunder 9500V series Brocade Universal Storage Platform V/VM QLogic Virtual Storage Platform 2.6.16.60-0.21bigsmp 2.6.16.60-0.21xenpae QLogic 2.6.16.60-0.54.
Kernel architecture Kernel HBA Supported storage systems 2.6.16.60-0.54.5smp 2.6.16.60-0.54.5xen 2.6.16.60-0.85.1default QLogic 2.6.16.60-0.85.1smp 2.6.16.60-0.85.1xen Table 3-35 Operating Environments for BladeSymphony and Boot Disks When Using SUSE LINUX Enterprise Server 10 on page 3-57 lists the operating environments when an HDLM device is used as a boot disk in a BladeSymphony environment.
For details on the functions provided by ServerConductor/ DeploymentManager, see the manual ServerConductor/DeploymentManager User's Guide. Related Products When Using SUSE LINUX Enterprise Server 11 The following describes related products when SUSE LINUX Enterprise Server 11 is used. Volume Managers Supported by HDLM Table 3-36 Volume Managers When Using SUSE LINUX Enterprise Server 11 on page 3-58 lists and describes the related programs when using a volume manager.
This message is also output in the following cases, but HDLM operations are not affected: ¢ ¢ You execute the utility for collecting HDLM error information (DLMgetras). The system is started.
Volume Manager Supported by HDLM Table 3-38 Volume Managers When Using Oracle Enterprise Linux 4 on page 3-60 lists and describes the related programs when using a volume manager. Table 3-38 Volume Managers When Using Oracle Enterprise Linux 4 Kernel architecture Kernel IA32 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.ELhugemem 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.ELhugemem EM64T/AMD64 LVM2.02.21-5.el4 2.6.9-55.
Kernel architecture Kernel HBA Supported storage systems Virtual Storage Platform 2.6.9-67.0.0.0.1.EL smp 2.6.9-67.0.0.0.1.EL hugemem EM64T/AMD64 2.6.9-55.0.0.0.2.EL 2.6.9-55.0.0.0.2.EL smp 2.6.9-55.0.0.0.2.ELl argesmp 2.6.9-67.0.0.0.1.EL 2.6.9-67.0.0.0.1.EL smp 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.
Kernel architecture Usable kernels Cluster software 2.6.18-238.el5 2.6.18-238.el5PAE EM64T/AMD64 2.6.18-53.el5 Oracle RAC 11g Release 1(11.1.0.6.0)# RHCM 2.0.73-1 2.6.18-164.el5 Oracle RAC 11g Release 2(11.2.0.2.0)# 2.6.18-194.el5 None 2.6.18-238.el5 # Only configurations that include the Automatic Storage Management (ASM) function (raw devices are used) and Cluster Ready Service (CRS) are supported. For details, see Settings for Oracle RAC on page 3-178.
Table 3-42 Supported File Systems When Using Oracle Enterprise Linux 5 Kernel architecture IA32 Kernel File system 2.6.18-53.el5 ext2 (supplied with the OS) 2.6.18-53.el5PAE ext3 (supplied with the OS) 2.6.18-164.el5 ext2 (supplied with the OS) 2.6.18-164.el5PAE ext3 (supplied with the OS) 2.6.18-194.el5 GFS2 (supplied with the OS) 2.6.18-194.el5PAE 2.6.18-238.el5 2.6.18-238.el5PAE EM64T/AMD64 2.6.18-53.el5 ext2 (supplied with the OS) ext3 (supplied with the OS) 2.6.18-164.
Kernel architecture Kernel Supported storage systems HBA 2.6.18-238.el5 Memory and Disk Capacity Requirements This section describes memory and disk capacity requirements. Memory Requirements Table 3-44 Memory Requirements for a Host on page 3-64 lists the memory requirements for a host.
p is obtained by the following formula: p = (s x m) / 1024 [MB] Where s is the error log file size (unit: KB, default value: 9900) and m is the number of error log files (default value: 2). The result is rounded up to MB. #2 This size differs depending on the settings for trace files (maximum size: 1000 MB). q is obtained by using the following formula: q = (t x n) / 1024 [MB] Where t is the trace file size (unit: KB, default value: 9900) and n is the number of trace files (default value: 4).
#8 The size of the configuration definition file. y is obtained by using the following formula: y = (2500 bytes x number-of-paths x 4) / 1024 / 1024 [MB] The result is rounded up to MB. #9 The size of the file that defines non-HDLM-managed disks. z is obtained by using the following formula: z = (20 bytes x number-of-non-HDLM-managed-disks x 4) / 1024 / 1024 [MB] The result is rounded up to MB.
Note that the range of values supported by HDLM is from 0 to 255. Therefore, do not assign an LU whose LUN is 256 or greater. Virtual Environments Supported by HDLM HDLM supports the following virtual environments: • HVM where the server virtualization mechanism is mounted on a BladeSymphony blade server • Xen If you choose to use Xen, make sure that HDLM is installed in domain0.
Table 3-48 KVM Operating Environments Supported by HDLM OS Red Hat Enterprise Linux 5 Kernel architecture EM64T/AMD64 Kernel 2.6.18-164.el5 2.6.18-194.el5 KVM version KVM supplied with the OS is supported. 2.6.18-238.el5 2.6.18-274.el5 Red Hat Enterprise Linux 6 EM64T/AMD64 2.6.32-71.el6.x86_ 64 2.6.32-131.0.15.el6 .x86_64 Flow for Creating an HDLM Environment Set up the environment to use HDLM as shown in the following diagram.
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 uninstalling the existing old version is called an upgrade installation of HDLM. Re-installation of HDLM: Installing the same version of HDLM, to restore the existing version, without first uninstalling that version is called a re-installation of HDLM.
Notes on Creating an HDLM Environment This section provides notes on creating an HDLM environment. For notes on operating HDLM, see Notes on Using HDLM on page 4-2. Notes on Hardware Settings • The types of HBA that are installed on one host can be mixed. However, the HBAs connected to an HDLM-managed device must all be of the same type. Also make sure that the HBA driver versions are the same.
sure that the following coding is in the line for INITRD_MODULES= in the / etc/sysconfig/kernel file. ¢ ¢ When using the QLA22XX HBA: qla2200 When using the QLA23XX HBA: qla2300 If qla2xxx is appears in the file instead of qla2200 or qla2300, change qla2xxx to qla2200 or qla2300 as follows: INITRD_MODULES="mptscsih qla2300 reiserfs" After editing the /etc/sysconfig/kernel file, execute the mkinitrd command to re-create an initial RAM disk image.
¢ An HDLM device for which automatic mounting is specified has not been mounted. ¢ An md device created on an HDLM device has not been activated. ¢ An LVM created on an HDLM device has not been activated. ¢ HDLM information is missing in the /etc/init.d/boot.localfs file, 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.
# /sbin/service haldaemon stop c. Make sure that the HAL daemon is stopped. Execute the /sbin/service command to make sure that the HAL daemon is not running. # /sbin/service haldaemon status 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.
Notes on a Device Manager Agent • When installing HDLM on a host where Device Manager agent 5.0 or later is installed, do not execute any of the following commands of Device Manager agent during installation: hbsasrv, HiScan, hdvmagt_account, hdvmagt_schedule, hldutil, TIC Installing HDLM The following section describes how to install HDLM for a new installation, for a re-installation, and for an upgrade installation. Depending on the procedure, the host might have to be restarted after HDLM is installed.
When accessing a device that is to be managed after HDLM installation, the setting name used until now cannot be used for access because the logical device file name for the HDLM device that HDLM creates is used. 4. Unmount the disks. 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-76.
Migration is not affected even when a logical volume or file system has been created. • A physical volume is created for only one of the logical device files on any one path for each SCSI device to be managed by HDLM. In addition, a volume group is created for only the physical volume. This subsection describes how to check whether this condition exists. • The logical volume is unmounted.
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.
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. Use the volname command to check media-volume-id. The following shows an execution example for when media-volume-id is VOL01234.
6. The KAPL09093-I message is displayed to confirm that you want to perform a new installation. Check the HDLM version, and if it is correct, enter y. The license key file will be deleted when installation finishes. 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.xxx Release : xx : If HDLM Version is x.x.x.x.xxx, the installed version of HDLM is correct. x.x.x.x.
A path will be established in the HDLM device and the HDLM manager will start. 14. If you have edited the /etc/fstab file as described in Operations Required for Devices to Be Managed by HDLM on page 3-75 in Preparations for a New Installation of HDLM on page 3-75, add the line show below to change the setting from a SCSI device specification to an HDLM device specification. The Linux functionality that adds LABEL= to a SCSI device is not supported in HDLM. Do not use this functionality.
For details on setting the cluster software, see Settings for Heartbeat on page 3-178, Settings for Oracle RAC on page 3-178, Settings for the RHCM on page 3-181, or Settings for VCS on page 3-183. 20. Execute the dlnkmgr command's view operation to check the HDLM settings and status of each program. The following is an example of executing the command: # /opt/DynamicLinkManager/bin/dlnkmgr view -sys HDLM Version : x.x.
For details on how to re-install HDLM, see Performing a Re-installation of HDLM on page 3-86. For details on how to upgrade-install HDLM, see Performing an Upgrade Installation of HDLM on page 3-91. Operations Required for Devices to Be Managed by HDLM Before performing an upgrade installation or re-installation of HDLM, you must unmount the HDLM devices that correspond to HDLM-managed devices, and then back up the HDLM-managed devices. 1.
0 logical volume(s) in volume group "vg01" now active Setting Up Xen If Xen is being used, make sure that domainU has been stopped. If domainU has been set up to automatically start whenever domain0 starts, temporarily change the setting so that domainU will not start automatically. Performing a Re-installation of HDLM The following is the procedure for a re-installation. Some preparations before installing HDLM are required.
# mount /dev/cdrom /media/cdrom For details about the fixed mount point for each distribution, see Table 3-50 Mount Point for Each Distribution on page 3-87.
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.sh -v ¢ When executing the installhdlm utility # /media/cdrom/HDLM_Linux/installhdlm -v A command execution example is described below. x.x.x-xx is the version of HDLM.
For details on this utility, see dlmsetopt Utility for Setting HDLM Driver Options on page 7-35. If you performed this step, go to step 11. 9. When you want to install HDLM without restarting the host, go to step 10. When you want to install HDLM with restarting the host, then go to step 11. 10. Execute the dlmstart utility for starting HDLM. For details, see dlmstart Utility for Starting HDLM on page 7-38. 11.
Perform this step if your host OS uses LUKS. If HDLM manages a SCSI device that has been configured to use LUKS, the LUKS settings must be migrated from the SCSI device to an HDLM device. For details on setting up LUKS, see Settings for LUKS on page 3-152. 15. If md devices are used, execute the following command to activate them: # mdadm -A -scan mdadm: /dev/md0 has been started with 2 drives. 16. If md devices are used, execute the following command to make sure that they have been activated.
If you are using Xen, set up Xen to use HDLM devices in domainU. If you are using KVM, register HDLM devices into the hardware configuration file. For details on operating environments for the virtual environments supported by HDLM, see Virtual Environments Supported by HDLM on page 3-67. For details on how to set up a virtual environment, see Settings for Xen on page 3-175 or Settings for KVM on page 3-177. 21. Specify the settings required for operations in a cluster configuration.
The following shows an example of command execution when the mount point is /media/cdrom: # mount /dev/cdrom /media/cdrom For details about the fixed mount point for each distribution, see Table 3-51 Mount Point for Each Distribution on page 3-92.
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.sh -v ¢ When executing the installhdlm utility # /media/cdrom/HDLM_Linux/installhdlm -v A command execution example is described below. x.x.
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. When you want to set the HDLM driver options, run the dlmsetopt utility for setting HDLM driver option. For details on this utility, see dlmsetopt Utility for Setting HDLM Driver Options on page 7-35. If you performed this step, go to step 12. 10. When you want to install HDLM without restarting the host, go to step 11.
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-152. 16. If md devices are used, execute the following command to activate them: # mdadm -A -scan mdadm: /dev/md0 has been started with 2 drives. 17.
# vgchange -ay vg01 vgchange -- volume group "vg01" successfully activated 20. Mount the logical volume that was moved. In the following example, the logical volume is /dev/vg01/lvol1 and the command mounts the volume on /mnt/lvol1: # mount /dev/vg01/lvol1 /mnt/lvol1 21. 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 an unattended installation, you can specify any directory to store the license key file. For details, see Editing an Installation-Information Settings File on page 7-42. 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.
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.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.
# /media/cdrom/installux.sh -f /any-directory/installationinformation-settings-file ¢ When executing the installhdlm utility # /media/cdrom/HDLM_Linux/installhdlm -f /any-directory/ installation-information-settings-file Note that, if you edited the installation information settings file in step 5 so that the host is restarted, the host is automatically restarted. 7. Make sure that HDLM is installed. Execute the following command to display detailed information about the installed package.
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. For details on setting up LUKS, see Settings for LUKS on page 3-152. 12. Specify the settings required for using md devices. If you want to use md devices, create them in a multi-path environment.
If you are using Xen, set up Xen to use HDLM devices in domainU. If you are using KVM, register HDLM devices into the hardware configuration file. For details on operating environments for the virtual environments supported by HDLM, see Virtual Environments Supported by HDLM on page 3-67. For details on how to set up a virtual environment, see Settings for Xen on page 3-175 or Settings for KVM on page 3-177. 17. Specify the settings required for operations in a cluster configuration.
In this case, if a problem occurs, use the log displayed on the console to analyze the problem. • The dlmcfgmgr log created at startup is output to /etc/opt/ DynamicLinkManager/hdlmboot.log. • Once you have built an environment for starting the OS from an HDLM device, you cannot change the boot disk.
Upgrade Installation in an Environment Where an HDLM Device Is Used as a Boot Disk on page 3-116 and perform operations while reading the SCSI device names in those subsections as the new SCSI device names (udev name) that were changed by using the udev function. In an environment where HDLM has been installed, you can use the dlmcfgmgr utility to check the correspondence between a SCSI device and a udev name.
Overview of the Procedure for Installing HDLM in a Boot Disk Environment This subsection provides an overview of the procedure for installing HDLM in a boot disk environment. Settings for Using an HDLM Device as a Boot Disk 1. Check whether LABEL is used. If it is, remove it. To use HDLM, you must remove the LABEL setting, because a SCSI device cannot be identified from the value set in LABEL in an HDLM environment. See steps 1 to 16 in Settings for Using an HDLM Device as a Boot Disk on page 3-106. 2.
Settings for Using a Logical Volume (LVM2) on an HDLM Device as a Boot Disk To migrate a single-path boot disk environment that uses a logical volume (LVM2) on a SCSI device to a multi-path boot disk environment that uses a logical volume on an HDLM device (for details, see Settings for Using a Logical Volume (LVM2) on an HDLM Device as a Boot Disk on page 3-124): 1. Check whether LABEL is used. If it is, remove it.
After completing the above procedure, you can perform an upgrade installation of HDLM in a multi-path boot disk environment that uses a logical volume (LVM2) on an HDLM device. Settings for Using an HDLM Device as a Boot Disk This subsection describes how to perform a new installation of HDLM in a single-path boot disk environment that uses a SCSI device and how to set up the environment. Note that if the settings are incorrect, the OS might not start.
¢ When GRUB is used as the boot loader with Xen kernels: For details on Xen kernels, see Table 3-47 Xen Hypervisor Operating Environments Supported by HDLM on page 3-67. : : title XEN root (hd0,0) kernel /xen-pae.gz module /vmlinuz-2.6.16.60-0.54.5-xenpae \ root=/dev/disk/by-id/scsi-SFUJITSU_MAS3735NC_A050P360007Npart6 vga=0x317 \ resume=/dev/disk/by-id/scsiSFUJITSU_MAS3735NC_A050P3600077-part2 \ splash=silent showopts multipath=off module /initrd-2.6.16.60-0.54.
defaults 0 0 /dev/disk/by-id/scsi-1HITACHI_D60H03750019-part3 / acl,user_xattr 1 1 : : 4. ext3 Check the definition in the boot loader configuration file. Check whether LABEL is used in the definition in the boot loader configuration file. The following shows examples for LABEL. ¢ When GRUB is used as the boot loader with non-Xen kernels: For details on kernels supported by HDLM, see Hosts and OSs Supported by HDLM on page 3-3. : : title Red Hat Enterprise Linux (2.6.18-194.
Xen Hypervisor Operating Environments Supported by HDLM on page 3-67. : : title XEN root (hd0,1) kernel /boot/xen.gz module /boot/vmlinuz-2.6.16.60-0.21-xen root=/dev/disk/by-id/ scsi-1HITACHI_D60H03750027-part2 vga=0x31a resume=/dev/sda1 splash=silent showopts module /boot/initrd-2.6.16.60-0.21-xen If LABEL or the device name (udev name) was not used in step 3 and step 4, proceed to step 17 and install a new instance of HDLM.
Execute the udevinfo command. Specify the device name (udev name) in the /dev/disk directory for -n. # udevinfo -q name -n /dev/disk/by-id/scsi-2000c50fffecb6ae0part2 sda2 The sda2 value output is the SCSI device name corresponding to / dev/disk/by-id/scsi-2000c50fffecb6ae0-part2. 8. Back up the /etc/fstab file. 9. Edit the /etc/fstab file, and delete the LABEL setting.
¢ When GRUB is used as the boot loader with non-Xen kernels: For details on kernels supported by HDLM, see Hosts and OSs Supported by HDLM on page 3-3. : : title Red Hat Enterprise Linu Linux (2.6.18-194.el5) root (hd0,0) kernel /vmlinuz-2.6.18-194.el5 ro option root=LABEL=/ option initrd /initrd-2.6.18-194.el5 ¢ When LILO or ELILO is used as the boot loader: : : image=/boot/vmlinuz-2.6.18-194.el5 label=linux initrd=/boot/initrd-2.6.18-194.el5 read-only append="option root=LABEL=/ option" 12.
Change the root specification on the kernel line to root=SCSIdevice. ¢ When LILO or ELILO is used as the boot loader: Change the specification for root to root=SCSI-device. If no options have been specified to suit the user environment, delete or comment out the append line. 14. 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 11.
The following shows an example of executing the command: # /sbin/dracut /boot/initramfs-hdlm-2.6.32-71.el6.i686.img `uname -r` ¢ For OSs other than the above: Execute the utility for supporting a boot disk (dlmmkinitrd). For details on the dlmmkinitrd utility, see dlmmkinitrd Utility for Supporting a Boot Disk on page 7-31. 20. Back up the /etc/fstab file. 21. Edit the /etc/fstab file.
title sd-Red Hat Enterprise Linux (2.6.18-194.el5) After: title HDLM-Red Hat Enterprise Linux (2.6.18-194.el5) ¢ When LILO or ELILO is used as the boot loader: Change the underlined text as follows: Before: label=linux-sd After: label=linux-HDLM 25. Edit the root specification written in the boot loader configuration file. From the following, perform the procedure that corresponds to the host OS.
Change the initrd specification in the configuration that you copied in step 23. If you are using a Xen kernel, change the initrd file name specified in module to the initial RAM disk image file you created in step 19. For details on Xen kernels, see Table 3-47 Xen Hypervisor Operating Environments Supported by HDLM on page 3-67. Keep in mind that the specification method for initrd differs depending on the boot loader.
/dev/sddlmaa6 on /usr type ext2 (rw) none on /dev/shm type tmpfs (rw) Check the underlined section. 34. If Red Hat Enterprise Linux, SUSE LINUX Enterprise Server 10, or SUSE LINUX Enterprise Server 11 is used, make sure that the HDLM device is allocated to the swap partition. Make sure that the HDLM device name is displayed in the Filename column of the /proc/swaps file.
¢ When LILO is used as the boot loader: Root directory (/), /tmp, /usr, /var, swap The following shows an example of the /etc/fstab file: 3. /dev/sddlmaa2 / ext2 /dev/sddlmaa4 /tmp ext2 : : : : : : defaults 1 1 defaults 1 2 Execute the HDLM-configuration definition utility (dlmcfgmgr) with the -v parameter specified to check the correspondence between the HDLM device and the SCSI device.
: : title XEN root (hd0,1) kernel /boot/xen.gz module /boot/vmlinuz-2.6.16.60-0.21-xen vga=0x31a splash=silent showopts module /boot/initrd-2.6.16.60-0.21-xen.hdlm ¢ When GRUB is used as the boot loader with non-Xen kernels: For details on kernels supported by HDLM, see Hosts and OSs Supported by HDLM on page 3-3. : : title Red Hat Enterprise Linux (2.6.18-194.el5) root (hd0,0) kernel /vmlinuz-2.6.18-194.el5 ro option ramdisk_size=18958 option initrd /initrd-hdlm-2.6.18-194.el5.
Change the specification for root contained in the configuration that you copied in step 5. ¢ When GRUB is used as the boot loader: Add root=SCSI-device to the kernel line. : : title Red Hat Enterprise Linux (2.6.18-194.el5) root (hd0,0) kernel /vmlinuz-2.6.18-194.el5 ro option ramdisk_size=18958 root=/dev/sda2 option ¢ 8. When LILO or ELILO is used as the boot loader: Add root=SCSI-device as the last line of the configuration.
14. Start the host. 15. Execute the mount command to make sure that the SCSI device is mounted. The following shows an execution example for when GRUB is used as the boot loader: # mount /dev/sda2 on / type ext2 (rw) : : /dev/sda1 on /boot type ext2 (rw) /dev/sda4 on /tmp type ext2 (rw) /dev/sda5 on /var type ext2 (rw) /dev/sda6 on /usr type ext2 (rw) none on /dev/shm type tmpfs (rw) Check the underlined section. 16.
# /sbin/dracut /boot/initramfs-hdlm-2.6.32-71.el6.i686.img `uname -r` ¢ For OSs other than the above: Execute the utility for supporting a boot disk (dlmmkinitrd). If the initial RAM disk image file to be created already exists and you are using Red Hat Enterprise Linux AS4/ES4 or Red Hat Enterprise Linux 5, specify the -f parameter to overwrite this file. If you are using SUSE LINUX Enterprise Server 10 or SUSE LINUX Enterprise Server 11, this file is overwritten even if you do not specify the parameter.
/dev/sda2 on / type ext4 (rw) proc on /proc type proc (rw) : : Check the underlined device name. b. Execute the blkid command to check the UUID of the device that you checked above. The following shows an example of executing the command. # blkid /dev/sda2 /dev/sda2: UUID="19597725-5d20-4d1d-9906-f9f891b7711a" TYPE="ext4" # c. Change the root specification in the configuration that you copied in step 21 to the UUID checked above.
27. Edit the /etc/fstab file.
32. If Red Hat Enterprise Linux, SUSE LINUX Enterprise Server 10, or SUSE LINUX Enterprise Server 11 is used, make sure that the HDLM device is allocated to the swap partition. Make sure that the HDLM device name is displayed in the Filename column of the /proc/swaps file.
kernel /xen-pae.gz module /vmlinuz-2.6.16.60-0.54.5-xenpae \ root=/dev/disk/by-id/scsi-SFUJITSU_MAS3735NC_A050P360007Npart6 vga=0x317 \ resume=/dev/disk/by-id/scsiSFUJITSU_MAS3735NC_A050P3600077-part2 \ splash=silent showopts multipath=off module /initrd-2.6.16.60-0.54.5-xenpae multipath=off is set in the underlined section. ¢ When GRUB is used as the boot loader with non-Xen kernels: For details on kernels supported by HDLM, see Hosts and OSs Supported by HDLM on page 3-3.
Figure 3-9 Example of Executing the mount Command on page 3-126 shows an example of executing the mount command. Figure 3-9 Example of Executing the mount Command The shaded portion indicates the SCSI device for which LABEL is set. This example assumes that IA32 uses GRUB as the boot loader. When you use IPF that uses ELILO as the boot loader, the mount point is displayed as /boot/efi instead of /boot (in the line where /boot is coded), and the file system type is displayed as vfat instead of ext3.
¢ For SUSE LINUX Enterprise Server 10 or SUSE LINUX Enterprise Server 11 Execute the udevinfo command. Specify the device name (udev name) in the /dev/disk directory for -n. # udevinfo -q name -n /dev/disk/by-id/scsi-2000c50fffecb6ae0part1 sda1 The sda1 value output is the SCSI device name corresponding to / dev/disk/by-id/scsi-2000c50fffecb6ae0-part1. 6. Edit the /etc/fstab file to remove the LABEL setting. The detailed procedure is explained in steps 7 and 8.
procedure differs depending on whether the host is restarted after installation. In steps 12 to 27 that follow, you will edit the configuration file to change the definition so that the OS starts with HDLM specified. 11. Execute the HDLM-configuration definition utility (dlmcfgmgr) with the -v parameter specified to check the correspondence between the HDLM device and the SCSI device.
a. Change hdlm_dracut=n defined in the /etc/opt/ DynamicLinkManager/hdlm.conf file to hdlm_dracut=y. b. Execute the dracut command. The following shows an example of executing the command: # /sbin/dracut /boot/initramfs-hdlm-2.6.32-71.el6.i686.img `uname -r` ¢ For OSs other than the above: Execute the utility for supporting a boot disk (dlmmkinitrd). For details on the dlmmkinitrd utility, see dlmmkinitrd Utility for Supporting a Boot Disk on page 7-31.
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. Comment out the existing SCSI device specification by placing a hash mark (#) at the beginning of each line, and then add the HDLM device specification as shown below, based on the correspondence between the HDLM device and the SCSI device as checked in step 11.
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.
23. Shut down the host. 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.
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.
2. Make sure that the HDLM device is defined in the /etc/fstab file. /dev/sddlmaa1 : : /boot : : 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. Edit the /etc/lvm/lvm.conf file so that the LVM2 recognizes the SCSI device, not the HDLM device. Figure 3-15 Example of Editing /etc/lvm/lvm.conf file on page 3-138 shows an example of editing the /etc/lvm/lvm.conf file.
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-139, Figure 3-17 Example of Editing /boot/grub/menu.
Figure 3-16 Example of Editing /etc/grub.conf file Edit the shaded portion. Figure 3-17 Example of Editing /boot/grub/menu.lst file (When using a kernel that supports Xen) Edit the shaded portion.
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. ¢ ¢ If you will use GRUB as the boot loader Change title. If you will use ELILO as the boot loader Change label. 11. Specify root as the name of the device mounted to / in the /etc/fstab file.
¢ When ELILO is the boot loader Specify label for default. 15. Shut down the host. Execute the following command to shut down the host: # shutdown -h now 16. Change the configuration from a multi-path configuration to a single-path configuration. 17. Start the host. 18. Execute the mount command to check that the SCSI device is mounted in /boot.
21. Perform an upgrade installation of HDLM. To perform an upgrade installation of HDLM, see Performing an Upgrade Installation of HDLM on page 3-91, perform steps 2 to 12 to create an HDLM device. You will also need to perform step 13 if you are only restarting the host. Note that the procedure differs depending on whether the host is restarted after installation. 22. Execute the dlmcfgmgr utility with the -v parameter specified to check the correspondence between the HDLM device and the SCSI device.
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. Figure 3-19 Example of Editing /etc/lvm/lvm.conf file on page 3-143 shows examples of editing the /etc/lvm/lvm.conf file. Figure 3-19 Example of Editing /etc/lvm/lvm.conf file Comment out the existing filter and types lines, and add the shaded lines in the figure. Set 0 in md_component_detection.
If the initial RAM disk image file to be created already exists and you are using Red Hat Enterprise Linux AS4/ES4 or Red Hat Enterprise Linux 5, specify the -f parameter to overwrite this file. If you are using SUSE LINUX Enterprise Server 10 or SUSE LINUX Enterprise Server 11, this file is overwritten even if you do not specify the parameter. For details on the dlmmkinitrd utility, see dlmmkinitrd Utility for Supporting a Boot Disk on page 7-31.
¢ ¢ 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.
/dev/mapper/systemvg-rootlv on / type ext4 (rw) 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.
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.
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. Execute the HDLM-configuration definition utility (dlmcfgmgr) with the -v parameter specified to check the correspondence between the SCSI device and the HDLM device.
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. Unmap the SCSI device from the device used by the device mapper. The following shows an example of unmapping the SCSI device from the /dev/mapper/luks-volume1 device. # cryptsetup luksClose luks-volume1 # 5. Map the device used by device mapper to the HDLM device.
• In mdadm package versions 1.6.0-2 or earlier, you cannot manage devices whose major or minor number is 256 or greater. Use mdadm package versions 1.6.0-3 or later. • You cannot simultaneously specify SCSI devices and HDLM devices to configure an md device. Figure 3-23 Example of Incorrectly Configured md Devices on page 3-155 shows an example when SCSI devices and HDLM devices are simultaneously specified by mistake.
During this procedure, /dev/md0 is created on /dev/sddlmaa1 and /dev/ sddlmab1. Use the following procedure to configure the environment shown in Figure 3-25 Device Configuration When Creating an md Device on an HDLM Device on page 3-156. Figure 3-25 Device Configuration When Creating an md Device on an HDLM Device To create an md device: 1. Create a disk partition. Specify the disk partition type 83 when you create a disk partition.
/dev/sddlmaa1 1 1018 5238597 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.
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. Execute the following command to deactivate the md device. # mdadm -Ss /dev/md0 11. Make sure that the md device has been deactivated. In the following example, RAID1 (mirroring) is used for the md device: # cat /proc/mdstat Personalities : [raid1] unused devices: Make sure that md0 : active is not displayed. 12. Install HDLM. Perform steps 2 to 11 in Performing a New Installation of HDLM on page 3-79.
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. In this procedure, the device /dev/md0 on /dev/sdo1 and /dev/sdh1 is migrated to the device /dev/md0 on /dev/sddlmaa1. Use the following procedure to configure the environment shown in Figure 3-27 Device Configuration Where an md Device (An Environment that Uses the md Device's MULTIPATH Function) on a SCSI Device Is Migrated to an md Device on an HDLM Device on page 3-163.
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. The HDevName and Device columns display HDLM devices and SCSI devices, respectively. 7. Create an md device. Based on the correspondence between the HDLM devices and SCSI devices checked in step 6, create an md device.
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.conf file to add auto=yes to the ARRAY line in the configuration file: DEVICE /dev/sdo1 /dev/sdh1 ARRAY /dev/md0 level=linear num-devices=1 UUID=426a9f1c: 9cfa6310:6aa9a80b:11ea2102 auto=yes 11.
Settings for LVM2 This section describes the procedure for setting the following items in an LVM2 environment: • When using an HDLM device to create a new logical volume • When moving a logical volume created on a SCSI device in a single-path environment, to an HDLM device When using HDLM in an LVM2 environment, use the HDLM device as an LVM2 physical volume.
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-168 Creating an HDLM Environment Hitachi Dynamic Link Manager User Guide (for Linux(R))
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.
Figure 3-30 Device Configuration When a Logical Volume on a SCSI Device Is Moved to an HDLM Device In Figure 3-30 Device Configuration When a Logical Volume on a SCSI Device Is Moved to an HDLM Device on page 3-172, sdn indicates the different LUs. sddlmad1 and sddlmad2 indicate the HDLM devices corresponding to each LU. To move the logical volume to an HDLM device: 1. Make sure that HDLM has been installed. Execute the rpm command to make sure that HDLM has been installed. # rpm -q HDLM HDLM-x.x.x.x.
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. In the following example, the logical volume to be moved belongs to the vg01 volume group: # vgchange -an vg01 0 logical volume(s) in volume group "vg01" now active 6. Export the volume group. In the following example, the command exports information about the vg01 volume group: # vgexport vg01 Volume group "vg01" successfully exported 7.
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 or the Hitachi AMS2000/AMS/WMS/SMS series is being used: (number-of-paths-connected-to-Oracle-Cluster-file-System-2 x 30 seconds / 2) + 1 When a host and an Oracle RAC voting disk are connected by multiple paths, HDLM performs failover processing for those paths (in the same way as for normal paths) when an I/O timeout occurs for one of the paths.
Table 3-56 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.
# /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.
Executing the following command to start the service: # service ccsd start # service cman start # service rgmanager start When Using Red Hat Enterprise Linux 5, or Red Hat Enterprise Linux 6 To specify settings for RHCM: 1. Stop the service of the RHCM cluster. Stop the RHCM service with the following command if the service is running: # service rgmanager stop # service cman stop 2. Change the SCSI device being used by RHCM to an HDLM device.
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. Stop the cluster service of VCS. 2. Change the SCSI device used by VCS to an HDLM device. Change the Block Devices parameter of the Mount resource from the SCSI device to an HDLM device. 3. Start the cluster service of VCS.
# /opt/DynamicLinkManager/bin/dlnkmgr view -drv > redirectdestination-file-2 Open redirect-destination-file-2 and check the HDevName and Device entries to see whether the HDLM device corresponding to the SCSI device has been created. Setting Up HDLM HDLM includes functions like the load balancing function, the automatic failback function, the error logging function, the audit logging function, etc. You can set up these functions by using the dlnkmgr command's set operation.
Table 3-57 The Recommended and Default Values of Each Function Function Load-balancing Default value Recommended value on on The Extended Least I/Os algorithm is used. The recommended algorithm depends on the operating environment. on on 30-minute check interval The recommended checking interval depends on the operating environment. on 1-minute check interval The recommended checking interval depends on the operating environment.
• lio for the Least I/Os algorithm • exlio for the Extended Least I/Os algorithm • lbk for the Least Blocks. algorithm • exlbk for the Extended Least Blocks algorithm The type of algorithm specified by the -lbtype parameter remains stored in the system, even if, you disable the load balancing function by specifying -lb off.
# /opt/DynamicLinkManager/bin/dlnkmgr set -afb on -intvl 10 To enable automatic failback, specify on. Specify off otherwise. When you specify on, you can use the -intvl parameter to specify the checking interval can be specified with the -intvl parameter when on is specified. The value that was specified previously will be applied if the checking interval is not specified. For example, specify auto failback as off after specifying the checking interval to five minutes and executing.
Setting the Error Log Collection Level The error log (the HDLM manager log (dlmmgrn.log (n indicates a file number from 1 to 16)) collection level can be set. Table 3-58 Values for the Error Log Collection Level Setting on page 3-188 lists and describes the values for the error log collection level setting. Table 3-58 Values for the Error Log Collection Level Setting Value Description 0 No error logs are collected. 1 All information for errors of the "Error" level or higher is collected.
Value 4 Description All information is output. If an error occurs, you might have to set the trace level to 1 or higher to collect any trace information. The higher this value is set, the more information that will be output. As the amount of trace information to be output increases, it will take less time to overwrite the old trace information with the new information. For normal operation, we recommend that you set the trace level to 0.
# /opt/DynamicLinkManager/bin/dlnkmgr set -elfn 5 Specify the number of error log files by a number. Setting the Trace File Size Trace files for which a trace file size can be set are hdlmtrn.log (n indicates a file number from 1 to 64). The length of a trace file is fixed, regardless of how much trace information is actually in the file. For the trace file size, you can specify a value (in kilobytes) from 100 to 16000.
Table 3-60 Values Indicating Audit Log Data Collection Levels on page 3-191 describes the values that indicate audit log data collection levels. An audit log data collection level is a severity level. The default is 6. Table 3-60 Values Indicating Audit Log Data Collection Levels Value (severity) 0 Explanation No audit log data is collected. 1 2 Critical-level audit log data is collected. 3 Critical-level and Error-level audit log data is collected.
If you want to specify the output destination for audit log data, first specify the audit log facility by using the dlnkmgr set -audfac command. Next, define the output destination of the facility in the /etc/syslog.conf file. Table 3-62 Values Indicating Audit Log Facility on page 3-192 describes the values that indicate audit log facility. The default is user. Table 3-62 Values Indicating Audit Log Facility Value Corresponding facility value in the /etc/syslog.
view, completion time = yyyy/mm/dd hh:mm:ss # After you have set up the collection of audit log data, use the following command to make sure that the setting has been specified correctly: # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -audlog Audit Log : on(6) Audit Log Category : all Audit Log Facility : local0 KAPL01001-I The HDLM command completed normally.
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. The character-type device file created by using an udev rule file is not deleted when the host is restarted.
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. Note that the file systems supported by HDLM are ext2, ext3, ReiserFS, and VxFS. For details about creating a file system, see Creating a File System on page 3-195. 2. Create a directory on which to mount the 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.
/dev/sddlmaa ¢ /mnt/sda ext2 defaults 0 0 For IP-SAN environments • If the OS is Red Hat Enterprise Linux 5.6, Red Hat Enterprise Linux 5.6 Advanced Platform, Red Hat Enterprise Linux 5.7, Red Hat Enterprise Linux 5.7 Advanced Platform, or Red Hat Enterprise Linux 6: /dev/sddlmaa • /mnt/sda ext2 _netdev 0 0 If the OS is SUSE LINUX Enterprise Server 11: /dev/sddlmaa /mnt/sda ext2 nofail 0 0 This example adds a line for /dev/sddlmaa (name of the logical device file of the HDLM device).
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. In the /etc/fstab file, change the logical device file name for a SCSI device to that for the HDLM device that you confirmed in step 1. The following is an example of editing the /etc/fstab file: ¢ For FC-SAN environments # /dev/sda /dev/sddlmaa ¢ /mnt/sda /mnt/sda ext2 ext2 defaults defaults 0 0 0 0 For IP-SAN environments • If the OS is Red Hat Enterprise Linux 5.
Figure 3-36 Overview of HDLM Uninstallation # Perform as required. Operations on HDLM-Managed Devices The following procedure must be performed before uninstalling HDLM: 1. Back up all HDLM-managed devices as required (for example, using a tape backup). 2. Collect all information on the correspondence between logical device file names for the HDLM devices and LU numbers of the LUs in the storage system.
For details on how to cancel the Xen settings, see Canceling the Xen Settings on page 3-203. 5. Cancel the KVM settings. Delete the HDLM devices from the hardware configuration file. For details on how to cancel the KVM settings, see Canceling the KVM Settings on page 3-204. 6. Unmount the HDLM device. If HDLM-managed devices have been mounted by specifying HDLM devices, unmount them. Also, if the disks are set to be mounted automatically when the host starts, delete this setting in the /etc/fstab file.
If a SCSI device that is subordinate to an HDLM device is being used as a file system resource, edit the settings as shown in the following example: # host1 172.26.4.321 Filesystem::/dev/sddlmaa::/mnt/point::ext3 host1 172.26.4.321 Filesystem::/dev/sda::/mnt/point::ext3 In this example, the HDLM device /dev/sddlmaa is commented out, and the SCSI device /dev/sda is added. 3. Start the Heartbeat service in the cluster. Execute the following command to start the Heartbeat service: # /etc/init.
Edit as shown below to use the SCSI device /dev/sda, which is the lower SCSI device of the HDLM device/dev/sddlmaa, as /dev/raw/raw1. # /dev/raw/raw1 /dev/sddlmaa /dev/raw/raw1 /dev/sda Comment out /dev/sddlmaa and add /dev/sda. 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. Start the cluster service of RHCM.
# /sbin/start_udev 6. Start the cluster service of RHCM. Executing the following command to start the service: # service cman start # service rgmanager start Canceling the Settings for VCS This section describes how to cancel the HDLM device settings in VCS in an environment where VCS is used. For details on how to perform operations from the VCS GUI, see the VCS documentation. To cancel the HDLM settings in an environment where VCS is used: 1. Stop the cluster service of VCS. 2.
In the following example, the domU configuration information is checked from the management domain: # /usr/sbin/xm list -l domU : : (device (vbd (uuid 6b393aaa-89e7-44dc-7a57-24d477dee43d) (bootable 0) (driver paravirtualised) (dev sdx) (uname phy:/dev/sddlmaa) (mode w) ) ) : : The HDLM device displayed on the uname phy line is an HDLM device that appeared in the check in step 1. 3. If domainU is running, stop it.
Id Name State ---------------------------------1 domK running The underlined part indicates the domain name. 2. If the guest OS is running, stop it. For details on how to stop the guest OS, see the OS documentation. 3. If necessary, delete the HDLM device from the hardware configuration file. If you want to delete the HDLM device (/dev/sddlmac), delete the following lines: 4.
To create the environment shown in Figure 3-37 Device Configuration When a Logical Volume on an HDLM Device Is Moved to a SCSI Device on page 3-206, carry out the procedure below. To uninstall HDLM, carry out the steps before the uninstallation. Figure 3-37 Device Configuration When a Logical Volume on an HDLM Device Is Moved to a SCSI Device In Figure 3-37 Device Configuration When a Logical Volume on an HDLM Device Is Moved to a SCSI Device on page 3-206, sda1, sdb1, sdc1, and sdd1 indicate the same LU.
# vgchange -an vg01 0 logical volume(s) in volume group "vg01" now active 4. Export the volume group. 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.
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-210, carry out the procedure below. To uninstall HDLM, carry out the steps before the uninstallation. Figure 3-39 Device Configuration When an md Device on an HDLM Device Is Moved to a SCSI Device (An Environment that Uses the md Device's RAID Functionality) To migrate /dev/md0: 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-209. 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-209, [linear] will be displayed until the host is restarted. However, there are no operational problems. Canceling the LUKS Settings This subsection describes how to migrate LUKS from a HDLM device environment using LUKS to SCSI devices. To migrate from /dev/sddlmaa to /dev/sdh: 1. Change the multi-path configuration to a single-path configuration. 2.
Uninstalling HDLM Note ¢ ¢ If the system initiates path health checking or automatic failback while HDLM is being uninstalled, an error message (KAPL04023) might be output to syslog. However, HDLM operations are not affected. If you uninstall HDLM, the error logs (/var/tmp/hdlminstlog/ installhdlm[01-10].log) generated during installation of HDLM are not uninstalled. 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-199, and then perform steps 2 and 3 in Uninstalling HDLM on page 3-217 so that the HDLM devices can no longer be used. 6. Execute the uninstall command. Execute the following command to uninstall HDLM: # rpm -e HDLM 7. Make sure that the uninstall processing has finished. Execute the following command to make sure that the uninstall processing has finished.
Root directory (/), /boot, /tmp, /usr, /var, swap ¢ When LILO is used as the boot loader: Root directory (/), /tmp, /usr, /var, swap ¢ When LVM2 is used: /boot The following shows an example of the /etc/fstab file: /dev/sddlmaa2 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.
#/dev/sddlmaa2 /dev/sda2 / / ext2 ext2 : : defaults defaults 1 1 1 1 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. Figure 3-43 Example of Editing /etc/lvm/lvm.conf file on page 3-220 show examples of editing the /etc/lvm/lvm.conf file. Figure 3-43 Example of Editing /etc/lvm/lvm.
boot=/dev/sda map=/boot/map install=/boot/boot.b prompt timeout=50 linear #default=HDLM_194.EL default=linux image=/boot/vmlinuz-2.6.18-194.el5 label=HDLM_194.EL initrd=/boot/initrd-hdlm-2.6.18-194.el5.gz read-only append="option ramdisk_size=18245 option" image=/boot/vmlinuz-2.6.18-194.el5 label=linux initrd=/boot/initrd-2.6.18-194.el5 read-only append="option" root=/dev/sda2 ¢ When the boot loader is GRUB Example 1 below shows an example of editing the /etc/grub.conf file (the underlined sections).
default 1 timeout 8 gfxmenu (hd0,1)/boot/message title XEN-hdlm root (hd0,1) kernel /boot/xen.gz module /boot/vmlinuz-2.6.16.60-0.21-xen vga=0x31a splash=silent showopts module /boot/initrd-2.6.16.60-0.21-xen.hdlm title XEN-sd root (hd0,1) kernel /boot/xen.gz module /boot/vmlinuz-2.6.16.60-0.21-xen root=/dev/sda2 vga=0x31a splash=silent showopts module /boot/initrd-2.6.16.60-0.21-xen ¢ When the boot loader is ELILO running on an IPF host An example of editing the /etc/elilo.
title Red Hat Enterprise Linux AS (2.6.9-11.EL) root (hd1,0) kernel /vmlinuz-2.6.9-11.EL ro root=/dev/VolGroup00/ LogVol00 rhgb quiet # initrd /initrd-hdlm-2.6.9-11.EL.img initrd /initrd-2.6.9-11.EL.img 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.
15. Make sure that the SCSI device is used by the file system and the swap partition. Make sure of the following three things: that the root directory is associated with the SCSI device, that the SCSI device is mounted, and that the SCSI device is assigned to the swap partition. ¢ When the boot loader is LILO or GRUB Figure 3-44 Example of Executing the mount Command When the Boot Loader Is LILO or GRUB on page 3-224 shows an example of executing the mount command.
Execute the following command to make sure that the physical volumes that make up the volume group are not HDLM devices. 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.
Execute the following command and make sure that 0 is displayed for Used for sddlmfdrv: # /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-199, and then perform steps 2 and 3 in Uninstalling HDLM on page 3-217 so that the HDLM devices can no longer be used. 21. Uninstall HDLM. To uninstall HDLM, execute the following command: # rpm -e HDLM 22.
Unsetup is complete. If HNTRLib2 is being used by another program: HNTRLib2 will not be uninstalled, and the following message will appear. Because a bundle PP name is registered, I did not do the Uninstall. If HNTRLib2 was not uninstalled, execute the following command to check if any programs are using it.
3-228 Creating an HDLM Environment Hitachi Dynamic Link Manager User Guide (for Linux(R))
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.
• You cannot execute the partprobe command for HDLM devices because this command does not support HDLM devices. If you want to add a partition to or delete a partition from an HDLM device (LU), first stop all applications that are using the target HDLM device (LU) so that the HDLM device (LU) is not being used#. If you add or delete a partition while an HDLM device (LU) is being used, restart the host to reload the partition table.
• 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. Unmount any devices mounted on the HDLM device. b. Execute the dlmcfgmgr -o command to exclude the HDLM device from management. • HDLM devices cannot be used to create an md device.
• If you execute the sync command on the file system that is mounted by ext3/ReiserFS, the following message is output to syslog, but there is no problem with HDLM operations. JBD: barrier-based sync failed on sddlmaa1 - disabling barriers • Before you update the OS SP, uninstall HDLM. After you have updated the OS SP, re-install HDLM. For details on HDLM installation and uninstallation, see Installing HDLM on page 3-75 and Uninstalling HDLM on page 3-216.
• HDLM devices cannot be used to create an md device. • If you execute the sync command on the file system that is mounted by ext3/ReiserFS, the following message is output to syslog, but there is no problem with HDLM operations.
Table 4-1 HDLM Installation Environments in Which Kernel Packages Can Be Updated or OS Update Packages Applied on page 4-9 shows the HDLM installation environments in which kernel packages can be updated or OS update packages applied.
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-116. Environment Where a Logical Volume (LVM2) on an HDLM Device Is Used as the Boot Disk To update a kernel package or apply an OS update package when a logical volume (LVM2) on an HDLM device is used as the boot disk: 1. Perform the procedure in Performing a Re-installation of HDLM on page 3-86. 2.
# /opt/DynamicLinkManager/bin/dlnkmgr view -path To display information only for the paths accessing the specified host device, execute the dlnkmgr command's view operation with the -path and -hdev parameters specified. The following example shows how to execute the command: For details on the displayed items and their descriptions, see view (Displays Information) on page 6-28. Changing the Status of Paths This section explains how to change path statuses.
KAPL01057-I All the paths which pass the specified HBA will be changed to the Online status. Is this OK? [y/n]:y KAPL01061-I 3 path(s) were successfully placed Online; 0 path(s) were not. Operation name = online # 3. Check to see if the statuses of all the applicable paths have changed. The following is an example of executing the command: # /opt/DynamicLinkManager/bin/dlnkmgr view -path Changing the Status of Paths to Offline(C) To change the status of paths to Offline(C): 1.
The following is an example of executing the command: # /opt/DynamicLinkManager/bin/dlnkmgr view -path Viewing LU Information This section explains how to display LU information by using an HDLM command. To display LU information, execute the dlnkmgr command's view operation with the -lu parameter specified.
the -drv parameter specified. For details on the view operation, see view (Displays Information) on page 6-28. The execution result of this operation is displayed on a single line for each path. The following is an example of executing the dlnkmgr command's view operation: # /opt/DynamicLinkManager/bin/dlnkmgr view -drv PathID HDevName Device LDEV 000000 sddlmaa /dev/sdag 9970/9980.15001.05B7 000001 sddlmaa /dev/sdq 9970/9980.15001.05B7 000002 sddlmab /dev/sdr 9970/9980.15001.
# 3. Check to see whether the statistical information for all the paths has been initialized. The following is an example of executing the command: # /opt/DynamicLinkManager/bin/dlnkmgr view -path Viewing and Setting Up the Operating Environment This section explains how to display and set up the HDLM operating environment. Viewing the Operating Environment To display the operating environment, execute the dlnkmgr command's view operation with the -sys and -sfunc parameters specified.
Setting Up the Operating Environment To set up the HDLM operating environment, execute the dlnkmgr command's set operation.
For details on the displayed items and their descriptions, see view (Displays Information) on page 6-28. Updating the License This section explains how to update the license. To update the license, execute the dlnkmgr command's set operation with the -lic parameter specified. When the confirmation message is displayed, enter y to execute, or n to cancel the command. If the license key file does not exist, a message asking you to enter the license key appears, so enter the license key.
Path Health Checking : on(30) Auto Failback : on(1) Reservation Status : Intermittent Error Monitor : off HDLM Manager Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.x-xx yyyy/mm/dd hh:mm:ss 1000 HDLM Driver Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss LicenseType Expiration Permanent KAPL01001-I The HDLM command completed normally.
Also, you can view information for each HDLM component. Execute the dlnkmgr command's view operation with the -sys and subsequent parameter specified.
Use the dlnkmgr command's view operation: Execute the following command: # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -msrv HDLM Manager Ver WakeupTime Alive x.x.x-xx yyyy/mm/dd hh:mm:ss KAPL01001-I The HDLM command completed normally. operation name = view, completion time = yyyy/mm/dd hh:mm:ss # When the HDLM Manager column shows Alive, the HDLM manager is active. Use a script for confirmation: Execute the following command to confirm that the HDLM manager is active: # /etc/init.
= view, completion time = yyyy/mm/dd hh:mm:ss # When the HDLM Manager column shows Dead, the HDLM manager is inactive. Use a script for confirmation: Execute the following command to confirm that the HDLM manager is inactive: # /etc/init.d/DLMManager status dlmmgr is stopped. Note If an error occurs, the execution results of the dlnkmgr command's view operation might be different from those of the DLMManager status command. In this case, see the execution results of the dlnkmgr command.
• Add devices to or remove devices from the list of devices to be managed by HDLM Replacing HBAs You can replace HBAs without stopping any applications when all of the following conditions are satisfied: • The OS on the host is either of the following: ¢ Red Hat Enterprise Linux 5 ¢ Red Hat Enterprise Linux 6 • The host allows HBA replacement, and the new HBAs are of the same type as the HBAs you replace.
# chmod 755 /etc/sysconfig/modules/acpiphp.modules Finally, after the chmod command has been executed, confirm that the execution permissions have been set as indicated by the underlined portion below. # ls –l /etc/sysconfig/modules/acpiphp.modules -rwxr-xr-x 1 root root 35 mm dd hh:mm /etc/sysconfig/modules/ acpiphp.modules 3. Load the acpiphp module. Execute the acpiphp.modules file you created in step 2. # /etc/sysconfig/modules/acpiphp.
The following steps assume that the HBAs whose WWN information is underlined above are to be replaced. 2. Execute the view operation of the dlnkmgr command (dlnkmgr view path -hbaportwwn) to check the information about the paths that pass through the HBAs you want to replace. See the port WWN information of the HBAs you checked in step 1 and HBAPortWWN displayed as the execution result to check the host port number and the bus number displayed in PathName.
4. Replace the HBAs. 5. Execute the dlmcfgmgr utility (dlmcfgmgr -r) to change the HDLM device configuration. # dlmcfgmgr –r 6. Execute the view operation of the dlnkmgr command (dlnkmgr view path -hbaportwwn) to confirm that the new paths have been added. In the above figure, new paths that have been added are indicated by shading.
8. Execute the dlmcfgmgr utility (dlmcfgmgr -u) to delete the information about the old paths and SCSI devices. In the -u parameter, specify an HDevName device for which old SCSI device information is displayed in step 9. Note that you need to execute the utility for each HDevName device that contains old SCSI device information. The following shows an example of the command you execute if the HDevName value is /dev/sddlmaa: # dlmcfgmgr -u /dev/sddlmaa 9.
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.
# dlmcfgmgr -v 5. Execute the view operation of the dlnkmgr command (dlnkmgr view path -hbaportwwn) to confirm that all the information about the paths that were placed in Offline(E) status has been deleted.
For example, to place in Offline (C) status the path that goes through the HBA with host port number 0001 and bus number 0000, execute the following command: # /opt/DynamicLinkManager/bin/dlnkmgr offline -hba 0001.0000 While the path that goes through the HBA with host port number 0001 is placed Offline, the status of the path that goes through the HBA with host port number 0002 is Online. Figure 4-3 When the Status of the Path That Goes Through the Fiber Cable to Be Replaced Is Offline(C) 2.
For example, execute the following command: # /opt/DynamicLinkManager/bin/dlnkmgr view -path For details about the path information, see view (Displays Information) on page 6-28. Replacing the Fibre Channel Switch If there are multiple online paths for a device in an LU, you can replace a desired Fibre Channel switch while running your applications by placing offline only the path that goes through the Fibre Channel switch to be replaced, and using other paths to continue accesses.
For example, to place in Offline (C) status the path that goes through the HBA with host port number 0001 and bus number 0000, execute the following command: # /opt/DynamicLinkManager/bin/dlnkmgr offline -hba 0001.0000 While the path that goes through the HBA with host port number 0001 is placed Offline, the status of the path that goes through the HBA with host port number 0002 is Online. Figure 4-5 When the Status of the Path That Goes Through the Fibre Channel Switch to Be Replaced Is Offline(C) 2.
# /opt/DynamicLinkManager/bin/dlnkmgr view -path For details about the path information, see view (Displays Information) on page 6-28. Changing the HDLM Device Configuration This section describes the actions and procedures to change the HDLM device configuration. To set up or change (add, change or delete) an LU in a storage system, use the management program of the storage system, rather than the HDLM functionality.
• When the dlmcfgmgr utility is executed to change the HDLM device configuration, memory might become insufficient due to the HAL daemon#. In this case, the host will not respond. To avoid this, stop the HAL daemon when executing the dlmcfgmgr utility. For details on how to stop the HAL daemon, see Notes on Installing HDLM on page 3-73. # The HAL daemon detects hardware configuration changes, for example, when a USB device or CD-ROM is inserted.
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 - Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 6 and a Brocade HBA driver - SUSE LINUX Enterprise Server and a Brocade HBA driver Execute the following command: # echo "- - -" > /sys/class/scsi_host/hostn/scan Execute the following command to check whether the OS has recognized any devices: # cat /proc/scsi/scsi 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/
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). Based on the SCSI device created in step 3, an HDLM device for the path configured in step 1 is added.
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. While restarting, the additional path configured in the above step 1 is automatically added as a path to the relevant HDLM device. 6. Refer to /var/opt/DynamicLinkManager/log/dlmcfgmgr1.
Make sure that all the SCSI device names corresponding to the LU for which path allocations were cancelled in step 2 are represented with a hyphen (-) (optional). The following is an example of executing the dlmcfgmgr utility with the -v option: # /sbin/dlmcfgmgr -v The following is an example of executing the view operation with the -drv option: # /opt/DynamicLinkManager/bin/dlnkmgr view -drv 8.
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). Check if the SCSI device name of the HDLM device whose path was deleted in the above step 2 is represented with a hyphen (-).
# /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. Execute the HDLM-configuration definition utility (dlmcfgmgr -v) to check if the device you want to exclude from HDLM management is being managed by HDLM.
HDLM. Perform this operation if necessary. If it is not necessary to check this, go to step 3. 3. Execute the dlmcfgmgr utility (dlmcfgmgr ilogical_device_file_name_of_HDLM_device ) on the relevant device you want to HDLM to manage. The specified device is managed by HDLM. The following is an example of executing the dlmcfgmgr utility: # /sbin/dlmcfgmgr -i name-of-logical-device-file-for-HDLM-device 4. Refer to /var/opt/DynamicLinkManager/log/dlmcfgmgr1.
2. Connect the cable. If the cable is broken, replace it. 3. Restart the host on which the HDLM is installed. The SCSI device is recreated, the path to the HDLM device, which was determined in step 1 to be in disconnected status when the host was started, is restored automatically, and the status changes to online. 4. Refer to /var/opt/DynamicLinkManager/log/dlmcfgmgr1.log or execute the dlmcfgmgr utility (dlmcfgmgr -v) to check if the path to the relevant HDLM device is 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 Table 4-4 Add SCSI Devices on page 4-43, to manually create the SCSI device.
Purpose Command If you are using Red Hat Enterprise Linux 5, Red Hat Enterprise Linux 6, SUSE LINUX Enterprise Server 10, or SUSE LINUX Enterprise Server 11, the devices might be automatically recognized by the OS hot plug function. If the devices are recognized, the above procedure is not necessary.
# /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.
detected path is already registered and a situation where a new HDLM device is created. If the SCSI device of the new path that HDLM detected is already registered, the HDLM device mapped with the path already registered is allocated. For example, if the path between the host and an LU of the storage system already exists and a new path is added, the HDLM device that already exists is allocated to the path.
device(s) not in use (or, represented with a hyphen (-)) to release the available name(s) to create an HDLM device file for the new LU. Even if you add a path to an HDLM device that is not managed by HDLM and restart the host, the HDLM device will not be managed by HDLM. An AutoPATH_ID is allocated sequentially as the HDLM recognizes a SCSI device during start up of the host. Therefore, an AutoPATH_ID for the same path may change whenever the host starts.
4-48 HDLM Operation Hitachi Dynamic Link Manager User Guide (for Linux(R))
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.
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 Figure 5-2 Troubleshooting Procedure When a Path Error Occurs on page 5-4 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 to narrow down the hardware in which an error has occurred.
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. Figure 5-3 Troubleshooting Procedure When a Program Error Occurs on page 5-6 shows the troubleshooting procedure.
What To Do for the Program Error Follow the recommended actions for messages in 8 Messages on page 8-1. If the error occurs again after you thought that you had resolved the problem, use the dlnkmgr command's view operation to check the status of the HDLM program, and then do whatever is necessary to resolve the problem. For details on the view operation, see view (Displays Information) on page 6-28.
5-8 Troubleshooting Hitachi Dynamic Link Manager User Guide (for Linux(R))
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.
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.
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. Format /opt/DynamicLinkManager/bin/dlnkmgr help [operation] [operation] ...
# Example 2 The following example shows how to display the formats of multiple operations. # /opt/DynamicLinkManager/bin/dlnkmgr help online offline help online: Format dlnkmgr online [-path] [-s] dlnkmgr online [-path] -hba HBAPortNumber.
Placing too many paths offline might prevent paths from being able to switch if an error occurs. Before placing a path offline, use the view operation to check how many online paths remain. For details about the view operation, see view (Displays Information) on page 6-28. Format To place paths offline /opt/DynamicLinkManager/bin/dlnkmgr offline [-path] {-hba host-port-number.
When the confirmation message is displayed, the user enters y to continue, or n to cancel the operation. # /opt/DynamicLinkManager/bin/dlnkmgr offline -hba 0010.0000 KAPL01055-I All the paths which pass the specified HBA will be changed to the Offline(C) status. Is this OK? [y/n]:y KAPL01056-I If you are sure that there would be no problem when all the paths which pass the specified HBA are placed in the Offline(C) status, enter y. Otherwise, enter n.
Specify the current AutoPATH_ID of the target path, which is displayed by using the view operation. For details about the view operation, see view (Displays Information) on page 6-28. Leading zeros can be omitted (000001 and 1 indicate the same AutoPATH_ID); however, when the target AutoPATH_ID is 000000, enter 000000 or 0 for the parameter value. AutoPATH_IDs are re-assigned every time the host is restarted.
KAPL01061-I 1 path(s) were successfully placed Offline(C); 0 path(s) were not. Operation name = offline # To Display the Format of the Offline Operation -help Displays the format of the offline operation. Example The following example shows how to display the format of the offline operation: # /opt/DynamicLinkManager/bin/dlnkmgr offline -help offline: Format dlnkmgr offline [-path] -hba HBAPortNumber.
# /opt/DynamicLinkManager/bin/dlnkmgr view -path -stname | grep 9500V | grep 0A The above command will display information pertaining to only those paths that pass through the specified CHA port. online (Places Paths Online) The dlnkmgr command's online operation places offline paths online. Specify the paths to be placed online by specifying an HBA port, CHA port, or single path. Instead of specifying a path, you can also specify a SCSI device name.
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-28.
will be changed to the Online status. Is this OK? [y/n]:y KAPL01061-I 2 path(s) were successfully placed Online; 0 path(s) were not. Operation name = online # -pathid AutoPATH_ID Use this parameter to place a single path online. Specify the current AutoPATH_ID of the target path, which is displayed by using the view operation. For details about the view operation, see view (Displays Information) on page 6-28.
The following example shows how to place a path, whose AutoPATH_ID is 000002, online without asking for confirmation of command execution from the user: # /opt/DynamicLinkManager/bin/dlnkmgr online -pathid 2 -s KAPL01061-I 1 path(s) were successfully placed Online; 0 path(s) were not. Operation name = online # To Display the Format of the Online Operation -help Displays the format of the online operation.
Example 2 The following example shows how to filter and display the information on all paths that pass through the CHA port 0A of the Thunder 9500V series: # /opt/DynamicLinkManager/bin/dlnkmgr view -path -stname | grep 9500V | grep 0A The above command will display information pertaining to only those paths that pass through the specified CHA port. 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 Table 6-2 Default and Recommended Values on page 6-15 shows the defaults and recommended values for each setting. If you change the value of the set operation, the new value takes effect immediately. Table 6-2 Default and Recommended Values Item name Load balancing Default value Recommended value on on The Extended Least I/Os algorithm is used. The recommended algorithm depends on the operating environment.
-lbtype {rr|exrr|lio|exlio|lbk|exlbk} Specify the algorithm to be used for load balancing. rr: The Round Robin algorithm exrr: The Extended Round Robin algorithm lio: The Least I/Os algorithm exlio: The Extended Least I/Os algorithm lbk: The Least Blocks algorithm exlbk: The Extended Least Blocks algorithm The type of algorithm specified by the -lbtype parameter remains stored in the system, even when you disable the load balancing function by specifying -lb off.
-elfs error-log-file-size Specify a value from 100 to 2,000,000 (in KB) for the size of the error log files (dlmmgrn.log (n indicates a file number from 1 to 16)). The specified files size is applied to HDLM manager logs. By specifying both the error log file size and the number of error log files, you can collect up to 32,000,000 KB (approximately 30 GB) of error logs in total.
Trace files for which the trace file size can be set are hdlmtrn.log (where n is a value from 1 to 64). The length of a trace file is fixed. Therefore, even if the amount of written trace information is less than the set file size, the file size of each output trace file is always fixed. When trace data is written to all trace files, new trace data overwrites old trace data (the oldest file is overwritten first). -systfn number-of-trace-files Specify a value from 2 to 64 for the number of trace log files.
not change the interval, the path health interval stored in the system is used. -afb {on [-intvl checking-interval]|off} Enables or disables automatic failback. on: Enabled off: Disabled Enabling automatic failbacks might automatically place paths online that were intentionally placed offline (for example, paths placed offline for maintenance work).
intermittent-error-monitoring If this condition is not satisfied, the KAPL01080-W message will be output and an error will occur. If this happens, change any of the following settings: the checking interval for automatic failbacks, the intermittent error-monitoring interval, or the number of times that the error is to occur. When you set the number of times that the error is to occur to 1, the above condition does not need to be satisfied.
When a value of 2 or more is specified for the number of times, the following condition must be satisfied: error-monitoring-interval >= checking-interval-for-automaticfailback x number-of-times-error-is-to-occur-during-intermittenterror-monitoring If this condition is not satisfied, the KAPL01080-W message will be output and an error will occur.
completes. When intermittent error monitoring is not being performed, the number of errors that determine that an intermittent error has occurred is not counted and this value is not changed. The number of times that the error is to occur is stored in the system, even when -iem off is specified and intermittent error monitoring is disabled.
Setting AFB IEM Available operation Change the IEM settings. Set IEM to off. off off on#2 off Result of operation • When a path is not being monitored, nothing changes. • While a path is being monitored, the value of the error count and the elapsed monitoring time are reset to 0, and then intermittent error monitoring will restart.
# /opt/DynamicLinkManager/bin/dlnkmgr set -iem on -intvl 20 iemnum 2 KAPL01049-I Would you like to execute the operation? Operation name = set [y/n]: y KAPL01001-I The HDLM command completed normally. Operation name = set, completion time = yyyy/mm/dd hh:mm:ss # -lic Specify this option for when a license is updated. The HDLM license is provided via a license key or license key file. A license key file is a file that stores the HDLM license key.
The following example shows how to update the license key when the license key file exists: # /opt/DynamicLinkManager/bin/dlnkmgr set -lic KAPL01049-I Would you like to execute the operation? Operation name = set [y/n]: y KAPL01071-I A permanent license was installed.
-category [[ss] [a] [ca]|all] Specifies the categories of audit log data to be collected. Table 6-8 Values Indicating Audit Log Data Categories on page 6-26 describes the values that indicate categories of audit log data. The default is all. If you specify the -category parameter without specifying a value, all is assumed. Table 6-8 Values Indicating Audit Log Data Categories Value Explanation ss Audit log events of the StartStop category are collected.
-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. To Display the Format of the Set Operation -help Displays the format of the set operation.
Number-Of-Times AudlogLevel Category-Value all) Facility-Name { 1 - 99 }(Times) (Default Value 3) { 0 - 7 } (Default Value 6) { [ss] [a] [ca] | all } (Default Value { user | local0 - local7 } (Default Value user) Facility-Number { 1 | 16 - 23 } (Default Value 1) Number-Of-PathUseTimes { 0 - 999999 }(Times) (Default Value 32) KAPL01001-I The HDLM command completed normally.
To display path information (by abbreviating the list items) /opt/DynamicLinkManager/bin/dlnkmgr view -path -c [-stname] [-srt {lu|cp}] [-t] To Display LU Information To display LU information /opt/DynamicLinkManager/bin/dlnkmgr view -lu [-hdev host-device-name|-pathid AutoPATH_ID] [-t] To display LU information (by selecting items to be displayed) /opt/DynamicLinkManager/bin/dlnkmgr view -lu -item [ [slpr] [pn] [cp] [clpr] [type] [ic] [ie] [dnu] [iep] [hctl]|all] [-hdev host-device-name|-pathid AutoPATH_
To display path information on page 6-36 To display LU information on page 6-47 To display corresponding information about an HDLM device, SCSI device, and LDEV on page 6-55 To display the format of the view operation on page 6-57 To display program information -sys [-sfunc|-msrv|-adrv|-pdrv|-lic|-audlog|-lbpathusetimes] Displays the HDLM program information. Use one of the sub-parameters (following -sys) to specify the program information that you want to display.
Parameter and program information to be displayed Item Description extended lbk: The Extended Least Blocks algorithm Support Cluster Blank# Elog Level Error logging level: • 0: Collects no error information. • 1: Collects error information at the Error level or higher. • 2: Collects error information at the Warning level or higher. • 3: Collects error information at the Information level or higher.
Parameter and program information to be displayed Item Description • Checking interval: When the setting of the automatic failback is on, the checking interval of automatic failback is displayed within the parentheses following on. The time is in minutes.
Parameter and program information to be displayed -lic Item Description Ver Version number of the HDLM driver WakeupTime Startup time of the HDLM driver License Type License type Information about the HDLM license Expiration • Permanent • Temporary • Emergency License expiration: When using a permanent license: When using a temporary license or emergency license: The license expiration period is displayed in the format: yyyy/mm/dd (ndays after).
Parameter and program information to be displayed Item Description If the collection of audit log data is disabled, a hyphen (-) is displayed. lbpathusetime s The number of times the same path can be used for load balancing Times Same Path Was Used 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.
KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss # Example 3 The following example shows how to display information about the HDLM alert driver: # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -adrv HDLM Alert Driver Ver WakeupTime ElogMem Size Alive x.x.x-xx yyyy/mm/dd hh:mm:ss 1000 KAPL01001-I The HDLM command completed normally.
The following example shows how to display the number of times the same path can be used for load balancing: # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -lbpathusetimes Times Same Path Was Used : 32 KAPL01001-I The HDLM command completed normally.
-iem Use this parameter to add IEP to path information and display information about intermittent errors. -srt {pn|lu|cp} Use this parameter to sort the path information in ascending order, according to the specified sorting keys. The sorting keys are as follows: the first sorting key is the name of the storage system (DskName), the second sorting key is the value specified by the -srt parameter, and the third sorting key is AutoPATH_ID.
displayed by the dlnkmgr view -path -item command and the parameter values for displaying each item.
Use this parameter to display the model ID of the storage system in the product ID element of the DskName field. When this parameter is omitted, the command displays the product ID or emulation type of the storage system instead. For details about the information to be displayed for product IDs, see Table 6-14 Product ID displayed by the view -path operation on page 6-46. When you use this parameter, DskName is displayed by default. It is not necessary to specify dn for the -item parameter.
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-42.
For details about the information about product IDs, see Table 6-14 Product ID displayed by the view -path operation on page 6-46. -srt {lu|cp} Use this parameter to sort the path information in ascending order, according to the specified sorting key. The sorting keys are as follows: the first sorting key is the name of the storage system (DskName), the second sorting key is the value specified by the -srt parameter, and the third sorting key is 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# 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 IEP# Description Summary displayed Information about the intermittent error. - This item is displayed only when you specify -iem with the -path parameter. One of the following values is displayed for each path: • Indicates that intermittent error monitoring is disabled or the monitoring time for an intermittent error is out of range. • A value of at least 0 Indicates the number of errors that occurred during intermittent error monitoring.
Table 6-14 Product ID displayed by the view -path operation Product ID Model names of storage systems Thunder 9500V series Without the -stname parameter product identifier# With the -stname parameter (Displays the following for the model name) 9500V Hitachi AMS2000 series AMS Hitachi AMS AMS Hitachi SMS SMS Hitachi WMS WMS Lightning 9900 series Emulation type# 9910/9960 Lightning 9900V series 9970/9980 SVS SVS • Hitachi NSC55 • Hitachi Universal Storage Platform 100 • Hitachi Univers
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 All items are displayed all In the sub-parameters, -hdev or -pathid, you can filter the LU information to be displayed. If you omit both parameters, the command displays the information about all the LUs recognized by HDLM. For details on the contents of each displayed item, see Table 6-17 LU Information on page 6-51.
To display a summary of LU information -lu -c When the -c parameter is specified with the -lu parameter, a summary of LU configuration information is displayed on one line. The total number of paths recognized by HDLM and the number of online paths are displayed for each LU. You cannot specify the -c parameter together with the -hdev or -pathid parameter. For details on the contents of each display item, see Table 6-17 LU Information on page 6-51. -t Omits the title for each information item.
The sub-parameter is: -t Omits the title for each information item. Example The following example shows how to display a summary of LU information, and selecting the items to be displayed. Execute the following command to display SLPR: Items of LU information Table 6-17 LU Information on page 6-51 describes the displayed LU information. The following explains the table headings: • No summary displayed: The user specifies the -lu parameter or -lu item parameter.
Displayed item No summary displayed Description Summary displayed characters are the internal LU number within the CU. • For HP XP10000/HP XP12000, P9500, and SVS, indicated by a hexadecimal number. The first three characters of iLU are the CU number, and the last two characters are the internal LU number within the CU.The first character of a CU number is 0. • For the Thunder 9500V series, and Hitachi AMS2000/AMS/WMS/SMS series, indicated by a decimal number.
Displayed item No summary displayed PathID Description Summary displayed - 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 determined by referring to What To Do for a Path Error on page 5-3. Type#1 - Attribute of the path • Own: Owner path • Non: Non-owner path When connecting to Lightning 9900 series, Lightning 9900V series, Hitachi USP, Universal Storage Platform V/VM, Virtual Storage Platform, Hitachi AMS2000 series, or Hitachi SMS, all paths are owner paths. IO-Count#1 - Total I/O count for a path.
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.
Using this parameter displays the PathID, the HDLM device, SCSI device for the HDLM device, and information on the LDEV in the storage system (storage system model name, serial number, and LU number, separated by period). For details on the contents of each display item, see Table 6-18 To display corresponding information about an HDLM device, SCSI device, and LDEV on page 6-56. -t Does not display the title for each information item.
000004 sddlmad 9970/9980.15001.05B2 000005 sddlmae /dev/sdu 9970/9980.15001.05B3 000006 sddlmaf /dev/sdv 9970/9980.15001.05B4 000007 sddlmag /dev/sdw 9970/9980.15001.05B5 000008 sddlmah /dev/sdx 9970/9980.15001.05B6 KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss # To display the format of the view operation -help Use this parameter to display the view operation format.
6-58 Command Reference Hitachi Dynamic Link Manager User Guide (for Linux(R))
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.
This utility performs a new installation, upgrade installation, or reinstallation of HDLM. For details on the installhdlm utility, see installhdlm Utility for Installing HDLM on page 7-41. For details about how to perform an unattended installation, see Installing HDLM on page 3-75. • The installux.sh utility for HDLM Common Installer HDLM will be installed on, and installs the corresponding version of HDLM from the DVD-ROM.
Format /opt/DynamicLinkManager/bin/DLMgetras {directory-to-which-collectedinformation-is-output [-f file-that-defines-information-to-be-collected]|-h} You can also use lower-case characters (dlmgetras instead of DLMgetras) as follows: /opt/DynamicLinkManager/bin/dlmgetras {directory-to-which-collectedinformation-is-output [-f file-that-defines-information-to-be-collected]|-h} Parameters directory-to-which-collected-information-is-output Specify the output directory for the information that is to be collec
• 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. • Only one file or directory can be specified per line. • The root directory (/) cannot be specified. • When a directory is specified, the DLMgetras utility collects all the files in that directory, including files contained in the directory's subdirectories.
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.tar.gz This file contains compressed error information of the Hitachi Command Suite products other than HDLM.
Output directory#1 /var/VRTSvcs/log Files 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 Explanation Red Hat Enterprise Linux 5, or SUSE LINUX Enterprise Server 9) OpenAIS settings file /etc/ais openais.conf /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 Files Explanation .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 dlmmgr.xml Manager setting information dlmwebagent.proper Hitachi Command Suite Common ties Agent Component settings file hdlm.conf iSCSI system configuration information file hdlmboot*.
Output directory#1 Files Explanation /etc/sysconfig/hdlmscripts All subdirectories and HDLM-related script files /etc/sysconfig/mkinitrd All subdirectories and initrd related file (when using Red files Hat Enterprise Linux 5) /etc/sysconfig/network ifcfg-eth* NIC network information /etc/sysconfig/networkscripts ifcfg-eth* NIC network information /etc/syslog-ng syslog-ng.
Output directory#1 Files Explanation 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 Information about the partitions recognized by the kernel pci PCI de
Output directory#1 /proc/xen Files balloon capabilities Xen-related information (when using SUSE LINUX Enterprise Server 10 or SUSE LINUX Enterprise Server 11) /sys/class/fc_host All subdirectories and Fibre Channel switch information files (when using Red Hat Enterprise Linux, SUSE LINUX Enterprise Server 10, or SUSE LINUX Enterprise Server 11) /sys/class/ fc_remote_ports All subdirectories and Fibre Channel switch information files (when using Red Hat Enterprise Linux 5, Red Hat Enterprise Linux 6,
Output directory#1 /var/opt/ DynamicLinkManager/log Files dlmmgr1.log : Explanation HDLM manager log (including the driver log) dlmmgr16.log dlmwebagent[1N].log #3 Hitachi Command Suite Common Agent Component log files dlminquiry.log Inquiry information log dlmcfgmgr1.log, dlmcfgmgr utility log dlmcfgmgr2.log .dlmomtrace1.log On-memory trace log .dlmomtrace2.log : .dlmomtrace5.log dlnkmgr2.log Process-specific-trace information file hdlmtr1.log Trace file dlnkmgr1.log, : hdlmtr64.
Table 7-4 Information Stored in the getras.tar.gz File, which Is Recorded by the OS and HDLM Commands When the DLMgetras Utility Is Executed Executed command 7-16 Files Explanation /bin/df bdf.txt Disk usage of the file system /bin/dmesg dmesg.txt System diagnostic message /bin/ls -altR /dev dev_dsk.txt List of disks to be handled as a block-type device /bin/ls -altR /dev/raw dev_raw.txt List of disks to be handled as a character-type device /bin/ls -altR /etc/rc.d rc.
Executed command Files Explanation information (when using Red Hat Enterprise Linux) /bin/rpm -qai rpm-qai.txt List of installed packages /bin/rpm -qlv HDLM HDLM_rpm-qlv.txt HDLM package file information /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.
Executed command Files Explanation /opt/DynamicLinkManager/ bin/dlnkmgr view -sys pdrv, /opt/DynamicLinkManager/ bin/dlnkmgr view -sys -lic, /opt/DynamicLinkManager/ bin/dlnkmgr view -sys audlog, /opt/DynamicLinkManager/ bin/dlnkmgr view -sys lbpathusetimes 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.
Executed command Files Explanation Enterprise Linux 5, Red Hat Enterprise Linux 6, or SUSE LINUX Enterprise Server 11) /sbin/lilo -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 /usr/bin/virsh list --all virsh-list.txt KVM guest OS information (when using Red Hat 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.
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.
dlmcfgmgr utility with the -r parameter specified, the HDLM partition information will be lost from /proc/partitions. To restore the information, follow these steps: • 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.
For SUSE LINUX Enterprise Server 10 or SUSE LINUX Enterprise Server 11 /opt/DynamicLinkManager/bin/dlmmkinitrd [-i initrd-image] [-b boot-directory] [-h] Parameters For Red Hat Enterprise Linux AS4/ES4 or Red Hat Enterprise Linux 5 -v Specify this parameter to output a log to the console during execution of the dlmmkinitrd utility. -f Specify this parameter to create an initial RAM disk image file that has the same name as an existing file.
Example: The name of the initial RAM disk image file for the vmlinuz-2.6.16.46-0.14-bigsmp kernel is initrd-2.6.16.46-0.14bigsmp.hdlm. -i initrd-image Specify the name of the initial RAM disk image file to be created by using the dlmmkinitrd utility. This parameter is used to create an initial RAM disk image file with a name other than the default file name (initrdversion.hdlm).
Specify this parameter to display the reservation key. The following explains the items displayed when the -k parameter is specified: Reservation Key If the reservation key is not set, [0x0000000000000000] is displayed. Regist Key The registered keys are displayed. Key Count The number of registered keys is displayed. -c Specify this parameter to clear the reservation key. sdn Specify the SCSI device (sdn) for which you want to display or clear the reservation key. You can specify more than one SCSI device.
3. The confirmation message appears. Enter y to clear. Otherwise, enter n. KAPL10641-I Reservation Key will now be cleared. Is this OK? [y/n]:y KAPL10642-I Reservation Key of sdb was cleared. KAPL10642-I Reservation Key of sdc was cleared. Note • Before executing the dlmpr utility, make sure that the LU for which persistent reservation will be cleared is not being accessed.
allocation fails, the KAPL05708-E message is output to syslog and to the HDLM manager log file. retrycount Specify a numeric value from -1 to 2,147,483,646. -1 : The system retries until memory is allocated. This is the initial value of the system. 0 : The system does not retry. 1 to 2,147,483,646: The system retries the specified number of times.
1 to 2,147,483,646: The system retries the specified number of times. If the following values are specified, the KAPL12553-W message is displayed and then processing ends: • Value of -1 or less • Value more than 2,147,483,646 • Non-numeric value -h Displays the format of the dlmsetopt utility for setting the HDLM driver option.
Table 7-8 conf files used by the dlmsetopt utility OS Red Hat Enterprise Linux AS4/ES4 File Name /etc/modprobe.conf Red Hat Enterprise Linux 5 SUSE LINUX Enterprise Server Red Hat Enterprise Linux 6 • /etc/modprobe.d/dlmdrvopt.conf If you use the dlmsetopt utility in an environment where an HDLM device is used for the boot disk, after changing the settings, you need to recreate the initial RAM disk image file.
Notes: • You cannot execute multiple instances of the dlmstart utility at the same time. • You cannot execute the dlmstart utility while the dlmcfgmgr utility is executing. • If you execute the dlmstart utility while one or more HDLM devices are mounted, an error message (KAPL05023-E) is output to the syslog. However, HDLM operations are not affected.
rc.d/rc.sysinit KAPL13502-I The utility for update system scripts completed successfully. Example 2 In this example, the utility was executed but there was no need to reregister the HDLM information: # /opt/DynamicLinkManager/bin/dlmupdatesysinit KAPL13501-I The utility for update system scripts started. KAPL13502-I The utility for update system scripts completed successfully.
page 7-41 describes the detailed information contained in installgetras.tar.gz. Table 7-10 Information Contained in installgetras.tar.gz Output directory# File Description output-directory-ofcollected-informationspecified-when-executingthe- -installgetras-utility installgetras.
For details about the installation-information settings file, see Editing an Installation-Information Settings File on page 7-42. Editing an Installation-Information Settings File This section describes how to edit the installation-information settings file. How to Edit an Installation-Information Settings File Keep the following in mind when you edit an installation-information settings file: • Enter keys in the order of the keys defined in the sample file sample_installhdlm.conf.
Necessity of definition Key name Description New installati on Maxim um Upgrade numbe installati r of on or re- charac installati ters on The default is /var/tmp/ hdlm_license. If you perform an upgrade installation or re-installation without updating the license, delete the licensekeyfile key and value.
a. License key file (/var/tmp/hdlm_license) b. File containing the license key (/etc/opt/DynamicLinkManager/ dlm.lic_key) If none of these files exist when you attempt to perform a new installation, the KAPL09011-E and KAPL09212-E message is output. If you specify a value for either the licensekey or licensekeyfile key, the specified file will not be deleted after the installhdlm utility is executed.
Necessity of definition Key name#1 load_balance_type Description#2 Specify one of the following values to indicate the load balancing algorithm: New installa tion Maxim Upgrad um e numbe installa r of tion or charac reters installa tion Optional Optional 5 Optional Optional 6 Optional Optional 1 Optional Optional 7 Optional Optional 2 Optional Optional 1 Optional Optional 5 rr: The Round Robin algorithm exrr: The Extended Round Robin algorithm lio: The Least I/Os algorithm exlio:
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 You can set a size from 100 to 16000. The default is 1000. trace_file_number Optional Optional 2 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.
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 You can specify a check interval from 1 to 1440. The default is 30. intermittent_error _monitor_number Optional Specify the number of times an error occurs. You can specify a value from 1 to 99. The default is 3. Optional 2 Legend: Optional: If a key and its setting are not specified, the installer uses the default.
error_log_size=9900 error_log_number=2 trace_level=0 trace_file_size=1000 trace_file_number=4 path_health_check=on path_health_check_interval=30 auto_failback=on auto_failback_interval=1 # intermittent_error_monitor=off # intermittent_error_monitor_interval=210 # intermittent_error_monitor_number=3 installux.sh Utility for HDLM Common Installer This utility determines what OS HDLM will be installed on, and installs the corresponding version of HDLM from the DVD-ROM.
Note The hdlm_installux_sh.log and hdlm_installux_sh2.log log files are not deleted when HDLM is uninstalled. Manually delete the log files, if they are no longer required.
7-50 Utility Reference Hitachi Dynamic Link Manager User Guide (for Linux(R))
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-134.
□ KAPL15001 to KAPL16000 □ Return Codes for Hitachi Command Suite Common Agent Component 8-2 Messages Hitachi Dynamic Link Manager User Guide (for Linux(R))
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 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-28. 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-28. 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-28. ¢ view operation Refer to 3 Creating an HDLM Environment on page 3-1. Creating an HDLM Environment or Reconfiguring the HDLM Operating Environment on page 4-21, and then configure any paths that exist.
Message ID Message Text Explanation view (Displays Information) on page 6-28. KAPL01024-W The specified parameters cannot Details be specified at the same time. aa...aa: clear, offline, online, Operation name = aa...aa, set, or view parameters = bb...bb bb...bb: Parameters that cannot be specified at the same time Action Execute help operation of the 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-14. 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-5. 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/Offline(C). aa...aa: Online or Offline(C) Action Use the view operation of the HDLM command (dlnkmgr) to check the status of the path. For details on the view operation, see view (Displays Information) on page 6-28. 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-5.
Message ID KAPL01073-E Message Text The temporary license expired. Explanation Details The temporary license has expired. Register a permanent license. Action Register a permanent license. KAPL01074-E The emergency license expired. Details The emergency license has expired. Register a permanent license. Action Register a permanent license. KAPL01075-E A fatal error occurred in HDLM. The system environment is invalid. Details The license information file is missing. Action Re-install HDLM.
Message ID KAPL01081-E Message Text The license key file is invalid. File name = aa...aa Explanation Details The format of the license key file is invalid. aa...aa: /var/tmp/hdlm_license Action Save the correct license key file in the designated, and then reexecute. /var/tmp/hdlm_license KAPL01082-E There is no installable license key in the license key file. File name = aa...aa Details There is no useable license key for HDLM in the license key file. aa...
Message ID Message Text Explanation Execute help operation-name of the HDLM command (dlnkmgr) to check which parameter can be specified, and then retry. For details on the help operation, see help (Displays the Operation Format) on page 6-4. KAPL01089-E One of the following was executed at the same time as an HDLM command set -lic operation: another set -lic operation, or an update of the license for an update installation. Action Check the license by using the HDLM command's view -sys -lic operation.
Message ID Message Text Explanation company for which you have a service contract. KAPL01097-W All the current trace files will be deleted. Is this OK? [y/n] Details If you set a value that is less than the current value of the trace file size or number of trace files, all the current trace files will be deleted. To continue the operation, enter y. To cancel the operation, enter n. Action If you want to execute the operation of the HDLM command, enter y. If you want to terminate processing, enter n.
Message ID Message Text Explanation If you did not perform HDLM configuration, Perform HDLM configuration. When performing neither of the above, or if the same error continues to occur even after one of the above procedures is performed, execute the utility for collecting HDLM error information (DLMgetras) to collect the error information, and then contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM.
Message ID Message Text Explanation The audit log configuration file is Manager, and execute the invalid. "dlnkmgr view -sys -audlog" command and check the setting. Action Restart the HDLM Manager, and execute the dlnkmgr view -sys -audlog command, and then specify the desired setting by using the dlnkmgr set -audlog command or the dlnkmgr set audfac command as necessary. KAPL01117-W An error occurred during processing to read the audit log configuration file.
Message ID Message Text Explanation 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. KAPL01123-W You do not have read permission for the file. File name = aa...aa Details aa...aa: / etc/.
Message ID Message Text Explanation and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see clear (Returns the Path Statistics to the Initial Value) on page 6-3. KAPL01128-W HNTRLib2 initialization failed. Trace per process information cannot be collected. Details HNTRLib2 initialization failed. Integrated trace information cannot be collected. Action Execute the HDLM command as a user who has root permissions.
Message ID Message Text Explanation contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL03004-C A critical error occurred in the HDLM API. (aa...aa) Details This information is required for resolving problems. aa...
Message ID Message Text Explanation HDLM Error Information on page 7-3. KAPL03008-E An error occurred during log input to the HDLM alert driver. (aa...aa) 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.
Message ID Message Text Explanation and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL04003-E The startup parameter is invalid. Details The HDLM manager internal parameter is invalid.
Message ID Message Text Explanation Use the dlnkmgr set operation to return options settings back to where you had them. If the KAPL04033-W message is not output, restart HDLM manager. If the same error occurs, re-install HDLM. For details on the view operation, see view (Displays Information) on page 6-28. For details on the set operation, see set (Sets Up the Operating Environment) on page 6-14. KAPL04010-E Could not open the error log file.
Message ID Message Text Explanation HDLM Error Information on page 7-3. KAPL04013-E Input is impossible via the communication pipe. RC = aa...aa Details Data could not be read from the pipe file while communicating with an HDLM command. aa...aa: OS error code (decimal (base-10) number) Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
Message ID Message Text Explanation HDLM Error Information on page 7-3. KAPL04021-I HDLM manager information aa...aa Details This information is required for resolving problems. 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...
Message ID Message Text Explanation and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL04025-C A memory shortage occurred in 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.
Message ID Message Text Explanation KAPL04033-W The option definition file was re- Details created. When an existing option definition file cannot be read, a new option definition file will be re-created by using the default values. If some of the options can be read, those values can be used. 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.
Message ID KAPL04045-I Message Text HDLM SNMP TRAP was sent. Trap ID = aa...aa, IP Address = bb...bb, Port Number= cc...cc, Community = dd...dd, Trap Data = ee...ee Explanation Details aa...aa: Trap ID bb...bb: Destination IP address of the trap cc...cc: Destination port number of the trap dd...dd: Community name given to the trap ee...ee: Transmission data Action None. KAPL04047-W The file does not exist. File name = aa...aa Details aa...aa: / etc/.DynamicLinkManager/ Path00 Action Reinstall HDLM.
Message ID Message Text Explanation aa...aa: /HDLM installation path/bin/.dlnkmgr_exe Action Reinstall HDLM. KAPL04052-E You do not have execute permission for the file. File name = aa...aa Details aa...aa: /HDLM installation path/bin/.dlnkmgr_exe 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 how to execute the DLMgetras utility. KAPL05011-E Explanation Execute the utility for setting HDLM driver option (dlmsetopt) and increase the number of retries for allocating memory. For details on the dlmsetopt utility, see dlmsetopt Utility for Setting HDLM Driver Options on page 7-35. Increase system memory. Stop any unnecessary processes.
Message ID Message Text Explanation None. Details KAPL05018-W The FO processing in the path (aa...aa) failed. (bb...bb:cc...cc) An attempt at FO processing for Check the connection status of path aa...aa has failed. the path aa...aa. If there is no aa...aa: Core logic path identifier problem with the connection for the failed FO (hexadecimal status, execute the DLMgetras number) utility to collect error information, and then contact bb...
Message ID Message Text Explanation An attempt to process the Check the message of the HDLM requested IOCTL call has failed. command or the HDLM manager, and then take the aa...aa: IOCTL code (hexadecimal appropriate action. If you do not number) know the appropriate action, bb...bb: Error code (hexadecimal execute the DLMgetras utility to number) collect error information, and then contact your vendor or cc...cc: Thread ID of the process maintenance company.
Message ID KAPL05704-E Message Text Explanation Details The LDEV information for an HDLM device has changed. HCTL The LDEV information for the value = aa...aa bb...bb cc...cc HCTL value corresponding to an dd...dd HDLM device has changed. LDEV information (storage system model name, serial number, and LU number, separated by period) aa...aa: Host ID (host port number) (decimal number) bb...bb: Channel number (bus number) (decimal number) cc...cc: Target ID (target ID) (decimal number) dd...
Message ID Message Text Explanation Driver Options on page 7-35. Increase system memory. Stop any unnecessary processes. If the problem is not solved, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL05709-I The system will retry to allocate memory aa...aa times.
Message ID Message Text Explanation bb...bb: Maintenance information (hexadecimal number) cc...cc: Maintenance information (hexadecimal number) dd...dd: Maintenance information (hexadecimal number) Action None. KAPL06001 to KAPL07000 Message ID KAPL06004-E Message Text Could not allocate memory. (aa...aa:bb...bb) Explanation Details An attempt to reserve memory to save alert information has failed. aa...aa: Program line (hexadecimal number) bb...
Message ID Message Text Explanation Action None. KAPL06009-I Invalid IOCTL(aa...aa) was received. The processing is canceled. Details A request having an invalid IOCTL code aa...aa was issued to the alert driver. aa...aa: IOCTL code (hexadecimal number) Action None. KAPL06010-E Could not process the Details IOCTL(aa...aa). (bb...bb:cc...cc) An IOCTL request was not processed normally. aa...aa: IOCTL code (hexadecimal number) bb...bb: Error number (hexadecimal number) cc...
Message ID Message Text Explanation Check whether any other error occurred. The information that could not be written is discarded. Review the actual memory size when another error does not occur. When the actual memory size is insufficient, increase the actual memory size. When 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.
Message ID Message Text does not match the currently booting kernel version. Explanation The version of the kernel supported by the installed HDLM is different from the currently running kernel version. It may be that you booted the kernel that is different from the kernel when you installed HDLM. Action Install an HDLM that supports the currently running kernel. KAPL06101-E The HDLM file is invalid. File name = aa...
Message ID Message Text Explanation An error occurred in the path. The error is most likely due to a disconnected cable. aa...aa: Path identifier (hexadecimal number) bb...bb: Error code (hexadecimal number) ¢ When a path error is detected by a path health checking or the online operation Displays 0x000F0000 (Fixed). ¢ 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.
Message ID Message Text Explanation hh...hh: Host device name (same as HDevName of view -path) Action There could be an error in the path. See What To Do for a Path Error on page 5-3 and restore the path displayed in the message to running status. 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...
Message ID Message Text Explanation because the system judged that an intermittent error was occurring in that path. aa...aa: Path ID (same as PathID of view -path) (decimal (base-10) number) Action An intermittent error has occurred. Check the path for any possible problems. 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.
Message ID Message Text Explanation installation program or the uninstallation program. KAPL09011-E Cannot find a license key file / etc/opt/DynamicLinkManager/ dlm.lic_key. Details The license key file, /etc/opt/ DynamicLinkManager/ dlm.lic_key, cannot be found in the specified directory. Action Create a license key file, and reexecute the installation program. KAPL09013-E Some HDLM drivers could not be Details removed.
Message ID KAPL09023-E Message Text Explanation Network Objectplaza Trace Library 2 failed. Action A file or directory related to HDLM could not be found. Reinstall HDLM. Details Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM. A target file to copy to the directory of Hitachi Command Suite products other than HDLM could not be found among the files related to HDLM. Action Re-install HDLM.
Message ID Message Text Explanation Execute the /etc/init.d/ DLMManager command with the start parameter to start the HDLM manager. KAPL09037-E KAPL09038-E The status of the HDLM manager could not be checked. If the HDLM manager does not start, execute the /etc/init.d/ DLMManager command with the start parameter to start the HDLM manager. Details The HDLM configuration could not be deleted. Details An attempt to acquire the status of the HDLM manager has failed.
Message ID KAPL09044-I Message Text The uninstallation of aa...aa completed successfully. Explanation Details HDLM was uninstalled. aa...aa: Name of uninstalled file. Action None. KAPL09045-E An attempt to create a file or directory related to HDLM has failed. Make sure that sufficient disk space exists, and then reinstall HDLM. Details Installation could not be executed because an attempt to create an HDLM-related file or directory failed.
Message ID Message Text Explanation Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM. KAPL09051-E You do not have permission to execute the file. File name = aa...aa Details Installation or uninstallation failed because there was no execution permission for a file. aa...aa: File name Action Make sure you can execute the file shown in aa...aa. KAPL09076-I The permanent license was installed. Details The permanent license was installed. Action None.
Message ID Message Text Explanation aa...aa: Year (4 digits)/month (01-12)/day (01-31) Action Install a permanent license by the expiration day. KAPL09082-W The temporary license expired. Action Enter a permanent license key. KAPL09083-W The emergency license expired. Action Install a permanent license. KAPL09087-E Details The entered license key is invalid. Renewal of the license License renewal will now stop key will now stop.
Message ID KAPL09093-I Message Text aa...aa will be installed. Is this OK? [y/n]: Explanation Details The message checks whether you want to install aa...aa. aa...aa: The version of HDLM to be installed, or the version of the HDLM SP to be installed Action Please enter "y" to install, and "n" to abort the installation. KAPL09094-W The entered value is invalid. Re- Details enter [y/n]: The message checks whether you want to correct an invalid value. Action Please enter "y" or "n".
Message ID KAPL09113-E Message Text There is no installable license key in the license key file. File name = aa...aa Explanation Details There is no HDLM-installable license key in the license key file. Make sure that the license key aa...aa: /var/tmp/hdlm_license file is correct, and then re-install Action HDLM. Make sure that the license key file is correct, and then re-install HDLM. /var/tmp/hdlm_license KAPL09114-I There is no license key file. File name = aa...
Message ID Message Text Explanation the DVD-ROM was copied, make sure that all the contents of the DVD-ROM have been copied to that directory, and then retry the installation. KAPL09135-E One of the following was executed at the same time as an HDLM command set -lic operation: another set -lic operation, or an update of the license for an update installation. Action Check the license by using the HDLM command's view -sys lic operation.
Message ID Message Text Explanation after creating the directory displayed in the message. KAPL09147-E KAPL09160-E An attempt to create a file related to HDLM has failed. File name = aa...aa. Remove unnecessary files and secure free space on the file system. Check the write permissions for the directory. Re-install HDLM. Details HDLM does not support this kernel. Install HDLM on a supported OS. Details aa...
Message ID Message Text Explanation Check the HDLM installation media, or check the current kernel. KAPL09177-I HDLM version: aa...aa Details aa...aa: The version of HDLM to be installed. Action None. KAPL09191-W The installation information settings file does not exist. Details The installation information settings file specified for the second parameter does not exist. Action Make sure that the path name of the installation-information settings file is appropriate, and then try again.
Message ID Message Text Explanation aa...aa: installhdlm, installhdlm_analysis, ENVIRONMENT_SETTINGS, driver_config_settings, or dlmcfgmgr Action None. KAPL09211-I aa...aa completed successfully. Details aa...aa completed successfully. aa...aa: installhdlm, installhdlm_analysis, ENVIRONMENT_SETTINGS, driver_config_settings, or dlmcfgmgr Action None. KAPL09212-E aa...aa ended abnormally. Details aa...aa ended abnormally. aa...
Message ID Message Text Explanation aa...aa: Error number (decimal number) that specifies the executed processing Action If the error code is 4: The /var/tmp directory does not have enough unused capacity, or the user does not have write permission for it. Make sure there is enough unused capacity and that the user has write permission for this directory, and then try again.
Message ID KAPL09217-E Message Text An error occurred during reading of the installation information settings file. Error Code = aa...aa,bb...bb Explanation Details An error occurred while reading the installation information settings file. aa...aa: Error number (decimal number) that specifies the executed processing bb...bb: Return value (decimal number) of the executed processing Action If the error code is 9001,-1: You do not have read permissions for the installation information settings file.
Message ID Message Text Explanation the required files to the correct location, and then retry the operation. If you do not have a required permission, grant required permissions to yourself, and then retry the operation. If aa...aa is dlmcfgmgr: The correct location of dlmcfgmgr is /sbin. If dlnkmgr was not in the correct location, or you did not have a required permission, re-execute installhdlm. KAPL09219-E An internal error occurred in the Details installhdlm_analysis.
Message ID Message Text Explanation aa...aa: Error number (decimal number) that specifies the executed processing bb...bb: Return value (decimal number) of the executed processing cc...cc: Line number (decimal number) of an installation information settings file. Action Specify the revised installation information settings file, and then retry the operation. KAPL09227-W The definition of the installation Details information settings file includes A key that does not exist is an invalid key.
Message ID Message Text Code = aa...aa,bb...bb, line = cc...cc Explanation aa...aa: Error number (decimal number) that specifies the executed processing bb...bb: Return value (decimal number) of the executed processing cc...cc: Line number (decimal number) of an installation information settings file. Action Specify the revised installation information settings file and then retry the operation.
Message ID Message Text Explanation aa...aa: Error number (decimal number) that specifies the executed processing bb...bb: Return value (decimal number) of the executed processing cc...cc: Line number (decimal number) of an installation information settings file. Action Specify the revised installation information settings file and then retry the operation. KAPL09233-W The definition of the installation information settings file is too long. Error Code = aa...aa,bb...bb, line = cc...
Message ID KAPL09239-I Message Text The system will now restart. Explanation Details The host will restart because restart was specified in the installation information settings file. Action None. KAPL09240-I There is no license key file. File Details name = aa...aa If you want to There is no license key file. update the HDLM license, create aa...aa: dlm.lic_key a license key file (referring to the HDLM installation Action instructions in the user's guide, None.
Message ID Message Text Explanation vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL09269-W The file is invalid. File name = aa...aa Details aa...aa: / etc/.DynamicLinkManager/ Path00, /etc/.HBaseAgent/ Path00 Action Reinstall HDLM. KAPL09270-E The directory does not exist. Directory name = aa...aa Details aa...
Message ID Message Text Explanation 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. Details The version of the SP being installed is the same as the already installed SP. Installation of the SP has stopped. aa...aa: Version of the SP being installed Action You do not have to install the SP. Keep using HDLM as is. KAPL09510-E Service Pack aa...aa cannot be installed.
Message ID Message Text Explanation If an installation is performed from the DVD-ROM, confirm that the DVD-ROM is not damaged. If an installation is performed by using files copied from the DVDROM, re-copy all of the DVD-ROM files. KAPL09603-E The installation will now stop because a command or utility cannot be executed. Confirm that the command or utility (aa...aa) exists, and that you have the proper permission. Details aa...aa: Name of the command or utility that cannot be executed.
Message ID Message Text Explanation Action Check the parameters of the DLMgetras utility for collecting HDLM error information, and then retry. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL10002-W Too many parameters have been specified. Details Four or more parameters have been specified. Action Check the parameters of the DLMgetras utility for collecting HDLM error information, and then retry.
Message ID Message Text KAPL10005-W The number of parameters is insufficient. Explanation 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. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3.
Message ID Message Text Explanation 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. To overwrite the directory, enter y. To cancel this operation, enter n. Action The specified directory already exists.
Message ID Message Text Explanation bb...bb: Indicated contents in a line Action After the DLMgetras utility for collecting HDLM error information terminates, check the contents of the file for defining the information to be collected. This file is shown in the message. If the contents of the file are incorrect, correct them and then try to collect error information again. The DLMgetras utility will ignore the specified file or directory and continue processing.
Message ID Message Text Explanation aa...aa: Line number of the file for defining information to be collected (decimal number) bb...bb: Indicated contents in a line Action After the DLMgetras utility for collecting HDLM error information terminates, check the contents of the file for defining the information to be collected. This file is shown in the message. If the contents of the file are incorrect, correct them and then try to collect error information again.
Message ID Message Text Explanation aa...aa: Third parameter Action After the DLMgetras utility for collecting HDLM error information terminates, check whether the file for defining the information to be collected is a text file. The file is shown in the message. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL10016-W The root directory has been specified in the first parameter.
Message ID Message Text Explanation The utility for collecting HDLM error information terminated before completion. If the directory is unnecessary, delete directory. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL10022-I The utility for collecting HDLM error information completed normally. Details Error information has been collected. Action None.
Message ID Message Text Explanation 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...bb: cp command output message Action An error occurred while the collected files were being copied. The environment, in which a user executed the command, might be wrong. Check the system configuration. KAPL10035-E An attempt to archive the error information failed. Details = aa...
Message ID Message Text Explanation There is no output file, or the user does not have execution permission. aa...aa: file name Action Make sure the specified file exists and the user has execution permission. KAPL10049-I Error information collection command = aa...aa, Return value = bb...bb, Execution time = cc...cc Details aa...aa: Executed command bb...bb: Return value of the executed command cc...cc: Year (4 digits)/month/day hour:minute:second Action None.
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. Details KAPL10306-W The configuration definition file is invalid.
Message ID KAPL10312-I Message Text HDLM has created an HDLM device special file. Device = aa...aa Explanation 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...aa Details A logical device file for an HDLM device has been deleted. aa...aa: Logical device file name of HDLM device Action None. KAPL10314-I HDLM has updated an HDLM device special file.
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. KAPL10319-W usage: /sbin/dlmcfgmgr [-s] {-r | -o {special-filename ... | all} | -i {special-filename ... | all} | -v | -u {special-filename ...
Message ID Message Text Explanation Action Specify a correct logical device file name of an HDLM device, and then re-execute the dlmcfgmgr utility. For details on the dlmcfgmgr utility, see dlmcfgmgr Utility for Managing the HDLM Configuration on page 7-22. KAPL10322-E A file that defines HDLMunmanaged disks could not be created. File name = aa...aa, Errno = bb...bb. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company.
Message ID KAPL10325-E Message Text 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. Explanation Details An HDLM device could not be deleted because the device could not be found by using a regular expression. aa...
Message ID Message Text Explanation Re-execute the dlmcfgmgr utility. For details on the dlmcfgmgr utility, see dlmcfgmgr Utility for Managing the HDLM Configuration on page 7-22. KAPL10329-E A file could not be opened. File name = aa...aa, Errno = bb...bb. Refer to the Messages section of the HDLM User's Guide for instructions to correct this problem. Details The file could not be opened. aa...aa: File name bb...bb: Error number (decimal number) Action Confirm the existence of the file.
Message ID Message Text Explanation vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL10332-E The registering of the partition information for HDLM device(s) failed. Errno = aa...aa. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company.
Message ID Message Text Explanation and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL10335-E A directory cannot be created. Directory = aa...aa, Errno = bb...bb. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company. Details An attempt to create a directory has failed. aa...
Message ID KAPL10339-I Message Text This operation will change the configuration of HDLM devices. Do you want to continue? [y/n]: Explanation Details This message checks whether you want to change the configuration definition of an HDLM device. Action Enter y to continue. Enter n to cancel. KAPL10340-E Several processes failed. See the aa...aa file. Check the message output before this message. Details Some processes in the execution of the HDLM-configuration definition utility (dlmcfgmgr) have failed.
Message ID Message Text HDLM device = aa...aa, Device = bb...bb (Host: cc...cc Channel: 0 ID: dd...dd Lun: ee...ee) Explanation By executing the HDLMconfiguration definition utility (dlmcfgmgr), a newly detected path has been added to the registered HDLM device. aa...aa: HDLM device name bb...bb: SCSI device name cc...cc: Host ID (decimal number) Channel: Channel ID (fixed value: 0) (decimal number) dd...dd: Target ID (decimal number) ee...ee: LUN (decimal number) Action None.
Message ID Message Text Explanation Utility for Managing the HDLM Configuration on page 7-22. KAPL10347-I The HDLM device is no longer under management. HDLM device = aa...aa Details By executing the HDLMconfiguration definition utility (dlmcfgmgr), the HDLM device has been removed from HDLM management. 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.
Message ID Message Text Explanation a. Execute the following command to load the HDLM driver # /opt/ DynamicLinkManager/bin/ dlminsadrv # modprobe sddlmfdrv b. Re-execute the dlmcfgmgr utility. For details on the dlmcfgmgr utility, see dlmcfgmgr Utility for Managing the HDLM Configuration on page 7-22. KAPL10351-E The specified HDLMconfiguration definition utility is invalid. Operation name = aa...aa, Parameter = bb...
Message ID Message Text utility to collect error information, and then contact your vendor or maintenance company. Explanation aa...aa: File name 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 Restart the host. If the host does not recover, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL10357-E The maximum number of HDLM Details device files has been reached. An attempt to execute the HDLMMaximum number = aa...aa.
Message ID Message Text running dlmcfgmgr utility ends, and then try the dlmcfgmgr utility again. Explanation instances of dlmcfgmgr were executed simultaneously. Action Wait until the running HDLMconfiguration definition utility (dlmcfgmgr) ends, and then reexecute the HDLM-configuration definition utility (dlmcfgmgr). For details on the dlmcfgmgr utility, see dlmcfgmgr Utility for Managing the HDLM Configuration on page 7-22. KAPL10360-I HDLM has activated a path for Details an HDLM device.
Message ID Message Text Explanation None. For details on the dlmcfgmgr utility, see dlmcfgmgr Utility for Managing the HDLM Configuration on page 7-22. KAPL10362-W HDLM has detected an active path that cannot be deleted. HDLM device = aa...aa, Device = bb...bb (Host: cc...cc Channel: 0 ID: dd...dd Lun: ee...ee). Refer to the Messages section of the HDLM User's Guide for instructions to correct this problem.
Message ID Message Text Explanation corresponding to an HDLM device was changed. aa...aa: Logical device file name of an HDLM device Action None. Details KAPL10365-W The LDEV for an HDLM device has changed. The processing for The processing for the HDLM that HDLM device will be device was interrupted because an cancelled. HDLM device = LDEV corresponding to an HDLM aa...aa. Execute the HDLMdevice was changed. configuration definition utility aa...
Message ID Message Text Explanation Execute the dlmpr -h utility to check the parameter, and then retry execution. For details on the dlmpr utility, see dlmpr Utility for Clearing HDLM Persistent Reservation on page 7-33. KAPL10644-W The specified parameters cannot Details be specified at the same time. The specified parameters cannot parameter = aa...aa be specified for the dlmpr utility at the same time. aa...
Message ID Message Text Explanation When the error code is 1: Make sure that there is sufficient memory. When the error code is 2: Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. When the error code is 4 or 5: Make sure that the SCSI device file permissions permit reading and writing. For details on the dlmpr utility, see dlmpr Utility for Clearing HDLM Persistent Reservation on page 7-33. KAPL10649-E aa...
Message ID Message Text KAPL10653-W The entered value is invalid. Please re-enter it [y/n]: Explanation Details A value other than y or n has been entered for a [y/n] request. Action Enter y or n. KAPL10665-I The dlmpr utility completed. Details The dlmpr utility completed normally. Action None. For details on the dlmpr utility, see dlmpr Utility for Clearing HDLM Persistent Reservation on page 7-33. KAPL10920-W Processing for HDLM Config Manager interrupted.
Message ID Message Text DynamicLinkManager/ hdlm_utillog.conf, Errno = aa...aa. Refer to the Messages section of the HDLM User's Guide for instructions to correct this problem. Explanation An attempt to open the settings file for the HDLM utility log (/etc/ opt/DynamicLinkManager/ hdlm_utillog.conf) has failed.A maximum log file size of 1024 KB will be assumed, and the processing of the dlmcfgmgr utility will continue. aa...aa: Error number (decimal number) Action Make sure that the file exist.
Message ID Message Text Explanation Action Execute the dlmcfgmgr utility with the -logfs parameter specified. If the error occurs again, /etc/opt/ DynamicLinkManager/ hdlm_utillog.conf which is not a regular file might exist. Delete / etc/opt/DynamicLinkManager/ hdlm_utillog.conf and then execute the dlmcfgmgr utility again. For details on the dlmcfgmgr utility, see dlmcfgmgr Utility for Managing the HDLM Configuration on page 7-22. KAPL10937-W The maximum number of paths was exceeded.
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. KAPL10941-W The file could not be opened. File name = aa...aa, Errno = bb...
Message ID Message Text (aa...aa) function. File name = bb...bb, Errno = cc...cc Explanation An error occurred during processing to read a file in the (aa...aa) function. bb...bb: File name cc...cc: Errno Action Confirm that the configuration for HDLM devices is correct. If it is not correct, execute the 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.
KAPL11001 to KAPL12000 Message ID KAPL11901-I Message Text aa...aa has started. Explanation Details The operation has started on the host. aa...aa: Operation (character string) ¢ Get Path Information ¢ Get Option Information ¢ Set Option Information ¢ Clear Data ¢ Get HDLM Manager Status ¢ Get HDLM Driver Status ¢ Get HDLM Alert Driver Status ¢ Get SNMP Trap Information ¢ Set SNMP Trap Information ¢ Set LU Load Balance ¢ ¢ Get Path Status Log Information Get Local Time Action None.
Message ID Message Text Explanation ¢ Get HDLM Alert Driver Status ¢ Online ¢ Offline ¢ Get SNMP Trap Information ¢ Set SNMP Trap Information ¢ Set LU Load Balance ¢ ¢ Get Path Status Log Information Get Local Time Action None. KAPL11904-E aa...aa has completed abnormally. Error status = bb...bb Details The operation has completed abnormally on the host. aa...
Message ID Message Text Explanation An exception occurred during processing on the host. Action Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if you have a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. KAPL11906-I GUI information - aa...aa Details This information is required for resolving problems. aa...
Message ID Message Text Explanation Install HDLM that adjusts to the kernel that is running now. KAPL12036-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. KAPL12301-E This script can only be executed with the name dlmmkinitrd. Action Please rename the script to dlmmkinitrd.
Message ID Message Text Explanation ¢ ¢ ¢ ¢ ¢ /etc/opt/DynamicLinkManager/ dlmmkinitrd.conf /lib/modules/kernel-version/ kernel/drivers/ DynamicLinkManager/ sddlmfdrv.o /lib/modules/kernel-version/ kernel/drivers/ DynamicLinkManager/ sddlmfdrv.ko /lib/modules/kernel-version/ kernel/drivers/ DynamicLinkManager/ sddlmadrv.o /lib/modules/kernel-version/ kernel/drivers/ DynamicLinkManager/ sddlmadrv.
Message ID KAPL12313-I KAPL12314-I KAPL12315-I Message Text Explanation Initial ramdisk is being unmounted. Action The compressed initial ramdisk image is being created. Action A compressed initial ramdisk image aa...aa was created with the ramdisk size = bb...bb KB. Details None. None. aa...aa: The created initial ramdisk image bb...bb: The ramdisk size required for the created initrd image (decimal number) Action None. KAPL12316-I The SCSI root partition is aa...aa Details aa...
Message ID Message Text Explanation overwriting the existing file, specify the -f parameter. Note that if you attempt to specify an existing directory name as the initial RAM disk image file, it is impossible to overwrite the file even if the -f parameter is specified. To overwrite the file, it is necessary to delete the directory first. KAPL12321-E An invalid root partition is specified in the file. File name = aa...aa Details aa...
Message ID KAPL12326-E Message Text The command could not execute. Command name = aa...aa Explanation Details aa...aa: The failed command Action Perform the following confirmation corresponding to the output command, and then retry. Re-execute the dlmmkinitrd utility for supporting the boot disk after performing the next check according to the outputted command. And if the error message is outputted before this message, remove the cause of the error with reference to the contents of the message.
Message ID Message Text Explanation Confirm that the user has write permission in the root directory (/). mkdir: Confirm that there is enough unused capacity and that the user has write permission in the following directory: ¢ /etc/opt/DynamicLinkManager. ¢ /opt/DynamicLinkManager. ¢ The root directory (/) mount: Confirm that there is unused capacity in the loop device. umount: A temporary file remains, so do the following: a. Unmount /etc/opt/DynamicLinkManager/ tmp/initrdmnt.
Message ID Message Text Explanation page 3-124 or Upgrade Installation in an Environment Where a Logical Volume (LVM2) on an HDLM Device Is Used as a Boot Disk on page 3-135: - filter - types - md_component_detection In the case of /etc/opt/ DynamicLinkManager/ dlmmkinitrd.conf file Install an HBA driver, which is 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.
Message ID Message Text Explanation Action Perform the dlmmkinitrd utility again after performing the following check: a. Confirm that the kernel of the version displayed into the message is installed. b. In Red Hat Enterprise Linux, confirm the kernel version specified as a parameter. For the details of the parameter, see dlmmkinitrd Utility for Supporting a Boot Disk on page 7-31.
Message ID Message Text Explanation Also, make sure that the HBA driver has been installed. KAPL12334-E Multiple root partition entries Details exist in the file. File name = aa...aa: The name of the file aa...aa referenced by the dlmmkinitrd utility for supporting the boot disk Action Modify the fstab file specified in the fstab parameter of the boot disk support utility (dlmmkinitrd), and then retry the operation.
Message ID KAPL12342-I KAPL12343-I KAPL12344-I Message Text Explanation Execution of bootup script completed. Action The bootup executable is being created. Action A compressed initial ramdisk image (aa...aa) was created. Details None. None. aa...aa: The created initial ramdisk image Action None. KAPL12345-E The version of the kernel supported by the installed HDLM does not match the currently running kernel version.
Message ID Message Text Explanation The collection of files for HDLM completed. Action None. KAPL12551-E KAPL12552-E The utility for setting HDLM driver option can be executed with the name dlmsetopt only. Action Change the utility name back to dlmsetopt, and then execute it. Action Multiple instances of the utility for setting HDLM Wait until the executing utility driver option (dlmsetopt) finishes, and then re-execute cannot execute concurrently. dlmsetopt.
Message ID KAPL12558-I KAPL12559-E Message Text Explanation Please restart the computer so that the option settings take effect. Action An invalid value was specified in the parameter. Option = aa...aa, Parameter = bb...bb Details Restart the computer. aa...aa: Option bb...bb: Specified parameter(Maximum 10 characters. If there are more than 10 characters, only 10 characters will be output followed by ...
Message ID Message Text Explanation utility for setting HDLM driver option (dlmsetopt). Delete any unnecessary files in the file system, and then re-execute the dlmsetopt utility. KAPL12564-E An attempt to back up a file has failed. File name = aa...aa Details aa...aa: Backup file name Action Make sure there is enough free disk capacity, and then re-execute the utility for setting HDLM driver option (dlmsetopt). KAPL12565-E Could not modify file. File name = aa...aa Details aa...
Message ID Message Text Explanation DLMSETOPT/modprobe.conf file, and then re-configure the content that was configured in the /etc/modprobe.conf file according to the user's environment. Then, delete the / etc/opt/DynamicLinkManager/ DLMSETOPT/modprobe.conf file. Finally, re-execute the dlmsetopt utility to make sure that an error does not occur. KAPL12567-E The version of the kernel supported by the installed HDLM does not match the currently running kernel version.
Message ID Message Text HDLM does not match the currently running kernel version. Explanation The version of the kernel to which installed HDLM has adjusted and the kernel that is running now is not corresponding. There is a possibility of installing the package of the kernel after installing HDLM. Action Install HDLM that adjusts to the kernel that is running now. KAPL12852-E The HDLM file is invalid. File name = aa...aa Details A file necessary for processing HDLM cannot be found.
Message ID Message Text Explanation Reinstall HDLM. KAPL13205-W You do not have read permission for the file. File name = aa...aa Details aa...aa: / etc/.DynamicLinkManager/ Path00, /etc/.HBaseAgent/ Path00 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.
Message ID KAPL13403-E Message Text You lack write permission for the specified directory. Value= aa...aa Explanation Details You do not have write permission for the specified directory, or the creation of a subdirectory of the specified directory failed. aa...aa: first parameter Action Check the following. 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.
Message ID Message Text Explanation cc...cc: the year of grace/month/ day hour:minute:second(GMT) Action None. KAPL13408-E 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 install error information terminated before completion. If the directory is unnecessary, delete directory. KAPL13409-I The utility for collecting HDLM install error information completed normally.
Message ID Message Text Explanation The file subject to collecting does not exist. aa...aa: Name of file to collect Action None. KAPL13414-E The file could not be copied. File Details = aa...aa, Details = bb...bb Execution of the cp command failed. aa...aa: file name you tried to copy bb...bb: cp output message Action Check the system configuration. KAPL13415-E An attempt to archive the install Details error information failed. Details Execution of the tar command = aa...aa failed. aa...
Message ID Message Text Explanation After installing HDLM, re-execute the installgetras utility. KAPL13418-E Too many parameters have been specified. Details Two or more parameters have been specified. Action Check the parameters of the utility for collecting HDLM install error information, and then retry. KAPL13501-I KAPL13502-I KAPL13503-I The utility for update system scripts started. Action The utility for update system scripts completed successfully. Action A system script has been modified.
Message ID Message Text Explanation was output just before this message. KAPL13508-E You lack permission for executing the utility for update system scripts. Details The current user does not have authority to execute dlmupdatesysinit utility. Action Re-execute dlmupdatesysinit utility as a user with root permission. Refer to dlmupdatesysinit Utility for Updating System Scripts on page 7-39.
Message ID Message Text Explanation Check for parameters, and then re-execute the dlmupdatesysinit utility. Refer to dlmupdatesysinit Utility for Updating System Scripts on page 7-39. KAPL13514-W Usage: /opt/ DynamicLinkManager/bin/ dlmupdatesysinit Action KAPL13515-E Details A command required by HDLM not found. Command = aa...aa Check for parameters, and then re-execute the dlmupdatesysinit utility. Refer to dlmupdatesysinit Utility for Updating System Scripts on page 7-39. aa...
Message ID Message Text Explanation dlmupdatesysinit Utility for Updating System Scripts on page 7-39. KAPL13519-E An HDLM file required for the dlmupdatesysinit utility was not found. File name = aa...aa Details aa...aa: File name Action Reinstall an HDLM. KAPL13520-E An HDLM directory required for the dlmupdatesysinit utility was not found. Directory name = aa...aa Details aa...aa: Directory name Action Reinstall an HDLM. KAPL13521-E A command has failed. Command = aa...aa, Details = bb...
Message ID Message Text command and check whether a normal result is displayed. Explanation The audit log configuration file cannot be opened. Action If the "dlnkmgr view -sys audlog" command does not display a normal result, contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. KAPL13603-W The audit log configuration file is Details invalid. Restart the HDLM The audit log configuration file is Manager, and execute the invalid.
Message ID KAPL13902-I KAPL13903-I KAPL13904-I KAPL13905-I KAPL13906-I Message Text Explanation Alert driver had been loaded. Alert driver's loading was skipped. Action The process related to Alert driver had been completed. The process related to Alert driver was skipped. Action Filter driver had been loaded. Filter driver's loading was skipped. Action HDLM manager had started. HDLM manager's start processing was skipped. Action aa...aa will now start. Details None. None. None. None.
Message ID Message Text Explanation KAPL13909-W Usage: /opt/ DynamicLinkManager/bin/ dlmstart Action KAPL13910-W The error occurred while processing the utility for HDLM start. Action KAPL13911-E Details The utility for HDLM start ended abnormally. Error Code = aa...aa Re-execute the utility for HDLM start if necessary. Refer to dlmstart Utility for Starting HDLM on page 7-38. Resolve the problem according to the message KAPL13908-W, which was output before this message. aa...
Message ID Message Text Explanation Remove the error cause described in the message output by the command indicated in the message KAPL13913-E. Next, reexecute the utility for HDLM start if necessary. Refer to dlmstart Utility for Starting HDLM on page 7-38. KAPL13914-E A file required by HDLM not found. File name = aa...aa Details aa...aa: file name Action Reinstall an HDLM. KAPL15001 to KAPL16000 Message ID KAPL15001-I Explanation The registered value of ReserveKey was successfully displayed.
Message ID KAPL15044-I KAPL15045-E KAPL15046-I KAPL15047-E KAPL15048-I KAPL15049-E Message Text Explanation Processing to add devices to HDLM management succeeded. Command Line = aa...aa Details Processing to add devices to HDLM management has failed. Command Line = aa...aa Details The management status and configuration information of HDLM devices was successfully displayed. Command Line = aa...
Message ID Message Text Explanation command has failed. Command Line = aa...aa KAPL15056-I The number of retries for the SCSI INQUIRY command was successfully set. Command Line = aa...aa Details aa...aa: Name of the utility that the user executed KAPL15057-E An attempt to set the number of Details retries for the SCSI INQUIRY aa...aa: Name of the utility that command has failed. Command the user executed Line = aa...aa KAPL15058-I Processing to re-register the HDLM information was successful.
Message ID KAPL15101-I KAPL15102-E KAPL15103-I Message Text Explanation Clear operation was completed successfully. Command Line = aa...aa Details Clear operation has failed. Command Line = aa...aa Details aa...aa path(s) were successfully placed bb...bb. cc...cc path(s) were not. Command Line = dd...dd Details aa...aa: Command that the user executed aa...aa: Command that the user executed aa...aa: Number of paths where online/offline is successful bb...bb: Online or Offline(C) cc...
Message ID Message Text Explanation KAPL15401-I HDLM Manager successfully started. - KAPL15402-E Could not start the HDLM manager. - KAPL15403-I HDLM Manager successfully stopped. - KAPL15404-W The HDLM Manager was executed by the user who does not have the authority.
Message ID Explanation Action Click Refresh to update the host information, check the path status, and then retry the offline operation. 1015 Details The Offline path cannot be placed Online. Action Remove the error in the path, and then retry. 1016 Details The target path(s) are already Online. 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.
Message ID 1026 Explanation Details The acquisition of path information has been aborted, because the path configuration was changed while the system was attempting to acquire the path information. Action Refresh the host information, check the path status, and then perform the operation again. 1027 Details The error monitoring interval and the number of times that the error needs to occur are conflicting with the automatic failback-checking interval.
Message ID Explanation Action Re-execute the command. If the same error occurs again, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3. 1037 Details A parameter is invalid. Action Refresh the host information, and then perform the operation again.
Message ID Explanation you have a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras Utility for Collecting HDLM Error Information on page 7-3.
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.
Figure A-3 Example of Executing the sar Command Notes on the fdisk and parted Commands When creating partitions on an HDLM device, only use the fdisk command or the parted command. If partitions have been created on an HDLM device using the fdisk or parted command, some of the partitions created by the fdisk command might not be visible to the parted command. Likewise, some of the partitions created by the parted command might not be visible to the fdisk command.
change, deactivate the volume group, and then activate the volume group after restarting the md device.
B Troubleshooting Products That Use the Weak-Modules Script This section explains how to deal with errors that are caused by installing or uninstalling products that use the weak-modules script.
Overview If you use an HDLM device as a boot disk in Red Hat Enterprise Linux 5 and attempt to install or uninstall a product that uses the weak-modules script, the following message might be output, and installation or uninstallation of that product might fail: grubby fatal error: unable to find a suitable template Therefore, when using an HDLM device as a book disk in Red Hat Enterprise Linux 5, execute the following commands before installing or uninstalling a product that uses the weak-modules script:
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 (/).
Uninstalling Products That Use the Weak-Modules Script To uninstall 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. Uninstall other products that use the weak-modules script. Perform uninstallation 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.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.0 or Later and Versions Earlier Than 6.0 □ Functional Differences Between Version 5.9.
□ 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.2 and Versions Earlier Than 7.2 • When creating an initial RAM disk image file in Red Hat Enterprise Linux 6, the dracut command is now used, instead of the dlmmkinitrd boot disk support utility. Due to this change, the dlmmkinitrd utility is no longer installed in a Red Hat Enterprise Linux 6 environment. Functional Differences Between Version 6.2.1 and Versions Earlier Than 6.2.
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.8 or Later and Versions Earlier Than 5.8 Table C-1 JRE/JDK Version Required for HDLM GUI on page C-5 describes the version of the JRE or JDK required to use the HDLM GUI on a host. Table C-1 JRE/JDK Version Required for HDLM GUI 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.2_09 JDK v1.4.2_08 JDK v1.4.2_09 Red Hat Enterprise Linux AS3/ES3 (EM64T/AMD64) JRE v1.5.0_03 JRE v1.5.
Functional Differences Between Version 5.7 or Later and Versions Earlier Than 5.7 In version 5.7 or later, if there are no files under the /etc/opt/ DynamicLinkManager directory when HDLM is uninstalled, the directory is deleted. Functional Differences Between Version 5.6.3 or Later and Versions Earlier Than 5.6.3 Table C-2 JRE/JDK Version Required for HDLM GUI on page C-6 describes the version of the JRE or JDK required to use the HDLM GUI on a host.
Acronyms and abbreviations The following acronyms and abbreviations might be used in this guide.
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 FC-SP Fibre Channel Security Protocol # A B C D E F G H I J K L M N O P Q R S T Acronyms-2 Hitachi Dynamic Link Manager User Guide (for Linux(R)) U
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 IDE Integrated Drive Electronics # 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(R))
IP Internet Protocol IPC Inter Process Communication IPF Itanium(R) 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 LVM Logical Volume Manager # A B C D E F G H I J K L M N O P Q R S T Acronyms-4 Hitachi Dynamic Link Manager User Guide (for Linux(R)) U V W X Y
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 S SAN Storage Area Network # 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(R))
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 T Acronyms-6 Hitachi Dynamic Link Manager User Guide (for Linux(R)) 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, Universal Storage Platform V/VM, Virtual Storage Platform, and Hitachi AMS2000/AMS/WMS/SMS series for logically splitting up a cache. This function can split up a cache into parity groups in the storage system, so that other parity groups do not affect the cache performance.
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. H HBA (Host Bus Adapter) Device that functions as an interface connecting a host with external devices.
(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. I intermittent error An error that occurs irregularly due to, for example, a loose cable connection. IP-SAN (Internet Protocol - Storage Area Network) A data transfer network that connects hosts and storage systems by using the iSCSI standard.
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. non-owner controller A controller other than an owner controller. Non-owner controllers exist only in the Thunder 9500V series, or Hitachi AMS/WMS series.
P path An access path from a host to a storage system. Access to an area within an LU in a storage system is made via a cable connecting the HBA on the host and the CHA on the storage system. This cable is a path. Each path has an AutoPATH_ID. (See also: AutoPATH_ID) path health checking A function for checking the status of paths at regular intervals. When an error occurs on a path that was in the Online status, path health checking changes the status of the path to the Offline(E) status.
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 T Glossary-8 Hitachi Dynamic Link Manager User Guide (for Linux(R)) U V W X Y Z
Index Symbols /proc/partitions files A-2 A active host 2-45 adding new LU 4-34 adding path to existing LU 4-36 audit log categories and audit events that HDLM can output 2-36 collecting data 2-34 data format 2-42 automatic failback 2-20, 6-19, Glossary-1 automatic failover 2-19 automatic path switching 2-19 AutoPATH_ID 2-3, Glossary-1 B BladeSymphony environment when using Red Hat Enterprise Linux 5 3-46, 3-48 when using Red Hat Enterprise Linux AS4/ES4 3-32, 3-35 when using SUSE LINUX Enterprise Server
when using Red Hat Enterprise Linux 5 when using Red Hat Enterprise Linux 6 3-36 3-49 when using Red Hat Enterprise Linux AS4/ES4 3-16 when using SUSE LINUX Enterprise Serve 9 3-50 when using SUSE LINUX Enterprise Server 10 3-51 coding file that defines information to be collected rules for 7-4 collecting error info.
Error-level errors 2-33 ErrorCode 5-2 errors detected by HDLM 2-33 management 2-30 examining message 5-5, 5-6 F failback 2-18, 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-3 fiber cable replacing 4-28 Fibre Channel switch replacing 4-30 file for defining information to be collected 7-4 file system creating 3-194 when using Oracle Enterprise Linux 4 3-60 when using Oracle Enterprise Linux 5 3-62 when using Red Hat Enterprise Linux 5 3-44 when us
help 6-4 Hitachi Network Objectplaza Trace Library Notes 3-193 Hitachi Network Objectplaza Trace Library (HNTRLib2) Uninstalling 3-226 HLU 2-8 host 3-3, Glossary-3 host bus adapter 2-3 host device 2-7, Glossary-3 host device name Glossary-3 host LU 2-7, Glossary-3 host LU number 6-45, Glossary-4 host port number 6-45 how to edit installation-information settings file 7-42 hypervisor Glossary-4 I I/O count 6-3 errors 6-3 identifying error part 5-5 error path 5-5 Information-level errors 2-33 installation 3-
recognized by host 2-8 LU configuration recognized by the host O 2-8 LUKS notes 3-152 LVM2 notes on using LVM2 3-166 setting LVM2 3-166 lvrename commands A-5 M manual path switching 2-21 md device creating 3-155 notes 3-154 settings 3-154 md device settings canceling 3-209 message examining 5-5, 5-6 Message level 8-3 Messages 8-1 checking error information 5-2 mkfs commands A-4 mount point 3-80 mounting file system 3-195 N narrowing down hardware causing error 5-5 network interface card 2-4 NIC 3-16 nod
path information obtaining 5-5 path name Glossary-6 path status transition 2-22 path switching automatically 2-19 manually 2-21 PathID 5-2 PathName 5-2 Paths To Which Load Balancing Is Applied 2-15 Performing Failovers and Failbacks Using Path Switching 2-18 persistent reservation Glossary-6 physical path 2-3, Glossary-6 placing a path or paths offline 6-5 placing a path or paths online 6-10 placing online path 5-5 port 2-3 position of the HDLM driver and HDLM device 2-10 process-specific-trace information
SUSE LINUX Enterprise Server 10 3-80 boot disk environment and BladeSymphony environment 3-55 cluster software 3-51 file system 3-55 kernel 3-10 volume manager 3-53 SUSE LINUX Enterprise Server 11 3-80 boot disk environment 3-59 file system 3-59 kernel 3-12 volume manager 3-58 SUSE LINUX Enterprise Server 9 3-80 cluster software 3-50 file system 3-51 kernel 3-9 volume manager 3-50 syntax conventions xvi syslog 2-32 system configuration 2-3, 2-4 T taking actions for hardware error 5-5 target ID 6-45 trace f
Index-8 Hitachi Dynamic Link Manager User Guide (for Linux(R))
Hitachi Dynamic Link Manager User Guide (for Linux(R))
Hitachi Data Systems Corporate Headquarters 750 Central Expressway Santa Clara, California 95050-2627 U.S.A. Phone: 1 408 970 1000 www.hds.com info@hds.com Asia Pacific and Americas 750 Central Expressway Santa Clara, California 95050-2627 U.S.A. Phone: 1 408 970 1000 info@hds.com Europe Headquarters Sefton Park Stoke Poges Buckinghamshire SL2 4HD United Kingdom Phone: + 44 (0)1753 618000 info.eu@hds.
