Hitachi Storage Command Suite Hitachi Device Manager Software Agent Installation Guide

Transcription

1 Hitachi Storage Command Suite Hitachi Device Manager Software Agent Installation Guide FASTFIND LINKS Document Organization Software Version Getting Help Contents MK-92HC019-18

2 Copyright 2008 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 (hereinafter referred to as "Hitachi Data Systems"). 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. 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, the Hitachi logo, and Hitachi Data Systems are registered trademarks and service marks of Hitachi, Ltd. The Hitachi Data Systems logo is a trademark of Hitachi, Ltd. IBM, AIX, MVS, OS/390, RACF, z/os, zseries are trademarks of International Business Machines Corporation in the United States, other countries, or both. 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. ii

3 Contents Preface...vii Intended Audience... viii Software Version... viii Release Notes...ix Document Revision Level...ix Document Organization...x Referenced Documents...xi Document Conventions... xii Convention for Storage Capacity Values... xiii Getting Help... xiii Comments... xiii Overview About the Device Manager Agent Reviewing the Host Requirements for the Device Manager Agent Supported Operating Systems Supported Operating Systems for Use on IPv4 Environments Supported Operating Systems for Use on IPv6 Environments Applicable Patches for Operating Systems Precautions for Using Provisioning Manager Applicable Java Programs Supported File Systems Supported Volume Managers Supported Path Management Software Supported Cluster Software Supported SAN Environments Supported Storage Subsystems Supported Host Bus Adapter Models Supported iscsi Connection Configurations Preface iii

4 Installing the Device Manager Agent Installing the Device Manager Agent in Windows Before Installing in Windows Performing a New Installation in Windows Performing an Upgrade Installation in Windows Performing a Restoration Installation in Windows Installing the Device Manager Agent in UNIX Before Installing in UNIX Before Installing in Solaris Before Installing in AIX Before Installing in Linux Before Installing in HP-UX Performing an Installation in UNIX Performing a Silent Installation of the Device Manager Agent Uninstalling the Device Manager Agent Uninstalling the Device Manager Agent in Windows Uninstalling in Windows Deleting Tasks that Execute the HiScan Command Uninstalling the Device Manager Agent in UNIX Operating the Device Manager Agent Before Operating the Device Manager Agent Operations that Require Restarting the Device Manager Agent Service Notes When a Host Has Multiple Network Adapters Notes When Changing the Storage Subsystem Configuration Notes When an Invalid Path Exists Notes on Using Device Manager to Monitor Copy Pairs Notes When the Host OS is Windows Notes for the Windows Server 2003 or Windows Server 2008 Host OS Notes on Allocating a Drive for The Device Notes on Using VMware ESX Server Notes When a Firewall is Being Enabled Notes on Changing the User of the Device Manager Agent Service Notes When the Host OS is Solaris Notes for When VxVM is Being Used Notes on Managing LU Partitions Without Labels Notes When the Host OS is AIX Notes on Operating in Cluster Environments Notes on Changing the SED Mode To all Notes on Upgrading to AIX 5.2 or later Notes When the Host OS is Linux Notes on using the Hitachi Storage Command Suite products Setting up the Device Manager Agent iv Preface

5 Setting Device Manager Server Information Setting the Cycle of Reporting Host Information to the Device Manager Server Specifying Settings for Managing Copy Pairs Specifying Settings When a Host Manages 100 or More LUs Setting Values When a Volume Manager is Not Used Setting Values When a Volume Manager is Used Operating the Device Manager Agent Managing the Operating Status of the Device Manager Agent Service Reporting Host Information to the Device Manager Server Checking the Version of the Device Manager Agent Using a User-created Configuration Definition File Before Using a User-created Configuration Definition File in Device Manager Reporting Configuration Definition File Data to the Device Manager Server Using Device Manager with CCI Notes When You Delete Copy Pairs Notes on Optimization Processing of the Configuration Definition File Instance Number and Service Number of CCI Used by Device Manager Using Device Manager Agent Commands hbsasrv Command Syntax hdvm_info Command Syntax hdvmagt_account Command Syntax hdvmagt_schedule Command Syntax hdvmagt_setting Command Syntax HiScan Command Syntax hldutil Command Syntax TIC Command Syntax Working with Agent Property Files The agent.properties File The hldutil.properties File The logger.properties File The programproductinfo.properties File The server.properties File Troubleshooting Troubleshooting Calling the Hitachi Data Systems Support Center Preface v

6 Contents of a Configuration Definition File Supported by Device Manager. A-1 Restrictions Common to All Parameters... A-6 Restrictions for the HORCM_MON Parameter... A-6 Restrictions for the HORCM_CMD Parameter... A-7 Restrictions for the HORCM_DEV Parameter... A-8 Restrictions for the HORCM_LDEV Parameter... A-9 Restrictions for the HORCM_INST Parameter... A-10 Acronyms and Abbreviations Index vi Preface

7 Preface This document describes how to install and work with the Device Manager agent. This preface includes the following information: Intended Audience Software Version Release Notes Document Revision Level Document Organization Referenced Documents Document Conventions Convention for Storage Capacity Values Getting Help Comments Notice: The use of Hitachi Device Manager software and all other Hitachi Data Systems products is governed by the terms of your agreement(s) with Hitachi Data Systems. Preface vii

