Hitachi Dynamic Link Manager for Solaris

Hitachi Freedom Storage™ Hitachi Dynamic Link Manager (HDLM)

User’s Guide for

Sun® Solaris™ Systems

HDLM User’s Guide for Sun® Solaris™ Systems iii

© 2002 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED

Notice: 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 Data Systems Corporation.

Hitachi Data Systems reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use. Hitachi Data Systems’ products and services can only be ordered under the terms and conditions of Hitachi Data Systems’ applicable agreements. All of the features described in this document may not be currently available. Refer to the most recent product announcement or contact your local Hitachi Data Systems sales office for information on feature and product availability.

This document contains the most current information available at the time of publication. When new and/or revised information becomes available, this entire document will be updated and distributed to all registered users.

Trademarks

Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd., and the Hitachi Data Systems design mark is a trademark and service mark of Hitachi, Ltd.

Hitachi Freedom Storage and Thunder 9200 and Lightning 9900 are trademarks of Hitachi Data Systems Corporation.

Tru64 UNIX is a registered trademark of Compaq Corporation in the US.

Sun Microsystems and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. SPARC and SPARCstation are trademarks or registered trademarks of SPARC International, Inc. and are licensed exclusively to Sun Microsystems, Inc.

UNIX is a registered trademark of X/Open Company Limited in the United States and other countries and is licensed exclusively through X/Open Company Limited.

Veritas and Veritas Cluster Server are trademarks or registered trademark of Veritas Software Corporation.

All other brand or product names are or may be trademarks or service marks of and are used to identify products or services of their respective owners.

iv Preface

Notice of Export Controls

Export of technical data contained in this document may require an export license from the United States government and/or the government of Japan. Please contact the Hitachi Data Systems Legal Department for any export compliance questions.

Document Revision Level

Revision Date Description

MK-92DLM114-P February 2002 Preliminary release

MK-92DLM114-P1 March 2002 Revision 1 of preliminary release. This revision supersedes and replaces MK-92DLM114-P.

MK-92DLM114-0 April 2002 Initial release. This revision supersedes and replaces MK-92DLM114-P1.

Source Document Revision Level

For a description of the changes in this document, please refer to the revision history of the Hitachi source document, Administrator’s Guide, Hitachi Dynamic Link Manager, Manual number: 3020-3-C23(E).

Changes in the Revision

Replaced and updated Figure 1.1, Figure 2.7, Figure 3.1, and Figure 3.3

Added references to “9900 V Series” to section 2.6.1.

Corrected “event log” to “OS log” (sections 2.7, 2.7.1, 2.7.2, and 3.4)

Replaced Figure 4.18 and corrected the text referring to it.

Removed /core-file-directory from Table 5.1.

Added more Error Codes (Table B.3)

Made various typographical error corrections (throughout)

HDLM User’s Guide for Sun® Solaris™ Systems v

Preface

The Hitachi Freedom Storage™ Hitachi Dynamic Link Manager (HDLM) User’s Guide describes and provides instructions for installing and using the HDLM feature of the Hitachi Freedom Storage Series disk array subsystems.

This manual is intended for system administrators who use Hitachi Dynamic Link Manager (hereafter referred to as HDLM) to operate and manage storage. The readers of this manual must have a basic knowledge of Solaris™ systems.

This user’s guide assumes that:

the user has a background in data processing and understands direct-access storage device (DASD) subsystems and their basic functions,

the user is familiar with the Hitachi Lightning 9900™ and Thunder 9200™ array subsystems,

and, the user is familiar with the Sun® Solaris™ file system, system commands, and utilities.

For further information on the 9900 subsystem, please refer to the Hitachi Lightning 9900™ User and Reference Guide (MK-90RD008). For further information on Hitachi Data Systems products and services, please contact your Hitachi Data Systems account team, or visit Hitachi Data Systems online at http://www.hds.com.

COMMENTS Please send us your comments on this document: [email protected].

Make sure to include the document title, number, and revision. Please refer to specific page(s) and paragraph(s) whenever possible.

(All comments become the property of Hitachi Data Systems Corporation.)

Thank you!

vi Preface

HDLM User’s Guide for Sun® Solaris™ Systems vii

Contents

