HiCommand Suite

Product Version

Document Organization

Getting Help

FASTFIND LINKS

Contents

Hitachi Command Suite SoftwareInstallation and Configuration Guide

MK-90HC173-05

Hitachi Command Suite Installation and Configuration Guide

ii

© 2010-2011 Hitachi, Ltd., Hitachi Data Systems Corporation. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd. (hereinafter referred to as “Hitachi”) and Hitachi Data Systems Corporation (hereinafter referred to as “Hitachi Data Systems”).

Hitachi and Hitachi Data Systems reserve the right to make changes to this document at any time without notice and assume no responsibility for its use. This document contains the most current information available at the time of publication. When new or revised information becomes available, this entire document will be updated and distributed to all registered users.

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.

Notice: Hitachi Data Systems products and services can be ordered only under the terms and conditions of Hitachi Data Systems’ applicable agreements. The use of Hitachi Data Systems products is governed by the terms of your agreements with Hitachi Data Systems.

By using this software, you agree that you are responsible for:

a) Acquiring the relevant consents as may be required under local privacy laws or otherwise from employees and other individuals to access relevant data; and

b) Ensuring that data continues to be held, retrieved, deleted or otherwise processed in accordance with relevant laws.

Hitachi is a registered trademark of Hitachi, Ltd. in the United States and other countries. Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd. in the United States and other countries.

ShadowImage is a registered trademark of Hitachi Data Systems.

Microsoft product screen shots reprinted with permission from Microsoft Corporation.

All other trademarks, service marks, and company names are properties of their respective owners.

iiiHitachi Command Suite Installation and Configuration Guide

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiIntended audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiiProduct version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiiRelease notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiiDocument revision level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiiDocument organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiiReferenced documents and additional resources. . . . . . . . . . . . . . . . . . . . . . . . ixDocument conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixConvention for storage capacity values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xGetting help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiComments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Basic system configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Prerequisites for basic configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Prerequisites for DVD installations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

2 Hitachi Command Suite server installation . . . . . . . . . . . . . . . . . . 2-1Planning for server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Verifying server installation conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Prerequisites for server installation locations (new installations only) . . . . . 2-3Prerequisites for database file storage locations (new installations only) . . . 2-4Prerequisites for management server information . . . . . . . . . . . . . . . . . . . 2-5Determining memory heap size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Prerequisites for database file backups or export locations. . . . . . . . . . . . . 2-7

HCS server installation prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Avoiding port conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9Determining management server readiness (Solaris or Linux) . . . . . . . . . . 2-9Setting kernel parameters and shell restrictions (Solaris or Linux). . . . . . . 2-10

Recommended Solaris 9 /etc/system values . . . . . . . . . . . . . . . . . . . . 2-10Recommended Solaris 10 /etc/project values . . . . . . . . . . . . . . . . . . . 2-13


iv

Recommended Solaris 10 /etc/system values . . . . . . . . . . . . . . . . . . . 2-15Recommended Red Hat Enterprise Linux /etc/sysctl.conf values. . . . . . 2-17Recommended Red Hat Enterprise Linux /etc/security/limits.conf values 2-19Recommended SUSE Linux Enterprise Server /etc/sysctl.conf values. . . 2-20Recommended SUSE Linux Enterprise Server /etc/security/limits.conf values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

Modifying kernel parameter values and shell restrictions . . . . . . . . . . . 2-23Registering firewall exceptions (Linux). . . . . . . . . . . . . . . . . . . . . . . . . . 2-24

HCS server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24Server installation prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24Installing HCS in a Windows environment . . . . . . . . . . . . . . . . . . . . . . . 2-25Installing HCS in a Solaris or Linux environment . . . . . . . . . . . . . . . . . . . 2-26

Post-installation tasks (new installation) . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26Verifying the installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27Registering licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27Changing the system account password . . . . . . . . . . . . . . . . . . . . . . . . 2-27Creating user accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28User permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29Built-in user groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30

About post-installation tasks (overwrite or upgrade) . . . . . . . . . . . . . . . . . . . 2-30Performing post-installation tasks (overwrite or upgrade) . . . . . . . . . . . . 2-31Backing up databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32Refreshing storage systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32Refreshing virtualization server information . . . . . . . . . . . . . . . . . . . . . . 2-33Resetting user accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33Resetting roles and permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33Using event notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36Updating property files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37Synchronizing databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37

3 Agent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Planning for Device Manager agent installation . . . . . . . . . . . . . . . . . . . . . . . 3-2

Prerequisites for agent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Prerequisites for agent installations with add-ons . . . . . . . . . . . . . . . . . . . 3-3Prerequisites for agent installation locations. . . . . . . . . . . . . . . . . . . . . . . 3-4Modifying agent services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Prerequisites for verifying server information . . . . . . . . . . . . . . . . . . . . . . 3-4About HiScan command execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Prerequisites for identifying CCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Agent installation prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6General prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6Windows prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Solaris prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Removing HDSHiScan packages when using Solaris . . . . . . . . . . . . . . . . . 3-9Removing agents when using Solaris 10 . . . . . . . . . . . . . . . . . . . . . . . . 3-10

vHitachi Command Suite Installation and Configuration Guide

AIX prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10Removing HDSHiScan packages when using AIX. . . . . . . . . . . . . . . . . . . 3-11Linux prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11Allowing communication with Linux firewalls . . . . . . . . . . . . . . . . . . . . . 3-12HP-UX prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12Removing HDSHiScan packages when using HP-UX. . . . . . . . . . . . . . . . . 3-13

Installing agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14Installing the Device Manager agent on a Windows host . . . . . . . . . . . . . 3-14Installing the Device Manager agent on a UNIX host . . . . . . . . . . . . . . . . 3-15

Device Manager agent post-installation tasks . . . . . . . . . . . . . . . . . . . . . . . . 3-15Modifying Device Manager agent properties . . . . . . . . . . . . . . . . . . . . . . 3-16Resetting the service execution user (Windows) . . . . . . . . . . . . . . . . . . . 3-16Registering firewall exceptions (Windows) . . . . . . . . . . . . . . . . . . . . . . . 3-17

4 Removing HCS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Removing HCS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Prerequisites for removing HCS server . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Removing HCS from a Windows host . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Removing HCS from a Solaris or Linux host . . . . . . . . . . . . . . . . . . . . . . . 4-3

Removing a Device Manager agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Prerequisites for removing Device Manager agents . . . . . . . . . . . . . . . . . . 4-3Removing Device Manager agents from Windows hosts. . . . . . . . . . . . . . . 4-4Removing Device Manager agents from UNIX hosts . . . . . . . . . . . . . . . . . 4-5

A Performing unattended installation and removal . . . . . . . . . . . . . . A-1Performing an HCS server unattended installation. . . . . . . . . . . . . . . . . . . . . . A-2