8 Intended Audience This guide describes how to install the Device Manager agent software for Hitachi Device Manager software. We assume that our audience has: a background in data processing and understands peripheral storage device subsystems and their basic functions, read and understands the user guide(s) for the applicable Hitachi storage subsystem(s); for example, Hitachi Lightning 9900 V Series User and Reference Guide (MK-92RD100), Hitachi Thunder 9500 V Series User and Reference Guide (MK-92DF601), familiarity with the host operating system (e.g., the HP-UX OS) on which the agent is installed, and has knowledge of Storage Area Networks (SANs). Note: The term "Universal Storage Platform (USP)" refers to the entire Hitachi USP subsystem family, unless otherwise noted. The term "9900V" refers to the entire Hitachi Lightning 9900 V Series subsystem family, unless otherwise noted. The term "9900" refers to the entire Hitachi Lightning 9900 subsystem family, unless otherwise noted. Please refer to the Hitachi Lightning 9900 User and Reference Guide (MK-90RD008) for further information on the 9900 disk array subsystems. The term "9500" refers to the entire Hitachi Thunder 9500 V Series subsystem family, unless otherwise noted. Please refer to the Hitachi Thunder 9500 V Series User and Reference Guide (MK-92RD100) for further information on the 9500V disk array subsystem. The term "9200" refers to the entire Hitachi Thunder 9200 subsystem family, unless otherwise noted. Please refer to the Hitachi Thunder 9200 User and Reference Guide (MK-90DF504) for further information on the 9200 disk array subsystem. Third-party agents are available for other servers. For the latest information about these agents, please contact your Hitachi Data System representative or refer to documentation about a specific agent. Software Version This document revision applies to Hitachi Device Manager software version 6.0 and higher. viii Preface

9 Release Notes Release notes can be found on the documentation CD or on the Hitachi Data Systems Support Portal: Release notes contain requirements and more recent product information that may not be fully described in this manual. Be sure to review the release notes before installation. Document Revision Level Revision Date Description MK-92HC November 2002 Initial Release Note: This document supersedes and replaces HiCommand Device Manager HiScan Installation Guide (MK-91HC005-4). MK-92HC May 2003 Revision 1, supersedes and replaces MK-92HC MK-92HC September 2003 Revision 2, supersedes and replaces MK-92HC MK-92HC February 2004 Revision 3, supersedes and replaces MK-92HC MK-92HC March 2004 Revision 4, supersedes and replaces MK-92HC MK-92HC September 2004 Revision 5, supersedes and replaces MK-92HC MK-92HC October 2004 Revision 6, supersedes and replaces MK-92HC MK-92HC February 2005 Revision 7, supersedes and replaces MK-92HC MK-92HC June 2005 Revision 8, supersedes and replaces MK-92HC MK-92HC July 2005 Revision 9, supersedes and replaces MK-92HC MK-92HC October 2005 Revision 10, supersedes and replaces MK-92HC MK-92HC February 2006 Revision 11, supersedes and replaces MK-92HC MK-92HC June 2006 Revision 12, supersedes and replaces MK-92HC MK-92HC October 2006 Revision 13, supersedes and replaces MK-92HC MK-92HC January 2007 Revision 14, supersedes and replaces MK-92HC MK-92HC June 2007 Revision 15, supersedes and replaces MK-92HC MK-92HC October 2007 Revision 16, supersedes and replaces MK-92HC MK-92HC January 2008 Revision 17, supersedes and replaces MK-92HC MK-92HC May 2008 Revision 18, supersedes and replaces MK-92HC Preface ix

10 Document Organization The following table provides an overview of the contents and organization of this document. Click the chapter title in the left column to go to that chapter. The first page of each chapter provides links to the sections in that chapter. Chapter Description Overview Installing the Device Manager Agent Operating the Device Manager Agent Contents of a Configuration Definition File Supported by Device Manager Troubleshooting Acronyms and Abbreviations Index Gives an overview of the Device Manager agent and describes its system requirements. Explains the procedures for installing and setting up the Device Manager agent. Provides notes on how to manage host operations and explains how to set up and operate the Device Manager agent. Describes the contents of the CCI configuration definition files when you use these definition files in Device Manager. Describes how to troubleshoot problems with the Storage Navigator. Defines the acronyms and abbreviations used in this document. Lists the topics in this document in alphabetical order. x Preface

11 Referenced Documents The following Hitachi referenced documents are also available for download on the Hitachi Data Systems Support Portal: Hitachi Storage Command Suite documents: Hitachi Device Manager and Provisioning Manager Server Installation and Configuration Guide, MK-98HC150 Hitachi Device Manager Command Line Interface (CLI) User's Guide, MK-91HC007 Hitachi Device Manager Error Codes, MK-92HC016 Hitachi Enterprise Storage Systems documents: Hitachi Lightning 9900 V Series User and Reference Guide, MK-92RD100 Hitachi Lightning 9900 User and Reference Guide, MK-90RD008 Hitachi Thunder 9500 V Series User and Reference Guide, MK-92RD100 Hitachi Modular Storage Systems document: Hitachi Thunder 9200 User and Reference Guide, MK-90DF504 Preface xi

12 Document Conventions This document uses the following typographic conventions: Convention Bold Italic screen/code Description Indicates text on a window, other than the window title, including menus, menu options, buttons, fields, and labels. Example: Click OK. Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: copy source-file target-file Note: Angled brackets (< >) are also used to indicate variables. Indicates text that is displayed on screen or entered by the user. Example: # pairdisplay -g oradb < > angled brackets Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: # pairdisplay -g <group> Note: Italic font is also used to indicate variables. [ ] square brackets Indicates optional values. Example: [ a b ] indicates that you can choose a, b, or nothing. { } braces Indicates required or expected values. Example: { a b } indicates that you must choose either a or b. vertical bar Indicates that you have a choice between two or more options or arguments. Examples: [ a b ] indicates that you can choose a, b, or nothing. { a b } indicates that you must choose either a or b. underline Indicates the default value. Example: [ a b ] This document uses the following icons to draw attention to information: Icon Label Description Note Calls attention to important and/or additional information. Tip Caution WARNING Provides helpful information, guidelines, or suggestions for performing tasks more effectively. Warns the user of adverse conditions and/or consequences (e.g., disruptive operations). Warns the user of severe conditions and/or consequences (e.g., destructive operations). xii Preface