Chapter 1 Overview of Hitachi Dynamic Link Manager (HDLM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.1 Hitachi Dynamic Link Manager (HDLM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.2 HDLM Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Chapter 2 HDLM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2.1 Configuration Basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.2 HDLM System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.3 LU Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.4 Host Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.5 Load Distribution Using Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2.6 Failover Using Path Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.6.1 Automatic Path Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.6.2 Manual Path Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.6.3 Path Status Transition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.7 Error Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.7.1 Logs Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.7.2 Error Information Filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.8 Cluster Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 3 HDLM Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.1 Overview of Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.1.1 Flow of Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.1.2 Program Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3.2 Constructing the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.2.1 Installation and Uninstallation from CD-ROM. . . . . . . . . . . . . . . . . . . . . . . . 19

3.2.1.1 Installing HDLM on a Solaris™ System . . . . . . . . . . . . . . . . . . . . . . 19 3.2.1.2 Automatic Mount Setup Procedure . . . . . . . . . . . . . . . . . . . . . . . . 22 3.2.1.3 Uninstalling HDLM on a Solaris™ System . . . . . . . . . . . . . . . . . . . . 23

3.2.2 Starting the HDLM Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.2.3 Stopping the HDLM Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.2.4 Checking Path Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3.3 Using the Error Management Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 3.3.1 Error Information Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.3.1.1 Information Displayed by the View Command . . . . . . . . . . . . . . . 27 3.3.1.2 Error Messages Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.3.2 Path Health Checking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 3.4 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.4.1 Actions Taken for a Path Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 3.4.2 Actions Taken for a Program Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

viii Contents

Chapter 4 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4.1 Overview of the Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 4.1.1 Command Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 4.1.2 Operations of the HDLM Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 4.1.3 Clear Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 4.1.4 Help Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 4.1.5 Offline Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 4.1.6 Online Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 4.1.7 Set Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 4.1.8 View Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 5 The HDLM DLMgetras Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 5.2 HDLM Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5.2.1 DLMgetras Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 5.2.2 DLMgetras Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 5.2.3 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 5.2.4 Important Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Appendix A Messages and Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Acronyms and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

HDLM User’s Guide for Sun® Solaris™ Systems ix

List of Figures

Figure 1.1 Connection Between Hosts and Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Figure 2.1 HDLM System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Figure 2.2 LU Configuration Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Figure 2.3 LU Configuration and HDLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Figure 2.4 Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Figure 2.5 Path Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Figure 2.6 Path Status Transition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Figure 2.7 Error Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Figure 2.8 Path Switching with Clustering Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Figure 3.1 HDLM Operational Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Figure 3.2 HDLM Program Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Figure 3.3 Editing the /kernel/drv/dlmfdrv.conf file. . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Figure 3.4 Specifying Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Figure 3.5 Restarting the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Figure 3.6 Command Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Figure 3.7 Output File Settings Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Figure 3.8 Example of editing the /etc/vfstab file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Figure 3.9 Stopping the HDLM Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Figure 3.10 Releasing the HDLM Manager Mount Points . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Figure 3.11 Restarting the Solaris™ System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Figure 3.12 Starting the HDLM Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Figure 3.13 Stopping the HDLM Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Figure 3.14 Logging Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Figure 3.15 View Command -path Information Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Figure 3.16 Example KAPL08022-E Error Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Figure 3.17 Troubleshooting Procedure for a Path Error . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Figure 3.18 Path Information Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Figure 3.19 Troubleshooting Procedure for a Program Error . . . . . . . . . . . . . . . . . . . . . . . 33 Figure 3.20 Program Error Action Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Figure 4.1 Command Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Figure 4.2 Clear Command Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Figure 4.3 Clear Statistics After User Command Execution Confirmation Request. . . . . . 37 Figure 4.4 Clear Statistics with No User Command Execution Confirmation Request. . . . 37 Figure 4.5 Help Command Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Figure 4.6 Display All HDLM Operations Available (Default) . . . . . . . . . . . . . . . . . . . . . . . 38 Figure 4.7 Display the online Operation Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Figure 4.8 Example of –help Command Displaying Operation Format. . . . . . . . . . . . . . . . 38 Figure 4.9 Path autoPATH_ID 000001 offline, No User Confirmation Request . . . . . . . . . 39 Figure 4.10 Path autoPATH_ID 000002 online, No User Confirmation Request. . . . . . . . . . 40 Figure 4.11 Setting the Log Level with User Command Execution Confirmation . . . . . . . . 43 Figure 4.12 View Command Displaying Program Information . . . . . . . . . . . . . . . . . . . . . . . 44 Figure 4.13 View Command Displaying Path Information . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Figure 4.14 Displaying HDLM Function Setting Information . . . . . . . . . . . . . . . . . . . . . . . . 45 Figure 4.15 Displaying HDLM Manager Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Figure 4.16 Displaying HDLM Alert Driver Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

x Contents

Figure 4.17 Displaying HDLM Driver Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Figure 4.18 Displaying Host Device Path Information (host device name = /mntpt). . . . . . 47 Table 4.10 Host Device Path Information Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Figure 5.1 DLMgetras Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Figure 5.2 Defining Information to be Collected. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

List of Tables

Table 2.1 HDLM System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Table 2.2 Components and Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Table 2.3 Log Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Table 2.4 Error Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Table 3.1 Functions of HDLM Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Table 3.2 Logging Level Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Table 3.3 Physical Path Representation in Solaris™ Systems . . . . . . . . . . . . . . . . . . . . . . 27

Table 4.1 HDLM Command Operations and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Table 4.2 Logging Level Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Table 4.3 Trace Levels Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Table 4.4 Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Table 4.5 View Command Parameters and Displayed Information . . . . . . . . . . . . . . . . . . 44 Table 4.6 HDLM Function Settings Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Table 4.7 HDLM Manager Information Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Table 4.8 HDLM Alert Driver Information Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Table 4.9 HDLM Driver Information Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Table 5.1 List of Error Information to be Collected by DLMgetras Utility . . . . . . . . . . . . 51

Table A.1 Message Format and Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Table A.2 Message Terminology and Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Table A.3 Messages and Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

HDLM User’s Guide for Sun® Solaris™ Systems 1

Chapter 1 Overview of Hitachi Dynamic Link Manager (HDLM)

1.1 Hitachi Dynamic Link Manager (HDLM)

The Hitachi Dynamic Link Manager (HDLM) program enables high-speed processing of large volumes of data on a network. Networks dedicated to data transfer, such as a storage area network (SAN), can use this technology to provide access to storage.

HDLM is a program that manages access paths to storage. It provides functions for distributing the load across paths and switching to another path if there is a failure in a path in use, thus improving reliability of the system. Figure 1.1 illustrates the connection between hosts and storage.

Figure 1.1 Connection Between Hosts and Storage

HDLM supports the following storage subsystems:

Hitachi Freedom Storage™ 5700E

Hitachi Freedom Storage™ 5800

Hitachi Freedom Storage™ 7700E

Hitachi Freedom Storage™ Thunder 9200™

Hitachi Freedom Storage™ Lightning 9900™

Hitachi Freedom Storage™ Lightning 9900™ V Series

2 Chapter 1 Overview of HDLM

1.2 HDLM Features

Load balancing: When multiple paths connect a host and storage, HDLM distributes the load across multiple paths. This prevents a heavily loaded path from affecting processing speed.

For details about load balancing, see section 2.5.

Failover: When multiple paths connect a host and storage, HDLM switches to another path if there is a failure in the current path being used. This allows processing to continue without interruption due to failure of a data access path.

For details about failover, see section 2.6.


Chapter 2 HDLM Configuration

2.1 Configuration Basics

In a large-scale storage system, fibre cables or SCSI cables connect a host and storage. The cable port on the host is a host bus adapter (HBA). The cable port on storage is a port (P) on a disk controller (DKC). A logical unit (LU) contained in storage is the target of input/output to and from the host. The LU can also be divided into devices (Dev). The connection path between the host and device is simply called a path. In the description of the operation of, and procedures for, HDLM, the connection path between the host and LU is called a physical path.

HDLM manages the paths. A path may also be called a management target.

Figure 2.1 shows the HDLM system configuration.

Figure 2.1 HDLM System Configuration

4 Chapter 2 HDLM Configuration

2.2 HDLM System Components

The following table contains the HDLM system components (Table 2.1).

Table 2.1 HDLM System Components

Components Description

Dev A logical division of a logical unit (LU). For Solaris™ systems, a device is called a slice.

DKC Disk controller

HBA Host bus adapter. This serves as a cable port on the host.

LU Logical unit in storage. An LU is the target of input/output to and from the host.

P A port on a disk controller. This serves as a cable port on storage.

Path A connection path between the host and device.

Physical path A connection path between the host and LU.

2.3 LU Configuration

The host operating system recognizes an LU for each physical path. A host LU (HLU) is an LU that the operating system recognizes. Each host LU has the same device as the storage LU has. This is called a host device (HDev). Even if multiple host devices actually point to the same device in storage, the user sees independent host devices. Figure 2.2 shows the LU configuration and how an administrative tool displays the disk configuration.

Figure 2.2 LU Configuration Display


2.4 Host Components

The following table contains HDLM component abbreviations and descriptions (Table 2.2).

Table 2.2 Components and Descriptions

Components Description

HDev Host device, a device within a host LU. The HDev entity is a device in storage.

HLU Host LU, an LU that the host recognizes. The HLU entity is an LU in storage.

HDLM consolidates identical LUs that are duplicates, as shown in Figure 2.2. This allows administrative tools such as Disk Administrator to display the actual LU storage configuration. Figure 2.3 is an example of LU storage configuration and how an administrative tool displays disk configuration when using HDLM.

Figure 2.3 LU Configuration and HDLM


2.5 Load Distribution Using Load Balancing

When a system contains more than one path for a single device within an LU, HDLM can distribute the load across the paths by using the paths to issue I/O commands. This function is called load balancing. Load balancing prevents a heavily loaded path from affecting performance of the entire system.

When using the Hitachi Freedom Storage™ 5700E, Hitachi Freedom Storage™ 5800, or Hitachi Freedom Storage™ Thunder 9200™, HDLM performs load balancing between two or more owner paths or between two or more non-owner paths. An owner path is a path that uses the disk controller (owner disk controller) to provide the fastest access to the LU. A non-owner path is a path that uses a disk controller other than the owner disk controller (non-owner disk controller). Since the owner disk controller varies depending on the LU, the owner path also varies depending on the LU. To prevent performance deterioration for the entire system, HDLM does not perform load balancing between an owner path and a non-owner path.

For example, when the Hitachi Freedom Storage™ 5700E, Hitachi Freedom Storage™ 5800, or Hitachi Freedom Storage™ Thunder 9200™ is in use, the owner disk controller for LU0 is DKC0. When a device within LU0 is accessed, HDLM performs load balancing between the paths that access the device via physical paths (1) and (2) (that is, between owner paths), or between the paths that access the device via physical paths (3) and (4) (that is, between non-owner paths).

When the Hitachi Lightning 9900™, 7700E and 9900V subsystems are in use, all the paths are owner paths, therefore HDLM performs load balancing among all the paths accessing the same device.

For example, when the Hitachi Lightning 9900™, 7700E and 9900V subsystems are in use, all the paths are the owner paths; therefore, when a device within LU0 is accessed, HDLM performs load balancing among all the paths that access the device via physical paths (1), (2), (3), and (4). Figure 2.4 illustrates this.


Figure 2.4 Load Balancing

You can specify whether to use load balancing by executing the set operation. For details about the set operation, see section 4.1.7.


2.6 Failover Using Path Switching

When the system contains more than one path for a single device within an LU and an error occurs in the path being used, HDLM can switch to another normal path to allow the system to continue to operate. This function is called failover. Two types of failover are available:

Automatic path switching

Manual path switching

Note: When using the Hitachi Freedom Storage™ 5700E, the Hitachi Freedom Storage™ 5800, and the Hitachi Freedom Storage™ Thunder 9200™, be sure to set the data share mode.

2.6.1 Automatic Path Switching

If an error occurs in a path, the Failover function automatically places the error path offline to allow the system to continue to operate using another online path. Automatic path switching is applicable to errors of the following levels that occurred in a management target:

Critical: A fatal error that may stop the system.

Error: A high-risk error that can be avoided by using failover or other countermeasures.

For more information about error levels, see section 2.7.2.

When using the Hitachi Freedom Storage™ 5700E, Hitachi Freedom Storage™ 5800, or Hitachi Freedom Storage™ Thunder 9200™, HDLM selects the switching destination from the paths that access the same device, in the order of owner paths and non-owner paths. For example, in Figure 2.5, the owner disk controller for LU0 is DKC0, and access to a device within LU0 is made only by the path via physical path (1). After the path being used is placed offline, as the first candidate for the switching destination, HDLM selects the path that accesses the same device via physical path (2). As the second candidate, HDLM selects the path that accesses the same device via physical path (3) or (4).

When the Hitachi Lightning 9900™, 7700E and 9900V subsystems are in use, all the paths are owner paths, meaning that all the paths accessing the same device can be used as switching destinations. For example, if a device within LU0 is accessed using only the path that is via physical path (1) and the path being used is placed offline, as the switching destination HDLM selects one of the paths that access the same device via physical path (2), (3), or (4) (Figure 2.5).

All paths that use the same physical path are switched at once. Therefore, if an error occurs in a path, HDLM switches all the other paths that are affected via the same physical path.


Figure 2.5 Path Switching

After recovery from the error, the offline path does not become active automatically. Executing the online operation of the HDLM command places the path online that was placed offline due to the error.

When using the Hitachi Freedom Storage™ 5700E, Hitachi Freedom Storage™ 5800, or Hitachi Freedom Storage™ Thunder 9200™, HDLM selects the path to use from online owner paths, and then from online non-owner paths. Therefore, if the online operation places an owner path online while any non-owner path is in use, the path to use is switched to the owner path.

When the Hitachi Freedom Storage™ Lightning 9900™, 7700E, or 9900V subsystems are in use, all the paths are owner paths. Therefore, if the online operation places any path online, the path to use is not switched.

For details about the online operation, see the description about online in Chapter 4.


2.6.2 Manual Path Switching

To manually switch a path, you can execute the offline operation of the HDLM command to place the path offline. Manually and temporarily switching a path is useful for maintenance of the system.

HDLM selects the switching destination path the same way as for automatic path switching. When using the Freedom Storage 5700E, Freedom Storage 5800, or Thunder 9200™, HDLM selects the switching destination path from owner paths and then from non-owner paths. When the Hitachi Lightning 9900™, 7700E, and 9900V subsystems are in use, all the paths accessing the same device can be the possible switching destination at the same time.

All paths that use the same physical path are switched at once. Therefore, if a path is placed offline, HDLM switches all the other paths that are via the same physical path.

Executing the online operation places the offline path online. HDLM selects the path to use after executing the online operation in the same way as for automatic path switching. When using the Hitachi Freedom Storage™ 5700E, Hitachi Freedom Storage™ 5800, or Hitachi Freedom Storage™ Thunder 9200™, HDLM selects the path to use from online owner paths, and then from online non-owner paths. When the Hitachi Lightning 9900™, 7700E and 9900V subsystems are in use, the path to use is not switched after execution of the online operation.

For details about the offline and online operations, see the descriptions about offline and online in Chapter 4.


2.6.3 Path Status Transition

There are two types of path status: online and offline. Online means the status in which I/O can normally be issued to the path. Offline means the status in which I/O cannot be issued to the path because the user executed the offline operation of the HDLM command.

Figure 2.6 shows the status transition of a path.

Figure 2.6 Path Status Transition

The last online path for each device is not placed offline even if an error occurs or even if the user executes the offline operation. This ensures access to the LU.

If an error occurs in the last online path for each device, HDLM checks the status of other paths that are already placed offline. If any path can be placed online, HDLM places that path online and switches to it.


2.7 Error Management

HDLM has an error management function that filters error information according to the error level and collects it in logs.

Figure 2.7 shows an overview of error management.

Figure 2.7 Error Management


2.7.1 Logs Collected

HDLM collects error logs and OS logs. The log files are in ASCII format and describe and explain the status of the error, and present an analysis of the cause of the error for troubleshooting purposes.

HDLM Error log files are stored in the directory /opt/DynamicLinkManager/log/.

Table 2.3 describes the logs.

Table 2.3 Log Descriptions

Log name Description

Error log Error information for the user-defined level is collected from detected errors. By default, HDLM collects all detected error information.

OS log Information about highly dangerous errors (Critical or Error level) is collected from detected errors. OS logs that are collected by UNIX®-based systems are called syslogs. Syslogs can be checked using a text editor (see Note 1).

Note 1: Syslog file paths are specified in the /etc/syslog.conf file. The syslog default file path collected by Solaris™ is /var/adm/messages. For details about error levels, see section 2.7.2.


2.7.2 Error Information Filtering

Errors that HDLM detects are classified into error levels. Table 2.4 shows the error levels.

Table 2.4 Error Descriptions

Error level Meaning OS Log

Critical Fatal error that may stop the system Error

Error High-risk error that can be avoided by using failover or other countermeasures

Error

Warning Although the system continues to operate, it is risky to let the error remain.

—

Information Indicates the operation history when the system operates normally. —

The Log Filter organizes error information according to error level. It filters error information to be collected for an error log or an OS log. The Log Filter does not collect an error log.

The error log collects error information for all logging levels, including Error and higher, Warning, and Information levels. The errors logged are categorized in the following order:

Does not collect an error log

Error or higher level.

Warning or higher level.

Information or higher level (that is, all levels).

For details about how to set the logging level, see section 3.3.


2.8 Cluster Support

HDLM supports Veritas Cluster Server ™ software. HDLM automatically recognizes the cluster configuration at startup and performs the appropriate processing.

When load balancing is supported in a cluster configuration, HDLM uses more than one physical path on the active host for one LU, and accesses devices within the LU by using the paths via the physical path.

When load balancing is not supported in a cluster configuration, HDLM uses only one of the physical paths of the active host for one LU, and accesses devices within the LU by using the paths that are via the physical path.

All paths that use the same physical path are switched at once; therefore, if an error occurs in a path, HDLM switches all the other paths that are via the same physical path to other paths using another physical path of the active host.

When the active host no longer has any physical path that contains only online paths, the cluster software switches to the standby host. For example, to access a device within the LU, HDLM uses a path that is via physical path (1) of the active host (Figure 2.8). If a path is placed offline, to continue processing HDLM switches all the other paths that are via physical path (1). HDLM switches them to the paths that are via physical path (3) of the active host. If a path that is via physical path (3) is also placed offline and the active host no longer has any physical path that contains only online paths, the cluster software switches to the standby host. Then, HDLM in the standby host uses physical path (2) or (4), and accesses the devices within the LU by using paths that are via the selected physical path.

For details about node switching triggers, refer to the Veritas Cluster Server™ product documentation.

Figure 2.8 Path Switching with Clustering Support

Note: To use the HDLM functions in a cluster configuration, HDLM must be installed in both the active host and standby host.


Chapter 3 HDLM Operations This chapter describes the procedure required for HDLM operation, including installing HDLM, setting the error management function, and performing troubleshooting.

This chapter contains the following sections:

3.1 Overview of operations

3.2 Constructing the system

3.3 Using the error management function

3.4 Troubleshooting

3.1 Overview of Operations

3.1.1 Flow of Operations

Figure 3.1 shows the flow of HDLM operations.

Figure 3.1 HDLM Operational Flow

Note 1: See hardware notes supplied with the product.

18 Chapter 3 HDLM Operations

3.1.2 Program Configuration

HDLM is a combination of programs. To use HDLM, these programs must be running normally. Figure 3.2 shows the HDLM program configuration.

Figure 3.2 HDLM Program Configuration

Table 3.1 shows the function of each program.

Table 3.1 Functions of HDLM Programs

Program Name Function

HDLM command Manages the paths and displays error information.

HDLM manager Collects error logs.

HDLM alert driver Reports the error information detected by the HDLM driver to the HDLM manager.

HDLM driver Controls the functions, manages the paths, and detects errors. The HDLM driver contains the core logic component that controls the HDLM basic functions, and the filter component that sends and receives I/O.


3.2 Constructing the System

This section describes the required procedures for constructing an HDLM system.

3.2.1 Installation and Uninstallation from CD-ROM

The Hitachi Network Objectplaza Trace Library is installed together with HDLM.

This subsection describes the installation method and the uninstallation method for the Sun® Solaris™ operating system.

For details on updating HDLM, uninstalling the software, and then re-installing it, see section 3.2.1.

3.2.1.1 Installing HDLM on a Solaris™ System

To install HDLM:

1. Log on as a user with root permission.

2. Insert the CD-ROM into the drive.

– After a few seconds, the CD-ROM will be automatically mounted; the CD-ROM mount point will be displayed in the file list.

3. If the CD-ROM is not automatically mounted, execute the following command:

– # mount /mount-point-of-CD-ROM

4. Execute the following installation command:

– # pkgadd -d /mount-point-of-CD-ROM DLManager

5. Follow the messages on the screen.

6. When the installation is completed, execute the following command to ensure that the package is installed:

– # pkginfo -l DLManager


7. Edit the /kernel/drv/dlmfdrv.conf file to specify the name of the physical device file for the slice you want to use for path switching. Figure 3.3 shows the system configuration and an example of editing "dlmfdrv.conf".

Figure 3.3 Editing the /kernel/drv/dlmfdrv.conf file


– Variables:

name: Specify the name of device driver. Specify dlmfdrv (DLM driver).

parent: Specify the node to link. Specify pseudo to specify the HDLM driver.

Instance: Specify the instance number of the driver. The numbers must be sequentially specified from 0 and must be unique.

FilterPath:

Specify the name of the path that is managed by one instance of the HDLM driver.

Specify the device node name for the sd driver under the /devices directory.

sd@4,2:c stands for the target ID, LUN, and the slice of the sd driver:

4 (hexadecimal) stands for the target ID

2 stands for LUN

c stands for the slice

Specify slice 0 to slice 7 using a to h in lower case

The slice c stands for the entire LU. Specify from slice c.

Note: To see available devices on the system, execute the command shown in Figure 3.4

# cd /dev/dsk# ls -l

Figure 3.4 Specifying Variables

8. After the kernel/drv/dlmfdrv.conf file has been modified, the system must be re-booted. Execute the command shown in Figure 3.5to restart the system:

# reboot -- -r

Figure 3.5 Restarting the System

9. Mount the logical block device file: /dev/dsk/dlmfdrvn (n stands for the instance number of the driver) of the configured HDLM. An example of command execution is shown in Figure 3.6.

# mkdir /mntpt# mount -F ufs /dev/dsk/dlmfdrv4 /mntpt

Figure 3.6 Command Execution


3.2.1.2 Automatic Mount Setup Procedure

To automatically mount HDLM-devices at the Solaris™ system startup, follow these steps:

1. Execute the following command (Figure 3.7) to output the /etc/vfstab file settings image:

# mount -p

Figure 3.7 Output File Settings Image

2. Use a text editor to edit the /etc/vfstab file while referencing the settings image. For more information, execute the man vfstab command and read the information displayed.

Figure 3.8 Example of editing the /etc/vfstab file

3. Add the shaded code show in Figure 3.8. The line above the shaded line is set during the Solaris™ system installation and setup. The contents of the lines above the shaded line differ depending on the environment.

4. In the mount point column, specify the mount point. In the mount at boot column, specify yes.


3.2.1.3 Uninstalling HDLM on a Solaris™ System

To uninstall HDLM:

1. Log on to Solaris™ as a user with root permission.

2. Terminate all programs that issue I/Os by using HDLM.

3. Execute the following command (Figure 3.9) to stop the HDLM manager:

# /etc/init.d/DLMManager stop

Figure 3.9 Stopping the HDLM Manager

4. Execute the following command (Figure 3.10) to release the mount points that use the HDLM Manager:

# umount /mount-point

Figure 3.10 Releasing the HDLM Manager Mount Points

5. Execute the following uninstallation command:

# pkgrm DLManager

6. When the message confirming the uninstallation is displayed, enter y. Uninstallation will begin.

7. When you complete uninstallation, execute the following command (Figure 3.11) to restart the system:

# reboot -- -r

Figure 3.11 Restarting the Solaris™ System


3.2.2 Starting the HDLM Manager

For UNIX®-based systems, the HDLM manager uses the start script that is set up during installation. Therefore, starting a UNIX®-based operating system automatically starts the HDLM manager.

If the HDLM manager has stopped, start it using the following steps:

1. Initiate the start script that was set up during installation.

2. Log on to the Solaris™ system as a user with root permission, and then execute the following command (Figure 3.12):

# /etc/init.d/DLMManager start

Figure 3.12 Starting the HDLM Manager

3.2.3 Stopping the HDLM Manager

HDLM stops automatically when uninstalling, or when installing a new instance of HDLM on a system in which HDLM is already installed. If HDLM does not stop automatically, stop it using the following steps:

1. Initiate the stop script that was set up during installation.

2. Log on to the Solaris™ system as a user with root permission, and then execute the following command (Figure 3.13):

# /etc/init.d/DLMManager stop

Figure 3.13 Stopping the HDLM Manager


3.2.4 Checking Path Information

You can use the HDLM functions such as load balancing and failover when there is more than one online path for a single device. After installing HDLM and after changing the hardware configuration, you need to check the path information, including the configuration of paths and their status.

Note: After changing the hardware configuration of the system be sure to restart the machine. This allows HDLM to recognize the changes in the hardware configuration.

Note: Be sure to start the storage subsystem before starting the host machine. This allows the operating system to detect the storage subsystem.

To check the path information:

1. Execute the view operation of the HDLM command to display the path information.

– Enter as follows:

>dlnkmgr view -path > pathinfo.txt

pathinfo.txt indicates the redirect destination file name.

– Set the file name according to your environment. Executing this command displays information about all paths.

2. Open the redirected file (pathinfo.txt in step 1) and check the following:

– LUs that physical paths access

A PathName identifies the physical path. A combination of DskName and iLU identifies the LU that a physical path accesses.

– If the physical paths access the same LU via different host bus adapters, check that:

The first number in PathName (port number of the host bus adapter) differs among the physical paths accessing the same LU

There are as many port numbers for the separate host bus adapters as there are physical host bus adapters.

– If the physical paths access the same LU via different disk controllers, check that:

Multiple disk controllers are physically mounted

The DkcPort indication (port number of the disk controller) differs among the physical paths accessing the same LU, and indicates the port number of different disk controller.

– Path status:

Check whether the state conditions are all Online.

For details about the items that the view operation displays, see section 4.1.8.


3.3 Using the Error Management Function

HDLM has the error management functions for logging and displaying error information, and path health checking. This section describes how to set the logging level and how to check information if an error occurs.

The example in Figure 3.14 sets 2 for the value of the logging level. Table 3.2 shows the values of the logging level.

>dlnkmgr set -ellv 2

Figure 3.14 Logging Level

Table 3.2 Logging Level Values

Value Description

0 Do not collect an error log.

1 Collect error information for the Error or higher level.

2 Collect error information for the Warning or higher level.

3 Collect error information for the Information or higher level (that is, all levels).

The default is 3.

To check the set value for the logging level, use the HDLM view command to display the HDLM function settings.

3.3.1 Error Information Checking

You can check for an error by referring to:

Information displayed by the HDLM view command

The message that is output when an error occurs.


3.3.1.1 Information Displayed by the View Command

You can use the view command to check error information. For example, specify –path in the view command parameters to display the path information.

Figure 3.15 shows an example of displayed information. Note: Equipment that is not mounted is also displayed when the -hdev parameter is not used.

>dlnkmgr view –path –hdev /mntptPaths:00002 OnlinePaths:00002PathState IO-Counts IO-ErrorsOnline 1332 0

PathID PathName DskName iLUDkcPort State Type IO-Counts IO-Errors DNum HDevName000011 004.0004.00029.0002 HITACHI.DF400F .1234 00101B Online own 1332 0 1 /mntpt

...

KAPL01001-I The HDLM command completed successfully. Operation name = view>

Figure 3.15 View Command -path Information Display

Check the following items in the display for path errors:

PathID: The ID that HDLM assigned to the path at system startup. This ID is called AutoPATH_ID.

PathName: The path name that identifies a physical path. A path name consists of four items separated by a period. Table 3.3 shows these items and their representation in Solaris™ systems.

Table 3.3 Physical Path Representation in Solaris™ Systems

Items Representation in Solaris™ systems (see Note)

Port number of the host bus adapter (Display example: 004) HBA Port number

Bus number (Display example: 0004) 0 (fixed)

Target ID (Display example: 00029) Target Id

Host LU number (Display example: 0002) Logical Unit ID or LUN


Note: The following is additional information about path name items in Solaris™ systems:

– Port number of Host Bus Adapter:

See the instance number of the corresponding Host Bus Adapter defined in the /etc/path_to_inst file.

– Bus number:

Is fixed to 0

– Target ID

See the target clause in the /kernel/drv/sd.conf file.

– Host LU number:

See the LUN clause in the /kernel/drv/sd.conf file.

DskName: The storage subsystem name identifying the storage subsystem. A storage subsystem name consists of three items separated by a period:

– Vendor ID (Display example: HITACHI): Vendor name of the storage subsystem

– Product ID (Display example: DF400F): Model name of the storage subsystem

– Serial number (Display example: 1234): Serial number of the storage subsystem.

Note: To physically identify the storage subsystem, use the management program for the storage subsystem to refer to these information items.

iLU

– The number assigned to an LU managed in the storage subsystem. You can use this number to identify the LU in the storage subsystem.

– For the Hitachi Lightning 9900™, 7700E and 9900V subsystems, the first two letters of the iLU indicates the CU (Control Unit) number, and the last two letters indicates the internal LU number in the CU. For the Hitachi Freedom Storage™ 5700E, Hitachi Freedom Storage™ 5800, and Hitachi Freedom Storage™ Thunder 9200, the entire iLU indicates the internal LU number in the storage subsystem.

– To physically identify the LU, use the management program for the storage subsystem to refer to iLU.

DkcPort

– Port number of the disk controller. You can use this number to identify the disk controller mounted on the storage subsystem.

– To physically identify the disk controller, use the management program for the storage subsystem to reference this port number.


State: Status of the path

– Online: path is online

– Offline(C): Path is offline by a command

– Offline(E): Path is offline due to an error.

Note: A path that has the same PathName as a path whose state is Offline may be in an error status even though its state is Online.

Dnum: Device number

– Device numbers are assigned to each device within an LU.

– The device numbers are assigned sequentially from 0.

–

HdevName: Host device name

– In Solaris™ systems, the mount point is displayed in this field. When the file system is not mounted, a hyphen (-) is displayed.

3.3.1.2 Error Messages Displayed

Referring to the output message in the OS log allows you to check the information about the error. For example, the following message is output if a path error occurs (Figure 3.16):

KAPL08022-E

A path error occurred.ErrorCode=%d, PathID=%d, PathName=%d.%d.%d.%d, DNum=%d, HDevName=%s

Figure 3.16 Example KAPL08022-E Error Message

Note: %d is a decimal number and %s is a character string.

Check the following items in the display for path errors:

ErrorCode:

– The error number when the operating system detected the path error.

PathID:

– The ID that HDLM assigned to the path at system startup.

– This ID is called AutoPath_ID.

– Note: this is the same as PathID that the view operation displays.


PathName:

– Identifies the physical path. A path name consists of four items separated by a period.

– Note: this is the same as PathName that the view operation displays. For details, see the description of PathName in Table 3.3.

Dnum:

– Device number. Device numbers are assigned to each device within an LU.

– The device numbers are assigned sequentially from 0.

– Note: This is the same as DNum that the view operation displays.

HdevName:

– Host device name.

– In Solaris® systems, the mount point is displayed in this field. When the file system is not mounted, a hyphen (-) is displayed.

– This is the same as HDevName that the view operation displays.

3.3.2 Path Health Checking

The HDLM program checks the status of the paths at regular intervals through a subprogram called path health checking. When an error occurs in a path in the Online status, path health checking changes the status of the path to the Offline(E) status. When a path that was in the Offline(E) status recovers from an error, path health checking changes the status of the path to the Online status.

Path health checking checks paths in the Online status and paths in the Offline(E) status.

Path health checking does not check the status of the paths in the Offline(C) status by executing the offline operation.

You can specify whether to use path health checking by executing the set operation. For details about the set operation, see the description of set in section 4.1.7.

Note: In previous versions of HDLM, executing a batch file that defined the online operation performed path health checking. With the current version, executing the set operation performs path health checking; do not execute the batch file. If the set operation is executed, the result will be duplicate instances of path health checking running simultaneously.


3.4 Troubleshooting

This section describes the actions you should take HDLM detects a path error or when an error occurs in a HDLM program.

For details about hardware maintenance, see the appropriate hardware manual accompanying the purchased product.

3.4.1 Actions Taken for a Path Error

When a path error is detected, HDLM performs failover for the path and outputs a KAPL08022 message. Figure 3.17 shows the troubleshooting procedure when this message is output.

Figure 3.17 Troubleshooting Procedure for a Path Error


Monitoring the message

– Read the KAPL08022 message output to the OS log.

– For details about the contents of the message, see section 3.3.1.2 and Appendix A.

Obtaining the path information

– Execute the following command to obtain the path information (Figure 3.18):

>dlnkmgr view -path > pathinfo.txt

Figure 3.18 Path Information Command

– pathinfo.txt indicates the redirect destination file name. Determine the file name according to your environment.

Extracting the error path:

– Check the obtained path information to find the error path. The path whose state indication is Offline(E) is the error path. (A path that has the same PathName as a path whose state is Offline may be in an error status even though its state is Online.)

– Next, search for the online error path. For the path for which Online is indicated in the path information, compare its PathName with the PathName in the KAPL08022 message. If both PathNames are the same, this path has the error. (Since HDLM always leaves one online path for each device, an error path actually exists even if the path information only indicates Online.)

Identifying the hardware that may have the error:

– Check the DskName, iLU, and DkcPort of the error path to narrow down the hardware that may have the error.

– Use the management program for the storage subsystem to check the DskName, iLU, and DkcPort to physically identify the hardware.

Identifying the error section and taking corrective action:

– Use the administrative tools for the operating system and hardware to identify the error section, and then take corrective action.

Placing the path online:

– After recovery from the error, place the paths online that were placed offline due to the error. Execute the following command:

>dlnkmgr online

This command places all the offline paths online.


3.4.2 Actions Taken for a Program Error

The following describes the actions you should take when an error occurs in an HDLM program. Figure 3.19 shows the troubleshooting procedure.

Figure 3.19 Troubleshooting Procedure for a Program Error

Monitoring the message

– If an error occurs in the HDLM program, a message whose message ID is other than KAPL08xxx is output to the OS log.

– Check the output message. Messages with error level E (Error) or higher require corrective action.

Taking the action for the error

– Take the action according to the information in Appendix A, Messages and Alerts.

– If the same error occurs again after you take the action, check the status of the HDLM program. Execute the following command (Figure 3.20):

>dlnkmgr view -sys

Figure 3.20 Program Error Action Command


– If the KAPL01013-E message is displayed, execute the following commands:

>dlnkmgr view -sys -msrv>dlnkmgr view -sys -adrv>dlnkmgr view -sys -pdrv

– These commands display information about the HDLM manager, HDLM alert driver, and HDLM driver. Check the indications for HDLM Manager, HDLM Alert Driver, and HDLM Driver, and then take any of the following actions:

When HDLM Manager shows Dead, start the HDLM manager service.

– Note: For details on how to start the HDLM manager, see section 3.2.2.

When the HDLM Alert Driver shows Dead, restart the system.

When the HDLM Driver shows Dead, restart the system.

Note: If the same error occurs again after you take the above action, contact maintenance personnel.

Obtaining program information

– Obtain the information you need to report to maintenance personnel.

– For Solaris™ systems, HDLM provides a utility (DLMgetras) for collecting error information that should be reported to maintenance personnel. For details, see the description of DLMgetras in Chapter 5.

Contacting maintenance personnel

– Contact maintenance personnel and report the obtained information.


Chapter 4 Commands This chapter describes the HDLM commands set. The following topics are covered:

Overview of the commands

clear (Clears the management information)

help (Displays the operation format)

offline (Places a path offline)

online (Places one or all offline paths online)

set (Sets the operating environment)

view (Displays information)

4.1 Overview of the Commands

This section describes how to specify the commands for HDLM, and the operations of the HDLM command itself.

4.1.1 Command Format

Enter a command using the following format:

dlnkmgr operation-name [parameter[parameter-value]]

Figure 4.1 Command Format

Variable definitions are as follows:

dlnkmgr

– Command name

operation-name

– Type of the operation that is entered after dlnkmgr.

parameter

– Value required for the operation

parameter-value

– Value required for the parameter

36 Chapter 4 Commands

4.1.2 Operations of the HDLM Command

Table 4.1 shows the operations of the HDLM command and their functions.

Table 4.1 HDLM Command Operations and Functions

Operation Functions

clear Clears the management information for the Dynamic Link Manager system.

help Displays the format of the operation used for Dynamic Link Manager.

offline Places an online path offline.

online Places one or all offline paths online.

set Sets the Dynamic Link Manager operating environment.

view Displays Dynamic Link Manager program information and path information.

Notes:

1. When you are using HDLM for Solaris™ systems, execute the command as a user with root permission.

2. To specify a value containing a space in parameter, enclose the entire value in double quotes (").


4.1.3 Clear Operation

Function: clears management information from the HDLM system.

Format:

dlnkmgr clear -pdst [-s]

Figure 4.2 Clear Command Format

Parameters:

– -pdst: Clears statistics such as the path error count.

– -s: Executes the command without displaying user confirmation message. Specify this parameter if you want to skip the user confirmation message for a shell script or batch file.

Examples ( see Figure 4.3, Figure 4.4):

>dlnkmgr clear -pdstdlnkmgr clear -pdstExecute command? [y/n]:y ... Enter y to execute the command.KAPL01001-I The DLM command completed successfully. Operation name = clear>

Figure 4.3 Clear Statistics After User Command Execution Confirmation Request

>dlnkmgr clear -pdst -sKAPL01001-I The DLM command completed successfully. Operation name = clear>

Figure 4.4 Clear Statistics with No User Command Execution Confirmation Request


4.1.4 Help Operation

Function: displays the format of an HDLM operation

Format:

dlnkmgr help [operation-name]

Figure 4.5 Help Command Format

Parameters:

– operation-name: specifies the name of an operation used in HDLM.

Note: If you do not specify the operation name, the command displays all the operations (default):

Examples (Figure 4.6 and Figure 4.7):

>dlnkmgr helpdlnkmgr { clear | help | offline | online | set | view }>

Figure 4.6 Display All HDLM Operations Available (Default)

>>dlnkmgr help onlinedlnkmgr online [-path] [-pathid AutoPATH_ID] [-s]>

Figure 4.7 Display the online Operation Format

Note: For any operation, entering –help following the operation name will display the format of that operation (Figure 4.8).

>dlnkmgr clear -helpdlnkmgr clear -pdst [-s]>

Figure 4.8 Example of –help Command Displaying Operation Format


4.1.5 Offline Operation

Function:

– Places an online path offline. Use the parameter to specify the path you want to place offline.

– The last path accessing each device cannot be placed offline.

Format:

dlnkmgr offline [-path] -pathid AutoPATH_ID [-s]

Note: Placing too many paths offline may prevent path switching if an error occurs. Before placing the path offline, use the view operation to check how many online paths remain.

Parameters:

– -path: specifies manipulating a path that Dynamic Link Manager manages.

Note: Be sure to specify the target path in the subsequent parameter. This parameter is optional because the offline operation is only effective on paths.

– -pathid AutoPATH_ID: specify the AutoPATH_ID that Dynamic Link Manager assigned to the path during system startup. The command places the specified path offline. Use the view operation to check the AutoPATH_ID.

Note: Leading zeros in the AutoPATH_ID can be omitted when it is specified for the parameter value.

– -s: executes the command without displaying the message asking for confirmation from the user. Specify this parameter if you want to skip the confirmation for a shell script or batch file.

Example (Figure 4.9):

>dlnkmgr offline -pathid 1 -sKAPL01022-I 1 path(s) were processed. Operation name = offlineKAPL01001-I The DLM command completed successfully. Operation name = offline>

Figure 4.9 Path autoPATH_ID 000001 offline, No User Confirmation Request


4.1.6 Online Operation

Function:

– Places one or all offline paths online.

– Use this parameter to specify the path you want to place online.

Format:

dlnkmgr online [-path] [-pathid AutoPATH_ID] [-s]

Parameters:

– -path: specifies manipulating a path that HDLM manages. Specify the target path in the subsequent parameter.

Note: If you do not specify the subsequent parameter, the command changes all the offline paths to online.

Note: This parameter is optional because the online operation is only effective on paths.

– -pathid AutoPATH_ID: specifies the AutoPATH_ID that HDLM assigned to the path during system startup. Places the specified path online.

Note: Use the view operation to check the AutoPATH_ID. Leading zeros in the AutoPATH_ID can be omitted when it is specified for the parameter value.

– -s: executes the command without displaying the message asking for confirmation from the user. Specify this parameter if you want to skip the confirmation for a shell script or batch file.

Example (Figure 4.10):

>dlnkmgr online -pathid 2 -sKAPL01022-I 1 path(s) were processed. Operation name = onlineKAPL01001-I The DLM command completed successfully. Operation name = online>

Figure 4.10 Path autoPATH_ID 000002 online, No User Confirmation Request


4.1.7 Set Operation

Function:

– Sets the HDLM operating environment

Format:

dlnkmgr set {-lb{on|off}|-ellv log-level|-elfs log-size|-systflv trace-level}|-pchk {on [-intvl execution-interval]|off}}[-s]

Parameters:

– -lb{on|off}: enables or disables the load balancing function.

on: Enabled

off: Disabled

Note: The default is on.

– -ellv log-level: specify the level of error information you want to collect for an error log. The default value is 3 (see Table 4.2).

Table 4.2 Logging Level Values

Value Description

0 Do not collect an error log.

1 Collect error information for the Error or higher level.

2 Collect error information for the Warning or higher level.

3 Collect error information for the Information or higher level (that is, all levels).

– -elfs log-size: specify in Kbytes the size of an error log file. Use a value between 100 and 9900.

Note: The default is 1000.

Note: If the size of the error log file reaches the specified value, HDLM switches to a new file and outputs the data to it. All old files except for the preceding one are deleted.

– systflv trace-level: specify the trace output level (see Table 4.3).

Note: The default is 0.


Table 4.3 Trace Levels Values

Value Description

0 Do not output any trace.

1 Only output error information.

2 Output a summary of program operation.

3 Output details of program operation.

4 Output all information.

Note: Larger trace level values cause a greater number of logs to be output. To accommodate a greater number of logs, data wrapping is applied by HDLM to reduce the time required for deleting old logs.

Note: Use a trace file applicable to all Hitachi products.

Note: The history and results of user-issued commands are output to the trace files regardless of the trace level.

– -pchk {on [-intvl execution-interval]|off}: Enables or disables path health checking.

on: Enabled

off: Disabled. The default is off.

Note: The path health checking function checks paths that are Online as well as Offline(E)

Note: Path health checking does not check the status of paths in the Offline(C) status by executing the offline operation.

– intvl execution-interval: specifies the path health checking execution interval with a parameter immediately following on. When you omit the execution interval specification, path health checking defaults to every 30 minutes.

Specify path health checking intervals in minutes. Use a value between 15 and 1440. The default is 30.

Once this parameter is set, it is stored, and the setting takes effect after the OS or the HDLM manager is restarted.

Once the OS or the HDLM manager is restarted, path health checking is executed when the specified execution interval has occurred.

Note: When you change the execution interval, the new setting takes effect only after path health checking is executed once using the interval specified previously. When you want to change the execution interval immediately, execute the dlnkmgr set -pchk off command to disable path health checking, wait more than five seconds, and then execute the dlnkmgr set -pchk on -intvl execution-interval command. This will change the path health checking execution interval.


Note: In previous versions of the HDLM software, path health checking was performed by executing a batch file that defined the online operation. Currently, path health checking is performed by executing the set operation; do not execute the batch file or two instances of path health checking will run simultaneously.

– -s: Executes the command without no user confirmation message display. Specify this parameter if you want to skip the confirmation for a shell script or batch file.

Table 4.4 shows the defaults of the above settings. If you change the value of the set operation, the new value takes effect immediately.

Table 4.4 Default Settings

Item Default

Load balancing function on: Enabled

Log level 3: Collect error information for Information or higher level (that is, all levels).

Log size 1000 (Kbytes)

Trace level 0: Do not output any trace.

Path health checking function off: Disabled

Example:

>dlnkmgr set -ellv 1dlnkmgr set -ellv 1Execute command? [y/n]: y ... Enter y to execute the command.KAPL01001-I The DLM command completed successfully. Operation name = set>

Figure 4.11 Setting the Log Level with User Command Execution Confirmation


4.1.8 View Operation

Function: Displays HDLM program information and path information.

Format (Figure 4.12 and Figure 4.13):

dlnkmgr view -sys [-sfunc|-msrv|-adrv|-pdrv] [-t ]

Figure 4.12 View Command Displaying Program Information

dlnkmgr view -path [-hdev host-device-name] [-t]

Figure 4.13 View Command Displaying Path Information

Parameters:

– -sys [-sfunc|-msrv|-adrv|-pdrv]: Displays the Dynamic Link Manager program information.

In the subsequent parameter, specify the program for which you want to display information.

Note: If you do not specify the subsequent parameter, the command displays all program information.

Table 4.5 shows the parameters you can specify and the displayed information.

Table 4.5 View Command Parameters and Displayed Information

Parameter Displayed Information

-sfunc Information about the Dynamic Link Manager function settings

-msrv Information about theHDLM manager

-adrv Information about theHDLM alert driver

-pdrv Information about theHDLM driver

– -path

Displays information about the paths that HDLM manages.

In the subsequent parameter, specify the path for which you want to display information. You can also specify the host device that the paths access

Note: If you do not specify the subsequent parameter, the command displays information for all the paths.

Specify the path as follows:

-hdev host-device-name

Specify the host device name. For Solaris™ systems, specify the mount point name.

The command displays information about all the paths accessing the specified host device.

– -t: Does not display the title for each information item.


Examples (Figure 4.14, Figure 4.15, Figure 4.16, Figure 4.17, and Figure 4.18):

>dlnkmgr view -sys -sfuncDynamic Link Manager Version : 03-01Load Balance : onSupport Cluster : offElog Level : 3Elog File Size (kbyte) : 1000Trace Level : 1Path Health Checking : on(30)

KAPL01001-I The DLM command completed successfully. Operation name = view>

Figure 4.14 Displaying HDLM Function Setting Information

Table 4.6 describes the items shown in Figure 4.14.

Table 4.6 HDLM Function Settings Description

Item Description

Dynamic Link Manager Version

HDLM version number consisting of 4 to 6 characters

Load Balance Setting of the load balancing function on: Enabled off: Disabled

Support Cluster Setting of the cluster support function Setting of the cluster support function (see Note 1) on: Enabled off: Disabled Type of the cluster server Veritas Cluster Server™

Elog Level Logging level 0: Do not collect an error log. 1: Collect error information for the Error or higher level. 2: Collect error information for the Warning or higher level. 3: Collect error information for the Information or higher level (that is, all levels).

Elog File Size (kbyte) Size of the error log file in Kbytes Trace Level Trace output level

0: Do not output any trace. 1: Only output error information. 2: Output a summary of program operation. 3: Output details of program operation. 4: Output all information.

Path Health Checking Path health checking function settings:

on: Enabled

off: Disabled

When path health checking is on, the execution interval is displayed in parentheses, in minutes.


Note 1: When you use HDLM for Solaris™ systems in a cluster configuration, off is displayed in the Support Cluster field; however, the cluster support function operates normally.

>dlnkmgr view -sys -msrvDLM Manager Ver WakeupTimeAlive 03-01 2001/04/16 11:37:56KAPL01001-I The DLM command completed successfully. Operation name = view>

Figure 4.15 Displaying HDLM Manager Information


Table 4.7 HDLM Manager Information Description

Item Description

DLM Manager Status of theHDLM manager

Alive: Normal

Dead: Stopped

Ver Version number of theHDLM manager

WakeupTime Startup time of theHDLM manager

>dlnkmgr view -sys -adrvDLM Alert Driver Ver WakeupTime Elog Mem SizeAlive 03-01 2001/04/16 11:28:34 128KAPL01001-I The DLM command completed successfully. Operation name = view

Figure 4.16 Displaying HDLM Alert Driver Information


Table 4.8 HDLM Alert Driver Information Description

Item Description

DLM Alert Driver Status of theHDLM alert driver

Alive: Normal

Dead: Stopped

Ver Version number of theHDLM alert driver

WakeupTime Startup time of theHDLM alert driver

Elog Mem Size Size of error log memory for theHDLM alert driver


>dlnkmgr view -sys -pdrvDLM Driver Ver WakeupTimeAlive 03-01 2001/04/16 11:28:34KAPL01001-I The DLM command completed successfully. Operation name = view>

Figure 4.17 Displaying HDLM Driver Information


Table 4.9 HDLM Driver Information Description

Item Description

DLM Driver Status of theHDLM driver

Alive: Normal

Dead: Stopped Ver Version number of theHDLM driver WakeupTime Startup time of theHDLM driver

>dlnkmgr view –path -hdev /mntptPaths:00002 OnlinePaths:00002PathState IO-Counts IO-ErrorsOnline 1332 0

PathID PathName DskName iLUDkcPort State Type IO-Counts IO-Errors DNum HDevName000011 004.0004.00029.0002 HITACHI.DF400 .1234 00101B Online Own 1332 0 1 /mntpt000005 003.0004.00027.0002 HITACHI.DF400 .1234 00100B Online Non 0 0 1 /mntpt

KAPL01001-I The DLM command completed successfully. Operation name = view>

Figure 4.18 Displaying Host Device Path Information (host device name = /mntpt)


Table 4.10 describes the information contained in Figure 4.18.

Table 4.10 Host Device Path Information Description

Item Description

Paths Sum of the number of displayed paths, indicated by up to five decimal numbers

OnlinePaths Number of available paths in the displayed paths, indicated by up to five decimal numbers

PathState Status of the displayed paths

Online: All paths are available.

Shrunken: Some of the paths are available.

Offline: No paths are available.

IO-Counts Total I/O count for the displayed paths, indicated by up to ten decimal numbers

IO-Errors Total I/O error count for the displayed paths, indicated by up to ten decimal numbers

PathID AutoPATH_ID indicated by up to six decimal numbers

PathName Path name indicated by a string of up to 19 one-byte characters. A path name consists of the port number for the host bus adapter, bus number, target ID, and host LU number, each of which is separated by a period.

DskName Storage subsystem name indicated by a string of up to 38 one-byte characters. A storage subsystem name consists of the vendor ID, product ID, and serial number, each of which is separated by a period.

iLU LU number of the storage subsystem, indicated by a string of up to four one-byte characters

DkcPort Port number of the disk controller, indicated by a string of two one-byte characters.

State (see Note 1) Status of the path

Online: Online

Offline(C): Offline by a command

Offline(E): Offline due to an error

Type Attribute of the path

Own: Owner path

Non: Non-owner path

IO-Counts Total I/O count for the path, indicated by up to ten decimal numbers

IO-Errors Total I/O error count for the path, indicated by up to ten decimal numbers

DNum Device number, indicated by up to three decimal numbers.

HDevName Host device name.

In Solaris™ systems, the mount point is displayed in this field. When the file system is not mounted, a hyphen (-) is displayed.

Note 1: A path that has the same PathName as a path whose state is offline(E) may be in an error status even though its state is online.


Chapter 5 The HDLM DLMgetras Utility

This chapter describes the DLMgetras utility that HDLM uses to collect error information.

5.1 Overview

HDLM provides a utility called DLMgetras for collecting error information. The user must have root permission to execute DLMgetras.

Note: DLMgetras is used in UNIX®-based systems only.

5.2 HDLM Details

5.2.1 DLMgetras Format

DLMgetras {directory-for-the-output-destination-of-collected-information [-f file-for-defining-the-information-to-be-collected]|-h}

Figure 5.1 DLMgetras Format

5.2.2 DLMgetras Function

– Collects information, such as trace files, definition files, core files and libraries, required for analyzing errors that occur in HDLM.

– Specify desired files by using the file for defining the information to be collected.

– For details about the information collected by DLMgetras for collecting error information when you do not use the file for defining information, see Table 5.1.

Note: DLMgetras is used in UNIX®-based systems only.

50 Chapter 5 The HDLM DLMgetras Utility

5.2.3 Parameters

– directory-for-the-output-destination-of-collected-information

Specify the output directory.

The directories to be output are created in the specified directory, and error information is collected in the created directories.

– -f file-for-defining-the-information-to-be-collected

Specify this parameter when you want to specify the directories or the files to be collected.

Specify the directories or the files in the file for defining the information to be collected, and then specify this parameter.

Use an absolute path to specify the file for defining the information to be collected (Figure 5.2).

Figure 5.2 Defining Information to be Collected

Coding rules for -f file-for-defining-the-information-to-be-collected

– Use absolute paths to specify the directories or files.

– If you specify the directories or the files in relative paths, the directory where DLMgetras was executed is searched, and the directories and files that are found there are collected.

– Make sure that the collected information directory is separate from the output destination directory, otherwise an endless loop will result and DLMgetras will never complete.

– If there is a pound sign (#) at the beginning of a line, the line is considered to be a comment.

– If there is a pound sign (#) within a line of code, it is considered to be part of a file path.

– Specify only one file or one directory in one line of code.

– Do not specify the root directory (/).

– If you specify a directory, all files in the specified directory are collected. The files in the specified directory’s subdirectories are also collected.

Note: If the specified directory contains no files, nothing will be collected. The specified directory will not be created in the output destination directory.

– -h

Displays DLMgetras format.


5.2.4 Important Notes

A large amount of data is stored in core files and OS crash files; therefore, sufficient space must be allocated in the directory designated for collecting error information.

If the specified output destination directory already exists, a message confirming that directories and files have been overwritten is displayed. When y is entered, the file will be overwritten. When n or any other character is entered, DLMgetras is terminated without being executed.

Table 5.1 List of Error Information to be Collected by DLMgetras Utility

Directory File Description

/opt/DynamicLinkManager/log dlmmgr1.log HDLM manager log file (driver logs are included)

dlmmgr2.log

/opt/hitachi/HNTRLib/mmap hntrhost-name.mm Memory mapped file

/opt/hitachi/HNTRLib/spool hntr{1|2|...|16}.log Note1 Trace files

/kernel/drv sd.conf sd (SCSI driver) configuration file

dlmfdrv.conf HDLM drivers configuration file

dlmadrv.conf HDLM alert driver configuration file

fca-pci.conf, fcaw.conf, or lpfc.conf HBA configuration file (file name depends on the installed HBA driver)

/etc coreadm.conf Core file configuration definition file

dumpadm.conf OS crash dump configuration definition file

syslog.conf Defines the syslog output destination directory

system Kernel batch file

vfstab File system automatic mount at startup information file

mnttab File system mount information

/etc/dfs fstypes Sets the default system type (NFS) and other file system types

dfstab Sets system boot command execution

52 Chapter 5 The HDLM DLMgetras Utility

Table 5.1 List of Error Information to be Collected by DLMgetras Utility (Continued)

Directory File Description

/OS-crash-file-directory OS-crash-file-name Collects all files in the DUMPADM_SAVDIR parameter specified directory.

/OS-crash-file-directory OS-crash-file-name Collects all files in the DUMPADM_SAVDIR parameter specified directory.

/directory-for-the-output-destination-of-syslog syslog-name The file path depends on the settings in the /etc/syslog.conf file

/getrasinfo — Directory for collecting the command execution results

dev_dsk.txt List of disks that are treated as block devices

dev_rdsk.txt List of disks that are treated as raw devices

devices.txt Device special file entities

df-k.txt Mount information

pagesize.txt Memory page size

uname-a.txt OS version

isainfo-b.txt OS type (32 bit or 64 bit)

ulimit-a.txt System resources limit (data segment, stack segment and file descriptor) available

pkginfo.txt List of installed packages

showrev-p.txt List of installed patches

prtconfMemory.txt Physical memory size

psrinfo-v.txt CPU information

sysdef.txt Kernel parameter value

swap-l.txt Swap area information

swap-s.txt Swap usage

modinfo.txt Loaded drivers information

dmesg.txt System diagnosis message

dlmmgr-path.txt HDLM path information

dlmmgr-sys.txt HDLM system information

Note1: Actual file names are hntr1.log to hntr16.log.


Appendix A Messages and Alerts

This appendix describes HDLM operational messages and associated required actions.

HDLM issues the following message types:

HDLM command messages

HDLM API messages

HDLM manager messages

HDLM driver (filter component) messages

HDLM alert driver messages

HDLM driver (core logic component) messages

HDLM management target messages

HDLM installation program messages

54 Appendix A Messages and Alerts

Each message has a unique message ID. Table A.1 contains the message ID format and descriptions.

Table A.1 Message Format and Descriptions

Format Meaning

KAPL Indicates that the message is a Dynamic Link Manager message.

mm Number of the Dynamic Link Manager module that issued the message.

01: DLM command

03: DLM API

04: DLM manager

05: DLM driver (filter component)

06: DLM alert driver

07: DLM driver (core logic component)

08: DLM management target

09: DLM installation program

nnn Message serial number for the module

l Message level

C: Critical

E: Error

W: Warning

I: Information

Table A.2 contains message terminology and definitions.

Table A.2 Message Terminology and Definitions

Terminology Meaning

%d Decimal number

%s Character string

%x Hexadecimal number

CS Cluster support

FO Failover

LB Load balancing

Operation name Type of the operation that is entered after dlnkmgr in the command.

Service status Running status of the service

Mounted drive A drive that the file system recognizes


Table A.3 contains message numbers, message descriptions, and actions to take, if appropriate.

Table A.3 Messages and Actions

Message Number

Message Action

KAPL01003-W No operation name is specified. Specify the operation name, and then retry.

KAPL01004-W The operation name is invalid. Operation name = %s Execute DLM help operation to check the operation name; retry.

KAPL01005-W A parameter is invalid. Operation name = %s, parameter = %s

Execute DLM help operation to check the parameter; retry.

KAPL01006-W A necessary parameter is not specified. Operation name = %s

Execute DLM help operation to check the parameter. Specify the correct parameter, and then retry.

KAPL01007-W A duplicate parameter is specified. Operation name = %s, parameter = %s

Delete the duplicate parameter, and then retry.

KAPL01008-W A necessary parameter value is not specified. Operation name = %s, parameter = %s

Specify the parameter value, and then retry.

KAPL01009-W A parameter value is invalid. Operation name = %s, parameter = %s, parameter value = %s

Specify the correct value for the parameter, and then retry.

KAPL01011-E An invalid interrupt was received during processing of the DLM command. Operation name = %s

Check whether you executed the interrupt or not.

KAPL01012-E Could not connect the DLM manager. Operation name = %s

Execute the view operation of the DLM command to check whether the DLM manager has started. Start the DLM manager if it has not previously started, and then retry the DLM command.

KAPL01013-E An error occurred in internal processing of the DLM command. Operation name = %s details = %s

Collect the error information (DLM command log), and then contact maintenance personnel.

KAPL01014-W No authority to execute the DLM command. Operation name = %s

Execute the command as a user with root permission..

KAPL01015-W The target HBA was not found. Operation name = %s Use the DLM command view operation to check the specification, and then retry.

KAPL01016-W The target DKC was not found. Operation name = %s Use the DLM command view operation to check the specification, and then retry.

KAPL01017-W The target LU was not found. Operation name = %s Use the DLM command view operation to check the specification, and then retry.

KAPL01018-W The target device was not found. Operation name = %s Use the DLM command view operation to check the specification, and then retry.

KAPL01019-W The target path was not found. Operation name = %s Use the DLM command view operation to check the specification, and then retry.

KAPL01021-E Cannot execute the DLM command due to insufficient memory.

Terminate unnecessary applications to increase the amount of free memory, or restart.

KAPL01023-W The last online path for the device cannot be placed offline.

Use the DLM command view operation to check the status of the path.

KAPL01024-W Cannot specify the parameters of the DLM command at the same time. Operation name = %s, parameter = %s

Execute "help operation-name" of the DLM command to check the parameter that can be specified, and then retry.


Message Number

Message Action

KAPL01025-W Range of dates is invalid. Specify the correct value in the parameter, and then retry.

KAPL01026-E A registry access error occurred. Operation name = %s The contents of the managed registry may be damaged. Restart. If the error occurs again after restart, terminate and then uninstall DLM, then reinstall it.

KAPL01027-E Cannot collect log information. Operation name = %s Check disk free space. If the disk has sufficient free space, check whether you have write permission for the log file directory and registry. Also check whether the log file is set to read-only mode.

KAPL01028-E An unexpected error occurred. Processing is canceled. Operation name = %s


KAPL01029-E A fatal error occurred. Details = Hcc, %s HccCoOutOfMemoryException: A memory shortage coccured. Terminate unnecessary application to increase the amount of free memory, or reset the machine.

Other indication: An internal conflict occurred. Collect the error information (HDLM command log),and then contact maintenance personnel.

KAPL01030-E A fatal error occurred. Details = Ansi, %s Collect the error information (DLM command log), and then contact maintenance personnel.

KAPL01031-E A %s message was received. Collect the error information (DLM command log), and then contact maintenance personnel.

KAPL01032-E A fatal error occurred. Details = Unexpected exception, %s


KAPL01036-E The offline path cannot be placed online. PathID=%d Remove the error in the path, and then retry.

KAPL01037-W Too many parameters are specified. Operation name = %s, parameters = %s

Execute help operation-name of the DLM command to check the parameter and retry.

KAPL04002-E Could not start the DLM manager. Check for any other errors.

KAPL04003-E The startup parameter is invalid. Check the specification of the startup parameter.

KAPL04005-E Cannot connect the service control manager. See section 3.2.2 and section 3.2.3 on starting and stopping the HDLM manager.

KAPL04006-E Cannot register the service control handler function. Return value=%d

Contact maintenance personnel.

KAPL04007-E Cannot register the service status. Return value=%d Contact maintenance personnel.

KAPL04008-E Cannot open the option definition file (%s). Check to see if another program is using the file (or has opened the file with Notepad), or if the file has been deleted inadvertently.

KAPL04009-E The option definition is invalid. If you edited the option definition file, check the contents of the file. If you did not, check the file for damage.

After checking the file for damage, restart the DLM manager. If the same error occurs again, reinstall DLM.


Message Number

Message Action

KAPL04010-E Could not open the error log file. Check to see if another program is using the file (or has opened the file with Notepad), or whether the file has been deleted inadvertently.

KAPL04011-E Could not output the error log file. Check that the disk has sufficient free space.

KAPL04012-E Could not create a communication pipe. RC=%d Contact maintenance personnel.

KAPL04013-E Input is impossible via the communication pipe. RC=%d Contact maintenance personnel.

KAPL04014-E Output is impossible via the communication pipe. RC=%d

Contact maintenance personnel.

KAPL04016-E The option is invalid. Specify the correct option.

KAPL04017-E Output of the option definition file was impossible. Check that the disk has sufficient free space.

KAPL04018-E Could not close the option definition file. Check that the disk has sufficient free space.

KAPL04019-E Could not collect the error information. RC=%d Check that the DLM driver (alert component) is running.

KAPL04022-W DLM manager warning information - %s Analyze the contents of the warning.

KAPL04023-E DLM manager error information - %s Analyze the error information.

KAPL04024-C A critical error occurred in the DLM manager. (%s) Examine the error for the cause.

KAPL04025-C A memory shortage occurred in the DLM manager. Increase the amount of memory available for the process.

KAPL05003-I The DLM driver (filter component) is successfully attached to Disk (%d), Partition (%d).

None.

KAPL05004-I Initialization of the filtering function (%x) for the DLM driver (filter component) was successful.

None.

KAPL05005-I Initialization of the control function (%x) for the DLM driver (filter component) was successful.

None.

KAPL05006-I Connection with the DLM alert driver was successful. None.

KAPL05007-E Could not connect the DLM alert driver. (%x:%x) Check to see if the DLM alert driver has started. If it has stopped, restart the machine.

If this message frequently appears when the DLM alert driver has started, contact maintenance personnel.

KAPL05008-E Could not allocate memory. (%x:%x) Check to see if the DLM driver has started normally. If it has not started or contains an error, contact maintenance personnel and report the error and detail code.

KAPL05009-E Could not start the thread (%x). (%x:%x) Check to see if the DLM driver has started normally. If it has not started or contains an error, contact maintenance personnel and report the error and detail code.

KAPL05010-E Could not initialize the DLM driver (filter component). (%x:%x)

Check to see if the DLM driver has started normally. If it has not started or contains an error, contact maintenance personnel and report the error and detail code.


Message Number

Message Action

KAPL05011-E Could not attach the DLM driver (filter component) to Disk (%d), Partition (%d). (%x:%x)

Check to see if the DLM driver has started normally. If it has not started or contains an error, contact maintenance personnel and report the error and detail code.

KAPL05012-I The device (%x) for Disk (%d), Partition (%d) is selected for a mounted drive.

None.

KAPL05013-I The device (%x) for Disk (%d), Partition (%d) is removed from the mounted drives.

This is normal operation. If the target drive cannot be referenced, check the disk configuration.

KAPL05014-I The device object (%x) is registered as the path (%x). None.

KAPL05018-W The FO processing in the path (%x) failed. (%x:%x) The I/O being processed is discarded. Check the status of the path and take an appropriate action.

KAPL05019-I The FO processing in the path (%x) finished. The I/O request is processed in the path (%x).

None.

KAPL05022-I An invalid IOCTL (%x) was received. The processing is canceled.

None.

KAPL05023-E Could not process the IOCTL (%x). (%x:%x) Check the message of the DLM command or DLM manager. If this message frequently appears, contact maintenance personnel and report the error and detail code.

KAPL05024-E Could not output a log to the DLM alert driver. (%x:%x) Check whether the DLM alert driver has started.

If this message frequently appears when the DLM alert driver has started, contact maintenance personnel.

KAPL05026-E An error occurred when the DLM driver (filter component) terminated. (%x:%x)

Check that the DLM driver completed normally. If you find any problems, contact maintenance personnel and report the error and detail code.

KAPL05027-I The DLM driver (filter component) (%x) received an UNLOAD request. The request was canceled.

None. You cannot stop the DLM driver.

KAPL05028-C Invalid processing (%x) was detected. The DLM driver (filter component) will now terminate abnormally. (%x:%x)

Since an unrecoverable error was detected, the DLM driver terminated. Contact maintenance personnel and report the error and detail code.

KAPL05029-I The MajorFunction (%x) that the DLM driver (filter component) does not handle was received. The request was transferred to the disk class driver.

None.

KAPL05030-W An unsupported MajorFunction (%x) was requested. The request was canceled.

None. If this message frequently appears, check whether an invalid program is running.

KAPL05031-W Disk(%d) is not a target disk system for DLM.(%x,%x) If this message is displayed for a disk that is not supported by HDML, there is no problem.

If this message is displayed for a disk that is supported by HDML, contact maintenance personnel.

KAPL05032-I The path health checking for the path (%x) completed normally. (%d,%x)

None.

KAPL05033-W The path health checking for the path (%x) failed. (%d,%x,%x)

Check the path for which path health checking failed. If this message is displayed for an unexpected path, contact maintenance personnel.


Message Number

Message Action

KAPL05034-I Disk(%d) is a target disk system for DLM. (%x,%x) None.

KAPL05035-I The DLM driver (filter component (%x)) is successfully attached to the device object (%d).

None.

KAPL05036-E Failed to attach the DLM driver (filter component (%x)) to the device object (%d).

Check whether the DLM driver has started normally. If it has not started or contains an error, contact maintenance personnel and report the error and detail code.

KAPL06003-I Initialization of the DLM alert driver (%x) was successful.

None.

KAPL06004-E Could not allocate memory. (%x:%x) Check to see if the DLM driver has started normally. If it has not started or contains an error, contact maintenance personnel and report the error and detail code.

KAPL06005-E Could not initialize the DLM alert driver. (%x:%x) Check whether the DLM driver has started normally. If it has not started or contains an error, contact maintenance personnel and report the error and detail code.

KAPL06006-E Could not start the thread (%x). (%x:%x) Check whether the DLM driver has started normally. If it has not started or contains an error, contact maintenance personnel and report the error and detail code.

KAPL06009-I Invalid IOCTL (%x) was received. The processing is canceled.

None.

KAPL06010-E Could not process the IOCTL (%x). (%x:%x) Check the message of the DLM command or DLM manager. If this message frequently appears, contact maintenance personnel and report the error and detail code.

KAPL06011-W Old log information was discarded because the log buffer did not have enough free space. (%x:%x)

Check that the DLM manager is running. If it is not, start the DLM manager.

KAPL06012-W Old emergency information was discarded because the emergency information buffer did not have enough free space. (%x:%x)

Check that the DLM manager is running. If it is not, start the DLM manager.

KAPL06013-E Could not write log information into the log buffer. (%x:%x)

Check whether any other error occurred. The log information that could not be written is discarded.

KAPL06014-E Could not write emergency information into the emergency information buffer. (%x:%x)

Check whether any other error occurred. The log information that could not be written is discarded.

KAPL06015-W The contents of the log buffer are discarded. The DLM manager could not correctly save the log information in the file during termination. Check whether any other error occurred.

KAPL06016-W The contents of the emergency information buffer are discarded.

The DLM manager could not correctly save the log information in the file during termination. Check whether any other error occurred.

KAPL06018-W An unsupported MajorFunction (%x) was requested. The request was canceled.

None. If this message frequently appears, check for an invalid program running.

KAPL06019-E An error occurred during termination of the DLM alert driver. (%x:%x)

Check that the DLM driver completed normally. If you find any problem, contact maintenance personnel and report the error and detail code.


Message Number

Message Action

KAPL06020-I The DLM alert driver (%x) received an UNLOAD request. The request was canceled.

None. You cannot stop the DLM alert driver.

KAPL06021-C Invalid processing (%x) was detected. The DLM alert driver will now terminate abnormally. (%x:%x)

Since an unrecoverable error was detected, the DLM alert driver terminated. Contact maintenance personnel and report the error and detail code.

KAPL07000-C An internal conflict occurred in the DLM driver (core logic component). Stage%d

Restart the system.

KAPL07002-C Could not enlarge the memory area for the DLM driver. Restart the system.


Restart the system.

KAPL07054-E Could not create an DLM driver table. Stage%d Restart the system.


Restart the system.


Restart the system.

KAPL07151-I The error path was recovered successfully. None.

KAPL07152-I The error path and offline path were recovered successfully.

None.

KAPL07153-W The request was ignored because access to the path at the media level was impossible.

None.

KAPL07154-W Could not recover the error path. Check the specified path again. If the specification is correct, you need to investigate further.

KAPL07155-W Could not recover the error path and offline path. Check the specified paths again. If the specification is correct, you need to investigate further.

KAPL07157-W Could not recover some of the paths related to the specified device.

Check the specified paths again. If the specification is correct, you need to investigate further.

KAPL07158-W Could not recover the paths related to the specified device.

Check the specified paths again. If the specification is correct, you need to investigate further.


Restart the system.

KAPL07201-W The configuration does not contain a standby path. Check the configuration.

KAPL07203-W A nonexistent path is specified for the main path. None.

KAPL07204-W Although an owner path exists, a non-owner path is selected for the main path.

Check the specification.

KAPL07208-E There is no standby path. ID%d Check the specification.


Restart the system.

KAPL07251-W The configuration is not applicable to LB. Check the configuration.

KAPL07254-W A path that cannot be a target of LB is specified. ID%d Check the specification.

KAPL07255-W An attempt was made to remove the last LB target from the LB target path. ID%d



Message Number

Message Action

KAPL07258-E There is no path-switching destination. ID%d Check the specification.


Restart the system.

KAPL07304-E An error in the standby path cancels the CS function forcibly.

Check the cause of the error.

KAPL07307-E The CS function could not retry. Check the cause of the error.


Restart the system.

KAPL07355-W An attempt to place the last path offline was rejected. ID%d


KAPL07357-C Could not place the path offline. ID%d Check the specified path again. If the specification is correct, investigate further.

KAPL07360-C Could not release the offline path. ID%d Check the specified path again. If the specification is correct, investigate further.

KAPL07372-C Could not place all the paths offline. Check the specified path again. If the specification is correct, investigate further.

KAPL07374-C Could not make some of the paths related to the specified device offline.

Check the specified path again. If the specification is correct, investigate further.


Restart the system.

KAPL07404-I The processor reduction for defusing an error is enabled.

None.

KAPL07405-I A request was made to enable the processor reduction for defusing an error when it was already enabled.

None.

KAPL07406-I A request was made to disable the processor reduction for defusing an error when it was already disabled.

None.

KAPL07407-I The processor reduction for defusing an error is disabled.

None.

KAPL07442-W The path is not the target of management for the specified LU/device. ID%d, ID%d


KAPL07443-W An error path was specified. ID%d, ID%d Check the specification.

KAPL07453-W The target of the CS function is not a single LU containing a single device. ID%d, ID%d



Restart the system.

KAPL07551-W Recovery instruction was made in response to the error report.

None.

KAPL07552-W Recovery instruction was made in response to an unknown error report.

Investigate the cause of the error.

KAPL08019-E The path (%x) detected an error (%x). (%s) Check the path that detected the error.

KAPL08020-E I/O processing in the path (%x) terminated with error (%x). (%s)

Check the path that detected the error.


Message Number

Message Action

KAPL08021-E I/O processing in the path (%x) in Disk (%d), Partition (%d) failed due to an error (%x). Failover is performed.

The failover function has no effect if there is only one online path in the path class. Check the error in the path and take an appropriate action.

KAPL08022-E A path error occurred. ErrorCode=%d, PathID=%d, PathName=%d.%d.%d.%d, DNum=%d, HDevName=%s

The hardware targeted to be controlled may have a problem. For details on the action to be taken, see section 3.4.1.

KAPL08023-E A path was recovered. PathID=%d, PathName=%d.%d.%d.%d, DNum=%d, HDevName=%s

None.

KAPL09001-E There is no system management permission. Execute the command as a user with root permission..

KAPL09002-E The disk does not have sufficient free space. Change the installation destination or delete unnecessary files to increase the amount of free space; retry.

KAPL09003-E Cannot install in this system. Install HDLM in an AIX® or Solaris® SPARC® system.

KAPL09005-E Could not stop the DLM manager. Stop the DLM manager manually. Then, re-execute the installation program or the uninstallation program.

KAPL09006-E Could not install Dynamic Link Manager. If installation was interrupted, incomplete files and directories may remain. Delete such files and directories.

KAPL09008-W The license code is invalid. Check the license code, and then re-enter it.

KAPL09009-E The license code is invalid. The DLM installation program will now terminate.

Check the license code, and then re-execute the installation program.

KAPL10001-W No parameter is specified. Check the parameters for the error-information collection utility and then retry.

KAPL10002-W There are too many parameters. Check the parameters for the error-information collection utility and then retry.

KAPL10003-W Something other than a directory name has been specified in the first parameter. value = %s

Check the parameters for the error-information collection utility and then retry.

KAPL10004-W The parameter has an incorrect value. value = %s Check the parameters for the error-information collection utility and then retry.

KAPL10005-W There is an insufficient number of parameters. Check the parameters for the error-information collection utility and then retry.

KAPL10006-W The file name for collection information definition does not exist or cannot be read. value = %s

Check whether the indicated collection-information definition file exists. Alternatively, check for access permission or the like.

KAPL10007-W A directory name has been specified in the third parameter. value = %s

Check the parameters for the error-information collection utility and then retry.

KAPL10008-W The user does not have write permission for the specified directory. value = %s

Check the access permission for the specified directory. Also, check whether the specified directory name is correct.

KAPL10009-W The specified directory name already exists. Do you want to overwrite? [y/n]:

The specified directory already exists. Enter y to overwrite. Enter n or any other key to terminate the error-information collection utility without executing it.


Message Number

Message Action

KAPL10010-W A root directory has been specified. line = %d Delete the coding of the root directory from the specified file. The displayed directory will be ignored and the error-information collection utility will continue.

KAPL10011-W More than one file or directory name has been specified on one line. line = %d, value = %s

After the error-information collection utility terminates, check the contents of the collection-information definition file shown in the message. If the contents are incorrect, correct them and then re-obtain the error information. The displayed file or directory will be ignored and the error-information collection utility will continue. This message is output up to five times and then omitted.

KAPL10012-W The specified file name or directory name does not exist. line = %d, value = %s

After the error-information collection utility terminates, check the contents of the collection-information definition file shown in the message. If the contents are incorrect, correct them and then re-obtain the error information. The displayed file or directory will be ignored and the error-information collection utility will continue.

KAPL10013-W The user does not have read permission for the specified file. line = %d, value = %s

After the error-information collection utility terminates, check the contents of the collection-information definition file shown in the message. If the contents are incorrect, correct them and then re-obtain the error information. The displayed file will be ignored and the error-information collection utility will continue.

KAPL10014-W The user does not have read permission for the specified directory. line = %d, value = %s

After the error-information collection utility terminates, check the contents of the collection-information definition file shown in the message. If the contents are incorrect, correct them and then re-obtain the error information. The displayed directory will be ignored and the error-information collection utility will continue.

KAPL10015-W The file format is incorrect. value = %s After the error-information collection utility terminates, check whether the collection-information definition file shown in the message is a text file.

KAPL10020-I The file has been obtained successfully. file = %s None

KAPL10021-I Processing terminated halfway because a signal was received.

The error-information collection utility will terminate halfway. If the directory is unnecessary, delete it including the subordinate files.


Acronyms and Abbreviations

ASCII American National Standard Code for Information Interchange

BL block length

CKD count key data CR carriage return CVS custom volume size

D delimiter DAT digital audio tape DO dataset organization DS dataset size

EA EBCDIC/ASCII (includes EBCDIC-to-ASCII and ASCII-to-EBCDIC) EBCDIC extended binary-coded decimal interchange code Emp empty file option EOF end of file

FC fibre channel FCU File Conversion Utility FD floppy disk FWD fast-wide differential

GUI graphical user interface

ICKDSF A Device Support Facilities (DSF) command used to perform media maintenance

kB kilobytes

LDEV logical device LF line feed LSM Logical Storage Manager LU logical unit LUN logical unit number LVI Logical volume image

MF mainframe mto mainframe-to-open

OPEN-x standard LU type, e.g., OPEN-3, OPEN-9 OS operating system otm open-to-mainframe oto open-to-open

R0 record 0 RDW record description word RF record format RL record length

66 Acronyms and Abbreviations

SCSI small computer system interface

volser volume serial number VSN volume serial number VTOC volume table of contents


Index

A actions taken for a path error, 37 actions taken for a program error, 38

B bus number, 34

C contacting maintenance personnel, 39 core logic component, 26

D DkcPort, 35 DLM alert driver, 26 DLM command, 26 DLM driver, 26 DLM manager, 26 DNum, 35

H HDevName, 35

I identifying the error section and taking

corrective action for the hardware, 38 iLU, 34

L Logical Unit Id, 34 LUN, 34

M monitoring the message, 39

N narrowing down the hardware that may have

the error, 38

O obtaining program information, 39 obtaining the path information, 37 operations, 42 operations of the HDLM command, 42

P path health checking, 36 port number of the host bus adapter, 34 product ID, 34

R

S SCSI Bus number, 34 SCSI Port number, 34 State, 35

T taking the action for the error, 39 target Id, 34

V vendor ID, 34

68 Index

Hitachi Dynamic Link Manager for Solaris

Documents

Transcript of Hitachi Dynamic Link Manager for Solaris