HCS server unattended installation properties and settings . . . . . . . . . . . . A-2Prerequisites for HCS server unattended installation . . . . . . . . . . . . . . . . . A-4Installing the server in a Windows environment (unattended installation) . . A-5Installing the server in a Solaris or Linux environment (unattended installation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6

Performing a Device Manager agent unattended installation . . . . . . . . . . . . . . A-7Prerequisites for Device Manager agent unattended installations . . . . . . . . A-7Installing a Device Manager agent on a Windows host (unattended installation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9

Installing a Device Manager agent on a UNIX host (unattended installation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10

Verifying Device Manager agent unattended installations . . . . . . . . . . . . . A-11Performing a Device Manager agent unattended removal . . . . . . . . . . . . . . . A-13

Removing a Device Manager agent from a Windows host (unattended removal) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13

Removing a Device Manager agent from a UNIX host (unattended removal) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14

Verifying the Device Manager agent unattended removal. . . . . . . . . . . . . A-14


vi

B Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1HCS server ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

Glossary

Index

Preface viiHitachi Command Suite Installation and Configuration Guide

Preface

This manual provides information about installing and removing Hitachi Command Suite (HCS).

Notice: The use of the features and/or products described in this manual and all other Hitachi Data Systems products is governed by the terms of your agreements with Hitachi Data Systems.

□ Intended audience

□ Product version

□ Release notes

□ Document revision level

□ Document organization

□ Referenced documents and additional resources

□ Document conventions

□ Convention for storage capacity values

□ Getting help

□ Comments


viii Preface

Intended audienceThis document provides instructions for storage administrators.

Product versionThis document revision applies to HCS version 7.2 or later.

Release notesRelease 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

Document organizationThe 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.

Revision Date Description

MK-90HC173-00 October 2010 Initial release.

MK-90HC173-01 October 2010 Revision 1, supersedes and replaces MK-90HC173-00

MK-90HC173-02 January 2011 Revision 2, supersedes and replaces MK-90HC173-01

MK-90HC173-03 May 2011 Revision 3, supersedes and replaces MK-90HC173-02

MK-90HC173-04 August 2011 Revision 4, supersedes and replaces MK-90HC173-03

MK-90HC173-05 November 2011 Revision 5, supersedes and replaces MK-90HC173-04

Chapter Description

Overview on page 1-1 Describes HCS configuration and the installation DVD.

Hitachi Command Suite server installation on page 2-1

Provides prerequisites and procedures for installing HCS.

Agent installation on page 3-1 Provides prerequisites and procedures for installing the Device Manager agent.

Removing HCS on page 4-1 Provides prerequisites and procedures for removing HCS components.

Performing unattended installation and removal on page A-1

Provides prerequisites and procedures for unattended installation and removal of the HCS server and Device Manager agent.

Ports on page B-1 Describes the ports for HCS.

Preface ixHitachi Command Suite Installation and Configuration Guide

Referenced documents and additional resourcesThe following Hitachi referenced documents can be found on the applicable Hitachi documentation CD:

• Hitachi Command Suite User Guide, MK-90HC172

• Hitachi Command Suite Configuration Reference Guide, MK-90HC175

• Hitachi Command Suite CLI Reference Guide, MK-90HC176

• Hitachi Command Suite Tiered Storage Manager CLI Reference Guide, MK-90HC177

• Hitachi Command Suite Messages Guide, MK-90HC178

• Hitachi Command Suite Mainframe Agent Installation and Configuration Guide, MK-90HC130

• Hitachi Command Suite Plug-in for Virtualization Server Provisioning User Guide, MK-91HC199

• Hitachi Command Suite Replication Manager Configuration Guide, MK-98HC151

• Hitachi Command Suite Replication Manager User Guide, MK-99HC166

• Hitachi Command Suite Replication Manager Application Agent CLI Reference Guide, MK-90HC181

• Hitachi Command Suite Replication Manager Application Agent CLI User Guide, MK-90HC189

Document conventionsThis 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.


x Preface

This document uses the following icons to draw attention to information:

Convention for storage capacity valuesPhysical storage capacity values (e.g., drive capacity) are calculated based on the following values:

Logical storage capacity values (e.g., logical device capacity) are calculated based on the following values:

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

Convention Description

Icon Label Description

Note Notes emphasize or supplement important points of the main text.

Caution Cautions indicate that failure to take a specified action could result in damage to the software or hardware.

Physical capacity unit Value

1 kilobyte (KB) 1,000 (103) bytes

1 megabyte (MB) 1,000 KB or 1,0002 bytes

1 gigabyte (GB) 1,000 MB or 1,0003 bytes

1 terabyte (TB) 1,000 GB or 1,0004 bytes

1 petabyte (PB) 1,000 TB or 1,0005 bytes

1 exabyte (EB) 1,000 PB or 1,0006 bytes

Logical capacity unit Value

1 block 512 bytes

1 KB 1,024 (210) bytes

1 MB 1,024 KB or 1,0242 bytes

1 GB 1,024 MB or 1,0243 bytes

1 TB 1,024 GB or 1,0244 bytes

1 PB 1,024 TB or 1,0245 bytes

1 EB 1,024 PB or 1,0246 bytes

Preface xiHitachi Command Suite Installation and Configuration Guide

Getting helpThe Hitachi Data Systems customer support staff is available 24 hours a day, seven days a week. If you need technical support, log on to the Hitachi Data Systems Portal for contact information: https://hdssupport.hds.com

CommentsPlease send us your comments on this document: [email protected]. Include the document title, number, and revision, and refer to specific sections and paragraphs whenever possible. All comments become the property of Hitachi Data Systems Corporation. Thank you!

https://hdssupport.hds.com


xii Preface

1

Overview 1–1Hitachi Command Suite Installation and Configuration Guide

Overview

This chapter provides basic system configuration information for Hitachi Command Suite (HCS).

□ Basic system configuration

□ Prerequisites for basic configurations

□ Prerequisites for DVD installations


1–2 Overview

Basic system configurationHitachi Command Suite (HCS) can manage different storage systems. A basic configuration must include a management server and appropriate components.

Figure 1-1 Hitachi Command Suite: Basic configuration on page 1-2 shows a basic system configuration.

You use HCS through a management client (either the Web client GUI or the Device Manager and Tiered Storage Manager CLI) from which you can operate HCS, Tiered Storage Manager, and Replication Manager.

The management server (where HCS is installed) centrally manages the storage systems and hosts.

HCS consists of the following components, which are always installed or removed together on the management server:

• Hitachi Command Suite Common Component

Provides user account management, security monitoring, and other functions common to all HCS products.

• Device Manager server

Figure 1-1 Hitachi Command Suite: Basic configuration


The component used by HCS to manage storage system volumes.

• Tiered Storage Manager server

The component used by Tiered Storage Manager to manage storage system volume migration.

• Replication Manager server

The component used by Replication Manager to manage storage system volume replication.

• Host Data Collector

The component used to collect information about the volumes used by the hosts.

The pair management server centrally manages copy pair status and configuration. The following components are installed on the pair management server:

• Device Manager agent

Collects hosts and storage system information.

• Command Controller Interface (CCI)

Controls storage system copy pairs.

The management server accesses the management clients and storage systems over a TCP/IP network. Hosts (application servers) access the volumes in storage systems that are managed by HCS over a Storage Area Network (SAN) or an IP-SAN.

Prerequisites for basic configurationsHitachi Command Suite (HCS) can manage different types of storage systems.

The information in this manual assumes the following system configuration:

• HCS (and Common Component) are used to manage user accounts.

• The system is not linked to an external authentication server.

• For the management server:

Only one management server is configured.

The management server is not part of a cluster configuration.

The management server and management client communicate with each other using non-SSL protocol.

• For copy pair management:

HCS is configured for open-volume copy pair management at a single site.

Copy pairs are centrally managed from a pair management server.

• For collecting information about managed hosts:

Note: The Host Data Collector component can be installed on other servers and accessed remotely by HCS.


1–4 Overview

The Device Manager agent is installed only on the pair management server used to centrally manage copy pairs.

The Host Data Collector component is installed on the management server (from a silent installation initiated by the integrated installer).

Prerequisites for DVD installationsThe installation DVD includes the HCS installer and the programs that must be installed by storage and server administrators.

If your media is for Windows, it also includes the following files:

• Index file: DVD-drive:\Index.htm

• Readme file: DVD-drive:\Readme.txt

Programs installed by storage administrators• HCS:

Common Component

Device Manager server

Tiered Storage Manager server

Replication Manager server

Host Data Collector

• Tuning Manager server


• Device Manager agent

• Device Manager Mainframe Agent

• Replication Manager application agent

• Tuning Manager Agent for RAID

• Tuning Manager Agent for Server System

• Tuning Manager Agent for SAN Switch

• Tuning Manager Agent for Network Attached Storage

• Tuning Manager Agent for Oracle

• Tuning Manager Agent for Microsoft SQL Server

• Tuning Manager Agent for DB2

• Tuning Manager Agent for Enterprise Applications

Note: Other configurations are possible. For more information, see the Hitachi Command Suite Configuration Reference Guide and the Hitachi Command Suite Replication Manager Configuration Guide.

Note: To upgrade the Replication Manager server when it is connected to Business Continuity Manager, see the Hitachi Command Suite Replication Manager Configuration Guide.


Programs installed by server administrators• Compute Systems Manager (setup.exe file included in the Windows

installation DVD)

• Plug-in for Virtualization Server Provisioning

Note: The noted versions of the following software support an upgrade installation from the installation DVD:

• From version 5.0 or later:

Device Manager server

Tiered Storage Manager server

• From version 6.0 or later:

Replication Manager server

When using an earlier software version, upgrade to 6.x and then to 7.0 or later.


1–6 Overview

2

Hitachi Command Suite server installation 2–1Hitachi Command Suite Installation and Configuration Guide

Hitachi Command Suite serverinstallation

This module describes how to install and set up servers.

□ Planning for server installation

□ HCS server installation prerequisites

□ HCS server installation

□ Post-installation tasks (new installation)

□ About post-installation tasks (overwrite or upgrade)


2–2 Hitachi Command Suite server installation

Planning for server installationBefore you install the Hitachi Command Suite (HCS) server, verify the conditions and gather the information you need to perform the installation.

Verifying server installation conditionsBefore using the installer for the HCS server, determine the required information.

For a new installation, you need:

• The installation destination path, in the format:

For Windows: program-files-folder\HiCommand#

For Solaris or Linux: /opt/HiCommand

#: program-files-folder indicates the following location:

For Windows (x86): The folder specified in the Windows system environment variable %ProgramFiles%.

For Windows (x64): The folder specified in the Windows system environment variable %ProgramFiles(x86)%.

• The storage destination path for database files, in the format:

For Windows: installation-destination-path\database

For Solaris or Linux: /var/installation-destination-path/database

• Management server information:

Host name set for the OS or IP address

For all installations, you need:

• Memory heap size

Memory heap size for Common Component:

For Windows (x86):

Default: Medium (minimum: 256 MB, maximum: 512 MB)

Expected volume count: 8,001 or more

Expected copy pair count: 5,001 or more

For Windows (x64):

Default: Large (minimum: 512 MB, maximum: 1024 MB)


Expected copy pair count:

- Open volumes: 12,001 or more

- Mainframe volumes: 60,001 or more

Note: Hitachi recommends accepting default values when available.

Note: The expected volume and copy pair counts below are based on the default memory heap size.


For Solaris or Linux:



Expected copy pair count:

- Open volumes: 12,001 or more

- Mainframe volumes: 60,001 or more

Memory heap size for the Device Manager server:

For Windows (x86):

Default: Medium (minimum: 128 MB, maximum: 512 MB)

Expected volume count: 2,001 to 6,000

For Windows (x64):






• Destination for database file backup or export (if HCS products are already installed on the management server):

Windows: installation-destination-path\backup

Solaris or Linux: /var/installation-destination-path/backup

Related topics• HCS server installation prerequisites on page 2-8

• Installing HCS in a Windows environment on page 2-25

• Installing HCS in a Solaris or Linux environment on page 2-26

Prerequisites for server installation locations (new installations only)

You can change the default installation location for the server except when using Solaris (SPARC).

If you change the destination, ensure that the path adheres to the restrictions in Table 2-1 Server installation path requirements on page 2-3.

Table 2-1 Server installation path requirements

Condition Requirements

Absolute path length 64 bytes maximum






Prerequisites for database file storage locations (new installations only)

You can change the default database file storage destination for HCS.

If you change the destination, ensure that the absolute path and location adhere to the restrictions in Table 2-2 Database file storage path and location requirements on page 2-5.

Allowed characters Windows:

A to Z, a to z, 0 to 9, periods (.), underscores (_), left parentheses ( ( ), right parentheses ( ) ), single-byte spaces, backslashes (\), and colons (:)

Solaris or Linux:

A to Z, a to z, 0 to 9, underscores (_), and forward slashes (/)

Other conditions Windows:

• Do not include consecutive spaces.

• Do not include a period or space at the end of a folder name.

• Do not use parentheses, except when the path includes the Program Files (x86) directory.

• Do not include a symbolic link and junction for the installation folder.

• Do not specify the root of a drive as the destination.

• Windows x64: Do not specify any of the following folders as the installation destination because the product that is installed comprises 32-bit applications:

- The folder that is specified by the %ProgramFiles% environment variable or a folder under that folder

- The folder that is specified by the %CommonProgramFiles% environment variable or a folder under that folder

- The Windows-system-folder\system32 folder or a folder under that folder

Solaris or Linux:

• Do not include a path delimiter (/) at the end of the directory path.

• If Common Component has not been installed, ensure that the installation directory you specify does not contain any files or subdirectories.



Table 2-2 Database file storage path and location requirements




Prerequisites for management server informationInstall HCS on the management server. To access the management server from the Web client, include the host name or IP address in the URL.

• When specifying the host name, verify that the management server host name is 32 bytes maximum.

• When using an IP address to access a management server with multiple NICs, use the IP address for the system connected to the management client.


Absolute path length 90 bytes maximum

Allowable characters Windows:

A to Z, a through z, 0 to 9, periods (.), underscores (_), left parentheses ( ( ), right parentheses ( ) ), single-byte spaces, backslashes (\), and colons (:)

Solaris or Linux:

A to Z, a to z, 0 to 9, periods (.), underscores (_), and forward slashes (/)






• Do not specify the destination as a folder directly under a drive (such as D:\).

Windows (x64):

Do not specify any of the following folders as the installation destination because the product that is installed comprises 32-bit applications:

• The folder that is specified by the %ProgramFiles% environment variable or a folder under that folder

• The folder that is specified by the %CommonProgramFiles% environment variable or a folder under that folder

• The Windows-system-folder\system32 folder or a folder under that folder

Solaris or Linux:

Do not include a path delimiter (/) at the end of the directory path.



Related topics• Verifying server installation conditions on page 2-2

• HCS server installation prerequisites on page 2-8



Determining memory heap sizeEstimate the number of volumes and copy pairs managed by HCS (resource count) to determine the memory heap size. Set the larger required memory heap size for the volume count and the memory heap size for the copy pair count.

Use Table 2-3 Appropriate memory heap size for Common Component on page 2-6 and Table 2-4 Appropriate memory heap size for the Device Manager server on page 2-7 to determine the appropriate memory heap size.

Table 2-3 Appropriate memory heap size for Common Component

Note: When changing settings to lower values, remove and re-install HCS.

Environment Managed Resources

Memory Heap Size

Small(Min: 128 MB, Max: 256 MB)

Medium(Min: 256 MB, Max: 512 MB)

Large(Min: 512 MB, Max: 1,024 MB)

Windows (x86) Number of LDEVs per storage system

8,000 or less 8,001 or more

--

Number of all copy pairs

Open volumes only


--

Mainframe volumes only


--

Both open volumes and mainframe volumes#

40,000 or less

40,001 or more

--

OS other than Windows (x86)

Number of LDEVs per storage system

8,000 or less 8,001 to 14,000

14,001 or more

Number of all copy pairs

Open volumes only

5,000 or less 5,001 to 12,000

12,001 or more

Mainframe volumes only

5,000 or less 5,001 to 60,000

60,001 or more

Both open volumes and mainframe volumes#

40,000 or less

40,001 to 60,000

60,001 or more


Table 2-4 Appropriate memory heap size for the Device Manager server





Prerequisites for database file backups or export locationsIf HCS is already installed on the management server, create a copy of the database using the method appropriate to the installed version before performing an upgrade.

• From a version earlier than 5.5: Back up the database.

• From version 5.5 or later: Export the database.

If you plan to use a path other than the default, ensure that the new path adheres to the restrictions in Table 2-5 Database path and location requirements on page 2-7.

Table 2-5 Database path and location requirements

Legend:

-- : You cannot specify this memory heap size.

#

If you manage both open volumes and mainframe volumes, use the following formula to calculate the number of copy pairs:

number-of-open-system-copy-pairs x 6 + number-of-mainframe-system-copy-pairs

Managed Resource

Memory Heap Size



Large(Min: 128 MB,

Max: 1,024 MB)

Number of LDEVs per storage system

2,000 or less 2,001 to 6,000 6,001 or more

Environment Managed Resources

Memory Heap Size



Large(Min: 512 MB, Max: 1,024 MB)


Absolute path length Maximum 150 bytes







HCS server installation prerequisitesBefore you install HCS, note the prerequisite tasks that are common to all operating system and those that apply to specific environments.

• All systems: Ports (see Avoiding port conflicts on page 2-9)

• Solaris or Linux: Management server prerequisites (see Determining management server readiness (Solaris or Linux) on page 2-9)

• Solaris or Linux: Kernel parameter values and shell restrictions (see Setting kernel parameters and shell restrictions (Solaris or Linux) on page 2-10 and Modifying kernel parameter values and shell restrictions on page 2-23)

Allowed characters Windows:

A to Z, a through z, 0 to 9, periods (.), underscores (_), left parentheses ((), right parentheses ()), single-byte spaces, backslashes (\), and colons (:)

Solaris or Linux:

A to Z, a to z, 0 to 9, underscores (_), and forward slashes (/)






• Do not specify the destination as a folder directly under a drive (such as D:\).

In Solaris or Linux:

Do not specify a path delimiter (/) at the end of the directory path.



• Linux: Registering firewall exceptions (see Registering firewall exceptions (Linux) on page 2-24)

Related Topics:• HCS server installation on page 2-24

Avoiding port conflictsIf any of the HCS products use a port number that is also used by another product on the management server, the affected products may not operate correctly.

To avoid port conflicts, execute the netstat command and check the output for conflicts.




• HCS server ports on page B-2

Determining management server readiness (Solaris or Linux)Before installing HCS in a Solaris or Linux environment, verify that the host environment satisfies installation conditions.

To do this, write localhost and the server host name to the /etc/hosts file.



Caution: When you upgrade HCS to version 7.0 or later, storage tiers (custom tiers) that were created in versions earlier than 7.0 from search conditions that included any of the following items are removed (although the volumes themselves remain):

• Logical group

• Average array group usage

• Maximum array group usage

• SYSPLEXID/DEVN

• VOLSER

• P-VOL migration group

• P-VOL MU number



Setting kernel parameters and shell restrictions (Solaris or Linux)Before installing HCS in Solaris or Linux, set the kernel parameters. In Linux, you must also set shell restrictions.

• Set these values in the file appropriate to the operating system running on the management server:

For Solaris 9: Set values in the /etc/system file.

For Solaris 10: Set values in the /etc/project and /etc/system files.

For Linux: Set values in the /etc/sysctl.conf and /etc/security/limits.conf files.



• Modifying kernel parameter values and shell restrictions on page 2-23

Recommended Solaris 9 /etc/system values

Before installing HCS on a Solaris 9 system, set the kernel parameters in the /etc/system file.

The values for these settings depend on which of the following HCS products you are installing:

• Common Component

• Device Manager

• Tiered Storage Manager

• Replication Manager

• Tuning Manager

Table 2-6 Kernel parameter values for /etc/system (1/2) on page 2-10 and Table 2-7 Kernel parameter values for /etc/system (2/2) on page 2-11 provide the kernel parameter values you need to set. The formulas for calculating these values follow the tables.

Table 2-6 Kernel parameter values for /etc/system (1/2)

Note: Ensure that the maximum value you set for a kernel parameter does not exceed the maximum value specified by the operating system.

Kernel Parameter Installer Check value

Operating System

Initial ValueHiRDB Common

Component

msgsys:msginfo_msgmni

138 50 0 44

msgsys:msginfo_msgtql

91 40 0 15


Table 2-7 Kernel parameter values for /etc/system (2/2)

The following formulas are for calculating the kernel parameters in the /etc/system file:

semsys:seminfo_semmni

1034 10 1024 9

semsys:seminfo_semmns

7260 60 7200 80

semsys:seminfo_semmnu

1054 30 1024 0

semsys:seminfo_semume

522 10 512 0

semsys:seminfo_semmsl

153 25 128 0

semsys:seminfo_semopm

138 10 128 0

shmsys:shminfo_shmmax

490571136 8388608 200000000 13100032

shmsys:shminfo_shmmni

2100 100 2000 0

Kernel Parameter Device Manager

Tiered Storage Manager Software

Replication Manager Software

Tuning Manager Software

msgsys:msginfo_msgmni

44 0 0 12

msgsys:msginfo_msgtql

36 0 0 1205

semsys:seminfo_semmni

10 1 1 12

semsys:seminfo_semmns

122 50 50 0

semsys:seminfo_semmnu

0 0 0 0

semsys:seminfo_semume

0 0 0 0

semsys:seminfo_semmsl

0 0 0 0

semsys:seminfo_semopm

0 0 0 246

shmsys:shminfo_shmmax

327471104 50000000 100000000 966656000

shmsys:shminfo_shmmni

497 0 0 0


Operating System


Component



• For parameters other than shmsys:shminfo_shmmax:

kernel-parameter-value-to-be-set =

Max {

value-that-is-enabled-in-the-system

,

initial-value-of-the-OS

}

+ Max {

value-for-Common-Component

+ value-for-Device-Manager

+ value-for-Tiered-Storage-Manager

+ value-for-Replication-Manager

+ value-for-Tuning-Manager

,

value-for-HiRDB

}

• For shmsys:shminfo_shmmax:


Max {

Max {


,


}

,






,

value-for-HiRDB

}

Note: Max {x, y, z} indicates the maximum value among x, y, and z.


Related topics• Setting kernel parameters and shell restrictions (Solaris or Linux) on

page 2-10


Recommended Solaris 10 /etc/project values

Before installing HCS on a Solaris 10 system, set the kernel parameters for both the user.root project and the system project in the /etc/project file.



• Device Manager



• Tuning Manager

Table 2-8 Kernel parameter values for /etc/project (1/2) on page 2-13 and Table 2-9 Kernel parameter values for /etc/project (2/2) on page 2-14 show the kernel parameter values you need to set. The formulas for calculating these values follow the tables.

Table 2-8 Kernel parameter values for /etc/project (1/2)


Operating System


Component

process.max-msg-messages

8243 8192 0 15

process.max-sem-nsems

640 512 128 0

process.max-sem-ops

640 512 128 0

project.max-msg-ids

216 128 0 44

project.max-sem-ids

1152 128 1024 9

project.max-shm-ids

2128 128 2000 0

project.max-shm-memory

660390056 One-quarter of the physical memory

0 26214400



Table 2-9 Kernel parameter values for /etc/project (2/2)

The following formulas are for calculating the values for the kernel parameters:

• For parameters other than project.max-shm-memory:


Max {


,


}

+ Max {






,

value-for-HiRDB

}

• For project.max-shm-memory:


Max {


,





process.max-msg-messages

36 0 0 1205

process.max-sem-nsems

0 0 0 0

process.max-sem-ops

0 0 0 0

project.max-msg-ids

44 0 0 12

project.max-sem-ids

10 1 1 12

project.max-shm-ids

497 0 0 0

project.max-shm-memory

439023616 100695040 94457000 966656000



}

+ value-for-Common-Component






page 2-10

• Recommended Solaris 10 /etc/system values on page 2-15


Recommended Solaris 10 /etc/system values

Before installing HCS on a Solaris 10 system, set the kernel parameters in the /etc/system file.



• Device Manager



• Tuning Manager

Determine the kernel parameter values to be set in the /etc/system file by using the values calculated in Recommended Solaris 10 /etc/project values on page 2-13. Use the following formulas to calculate the values for the kernel parameters:

• For msgsys:msginfo_msgtql:

kernel-parameter-value-to-be-set = Max {

value-set-for-"process.max-msg-messages”

maximum-value-between-the-valid-values-for

-"process.max-msg-messages"-for-each-project}

• For semsys:seminfo_semmsl:


value-set-for-"process.max-sem-nsems"

Note: Max {x, y} indicates the larger value of x or y.




-"process.max-sem-nsems"-for-each-project}

• For semsys:seminfo_semopm:


value-set-for-"process.max-sem-ops" ,


-"process.max-sem-ops"-for-each-project}

• For msgsys:msginfo_msgmni:


value-set-for-"project.max-msg-ids" ,


-"project.max-msg-ids"-for-each-project}