13 Convention for Storage Capacity Values Getting Help Comments Storage capacity values for logical devices are calculated based on the following values: 1 KB (kilobyte) = 1024 bytes 1 MB (megabyte) = 1024 kilobytes or bytes 1 GB (gigabyte) = 1024 megabytes or bytes 1 TB (terabyte) = 1024 gigabytes or bytes The Hitachi Data Systems Support Center staff is available 24 hours a day, seven days a week. To reach us, please visit the support Web site for current telephone numbers and other contact information: If you purchased this product from an authorized HDS reseller, contact that reseller for support. Before calling the Hitachi Data Systems Support Center, please provide as much information about the problem as possible, including: The circumstances surrounding the error or failure. The exact content of any error message(s) displayed on the host system(s). Please send us your comments on this document. Make sure to include the document title, number, and revision. Please refer to specific section(s) and paragraph(s) whenever possible. doc.comments@hds.com Fax: Mail: Technical Writing, M/S Hitachi Data Systems Scripps Ranch Blvd. San Diego, CA Thank you! (All comments become the property of Hitachi Data Systems Corporation.) Preface xiii

14 xiv Preface

15 Overview This chapter gives an overview of the Device Manager agent and its system requirements. About the Device Manager Agent Reviewing the Host Requirements for the Device Manager Agent Supported SAN Environments Overview 1-1

16 About the Device Manager Agent The Device Manager agent is a program that runs on a host (an application server) to collect host and storage subsystem information, and report that data to the Device Manager server. Following is the information that is primarily collected: Host machine information (such as host names, IP addresses, HBA WWN, and iscsi name) Information about LDEVs allocated to the host (such as LDEV number, storage subsystem, LUN, and LDEV type) Information about file systems allocated to the host (such as file system types, mount points, and usage) Copy pair information (such as pair types and statuses) Although Device Manager agents are not required for Device Manager operations, they enable the following operations when they are installed on a host: Device Manager management of the status storage usage for each Device Manager host By installing a Device Manager agent on each host, you can control how the volumes in the storage subsystems to be managed are used on each host. Also, if you specify the settings so that information about the hosts that are managed by the Device Manager server is periodically updated, you can use a management client to check the latest information. Device Manager management of copy pairs By linking with CCI, you will be able to use the Device Manager Web Client to centrally perform operations such as creating copy pairs, and changing configurations and statuses, which previously had to be performed for each server. Note that the Device Manager agent is required when Provisioning Manager or Replication Manager is used. The Provisioning Manager server and Replication Manager communicate with the Provisioning Manager agent functionality and Replication Manager agent functionality within the Device Manager agent to perform operations, such as collecting necessary information or configuring host settings. Note: If you use the CIM/WBEM function of Device Manager, you can use the Device Manager agent to obtain performance information about Hitachi USP or Universal Storage Platform V/VM. For details about the required settings for obtaining performance information, see the Hitachi Device Manager and Provisioning Manager Server Installation and Configuration Guide. 1-2 Overview

17 Reviewing the Host Requirements for the Device Manager Agent The following explains the system requirements for hosts on which the Device Manager agent is to be installed. Caution: The name of each host on which the Device Manager agent runs must be unique within the notification destination Device Manager server. Device Manager agent version 6.0 can connect to Device Manager server version 6.0 or later. However, if the version of the Device Manager server is later than that of the Device Manager agent, the Device Manager functionality that can be used is limited to that of the Device Manager agent. Supported Operating Systems The prerequisite OS for the Device Manager agent depends on whether the agent is used in an IPv4 environment or IPv6 environment. Also, the Device Manager agent service might not start unless the patches required for the Device Manager agent prerequisite OS have been applied. Supported Operating Systems for Use on IPv4 Environments The following table shows the prerequisite OSs for Device Manager agents used in an IPv4 environment. Table 1.1 Prerequisite Operating Systems for Device Manager Agents (IPv4 Environments) OS Version Architecture Remarks Windows 2000 #1, #2 SP4 or later x86 Not applicable Windows Server No SP 2003 #1, #2 SP1 SP2 No SP SP2 Windows Server 2003 R2 #1, #2 No SP SP2 x86 IPF x64 Edition (EM64T and AMD 64) x86 x64 Edition (EM64T and AMD64) Not applicable Runs under WOW64.We recommend that SP2 be installed. Runs under WOW64. Not applicable Runs under WOW64. Overview 1-3

18 OS Version Architecture Remarks Windows Server 2008 No SP x86 Not applicable IPF x64 Edition (EM64T and AMD64) Runs under WOW64. Runs under WOW64. Solaris 8 SPARC (32 and 64 bit) We recommend that Solaris Patch Cluster be installed. 9 SPARC (32 and 64 bit) We recommend that Solaris Patch Cluster be installed. 10 #3 SPARC (32 and 64 bit) We recommend that Solaris Patch Cluster be installed. x64 Edition (AMD64) #4 AIX bit 64 bit bit 64 bit bit 64 bit We recommend that Solaris Patch Cluster be installed. Not applicable Not applicable The Device Manager agent does not support environments where the Secure by Default function is enabled. Red Hat Enterprise Linux Linux AS/ES 3 Update 0 Update 3 Update 4 Update 6 x86 IPF x64 Edition (EM64T) The following OSs are not supported for Provisioning Manager. Linux AS/ES 3 (x64 Edition) Linux AS/ES 3 (IPF) Linux AS/ES 4 Update 1 Update 3 Update Linux SUSE LINUX Enterprise Server 9 x86 Only the default kernel is supported. Not supported for Provisioning Manager. 10 x86 Only the default kernel is supported. Not supported for Provisioning Manager. 1-4 Overview

