No part of this publication may be reproduced or transmitted in any form or by any means,
electronic or mechanical, including photocopying and recording, or stored in a database or retrieval
system for any purpose without the express written permission of Hitachi, Ltd.
Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and
assumes no responsibility for its use. This document contains the most current information available
at the time of publication. When new or revised information becomes available, this entire
document will be updated and distributed to all registered users.
Some of the features described in this document might not be currently available. Refer to the most
recent product announcement for information about feature and product availability, or contact
Hitachi Data Systems Corporation at
Notice: Hitachi, Ltd., products and services can be ordered only under the terms and conditions of
the applicable Hitachi Data Systems Corporation agreements. The use of Hitachi, Ltd., products is
governed by the terms of your agreements with Hitachi Data Systems Corporation.
Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. Hitachi
Data Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States and
other countries.
Archivas, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage, Tagmaserve, Tagmasoft,
Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform are
registered trademarks of Hitachi Data Systems.
AIX, AS/400, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, ESCON, FICON,
FlashCopy, IBM, Lotus, MVS, OS/390, RS/6000, S/390, System z9, System z10, Tivoli, VM/ESA,
z/OS, z9, z10, zSeries, z/VM, and z/VSE are registered trademarks or trademarks of International
Business Machines Corporation.
https://portal.hds.com.
All other trademarks, service marks, and company names in this document or web site are
properties of their respective owners.
Microsoft product screen shots are reprinted with permission from Microsoft Corporation.
Notice on Export Controls. The technical data and technology inherent in this Document may be
subject to U.S. export control laws, including the U.S. Export Administration Act and its associated
regulations, and may be subject to export or import regulations in other countries. Reader agrees to
comply strictly with all such regulations and acknowledges that Reader has the responsibility to
obtain licenses to export, re-export, or import the Document and any Compliant Products.
ii
Hitachi Dynamic Link Manager (for Solaris) User Guide
Before Viewing the List of Messages.........................................................................8-3
xi
Hitachi Dynamic Link Manager (for Solaris) User Guide
Format and Meaning of Message IDs................................................................. 8-3
Terms Used in Messages and Message Explanations............................................8-3
Components That Output Messages to Syslog.....................................................8-3
KAPL01001 to KAPL02000....................................................................................... 8-4
KAPL03001 to KAPL04000......................................................................................8-31
KAPL04001 to KAPL05000......................................................................................8-33
KAPL05001 to KAPL06000......................................................................................8-41
KAPL06001 to KAPL07000......................................................................................8-49
KAPL07001 to KAPL08000......................................................................................8-52
KAPL08001 to KAPL09000......................................................................................8-53
KAPL09001 to KAPL10000......................................................................................8-57
KAPL10001 to KAPL11000......................................................................................8-84
KAPL11001 to KAPL12000....................................................................................8-128
KAPL13001 to KAPL14000....................................................................................8-131
KAPL15001 to KAPL16000....................................................................................8-133
Return Codes for Hitachi Command Suite Common Agent Component.....................8-136
A Sun Cluster 3.2 Commands................................................................... A-1
Sun Cluster 3.2 Commands..................................................................................... A-2
B Functional Differences Between Versions of HDLM.................................. B-1
Functional Differences Between Version 6.1 or Later and Versions Earlier Than 6.1..... B-2
Functional Differences Between Version 6.0 or Later and Versions Earlier Than 6.0..... B-2
Precautions on Differences in Functionality Between HDLM 5.6.1 or Earlier and HDLM
5.6.2 or Later......................................................................................................... B-2
Acronyms and abbreviations
Glossary
Index
xii
Hitachi Dynamic Link Manager (for Solaris) User Guide
Preface
This document describes how to use the Hitachi Dynamic Link Manager.
Intended audience
□
Product version
□
Release notes
□
Document revision level
□
Document organization
□
Related documents
□
Document conventions
□
Conventions for storage capacity values
□
Accessing product documentation
□
Getting help
□
Comments
□
Hitachi Dynamic Link Manager (for Solaris) User Guide
Preface
xiii
Intended audience
This document is intended for storage administrators who use Hitachi
Dynamic Link Manager (HDLM) to operate and manage storage systems, and
assumes that readers have:
•Knowledge of Solaris and its management functionality
•Knowledge of Storage system management functionality
•Knowledge of Cluster software functionality
•Knowledge of Volume management software functionality
Product version
This document revision applies to HDLM for Solaris version 8.0.0 or later.
Release notes
Read the release notes before installing and using this product. They may
contain requirements or restrictions that are not fully described in this
document or updates or corrections to this document.
Document revision level
RevisionDateDescription
MK-92DLM114-21 November 2011 Initial Release
MK-92DLM114-22 July 2012Revision 1, supersedes and replaces
MK-92DLM114-23 August 2012Revision 2, supersedes and replaces
MK-92DLM114-24 November 2012 Revision 3, supersedes and replaces
MK-92DLM114-25 February 2013Revision 4, supersedes and replaces
MK-92DLM114-26 May 2013Revision 5, supersedes and replaces
MK-92DLM114-27 October 2013Revision 6, supersedes and replaces
MK-92DLM114-28 April 2014Revision 7, supersedes and replaces
MK-92DLM114-21
MK-92DLM114-22
MK-92DLM114-23
MK-92DLM114-24
MK-92DLM114-25
MK-92DLM114-26
MK-92DLM114-27
xiv
Preface
Hitachi Dynamic Link Manager (for Solaris) User Guide
Document organization
The following table provides an overview of the contents and organization of
this document. Click the chapter title in the left column to go to that chapter.
The first page of each chapter provides links to the sections in that chapter.
Chapter/AppendixDescription
Chapter 1, Overview of HDLM on
page 1-1
Chapter 2, HDLM Functions on
page 2-1
Chapter 3, Creating an HDLM
Environment on page 3-1
Chapter 4, HDLM Operation on
page 4-1
Chapter 5, Troubleshooting on
page 5-1
Chapter 6, Command Reference
on page 6-1
Chapter 7, Utility Reference on
page 7-1
Gives an overview of HDLM, and describes its
features.
Describes management targets and the system
configuration of HDLM, and the basic terms and
functions for HDLM.
Describes the procedures for setting up an HDLM
environment and the procedure for canceling those
settings.
Describes how to use HDLM by using both the HDLM
GUI and 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 managementtarget devices that connect paths or replacing the
hardware that makes up a path. describes how to
check path information by using the Windows
management tool.
Explains how to troubleshoot a path error, HDLM
failure, or any other problems that you might
encounter.
Describes all the HDLM commands.
Describes the HDLM utilities.
Chapter 8, Messages on page
8-1
Appendix A, Sun Cluster 3.2
Commands on page A-1
Appendix B, Functional
Differences Between Versions of
HDLM on page B-1
Related documents
The following related Hitachi Command Suite documents are available on the
documentation CD:
•Hitachi Command Suite Global Link Manager Installation andConfiguration Guide, MK-95HC107
•Hitachi Command Suite Global Link Manager Messages, MK-95HC108
Hitachi Dynamic Link Manager (for Solaris) User Guide
Provides information about viewing messages output
by HDLM. It also lists and explains the HDLM
messages and shows the actions to be taken in
response to each message.
Describes the Sun Cluster 3.2 commands.
Gives precautions on differences in functionality
between HDLM versions.
Preface
xv
•Hitachi Adaptable Modular Storage Series User's Guide
•Hitachi Simple Modular Storage Series User's Guide
•Hitachi Unified Storage Series User's Guide
•Hitachi USP Series User's Guide
•Hitachi Workgroup Modular Storage Series User's Guide
•Thunder9580V Series Disk Array Subsystem User's Guide
•Hitachi Universal Storage Platform V Hitachi Universal Storage Platform
VM User and Reference Guide
•Hitachi Virtual Storage Platform Series User's Guide
This document uses the following typographic conventions:
ConventionDescription
BoldIndicates text on a window, other than the window title, including
menus, menu options, buttons, fields, and labels. Example: Click OK.
ItalicIndicates a variable, which is a placeholder for actual text provided by
the user or system. Example: copysource-file target-file
Note: Angled brackets (< >) are also used to indicate variables.
Monospace
< > angled
brackets
[ ] square
brackets
{ } bracesIndicates required or expected values. Example: { a | b } indicates
| vertical barIndicates that you have a choice between two or more options or
underline
Indicates text that is displayed on screen or entered by the user.
Example: # pairdisplay -g oradb
Indicates a variable, which is a placeholder for actual text provided by
the user or system. Example: # pairdisplay -g <group>
Note: Italic font is also used to indicate variables.
Indicates optional values. Example: [ a | b ] indicates that you can
choose a, b, or nothing.
that you must choose either a or b.
arguments. Examples: [ a | b ] indicates that you can choose a, b, or
nothing. { a | b } indicates that you must choose either a or b.
Indicates the default value.
Example:
[ a | b ]
Conventions for storage capacity values
Physical storage capacity values (for example, disk drive capacity) are
calculated based on the following values:
xvi
Preface
Hitachi Dynamic Link Manager (for Solaris) User Guide
Physical capacity unitValue
1 kilobyte (KB)
1 megabyte (MB)
1 gigabyte (GB)
1 terabyte (TB)
1 petabyte (PB)
1 exabyte (EB)
1,000 (103) bytes
1,000 KB or 1,0002 bytes
1,000 MB or 1,0003 bytes
1,000 GB or 1,0004 bytes
1,000 TB or 1,0005 bytes
1,000 PB or 1,0006 bytes
Logical storage capacity values (for example, logical device capacity) are
calculated based on the following values:
Logical capacity unitValue
1 block512 bytes
1 KB
1 MB
1 GB
1 TB
1 PB
1,024 (210) bytes
1,024 KB or 1,0242 bytes
1,024 MB or 1,0243 bytes
1,024 GB or 1,0244 bytes
1,024 TB or 1,0245 bytes
1 EB
Accessing product documentation
The HDLM user documentation is available on the Hitachi Data Systems
Portal: https://portal.hds.com. Check this site for the most current
documentation, including important updates that may have been made after
the release of the product.
Getting help
Hitachi Data Systems Support Portal is the destination for technical support of
your current or previously-sold storage systems, midrange and enterprise
servers, and combined solution offerings. 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 Support Portal for
contact information:
Hitachi Data Systems Community is a new global online community for HDS
customers, partners, independent software vendors, employees, and
prospects. It is an open discussion among these groups about the HDS
portfolio of products and services. It is the destination to get answers,
discover insights, and make connections. The HDS Community complements
https://portal.hds.com.
1,024 PB or 1,0246 bytes
Preface
Hitachi Dynamic Link Manager (for Solaris) User Guide
xvii
our existing Support Portal and support services by providing an area where
you can get answers to non-critical issues and questions. Join theconversation today! Go to community.hds.com, register, and complete
your profile.
Comments
Please send us your comments on this document: doc.comments@hds.com.
Include the document title and number, including the revision level (for
example, -07), and refer to specific sections and paragraphs whenever
possible. All comments become the property of Hitachi Data Systems
Corporation.
Thank you!
xviii
Preface
Hitachi Dynamic Link Manager (for Solaris) User Guide
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?
□
HDLM Features
□
Overview of HDLM
Hitachi Dynamic Link Manager (for Solaris) User Guide
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.
The figure below shows the connections between hosts and storage systems.
A server on which HDLM is installed is called a host.
For details about the storage systems supported by HDLM, see Storage
Systems Supported by HDLM on page 3-4.
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
Balancing on page 2-10.
1-2
Figure 1-1 Connections between hosts and storage systems
Distributing a Load Using Load
Overview of HDLM
Hitachi Dynamic Link Manager (for Solaris) User Guide
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
Using Path Switching on page 2-15.
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 automatic
failback, HDLM automatically restores the route to the active state after
the user has corrected hardware problems in the route.
For details on performing failbacks, see
Failbacks Using Path Switching on page 2-15.
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 userdefined 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
Detecting Errors by Using Path Health Checking on page 2-28.
Performing Failovers and Failbacks
Performing Failovers and
Overview of HDLM
Hitachi Dynamic Link Manager (for Solaris) User Guide
1-3
1-4
Overview of HDLM
Hitachi Dynamic Link Manager (for Solaris) User Guide
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.
Devices Managed by HDLM
□
System Configuration
□
LU Configuration
□
Program Configuration
□
Position of the HDLM Driver and HDLM Device
□
Logical Device Files for HDLM Devices
□
Distributing a Load Using Load Balancing
□
Performing Failovers and Failbacks Using Path Switching
□
Intermittent Error Monitoring (Functionality When Automatic Failback Is
□
Used)
Detecting Errors by Using Path Health Checking
□
Distributing a Load by Using the Dynamic I/O Path Control Function
□
Error Management
□
HDLM Functions
Hitachi Dynamic Link Manager (for Solaris) User Guide
2-1
Collecting Audit Log Data
□
Integrated HDLM management using Global Link Manager
□
Cluster Support
□
2-2
HDLM Functions
Hitachi Dynamic Link Manager (for Solaris) User Guide
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-targetdevices.
HDLM management-target devices:
The following devices are from the storage systems listed in Section What
is HDLM? on page 1-2:
¢
SCSI devices (sd or ssd devices)
¢
Boot disks
¢
Swap devices
¢
Dump devices
#:
If you want to use these disks as HDLM management-target devices,
assign VTOC labels to them. EFI labels are not supported.
Non-HDLM management-target devices:
¢
SCSI devices (sd or ssd devices) other than those of the storage
systems listed in Section What is HDLM? on page 1-2
¢
Built-in disks in a host
¢
Devices other than disks (tape devices, etc.)
¢
Command devices of the storage systems listed in Section
HDLM? on page 1-2 (For example, Hitachi RAID Manager command
devices.)
#
#
#
What is
System Configuration
HDLM manages routes between a host and a storage system by using the
SCSI driver (sd or ssd driver). The host and storage systems are connected
using SAN with fiber cables or SCSI cables. The cable port on the host is a
host bus adapter (HBA). The cable port on the storage system is a port (P) on
a channel adapter (CHA).
A logical unit (LU) contained in a storage system is the target of input to, or
output from, the host. You can divide an LU into multiple areas. Each area
after the division is called a Dev. The Dev is equivalent to a slice or 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. When an LU has been divided
into multiple Devs, the number of paths set to the LU is equal to the number
that is found by multiplying the number of physical paths by the number of
Devs in the LU.
HDLM assigns an ID to each physical path and manages paths on a physicalpath basis. Because you do not need to be aware of the difference between
physical paths and paths to operate HDLM, the following descriptions might
simply refer to paths, without distinguishing between physical paths and
HDLM Functions
Hitachi Dynamic Link Manager (for Solaris) User Guide
2-3
paths. The ID that HDLM assigns to each path (physical path) is called a
AutoPATH_ID. A path is also sometimes called a managed object.
The following figure shows the HDLM system configuration.
Figure 2-1 HDLM System Configuration
The following table lists and describes the HDLM system components.
Table 2-1 HDLM System Components
ComponentsDescription
HBAA host bus adapter. This serves as a cable port on the host.
SANA dedicated network that is used for data transfer between the
host and storage systems
CHAA channel adapter
PA port on a CHA. This serves as a cable port on a storage
system.
LUA logical unit (a logical volume defined on the storage system).
This serves as the target of input or output operations from the
host.
DevAn area (slice or partition) that is created when an LU is divided
Physical pathA route that connects a host and an LU
PathA route that connects a host and a Dev
2-4
HDLM Functions
Hitachi Dynamic Link Manager (for Solaris) User Guide
LU Configuration
After you have properly installed HDLM, the LU configuration will change as
follows:
Before the installation of HDLM:
The host recognizes that an sd or ssd device is connected to each physical
path.
Thus, a single LU in the storage system is recognized as the same
number of LUs as that of physical paths.
After the installation of HDLM:
An HDLM device that corresponds one-to-one with the Dev in an LU in the
storage system is created above an sd or ssd device.
Thus, from the host, LUs in the storage system are also recognized as one
LU regardless the number of physical paths.
After the installation of HDLM, an LU recognized by a host is called a host LU
(HLU). The areas in a host LU that correspond to the Devs (slice or partition)
in a storage system LU are called host devices (HDev).
On a system using HDLM, the logical device file for the HDLM device is used
to access the target LU instead of the logical device file for the sd or ssd
device.
The logical device files for sd or ssd are deleted by HDLM.
The following figure shows the LU configuration recognized by the host, after
the installation of HDLM.
HDLM Functions
Hitachi Dynamic Link Manager (for Solaris) User Guide
2-5
Figure 2-2 LU Configuration Recognized by the Host After the Installation
The following table lists and describes the components recognized by the
host.
Table 2-2 Components Recognized by the Host
ComponentsDescription
HLUAn LU that the host recognizes via the HDLM driver. It is
HDevA Dev (a slice or partition) in an LU that the host
Program Configuration
HDLM is actually a combination of several programs. Because each program
corresponds to a specific HDLM operation, it is important to understand the
name and purpose of each program, along with how they are all interrelated.
of HDLM
called a host LU. No matter how many physical paths
exist, one host LU is recognized for one LU in the storage
system.
recognizes via the HDLM driver. It is called a host device.
No matter how many physical paths exist, one host
device is recognized for one Dev in the storage system.
2-6
The following figure shows the configuration of the HDLM programs.
HDLM Functions
Hitachi Dynamic Link Manager (for Solaris) User Guide
Figure 2-3 Configuration of the HDLM Programs
The following table lists and describes the functions of these programs.
Table 2-3 Function of HDLM Programs
Program nameFunctions
HDLM commandProvides the dlnkmgr command, which enables you to:
•Manage paths
•Display error information
•Set up the HDLM operating environment
HDLM utilityProvides the HDLM utility, which enables you to:
•Collect error information
•Add a new LU and delete an existing LU
(reconfiguring an HDLM device dynamically)
•Create an HDLM driver configuration definition file (/kernel/drv/dlmfdrv.conf)
•Create a correspondence table of logical device files
when migrating to HDLM 6.5.1
•Support the creation of a VxVM configuration file
•The unattended installation of HDLM
•Install Hitachi Command Suite Common Agent
Component
HDLM managerProvides the HDLM manager, which enables you to:
•Configure the HDLM operating environment
HDLM Functions
Hitachi Dynamic Link Manager (for Solaris) User Guide
2-7
Program nameFunctions
•Request path health checks and automatic failbacks
to be performed
•Collect error log data
HDLM alert driverReports the log information collected by the HDLM driver
to the HDLM manager. The driver name is dlmadrv.
HDLM driverControls all the HDLM functions, manages paths, and
detects errors. The HDLM driver consists of the following:
•Core logic component
Controls the basic functionality of HDLM.
•Filter component
Sends and receives I/O data. The driver name is
dlmfdrv.
•HDLM nexus driver
Performs operations such as reserving controller
numbers for logical device files of the HDLM device,
and managing HDLM driver instances for each HBA
port. The driver name is dlmndrv.
Position of the HDLM Driver and HDLM Device
The HDLM driver is positioned above the SCSI driver. Each application on the
host uses the HDLM device (logical device file) created by HDLM, to access
LUs in the storage system. The following figure shows the positions of the
HDLM driver and HDLM devices.
2-8
HDLM Functions
Hitachi Dynamic Link Manager (for Solaris) User Guide
Loading...
+ 616 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.