• For semsys:seminfo_semmni:


value-set-for-"project.max-sem-ids" ,


-"project.max-sem-ids"-for-each-project}

• For shmsys:shminfo_shmmni:


value-set-for-"project.max-shm-ids" ,


-"project.max-shm-ids"-for-each-project}

• For shmsys:shminfo_shmmax:


value-set-for-"project.max-shm-memory" ,


-"project.max-shm-memory"-for-each-project}

/ value-set-for-"shmsys:shminfo_shmmni"


page 2-10

• Recommended Solaris 10 /etc/project values on page 2-13

Note: For shmsys:shminfo_shmmax, round fractions up before specifying the value.

Max {x, y} indicates the larger value of x or y.



Recommended Red Hat Enterprise Linux /etc/sysctl.conf values

Before installing HCS on a Red Hat Enterprise Linux system, set the kernel parameters for the /etc/sysctl.conf file.



• Device Manager



• Tuning Manager

The following tables show the kernel parameter values you need to set. The formulas for calculating these values follow the tables.

Table 2-10 Kernel parameter values for /etc/sysctl.conf (1/2)



Operating System


Component

fs.file-max 213556 50525 53898 53898

kernel.threads-max 16790 16384 576 184

kernel.msgmni 104 16 44 44

4th parameter of kernel.sem

1024 128 1024 9

2nd parameter of kernel.sem

32302 32000 7200 80

kernel.shmmax 490571136 4294967295 200000000 13100032

kernel.shmmni 4593 4096 2000 0

kernel.shmall 692147456 268435456 26214400 26214400





fs.file-max 108109 512 512 41354




10 1 1 12


122 50 50 0

kernel.shmmax 327471104 50000000 100000000 966656000



These formulas are for calculating kernel parameters values:

• For kernel.shmmax:

kernel-parameter-value-to-be-set = Max { Max { value-that-is-enabled-in-the-system , initial-value-of-the-OS }, value-for-Common-Component + value-for-Device-Manager + value-for-Tiered-Storage-Manager + value-for-Replication-Manager + value-for-Tuning-Manager , value-for-HiRDB}

• For kernel.shmall:

kernel-parameter-value-to-be-set = Max { value-that-is-enabled-in-the-system , initial-value-of-the-OS}+ value-for-Common-Component+ value-for-Device-Manager+ value-for-Tiered-Storage-Manager+ value-for-Replication-Manager + value-for-Tuning-Manager+ value-for-HiRDB

• All other kernel parameters and shell restrictions:

kernel-parameter-value-to-be-set = Max{ Max { value-that-is-enabled-in-the-system , initial-value-of-the-OS } + value-for-Common-Component + value-for-Device-Manager + value-for-Tiered-Storage-Manager + value-for-Replication-Manager + value-for-Tuning-Manager, value-for-HiRDB }


kernel.shmall 439023616 100695040 100000000 966656000








page 2-10

• Recommended Red Hat Enterprise Linux /etc/security/limits.conf values on page 2-19


Recommended Red Hat Enterprise Linux /etc/security/limits.conf values

Before installing HCS on a Red Hat Enterprise Linux system, set the shell restriction values for the /etc/security/limits.conf file. Set the shell restrictions for soft and hard settings.



• Device Manager



• Tuning Manager

The following tables show the shell restriction values you need to set. The formula for calculating these values follow the tables.

Table 2-12 Shell restriction values for /etc/security/limits.conf (1/2)


The following formula is for calculating the values for the shell restriction:

shell-restrictions-value-to-be-set = Max{ Max { value-that-is-enabled-in-the-system , initial-value-of-the-OS

Note: The soft value must be less than or equal to the hard value.

Shell Restriction Installer Check Value

Operating System


Component

nofile (soft/hard) 1596 1024 1344 572

nproc (soft/hard) 8358 8192 512 165

Shell Restriction Device Manager




nofile (soft/hard) 0 0 0 1024

nproc (soft/hard) 1 0 0 32



} + value-for-Common-Component + value-for-Device-Manager + value-for-Tiered-Storage-Manager + value-for-Replication-Manager + value-for-Tuning-Manager , value-for-HiRDB}


page 2-10

• Recommended Red Hat Enterprise Linux /etc/sysctl.conf values on page 2-17


Recommended SUSE Linux Enterprise Server /etc/sysctl.conf values

Before installing HCS on a SUSE Linux Enterprise Server system, set the kernel parameters for the /etc/sysctl.conf file.



• Device Manager



• Tuning Manager

The following tables show the kernel parameter values you need to set. The formulas for calculating these values follow the tables.




Operating System


Component

fs.file-max 213556 50525 53898 53898




1045 1024 1024 9


256302 256000 7200 80

kernel.shmmax 490571136 4294967295 200000000 13100032




The following formulas are for calculating the values for the kernel parameters:

• For kernel.shmmax:

kernel-parameter-value-to-be-set = Max { Max { value-that-is-enabled-in-the-system , initial-value-of-the-OS }, value-for-Common-Component + value-for-Device-Manager + value-for-Tiered-Storage-Manager + value-for-Replication-Manager + value-for-Tuning-Manager, value-for-HiRDB}

• For kernel.shmall:

kernel-parameter-value-to-be-set = Max { value-that-is-enabled-in-the-system , initial-value-of-the-OS}+ value-for-Common-Component+ value-for-Device-Manager+ value-for-Tiered-Storage-Manager+ value-for-Replication-Manager+ value-for-Tuning-Manager+ value-for-HiRDB

kernel.shmall 692147456 268435200 26214400 26214400





fs.file-max 108109 512 512 41354




10 1 1 12


122 50 50 0

kernel.shmmax 327471104 50000000 100000000 966656000


kernel.shmall 439023616 100695040 100000000 966656000


Operating System


Component



• All other kernel parameters and shell restrictions:

kernel-parameter-value-to-be-set = Max{ Max { value-that-is-enabled-in-the-system , initial-value-of-the-OS } + value-for-Common-Component + value-for-Device-Manager + value-for-Tiered-Storage-Manager + value-for-Replication-Manager + value-for-Tuning-Manager, value-for-HiRDB}


page 2-10

• Recommended SUSE Linux Enterprise Server /etc/security/limits.conf values on page 2-22


Recommended SUSE Linux Enterprise Server /etc/security/limits.conf values

Before installing HCS on a SUSE Linux Enterprise Server system, set the shell restrictions for the /etc/security/limits.conf file. Set the shell restrictions for soft and hard settings.



• Device Manager



• Tuning Manager

The following tables show the shell restrictions values you need to set. The formula for calculating these values follows the tables.


Note: The soft value must be less than or equal to the hard value.




The following formula is for calculating the values for the shell restriction:

shell-restrictions-value-to-be-set = Max{ Max { value-that-is-enabled-in-the-system , initial-value-of-the-OS } + value-for-Common-Component + value-for-Device-Manager + value-for-Tiered-Storage-Manager + value-for-Replication-Manager + value-for-Tuning-Manager, value-for-HiRDB}


page 2-10

• Recommended SUSE Linux Enterprise Server /etc/sysctl.conf values on page 2-20


Modifying kernel parameter values and shell restrictions

Once you check the current kernel parameter values and shell restrictions against your estimated requirements, you can change the values if necessary.

To change the kernel parameter and shell restriction values:

1. Back up the kernel parameter files.

Shell Restriction Installer Check value

Operating System


Component

nofile (soft/hard) 1596 1024 1344 572

nproc (soft/hard) 4262 4096 512 165

Shell Restriction Device Manager




nofile (soft/hard) 0 0 0 1024

nproc (soft/hard) 1 0 0 32




For the /etc/project file, use the prctl or similar command to check and record the values that are in effect in the user.root and system projects.

2. Set the value of each parameter according to the estimate.

3. Restart the operating system.


page 2-10


Registering firewall exceptions (Linux)You must register exceptions for Linux firewalls.

To manually register Linux firewall exceptions:

• For Red Hat Enterprise Linux: Use the text mode setup utility to register firewall exceptions.

• For SUSE Linux Enterprise Server: Edit the /etc/sysconfig/SuSEfirewall2 file to register firewall exceptions.

Related topics:• HCS server installation prerequisites on page 2-8


HCS server installationWhen you install HCS on the management server, use the installation procedure that is appropriate for the operating system you are using.

Related Topics:• Post-installation tasks (new installation) on page 2-26

• About post-installation tasks (overwrite or upgrade) on page 2-30

Server installation prerequisitesBefore installing HCS, review the information in Planning for server installation on page 2-2.

When you are done reviewing the information, perform the following tasks:

Stop Tuning Manager services:

• If a version earlier than 6.3 is installed on the same management server, stop the Tuning Manager Agent for SAN Switch service.

Note: For information about registering port numbers as exceptions, see Avoiding port conflicts on page 2-9.


• If Tuning Manager is remotely connected, stop the Tuning Manager server service.

Run Tiered Storage Manager tasks when upgrading from 7.1.0 or earlier:

• If there are incomplete tasks (standby, running, or being cancelled), go to the Tasks & Alerts tab and execute or cancel the tasks. After upgrading, register the canceled tasks as new.

Determine values that are set during installation

• The installation destination path

• The database storage destination path

• Management server information

• Memory heap size

• The database backup destination

Prerequsite checker

The prerequisite checker verifies whether the installation destination satisfies the requirements.

• In Windows, use the integrated installation media or run the prereqchk.exe file in DVD-drive:\HCS\

• In Solaris or Linux, run the prereqchk.sh file in DVD-ROM-mount-point/HCS/Platform-name/

For system requirements, see the Hitachi Command Suite Release Notes. To check task status, see the Hitachi Command Suite User Guide.




Installing HCS in a Windows environmentInstall the HCS in Windows with the installation DVD.

To install HCS:

1. Log on to Windows as the administrator.

2. Insert the installation DVD.

3. Click Install in the window that appears.

4. When you are prompted, enter the required information.

5. In the Installation Completed window, select the When installation completes, open the Device Manager GUI check box.

Note: If the installation window does not display automatically, run the following command:

DVD-drive\HCS\setup.exe



6. Click Finish.

The GUI login window appears.



• Post-installation tasks (new installation) on page 2-26


Installing HCS in a Solaris or Linux environmentInstall HCS on a Solaris or Linux host by using the installation DVD.

To install HCS:

1. Log on to Solaris or Linux as the root user.

2. Insert the installation DVD.

If the drive with the DVD is not mounted automatically, mount it manually.

3. Navigate to the installer directory:

DVD-ROM-mount-directory/HCS/platform-name/install.sh

4. Run the command # ./install.sh

5. When you are prompted, enter the required information.

When the installation is complete, the following message displays:

Hitachi Command Suite installation completed successfully.





Post-installation tasks (new installation)After you perform a new installation of Device Manager, Tiered Storage Manager, or Replication Manager, you must verify the installation.

In addition, perform these tasks:

• Open a browser and log on to HCS.

Note: If the integrated installation media is automatically mounted (Red Hat Enterprise Linux only), unmount the media and then re-mount it without specifying the noexec mount option.

These characters can be specified in the mount path of a DVD-ROM: A to Z, a to z, 0 to 9, underscores (_), forward slashes (/).


• Register the license.

• Change the system account passwords (recommended).

• Create a new user to whom you can assign permissions for all HCS resources and who will become the storage administrator.

