Hitachi Storage Command Suite Hitachi Device Manager Software Agent Installation Guide

(1)

Hitachi Storage Command Suite

Hitachi Device Manager Software

Agent Installation Guide

F

AST

F

IND

L

INKS

Document Organization

Software Version

Getting Help

Contents

(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.

(3)

Overview ... 1-1

About the Device Manager Agent...1-2

Reviewing the Host Requirements for the Device Manager Agent ...1-3

Supported Operating Systems...1-3

Supported Operating Systems for Use on IPv4 Environments...1-3

Supported Operating Systems for Use on IPv6 Environments...1-5

Applicable Patches for Operating Systems ...1-7

Precautions for Using Provisioning Manager...1-13

Applicable Java Programs ...1-14

Supported File Systems...1-16

Supported Volume Managers ...1-19

Supported Path Management Software...1-23

Supported Cluster Software ...1-30

Supported SAN Environments...1-34

Supported Storage Subsystems...1-34

Supported Host Bus Adapter Models...1-35

Supported iSCSI Connection Configurations ...1-37

(4)

Installing the Device Manager Agent... 2-1

Installing the Device Manager Agent in Windows ... 2-2

Before Installing in Windows... 2-2

Performing a New Installation in Windows ... 2-5

Performing an Upgrade Installation in Windows... 2-10

Performing a Restoration Installation in Windows ... 2-13

Installing the Device Manager Agent in UNIX ... 2-16

Before Installing in UNIX ... 2-16

Before Installing in Solaris... 2-19

Before Installing in AIX ... 2-20

Before Installing in Linux... 2-21

Before Installing in HP-UX... 2-21

Performing an Installation in UNIX ... 2-23

Performing a Silent Installation of the Device Manager Agent... 2-28

Uninstalling the Device Manager Agent... 2-31

Uninstalling the Device Manager Agent in Windows ... 2-32

Uninstalling in Windows ... 2-32

Deleting Tasks that Execute the HiScan Command ... 2-32

Uninstalling the Device Manager Agent in UNIX ... 2-33

Operating the Device Manager Agent... 3-1

Before Operating the Device Manager Agent... 3-2

Operations that Require Restarting the Device Manager Agent Service ... 3-2

Notes When a Host Has Multiple Network Adapters ... 3-2

Notes When Changing the Storage Subsystem Configuration ... 3-3

Notes When an Invalid Path Exists ... 3-3

Notes on Using Device Manager to Monitor Copy Pairs ... 3-3

Notes When the Host OS is Windows... 3-4

Notes for the Windows Server 2003 or Windows Server 2008 Host OS... 3-4

Notes on Allocating a Drive for The Device ... 3-4

Notes on Using VMware ESX Server ... 3-4

Notes When a Firewall is Being Enabled ... 3-6

Notes on Changing the User of the Device Manager Agent Service ... 3-6

Notes When the Host OS is Solaris ... 3-7

Notes for When VxVM is Being Used ... 3-7

Notes on Managing LU Partitions Without Labels... 3-7

Notes When the Host OS is AIX... 3-8

Notes on Operating in Cluster Environments... 3-8

Notes on Changing the SED Mode To all... 3-8

Notes on Upgrading to AIX 5.2 or later... 3-9

Notes When the Host OS is Linux ... 3-9

(5)

Setting Device Manager Server Information ...3-10

Setting the Cycle of Reporting Host Information to the Device Manager

Server...3-10

Specifying Settings for Managing Copy Pairs ...3-11

Specifying Settings When a Host Manages 100 or More LUs ...3-11

Setting Values When a Volume Manager is Not Used...3-13

Setting Values When a Volume Manager is Used...3-14

Operating the Device Manager Agent...3-19

Managing the Operating Status of the Device Manager Agent Service ...3-19

Reporting Host Information to the Device Manager Server ...3-20

Checking the Version of the Device Manager Agent ...3-20

Using a User-created Configuration Definition File...3-21

Before Using a User-created Configuration Definition File in Device

Manager...3-21

Reporting Configuration Definition File Data to the Device Manager Server....3-22

Using Device Manager with CCI ...3-22

Notes When You Delete Copy Pairs...3-22

Notes on Optimization Processing of the Configuration Definition File ...3-22

Instance Number and Service Number of CCI Used by Device

Manager ...3-23

Using Device Manager Agent Commands...3-24

hbsasrv Command Syntax ...3-24

hdvm_info Command Syntax ...3-25

hdvmagt_account Command Syntax...3-26

hdvmagt_schedule Command Syntax ...3-27

hdvmagt_setting Command Syntax ...3-28

HiScan Command Syntax ...3-30

hldutil Command Syntax...3-31

TIC Command Syntax ...3-36

Working with Agent Property Files ...3-37

The agent.properties File...3-37

The hldutil.properties File ...3-39

The logger.properties File...3-40

The programproductinfo.properties File ...3-41

The server.properties File...3-41

Troubleshooting ... 4-1

Troubleshooting ...4-2

Calling the Hitachi Data Systems Support Center ...4-2

(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

(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.

(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.

(9)

Release Notes

Release notes can be found on the documentation CD or on the Hitachi Data Systems Support Portal:

https://extranet.hds.com/http:/aim.hds.com/portal/dt

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-92HC019-00 November 2002 Initial Release

Note: This document supersedes and replaces HiCommand Device Manager HiScan Installation Guide (MK-91HC005-4).

MK-92HC019-01 May 2003 Revision 1, supersedes and replaces MK-92HC019-00 MK-92HC019-02 September 2003 Revision 2, supersedes and replaces MK-92HC019-01 MK-92HC019-03 February 2004 Revision 3, supersedes and replaces MK-92HC019-02 MK-92HC019-04 March 2004 Revision 4, supersedes and replaces MK-92HC019-03 MK-92HC019-05 September 2004 Revision 5, supersedes and replaces MK-92HC019-04 MK-92HC019-06 October 2004 Revision 6, supersedes and replaces MK-92HC019-05 MK-92HC019-07 February 2005 Revision 7, supersedes and replaces MK-92HC019-06 MK-92HC019-08 June 2005 Revision 8, supersedes and replaces MK-92HC019-07 MK-92HC019-09 July 2005 Revision 9, supersedes and replaces MK-92HC019-08 MK-92HC019-10 October 2005 Revision 10, supersedes and replaces MK-92HC019-09 MK-92HC019-11 February 2006 Revision 11, supersedes and replaces MK-92HC019-10 MK-92HC019-12 June 2006 Revision 12, supersedes and replaces MK-92HC019-11 MK-92HC019-13 October 2006 Revision 13, supersedes and replaces MK-92HC019-12 MK-92HC019-14 January 2007 Revision 14, supersedes and replaces MK-92HC019-13 MK-92HC019-15 June 2007 Revision 15, supersedes and replaces MK-92HC019-14 MK-92HC019-16 October 2007 Revision 16, supersedes and replaces MK-92HC019-15 MK-92HC019-17 January 2008 Revision 17, supersedes and replaces MK-92HC019-16 MK-92HC019-18 May 2008 Revision 18, supersedes and replaces MK-92HC019-17

(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 Gives an overview of the Device Manager agent and describes its system requirements.

Installing the Device Manager

Agent Explains the procedures for installing and setting up the Device Manager agent.

Operating the Device

Manager Agent Provides notes on how to manage host operations and explains how to set up and operate the Device Manager agent.

Contents of a Configuration Definition File Supported by Device Manager

Describes the contents of the CCI configuration definition files when you use these definition files in Device Manager.

Troubleshooting Describes how to troubleshoot problems with the Storage Navigator.

Acronyms and Abbreviations Defines the acronyms and abbreviations used in this document.

(11)

Referenced Documents

The following Hitachi referenced documents are also available for download on the Hitachi Data Systems Support Portal:

https://extranet.hds.com/http:/aim.hds.com/portal/dt 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:

(12)

Document Conventions

This document uses the following typographic conventions:

Convention Description

Bold Indicates text on a window, other than the window title, including menus, menu options, buttons, fields, and labels. Example: Click OK.

Italic 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. screen/code 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 Provides helpful information, guidelines, or suggestions for performing tasks more effectively.

Caution Warns the user of adverse conditions and/or consequences (e.g., disruptive operations).

WARNING Warns the user of severe conditions and/or consequences (e.g., destructive operations).

(13)

Convention for Storage Capacity Values

Storage capacity values for logical devices are calculated based on the following values:

1 KB (kilobyte) = 1024 bytes

1 MB (megabyte) = 1024 kilobytes or 10242_bytes 1 GB (gigabyte) = 1024 megabytes or 10243_bytes 1 TB (terabyte) = 1024 gigabytes or 10244 bytes

Getting Help

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:

http://www.hds.com/services/support/. 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).

Comments

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.

â¢

E-mail: [email protected]

â¢

Fax: 858-695-1186

â¢

Mail:

Technical Writing, M/S 35-10 Hitachi Data Systems

10277 Scripps Ranch Blvd. San Diego, CA 92131

Thank you! (All comments become the property of Hitachi Data Systems

(14)

(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

(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

(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

2003#1, #2 No SP

SP1 SP2

x86 Not applicable

IPF Runs under WOW64.We

recommend that SP2 be installed.

No SP

SP2

x64 Edition (EM64T

and AMDÂ®₆₄₎ Runs under WOW64.

Windows Server

2003 R2#1, #2 No SP

SP2

x86 Not applicable

x64 Edition (EM64T

(18)

Windows Server

2008 No SP x86 Not applicable

IPF Runs under WOW64.

x64 Edition (EM64T

and AMD64) 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 We recommend that Solaris _{Patch Cluster be installed.}

AIXÂ®_5.2₃₂_bit 64 bit Not applicable 5.3 32 bit 64 bit Not applicable 6.1 32 bit 64 bit

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 Linux AS/ES 4 Â Update 1 Â Update 3 Â Update 4 Â 4.5 Linux 5 Â 5.0 Â 5.1 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)

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.

(19)

HP-UXÂ®_11i_v1_{PA-RISC (32 and 64}

bit) Workstation is not supported. _{32-bit is not supported for} Provisioning Manager.

11i v2 PA-RISC (64bit)

IPF

Workstation is not supported.

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 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)

Windows Server

2003#1, #2 SP2 or later x86 Not applicable

x64 Edition (EM64T and

AMD64) Runs under WOW64.

Windows Server

2003 R2#1, #2 SP2 or later x86 Not applicable

AMD64) Runs under WOW64.

Windows Server

2008 No SP x86 Not applicable

(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 _{We recommend that}

Solaris Patch Cluster be installed. AIX 5.3 32 bit 64 bit Not applicable 6.1 32 bit 64 bit

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} Â 4.5 Linux 5 Â 5.0 Â 5.1 x86 x64 Edition (EM64T) Not applicable

HP-UX 11i v2 PA-RISC (64bit)

IPF

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.

(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) x64 (EM64T and AMD64) KB922772 Windows Server 2003(SP1) x86IPF KB922772 Windows Server 2003 R2(No SP) x86 KB922772 x64 (EM64T and AMD64) KB922772

(22)

Table 1.4 Required Patches for Operating Systems Supported by the Device Manager Agent (Solaris)

Solaris 8 SPARC (32 and 64 bit) Â 112396-03 SunOS 5.8: /usr/bin/fgrep patch Â 111111-07 SunOS 5.8: /usr/bin/nawk patch Â 108987-19 SunOS 5.8: Patch for patchadd and

patchrm

Â 112003-03 SunOS 5.8: Unable to load fontset in 64-bit Solaris 8 iso-1 or iso-15

Â 111310-01 SunOS 5.8: /usr/lib/libdhcpagent.so.1 patch

Â 112472-01 SunOS 5.8: Font2DTest2 abort when Lucida Sans Thai Typewriter selected

Â 111308-05 SunOS 5.8: /usr/lib/libmtmalloc.so.1 patch Â 112438-03 SunOS 5.8: /kernel/drv/random patch Â 111023-03 SunOS 5.8: /kernel/fs/mntfs and

/kernel/fs/sparcv9/mntfs patch

Â 115827-01 SunOS 5.8: /sbin/sulogin and /sbin/netstrategy patch

Â 116602-01 SunOS 5.8: /sbin/uadmin and /sbin/hostconfig patch

Â 113648-04 SunOS 5.8: mount patch Â 109147-44 SunOS 5.8: linker patch

Â 108434-22 SunOS 5.8: 32-Bit Shared library patch for C++

Â 111317-07 SunOS 5.8: /sbin/init and /usr/sbin/init patch

Â 110386-04 SunOS 5.8: RBAC Feature Patch Â 113886-48 OpenGL 1.3: OpenGL Patch for Solaris

(32-bit)

Â 113887-48 OpenGL 1.3: OpenGL Patch for Solaris (64-bit)

Â 123478-01 SunOS 5.8: fsck patch Â 119067-09 X11 6.4.1: Xsun patch

Â 108773-27 SunOS 5.8: IIIM and X Input & Output Method patch

Â 108940-76 Motif 1.2.7 and 2.1.1: Runtime library patch for Solaris 8

Â 110910-11 SunOS 5.8: /usr/lib/fs/ufs utilities patch Â 108528-29 SunOS 5.8: kernel update and Apache

patch

Â 117000-05 SunOS 5.8: Kernel Patch Â 108921-25 CDE 1.4: dtwm patch

(23)

OS Architecture Patches

Â 108989-02 SunOS 5.8: /usr/kernel/sys/acctctl and /usr/kernel/sys/exacctsys patch

Â 128624-04 SunOS 5.8: LDAP2 client, libc, libthread and libnsl libraries patch

Â 117350-53 SunOS 5.8: kernel patch

Â 109326-20 SunOS 5.8: libresolv.so.2 and in.named patch

Solaris 9 SPARC (32 and 64 bit) Â 113096-03 X11 6.6.1: OWconfig patch

Â 111711-16 SunOS 5.9: 32-bit Shared library patch for C++

Â 112963-32 SunOS 5.9: linker Patch Â 112785-63 X11 6.6.1: Xsun patch

Solaris 10 SPARC (32 and 64 bit) Â 120900-04 SunOS 5.10: libzonecfg Patch Â 121133-02 SunOS 5.10: zones library and zones

utility patch

Â 119254-52 SunOS 5.10: Install and Patch Utilities Patch

Â 118918-24 SunOS 5.10: Solaris Crypto Framework patch

Â 119042-10 SunOS 5.10: svccfg & svcprop patch Â 119578-30 SunOS 5.10: FMA Patch

Â 118833-36 SunOS 5.10: kernel patch

x64 Edition (AMD64) Â 120901-03 SunOS 5.10_x86: libzonecfg patch Â 121334-04 SunOS 5.10_x86: zoneadmd, zlogin and

zoneadm patch

Â 119255-50 SunOS 5.10_x86: Install and Patch Utilities Patch

Â 119255-34 Obsoleted by: 119255-35 SunOS 5.10_x86: Install and Patch Utilities Patch Â 126420-01 SunOS 5.10_x86: umountall patch Â 117435-02 SunOS 5.10_x86: biosdev patch Â 118344-14 SunOS 5.10_x86: Fault Manager Patch Â 121264-01 SunOS 5.10_x86: cadp160 driver patch Â 119964-08 SunOS 5.10_x86: Shared library patch for

C++_x86

Â 113000-07 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

(24)

Table 1.5 Required Patches for Operating Systems Supported by the Device Manager Agent (AIX)

AIX 5.2 32 bit 64 bit

When using Java program version 1.4.2: 5200-06 (APAR IY67913)

When using Java program version 5.0: 5200-07 (APAR IY67914)

AIX 5.3 32 bit 64 bit

When using Java program version 1.4.2 5300-02 (APAR IY69190)

When using Java program version 5.0: 5300-03 (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 x86 x64 Edition (EM64T) gdb-5.3.90-0.20030710.40.i386.rpm IPF gdb-5.3.90-0.20030710.40.i386.rpm gdb-5.3.90-0.20030710.40.ia64.rpm SUSE LINUX Enterprise Server 10 x86 gdb-6.5-21.2 or later

(25)

Table 1.7 Required Patches for Operating Systems Supported by the Device Manager Agent (HP-UX)

HP-UX 11i v1 PA-RISC (32 and 64

bit) Â PHNE_23502 s700_800 11.11 ONC/NFS General Release/Performance Patch Â PHKL_24253 s700_800 11.11 thread nostop patch

supporting NFS

Â PHKL_24254 s700_800 11.11 thread nostop patch supporting NFS

Â PHKL_24256 s700_800 11.11 signal race condition patch/threads enh

Â PHKL_24751 s700_800 11.11 preserve IPSW W-bit and GR31 lower bits

Â PHSS_24932 s700_800 11.11 Japanese TrueType font patch

Â PHSS_24934 s700_800 11.11 Korean TrueType font patch

Â PHSS_24936 s700_800 11.11 Chinese-S TrueType font patch for 11.11

Â PHNE_25084 s700_800 11.11 Cumulative STREAMS Patch

Â PHCO_25226 s700_800 11.11 Initialized TLS, Psets, Mutex performance

Â PHKL_25227 s700_800 11.11 VM/JFS deadlock; mmap performance/defect

Â PHKL_25367 s700_800 11.11 Priority inversion and thread hang

Â PHSS_25449 s700_800 11.11 X/Motif Runtime OCT2001 Periodic Patch

Â PHCO_25452 s700_800 11.11 libc cumulative patch Â PHKL_25468 s700_800 11.11 eventport (/dev/poll)

pseudo driver

Â PHKL_25614 s700_800 11.11 VM-JFS deadlock, mmap, perf thread creation

Â PHKL_25728 s700_800 11.11 Psets Enablement, thread cumulative

Â PHKL_25729 s700_800 11.11 signals, threads enhancement, Psets Enablement

Â PHKL_25840 s700_800 11.11 Thread NOSTOP, Psets, Thread Abort

(26)

OS Architecture Patches

Â PHKL_25871 s700_800 11.11 eventport syscalls;socket close(2) hang fix

Â PHSS_25881 s700_800 11.11 X/Motif Runtime JAN2002 Periodic Patch

Â PHKL_27091 s700_800 11.11 Core PM, vPar, Psets Cumulative, slpq1 perf

Â PHKL_27092 s700_800 11.11 Thread NOSTOP, Abort; Psets

Â PHKL_28489 s700_800 11.11 copyin EFAULT, LDCD access type

Â PHNE_29887 s700_800 11.11 cumulative ARPA Transport patch

Â PHCO_29960 s700_800 11.11 Pthread enhancement and fixes

Â PHSS_30049 s700_800 11.11 ld(1) and linker tools cumulative patch

Â PHKL_32457 s700_800 11.11 SPP fragmentation;AIO;EVP;ufalloc;dup2 race

Â PHKL_32927 s700_800 11.11 PA-8800 Fix Java (64-bit JVM) process hang

Â PHKL_34534 s700_800 11.11 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_800 11.23 ksleep cumulative patch IPF When using Java program version 1.4.2:

Â PHSS_30015 s700_800 11.23 Aries cumulative patch Â PHKL_30192 s700_800 11.23 Eliminate race at MxN

kernel thread creation

Â PHCO_30476 s700_800 11.23 Pthread library patch Â PHSS_34201 s700_800 11.23 Aries cumulative patch When using Java program version 5.0:

Â PHSS_30015 s700_800 11.23 Aries cumulative patch Â PHKL_30192 s700_800 11.23 Eliminate race at MxN

kernel thread creation

Â PHCO_30476 s700_800 11.23 Pthread library patch Â PHSS_33349 s700_800 11.23 linker + fdp cumulative

patch

Â PHSS_33350 s700_800 11.23 aC++ Runtime

Â PHSS_34043 s700_800 11.23 Integrity Unwind Library Â PHSS_34201 s700_800 11.23 Aries cumulative patch Â PHKL_35029 s700_800 11.23 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

(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.

(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 AMD64 JDK 5.0 (Update 11 or later)

The JRE bundled with the OS

AIX 32 bit

64 bit

For IPv4 environment operation: JDK 1.4.2 (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

(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 1.4.2 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 1.4.2 pkginfo -li SUNWj3rt

AIX JDK 5.0 (32 bit) lslpp -l Java5.sdk

JDK 5.0 (64 bit) lslpp -l Java5_64.sdk

JDK 1.4.2 (32 bit) lslpp -l Java14.sdk

JDK 1.4.2 (64 bit) lslpp -l Java14_64.sdk

HP-UX JDK 5.0 swlist Java15JDK

JRE 5.0 swlist Java15JRE

JDK 1.4.2 swlist T1456AA

(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 Standard OS file system.

Provisioning Manager only allows the file system to be displayed.

FAT32 Standard OS file system.

(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 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.

SUSE LINUX

Enterprise Server ext2 _ext3 Standard OS file system. _{Provisioning Manager is not supported on SUSE LINUX} Enterprise Server.

(32)

OS File System Description

HP-UX Veritas File System

(JFS#₎

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 2002.

Â 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.

HFS Standard OS file system.

#: 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 5.1.0 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 5.1.0 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.

(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

Basic#1

(34)

OS Version Architecture Volume Manager Windows Server 2003 SP2 x86 IPF x64 Edition (EM64T and AMD64)

Dynamic

When Provisioning Manager is also used: Basic#1 Dynamic Windows Server 2003 R2 No SP _SP2 x86 _{x64 Edition} (EM64T and AMD64)

Dynamic

When Provisioning Manager is also used: Basic#1 Dynamic Windows Server 2008 No SP x86 IPF x64 Edition (EM64T and AMD64)

Dynamic

Basic#1

Dynamic

Solaris 8 SPARC (32 or

64 bit) When Device Manager is used: _{SDS 4.2.1} VERITAS Volume Manager 3.2 VERITAS Volume Manager 3.5 VERITAS Volume Manager 4.0 When Provisioning Manager is also used#2_:

SDS 4.2.1

VERITAS Volume Manager 3.5 VERITAS Volume Manager 4.0

9 SPARC (32 or

64 bit) 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 5.0

(35)

OS Version Architecture Volume Manager

Solaris 10 SPARC (32 or

64 bit) 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

10 x64 Edition

(AMD64) 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 5.2

5.3 6.1

32 bit 64 bit

When Device Manager is used: LVM

LVM Red Hat Enterprise

Linux Linux AS/ES 3 x86 _IPF x64 Edition (EM64T)

When Provisioning Manager is also used: LVM Linux AS/ES 4 x86 IPF x64 Edition (EM64T)

When Device Manager is used: LVM2

When Provisioning Manager is also used: LVM2 Linux 5 x86 IPF x64 Edition (EM64T)

When Device Manager is used: LVM2

LVM2 SUSE LINUX Enterprise

Server 9 x86 When Device Manager is used: _LVM2

Unsupported

10 x86 When Device Manager is used:

LVM2

(36)

OS Version Architecture Volume Manager

HP-UX 11i v1 PA-RISC (32

bit) When Device Manager is used: _LVM VERITAS Volume Manager 3.5 When Provisioning Manager is also used:

Unsupported

11i v1 PA-RISC (64

bit) 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) PA-RISC (64 bit) IPF

VERITAS Volume Manager 3.5 VERITAS Volume Manager 4.1 When Provisioning Manager is also used:

LVM

11i v2 (for versions later than or equal to 12/2005) PA-RISC (64 bit) IPF

VERITAS Volume Manager 3.5 VERITAS Volume Manager 4.1 When Provisioning Manager is also used:

LVM

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

(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.

(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.

(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

Dynamic Link Manager 05-01-/A to 6.0.0 When Provisioning Manager is also used:

Dynamic Link Manager 05-02 to 6.0.0 Windows Server 2003 No SP x86

IPF

When Device Manager is used:

Dynamic Link Manager 05-01 to 6.0.0 When Provisioning Manager is also used: Dynamic Link Manager 05-02 to 6.0.0 x64 Edition

(EM64T and AMD64)

When Device Manager is used: Dynamic Link Manager 5.7 to 6.0.0 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 6.0.0

SP1 x86

IPF

Dynamic Link Manager 05-60 to 6.0.0 SP2 x86 When Device Manager is used:

Dynamic Link Manager 5.9.1 to 6.0.0 Windows MPIO (MPIO DSM: Provided by Dynamic Link Manager 5.9.1 or later) When Provisioning Manager is also used:

Dynamic Link Manager 5.9.1 to 6.0.0 IPF When Device Manager is used:

Dynamic Link Manager 5.6 to 6.0.0 Windows MPIO (MPIO DSM: Provided by Dynamic Link Manager 5.9.1 or later) When Provisioning Manager is also used:

(40)

OS Version Architecture Path Management Software

Windows Server 2003 SP2 x64 Edition (EM64T and AMD64)

Dynamic Link Manager 5.9.1 to 6.0.0 Windows Server 2003

R2 No SP x86 _{x64 Edition} (EM64T and AMD64)

Dynamic Link Manager 5.8 to 6.0.0

SP2 x86

x64 Edition (EM64T and AMD64)

Dynamic Link Manager 5.9.1 to 6.0.0 Windows Server 2008 No SP x86

x64 Edition (EM64T and AMD64) IPF

Dynamic Link Manager 5.9.5 to 6.0.0 Windows MPIO (MPIO DSM: Provided by Dynamic Link Manager 5.9.5 or later)

Solaris 8 SPARC (32 and

64 bit) When Device Manager is used: _{Dynamic Link Manager 03-00} Dynamic Link Manager 03-02

Dynamic Link Manager 04-00 to 6.0.0 When Provisioning Manager is also used (VERITAS Volume Manager 3.5 is used):

Dynamic Link Manager 04-01/B Dynamic Link Manager 05-02 to 6.0.0 When Provisioning Manager is also used (VERITAS Volume Manager 4.0 is used):

(41)

OS Version Architecture Path Management Software

Solaris 9 SPARC (32 and

64 bit) When Device Manager is used: _{VERITAS Volume Manager 4.1 (Dynamic} Multi-Pathing)

Dynamic Link Manager 04-01 to 6.0.0 Sun StorEdge Traffic Manager 6.2.6 When Provisioning Manager is also used: (VERITAS Volume Manager 3.5 is used)

Dynamic Link Manager 04-01/B Dynamic Link Manager 05-02 to 6.0.0 When Provisioning Manager is also used: (VERITAS Volume Manager 4.0 is used)

Dynamic Link Manager 05-41 to 6.0.0

10 SPARC (32 and

64 bit) When Device Manager is used: _{Dynamic Link Manager 5.6.1 to 6.0.0} Sun StorEdge Traffic Manager When Provisioning Manager is also used:

Unsupported x64 Edition

(AMD64) When Device Manager is used: _{Sun StorEdge Traffic Manager} When Provisioning Manager is also used:

Unsupported

AIX 5.2 32 bit

64 bit

Dynamic Link Manager 05-00 to 6.0.0 MPIO

When Provisioning Manager is also used: Dynamic Link Manager 05-02 to 6.0.0

5.3 32 bit

64 bit

Dynamic Link Manager 05-41 to 6.0.0 MPIO

When Provisioning Manager is also used: Dynamic Link Manager 05-41 to 6.0.0

6.1 32 bit

64 bit

Dynamic Link Manager 5.9.4 to 6.0.0 When Provisioning Manager is also used:

Dynamic Link Manager 5.9.4 to 6.0.0 Red Hat Enterprise

Linux Linux AS/ES 3 Update 3

x86 When Device Manager is used: Dynamic Link Manager 5.4 to 5.9.4 When Provisioning Manager is also used:

Dynamic Link Manager 5.4 to 5.9.4 When Provisioning Manager is also used:

(42)

OS Version Architecture Path Management Software

Red Hat Enterprise

Linux Linux AS/ES 3 Update 3

x64 Edition

(EM64T) When Device Manager is used: _{Dynamic Link Manager 5.6.2 to 5.9.4} When Provisioning Manager is also used:

Unsupported Linux AS/ES 3 Update 4

Dynamic Link Manager 5.6 to 5.9.4 IPF When Device Manager is used:

Unsupported Linux

AS/ES Update 6

Unsupported Linux AS/ES 4 Update 1 x86 IPF

Dynamic Link Manager 5.7.0-02 to 6.0.0 When Provisioning Manager is also used:

Dynamic Link Manager 5.7.0-02 to 6.0.0 x64 Edition

Dynamic Link Manager5.7.0-02 to 6.0.0 Linux AS/ES 4 Update 3 x86 IPF x64 Edition (EM64T)

(43)

OS Version Architecture Path Management Software

Red Hat Enterprise

Linux Linux AS/ES 4 Update 4 x86 IPF x64 Edition (EM64T)

Dynamic Link Manager 5.9.1 to 6.0.0 Linux AS/ES 4.5 x86 IPF x64 Edition (EM64T)

Dynamic Link Manager 5.9.3 to 6.0.0

Linux 5 x86

IPF x64 Edition (EM64T)

Dynamic Link Manager 5.9.3 to 6.0.0 Linux

5.1 x86 _IPF x64 Edition (EM64T)

Dynamic Link Manager 5.9.4 to 6.0.0 SUSE LINUX

Enterprise Server 9 x86 When Device Manager is used: _{Dynamic Link Manager 5.7 to 6.0.0} When Provisioning Manager is also used:

Unsupported

10 x86 When Device Manager is used: Dynamic Link Manager 5.9 to 6.0.0 When Provisioning Manager is also used:

Unsupported

HP-UX 11i v1 PA-RISC (32bit) When Device Manager is used: PV-link

When Provisioning Manager is also used: Unsupported

PA-RISC (64bit) When Device Manager is used: PV-link

Dynamic Link Manager 04-00 to 6.0.0 When Provisioning Manager is also used:

PV-link

Dynamic Link Manager 5.6.1 to 6.0.0

IPF

When Device Manager is used: PV-link

PV-link

(44)

OS Version Architecture Path Management Software

HP-UX 11i v3 PA-RISC (64bit)

IPF

When Device Manager is used: PV-link

MPIO

When Provisioning Manager is also used: PV-link

MPIO

Note: You can use Provisioning Manager to configure host settings for LUs

managed by PV-link only if Dynamic Link Manager is not installed. If Dynamic Link Manager is installed, you can view information, but cannot perform host setting operations.

Supported Cluster Software

When cluster software is installed, hosts on which Device Manager agent is also installed can be clustered in an Active-Standby configuration or

Active-Active configuration. The Device Manager agent runs in cluster environments configured with the cluster software listed in the table below. Note that the table only lists OSs that support cluster software.

Note:

Because the Device Manager agent is not compatible with the logical host, the Device Manager agent cannot be registered in cluster resources. The Device Manager agent is activated on the physical hosts that make up the cluster, and collects the data for those hosts.

Cluster software cannot be set up from Provisioning Manager. When you use file systems and device files created by using Provisioning Manager as cluster resources, or when you use a host setting function of Provisioning Manager to operate file systems or device files, set up the cluster software manually.

For details about setting up the cluster software, see the manual for each cluster software product.

(45)

Table 1.13 Cluster Software Supported by the Device Manager Agent

OS Version Architecture Cluster Software

Microsoft Cluster Service When Provisioning Manager is also used:

Microsoft Cluster Service Windows Server 2003 No SP x86 When Device Manager is used:

Microsoft Cluster Service VERITAS Cluster Service 4.1 When Provisioning Manager is also used:

Microsoft Cluster Service IPF When Device Manager is used:

Microsoft Cluster Service x64 Edition

(EM64T and AMD64)

When Device Manager is used: Microsoft Cluster Service When Provisioning Manager is also used:

Microsoft Cluster Service

SP1 x86 When Device Manager is used:

Microsoft Cluster Service VERITAS Cluster Service 4.1 VERITAS Cluster Service 4.3 When Provisioning Manager is also used:

Microsoft Cluster Service IPF When Device Manager is used:

Microsoft Cluster Service Windows Server 2003

R2 No SP x86 When Device Manager is used: _{Microsoft Cluster Service} When Provisioning Manager is also used:

Microsoft Cluster Service x64 Edition

(EM64T and AMD64)

When Device Manager is used: Microsoft Cluster Service When Provisioning Manager is also used:

(46)

OS Version Architecture Cluster Software

Solaris 8 SPARC (32

and 64 bit) When Device Manager is used: _{Sun Cluster 3.0} Sun Cluster 3.1

VERITAS Cluster Service 1.3 VERITAS Cluster Service 2.0 VERITAS Cluster Service 3.5 When Provisioning Manager is also used:

VERITAS Cluster Service 3.5

9 SPARC (32

and 64 bit) When Device Manager is used: _{Sun Cluster 3.1} VERITAS Cluster Service 3.5 VERITAS Cluster Service 4.0 VERITAS Cluster Service 4.1 Cluster Perfect 4.1

VERITAS Cluster Service 3.5 VERITAS Cluster Service 4.0

10 SPARC (32

and 64 bit) When Device Manager is used: _{Sun Cluster 3.1} VERITAS Cluster Service 4.1 PRIMECLUSTER 4.1.4#1, #2

Sun Cluster 3.1

VERITAS Cluster Service 4.1

AIX 5.2 32 bit

64 bit

When Device Manager is used: HACMPÂ®_5.1

Unsupported

5.3 32 bit When Device Manager is used: HACMP 5.2

HACMP 5.2

64 bit When Device Manager is used: HACMP 5.2

HACMP 5.3

(47)

OS Version Architecture Cluster Software

Red Hat Enterprise

Linux Linux AS/ES 4 _{Update 1} x86 When Device Manager is used: _{VERITAS Cluster Service 4.1} When Provisioning Manager is also used:

Unsupported Linux AS/ES 4

Update 4

IPF When Device Manager is used: PRIMECLUSTER 4.2#1

Unsupported

HP-UX 11i v1 PA-RISC (32

bit) When Device Manager is used: _{Serviceguard A11.16} When Provisioning Manager is also used:

Unsupported PA-RISC (64

bit) When Device Manager is used: _{MC/Service Guard 11.15} Serviceguard A11.16

Serviceguard A11.16

11i v2 PA-RISC (64

bit) IPF

When Device Manager is used: Serviceguard A11.16 Serviceguard A11.17

When Provisioning Manager is also used: Serviceguard A11.16 Serviceguard A11.17 11i v3 PA-RISC (64 bit) IPF

When Device Manager is used: Serviceguard A11.17

Serviceguard A11.17 #1: File systems created with GDS are not supported.

(48)

Supported SAN Environments

This section explains the system requirements for SAN environments that are supported by Device Manager agents.

Caution:

Before you connect the host with storage subsystems via FC-HUB (or

FC-SWITCH), confirm whether FC-HUB (or FC-SWITCH) and its firmware are available for the storage subsystem:

â¢ Check the corresponding HBA model. See Supported Host Bus Adapter Model.

â¢ Check the FC-HUB (and firmware) supported by the target storage subsystems. Refer to the appropriate documentation for your storage subsystem.

Supported Storage Subsystems

These storage subsystem models are supported by the Device Manager agent:

â¢

Universal Storage Platform V/VM

â¢

Hitachi USP

â¢

Lightning 9900V

â¢

Lightning 9900

â¢

Hitachi SMS

â¢

Hitachi AMS/WMS

â¢

Thunder 9500V

â¢

Thunder 9200

If a host in which the Device Manager agent is installed is connected to a Hitachi storage subsystem