19 OS Version Architecture Remarks HP-UX 11i v1 PA-RISC (32 and 64 bit) Workstation is not supported. 32-bit is not supported for Provisioning Manager. 11i v2 11i v3 PA-RISC (64bit) IPF PA-RISC (64bit) IPF Workstation is not supported. Workstation is not supported. Note: Third-party agents are available for other servers. For the latest information about these agents, please contact your Hitachi Data System representative or refer to documentation about a specific agent. #1: VMware ESX Server 3.0.x is supported. #2: If Windows Firewall has been enabled, the Device Manager agent must be registered as an exception with Windows Firewall when a new installation of the Device Manager agent is performed. For details on how to do this after installing the agent, see Notes When a Firewall is Being Enabled. #3: The Device Manager agent runs in the usual global environment (global zone) only. If a non-global zone has been created, install the Device Manager agent in the global zone. #4: The Device Manager agent supports only the Sun Fire x64 server family hardware. In addition, only the 64-bit kernel mode is supported. Supported Operating Systems for Use on IPv6 Environments The following table shows the prerequisite OSs for Device Manager agents used in an IPv6 environment. Table 1.2 Prerequisite Operating Systems for Device Manager Agents (IPv6 Environments) OS Version Architecture Remarks Windows Server SP2 or later x86 Not applicable 2003 #1, #2 IPF x64 Edition (EM64T and AMD64) Runs under WOW64. Runs under WOW64. Windows Server SP2 or later x86 Not applicable 2003 R2 #1, #2 x64 Edition (EM64T and AMD64) Runs under WOW64. Windows Server 2008 No SP x86 Not applicable IPF x64 Edition (EM64T and AMD64) Runs under WOW64. Runs under WOW64. Overview 1-5

20 OS Version Architecture Remarks Solaris 10 #3 SPARC (32 and 64 bit) We recommend that Solaris Patch Cluster be installed. x64 Edition (AMD64) #4 AIX bit 64 bit bit 64 bit We recommend that Solaris Patch Cluster be installed. Not applicable The Device Manager agent does not support environments where the Secure by Default function is enabled. Red Hat Enterprise Linux Linux AS/ES 4 Update 4 x86 x64 Edition (EM64T) Not applicable 4.5 Linux HP-UX 11i v2 PA-RISC (64bit) IPF Workstation is not supported. 11i v3 PA-RISC (64bit) IPF Workstation is not supported. Note: Third-party agents are available for other servers. For the latest information about these agents, please contact your Hitachi Data System representative or refer to documentation about a specific agent. #1: VMware ESX Server 3.0.x is supported. #2: If Windows Firewall has been enabled, the Device Manager agent needs to be registered as an exception with Windows Firewall when a new installation of the Device Manager agent is performed. For details on how to do this after installing the agent, see Notes When a Firewall is Being Enabled. #3: The Device Manager agent runs in the usual global environment (global zone) only. If a non-global zone has been created, install the Device Manager agent in the global zone. #4: The Device Manager agent supports only the Sun Fire x64 server family hardware. In addition, only the 64-bit kernel mode is supported. 1-6 Overview

21 Caution: To perform operations in an IPv6 environment, set the following properties in the server.properties file: server.http.socket.agentaddress server.http.socket.bindaddress For details about the server.properties file, see The server.properties File. The Device Manager agent does not support environments where only IPv6 addresses can be used. To use the Device Manager agent in IPv6 environments, set up the OS so both IPv4 and IPv6 addresses can be used. The Device Manager agent only supports global addresses. You cannot use link-local addresses or global unique local addresses (site-local addresses). Applicable Patches for Operating Systems When using the Device Manager agent, it is assumed that the patches listed in Table 1.3 to Table 1.7 have been applied. If those patches are not applied, the Device Manager agent service might not start. Note that Table 1.3 to Table 1.7 only list the OSs to which patches must be applied. Table 1.3 Required Patches for Operating Systems Supported by the Device Manager Agent (Windows) OS Architecture Patches Windows Server 2003(No SP) Windows Server 2003(SP1) Windows Server 2003 R2(No SP) x64 (EM64T and AMD64) x86ipf x86 x64 (EM64T and AMD64) KB KB KB KB Overview 1-7

22 Table 1.4 Required Patches for Operating Systems Supported by the Device Manager Agent (Solaris) OS Architecture Patches Solaris 8 SPARC (32 and 64 bit) SunOS 5.8: /usr/bin/fgrep patch SunOS 5.8: /usr/bin/nawk patch SunOS 5.8: Patch for patchadd and patchrm SunOS 5.8: Unable to load fontset in 64-bit Solaris 8 iso-1 or iso SunOS 5.8: /usr/lib/libdhcpagent.so.1 patch SunOS 5.8: Font2DTest2 abort when Lucida Sans Thai Typewriter selected SunOS 5.8: /usr/lib/libmtmalloc.so.1 patch SunOS 5.8: /kernel/drv/random patch SunOS 5.8: /kernel/fs/mntfs and /kernel/fs/sparcv9/mntfs patch SunOS 5.8: /sbin/sulogin and /sbin/netstrategy patch SunOS 5.8: /sbin/uadmin and /sbin/hostconfig patch SunOS 5.8: mount patch SunOS 5.8: linker patch SunOS 5.8: 32-Bit Shared library patch for C SunOS 5.8: 64-Bit Shared library patch for C SunOS 5.8: /sbin/init and /usr/sbin/init patch SunOS 5.8: RBAC Feature Patch OpenGL 1.3: OpenGL Patch for Solaris (32-bit) OpenGL 1.3: OpenGL Patch for Solaris (64-bit) SunOS 5.8: fsck patch X : Xsun patch SunOS 5.8: IIIM and X Input & Output Method patch Motif and 2.1.1: Runtime library patch for Solaris SunOS 5.8: /usr/lib/fs/ufs utilities patch SunOS 5.8: kernel update and Apache patch SunOS 5.8: Kernel Patch CDE 1.4: dtwm patch 1-8 Overview