After you have created a storage administrator, the storage administrator can register storage systems and hosts, add accounts for other storage administrators and begin operating HCS.

Verifying the installationYou can verify that the installation was successful by accessing the Web client from a browser.

To access the HCS Web client:

1. Start a Web browser.

2. In the address bar, specify the URL for HCS in the following format:

http://Management-server-IP-address-or-hostname:23015/DeviceManager/

The login window appears.

Registering licensesBefore you can use HCS to operate and manage storage systems and hosts, you must register a license key for each product.

To register a license key for a product:

1. In the product login window, click Licenses.

2. Add the license key.

3. Click Save.

License Information by Product is updated with the license information for the associated product.

Changing the system account passwordThe system account is a default account that has user management and execute permission for HCS.

The initial system account password is manager. When you install HCS for the first time, Hitachi recommends that you change the password.

To change the system account password:

1. Log in to HCS:

User ID: System

Password: manager

2. On the Administration tab, click Users and Permissions.

Note: When using Internet Explorer 6.0 in an IPv6 environment, specify the IP address and host name on the management server in the hosts file and use the host name to access the eb clientW.



3. In the tree view, select Users.

4. In the list of users, select the System account.

5. Click Change Password, type and verify the new password, and then click OK.

6. Confirm that you can log in to HCS with the new password.

Creating user accountsCreate accounts for users so they can perform operations.

To create a user account and assign permissions (roles) to the new account:

1. Log in to HCS using the System account.


3. In the tree view, click Users and then Add User.

4. Specify the required information, such as user ID and password.

5. On the Administration tab, click User Groups.

6. From the list of users in the Users tab, select a user account and click Assign User Groups.

7. Register the account into the group AdminGroup.

AdminGroup is a built-in user group.


9. In the tree view, select the user account and click Change Permission.

10.From All Applications, select the Admin, Modify, View, and Execute check boxes.

This grants operating permissions for managing users and using HCS products other than Device Manager.

Related topics• Roles on page 2-28

• User permissions on page 2-29

• Built-in user groups on page 2-30

RolesThe operations that a user can perform depends on the roles you assign to that user. You can also assign roles to each resource group.

Admin• Resource groups can be managed when All Resources is assigned.

Note: After you install an HCS product, you can add permissions (roles) for that product to existing user accounts.


• Management resources and tasks can be registered, management resource settings can be modified, and management resource information can be referenced.

Modify• Management resources and tasks can be registered, management

resource settings can be modified, and management resource information can be referenced.

View• Management resource and task information can be referenced.

Peer• Only for Device Manager agents and file server management software.

Cannot be assigned to resource groups. This role does not allow a user to log in to HCS or view resource information.

Related Topics• User permissions on page 2-29


User permissionsYou can assign permissions to a HCS user account.

User management permissions• Admin allows the user to manage users and security for all HCS

products. This permission can be set in conjunction with assigned roles for each product.

Tiered Storage Manager CLI permissions

These permissions are required when using the Tiered Storage Manager CLI. In addition, All Resources must be assigned and roles must be set.

• Admin: Allows the user to view information about Tiered Storage Manager resources and tasks.

• Modify: Allows the user to perform any operation from Tiers on the Resources tab, and migrate volumes.

• Execute: Allows the user to view information about Tiered Storage Manager Software resources and execute Tiered Storage Manager tasks.

• View: Allows the user to view information about Tiered Storage Manager resources and tasks.

Replication Manager permissions• Admin: Allows the user to perform any operation within a resource

group, with the exception of user management.



• Modify: Allows the user to manage resources within a resource group, as well as resources that have been granted by a user with Admin permissions.

• View: Allows the user to view any resources within a resource group that have been granted by a user with Admin permissions.

Related Topics• Roles on page 2-28


Built-in user groups Built-in user groups are provided.

Table 2-18 Built-in user groups

Related topics• User permissions on page 2-29

• Roles on page 2-28

About post-installation tasks (overwrite or upgrade)After performing an overwrite or upgrade HCS installation, set the information required by each installed product according to the version of each product before the overwrite or upgrade installation.

Built-in user group name Description

Roles Resource groupAdmin Modify View Peer

AdminGroup -- Y Y Y -- All Resources

ModifyGroup -- -- Y Y -- All Resources

ViewGroup -- -- -- Y -- All Resources

PeerGroup This user group applies only to Device Manager agents and files server management software. Users that belong to this group and have no other HCS permissions are not allowed to log in to HCS, nor can they view resource information. The HaUser account is assigned to this group after installation completes.

-- -- -- Y All Resources

Legend:

Y : The user group has this role

-- : Not applicable


When upgrading from version 7.1.0 or earlier, existing user accounts are migrated according to the previous environment.

After upgrading, the storage administrator can modify user group and resource group assignments as necessary.

Related topics• Built-in user groups on page 2-30



Performing post-installation tasks (overwrite or upgrade)After performing an overwrite or upgrade HCS installation, set the information required by each installed product according to the version of each product before the overwrite or upgrade installation.

When upgrading from Device Manager 7.1.1 or earlier, register again any SMI-S enabled storage systems managed by Device Manager.

Backing up databases

Back up databases after upgrades.

Refreshing storage systems

Always refresh storage systems.

Refreshing virtualization server information

If Device Manager manages virtualization servers, refresh the virtualization server information.

Resetting user accounts

After upgrading from these versions, reset user accounts:

• 5.00 to 5.10-04

• 5.50 to 5.50-02

• 5.60

Resetting roles and permissions

When upgrading from 7.1.0 or earlier, reset roles and permissions.

Notifications

When upgrading from 7.1.0 or earlier, you can specify Tiered Storage Manager event notifications.



Updating property files

Update property files when using Tuning Manager for volume performance information (IOPS or response time).

Synchronizing databases

Synchronize databases when Replication Manager is used and the Device Manager GUI is used to manage copy pairs, even if a Replication Manager license is not registered.

Related topics• Built-in user groups on page 2-30



Backing up databasesTo prepare against failures, back up databases after completing the installation.

To back up databases:

1. Log on to the management server as a user with administrator or root permissions.

2. Execute the hcmdsbackups command to back up the database.

For Windows:

Common-Component-installation-folder\bin\hcmdsbackups /dir folder-for-storing-backup-files /auto


Common-Component-installation-directory/bin/hcmdsbackups -dir directory-for-storing-backup-files -auto

When hcmdsbackups completes, the backup directory is created in the directory specified by the dir option, and database files are combined and stored as backup.hdb.

Refreshing storage systemsTo refresh the database, refresh all storage systems registered in HCS.

Note: The dir option is used to specify the absolute path of the folder or directory on the local disk where the database backup files are stored. Verify that the folder or directory specified does not already include any files or subdirectories. (For Solaris or Linux, do not specify a path that includes a space.)

The auto option automatically changes the status of the HCS product services and the HiRDB service on the same system to active, so the database can be backed up.


To refresh storage system information:

1. Log in to HCS using the System account.

2. On the Resources tab, click Storage Systems.

3. From the list of storage systems, select the storage system you want to refresh.

4. Click Refresh Storage Systems.

The database of storage systems is updated and the current information is reflected in the Summary and Storage Systems list.

Refreshing virtualization server informationDevice Manager virtualization server information must be refreshed to reflect the current database virtualization server configuration.

When a virtualization server management program (vMA) monitors VMware vCenter Server, register again the virtualization servers by specifying the IP address of vMA to automatically update the information for the virtualization servers connected to VMware vCenter Server.

To refresh virtualization server information:

1. Log in to Device Manager using the System account.

2. On the Administration tab, click Managed Resources.

3. On the Hosts tab, select the virtualization server you are refreshing and click Refresh Hosts.

The updated information appears on the Hosts tab.

Resetting user accountsTo improve user account security from versions earlier than 5.7, change user passwords.

To change the password for a user account:



3. Select the target user.

4. Click Change Password.

5. Type the new password and verify it.

6. Click OK.

7. Confirm that the user can log in with the new password.

Resetting roles and permissionsWhen upgrading from 7.1.0 and earlier, user roles or permissions can change.

To verify user account status after upgrading, output the following CSV files:

• user information (you can verify the user group for each user account).



• user group information (you can verify the resource group or roles for each user group).

Managing accounts by users

When upgrading, user accounts change according to the version before the upgrade, the user permissions (roles), and the resource groups. The storage administrator must review user account settings for the new environment.

Managing accounts by groups

When linked to external authorization servers, nested groups acquire the permissions (roles) specified for the higher-level groups.

Since permissions (roles) of users who belong to nested groups can change after an upgrade, the storage administrator must review:

• Device Manager roles

• Tiered Storage Manager permissions

• Replication Manager permissions and user roles

Table 2-19 User account settings after upgrading

From version

Before upgrading

After upgradingDevice

Manager permissions

(roles)

Tiered Storage Manager

permissions

Resource group

6.x and earlier Y None All Resources Registered in built-in user groups according to Device Manager permissions. Operations can be restarted without performing any additional tasks.

6.x and earlier Y None User defined resource groups

Resource groups and permissions are released, but only the accounts remain registered. To restart Device Manager operations, do the following:

Register user accounts in user groups.

Allocate resource groups to user groups.

Set roles to resource groups.

6.x and earlier Y Y All Resources User accounts are registered in built-in user groups according to Device Manager permissions.

Depending on the user responsibilities, ask the storage administrator to review the allocation of user groups and resource groups that the user belongs to. #


6.x and earlier Y Y User defined resource groups

Resource groups and permissions are released, and only the accounts remain registered. To restart Device Manager and Tiered Storage Manager operations, verify the following from the GUI #:

User accounts must be registered to user groups.

Resource groups must be allocated to user groups.

Roles must be set to resource groups.

6.x and earlier None Y None Only the accounts remain registered. To restart Tiered Storage Manager operations, verify the following from the GUI #:

User accounts must be registered to user groups.

Resource groups must be allocated to user groups.

Roles must be set to resource groups.

7.0.0 - 7.0.1 Y None All Resources Registered in built-in user groups according to Device Manager permissions. Operations can be restarted without performing any additional tasks.

7.0.0 - 7.0.1 Y Y All Resources Registered in built-in user groups according to Device Manager permissions.


7.1.0 Y None All Resources User groups, resource groups, and roles are inherited. Operations can be restarted without performing any additional tasks.

7.1.0 Y None User defined resource groups

User groups, resource groups, and roles are inherited. Operations can be restarted without performing any additional tasks.

From version

Before upgrading


Manager permissions

(roles)


permissions

Resource group



For more information, see the Hitachi Command Suite User Guide and Hitachi Command Suite Configuration Reference Guide.

Related Topics• User permissions on page 2-29



Using event notificationsYou can use event notifications in Tiered Storage Manager after upgrading Hitachi Command Suite from 7.1.0 or earlier.

To use event notifications:

1. In the server.properties file for Device Manager, set the following.

server.mail.enabled

server.mail.smtp.host

server.mail.from

server.mail.errorsTo

server.mail.smtp.port

server.mail.smtp.auth

server.eventNotification.mail.to

2. Register SMTP authenticated users to Device Manager.

3. Customize the email template (optional).

For more information, see the Hitachi Command Suite Configuration Reference Guide.

7.1.0 Y Y All Resources User groups, resource groups, and roles are inherited.


#: When migrating from the Tiered Storage Manager GUI using an existing migration group or when using the Tiered Storage Manager CLI, allocate All Resources to the user group. In addition, when migrating from the Tiered Storage Manager GUI using an existing migration group, change the client.migration.use.legacymode property in the Device Manager client.properties file to true (default is false), and restart all services.

From version

Before upgrading


Manager permissions

(roles)


permissions

Resource group


Updating property filesIf you upgraded from 7.1.1 and are using Tuning Manager for volume performance information (IOPS or response time), update the config.xml property file.

After you modify the logFileSize value to at least 8, restart Hitachi Command Suite services.

Windows

installation-folder-for-Device-Manager-server\HiCommandServer\vsa\conf

Solaris and Linux

installation-directory-for-Device-Manager-server/HiCommandServer/vsa/conf

Synchronizing databasesWhen you use Replication Manager, after you perform an upgrade or overwrite installation, you must synchronize the Replication Manager database and the HCS database to update the Replication Manager database to the latest configuration.

To synchronize databases:

1. If Replication Manager Application Agent version 7.1 or later is installed on the management server, set the value of the base.refreshdginfo.exec property in the Replication Manager base.properties file to 0.

The base.properties file is stored in the following location:

In Windows:

Replication-Manager-server-installation-folder\conf

In Solaris or Linux:

Replication-Manager-server-installation-directory/conf


3. On the Actions menu, select Manage Replication.

4. In the Explorer menu, select Settings and then select Refresh Setting.

5. In the tree view, select Configuration Setting.

6. Select the instances to synchronize and click Refresh Configuration.

When upgrading Replication Manager server at the primary site, do this for every site.

When upgrading Device Manager server at the remote (secondary) site, do this at the remote site.



3

Agent installation 3–1Hitachi Command Suite Installation and Configuration Guide

Agent installation

This module describes how to install and set up Device Manager agents.

□ Planning for Device Manager agent installation

□ Agent installation prerequisites

□ Installing agents

□ Device Manager agent post-installation tasks


3–2 Agent installation

Planning for Device Manager agent installationBefore you install the Device Manager agent, verify the prerequisites and gather the information you need to perform the installation.

Prerequisites for agent installationBefore performing a new installation, gather the appropriate information for the installation wizard, including the installation folder.

For Windows:

• Installation folder. Default: program-files-folder\HITACHI\HDVM\HBaseAgent#

#: program-files-folder indicates the following location:

For Windows (x86): The folder specified in the Windows system environment variable %ProgramFiles%.

For Windows (x64 or IPF): The folder specified in the Windows system environment variable %ProgramFiles(x86)%.

You can change the agent installation folder location in Windows as long as the following software is not installed:

Dynamic Link Manager

Replication Manager application agent

Tuning Manager Agent for SAN switch

Global Link Manager Agent

• Whether to set up agent services account information. To set up account information for agent services, you must specify a Windows account with Administrator permissions (default is Yes).

For UNIX:

• The UNIX installation folder cannot be changed.

For Windows and UNIX:

• Device Manager server IP address or host name. Default: 255.255.255.255

• Device Manager port. Default: 2001/tcp

• User ID (user account that belongs to PeerGroup): HaUser

Password: haset

• HiScan command execution schedule. Default: Daily at 2:30 AM.

For CCI:

