Hitachi Dynamic Link Manager Software
User's Guide (for Linux(R))
3000-3-F04-60(E)
Relevant program products
Hitachi Dynamic Link Manager version 6.6.2
For details about applicable OSs, see the Release Notes.
Trademarks
AIX is a trademark of International Business Machines Corporation in the United States, other countries, or both.
AMD, AMD Opteron, and combinations thereof, are trademarks of Advanced Micro Devices, Inc.
Brocade is a trademark or a registered trademark of Brocade Communications Systems, Inc. in the United States and/or in other
countries.
Emulex is a registered trademark of Emulex Corporation.
HP-UX is a product name of Hewlett-Packard Company.
HP StorageWorks is a trademark of Hewlett-Packard Company.
Intel Xeon is a trademark of Intel Corporation in the United States and other countries.
Itanium is a trademark of Intel Corporation in the United States and other countries.
Java is a registered trademark of Oracle and/or its affiliates.
JDK is either a registered trademark or a trademark of Oracle and/or its affiliates.
Linux(R) is the registered trademark of Linus Torvalds in the U.S. and other countries.
Microsoft is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
Oracle and Oracle9i are either registered trademarks or trademarks of Oracle and/or its affiliates.
Oracle and Oracle Database 10g are either registered trademarks or trademarks of Oracle and/or its affiliates.
Oracle and Oracle Database 11g are either registered trademarks or trademarks of Oracle and/or its affiliates.
Pentium is a trademark of Intel Corporation in the United States and other countries.
QLogic is a registered trademark of QLogic Corporation.
Red Hat is a trademark or a registered trademark of Red Hat Inc. in the United States and other countries.
Solaris is either a registered trademark or a trademark of Oracle and/or its affiliates.
SteelEye Technology, SteelEye and LifeKeeper are registered trademarks of SteelEye Technology, Inc.
Sun Microsystems is either a registered trademark or a trademark of Oracle and/or its affiliates.
SUSE is a registered trademark of Novell, Inc. in the United States and other countries.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Veritas is a trademark or registered trademark of Symantec Corporation in the U.S. and other countries.
Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
Throughout this document Hitachi has attempted to distinguish trademarks from descriptive terms by writing the name with the
capitalization used by the manufacturer, or by writing the name with initial capital letters. Hitachi cannot attest to the accuracy of
this information. Use of a trademark in this document should not be regarded as affecting the validity of the trademark.
Restrictions
Information in this document is subject to change without notice and does not represent a commitment on the part of Hitachi. The
software described in this manual is furnished according to a license agreement with Hitachi. The license agreement contains all of
the terms and conditions governing your use of the software and documentation, including all warranty rights, limitations of liability,
and disclaimers of warranty.
Material contained in this document may describe Hitachi products not available or features not available in your country.
No part of this material may be reproduced in any form or by any means without permission in writing from the publisher.
Edition history
3000-3-F04-60(E): August 2011
Copyright
All Rights Reserved. Copyright (C) 2008, 2011, Hitachi, Ltd.
Summary of Amendments
The following table lists changes in this manual (3000-3-F04-60(E)) and product
changes related to this manual.
ChangesLocation in this manual
Systems that use an IP-SAN are now supported.2.2, 2.2.2, 3.1.1, 3.1.2, 3.1.4, 3.1.5, 3.6.3, 3.6.6, 3.22.1,
Red Hat Enterprise Linux AS 4.9 and Red Hat
Enterprise Linux ES 4.9 are now supported.
It is now possible to specify the number of times
the same path can be used for I/O operations when
the Round Robin (
Blocks (
lbk) algorithm is used for load balancing.
rr), Least I/Os (lio), or Least
3.22.2, 4.6.4, 6.7.2, 7.2.3, 7.10.3, Appendix D
2.12.1, 8.4, 8.5, 8.10, 8.14
3.1.1, 3.1.3
4.3.7, 6.6.1, 6.6.2, 6.7.1, 6.7.2, 7.2.3, 7.10.3
In addition to the above changes, minor editorial corrections have been made.
Preface
This manual describes the functions and use of the following program products:
•Hitachi Dynamic Link Manager
Intended Readers
This manual is intended for system administrators who use Hitachi Dynamic Link
Manager (HDLM) to operate and manage storage systems. The readers of this manual
must have a basic knowledge of the following areas:
•Linux and its management functionality
•Storage system management functionality
•Cluster software functionality
•Volume management software functionality
Organization of This Manual
This manual is organized as follows:
1. Overview of HDLM
Chapter 1 gives an overview of HDLM, and describes its features.
2. HDLM Functions
Chapter 2 describes management targets and the system configuration of HDLM,
and the basic terms and functions for HDLM.
3. Creating an HDLM Environment
Chapter 3 describes the procedures for building an HDLM environment
(including installing and setting up HDLM), and describes for canceling the
settings.
4. HDLM Operation
Chapter 4 describes how to use HDLM by using both the HDLM commands, and
how to manually start and stop the 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
Chapter 5 explains how to troubleshoot a path error, HDLM failure, or any other
i
problems that you might encounter.
6. Command Reference
Chapter 6 describes all the HDLM commands.
7. Utility Reference
Chapter 7 describes the HDLM utilities.
8. Messages
Chapter 8 provides information for all the possible messages that could be output
by HDLM. It also lists and explains the HDLM messages and shows the actions
to be taken in response to each message.
A. Notes on Linux Commands and Files
Appendix A gives notes on Linux commands and files.
B. Troubleshooting Products That Use the Weak-Modules Script
Appendix B explains how to deal with errors that are caused by installing or
uninstalling products that use the weak-modules script.
C. Functional Differences Between Versions of HDLM
Appendix C explains the differences in functionality between HDLM versions.
D. Glossary
This glossary explains terms used in this manual.
Related Publications
Manuals related to this manual are listed below. See these manuals when necessary:
•Hitachi Global Link Manager Software Installation and Configuration Guide
•Hitachi Global Link Manager Software Messages
•Hitachi Adaptable Modular Storage Series User's Guide
•Hitachi Simple Modular Storage Series User's Guide
•Hitachi USP Series User's Guide
•Hitachi Workgroup Modular Storage Series User's Guide
•Thunder9580V Series Disk Array Subsystem User's Guide
•Universal Storage Platform V Series User's Guide
•Universal Storage Platform VM Series User's Guide
•Virtual Storage Platform Series User's Guide
ii
•HITACHI Gigabit Fibre Channel Board User's Guide
•ServerConductor/DeploymentManager User's Guide
Conventions: Abbreviations
This manual uses the following abbreviations for product names.
AbbreviationFull name or meaning
Device Manager AgentDevice Manager Agent included in Hitachi Device Manager
Hitachi Global Link ManagerGlobal Link Manager
HDLMHitachi Dynamic Link Manager
Hitachi AMSA generic term for:
• Hitachi Adaptable Modular Storage 1000
• Hitachi Adaptable Modular Storage 500
• Hitachi Adaptable Modular Storage 200
Hitachi AMS/WMS seriesA generic term for:
• Hitachi Adaptable Modular Storage 1000
• Hitachi Adaptable Modular Storage 500
• Hitachi Adaptable Modular Storage 200
• Hitachi Workgroup Modular Storage series
Hitachi AMS2000/AMS/WMS/SMS seriesA generic term for:
• Hitachi Adaptable Modular Storage 2000 series
• Hitachi Adaptable Modular Storage 1000
• Hitachi Adaptable Modular Storage 500
• Hitachi Adaptable Modular Storage 200
• Hitachi Workgroup Modular Storage series
• Hitachi Simple Modular Storage series
Hitachi AMS2000 seriesHitachi Adaptable Modular Storage 2000 series
Hitachi WMSHitachi Workgroup Modular Storage series
iii
AbbreviationFull name or meaning
HP XP128HP StorageWorks XP128 Disk Array
HP XP1024HP StorageWorks XP1024 Disk Array
HP XP10000HP StorageWorks XP10000 Disk Array
HP XP12000HP StorageWorks XP12000 Disk Array
HP XP20000HP StorageWorks XP20000 Disk Array
HP XP24000HP StorageWorks XP24000 Disk Array
HP XP seriesA generic term for:
• HP XP128
• HP XP1024
• HP XP10000
• HP XP12000
• HP XP20000
• HP XP24000
HVMHitachi Virtualization Manager
JDK
JRE
TM
JavaTM 2 SDK, Standard Edition
TM
2 Runtime Environment, Standard Edition
Java
Lightning 9900V seriesA generic term for:
• Lightning 9900V series
• HP XP128
• HP XP1024
LinuxLinux(R)
LUKSLinux Unified Key Setup
Oracle9i RACOracle9i Real Application Clusters
Oracle Enterprise Linux 4A generic term for:
• Oracle Enterprise Linux 4 Update 5
• Oracle Enterprise Linux 4 Update 6
Oracle Enterprise Linux 5A generic term for:
• Oracle Enterprise Linux 5 Update 1
• Oracle Enterprise Linux 5 Update 4
• Oracle Enterprise Linux 5 Update 5
Oracle RAC 10gOracle Real Application Clusters 10g
Oracle RAC 11gOracle Real Application Clusters 11g
iv
AbbreviationFull name or meaning
Oracle RACA generic term for:
• Oracle9i Real Application Clusters
• Oracle Real Application Clusters 10g
• Oracle Real Application Clusters 11g
P9500HP StorageWorks P9500 Disk Array
Red Hat Enterprise LinuxA generic term for:
• Red Hat Enterprise Linux(R) AS4/ES4
• Red Hat Enterprise Linux(R) 5
• Red Hat Enterprise Linux(R) 6
Red Hat Enterprise Linux AS4/ES4A generic term for:
• Red Hat Enterprise Linux(R) AS 4
• Red Hat Enterprise Linux(R) AS 4.5
• Red Hat Enterprise Linux(R) AS 4.6
• Red Hat Enterprise Linux(R) AS 4.7
• Red Hat Enterprise Linux(R) AS 4.8
• Red Hat Enterprise Linux(R) AS 4.9
• Red Hat Enterprise Linux(R) ES 4
• Red Hat Enterprise Linux(R) ES 4.5
• Red Hat Enterprise Linux(R) ES 4.6
• Red Hat Enterprise Linux(R) ES 4.7
• Red Hat Enterprise Linux(R) ES 4.8
• Red Hat Enterprise Linux(R) ES 4.9
Red Hat Enterprise Linux 5A generic term for:
• Red Hat Enterprise Linux(R) 5
• Red Hat Enterprise Linux(R) 5 Advanced Platform
• Red Hat Enterprise Linux(R) 5.1
• Red Hat Enterprise Linux(R) 5.1 Advanced Platform
• Red Hat Enterprise Linux(R) 5.2
• Red Hat Enterprise Linux(R) 5.2 Advanced Platform
• Red Hat Enterprise Linux(R) 5.3
• Red Hat Enterprise Linux(R) 5.3 Advanced Platform
• Red Hat Enterprise Linux(R) 5.4
• Red Hat Enterprise Linux(R) 5.4 Advanced Platform
• Red Hat Enterprise Linux(R) 5.5
• Red Hat Enterprise Linux(R) 5.5 Advanced Platform
• Red Hat Enterprise Linux(R) 5.6
• Red Hat Enterprise Linux(R) 5.6 Advanced Platform
Red Hat Enterprise Linux 6A generic term for:
• Red Hat Enterprise Linux(R) 6
• Red Hat Enterprise Linux(R) 6 Advanced Platform
RHCMRed Hat(R) Cluster Manager
v
AbbreviationFull name or meaning
SUSE LINUX Enterprise ServerA generic term for:
• SUSE LINUX(R) Enterprise Server 9
• SUSE LINUX(R) Enterprise Server 10
• SUSE LINUX(R) Enterprise Server 11
SVSHP StorageWorks 200 Storage Virtualization System
Thunder 9200Hitachi Freedom Storage Thunder 9200
Universal Storage Platform V/VMA generic term for:
• Hitachi Universal Storage Platform V
• Hitachi Universal Storage Platform VM
• HP XP20000
• HP XP24000
UNIXA generic term for:
• AIX
• Solaris
• Linux
• HP-UX
VCSVeritas Cluster Server
Virtual Storage PlatformA generic term for:
• Hitachi Virtual Storage Platform
• HP StorageWorks P9500 Disk Array
VxFSVeritas File System
VxVMVeritas Volume Manager
Note that if descriptions include the term Red Hat Enterprise Linux or Red Hat Enterprise Linux AS4/ES4, and there is no specific explanation about Oracle
Enterprise Linux 4, read them as Oracle Enterprise Linux 4 when necessary. Similarly,
note that if descriptions include the term Red Hat Enterprise Linux or Red Hat Enterprise Linux 5, and there is no specific explanation about Oracle Enterprise Linux
5, read them as Oracle Enterprise Linux 5 when necessary.
This manual also uses the following abbreviations.
AbbreviationFull name or meaning
APIApplication Programming Interface
BIOSBasic Input / Output System
CFQComplete Fair Queuing
CHAChannel Adapter
vi
AbbreviationFull name or meaning
CLPRCache Logical Partition
CPUCentral Processing Unit
CUControl Unit
DBMSDatabase Management System
DevDevice
DMIDesktop Management Interface
DNSDomain Name Server
DRBDDistributed Replicated Block Device
ELILOExtensible Firmware Interface Linux Loader
EM64TExtended Memory 64 Technology
EVMSEnterprise Volume Management System
extExtended File System
FCFibre Channel
FC-SPFibre Channel Security Protocol
FOFailover
GMTGreenwich Mean Time
GRUBGRand Unified Bootloader
GUIGraphical User Interface
HBAHost Bus Adapter
HDevHost Device
HLUHost Logical Unit
HTTPHypertext Transfer Protocol
I/OInput/Output
IA32Intel Architecture 32
IDEIntegrated Drive Electronics
IPInternet Protocol
IPCInter Process Communication
vii
AbbreviationFull name or meaning
IPFItanium(R) Processor Family
IRQInterrupt ReQuest
iSCSIInternet Small Computer System Interface
KVMKernel-based Virtual Machine
LANLocal Area Network
LDAPLightweight Directory Access Protocol
LDEVLogical Device
LILOLinux Loader
LULogical Unit
LUNLogical Unit Number
LVMLogical Volume Manager
mdMultiple Devices
NASNetwork Attached Storage
NICNetwork Interface Card
NTPNetwork Time Protocol
OSOperating System
PPort
PCIPeripheral Component Interconnect
RADIUSRemote Authentication Dial in User Service
SANStorage Area Network
SCSISmall Computer System Interface
SLPRStorage Logical Partition
SMTPSimple Mail Transfer Protocol
SNMPSimple Network Management Protocol
SPService Pack
SSLSecure Sockets Layer
SVPService Processor
viii
AbbreviationFull name or meaning
UUIDUniversally Unique Identifier
VGVolume Group
WWNWorld Wide Name
Conventions: Diagrams
This manual uses the following conventions in diagrams:
Conventions: Fonts and Symbols
Font and symbol conventions are classified as:
•General font conventions
•Conventions in syntax explanations
These conventions are described below.
General Font Conventions
The following table lists the general font conventions:
ix
FontConvention
BoldBold type indicates text on a window, other than the window title. Such text includes menus,
ItalicsItalics are used to indicate a placeholder for some actual text provided by the user or system.
Code fontA code font indicates text that the user enters without change, or text (such as messages) output
menu options, buttons, radio box options, or explanatory labels. For example, bold is used in
sentences such as the following:
• From the File menu, choose Open.
• Click the Cancel button.
• In the Enter name entry box, type your name.
Italics are also used for emphasis. For example:
• Write the command as follows:
copy source-filetarget-file
• Do not delete the configuration file.
by the system. For example:
• At the prompt, enter
• Use the
• The following message is displayed:
send command to send mail.
The password is incorrect.
dir.
Code examples and messages appear as follows (though there may be some
exceptions, such as when the code is part of a diagram):
MakeDatabase
...
StoreDatabase temp DB32
In examples of coding, an ellipsis (...) indicates that one or more lines of coding are not
shown for purposes of brevity.
Conventions in Syntax Explanations
Syntax definitions appear as follows:
StoreDatabase [temp|perm] (database-name ...)
The following table lists the conventions used in syntax explanations:
Example font or symbolConvention
StoreDatabaseCode-font characters must be entered exactly as shown.
database-nameThis font style marks a placeholder that indicates where appropriate characters are
SDBold code-font characters indicate the abbreviation for a command.
permUnderlined characters indicate the default value.
x
to be entered in an actual command.
Example font or symbolConvention
[ ]Square brackets enclose an item or set of items whose specification is optional. An
item that is underlined is specified when all items are omitted.
{ }One of the options enclosed in { } must be specified.
|Only one of the options separated by a vertical bar can be specified at the same
time.
...An ellipsis (...) indicates that the item or items enclosed in ( ) or [ ] immediately
()Parentheses indicate the range of items to which the vertical bar (|) or ellipsis (...)
#A prompt on a command-execution window when the OS is UNIX
preceding the ellipsis may be specified as many times as necessary.
C.8 Functional Differences Between Version 5.7.1 or Later and Versions Earlier
Than 5.7.1..................................................................................................... 705
C.9 Functional Differences Between Version 5.7.0-01 or Later and Versions Earlier
Than 5.7.0-01 ............................................................................................... 705
C.10 Functional Differences Between Version 5.7 or Later and Versions Earlier
Than 5.7........................................................................................................ 705
C.11 Functional Differences Between Version 5.6.3 or Later and Versions Earlier
Than 5.6.3..................................................................................................... 706
C.12 Functional Differences Between Version 5.4 or Later and Versions Earlier
Than 5.4........................................................................................................ 706
D. Glossary .................................................................................................................. 707
Index715
xx
Chapter
1.Overview of HDLM
HDLM is a software package that manages paths between a host and a storage system.
HDLM is designed to distribute loads across multiple paths and will switch a given
load to another path if there is a failure in the path that is currently being used, thus
improving system reliability.
This chapter gives an overview of HDLM and describes its features.
1.1 What is HDLM?
1.2 HDLM Features
1
1. Overview of HDLM
1.1 What is HDLM?
With the widespread use of data warehousing and increasing use of multimedia data,
the need for high-speed processing of large volumes of data on networks has rapidly
grown. To satisfy this need, networks dedicated to the transfer of data, such as SANs,
are now being used to provide access to storage systems.
HDLM manages the access paths to these storage systems. HDLM provides the ability
to distribute loads across multiple paths and switch to another path if there is a failure
in the path that is currently being used, thus improving system availability and
reliability.
Figure 1-1: Between Hosts and Storage Systems illustrates the connections between
various hosts and storage systems. A server on which HDLM is installed is called a
host.
Figure 1-1: Between Hosts and Storage Systems
HDLM supports the following storage systems:
•Hitachi AMS2000/AMS/WMS/SMS series
•Hitachi USP
•Lightning 9900 series
2
•Lightning 9900V series
•Thunder 9500V series
•Universal Storage Platform V/VM
•Virtual Storage Platform
1. Overview of HDLM
3
1. Overview of HDLM
1.2 HDLM Features
HDLM features include the following:
The ability to distribute a load across multiple paths. This is also known as load balancing.
When a host is connected to a storage system via multiple paths, HDLM can
distribute the load across all the paths. This prevents one, loaded down path from
affecting the processing speed of the entire system.
For details on load balancing, see 2.7 Distributing a Load Using Load Balancing.
The ability to continue running operations between a host and storage system, even if
there is a failure. This is also known as performing a failover.
When a host is connected to a storage system via multiple paths, HDLM can
automatically switch to another path if there is some sort of failure in the path that
is currently being used. This allows operations to continue between a host and a
storage system.
For details on performing failovers, see 2.8 Performing Failovers and Failbacks Using Path Switching.
The ability to bring a path that has recovered from an error back online. This is also
known as performing a failback.
If a path is recovered from an error, HDLM can bring that path back online. This
enables the maximum possible number of paths to always be available and online,
which in turn enables HDLM to better distribute the load across multiple paths.
Failbacks can be performed manually or automatically. In an automatic failback,
HDLM will automatically restore the path to an active state after the user has
corrected the problem that exists on the physical path.
For details on performing failbacks, see 2.8 Performing Failovers and Failbacks Using Path Switching.
The ability to automatically check the status of any given path at regular intervals. This
is also known as path health checking.
HDLM can easily detect errors by checking the statuses of paths at user-defined
time intervals. This allows you to check for any existing path errors and to resolve
them promptly and efficiently.
For details on setting up and performing path health checking, see 2.10 Detecting Errors by Using Path Health Checking.
4
Chapter
2.HDLM Functions
This chapter describes the various functions that are built into HDLM. Before the
function specifications are explained though, this chapter will go into detail about the
HDLM management targets, system configuration, and basic terms that are necessary
to know to effectively operate HDLM. After that, the rest of the chapter focus on
describing all the HDLM functions, including the main ones: load distribution across
paths and path switching.
2.1 Devices Managed by HDLM
2.2 System Configuration
2.3 LU Configuration
2.4 Program Configuration
2.5 Position of the HDLM Driver and HDLM Device
2.6 Logical Device Files for HDLM Devices
2.7 Distributing a Load Using Load Balancing
2.8 Performing Failovers and Failbacks Using Path Switching
2.9 Monitoring Intermittent Errors (Functionality When Automatic Failback Is
Used)
2.10 Detecting Errors by Using Path Health Checking
2.11 Error Management
2.12 Collecting Audit Log Data
2.13 Integrated HDLM management using Global Link Manager
2.14 Cluster Support
5
2. HDLM Functions
2.1 Devices Managed by HDLM
Below is a list of devices that can or cannot be managed by HDLM. The devices that
can be managed by HDLM are called HDLM management-target devices.
HDLM management-target devices:
The following devices of the storage systems listed in Section 1.1 What is HDLM?:
•SCSI devices
•Boot disks
Non-HDLM management-target devices:
•SCSI devices other than those of the storage systems listed in Section
1.1 What is HDLM?
•Devices other than disks (such as tape devices)
•Command devices of the storage systems listed in Section 1.1 What is
HDLM? (For example, Hitachi RAID Manager command devices.)
6
Loading...
+ 716 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.