23 OS Architecture Patches SunOS 5.8: /usr/kernel/sys/acctctl and /usr/kernel/sys/exacctsys patch SunOS 5.8: LDAP2 client, libc, libthread and libnsl libraries patch SunOS 5.8: kernel patch SunOS 5.8: libresolv.so.2 and in.named patch Solaris 9 SPARC (32 and 64 bit) X : OWconfig patch SunOS 5.9: 32-bit Shared library patch for C SunOS 5.9: 64-Bit Shared library patch for C SunOS 5.9: linker Patch X : Xsun patch OpenGL 1.3: OpenGL Patch for Solaris (32-bit) OpenGL 1.3: OpenGL Patch for Solaris (64-bit) Solaris 10 SPARC (32 and 64 bit) SunOS 5.10: libzonecfg Patch SunOS 5.10: zones library and zones utility patch SunOS 5.10: Install and Patch Utilities Patch SunOS 5.10: Solaris Crypto Framework patch SunOS 5.10: svccfg & svcprop patch SunOS 5.10: FMA Patch SunOS 5.10: kernel patch x64 Edition (AMD64) SunOS 5.10_x86: libzonecfg patch SunOS 5.10_x86: zoneadmd, zlogin and zoneadm patch SunOS 5.10_x86: Install and Patch Utilities Patch Obsoleted by: SunOS 5.10_x86: Install and Patch Utilities Patch SunOS 5.10_x86: umountall patch SunOS 5.10_x86: biosdev patch SunOS 5.10_x86: Fault Manager Patch SunOS 5.10_x86: cadp160 driver patch SunOS 5.10_x86: Shared library patch for C++_x SunOS 5.10_x86: SUNWgrub patch Note: You can also install required patches by applying the following patches for the appropriate OS version. J2SE Solaris 8 Recommended Patch Cluster J2SE Solaris 9 Recommended Patch Cluster J2SE Solaris 10 Recommended Patch Cluster For details on the latest information, see the Sun Microsystems web site. Overview 1-9

24 Table 1.5 Required Patches for Operating Systems Supported by the Device Manager Agent (AIX) OS Architecture Patches AIX 5.2 AIX bit 64 bit 32 bit 64 bit When using Java program version 1.4.2: (APAR IY67913) When using Java program version 5.0: (APAR IY67914) When using Java program version (APAR IY69190) When using Java program version 5.0: (APAR IY71011) Note: For details on the latest information, see the IBM web site Table 1.6 Required Patches for Operating Systems Supported by the Device Manager Agent (Linux) OS Architecture Patches Red Hat Enterprise Linux AS/ES 3 SUSE LINUX Enterprise Server 10 x86 x64 Edition (EM64T) IPF x86 gdb i386.rpm gdb i386.rpm gdb ia64.rpm gdb or later 1-10 Overview

25 Table 1.7 Required Patches for Operating Systems Supported by the Device Manager Agent (HP-UX) OS Architecture Patches HP-UX 11i v1 PA-RISC (32 and 64 bit) PHNE_23502 s700_ ONC/NFS General Release/Performance Patch PHKL_24253 s700_ thread nostop patch supporting NFS PHKL_24254 s700_ thread nostop patch supporting NFS PHKL_24255 s700_ thread nostop patch supporting NFS PHKL_24256 s700_ signal race condition patch/threads enh PHKL_24257 s700_ thread nostop patch supporting NFS PHKL_24751 s700_ preserve IPSW W-bit and GR31 lower bits PHSS_24932 s700_ Japanese TrueType font patch PHSS_24934 s700_ Korean TrueType font patch PHSS_24936 s700_ Chinese-S TrueType font patch for PHNE_25084 s700_ Cumulative STREAMS Patch PHCO_25226 s700_ Initialized TLS, Psets, Mutex performance PHKL_25227 s700_ VM/JFS deadlock; mmap performance/defect PHKL_25367 s700_ Priority inversion and thread hang PHSS_25449 s700_ X/Motif Runtime OCT2001 Periodic Patch PHCO_25452 s700_ libc cumulative patch PHKL_25468 s700_ eventport (/dev/poll) pseudo driver PHKL_25614 s700_ VM-JFS deadlock, mmap, perf thread creation PHKL_25728 s700_ Psets Enablement, thread cumulative PHKL_25729 s700_ signals, threads enhancement, Psets Enablement PHKL_25840 s700_ Thread NOSTOP, Psets, Thread Abort PHKL_25842 s700_ Thread Abort Overview 1-11

26 OS Architecture Patches PHKL_25871 s700_ eventport syscalls;socket close(2) hang fix PHSS_25881 s700_ X/Motif Runtime JAN2002 Periodic Patch PHKL_27091 s700_ Core PM, vpar, Psets Cumulative, slpq1 perf PHKL_27092 s700_ Thread NOSTOP, Abort; Psets PHKL_28489 s700_ copyin EFAULT, LDCD access type PHNE_29887 s700_ cumulative ARPA Transport patch PHCO_29960 s700_ Pthread enhancement and fixes PHSS_30049 s700_ ld(1) and linker tools cumulative patch PHKL_32457 s700_ SPP fragmentation;aio;evp;ufalloc;dup2 race PHKL_32927 s700_ PA-8800 Fix Java (64-bit JVM) process hang PHKL_34534 s700_ vpar,callout, abstime, sync perf, wakeup HP-UX 11i v2 PA-RISC (64bit) When using Java program version 1.4.2: None. When using Java program version 5.0: PHKL_35029 s700_ ksleep cumulative patch IPF When using Java program version 1.4.2: PHSS_30015 s700_ Aries cumulative patch PHKL_30192 s700_ Eliminate race at MxN kernel thread creation PHCO_30476 s700_ Pthread library patch PHSS_34201 s700_ Aries cumulative patch When using Java program version 5.0: PHSS_30015 s700_ Aries cumulative patch PHKL_30192 s700_ Eliminate race at MxN kernel thread creation PHCO_30476 s700_ Pthread library patch PHSS_33349 s700_ linker + fdp cumulative patch PHSS_33350 s700_ ac++ Runtime PHSS_34043 s700_ Integrity Unwind Library PHSS_34201 s700_ Aries cumulative patch PHKL_35029 s700_ ksleep cumulative patch Note: Depending on the OS release date, required patches might have been applied at the time of delivery. For details on the latest information, see the HP web site 1-12 Overview