• Installation location. Default in Windows: Device Manager agent installation drive.

• Default in UNIX: /HORCM

Note: When updating a system or performing a recovery, the Device Manager server information and HiScan command execution periods are imported.


• By default, copy pairs are not batch managed by the agent host (default is no).

Related topics• Agent installation prerequisites on page 3-6

• Installing the Device Manager agent on a Windows host on page 3-14

• Installing the Device Manager agent on a UNIX host on page 3-15

Prerequisites for agent installations with add-onsIf you use Replication Manager in Windows to monitor or perform copy pair operations, you can use an add-on function to install and configure the Device Manager agent.

When using either of the following configurations, you can use the add-on function to install and configure the Device Manager agent with settings suitable for the corresponding configuration:

• Configurations in which SVPs are used for virtual command devices to manage copy pairs

• Configurations in which copy pairs are defined as device groups

The following items are automatically set when the add-on function is used:

• Installation destination: The installation destination is automatically set by the installer.

• Agent service accounts: By default, agent service accounts are not set up on your local system. You do not need to change this setting.

• Information for the Device Manager server:

IP address or host name: localhost

Default Device Manager server port: 2001/tcp#

#: If the port set for the server.http.port property in the Device Manager server server.properties file is different from the default port setting, after the installation, use the hdvmagt_setting command to change the Device Manager agent setting.

User ID (user account that belongs to PeerGroup): HaUser

Password: haset

HiScan command schedule: Do not set.

• For CCI:

The Windows default installation folder: CCI installation drive

Enable batch management of copy pairs on the host on which the Device Manager agent is installed: Yes


Related topics• Agent installation prerequisites on page 3-6




Prerequisites for agent installation locationsBefore specifying an installation folder for the Device Manager agent, verify that the required disk space is available.

When creating the installation location for the Device Manager agent, adhere to the naming conventions in Table 3-1 Agent installation folder naming requirements on page 3-4.

Table 3-1 Agent installation folder naming requirements

Related topics• Prerequisites for agent installation on page 3-2

• Agent installation prerequisites on page 3-6



Modifying agent servicesA user account that is registered in a Device Manager agent service (HBsA Service) and is part of the Administrators group can be used to edit horcm instances run by the Device Manager agent.

To modify horcm instances run by the Device Manager agent:

• Specify a user account in the Administrators group.

• Specify domain users as domain-name\user-name.





Prerequisites for verifying server informationBefore installing a Device Manager agent, determine information about the Device Manager server (where the host information is sent).


Maximum length 64 characters

Allowed characters A to Z, a to z, 0 to 9, periods (.), underscores (_), left parentheses ( ( ), right parentheses ( ) ), and single-byte spaces

Other conditions • Do not use a space as the first or last character of the installation folder name.

• Do not include multi-byte characters in the file name or path.

• Do not include consecutive spaces in the file name or path.


• The server IP address or host name. IPv6 addresses can be specified using global addresses.

Server host name maximum length: 50 bytes.

Server host name allowed characters: A through Z, a through z, 0 through 9, hyphens (-), underscores (_), periods (.), and at signs (@)

Other server host name conditions: Do not use a hyphen as the first or last character.

• The server port number. This is used by the agent and the server.

• User ID and password. This is the user account for logging in to the Device Manager server. The user account must belong to PeerGroup.





About HiScan command executionThe HiScan command configures Device Manager agents to send information to the server on a regular basis. You can schedule HiScan for hourly, daily, or weekly execution.

If no HiScan execution periods are set, agents do not regularly send acquired information to the server.

To reduce HCS server loads when agents are installed on multiple hosts, specify daily or weekly executions and verify that multiple HiScans do not run simultaneously.

For Windows, the batch file exeHiScan.bat with the HiScan settings is registered as a Windows task.





Prerequisites for identifying CCIWhen Device Manager is linked to CCI and used to manage copy pairs, you must determine some information.

• The location of the CCI installation folder:

Note: If you specify weekly executions, also specify the day of the week you want the scan to run.



In Windows, the installation drive.

In UNIX, the installation directory.

• The method used for managing copy pairs:

Batch managed on a Device Manager agent host.

Managed for each host on which the Device Manager agent is installed.





Agent installation prerequisitesBefore installing the Device Manager agent, review the general prerequisites and check the host settings and the status of each affected program to confirm that the host system is in the appropriate state.

For more information about system requirements, see the Hitachi Command Suite Release Notes.

Related topics• General prerequisites on page 3-6

• Windows prerequisites on page 3-8

• Solaris prerequisites on page 3-9

• AIX prerequisites on page 3-10

• Linux prerequisites on page 3-11

• HP-UX prerequisites on page 3-12

• Installing agents on page 3-14

General prerequisitesBefore installing the Device Manager agent, perform prerequisite tasks as appropriate.

• The Device Manager agent does not support operating systems that allow only IPv6 addresses. To use the agent in an IPv6 operating system, configure it to allow both IPv4 and IPv6 addresses.

• Stop all programs.

• When setting up a firewall provided by an operating system, configure it so socket connections cannot be terminated in the local host.

• If you are running security monitoring programs, either temporarily stop them or change the settings so they do not prevent the installation.


• Device Manager agent versions 5.7 and later are compatible with the Daylight Saving Time (DST) rules implemented in the United States and Canada in 2007. When using the Device Manager agent in these time zones, set the host operating system for the new DST rules according to information provided by the operating system vendor.

• When installing or upgrading Device Manager agent, do not run these commands:

hbsasrv

hdvmagt#1

hdvmagt_account#2

hdvmagt_schedule#2

hdvmagt_setting

HiScan

hldutil

stop_hdvmagt#1

TIC

#1Commands for Device Manager agent versions earlier than 5.0.

#2Commands for Device Manager agent versions earlier than 7.0.

If you run these one of these commands by mistake, restart your system when the installation or upgrade completes.

• Do not perform an overwrite installation of Device Manager agent using a version that is earlier than the one currently installed. To install an earlier version, first remove the Device Manager agent that is currently installed.

• Do not install Replication Monitor agent version 5.9 or earlier if Device Manager agent version 6.0 or later is already installed.

Related topics• Windows prerequisites on page 3-8

• Solaris prerequisites on page 3-9

• AIX prerequisites on page 3-10

• Linux prerequisites on page 3-11

• HP-UX prerequisites on page 3-12



Note: Replication Monitor agent is integrated with Device Manager agent version 6.0 and later. If you update Device Manager agent to version 6.0 or later on a system with Replication Monitor version 5.9 or earlier installed, Replication Monitor agent is automatically removed.

Replication Monitor program information is no longer displayed in the Windows Add or Remove Programs dialog box.



Windows prerequisitesIf these conditions are not satisfied, Device Manager agent installation may fail or the Device Manager agent may not work properly.

Before installing Device Manager agents, perform the following tasks:

• Stop the hdvmagt service before updating to an agent that is version 3.5 or earlier.

• If you install in Windows Server 2003 (IPF), verify that Service Pack 1 or later is installed. If you install a service pack after installing agents, perform an overwrite installation of the Device Manager agent.

• If the Windows logon account contains multi-byte characters, agents cannot be installed. Specify a folder that does not include multi-byte characters for the TMP environment variable.

HCS products for Windows support the Windows remote desktop functionality.

Keep the following in mind when working with Windows remote desktop:

• When using the remote desktop, connect to the console session of the target server in advance and ensure that no one else connects to your session.

• When logging on to Windows from a remote console, use the Terminal Service Client.

Ensure that the setting for automatically generating short file and folder names (8.3 format) is enabled and use an account that was created while this setting was enabled. Do not change the setting for automatically generating short names, even after the installation is completed.

To check whether a user was created while the setting for automatically generating short file and folder names was disabled, run:

dir /x /a- Windows-system-drive:\Documents and Settings\Windows-account-name | find "Local Settings"

If the user was created while this setting was enabled, LOCALS~1 is included in the returned information:

2008/01/01 18:26 <DIR> LOCALS~1 Local Settings

If the user was created with this setting disabled, the following is returned:

2008/01/01 18:26 <DIR> Local Settings

Note: The Microsoft terms for this functionality differ, depending on the Windows operating system. These terms can refer to the same functionality:

• Terminal Services in the Remote Administration mode

• Remote Desktop for Administration

• Remote Desktop Connection




Solaris prerequisitesDo not install Device Manager agents in Solaris environments when symbolic links exist for the following directories:

• /opt

• All subdirectories under /opt/HDVM (including /opt/HDVM)

• /var

• /var/opt

• All subdirectories under /var/opt/HBaseAgent (including /var/opt/HBaseAgent)

• All subdirectories under /var/opt/HDVM (including /var/opt/HDVM)

• /var/tmp

When installing the Device Manager agent in a Solaris 10 environment, do not specify system zone settings.



Removing HDSHiScan packages when using SolarisRemove the HDSHiScan package before installing the Device Manager agent. Hitachi recommends that you remove any agent not being used.

To remove HDSHiScan packages:

1. At the prompt, confirm whether a HiScan package is installed by running:

% su

# pkginfo -l HDSHiScan

2. If the HDSHiScan package is installed, confirm the execution period of the HiScan command before removing by running:

% su

# crontab -l

3. To remove HiScan packages, run:

% su

# pkgrm HDSHiScan

Caution: HDSHiScan is the name used for versions earlier than 2.2. HDVMAgent is the name used for version 2.2 and later. The HDSHiScan package is installed in the /opt/HDVM directory.





Removing agents when using Solaris 10If the Device Manager agent (version 4.1- 5.1) was upgraded to 5.5 or later by an overwrite installation in an environment with the non-global zone specified, it is installed in the global and non-global zones. Since the agent is not required for the non-global zone, you can remove it.

To remove the Device Manager agent from the non-global zone:

1. Log in to the non-global zone.

2. Execute # pkgrm HDVMAgent



AIX prerequisitesDo not install Device Manager agents in AIX environments when symbolic links exist for the following directories:

• /usr

• /usr/HDVM and its subdirectories

• /var/HDVM and its subdirectories

• /var

• /var/HBaseAgent and its subdirectories

• /var/tmp

• When IBM XL C/C++ Enterprise Edition V8 for AIX Runtime version 8.0.0.3 to 8.0.0.5 is applied, the overwrite installation of the Device Manager agent hangs if either:

the Dynamic Link Manager installed is version 5.8 through 5.9

the Device Manager agent installed is version 5.0 - 5.1.03

When you use the Device Manager agent, upgrade IBM XL C/C++ Enterprise Edition V8 for AIX Runtime to version 8.0.0.6 or later, or apply the APAR IY87291 patch.

Before you install the Device Manager agent in AIX, verify the IBM XL C/C++ Enterprise Edition V8 for AIX Runtime version by running # lslpp -L xlC.aix50.rte


• AIX includes the Stack Execution Disable (SED) function that protects systems from attacks that use a buffer overflow. If the SED mode is set to all, change the mode before installing the Device Manager agent by running # sedmgr -m {select|off|setidfiles}



Removing HDSHiScan packages when using AIXRemove the HDSHiScan package before installing the Device Manager agent. Hitachi recommends that you remove any agent not being used.



% su

% lslpp -l HDSHiScan.rte


% su

# crontab -l

3. To remove HiScan packages, run the following commands.

Device Manager agent version 2.4 or earlier:

% su

% installp -u HDSHiScan.rte

Device Manager agent version 3.0 or later: % /usr/HDVM/bin.uninstall.sh



Linux prerequisitesDo not install Device Manager agents in Linux environments when symbolic links exist for the following directories:

Note: To return the SED mode to all after installing the Device Manager agent, exclude the Java process used by the Device Manager agent from the SED protection targets. For details, see the Hitachi Device Manager Configuration Reference Guide.

Caution: HDSHiScan is the name used for versions earlier than 2.2. HDVMAgent is the name used for version 2.2 and later. The HDSHiScan package is installed in the /usr/HDVM directory.



• /opt

• /opt/HDVM and its subdirectories

• /var

• /var/opt

• /var/opt/HBaseAgent and its subdirectories

• /var/opt/HDVM and its subdirectories

• /var/tmp



Allowing communication with Linux firewallsA Linux firewall may prevent communication between the Device Manager agent and the Device Manager server.

If you are installing on a Linux system that has a firewall:

1. Disable iptables by running iptables stop on the Linux host.

2. Do one of the following:

Configure the host not to start iptables when Linux starts.

Configure iptables to release the port in use.



HP-UX prerequisitesWhen installing the Device Manager agent in an HP-UX environment, you must consider some items.

Keep the following in mind when installing the Device Manager agent in an HP-UX environment:

• Verify that the swagentd daemon is running.

If necessary, start the daemon process by executing:

/usr/sbin/swagentd

• Verify that the file system mounted on the host matches that defined in /etc/fstab.


• Verify that the network settings (such as those in the hosts file) are correct.

• Do not create a symbolic link for any of the directories below. If you have already created a symbolic link by using any of the directories below, do not install the Device Manager agent.

/opt

All subdirectories under /opt/HDVM (including /opt/HDVM)

/var

/var/opt

All subdirectories under /var/opt/HBaseAgent (including /var/opt/HBaseAgent)

All subdirectories under /var/opt/HDVM (including /var/opt/HDVM)

/var/tmp



Removing HDSHiScan packages when using HP-UXRemove the HDSHiScan package before installing the Device Manager agent. Hitachi recommends that you remove any agent not being used.



% su

# swlist HDSHiScan


% su

# crontab -l

3. To remove HiScan packages, run the following commands.

% su

Note: Do not try to install the Device Manager agent on an HP-UX workstation. If you do, the installation fails and the following message appears:

ERROR: Could not apply the software selection "HDVMAgent" because there are no product variations that are compatible with the destination host(s).

Caution: HDSHiScan is the name used for versions earlier than 2.2. HDVMAgent is the name used for version 2.2 and later. The HDSHiScan package is installed in the /opt/HDVM directory.



# swremove HDSHiScan



Installing agentsFollow the instructions for installing the Device Manager agent on your operating system.

Before you install the Device Manager agent, review the information in Planning for Device Manager agent installation on page 3-2, and Agent installation prerequisites on page 3-6.

Related topics• Device Manager agent post-installation tasks on page 3-15

Installing the Device Manager agent on a Windows hostYou can install the Device Manager agent on a Windows host from the product DVD, and add the agent-commands folder to the PATH variable.

To install the Device Manager agent in Windows:

1. Log in to Windows as the administrator.

2. Insert the product DVD.