27 Precautions for Using Provisioning Manager Keep the following in mind for use with Provisioning Manager: Host configuration (creation, expansion, and deletion of file systems, and creation and deletion of device files) is supported for host OSs of the following language versions: For Windows 2000 English, French, German, Italian, Spanish, Simplified Chinese, Traditional Chinese, Korean, Japanese, Portuguese, Brazilian (Portuguese Brazilian), Danish, and Swedish For Windows Server 2003 (x86), or Windows Server 2003 R2 English, French, German, Italian, Spanish, Simplified Chinese, Traditional Chinese, Korean, Japanese, Portuguese, Brazilian (Portuguese Brazilian), and Swedish For Windows Server 2003 (IPF), or Windows Server 2003 (x64) English and Japanese For Windows Server 2008 English, French, German, Spanish and Japanese Host configuration cannot be performed in the following two cases even if the OS is one of the above language versions: When the Multilingual User Interface Pack has been applied. When the language settings of the system have been changed. Host, file system, and device file settings can be viewed from the server no matter what language version of Windows is on the agent host. If the host OS is Windows 2000, you must install the diskpart.exe command line utility provided by Microsoft in the following folder: system-folder\system32\ If the host OS is HP-UX, Provisioning Manager will not support environments containing or allowing mirror volumes. For HP-UX 11i v2 or earlier: If MirrorDisk/UX is installed on the host, Provisioning Manager functionality cannot be used to view host information and perform host settings. For HP-UX 11i v3: MirrorDisk/UX is installed on the host by OS default. In this case, Provisioning Manager functionality can be used to view host information and perform host settings. Note that software RAIDs using MirrorDisk/UX are not supported. Overview 1-13

28 When the host OS is HP-UX, in the /etc/lvmconf directory, LVM creates a backup file for the configuration information about volume groups. Therefore, to create a volume group by using the host management functionality of Provisioning Manager, a maximum of 500 MB of free disk space (when 255 volume groups are created) is additionally required under /etc/lvmconf. Applicable Java Programs If the host OS is Solaris, AIX, or HP-UX, Java programs need to be installed on the host before the Device Manager agent is installed. Note: If the host OS is Windows or Linux, JRE 5.0 is automatically installed with the Device Manager agent. The following table shows the prerequisite Java programs for Device Manager agents. Table 1.8 Java Programs Required for Device Manager Agents OS Architecture Java Programs Solaris SPARC (32 and 64 bit) For IPv4 environment operation: JDK 1.4.2_xx (xx is 15 or later) JDK 5.0 (Update 11 or later) The JRE bundled with the OS For IPv6 environment operation: JDK 5.0 (Update 11 or later) The JRE bundled with the OS AIX AMD64 32 bit 64 bit JDK 5.0 (Update 11 or later) The JRE bundled with the OS For IPv4 environment operation: JDK (Update 8 or later) JDK 5.0 (Update 5 or later) The JRE bundled with the OS For IPv6 environment operation: JDK 5.0 (Update 5 or later) The JRE bundled with the OS 1-14 Overview

29 OS Architecture Java Programs HP-UX PA-RISC (32 and 64 bit) IPF For IPv4 environment operation: JDK 5.0 (Update 11 or later) JRE 5.0 (Update 11 or later) JDK 1.4.2_xx (xx is 17 or later) RTE 1.4.2_xx (xx is 17 or later) The JRE bundled with the OS For IPv6 environment operation: JDK 5.0 (Update 11 or later) JRE 5.0 (Update 11 or later) The JRE bundled with the OS Note: Use a package program instead of a self-expanding program. If both version and version 5.0 are installed, Device Manager agent uses the version 5.0 Java program. The following commands can be used to check the version of the Java programs installed on the host. Table 1.9 Checking the Version of the Java Programs OS Java Programs Command Solaris JDK 5.0 pkginfo -li SUNWj5rt JDK pkginfo -li SUNWj3rt AIX JDK 5.0 (32 bit) lslpp -l Java5.sdk JDK 5.0 (64 bit) lslpp -l Java5_64.sdk JDK (32 bit) lslpp -l Java14.sdk JDK (64 bit) lslpp -l Java14_64.sdk HP-UX JDK 5.0 swlist Java15JDK JRE 5.0 swlist Java15JRE JDK swlist T1456AA RTE swlist T1457AA Overview 1-15

30 Caution: Before updating the Java programs (after installing the Device Manager agent), stop the Device Manager agent service. Also, when changing a Java program installation path, change the server.agent.jre.location setting in the server.properties file. For details about stopping and starting the Device Manager agent service, see Managing the Operating Status of the Device Manager Agent Service. For details about the server.properties file, see The server.properties File. Supported File Systems The following table lists the file systems supported by the Device Manager agent. However, depending on the combination of OS and file system, you might not be able to use Provisioning Manager to manage or use these. Table 1.10 File Systems Supported by the Device Manager Agent OS File System Description Windows NTFS Standard OS file system. If you use Provisioning Manager to manage this type of file system, you need to use a dynamic disk or basic disk for the volume manager. However, if you use a basic disk, you cannot expand file systems by using Provisioning Manager. Also, if you use a dynamic disk, you can expand file systems only when they are mounted. FAT FAT32 Standard OS file system. Provisioning Manager only allows the file system to be displayed. Standard OS file system. Provisioning Manager only allows the file system to be displayed Overview

31 OS File System Description Solaris UFS Standard OS file system. Provisioning Manager does not allow the file system to be expanded. Veritas File System One of the following versions needs to be used for management by Provisioning Manager: For Solaris 8: VERITAS File System 3.5 VERITAS File System 4.0 For Solaris 9: VERITAS File System 3.5 VERITAS File System 4.0 Veritas File System 5.0 For Solaris 10 (SPARC edition): Veritas File System 5.0 For Solaris 10 (x64 Edition (AMD64)): VERITAS File System 4.1 Use the same version of Veritas Volume Manager as the Veritas File System used on the volume manager. Note that file systems can only be expanded when mounted. AIX JFS Standard OS file system. Note that file systems can only be expanded when mounted. Red Hat Enterprise Linux SUSE LINUX Enterprise Server ext2 ext3 ext2 ext3 Standard OS file system. Note that file systems can only be expanded when mounted. When the file system is expanded, it is temporarily unmounted. The file system cannot be extended online. When a file system is expanded, stop all jobs. Standard OS file system. Provisioning Manager is not supported on SUSE LINUX Enterprise Server. Overview 1-17

32 OS File System Description HP-UX Veritas File System (JFS # ) HFS The following versions need to be used for management by Provisioning Manager: For HP-UX 11i v1 (x64): VERITAS File System 3.5. Note: To enable VERITAS File System 3.5, install a version of Software Pack (Optional HP-UX 11i v1 Core Enhancements) that was released in or after December For versions released before the December 2005 version of HP-UX 11i v2: VERITAS File System 3.5 (OS default) For the December 2005 and later versions of HP-UX 11i v2: VERITAS File System 4.1 (OS default) For HP-UX 11i v3: VERITAS File System 4.1 (OS default) Note that file systems can only be expanded when mounted. Standard OS file system. Provisioning Manager only allows the file system to be displayed. #: This includes HP OnlineJFS and HP JFS, which are recognized as Veritas File System on a host. A file system can be expanded in the online mode by using Provisioning Manager, if a Device Manager agent version or later and HP OnlineJFS are installed on the host. When you install HP OnlineJFS, make sure you do the following: Install a version of HP OnlineJFS that is the same as the version of Veritas File System. Provisioning Manager only supports an environment where the versions of Veritas File System and HP OnlineJFS are the same. Enable HP OnlineJFS. If HP OnlineJFS is disabled, you cannot use Provisioning Manager to expand file systems. If a Device Manager agent version earlier than is installed on the host, or HP OnlineJFS is not installed on the host, the file system is unmounted during expansion, so it cannot be expanded in the online mode. When a file system is expanded, stop all jobs Overview

33 Supported Volume Managers The following table lists volume managers supported by the Device Manager agent. Note that the table only lists OSs that support volume managers: The % Used metric is not reported by these volume managers on the HP-UX or AIX OS. Please refer to the note following the table for information about % Used. Table 1.11 Volume Managers Supported by the Device Manager Agent OS Version Architecture Volume Manager Windows 2000 SP4 x86 When Device Manager is used: Basic Dynamic VERITAS Volume Manager 2.7 VERITAS Volume Manager 3.0 VERITAS Volume Manager 3.5 When Provisioning Manager is also used: Basic #1 Dynamic Windows Server 2003 No SP x86 IPF x64 Edition (EM64T and AMD64) When Device Manager is used: Basic Dynamic When Provisioning Manager is also used: Basic #1 Dynamic SP1 x86 When Device Manager is used: Basic Dynamic VERITAS Volume Manager 4.3 When Provisioning Manager is also used: Basic #1 Dynamic IPF When Device Manager is used: Basic Dynamic When Provisioning Manager is also used: Basic #1 Dynamic Overview 1-19

34 OS Version Architecture Volume Manager Windows Server 2003 SP2 x86 IPF x64 Edition (EM64T and AMD64) When Device Manager is used: Basic Dynamic When Provisioning Manager is also used: Basic #1 Dynamic Windows Server 2003 R2 No SP SP2 x86 x64 Edition (EM64T and AMD64) When Device Manager is used: Basic Dynamic When Provisioning Manager is also used: Basic #1 Dynamic Windows Server 2008 No SP x86 IPF x64 Edition (EM64T and AMD64) Solaris 8 SPARC (32 or 64 bit) 9 SPARC (32 or 64 bit) When Device Manager is used: Basic Dynamic When Provisioning Manager is also used: Basic #1 Dynamic When Device Manager is used: SDS VERITAS Volume Manager 3.2 VERITAS Volume Manager 3.5 VERITAS Volume Manager 4.0 When Provisioning Manager is also used #2 : SDS VERITAS Volume Manager 3.5 VERITAS Volume Manager 4.0 When Device Manager is used: SVM 1.0 VERITAS Volume Manager 3.5 VERITAS Volume Manager 4.0 VERITAS Volume Manager 4.1 Veritas Volume Manager 5.0 When Provisioning Manager is also used #2 : SVM 1.0 VERITAS Volume Manager 3.5 VERITAS Volume Manager 4.0 Veritas Volume Manager Overview

35 OS Version Architecture Volume Manager Solaris 10 SPARC (32 or 64 bit) 10 x64 Edition (AMD64) When Device Manager is used: SVM 1.0 Veritas Volume Manager 5.0 When Provisioning Manager is also used #2 : SVM 1.0 Veritas Volume Manager 5.0 When Device Manager is used: SVM 1.0 Veritas Volume Manager 4.1 When Provisioning Manager is also used #2 : SVM 1.0 Veritas Volume Manager 4.1 AIX bit 64 bit When Device Manager is used: LVM When Provisioning Manager is also used: LVM Red Hat Enterprise Linux Linux AS/ES 3 x86 IPF When Device Manager is used: LVM x64 Edition (EM64T) When Provisioning Manager is also used: LVM Linux AS/ES 4 x86 When Device Manager is used: IPF LVM2 x64 Edition (EM64T) When Provisioning Manager is also used: LVM2 Linux 5 x86 When Device Manager is used: IPF LVM2 x64 Edition (EM64T) When Provisioning Manager is also used: LVM2 SUSE LINUX Enterprise Server 9 x86 When Device Manager is used: LVM2 When Provisioning Manager is also used: Unsupported 10 x86 When Device Manager is used: LVM2 When Provisioning Manager is also used: Unsupported Overview 1-21

36 OS Version Architecture Volume Manager HP-UX 11i v1 PA-RISC (32 bit) 11i v1 PA-RISC (64 bit) When Device Manager is used: LVM VERITAS Volume Manager 3.5 When Provisioning Manager is also used: Unsupported When Device Manager is used: LVM VERITAS Volume Manager 3.5 When Provisioning Manager is also used: LVM VERITAS Volume Manager 3.5 #3 11i v2 (for versions earlier than 12/2005) 11i v2 (for versions later than or equal to 12/2005) PA-RISC (64 bit) IPF PA-RISC (64 bit) IPF When Device Manager is used: LVM VERITAS Volume Manager 3.5 VERITAS Volume Manager 4.1 When Provisioning Manager is also used: LVM VERITAS Volume Manager 3.5 #3 When Device Manager is used: LVM VERITAS Volume Manager 3.5 VERITAS Volume Manager 4.1 When Provisioning Manager is also used: LVM VERITAS Volume Manager 4.1 #3 11i v3 PA-RISC (64 bit) IPF When Device Manager is used: LVM #4 VERITAS Volume Manager 4.1 When Provisioning Manager is also used: LVM #4 VERITAS Volume Manager 4.1 # Overview

37 OS Version Architecture Volume Manager Note: To use Provisioning Manager to perform operations on file systems or device files (creation, expansion, or deletion), you must install a volume manager on each host. #1: File systems cannot be expanded by using Provisioning Manager. #2: If the host OS is Solaris, you can use Provisioning Manager to display, create and delete file systems and device files, even without a volume manager. However Provisioning Manager cannot expand file systems created without using Veritas Volume Manager, and can only display file systems and device files that are created by using SDS or SVM. If a host is not the owner of a SDS/SVM diskset, information about the logical volumes and file systems related to that diskset is not displayed. #3: Provisioning Manager can only display file systems and device files that are created by using Veritas Volume Manager. #4: If LVM that supports L2 is installed on a host, Provisioning Manager always uses L2 to create file systems and device files. Note: % Used Displays the volume usage (units: %). This item is updated when the Device Manager agent sends the volume usage to the Device Manager server. If the agent is not running on the host, this field is blank. The Device Manager agent may not be installed or may be installed but not started. If multiple paths are assigned to a single volume, information is displayed for the number of times LUN security is configured to the paths, in the List Objects - Open-Allocated subwindow. Use the following formula to obtain the storage usage: ((used-capacity-of-the-file-system-built-on-the-target-storage) / (storage-capacity)) x 100 (%) The usage cannot be calculated if the values required for calculation cannot be obtained correctly. In this case, -- appears. The conditions that enable % used to be displayed are as follows: When Windows is the platform of the host using the storage: A drive letter is assigned to the LU. The LU is mounted on a directory. The LU has multiple partitions and, among the disks in the LU, drive letters are assigned to all partitioned disks and that LU is mounted on a directory. The LU or all of the LU that has multiple partitions is not under a dynamic disk configuration and is not incorporated into a volume manager (VxVM). If the version of the Device Manager agent is earlier than 3.5, the displayed usage rate might be incorrect. Overview 1-23

38 When Solaris is the platform of the host using the storage: The target LU is not incorporated into a volume manager (VxVM, SVM, or SDS). The LU is mounted. When Linux is the platform of the host using the storage: The target LU is not incorporated into a volume manager (LVM, LVM2). The LU has multiple partitions and no partitioned disk is incorporated into a volume manager (LVM, LVM2). The LU or all of the LU that has multiple partitions is mounted. When HP-UX or AIX is the platform of the host using the storage, % used is not displayed Overview

39 Supported Path Management Software Path management software is required when path redundancy is used between host ports and storage subsystem ports to increase system reliability and availability. Table 1.12 lists the path management software supported by the Device Manager agent. Note that the table only lists OSs that support path management software. Table 1.12 Path Management Software Supported by the Device Manager Agent OS Version Architecture Path Management Software Windows 2000 SP4 x86 When Device Manager is used: Dynamic Link Manager /A to When Provisioning Manager is also used: Dynamic Link Manager to Windows Server 2003 No SP x86 IPF x64 Edition (EM64T and AMD64) When Device Manager is used: Dynamic Link Manager to When Provisioning Manager is also used: Dynamic Link Manager to When Device Manager is used: Dynamic Link Manager 5.7 to Windows MPIO (MPIO DSM: Provided by Dynamic Link Manager 5.5 or later) When Provisioning Manager is also used: Dynamic Link Manager 5.7 to SP1 x86 IPF When Device Manager is used: Dynamic Link Manager 5.6 to Windows MPIO (MPIO DSM: Provided by Dynamic Link Manager 5.5 or later) When Provisioning Manager is also used: Dynamic Link Manager to SP2 x86 When Device Manager is used: Dynamic Link Manager to Windows MPIO (MPIO DSM: Provided by Dynamic Link Manager or later) When Provisioning Manager is also used: Dynamic Link Manager to IPF When Device Manager is used: Dynamic Link Manager 5.6 to Windows MPIO (MPIO DSM: Provided by Dynamic Link Manager or later) When Provisioning Manager is also used: Dynamic Link Manager 5.6 to Overview 1-25