3. In the installation window, click Install next to Device Manager Agent.

If the installation window does not display automatically, run the following command:

DVD-drive\AGENTS\HDVM\Windows\setup.exe

4. Enter the required information when prompted.

5. Log out.

6. Log in again to add the agent-commands folder to the PATH environment variable.

7. If the following temporary folder remains after the installation, delete it:

system-drive\_HDVMAgentversion-number_Install_tmp_\



• Device Manager agent post-installation tasks on page 3-15

Note: To install the Device Manager agent and automatically configure the appropriate settings for Replication Manager operation, click Install next to Replication Manager add-on.


Installing the Device Manager agent on a UNIX hostYou can install the Device Manager agent on a UNIX host with the product DVD.

To install the Device Manager agent in UNIX:

1. Log in to UNIX as the root user.

2. Insert the product DVD.

If the drive with the DVD is not mounted automatically, mount it manually.

3. Navigate to the directory where the installer program (install.sh) is located:

DVD-ROM-mount-point/AGENTS/HDVM/platform-name


4. Enter the following command: # ./install.sh.

5. Enter the required information when prompted.

The following message displays when the Device Manager agent setup is complete:

The Device Manager agent setup has completed successfully.

6. Add host names to the hosts file:a. Open the /etc/hosts file.b. Confirm that the local host name and agent host name are in the file.

If your host is running on Linux, enter the name of the local host in the line before the localhost entry.

c. Restart the Device Manager agent services.




Device Manager agent post-installation tasksAfter the Device Manager agent installation completes, additional tasks may be required, depending on the previous version of the agent that was installed.

These additional tasks are described in the following sections:

• Modifying Device Manager agent properties on page 3-16

• Resetting the service execution user (Windows) on page 3-16

• Registering firewall exceptions (Windows) on page 3-17



Modifying Device Manager agent propertiesAfter installing the Device Manager agent, you may have to modify some of its properties.

To modify Device Manager agent properties:

1. Stop the agent service.

2. Modify the properties for the appropriate environment.

Internet Protocol version 6 (IPv6)

Set the following properties in the agent server.properties file.

• server.http.socket.agentAddress: Set the property to the IP address used to connect the Device Manager agent to the Device Manager server.

• server.http.socket.bindAddress: If the agent host has multiple NICs, specify the IP address of one or more NIC, as needed, to receive requests.

Veritas Volume Manager (VxVM)

Specify the installed VxVM version in the veritas.volume.manager.version property of the programproductinfo.properties file. Use the format x.x to specify a version.

Dynamic Link Manager versions 05-00 through 05-9

In the agent server.properties file, specify the agent ports for the server.http.port and server.agent.port properties.

UNIX environments, when the Device Manager agent is updated from version 05-00 to 5.9

If host programs do not require a different Java Runtime Environment (JRE) version from 1.4, then JRE 1.4 (included in versions 05-00 through 5.9) is used.

After the update, if a program is installed with a valid JRE, specify that program installation path in the server.agent.JRE.location property of the server.properties file.

Resetting the service execution user (Windows)After an update or recovery installation in Windows, the agent service execution user setting reverts to the default (LocalSystem). If the agent execution user is not LocalSystem, change this setting after the installation.

To reapply the setting, go to Windows Computer Management and modify the HBsA Service service account information.


Registering firewall exceptions (Windows)When you perform an unattended installation and you have Windows Firewall enabled, you must add port numbers to the firewall exceptions list.

• The port number specified for the server.agent.port property in the server.properties file (Default: 24041/tcp)

• The port number specified for the server.http.port property in the server.properties file (Default: 24042/tcp)

• The port number specified for the server.http.localPort property in the server.properties file (Default: 24043/tcp)

To register firewall exceptions:

1. Log in to Windows using a user ID with Administrator permissions.

2. Execute the following command to add the port numbers used by the Device Manager agent to the exceptions list:

Device-Manager-agent-installation-folder\bin\firewall_setup.bat -set



4

Removing HCS 4–1Hitachi Command Suite Installation and Configuration Guide

Removing HCS

This module describes how to remove HCS and components.

□ Removing HCS server

□ Removing a Device Manager agent


4–2 Removing HCS

Removing HCS serverYou can remove HCS when you no longer need to manage storage systems and hosts.

Removing HCS also deletes associated properties files, database files, log files, and other files belonging to the following components:

• Device Manager server

• Replication Manager server

• Tiered Storage Manager server

• Common Component#


#The Common Component files are deleted only if there are no products that require Common Component on the management servers.

In addition, removing HCS deletes any files and subdirectories or folders added to the installation directory after the installation.

Prerequisites for removing HCS serverIf you are installing HCS on another management server, or if you are continuing system operation with HCS products installed on a different system, export the database before removing HCS.


Related topics• Removing HCS from a Windows host on page 4-2

• Removing HCS from a Solaris or Linux host on page 4-3

Removing HCS from a Windows hostRemove HCS from Windows hosts using Add or Remove Programs.

To remove HCS:

1. Log on to Windows as the administrator.

2. Navigate to Start > Settings > Control Panel.

3. Double-click Add or Remove Programs.

4. In the Add or Remove Programs window, select Hitachi Command Suite.

5. Click Remove.

6. Follow the on-screen instructions.

When HCS is removed, the Removal Complete window appears.


Related topics• Prerequisites for removing HCS server on page 4-2

Removing HCS from a Solaris or Linux hostRemove HCS from Solaris or Linux hosts using the command line.

To remove HCS:

1. Log on to Solaris or Linux as the root user.

2. Navigate to the root directory.

3. Enter the following command:

# HCS-installation-directory/Uninstall/uninstall.sh

4. Follow the on-screen instructions.

When HCS is removed, the following message appears:

Hitachi Command Suite removal completed successfully.

Related topics• Prerequisites for removing HCS server on page 4-2

Removing a Device Manager agentYou can remove the Device Manager agent when you no longer need it to manage a host. Removing an agent also removes its properties and log files.

Prerequisites for removing Device Manager agentsBefore removing the Device Manager agent from a host, you must note some information.

Note the following:

• For HP-UX: Verify that the swagentd daemon is running.

If necessary, start the daemon process by executing:

/usr/sbin/swagentd

• For HP-UX: Verify that the file system mounted on the host matches that defined in /etc/fstab.

• If you perform another operation while the Device Manager agent is being removed, the operation terminates with an error. If a program related to the Device Manager agent is installed on the host when this occurs, some Device Manager agent data may remain on the host.

• If you start to remove the Device Manager agent while one of the following commands is executing, the attempt may terminate in an incomplete state, forcing you to restart the system before removing the agent:

hbsasrv

hdvmagt_setting


4–4 Removing HCS

HiScan

hldutil

TIC

• If the host operating system is Solaris 10, do not specify settings related to a system zone when you remove the Device Manager agent. If you do, the removal may terminate abnormally.

• When the process for removing the Device Manager agent starts, the Device Manager agent and any add-on modules automatically stop.

• The following files are not deleted:

Files created by the HiScan command

CCI configuration definition files

Error information files created by executing the TIC command

• If version 05-80 or later of Dynamic Link Manager or version 6.2 or later of the Global Link Manager agent is installed, the following data remains after the Device Manager agent is removed:

Data in the Device Manager agent installation folder

Data in the JRE installation folder

To delete this data, completely remove the Dynamic Link Manager and the Global Link Manager agent.

Related topics• Removing Device Manager agents from Windows hosts on page 4-4

• Removing Device Manager agents from UNIX hosts on page 4-5

Removing Device Manager agents from Windows hostsRemove Device Manager agents from Windows hosts using Add or Remove programs.

After you log into Windows as the administrator, remove the agent according the version of Windows server installed on your system.

To remove agents from Windows other than Windows Server 2008 or Windows Server 2008 R2:

1. Navigate to Start > Settings > Control Panel.

2. Double-click Add or Remove Programs.

3. In the Add or Remove Programs window, select Hitachi Device Manager agent.

4. Click Remove.

You can also execute Device-Manager-agent-installation-folder\bin\agent_uninstShortcut.bat.

Note: If you remove the Device Manager agent while HiScan is executing, the process for removing the agent is canceled. If this occurs, wait until the command terminates, and then remove the agent.


To remove agents from Windows Server 2008 or Windows Server 2008 R2:

1. In the Server Core environment, enter the following command at the prompt that displays when you log in: agent_uninstShortcut.bat.

When Device Manager agent is removed, the InstallShield Wizard Completed window appears.

Related topics• Prerequisites for removing Device Manager agents on page 4-3

Removing Device Manager agents from UNIX hostsRemove Device Manager agents from UNIX hosts using the command line.

To remove the Device Manager agent:

1. Log on to UNIX as the root user.

2. At the command line, enter the following:

For Solaris, Linux or HP-UX:

# /opt/HDVM/HBaseAgent/bin/.uninstall.sh

For AIX:

# /usr/HDVM/HBaseAgent/bin/.uninstall.sh

3. Follow the instructions on the screen.

When the Device Manager agent is removed, the following message appears:

Device Manager - Agent removed successfully.


Note: The following tasks that run the HiScan command remain after you remove Device Manager agent. Remove them manually:

• Any task that runs exeHiScan.bat with a schedule that was changed in the Scheduled Tasks window that opens from the Control Panel.

• Any task that runs exeHiScan.bat that is registered in Windows.


4–6 Removing HCS

A

Performing unattended installation and removal A–1Hitachi Command Suite Installation and Configuration Guide

Performing unattended installationand removal

This appendix describes unattended installation and removal operations.

□ Performing an HCS server unattended installation

□ Performing a Device Manager agent unattended installation

□ Performing a Device Manager agent unattended removal


A–2 Performing unattended installation and removal

Performing an HCS server unattended installationHCS provides an unattended feature so that you do not need to provide responses during installation. You can perform an unattended installation by creating and executing a script file when the conditions on multiple management servers are the same.

HCS server unattended installation properties and settingsBefore performing an unattended server installation, provide values for the following properties:

• HINST_INSTDIR You cannot specify this property in Solaris (SPARC).

• HINST_DBDIR

• HINST_IPADDRESS

• HINST_DBBACKUP

• HINST_DBBACKUPDIR

• HINST_COMMONHEAP

• HINST_HDVMHEAP

• HINST_RUNSERVICE

• HINST_IGNORE_CAPACITY_CHECK

• HINST_IGNORE_NETWORKING_CHECK

• HINST_IGNORE_VIRTUAL_MEMORY_CHECK

If a property is not specified, the default value is used.

Table A-1 Unattended-installation properties settings on page A-2 lists the properties you must set for an unattended installation. The table also includes information about property settings and defaults.

Table A-1 Unattended-installation properties settings

Property Name Details Default Value

HINST_INSTDIR#1 For a new installation: Specify the installation directory.

Windows: program-files-folder\HiCommand#2

Solaris and Linux:

/opt/HiCommand

HINST_DBDIR#3 For a new installation: Specify the directory for database files.

Windows:

value-specified-for-HINST_INSTDIR\database

Solaris or Linux:

/var/value-specified-for-HINST_INSTDIR/database

HINST_IPADDRESS#4 For a new installation: Specify the IP address or host name of the management server.

Host name obtained by the hostname command.


HINST_DBBACKUP#5 Specify whether to backup or export the databases before performing an upgrade installation on the management server:

• TRUE: Backup or export the databases

• FALSE: Do not backup or export the databases

TRUE

HINST_DBBACKUPDIR#5 If HCS products are installed on the management server: Specify the directory for database backup files.

Windows:

value-specified-for-HINST_INSTDIR\backup

Solaris or Linux:

/var/value-specified-for-HINST_INSTDIR/backup

HINST_COMMONHEAP Specify the memory heap size for Common Component:

• Small

• Medium

• Large

Windows (x86):

Medium

Windows (x64), Solaris or Linux:

Large

HINST_HDVMHEAP Specify the memory heap size for the Device Manager server:

• Small

• Medium

• Large

Windows (x86):

Medium

Windows (x64), Solaris or Linux:

Large

HINST_RUNSERVICE#6 Specify whether to start the product services after the installation:

• TRUE: Start after installation.

• FALSE: Do not start after installation.

TRUE

HINST_IGNORE_CAPACITY_CHECK

Specify whether to continue the installation when there is insufficient unused capacity:

• TRUE: Continue the installation

• FALSE: Stop the installation.

FALSE




Related topics• Prerequisites for server installation locations (new installations only) on

page 2-3

• Prerequisites for database file storage locations (new installations only) on page 2-4

• Prerequisites for management server information on page 2-5

• Determining memory heap size on page 2-6

• Prerequisites for database file backups or export locations on page 2-7

Prerequisites for HCS server unattended installationBefore performing an unattended installation of HCS server, review system requirements information.

• Stop Tuning Manager services:

HINST_IGNORE_NETWORKING_CHECK

Specify whether to continue the installation when the host name or IP address that was specified in HINST_IPADDRESS is not communicating with the network.



FALSE

HINST_IGNORE_VIRTUAL_MEMORY_CHECK

Specify whether to continue the installation when there is insufficient virtual memory.



FALSE

#1You cannot specify this property in Solaris (SPARC) environments.

#2program-files-folder indicates the following location:

• For Windows x86: The folder specified in the Windows system environment variable %ProgramFiles%

• For Windows x64: The folder specified in the Windows system environment variable %ProgramFiles(x86)%

#3When installing in a cluster environment, default values are not specified automatically. You must explicitly specify values. When installing on the standby node, you do not need to specify this property.

#4When installing in a cluster environment, you must specify this property on both the executing and standby nodes.

#5If you perform an installation on the standby node in a cluster environment, databases are not backed up or exported.

#6If you specify this property in a cluster environment, it is ignored.



If a version earlier than 6.3 is installed on the same management server, stop the Tuning Manager Agent for SAN Switch service.

If Tuning Manager is remotely connected, stop the Tuning Manager server service.

• Run Tiered Storage Manager tasks when upgrading from 7.1.0 or earlier:

If there are incomplete tasks (standby, running, being cancelled), go to the Tasks & Alerts tab and execute or cancel the tasks. After upgrading, register the canceled tasks as new.

• Determine the values that are set during installation

• Verify that the execution result file (HInstReport.txt) is closed.

The prerequisite checker verifies whether the installation destination satisfies the requirements.

To access the prerequisite checker in Windows, use the integrated installation media or run the prereqchk.exe file in DVD-drive:\HCS\

To access the prerequisite checker in Solaris or Linux, run the prereqchk.sh file in DVD-ROM-mount-point/HCS/Platform-name/

For system requirements, see the Hitachi Command Suite Release Notes. To check task status, see the Hitachi Command Suite User Guide.



• Installing the server in a Windows environment (unattended installation) on page A-5

• Installing the server in a Solaris or Linux environment (unattended installation) on page A-6

Installing the server in a Windows environment (unattended installation)

You can perform unattended installations in Windows environments.

To perform an unattended installation of the server in a Windows environment:

1. Log on to the Windows operating system with administrator permissions.

2. Open a command window or a PowerShell window and navigate to DVD-drive:\HCS\.

In Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2, use the command prompt or PowerShell window you opened as the administrator.


Note: This is the location of the installer program (setup.exe).



In a command window:

> setup.exe /v"/qr property-name=value"

To specify a value that contains a space, add a backslash and quotation mark (\") before and after the value.

In a PowerShell window:

> setup.exe /v`"/qr property-name=value`"

If you specify multiple properties, use a space to separate each property-name=value entry.

To specify a value that contains a space, add a slash and quotation mark (/") before and after the value.

When the installation completes, the result is written in the HInstReport.txt file on the desktop. If you see SUCCESS in the summary section of the file, the installation was successful.



• HCS server unattended installation properties and settings on page A-2



Installing the server in a Solaris or Linux environment (unattended installation)

You can perform unattended server installations on Solaris or Linux.

To perform an unattended installation of the server in a Solaris or Linux environment:

1. Log on to the Solaris or Linux operating system as the root user.

2. Open a shell window and navigate to DVD-ROM-mount-directory/HCS/platform-name



#./install.sh -s property-name=value

To specify multiple properties, use a space to separate each property-name=value entry.

To specify a value that contains a space, add a backslash and quotation mark (\") before and after the value.

Note: This is the directory that holds the installer program (install.sh).


When the installation completes, the result is written in the HInstReport.txt file in the /tmp directory. If you see SUCCESS in the summary section of the file, the installation was successful.



• HCS server unattended installation properties and settings on page A-2



Performing a Device Manager agent unattended installation

You can automate agent installation by creating and executing a script file. Unattended installation can be used when installing on multiple hosts with the same conditions. By creating a settings file (HDVMAgent.conf), you can also perform basic setup functions during the unattended installation.

When setting up an unattended installation, note the following:

• For an overwrite installation, version 04-10 or later of the Device Manager agent must be installed.

• In Windows, manually add a firewall exception after completing the installation.

• LocalSystem is set for the agent service account.

Prerequisites for Device Manager agent unattended installationsBefore performing an unattended installation of the Device Manager agent, verify the host requirements and system prerequisites and set up the installation machine.

You must have the Device Manager agent installation folder ready for the new installation and configure the settings for basic setup by editing the HDVMAgent.conf file to provide basic setup values that are accessed during the unattended installation.

The HDVMAgent.conf file is stored in the following location:

• In Windows: DVD-drive:\AGENTS\HDVM\Windows\HDVMAgent.conf

• In UNIX: DVD-ROM-mount-directory/AGENTS/HDVM/platform-name/HDVMAgent.conf

If a property is not specified, the default value is used. Table A-2 Data set in HDVMAgent.conf on page A-8 shows these default values.

Note: If HDVMAgent.conf is stored on a write-protected medium such as an installation DVD, copy the directory that contains the file to a writable location and edit HDVMAgent.conf.



Table A-2 Data set in HDVMAgent.conf

Property Name Details Default value

serverIP (required) Specify the IP address or host name of the Device Manager server.

None

serverPort (required)

Specify the port number of the Device Manager server.

2001

HiScanPeriod (required)

Specify the HiScan execution interval.

• H: Once an hour

• D: Once a day

• W,SUN: Once every Sunday

• W,MON: Once every Monday

• W,TUE: Once every Tuesday

• W,WED: Once every Wednesday

• W,THU: Once every Thursday

• W,FRI: Once every Friday

• W,SAT: Once every Saturday

• N: No interval

D

HiScanSchedule (optional)

If you specify a value other than N for HiScanPeriod, specify the timing for executing the HiScan command using one of the following methods:

To specify execution at a scheduled time, use the following format:

• Once an hour: Specify the time as mm.

• Once a day: Specify the time as hh:mm.

• Once a week: Specify the time as hh:mm.

To specify execution at random times:

Specify this option in an environment where multiple hosts are connecting to the Device Manager server to execute the HiScan command at random times on the hosts. This can decrease Device Manager loads.

Specify the HiScan start and end time in the following format:

• Once an hour: Specify the start and end time as mm-mm.

• Once a day: Specify the start and end time as hh:mm-hh:mm.

• Once a week: Specify the start and end time as hh:mm-hh:mm.

If the start time is later than the end time, the end time is set for the next day or hour (example: 23:00-1:00 or 45-15).

If the start time and the end time are the same, HiScan executes as if you had specified a scheduled time.

2:30


For a complete list of system requirements, see the Hitachi Command Suite Release Notes.



• Installing a Device Manager agent on a Windows host (unattended installation) on page A-9

• Installing a Device Manager agent on a UNIX host (unattended installation) on page A-10

Installing a Device Manager agent on a Windows host (unattended installation)

An unattended installation is one that has the user input stored in a script file and then read from that file.

To perform an unattended installation in Windows:

1. Log on to the Windows operating system with administrator permissions.

2. Open a command window or a PowerShell window, and change the directory to the location of the installer program (setup.exe).

In Windows Server 2008 or Windows Server 2008 R2, use the command prompt or PowerShell window you opened as the administrator.


> start /WAIT setup.exe /s [Device-Manager-agent-installation-folder] [/u]

Specify Device-Manager-agent-installation-folder for new installations, only. If you omit this folder name, the Device Manager agent is installed in the default location.

Specify /u to perform basic setup during installation.

4. To verify the success of the installation, enter the following command:

configOverwrite (optional)

Specify whether to overwrite the settings during an overwrite installation.

enable: Overwrite the settings

disable: Do not overwrite the settings

Caution:

If you enable overwriting installation of the Device Manager agent, the user ID and password used for communication with the Device Manager server are set to the default.

disable

Property Name Details Default value

Note: To perform basic setup tasks during the installation, change the directory to the location of the copy you made of the setup.exe file.



> echo %ERRORLEVEL%

If the return value is 0x00, the installation completed successfully.



• Prerequisites for Device Manager agent unattended installations on page A-7

• Verifying the Device Manager agent unattended removal on page A-14


Installing a Device Manager agent on a UNIX host (unattended installation)

An unattended installation is one that has the user input stored in a script file and then read from that file.

To perform an unattended installation in UNIX:

1. Log in to the UNIX operating system as the root user.

2. Open a shell window, and change the directory to the location of the installer program (install.sh).


# install.sh -s [-u]

Specify the -u option to perform basic setup during installation.

4. To check the success of the installation, enter the following command:

# echo $?

If the return value is 0x00, the installation completed successfully.

When starting the installer from a DVD-ROM, these characters can be specified in the mount path: A to Z, a to z, 0 to 9, underscores (_), forward slashes (/).



• Prerequisites for Device Manager agent unattended installations on page A-7

• Verifying Device Manager agent unattended installations on page A-11


Note: To perform basic setup tasks during the installation, change the directory to the location of the copy you made of the install.sh file.


Verifying Device Manager agent unattended installationsWhen unattended installation of the Device Manager agent completes, check the returned values.

You can verify the returned values listed in Table A-3 Device Manager agent unattended installation returned values on page A-11 to determine the result.

Table A-3 Device Manager agent unattended installation returned values

Return value# Description Action

0x00 Ended normally. None.

0x90 A failure occurred during the installation of the Device Manager agent.

The following are likely causes:

• There is insufficient free disk space. Secure the required disk space and perform the installation again.

• The host operating system is not supported. Verify that the operating system is supported.

• A program other than Device Manager agent is being installed or removed. Wait for the current process to finish and perform the installation again.

• The software that provides the Java execution environment cannot run.

Verify that the updates required for the Device Manager agent have been applied to the host system. Also, make sure that the software that provides the Java execution environment is installed in the location indicated by the installation path specified in the property server.agent.JRE.location of the server.properties file.

In UNIX, the following causes are also possible:

• The software that provides a Java execution environment is not installed. Install the software, then retry installing the Device Manager agent.

• The permission for the installer execution file could not be changed. Move all files and subdirectories in the directory where the installer execution file location to a directory where the permission can be changed, and then execute the installation again.

0x91 The installation command contains a syntax error.

The syntax of the installation command argument is incorrect. Correct the syntax, and then perform the installation again.

The specified value for the installation directory is not correct.

The installation directory has been specified using characters that cannot be used, or exceeds 64 bytes. Correct the setting, and then perform the installation again.



0x92 HDVMAgent.conf is not stored in the directory in which the installer execution file is stored, or HDVMAgent.conf contains some setting errors.

Installation failed. Perform the following, depending on the cause of the error:

• HDVMAgent.conf is not stored in the directory in which the installer execution file is stored.

Store HDVMAgent.conf in the directory in which the installer execution file is stored and execute the installation again.

• HDVMAgent.conf contains some setting errors.

Correct the errors and execute the installation again.

0x93 The Device Manager agent was successfully installed, but the settings for linking to other program products could not be applied.

For an environment in which Protection Manager Console has been installed, execute hptmguiinst.exe or hptmguiinst.sh. Check the error message, take the appropriate action to correct the error, and then perform the installation again.

For Solaris or HP-UX: The installation of the Global Link Manager agent may have failed. Execute the installation again.

0x95 The Device Manager agent functionality setup succeeded. However, an error may have occurred while setting up Replication Manager application agent functionality.

Verify that the operating system is supported and the required updates have been applied, and then perform installation again.

0x96 The user attempting this operation does not have Administrator permissions.

Retry the operation using a user ID with Administrator permissions.

0x98 You cannot downgrade the Device Manager agent because a newer version of the Device Manager agent is installed.

None.

0x99 The Device Manager agent or a related program is running.

Take action by following the KAIC25111-W to KAIC25113-W messages.

0x9A setup.exe may not have started correctly, or a user may have executed an internal command manually.

Take action by following the KAIC25156-E message.



Performing a Device Manager agent unattended removalThe unattended removal of an agent eliminates the need for user responses during agent removal. This function is useful when agents are installed on multiple hosts.

To perform an unattended agent removal, you create and execute a script file.

Removing a Device Manager agent from a Windows host (unattended removal)

You can perform an unattended removal in a Windows environment.

To remove the Device Manager agent:

1. Log in to the Windows operating system with a user ID that has administrator permissions.

2. Copy the following file to any location:

Device-Manager-agent-installation-folder\bin\agent_uninstShortcut.bat

3. Execute the following command at the command prompt:

copy-destination-folder\agent_uninstShortcut.bat /s

4. To check the success of the removal, enter the following command:

> echo %ERRORLEVEL%

If the returned value is 0x00, the Device Manager agent is successfully removed.

5. Delete the copy of agent_uninstShortcut.bat you made in step 2.



0x9D A failure occurred while connecting to the Device Manager server specified in HDVMAgent.conf.

Use the hdvmagt_setting command to specify the IP address or host name of the Device Manager server again.

#Return values are output in hexadecimal.


Note: In Windows Server 2008 or Windows Server 2008 R2, use the command prompt you started as administrator.



Removing a Device Manager agent from a UNIX host (unattended removal)

You can perform an unattended removal in a UNIX environment.

To remove a Device Manager agent:

1. Log in to UNIX as the root user.

2. Open a shell, and enter the following command:

Solaris, Linux, HP-UX

/opt/HDVM/HBaseAgent/bin/.uninstall.sh -s

AIX

/usr/HDVM/HBaseAgent/bin/.uninstall.sh -s

3. To check the success of the removal, enter the following command:

# echo $?

If the value returned is 0x00, the Device Manager agent is successfully removed.



Verifying the Device Manager agent unattended removalWhen unattended removal of the Device Manager agent completes, check the returned values.

You can verify the returned values shown in Table A-4 Device Manager agent unattended removal returned values on page A-14 to determine the result.

Table A-4 Device Manager agent unattended removal returned values


0x00 Normal termination --


0x90 Removing the Device Manager agent failed.

The following are likely causes:

• A program other than the Device Manager agent is either being installed or removed. Wait for the current process to finish, and then attempt to remove the Device Manager agent again.

• A process for removing a related program failed.

• The software that provides the Java execution environment cannot run.

Verify that the updates required for the Device Manager agent have been applied to the host system.

Verify that the software that provides the Java execution environment is installed in the location specified in property server.agent.JRE.location of the server.properties file.

0x91 The command entered to remove the agent software contains a syntax error.

The syntax of the command argument is not correct. Correct the syntax, and then repeat the command.

0x93 A failure occurred while removing a program other than the Device Manager agent

The failure may have occurred when the Global Link Manager agent was being removed. Try to remove it again.

0x96 The user attempting this operation does not have Administrator permissions.

Retry the operation by using a user ID that has Administrator permissions.

0x99 The Device Manager agent or a related program is running.

Follow the KAIC25111-W to KAIC25113-W messages and act accordingly.

0x9B The current directory is in the Device Manager agent installation directory. This return value may be displayed in UNIX.

Move the current directory to another directory, such as the root directory, and then try to remove the Device Manager agent again.

#Return values are output in hexadecimal.




B

Ports B–1Hitachi Command Suite Installation and Configuration Guide

Ports

This appendix describes the ports used for Hitachi Command Suite (HCS).

For a complete list of system requirements, see the Hitachi Command Suite Release Notes.

□ HCS server ports


B–2 Ports

HCS server portsEnsure that HCS ports do not overlap with those used by other programs on the management server.

Some ports can overlap with ports temporarily assigned by the operating system. You can stop ports from being temporarily assigned by setting the ports in the operating system services file.

These ports are described in Table B-1 Port numbers used by HCS on page B-2.


Table B-1 Port numbers used by HCS

Port Number Description If the port is in use by another product

162/udp Device Manager ports The settings cannot be changed from Device Manager.

Change the settings for the product that uses this port or follow the message that is output during installation to disable SNMP trap reception.

2001/tcp

2443/tcp

Change the settings for the product that uses this port or change Device Manager settings before starting the Device Manager server.

If another product is using this port, the following message is output to the event log file and Device Manager does not start: KAIC00114-E An attempt to start the HTTP server on port "port-number" failed.

5983/tcp

5988/tcp

5989/tcp

23055/tcp

Change the settings for the product that uses this port or change Device Manager settings.

20352/tcp Tiered Storage Manager ports

Change the settings for the product that uses this port or change Tiered Storage Manager settings.

23015/tcp to 23018/tcp

23025/tcp

23026/tcp

23032/tcp

Common Component ports Change the settings for the product that uses this port or change Common Component settings.

NOTE: If Common Component is installed and you changed its ports, you do not need to reset the values.

23050/tcp

23051/tcp

23052/tcp

Host Data Collector ports Change the settings for the product that uses this port.

Ports B–3Hitachi Command Suite Installation and Configuration Guide

45001/tcp to 49000/tcp

Common Component ports The settings cannot be changed from the Common Component.

Change the settings for the product using this port.

Port Number Description If the port is in use by another product


B–4 Ports

CA KD E F G H I J L M N O P Q R S T U V W X Y# B ZA C D E F G H I J L M N O P R S T U V

Glossary–1Hitachi Command Suite Installation and Configuration Guide

Glossary

This glossary defines the special terms used in this document. Click the desired letter at the bottom of each page to display the glossary entries that start with that letter.

A

allocated volume

A volume for which one or more host paths are defined.

C

cache

A set of RAM (Random Access Memory) modules used to store data temporarily.

capacity

The amount of data storage space available on a drive or storage system. Capacity is generally measured in MB, but it can also be measured in other units such as TB and PB, depending on the total storage space.

CCI

Command Control Interface. Software used to control volume replication functionality (such as TrueCopy or ShadowImage) by means of commands issued from a host to a storage system. A command device must be set up in the storage system to enable the storage system to receive commands from CCI.

In an open system, Replication Manager uses the CCI configuration definition files to modify copy pair configurations and to acquire configuration information. Copy pair modification processing, such as splitting and resynchronizing copy pairs, is executed on the storage system via CCI.



Glossary–2

CLI

Command-line interface

CLPR

Cache Logical Partition

copy pair

A primary and secondary volume pair linked by the volume replication functionality of a storage system.

CSV

Comma separated value

CU (control unit)

A virtual control unit created in an enterprise-class storage system. Also called a CU image. Each volume created in a storage system is connected to a single CU, and a number is assigned to each CU for identifying its volumes. Therefore, volumes (LDEVs) in a storage system are specified by the CU number (CU#) and LDEV number.

D

data drive

A physical data storage device that can be either a hard disk drive (HDD) or a flash (solid-state) drive.

data pool

One or more logical volumes designated to temporarily store original data. When a snapshot is taken of a primary volume, the data pool is used if a data block in the primary volume is to be updated. The original snapshot of the volume is maintained by storing the changeable data blocks in the data pool.

DB

Database

device

A physical or logical unit with a specific function.

DHCP

Dynamic Host Configuration Protocol

DKCMAIN

Disk controller main



DKP

Disk processor

DKU

Disk unit

DP-VOL

Dynamic Provisioning virtual volume. A virtual volume with no memory space used by Dynamic Provisioning.

E

external volume

A logical volume whose data resides on drives that are physically located in an externally connected storage system.

F

FC

Fibre Channel

G

GUI

Graphical user interface

H

HBA

Host bus adapter

HDP

Hitachi Dynamic Provisioning. An approach to managing storage. Instead of reserving storage, the system removes capacity from the available pool only when data is actually written to the drive.

HDT

Hitachi Dynamic Tiering

host group

A means of segregating hosts by operating system.



Glossary–4

HSD

Host storage domain. A group defined in Device Manager that is used to strengthen the security of volumes in storage systems. By associating and grouping hosts and volumes by storage system port, host storage domains can be used to restrict access from hosts to volumes.

Device Manager defines the host groups set up with the storage system LUN security function as host storage domains. Host storage domains for storage systems that do not have host groups are defined in the same manner as if they had been set with the LUN security function.

HTML

Hypertext Markup Language

HTTP

Hypertext Transfer Protocol

HTTPS

Hypertext Transfer Protocol Secure

I

internal volume

A logical volume whose data resides on drives that are physically located within the storage system. See also external volume.

IO

Input/output

IOPS

I/O per second

IP

Internet protocol

J

JRE

Java Runtime Environment

JVM

Java Virtual Machine



L

LAN

Local area network

LDAP

Lightweight Directory Access Protocol

LDEV (logical device)

A volume created in a mainframe storage system. See also LU.

LDKC

Logical disk controller

LU (logical unit)

A volume created in an open storage system. See also LDEV.

LUN (logical unit number)

A management number assigned to an LU in a storage system. A LUN is a number assigned to identify an LU for the port in the storage system to which the LU is connected, either by the port or by the host group assigned to the port. An open system host uses a LUN to access a particular LU.

LUSE

LU size expansion

M

management client

A computer used to operate HCS. A Web client or CLI client can be used.

N

NAS

Network-attached storage

NIC

Network interface card



Glossary–6

O

OS

Operating system

P

pair status

The current status of the copy pair.

pool

A set of volumes that are reserved for storing Copy-on-Write Snapshot data or Dynamic Provisioning write data.

pool volume (pool-VOL)

A logical volume that is reserved for storing snapshot data for Copy-on-Write Snapshot operations or write data for Dynamic Provisioning.

PVOL (primary volume)

The source volume that is copied to another volume using the volume replication functionality of a storage system.

properties files

The files that define the operating environment. The operating environment can be modified by changing the appropriate properties files.

R

RACF (Remote Access Control Facility)

Functionality for controlling user authentication and resource access on the mainframe host.

RADIUS

Remote Authentication Dial In User Service

RAID

Redundant array of inexpensive disks

RAID level

The type of RAID implementation. RAID levels include RAID 0, RAID 1, RAID 2, RAID 3, RAID 4, RAID 5, and RAID 6.



refresh

To update the database using the most recent information.

S

SAN

Storage area network

SNMP

Simple Network Management Protocol

SSD

Solid-state drive

SSL

Secure Sockets Layer

SVOL (secondary volume)

The copy destination volume of two volumes that are associated in a copy pair by a storage system volume replication functionality.

T

tiered storage

A layered structure of performance levels, or tiers, that matches data access requirements with the appropriate performance tiers.

U

unallocated volume

A volume for which no host paths are assigned.

URL

Uniform Resource Locator

V

VMA

Volume management area

VOLSER

The label of a volume assigned by the mainframe host.



Glossary–8

volume

A collective name for the logical devices (LDEVs) and logical units (LUs) that are created in a storage system.

Index–1Hitachi Command Suite Installation and Configuration Guide

Index

Aagent

modifying agent services 3–4modifying properties 3–16registering firewall exceptions 3–17resetting service execution user 3–16

agent configurationCommand Control Interface 3–5HiScan execution 3–5

agent installationAIX precautions 3–10HP-UX prerequisites 3–12Linux prerequisites 3–12prerequisites 3–2, 3–4, 3–6, 3–8server information 3–4Stack Execution Disable function 3–11unattended A–7, A–9, A–11unattended Windows A–9UNIX 3–15Windows 3–14

agent removal 4–3prerequisites 4–3unattended A–13, A–14unattended UNIX A–14unattended Windows A–13UNIX 4–5Windows 4–4

agent unattended installationproperties A–7

agent unattended removal A–13UNIX A–14Windows A–13

Bbuilt-in user groups 2–30

CCommand Control Interface

agent configuration 3–5Common Component parameters

Red Hat Enterprise Linux 2–19

Solaris 10 2–13, 2–15Solaris 9 2–10SUSE Linux Enterprise Server 2–20, 2–22

copy pair management 1–3custom tiers 2–9

Ddatabase backup

server installation 2–7database destination

server installation 2–4Device Manager agent 1–4Device Manager parameters

Red Hat Enterprise Linux 2–17, 2–19Solaris 10 2–13, 2–15Solaris 9 2–10SUSE Linux Enterprise Server 2–20, 2–22

Ffirewall exceptions

registering 3–17

HHDVMAgent.conf A–7HInstReport.txt A–6HiScan command 3–5horcm

modifying 3–4Host Data Collector 1–4HP-UX prerequisites

agent installation 3–12

Iinstall.sh A–6, A–9, A–10installation

upgrade 1–5installation folder

agent 3–4


Index–2

Kkernel parameters

Linux 2–10Red Hat Enterprise Linux 2–17Solaris 2–10Solaris 10 2–13, 2–15Solaris 9 2–10SUSE Linux Enterprise Server 2–20

LLinux

agent installation prerequisites 2–9kernel parameters 2–10server installation 2–26server installation prerequisites 2–2, 2–3, 2–

9shell restrictions 2–10

Linux prerequisitesagent installation 3–12firewall changes 3–12

Linux unattended installationserver A–6

Mmanagement client 1–2management server 1–3

installation information 2–5memory heap size

server installation 2–6

Ppassword

changing 2–27port number validation

server installation 2–9

RRed Hat Enterprise Linux

:Tuning Manager parameters 2–17/etc/security/limits.conf 2–19/etc/sysctl.conf 2–17Common Component parameters 2–17, 2–

19Device Manager parameters 2–17, 2–19kernel parameters 2–17registering firewall exceptions 2–24Replication Manager Software parameters 2–

17, 2–19shell restrictions 2–19Tiered Storage Manager parameters 2–17,

2–19Tuning Manager Software parameters 2–22

refreshing storage systemsserver installation 2–32

registering firewall exceptionsRed Hat Enterprise Linux 2–24SUSE Linux Enterprise Server 2–24

removing agent 4–3prerequisites 4–3unattended A–13UNIX 4–5Windows 4–4

removing serverLinux 4–3Solaris 4–3Windows 4–2

Replication Manager Softwareoperation permissions 2–29

Replication Manager Software parametersRed Hat Enterprise Linux 2–17, 2–19Solaris 10 2–13, 2–15Solaris 9 2–10SUSE Linux Enterprise Server 2–20, 2–22

resetting user accountserver installation 2–33

resource groupsserver installation 2–32, 2–37

returned valuesunattended installation agent A–11unattended removal agent A–14

Sserver installation

assigning resource groups 2–32, 2–37changing kernel parameter values 2–23changing shell restriction values 2–23creating user 2–28database backup 2–7database destination 2–4destination 2–3Device Manager roles 2–28Linux 2–26management server 2–5memory heap size 2–6port number validation 2–9prerequisites 2–2, 2–24refreshing storage systems 2–32registering licenses 2–27Replication Manager Software operation

permissions 2–29resetting user account 2–33Solaris 2–26system account password 2–27tasks after installation 2–26unattended A–2, A–4, A–6unattended Linux A–6unattended Windows A–5user account permissions 2–29user management permissions 2–29verifying successful installation 2–27Windows 2–25

server removal 4–2Linux 4–3Solaris 4–3Windows 4–2

server settings

Index–3Hitachi Command Suite Installation and Configuration Guide

unattended installation A–2server unattended installation

prerequisites A–4properties A–2

service execution userresetting 3–16

setup.exe A–5, A–9, A–10shell restrictions

Linux 2–10Red Hat Enterprise Linux 2–19SUSE Linux Enterprise Server 2–20, 2–22

short namesautomatic generation 3–8

Solarisagent installation prerequisites 2–9, 3–9kernel parameters 2–10server installation 2–26server installation prerequisites 2–2, 2–3, 2–

9, 2–10Solaris 10

/etc/project file 2–13/etc/system file 2–15Common Component parameters 2–13, 2–

15Device Manager parameters 2–13, 2–15kernel parameters 2–13, 2–15Replication Manager Software parameters 2–

13, 2–15Tiered Storage Manager parameters 2–13,

2–15Tuning Manager parameters 2–13, 2–15

Solaris 9Common Component parameters 2–10Device Manager parameters 2–10etc/system file 2–10kernel parameters 2–10Replication Manager Software parameters 2–

10Tiered Storage Manager parameters 2–10Tuning Manager parameters 2–10

storage tiers 2–9SUSE Linux Enterprise Server

/etc/security/limits.conf 2–22/etc/sysctl.conf 2–20Common Component parameters 2–20, 2–

22Device Manager parameters 2–20, 2–22registering firewall exceptions 2–24Replication Manager Software parameters 2–

20, 2–22shell restrictions 2–20, 2–22Tiered Storage Manager parameters 2–20,

2–22Tuning Manager Software parameters 2–20

TTiered Storage Manager

property files 2–9Tiered Storage Manager parameters

Red Hat Enterprise Linux 2–17, 2–19Solaris 10 2–13, 2–15Solaris 9 2–10SUSE Linux Enterprise Server 2–20, 2–22

Tuning Manager parametersRed Hat Enterprise Linux: 2–17Solaris 10 2–13, 2–15Solaris 9 2–10

Tuning Manager Software parametersRed Hat Enterprise Linux 2–22SUSE Linux Enterprise Server 2–20

Uunattended agent removal

UNIX A–14Windows A–13

unattended installationagent A–7, A–9, A–11agent properties A–7agent returned values A–11Linux server A–6server A–2, A–4, A–6server prerequisites A–4server properties A–2server settings A–2Windows agent A–9Windows server A–5

unattended removalagent A–13, A–14agent returned values A–14UNIX agent A–14Windows agent A–13

UNIXagent installation 3–15agent installation prerequisites 3–2

UNIX unattended removalagent A–14

user accountassigning Device Manager roles 2–28assigning permissions 2–29creating 2–28

user groupsbuilt-in user groups 2–30

user management permissionsserver installation 2–29

WWindows

additional installation files 1–4agent execution user 3–16agent firewall exceptions 3–17agent installation 3–14agent installation prerequisites 3–2, 3–8remote access 3–8server installation 2–25server installation prerequisites 2–2

Windows (x64)server installation prerequisites 2–2, 2–3

Windows (x86)


Index–4

server installation prerequisites 2–2, 2–3Windows Remote Desktop functionality 3–8Windows unattended installation

agent A–9server A–5

Windows unattended removalagent A–13


MK-90HC173-05

Hitachi Data Systems

Corporate Headquarters750 Central ExpresswaySanta Clara, California 95050-2627U.S.A.Phone: 1 408 970 [email protected]

Asia Pacific and Americas750 Central ExpresswaySanta Clara, California 95050-2627U.S.A.Phone: 1 408 970 [email protected]

Europe HeadquartersSefton ParkStoke PogesBuckinghamshire SL2 4HDUnited KingdomPhone: + 44 (0)1753 [email protected]