HiCommand DeviceManager PDF

Hitachi HiCommand Device Manager
Web Client Users Guide
2004 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED

Notice: No part of this publication may be reproduced or transmitted in any form or by any
means, electronic or mechanical, including photocopying and recording, or stored in a
database or retrieval system for any purpose without the express written permission of
Hitachi Data Systems Corporation.
Hitachi Data Systems reserves the right to make changes to this document at any time
without notice and assumes no responsibility for its use. Hitachi Data Systems products and
services can only be ordered under the terms and conditions of Hitachi Data Systems
applicable agreements. All of the features described in this document may not be currently
available. Refer to the most recent product announcement or contact your local Hitachi
Data Systems sales office for information on feature and product availability.
This document contains the most current information available at the time of publication.
When new and/or revised information becomes available, this entire document will be
updated and distributed to all registered users.
Trademarks
Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd., and the
Hitachi Data Systems design mark is a trademark and service mark of Hitachi, Ltd.
HiCommand, Hitachi Freedom Storage, Lightning 9900, Thunder 9200, and Thunder 9500 are
trademarks of Hitachi Data Systems Corporation in the United States and other countries.
AIX and AT are registered trademarks of International Business Machines Corporation.
ESCON and FICON are registered trademarks of International Business Machines Corporation.
InterSAN is a trademark of InterSAN in the United States and other countries.
Microsoft, Windows, and Windows NT are registered trademarks, and Windows Server is a
trademark, of Microsoft Corporation in the United States and other countries.
Netscape and Netscape Navigator are registered trademarks of Netscape Communications
Corporation in the United States and other countries.
NetWare is a registered trademark of Novell, Incorporated.
BSAFE is a registered trademark or trademark of RSA Security, Inc. in the United States
and/or other countries. RC2, RC4, and RSA are registered trademarks or trademarks of RSA
Security, Inc. in the United States and/or other countries. HiCommand Device Manager
includes RSA BSAFE Cryptographic software from RSA Security, Inc.
Java, Java Runtime Environment (JRE), Solaris, SPARC, and StorEdge are trademarks, and
Sun is a service mark, of Sun Microsystems, Inc.
VERITAS is a trademark of VERITAS Software Corp.
Hitachi HiCommand Device Manager Web Client Users Guide
iii
HP-UX is a registered trademark of the Hewlett-Packard Development Company, L.P.

UNIX is a registered trademark of The Open Group in the United States and other countries.
Linux is a registered trademark of Linus Torvalds.
This product includes software developed by Borland Software Corp.
The file interclient.jar was extracted from InterClient Solaris version 2.0 as of November
15, 2002. Original code was created by InterBase Software Corp and its successors, and
portions were created by Borland/Inprise, Copyright Borland/Inprise. All Rights Reserved.
All other brand or product names are or may be registered trademarks, trademarks or
service marks of and are used to identify products or services of their respective owners.
Notice of Export Controls

Export of technical data contained in this document may require an export license from the
United States government and/or the government of Japan. Please contact the Hitachi Data
Systems Legal Department for any export compliance questions.
Document Revision Level
iv
Revision
Date
Description
MK-91HC001-P
August 2001
Preliminary Release
MK-91HC001-0
September 2001
Initial Release
MK-91HC001-1
November 2001
Revision 1, supersedes and replaces MK-91HC001-0
MK-91HC001-2
January 2002
MK-91HC001-3
February 2002
MK-91HC001-4
June 2002
MK-91HC001-5
November 2002
MK-91HC001-6
May 2003
MK-91HC001-7
September 2003
MK-91HC001-8
February 2004
MK-91HC001-9
February 2004
MK-91HC001-10
April 2004
MK-91HC001-11
September 2004
Preface
Source Documents for this Revision
3020-3-E61(E) (06.15.04) (t-code)
SSD-94HC076-Ed.1(07.30.04)(V3.5)(q-code)
Changes in this Revision
Added information to the 9900V Storage Navigator Requirements section in Chapter 4.
Added information to the Viewing all alerts section in Chapter 5.
Added information to the Launching Protection Manager section in Chapter 5.
Added information about the Link-and-Launch function for the 9500V Disk Array
Management Program (DAMP).
Added Instructions for creating a configuration file for CCI.
Added allocated group information to Chapter 8.
Updated approximately 60 figures.
Added information on linkage with related products (see section 4.3).
Added information about logging in to Device Manager (see section 4.5).
Added information on importing a security certificate into a browser (see section 5.7.9).
Added notes on Copy Pair operations (see section 9.7.3).
Added tables to Create Array Group information (see section 10.4).
Referenced Documents
HiCommand Device Manager Agent Installation Guide (MK-92HC019)
HiCommand Device Manager Server Installation and Configuration Guide (MK-91HC002)
HiCommand Device Manager Command Line Interface (CLI) Users Guide (MK-91HC007)
HiCommand Tuning Manager Reference Guide (MK-92HC022)
Hitachi Thunder 9500 V Series Resource Manager 9500V Users Guide (MK-92DF605)
Hitachi Thunder 9200 Resource Manager 9200 Users Guide (MK-90DF505)
Hitachi Thunder 9500 V Series QuickShadow 9500V Users Guide (MK-92DF666)
Hitachi Lightning 9900 V Series Command Control Interface (CCI) User and Reference
Guide (MK-90RD011)
Hitachi Dynamic Link Manager (HDLM) Users Guide for Solaris Systems (MK-92DLM114)
Hitachi Lightning 9900 V Series LUN Manager Users Guide (MK-92RD105)
Hitachi Lightning 9900 LUN Manager Users Guide (MK-90RD003)
Hitachi Lightning 9900 V Series and Lightning 9900 Command Control Interface (CCI)
User and Reference Guide (MK-90RD01)
vi
Hitachi Lightning 9900 V Series LUN Manager Users Guide (MK-92RD105)
Hitachi Lightning 9900 V Series TrueCopy User and Reference Guide (MK-92RD108)
Hitachi Lightning 9900 V Series ShadowImage Users Guide (MK-92RD110)
Hitachi TagmaStoreTM Universal Storage Platform Universal Volume Manager Users

Guide (MK-94RD220)
Preface
Preface
This document describes and provides instructions for using the HiCommand Device
Manager Web Client software to manage storage on the Hitachi Freedom Storage and Sun
StorEdge RAID subsystems. This document assumes that the user:
has a background in data processing and understands peripheral storage device

subsystems and their basic functions.
has read and understands the user guides for the subsystem:
Hitachi Lightning 9900 V Series User and Reference Guide
Hitachi Lightning 9900 User and Reference Guide
Hitachi Thunder 9500 V Series User and Reference Guide
Hitachi Thunder 9200 User and Reference Guide
Sun StorEdge T3 Disk Tray Configuration Guide
has read and understands the user guide(s) for the subsystem configuration functions
(e.g., Lightning 9900 V Series LUN Manager Users Guide, Thunder 9200 Resource
Manager 9200 Users Guide, StorEdge T3 Disk Tray Configuration Guide).
has read and understands the user guide(s) for the data management functions (e.g.,
Hitachi Lightning 9900 Virtual LVI/LUN Users Guide, Hitachi Lightning 9500 V Series
ShadowImage Users Guide).
is familiar with the operating system which hosts the HiCommand Device Manager Web
Client software (e.g., Solaris OS, Windows NT OS).
Notes:
The term 9900V refers to the entire Lightning 9900 V Series subsystem family (e.g.,
9980V, 9970V), unless otherwise noted. The term 9900 refers to the entire Lightning
9900 subsystem family (e.g., 9960, 9910), unless otherwise noted. The term 9500V refers
to the entire Thunder 9500V subsystem family (e.g., 9570V, 9580V), unless otherwise noted.
The use of HiCommand Device Manager and all Hitachi Data Systems products is governed
by the terms of your agreement(s) with Hitachi Data Systems.
The use of the Sun StorEdge T3 array and all other Sun products is governed by the terms of
your license agreement(s) with Sun Microsystems.
Software Version
This document revision applies to HiCommand Device Manager version 3.5 and higher.
vii
Conventions
This manual uses the following conventions:
1 KB (kilobyte) is 1,024 bytes.
1 MB (megabyte) is 1,0242 bytes.
1 GB (gigabyte) is 1,0243 bytes.
1 TB (terabyte) is 1,0244 bytes.
Comments
Please send us your comments on this document. Make sure to include the document title,
number, and revision. Please refer to specific section(s) and paragraph(s) whenever possible.
E-mail: doc.comments@hds.com
Fax: 858-695-1186
Mail:
Technical Writing, M/S 35-50
Hitachi Data Systems
10277 Scripps Ranch Blvd.
San Diego, CA 92131
Thank you! (All comments become the property of Hitachi Data Systems Corporation.)
viii
Preface
Contents
Chapter 1
Overview of HiCommand Device Manager .......................................................................1

1.1
1.2
1.3
1.4
1.5
1.6
Chapter 2
Overview of HiCommand Device Manager .................................................. 2

1.1.1 Overview of Hitachi ShadowImage ................................................... 3
1.1.2 Overview of Hitachi TrueCopy ........................................................ 4
1.1.3 Overview of Hitachi QuickShadow (9500V Only) ................................... 5
1.1.4 Overview of Command Control Interface (CCI) ..................................... 6
New Functions in HiCommand Device Manager 3.5 ....................................... 7
Related Software Products...................................................................... 8
HiCommand Device Manager Software Components ...................................... 9
Important Terms and Concepts............................................................... 11
Conventions in Syntax Explanations ......................................................... 14
HiCommand Device Manager Operations.......................................................................15

2.1
2.2
2.3
2.4
2.5
2.6
2.7
User Groups and User Access Levels.........................................................

Storage Management Operations.............................................................
Subsystem and Volume Configuration Operations .........................................
2.3.1 Configuration Operations for theTagmaStore
USP Subsystem .........................................................................
2.3.2 Configuration Operations for the Lightning 9900 V Series
Subsystem ..............................................................................
2.3.3 Configuration Operations for the Thunder 9500 V Series
Subsystem ..............................................................................
2.3.4 Configuration Operations for the Thunder 9200 Subsystem ..................
2.3.5 Configuration Operations for the Sun StorEdge T3 Array......................
Data Management Operations ................................................................
2.4.1 Data Management Operations for the TagmaStore USP
Subsystem ..............................................................................
2.4.2 Data Management Operations for the Lightning 9900 V Series
Subsystem ..............................................................................
2.4.3 Data Management Operations for the Lightning 9900
Subsystem ..............................................................................
2.4.4 Data Management Operations for the Thunder 9500 V Series
Subsystem ..............................................................................
2.4.5 Data Management Operations for the Thunder 9200
Subsystem ..............................................................................
Link-and-Launch Operations ..................................................................
Report Operations ..............................................................................
System Security Operations ...................................................................
16
18
19
20
23
24
25
26
28
28
28
29
30
31
32
33
34
ix
Chapter 3
Installing the Device Manager Web Client .........................................................................35

3.1
3.2
3.3
3.4
3.5
Chapter 4
Preparing for and Starting Device Manager Operations...................................................47

4.1
4.2
4.3
4.4
4.5
4.6
Chapter 5
Preparing to Start HiCommand Device Manager Operations............................ 48

Link-and-Launch Requirements ............................................................... 50
Linkage with Related Products................................................................ 52
4.3.1 Linkage with Universal Volume Manager ........................................... 52
4.3.2 Linkage with DAMP (for Web) ........................................................ 53
4.3.2.1 Prerequisites and Procedures ............................................. 53
4.3.2.2 Storage Subsystem Information to Be Registered
Using DAMP (for Web) ...................................................... 54
Copy Pair Requirements........................................................................ 55
4.4.1 General Requirements ................................................................ 55
4.4.2 TrueCopy Requirements .............................................................. 57
4.4.3 ShadowImage Requirements ......................................................... 59
4.4.4 QuickShadow Requirements .......................................................... 60
Logging in to HiCommand Device Manager for the First Time
after Installation ................................................................................ 61
Starting HiCommand Device Manager Operations ........................................ 65
Performing Device Manager System Operations ..............................................................67

5.1
5.2
5.3
5.4
5.5
5.6
Requirements for Web Client Operations ................................................... 36

Preparing to Access the Web Client.......................................................... 38
Installing the Java Software Environment................................................. 39
3.3.1 Installing Java Software on a Windows System ................................ 39
3.3.2 Installing Java Software on a Solaris System................................... 40
Configuring Java Software for Client/Server Operations ............................... 41
3.4.1 Setting up the Proxy................................................................... 42
3.4.2 Setting up the Log Output ............................................................ 42
3.4.3 Setting up JRE when Different JRE Versions Have Been Installed.............. 43
3.4.4 Clearing the Cache in Java Web Start ............................................ 44
Upgrading the Java GUI ...................................................................... 45
Contents
Using the HiCommand Device Manager Main Window ................................... 68

5.1.1 Menu Bar ................................................................................ 70
5.1.2 Navigation Frame ...................................................................... 71
5.1.3 Popup Windows......................................................................... 72
Logging in and out of HiCommand Device Manager ...................................... 73
5.2.1 Logging In to Device Manager ........................................................ 73
5.2.2 Logging out of Device Manager ...................................................... 75
Viewing Version and License Type Information ............................................ 76
Viewing User Profile Information ............................................................. 77
Performing Alert Operations .................................................................. 78
5.5.1 Viewing Alerts .......................................................................... 79
5.5.2 Monitoring Alerts....................................................................... 81
5.5.3 Deleting Alerts ......................................................................... 83
Viewing the Task List ........................................................................... 84
5.7
Chapter 6
6.3
89
90
90
91
Overview of User Management Operations ................................................. 94

User Account Operations ...................................................................... 95
6.2.1 Adding a User .......................................................................... 97
6.2.2 Viewing and Editing User Properties ............................................... 99
6.2.3 Changing Your Password............................................................. 100
6.2.4 Deleting a User ....................................................................... 101
User Group Operations........................................................................ 102
6.3.1 Adding a User Group ................................................................. 104
6.3.2 Viewing and Editing User Group Properties ...................................... 106
6.3.3 Deleting a User Group ............................................................... 108
Performing Logical Group Operations .............................................................................111

7.1
7.2
7.3
7.4
7.5
7.6
Chapter 8
85
85
85
86
86
87
Performing User Management Operations.........................................................................93

6.1
6.2
Chapter 7
Launching Other Applications from Device Manager ......................................

5.7.1 Launching HiCommand Tuning Manager .........................................
5.7.2 Launching Hitachi Dynamic Link Manager (HDLM)................................
5.7.3 Launching Protection Manager ......................................................
5.7.4 Launching Provisioning Manager ....................................................
5.7.5 Launching 9900V Storage Navigator ................................................
5.7.6 Launching NAS Blade Manager (TagmaStore USP
and Lightning 9900 V).................................................................
5.7.7 Launching DAMP (Thunder 9500 V and Thunder 9200) ..........................
5.7.8 Launching a Third-Party Application ...............................................
5.7.9 Importing a Server Certificate into a Browser ....................................
Overview of Logical Groups .................................................................. 112

Viewing the List of Logical Groups.......................................................... 114
Adding a Logical Group ....................................................................... 115
Viewing and Editing Logical Group Properties ............................................ 117
Removing a Logical Group.................................................................... 119
Storage Group Operations.................................................................... 121
7.6.1 Viewing the Contents of a Storage Group ........................................ 122
7.6.2 Adding Storage to a Storage Group ................................................ 127
7.6.3 Moving Storage from One Group to Another ..................................... 138
7.6.4 Modifying LUN Security for a Group ............................................... 141
7.6.5 Deleting Storage from a Group..................................................... 145
7.6.6 Removing a Storage Group.......................................................... 148
All Storage/My Storage Operations ..................................................................................151

8.1
8.2
8.3
8.4
8.5
8.6
8.7
Overview of All Storage/My Storage Operations.......................................... 152

Viewing the All Storage/My Storage Group................................................ 153
8.2.1 Viewing the Allocated Group for a Subsystem ................................... 155
8.2.2 Viewing the Unallocated Group for a Subsystem................................ 160
Performing a LUN Scan Operation .......................................................... 164
Allocating Storage ............................................................................. 166
Unallocating Storage .......................................................................... 167
Creating LUSE Devices ........................................................................ 171
Deleting LUSE Devices ........................................................................ 175
xi
Chapter 9
Performing Host Operations .............................................................................................177

9.1
9.2
9.3
9.4
9.5
9.6
9.7
9.8
Overview of HiCommand Device Manager Host Operations...........................

Viewing the List of Hosts.....................................................................
Adding a Host ..................................................................................
9.3.1 Adding Hosts by Executing a LUN Scan ...........................................
9.3.2 Adding Hosts Manually ..............................................................
Viewing Host Properties and Volume Information .......................................
Modifying Host Properties ...................................................................
Updating (Refreshing) Host Information...................................................
Managing Copy Pairs ..........................................................................
9.7.1 Creating Copy Pairs..................................................................
9.7.2 Modifying Copy Pairs ................................................................
9.7.3 Notes on Copy Pair Operations ....................................................
9.7.3.1 Using CCI or Protection Manager
to Manage Existing Copy Pairs ..........................................
9.7.3.2 Using Web Client to Create a
Configuration Definition File for CCI...................................
9.7.4 Deleting Copy Pairs ..................................................................
Removing a Host...............................................................................
178
180
181
181
182
184
187
191
194
194
203
209
214
214
215
219
Chapter 10 Performing Subsystem Operations ..................................................................................221

10.1 Subsystem Operations ........................................................................
10.1.1 Viewing the List of Storage Subsystems ..........................................
10.1.2 Adding a Storage Subsystem........................................................
10.1.3 Viewing and Editing Storage Subsystem Properties.............................
10.1.4 Performing a Refresh Operation ...................................................
10.1.5 Handling a Change to the IP Address of a Subsystem ..........................
10.1.6 Deleting a Storage Subsystem......................................................
10.2 Physical View Operations ....................................................................
10.2.1 Viewing Detailed Information for TagmaStore USP ...........................
10.2.2 Viewing Detailed Information for Lightning 9900 V...........................
10.2.3 Viewing Detailed Information for Lightning 9900 .............................
10.2.4 Viewing Detailed Information for Thunder 9500 V ............................
10.2.5 Viewing Detailed Information for Thunder 9200 ..............................
10.2.6 Viewing Detailed Information for T3..............................................
10.2.7 Viewing Detailed LDEV Information ...............................................
10.3 Port Operations................................................................................
10.3.1 Configuring Ports (9900 V, 9900, 9500 V, and 9200) ...........................
10.3.2 Managing LUN Groups ...............................................................
10.3.3 Managing WWN Groups..............................................................
10.3.4 Configuring the Fibre-Channel Adapters (9900 V, 9900).......................
10.4 Array Group Operations ......................................................................
10.4.1 Creating an Array Group on the Thunder 9500 V and
9200 Subsystems .....................................................................
10.4.2 Creating an Array Group on the StorEdge T3 Array...........................
10.4.3 Deleting an Array Group (9500 V, 9200, and T3) ...............................
10.4.4 Configuring Spare Drives on the Thunder 9500 V
and 9200 Subsystems ................................................................
xii
Contents
222
222
224
227
231
233
234
236
237
237
246
251
253
255
257
263
263
270
275
278
281
281
285
287
288
10.5 LDEV Operations ............................................................................... 290

10.5.1 Allocating Storage (Adding Volume Paths) ....................................... 290
10.5.2 Unallocating Storage (Removing Volume Paths)................................. 294
10.5.3 Creating an LDEV ..................................................................... 296
10.5.4 Deleting an LDEV ..................................................................... 299
10.5.5 Setting a Command Device ......................................................... 300
Chapter 11 Performing Report Operations ..........................................................................................303

11.1
11.2
11.3
11.4
11.5
Overview of HiCommand Device Manager Reports ..................................... 304

Physical Configuration of the Storage Subsystem Report ............................... 306
Storage Utilization by Host Report ......................................................... 308
Storage Utilization by Logical Group Report .............................................. 309
Users and Permissions Report ............................................................... 310
Chapter 12 Troubleshooting .................................................................................................................311

12.1 Troubleshooting Operations.................................................................. 312
12.2 General Troubleshooting ..................................................................... 313
12.3 Warning Messages Output from Device Manager ......................................... 318
12.3.1 When User Data Is Deleted.......................................................... 318
12.3.2 When an Error Occurs in I/O from Hosts.......................................... 318
12.3.3 When LUN Security Automatically Takes Effect ................................. 319
12.3.4 When Access from Hosts Is Disabled............................................... 319
12.3.5 When Data in an S-VOL (Secondary Volume) Becomes Incomplete........... 319
12.3.6 When I/Os to P-VOL (Primary Volume) Are Affected ........................... 319
12.3.7 When Pair Setting Cannot Be Performed ......................................... 320
12.3.8 When an Internal Volume Mapped with an External Volume
Becomes Invalid ...................................................................... 320
12.3.9 When an Attempt Is Made to Create a LUSE Volume Using Volumes
from Multiple External Subsystems ................................................ 320
12.4 Error Messages ................................................................................. 321
12.5 Calling the Support Center................................................................... 322
Acronyms and Abbreviations..................................................................................................................323
xiii
List of Figures
xiv
Figure 1.1
HiCommand Device Manager System

and Software Components............................................................... 10
Figure 2.1
System Configuration (When Using Universal Volume Manager)................... 21
Figure 3.1
Java Web Start Application Manager Window ...................................... 41
Figure 4.1
Figure 4.2
Figure 4.3
HiCommand Device Manager Login Panel

Showing License Warning ................................................................ 62
Version Information for Device Manager Panel....................................... 63
HiCommand Device Manager Main Window Initial Start-Up .................... 64
Figure 5.1
Figure 5.2
Figure 5.3
Figure 5.4
Figure 5.5
Figure 5.6
Figure 5.7
Figure 5.8
Figure 5.9
Figure 5.10
Figure 5.11
Figure 5.12
Figure 5.13
Frames on the HiCommand Device Manager Main Window ....................... 68

Example of a Popup Window ............................................................ 72
HiCommand Device Manager Login Panel ........................................... 74
Logging out of HiCommand Device Manager ........................................ 75
Version Information for Device Manager Panel....................................... 76
Show User Profile ......................................................................... 77
Alerts ....................................................................................... 78
Detailed Information Alert Panel ..................................................... 80
Monitor Alerts Panel Showing Monitoring ........................................... 81
Monitor Alerts Panel Showing Occurrence of Alerts ............................... 82
Viewing the Task List..................................................................... 84
Link-and-Launch Command for 9900 V Storage Navigator.......................... 88
Select Nas/Management Port Controller Dialog Box ................................ 89
Figure 6.1
Figure 6.2
Figure 6.3
Figure 6.4
Figure 6.5
Figure 6.6
Figure 6.7
Figure 6.8
Figure 6.9
Figure 6.10
User Management ......................................................................... 94

User Administration Panel ............................................................... 96
Add a New User ........................................................................... 98
Edit Properties ............................................................................ 99
Change Password........................................................................ 100
Delete User Confirmation............................................................ 101
User Group Administration Panel..................................................... 103
Add a New User Group ................................................................. 105
Edit User Group Properties ............................................................ 107
Delete User Group Confirmation ................................................... 109
Figure 7.1
Figure 7.2
Figure 7.3
Figure 7.4
Figure 7.5
Figure 7.6
Figure 7.7
Figure 7.8
Figure 7.9
Figure 7.10
Figure 7.11
Logical Groups...........................................................................
Adding a New Group....................................................................
Viewing and Editing Logical Group Properties .....................................
Removing an Empty Logical Group ...................................................
Removing a Parent Logical Group ....................................................
Viewing the Contents of a Storage Group...........................................
Detailed Information LDEV-Number Panel ........................................
Add Storage Selecting the Group ...................................................
Add Storage Selecting the Storage Addition Operation .........................
Add Storage Selecting Ports .........................................................
Add Storage Defining Host/Port Connections.....................................
Contents
112
116
118
119
120
123
124
130
131
132
132
Figure 7.12
Figure 7.13
Figure 7.14
Figure 7.15
Figure 7.16
Figure 7.17
Figure 7.18
Figure 7.19
Figure 7.20
Figure 7.21
Figure 7.22
Figure 7.23
Figure 7.24
Figure 7.25
Figure 7.26
Figure 7.27
Figure 7.28
Add Storage Viewing 9900 V HSD Information .................................... 133

Add Storage Allocating Storage ..................................................... 134
Add Storage Browsing for LDEVs .................................................... 134
Add Storage Storage Found .......................................................... 135
Add Storage Defining LUs............................................................. 135
Add Storage Assigning Host/Port Connection ..................................... 136
Add Storage Assigning LUNs.......................................................... 136
Add Storage Confirmation (Summary of Changes)................................ 137
Move Storage Selecting the Target Group ......................................... 139
Move Storage Selecting the Path(s)................................................. 140
Move Storage Confirmation .......................................................... 140
Modify Security Selecting Hosts ..................................................... 143
Modify Security Selecting WWNs .................................................... 143
Modify Security Warning.............................................................. 144
Modify Security Confirmation (Summary of Changes) ........................... 144
Delete Storage Confirmation ........................................................ 147
Remove Logical Group Confirmation ............................................... 150
Figure 8.1
Figure 8.2
Figure 8.3
Figure 8.4
Figure 8.5
Figure 8.6
Figure 8.7
Figure 8.8
Figure 8.9
Figure 8.10
Figure 8.11
All Storage or My Storage .............................................................. 154

Viewing a Subsystem Group in All Storage/My Storage............................ 154
Viewing the Allocated Group for a Subsystem (9900 V) ........................... 156
Viewing the Unallocated Group for a Subsystem (9900 V)........................ 161
Performing a LUN Scan Confirmation............................................... 165
Unallocate Storage Confirmation ................................................... 168
Unallocate Storage Selecting the Path(s).......................................... 169
Unallocate Storage LUSE Confirmation ............................................ 170
Create LUSE Selecting LDEVs ........................................................ 173
Create LUSE Confirmation and Warning ........................................... 174
Delete LUSE - Confirmation and Warning............................................ 176
Figure 9.1
Figure 9.2
Figure 9.3
Figure 9.4
Figure 9.5
Figure 9.6
Figure 9.7
Figure 9.8
Figure 9.9
Figure 9.10
Figure 9.11
Figure 9.12
Figure 9.13
Figure 9.14
Figure 9.15
Figure 9.16
Figure 9.17
Figure 9.18
Figure 9.19
Figure 9.20
Figure 9.21
Hosts....................................................................................... 179
Add Host Entering the Name......................................................... 183
Add Host Entering the WWN(s) ...................................................... 183
Viewing Host Properties ................................................................ 185
Detailed Information LDEV-Number Panel......................................... 186
Modify Host Properties ................................................................. 188
Modify Host Properties Adding a WWN ............................................. 188
Modify Host Properties Selecting LUN Security Changes ........................ 189
Modify Host Properties Confirming LUN Security Changes ...................... 190
Refresh Host Refresh Button ......................................................... 192
Refresh Host Confirmation ........................................................... 193
Create Pair Selecting the P-VOLs ................................................... 198
Create Pair Choose Pair(s) Step ..................................................... 199
Create Pair Selecting the S-VOL(s) ................................................. 199
Create Pair Define Pair(s) Step....................................................... 200
Create Pair View Pair Information .................................................. 200
Create Pair Defining a New Copy Group ........................................... 201
Create Pair Confirmation Step ...................................................... 201
Create Pair Warning of Data Loss ................................................... 202
Modify Pair Selecting the Host ...................................................... 206
Modify Pair Select Modify Pair(s) Step ............................................. 207
xv
xvi
Figure 9.22
Figure 9.23
Figure 9.24
Figure 9.25
Figure 9.26
Figure 9.27
Modify Pair(s) Step......................................................................

Modify Pair Summary of Changes Step.............................................
Modify Pair Warning of I/O Activity on P-VOL ....................................
Delete Pair Select Delete Pair(s) Step .............................................
Delete Pair Confirmation (Summary of Changes Step) ..........................
Remove Host Confirmation ..........................................................
207
208
208
217
218
219
Figure 10.1
Figure 10.2
Figure 10.3
Figure 10.4
Figure 10.5
Figure 10.6
Figure 10.7
Figure 10.8
Figure 10.9
Figure 10.10
Figure 10.11
Figure 10.12
Figure 10.13
Figure 10.14
Figure 10.15
Figure 10.16
Figure 10.17
Figure 10.18
Figure 10.19
Figure 10.20
Figure 10.21
Figure 10.22
Figure 10.23
Figure 10.24
Figure 10.25
Figure 10.26
Figure 10.27
Figure 10.28
Figure 10.29
Figure 10.30
Figure 10.31
Figure 10.32
Figure 10.33
Figure 10.34
Figure 10.35
Figure 10.36
Figure 10.37
Figure 10.38
Figure 10.39
Figure 10.40
Figure 10.41
Figure 10.42
Figure 10.43
Subsystems...............................................................................
Add Subsystem (9900V) ................................................................
Viewing Storage Subsystem Properties ..............................................
Modify Properties (9900V) .............................................................
Refresh Storage Subsystem Confirmation .........................................
Remove Subsystem Confirmation...................................................
Physical View for Lightning 9900 V (Configuration) .............................
Physical View for Lightning 9900 V (Array Groups) ..............................
Frame Information Panel for Lightning 9900 V (Level 1) .......................
Discrete VDEV Configuration for Lightning 9900 V ...............................
Frame Information Panel for Discrete VDEV Configuration ......................
Frame Information Panel for Lightning 9900 V (Level 2) .......................
Physical View for Lightning 9900 V (Disks) ........................................
Physical View for Lightning 9900 (Configuration) ................................
Physical View for Lightning 9900 (Array Groups).................................
Frame Information Panel for Lightning 9900 .....................................
Physical View for Lightning 9900 (Disks) ..........................................
Physical View for Thunder 9500 V ..................................................
Physical View for Thunder 9200 ....................................................
Physical View for T3 ....................................................................
LDEV Information Panel Detail Tab ................................................
LDEV Information Panel Path Info Tab.............................................
LDEV Information Panel Pair Info Tab .............................................
Port Information Panel for the Lightning 9900 V.................................
WorldWideName Information Panel for the 9900 V ...............................
Modify LUN Group Panel ...............................................................
Add New LUN Group Selecting the LUN(s) ........................................
Add New LUN Group Selecting the WWN(s) .......................................
Add New LUN Group Selecting the WWN Group(s)...............................
Modify WWN Group Panel..............................................................
Changing the Channel Adapter Mode (9900 V) .....................................
Changing the Channel Adapter Mode Confirmation..............................
Create Array Group Selecting Array Group Parameters.........................
Create Array Group Confirmation ..................................................
Create Array Group (T3) ...............................................................
Create Array Group (T3) Confirmation ............................................
Delete Array Group Confirmation ..................................................
Spare Drive Panel (9500V) .............................................................
Allocate Storage Define Host/Port Connections .................................
Allocate Storage Assign Host/Port Connections ..................................
Allocate Storage Assign LUNs........................................................
Allocate Storage Confirmation ......................................................
Unallocate Storage Confirmation ...................................................
223
226
229
230
232
235
238
240
241
242
243
244
245
247
248
249
250
252
254
256
258
259
261
265
266
270
272
272
273
275
279
280
282
283
286
286
288
289
291
292
292
293
295
Contents
Figure 10.44
Figure 10.45
Figure 10.46
Figure 10.47
Figure 10.48
Figure 10.49
Unallocate Storage Delete LUSE or Keep LUSE ................................... 295

Create LDEV Specifying the LDEV Parameters (9900 V) ......................... 298
Create LDEV Confirmation ........................................................... 298
Delete LDEV Confirmation ........................................................... 300
LDEV Configuration Set Command Device ......................................... 302
LDEV Configuration Set Command Device ......................................... 302
Figure 11.1
Figure 11.2
Figure 11.3
Figure 11.4
Figure 11.5
Figure 11.6
Reports.................................................................................... 305
Physical Configuration of Storage Subsystem Report HTML..................... 306
Physical Configuration of Storage Subsystem Report CSV....................... 307
Storage Utilization by Host Report (HTML).......................................... 308
Storage Utilization by Logical Group Report (HTML) .............................. 309
Users and Permissions Report (HTML)................................................ 310
xvii
List of Tables
Table 1.1
Table 1.2
Device Manager Terms and Storage Subsystem Terms .............................. 13

Conventions for Syntax Explanations .................................................. 14
Table 2.1
HiCommand Device Manager User Roles............................................. 17
Table 3.1
Upgrading the Web Client Java GUI .................................................. 45
Table 7.1
Detailed Information LDEV-Number Panel Information ......................... 125
Table 8.1
Table 8.2
Allocated Group Information under All Storage/My Storage ..................... 157

Unallocated Group Information under All Storage/My Storage .................. 162
Table 9.1
Table 9.2
Table 9.3
Table 9.4
Table 9.5
Requirements for Modify Pair Operations...........................................

Requirements for Operations on ShadowImage Cascade Pairs...................
Items to Consider before Creating Copy Pairs......................................
Notes on Copy Pair Operations .......................................................
Notes on Managing the Host...........................................................
203
204
209
210
213
Table 10.1
Table 10.2
263
Table 10.4
Table 10.5
Available AL-PA Values.................................................................

Acceptable RAID Level and Width Value Combinations
(9200 and 9500 V).......................................................................
Acceptable RAID Level and Depth Value Combinations
(9200 and 9500 V).......................................................................
Acceptable RAID Level and Width Value Combinations (T3) .....................
Maximum Capacities of Standard LU Types.........................................
Table 12.1
General Troubleshooting Information ............................................... 313
Table 10.3
xviii
Contents
283
284
287
296
Chapter 1
Overview of HiCommand Device Manager
This chapter provides an overview of HiCommand Device Manager:
Overview of HiCommand Device Manager (section 1.1)
New functions in Device Manager 3.5 (section 1.2)
Related software products (section 1.3)
HiCommand Device Manager software components (section 1.4)
Important terms and concepts (section 1.5)
1.1
Overview of HiCommand Device Manager

HiCommand Device Manager is a core product for storage management which enables users
to consolidate storage operations and manage capacity in systems that contain multiple
Hitachi storage subsystems (e.g., TagmaStore USP, Lightning 9900 V Series, Thunder
9500 V Series, Lightning 9900, and Thunder 9200) as well as subsystems from other
companies (e.g., StorEdge from Sun Microsystems Corporation). Targeted for users
managing multiple storage arrays in open or shared environments, HiCommand Device
Manager quickly discovers the key configuration attributes of storage systems and allows
users to begin proactively managing complex and heterogeneous storage environments
quickly and effectively using an easy-to-use browser-based GUI. HiCommand Device
Manager enables remote storage management over secure IP connections and does not have
to be direct-attached to the storage system. HiCommand Device Manager is a component of
the HiCommand family of software products, Hitachi Data Systems storage management
framework.
HiCommand Device Manager gives storage administrators easier access to the existing array
configuration, monitoring, and data management features and allows users to perform
important operations such as adding/deleting storage, configuring volume paths and fibrechannel ports, creating custom-size volumes, managing LUN security, and configuring
TrueCopy, ShadowImage, and QuickShadow copy operations. HiCommand Device Manager
also provides link-and-launch integration with HiCommand Tuning Manager, Hitachi
Dynamic Link Manager (HDLM), HiCommand Protection Manager, HiCommand Provisioning
Manager, the Storage Navigator software, and the 9500V Disk Array Management Program
(DAMP).
HiCommand Device Manager provides a consistent, easy-to-use, and easy-to-configure set
of interfaces for managing storage in a distributed environment. The Device Manager system
includes the Device Manager Server, the storage array(s) connected to the Server, the
(optional) Device Manager agents, and the Device Manager clients. The Device Manager Web
Client provides a web-distributed client for real-time interaction with the storage arrays
being managed. The Device Manager Command Line Interface (CLI) is targeted for expert
users who prefer a character-based interface to create their own automation scripts.
Designed as an open framework, HiCommand Device Manager provides a set of application
programming interfaces (APIs) which allow industry-leading software vendors (e.g., Sun
Microsystems, VERITAS, Microsoft, BMC, Computer Associates, InterSAN) to seamlessly
integrate their applications with HiCommand Device Manager. Users can also plug in
existing or new applications to the HiCommand Device Manager system. Please contact
your Hitachi Data Systems account team for the latest information on HiCommand Device
Manager development partners.
HiCommand Device Manager enables management of storage by user-defined hierarchical
groups. HiCommand Device Manager displays detailed information on the configuration of
the storage arrays added to the HiCommand Device Manager Server and provides subsystem
alert presentation. You can also configure HiCommand Device Manager to monitor and
display volume usage statistics using the HiCommand Device Manager Agent (optional).
HiCommand Device Managers built-in report facility compiles and presents key information
in preformatted reports (HTML) and as comma-separated values for export.
Chapter 1 Overview of HiCommand Device Manager
HiCommand Device Manager provides several levels of access and functionality for users:
Access Control: Support for the System Administrator (Local System Administrator),
Storage Administrator (Local Storage Administrator), and guest users (Local Guest)
Storage Management: Storage configuration and manipulation
System support: Web Client support, user administration, Agent activity, and security
Note: The use of the HiCommand Device Manager product and all Hitachi Data Systems
products is governed by the terms of your license agreement(s) with Hitachi Data Systems.
Note: The use of the Sun StorEdge T3 array and all Sun products is governed by the terms
of your license agreement(s) with Sun Microsystems.
1.1.1
Overview of Hitachi ShadowImage

Hitachi ShadowImage is a storage-based hardware solution for duplicating logical volumes
which reduces backup time and provides point-in-time backup. The RAID-protected duplicate
volumes are created within the same subsystem as the primary volume at hardware speeds.
The ShadowImage primary volumes (P-VOLs) contain the original data; the secondary
volumes (S-VOLs) contain the duplicate data. Up to nine copies of each P-VOL can be made
using the ShadowImage cascade function. And since each S-VOL is paired with its P-VOL
independently, each S-VOL can be maintained as an independent copy set that can be split,
resynchronized, and deleted separately from the other S-VOLs assigned to the same P-VOL.
ShadowImage operations are nondisruptive and allow the primary volume of each copy pair
to remain online to all hosts for both read and write I/O operations. Once established,
ShadowImage operations continue unattended to provide asynchronous internal data backup.
Usability is further enhanced through a resynchronization capability that reduces data
duplication requirements and backup time. ShadowImage also supports reverse
resynchronization for maximum flexibility.
For detailed information on ShadowImage operations, refer to the ShadowImage Users
Guide for the subsystem (e.g., Hitachi Lightning 9900 ShadowImage Users Guide).
1.1.2
Overview of Hitachi TrueCopy

Hitachi TrueCopy is a storage-based hardware solution for disaster recovery which enables
fast and accurate system recovery. Once TrueCopy operations are established, remote
copies of data are automatically maintained for backup and disaster recovery purposes.
During normal TrueCopy operations, the primary volumes remain online to all hosts and
continue to process both read and write I/O operations. In the event of a disaster or system
failure, the secondary copy of data can be rapidly invoked to allow recovery with a very high
level of data integrity. TrueCopy can also be used for data duplication and migration tasks.
TrueCopys synchronous and asynchronous copy modes accommodate a wide variety of user
requirements and data copy/movement scenarios.
TrueCopy Synchronous provides volume-based real-time data backup and is ideal for highpriority data backup, duplication, and migration tasks. In the event of a disaster or system
failure at the primary site, the secondary TrueCopy Synchronous data can be rapidly invoked
to allow recovery at the volume level with an extremely high level of data integrity.
TrueCopy Asynchronous (TCA) (available for TagmaStore USP, Lightning 9900V, and 9900)
represents a unique and advanced disaster recovery solution for large amounts of data which
span multiple volumes. The TrueCopy Asynchronous group-based update sequence
consistency solution enables fast and accurate database recovery, even after a rolling
disaster, without the need for time-consuming data recovery procedures. The TrueCopy
Asynchronous volume groups at the remote site can be recovered with full update sequence
consistency, but the updates will be behind the primary site due to the asynchronous copy
operations. TrueCopy Asynchronous provides update sequence consistency for user-defined
groups of volumes (e.g., large databases) as well as protection for write-dependent
applications in the event of a disaster.
For detailed information on TrueCopy operations, refer to the TrueCopy manual for the
subsystem (e.g., Hitachi Thunder 9500 V Series Synchronous TrueCopy Users Guide).
1.1.3
Overview of Hitachi QuickShadow (9500V Only)

Hitachi QuickShadow provides nondisruptive, high-speed, logical snapshot data replication
within Thunder 9500V subsystems for immediate use in decision support, software testing
and development, data backup, or rapid recovery operations. The high-speed, nondisruptive,
point-in-time snapshot technology of the QuickShadow feature rapidly creates up to fourteen
point-in-time snapshot copies of any data volume within the 9500V subsystem, without
impacting host service or performance levels. Since QuickShadow snapshots only store the
changed data blocks in the QuickShadow storage pool, the amount of storage capacity
required for each QuickShadow snapshot copy is substantially smaller than the source
volume, resulting in a significant savings when compared with full cloning methods.
The QuickShadow copies are fully read/write compatible by other hosts and can be used for
rapid data restores, application testing and development, data mining/data warehousing, or
nondisruptive backup or maintenance procedures.
Business Continuity
Reduces recovery from data corruption or human error considerably by allowing an

immediate restore from a disk-resident, point-in-time data snapshot copy.
Enhances data availability by allowing more frequent and nondisruptive data backup
operations to be performed while critical applications continue to run unaffected.
Productivity and Process Improvements
Reduces application testing and deployment time while increasing the accuracy of
application development by providing always-available copies of current production
information.
Increases competitive advantage by enabling workload sharing and immediate access to

time-critical information for decision support, populating data warehouses, performing
analysis, or other data mining operations.
For detailed information on QuickShadow 9500V operations, refer to the Hitachi Thunder
9500 V Series QuickShadow 9500V Users Guide (MK-92DF666).
1.1.4
Overview of Command Control Interface (CCI)

Hitachi Command Control Interface (CCI) enables users to perform Hitachi TrueCopy, Hitachi
ShadowImage, Data Retention and Open LDEV Guard operations on the Lightning and
Thunder series subsystems by issuing commands from the UNIX/PC server host to the
subsystems. The CCI software interfaces with the system software and high-availability (HA)
software on the UNIX/PC server host as well as the TrueCopy/ShadowImage software on the
subsystem(s). The CCI software provides failover and other functions such as backup
commands to allow mutual hot standby in cooperation with the failover product on the
UNIX/PC server (e.g., MC/ServiceGuard, FirstWatch, HACMP).
CCI also supports a scripting function that allows users to define multiple TrueCopy and/or
ShadowImage operations in a script (text) file. Using CCI scripting, you can set up and
execute a large number of TrueCopy and/or ShadowImage commands in a short period of
time while integrating host-based high-availability control over remote copy operations.
Note: For detailed information on CCI, please see the applicable CCI manual (e.g., Hitachi
Lightning 9900 V Series Command Control Interface (CCI) User and Reference Guide
(MK-90RD011), or contact your Hitachi Data Systems account team.
1.2
New Functions in HiCommand Device Manager 3.5

HiCommand Device Manager 3.5 provides the following new functions:
Support for the TagmaStore USP subsystem.

Management of the storage for a new storage subsystem, TagmaStore USP, is
supported. Also, the external volume management provided by the TagmaStore USP
external storage connection management function (Universal Volume Manager) is
supported.
Linkage to Disk Array Management Program2

Link-and-Launch features allow you to start, from a Web Client, Disk Array Management
Program2 that manages Thunder 9200 and Thunder 9500V.
Linkage to HiCommand Protection Manager

Link-and-Launch features allow you to start, from a Web Client, HiCommand Protection
Manager.
Linkage to HiCommand Provisioning Manager

Single Sign On features allow you to start, from a Web Client, HiCommand Provisioning
Manager.
Support for selecting the items displayed in the list in a batch

When using a Web Client to perform operation on each resource, you can select the
displayed multiple objects at once and cancel the selections at once.
Support for sorting the displayed items in the list

When using a Web Client to perform operation on each resource, you can sort the
displayed objects by item.
HiCommand Device Manager 3.5 provides the following enhancements to existing functions:
Support for a new operating system (OS)

Microsoft Windows Server 2003 is supported. The Device Manager server and Device
Manager client support the 32-bit processor version only. The Device Manager agent
supports the 32-bit processor version and 64-bit processor version.
Expansion of Thunder 9500V operation management

HiCommand Device Manager 3.5 can identify and display the volumes protected by the
Thunder 9500V OPEN LDEV GUARD function.
HiCommand Device Manager 3.5 allows you to set up the command device security.
HiCommand Device Manager 3.5 can identify and display the SATA drive mounted on
Thunder 9500V.
1.3
Related Software Products

The following software products are related to Device Manager:
Hitachi Dynamic Link Manager

The Hitachi Dynamic Link Manager (HDLM) software product is installed on the host and
manages access paths to storage (e.g., automatic failover and failback, load balancing).
The HDLM GUI can be displayed from the Device Manager Web Client (see section 2.5).
For details on Dynamic Link Manager, see the applicable HDLM manual(s) (e.g., Hitachi
Dynamic Link Manager (HDLM) Users Guide for Solaris Systems (MK-92DLM114)).
HiCommand Tuning Manager

The HiCommand Tuning Manager software product monitors the performance of an
entire network, including the SAN environment provided by the Lightning/Thunder series
storage subsystems.
The Tuning Manager GUI can be displayed from the Device Manager Web Client (see
section 2.5). For details on Tuning Manager, see the applicable Tuning Manager
manual(s) (e.g., HiCommand Tuning Manager Reference Guide (MK-92HC022)).
HiCommand Policy Manager

The HiCommand Policy Manager software product automates storage operations and
reduces workload of administrative tasks. Policy Manager can automate a series of
operations in Device Manager, and execute it based on a pre-specified schedule.
For details on Policy Manager, please contact your Hitachi Data Systems account team.
HiCommand Protection Manager

The HiCommand Protection Manager software product collectively control the storage
subsystems, backup management products, database products, and application products
to simplify the necessary procedure for data protection management. The Protection
Manager GUI can be displayed from the Web Client (see section 2.5). For details about
Protection Manager, see the applicable manuals for Protection Manager.
HiCommand Provisioning Manager

The HiCommand Provisioning Manager product automates a series of operations
required for allocating LDEVs to the server or expanding a file system. This reduces
workload of administrative tasks for storage resources. The Provisioning Manager GUI can
be displayed from the Web Client (see section 2.5). For details about Provisioning
Manager, see the applicable manuals for Provisioning Manager.
1.4
HiCommand Device Manager Software Components

The HiCommand Device Manager system consists of the following software components (see
Figure 1.1):
HiCommand Suite Common Component. HiCommand Device Manager supports

integration with the HiCommand Suite Common Component, which provides features
that are common to all HiCommand suite products. Single sign-on (SSO) user
authentication and integrated event/error logging are provided for HiCommand Device
Manager (version 2.3 and higher) and HiCommand Tuning Manager (version 1.1 and
higher). Each HiCommand product now includes HiCommand Suite Common
Component.
Single sign-on. Integrated single sign-on is used during the link & launch operation
(see section 2.5). The already authenticated user ID and password are available to
the launched HiCommand software, so that users do not need to re-enter their user
ID and password. User privileges are maintained across HiCommand products.
Common logging. The HiCommand Suite Common Component integrated logging

feature provides a common log repository for the various logs of the HiCommand
suite products.
Server. The HiCommand Device Manager Server is LAN-attached to the storage arrays
and controls HiCommand Device Manager operations based on requests from the
HiCommand Device Manager clients. The HiCommand Device Manager clients (e.g.,
Web Client, CLI, third-party application) communicate with the HiCommand Device
Manager Server, and the HiCommand Device Manager Agent sends information to the
HiCommand Device Manager Server.
Note: For further information on the HiCommand Device Manager Server, refer to the
HiCommand Device Manager Server Installation and Configuration Guide
(MK-91HC002).
Clients:
Web Client. The HiCommand Device Manager Web Client provides two types of
user interfaces, an HTML GUI and a Java GUI, for HiCommand Device Manager
functions. The Web Client communicates with and runs as a client of the
The HTML GUI is a browser-based application that can be accessed from Web
browsers. This GUI provides the windows and dialog boxes for other than the
subsystem and user management features.
The Java GUI is a stand-alone Java-based application which is deployed using the
Java Web Start software. This GUI provides the windows and dialog boxes for the
subsystem and user management features.
This document describes and provides instructions for installing and using the
HiCommand Device Manager Web Client software and the Java GUI (see Chapter
3).
Command Line Interface (CLI). The HiCommand Device Manager CLI enables you
to perform HiCommand Device Manager operations by issuing commands from the
system command line prompt. The HiCommand Device Manager CLI communicates
with and runs as a client of the HiCommand Device Manager Server.
Note: For further information on the HiCommand Device Manager CLI, please refer
to the HiCommand Device Manager Command Line Interface (CLI) Users Guide
(MK-91HC007).
Third-party application. HiCommand Device Manager supports third-party

applications by providing an application program interface (API) that developers can
use to interface with the HiCommand Device Manager Server. For details, please
contact Hitachi Data Systems.
Agent (recommended, optional). The HiCommand Device Manager Agent runs on the
host server that is attached to one or more storage subsystems, collects data on the
configuration and utilization of the attached storage, and sends this information to the
HiCommand Device Manager Server. The HiCommand Device Manager clients display
this information for the user when it is available on the Server. For further information
on the HiCommand Device Manager Agent, please refer to the HiCommand Device
Manager Agent Installation Guide (MK-92HC019).
Figure 1.1
10
HiCommand Device Manager System and Software Components
1.5
Important Terms and Concepts

HiCommand Device Manager users should be familiar with the following terms and
concepts. Table 1.1 shows some of these Device Manager terms and the corresponding terms
used on the storage subsystems.
Storage Group: A user-defined set of paths (LUNs) which can be manipulated as a group.
The LUNs in a storage group must physically reside in the same storage subsystem. A
storage group cannot contain another group. Storage groups are displayed under the
Logical Groups, All Storage/My Storage, and Hosts objects.
Logical Group: A user-defined group of groups. A logical group can contain subordinate
logical groups and/or storage groups containing LUNs. Storage cannot be added directly
below a logical group that includes a storage group, or that includes a lower logical
group. A logical group does not contain storage. Logical groups are displayed under the
Logical Groups object.
User Group: A user-defined set of users which can be manipulated as a group. Users in a
user group can only see and manage the logical groups, hosts, and volumes which are
assigned to that user group. User groups are displayed on the User Group Administration
panel (restricted to System and Local Administrators).
LUN Group: A LUN security group on a 9900 subsystem. HiCommand Device Manager
allows the user to manage LUN groups.
Host: A user-defined set of worldwide names (WWNs) which represent a physical host
server with one or more fibre-channel host bus adapters (HBAs), each of which may have
one or two ports with unique WWNs.
WWN Group: A WWN group on a 9900 subsystem. HiCommand Device Manager allows
the user to manage WWN groups.
Host Storage Domain: An existing host group on a TagmaStore USP, Lightning 9900V or
Thunder 9500V subsystem that is configured using the LUN Manager software for the
storage subsystem. Host group in the Thunder 9500V is applicable when the security
mode is set to LUN Management, and is not applicable when the security mode is LUN
Security. HiCommand Device Manager displays the host storage domain information for
the TagmaStore USP, 9900V and 9500V subsystems and allows the user to change host
storage domain names.
Logical Group View: A display of the user-defined logical groups in HiCommand Device
Manager. Top-level groups can be expanded to display the subgroups. The Logical Group
view displays all storage managed by HiCommand Device Manager independent of the
physical location of the storage. The Logical Group view can be structured as desired by
the user (e.g., by platform, organizational department, etc.).
Subsystem View: A display of the physical configuration information for the storage
subsystems, for example: serial number, number and type(s) of ports, location and
capacity of installed array groups, LDEVs and paths, and amount of cache memory.
Host View: A display of the user-defined hosts in HiCommand Device Manager and the
detailed storage information for each host, including allocated capacity and storage
groups in use. The Host view displays allocated storage grouped by host server and by
storage group.
11
12
Array (parity) group: A set of hard disk drives (HDDs) which have the same capacity and
are treated as one RAID unit. An array group contains user data and parity information,
which ensures user data integrity in the event of a disk drive failure in the array group.
Discrete/normal VDEV: Discrete VDEV configuration (9900V RAID5 7D+1P only) involves
using two parity groups (PGs)to create a virtual device (VDEV) (array group in
HiCommand Device Manager). A normal VDEV is created on a single parity group.
LDEV: A logical device on a storage subsystem. An unallocated LDEV is not mapped to a

LUN (no access path). An allocated LDEV has one or more access paths (LUNs).
LU/volume: A logical unit (LU)on a storage subsystem. In most cases an LU, or volume, is
the same as an LDEV. An exception is a LUN Expansion (LUSE) device.
LUSE: An LU consisting of multiple LDEVs. You can create a LUSE device on TagmaStore
USP Lightning 9900V, Thunder 9500V, Lightning 9900, and Thunder 9200 subsystem.
Volume path/LUN: A path to an LU (volume) in a storage subsystem which maps the LU

to a port and LU number (LUN). Each LU can have one or more paths, and each path can
have different LUN security settings. The type of host platform determines the number
of logical units (LUs) that may be connected to each port.
The Lightning 9980V subsystem supports up to 32,768 paths via fibre-channel ports
(512/port 64 ports). The 9970V supports up to 24,576 paths (512/port 48 ports).
The Lightning 9960 subsystem supports up to 16,384 paths via fibre-channel ports
(512/port 32 ports). The 9910 supports up to 12,288 paths (512/port 24 ports).
The Thunder 9500 V Series subsystem supports a maximum of 1,024 paths.
The Thunder 9200 subsystem supports a maximum of 64 paths.
The Sun StorEdge T3 array (partner-pair configuration) supports a maximum of 8

paths: (4 volumes on one port) 2.
Channel adapter/Port controller: A fiber-channel adapter in the storage subsystem that

is equipped with one or more ports to establish connection with the host. For
TagmaStore USP, Lightning 9900V and 9900, it is referred to as the channel adapter
(CHA). For Thunder 9500V, Thunder 9200, and Sun StorEdge T3, it is referred to as the
controller.
Port: Port of the CHA/port controller where the cable from the subsystem is connected.
ShadowImage: The ShadowImage feature enables the user to make backup copies of
volumes in the same storage subsystem (see section 1.1.1).
TrueCopy: The TrueCopy feature enables the user to make backup copies of volumes in
a different storage subsystem (see section 1.1.2).
QuickShadow: The QuickShadow feature (9500V only) enables the user to make backup
copies of volumes in the same storage subsystem (see section 1.1.3).
Primary volume (P-VOL): The source volume that is being copied to another volume by
ShadowImage, QuickShadow, and/or TrueCopy.
Secondary volume (S-VOL): The target volume onto which a P-VOL is being copied by
ShadowImage, QuickShadow, and/or TrueCopy.
Secondary-primary volume (SP-VOL): ShadowImage volume that is an S-VOL in the top

layer and a P-VOL in the second layer. When you use the ShadowImage cascade
functionality (for TagmaStore USP, Lightning 9900V, and 9900 only), you can create a
copy pair (in the second layer) whose P-VOL is an S-VOL of another copy pair (in the top
layer).
V-VOL: Logical duplicated volume of the QuickShadow function consisting of physical

data stored in the primary volume and differential data stored in the Data Pool.
Copy pair: A TrueCopy copy pair consists of one P-VOL and one S-VOL in different
subsystems. A QuickShadow copy pair (9500V only) consists of one P-VOL and up to 14
V-VOLs. A ShadowImage copy pair (layer 1) consists on one P-VOL and up to three S-VOLs
in the same subsystem. A layer-2 ShadowImage cascade copy pair (for TagmaStore USP,
Lightning 9900V, and 9900 only) has one SP-VOL and up to two S-VOLs in the same
subsystem.
Command Control Interface (CCI): The licensed software product that enables the user
to perform TrueCopy and/or ShadowImage operations by issuing commands from the
host to the command device on the storage subsystem (see section 1.1.4).
Command device: An LU used exclusively for communicating with the CCI software on
the host to control ShadowImage and/or TrueCopy operations.
Table 1.1
Device Manager Terms and Storage Subsystem Terms
Device
Manager
TagmaStore
USP
Lightning
9900 V
Lightning
9900
Thunder
9500 V
Thunder
9200
Sun T3
Port controller
CHA
CHA
CHA
Controller
Controller
Controller
Port
Port
Port
Port
Port
Port
Port
Host storage
domain
Host group
Host group
Not applicable
Host group
Not applicable
Not applicable
LUN
LUN
LUN
LUN
LUN
LUN
LUN
Array group
VDEV (an area

that subdivides
a parity group)
VDEV (an area

that subdivides
a parity group)
Parity group or
array group
RAID
RAID
Volume
LDEV
LDEV
LDEV
LDEV
Logical unit
(LU)
Logical unit
(LU)
Not applicable
(one LDEV =
one array
group)
ShadowImage
ShadowImage
ShadowImage
ShadowImage
ShadowImage
MRCF-Lite
Not applicable
TrueCopy
TrueCopy
TrueCopy
TrueCopy
TrueCopy
Synchronous
Remote Copy
Not applicable
QuickShadow
Not applicable
Not applicable
Not applicable
QuickShadow
Not applicable
Not applicable
13
1.6
Conventions in Syntax Explanations

Syntax definitions appear as follows:
StoreDatabase [temp|perm] (database-name ...)
The following table lists the conventions used in syntax explanations.
Table 1.2
14
Conventions for Syntax Explanations
Example Font or Symbol
Convention
StoreDatabase
The user should enter code-font characters exactly as shown.
database-name
In actual commands the user must replace the italics by suitable characters.
SD
Bold code-font characters indicate an abbreviation for a command.
perm
Underlined characters indicate a default value.
[ ]
An item or items enclosed in brackets are optional.
Only one of the options separated by a vertical bar can be used at one time.
...
Ellipses (...) indicate that the item or items enclosed in () or [] and which
immediately precede the ellipses can be repeated.
()
The items enclosed by the parentheses are in the range to which | or ... are applied.
Chapter 2
HiCommand Device Manager Operations
This chapter describes HiCommand Device Manager operations:
User groups and user access levels (see section 2.1)
Storage management operations (see section 2.2)
Subsystem and volume configuration operations (see section 2.3)
Data management operations (see section 2.4)
Link-and-Launch operations (see section 2.5)
Report operations (see section 2.6)
System security operations (see section 2.7)
15
2.1
User Groups and User Access Levels

HiCommand Device Manager provides two sets of user groups: System and Local. System
users have access to all Device Manager resources. Local users have access only to specific
Device Manager resources. Device Manager also provides three levels of user access, or user
roles: System Administrator, Storage Administrator, and Guest. Each user is identified by
user ID (login name) and password as a member of one user group with one user role.
The Device Manager system user groups are: Admin, StorageAdmin, and Guest. These predefined user groups can only contain users of the designated role. The Admin group contains
only System Administrators, the StorageAdmin group contains only Storage Administrators,
and the Guest group contains only guest users. The system user groups cannot be deleted.
Device Manager also allows you to define user groups tailored to your specific access
requirements. Users assigned to a user-defined user group can access and operate only the
resources (logical groups, hosts, LDEVs) assigned to the user group. The user-defined user
groups can contain local users of each role. For example, the Marketing group can contain
Local System Administrators, Local Storage Administrators, and Local Guest users.
The HiCommand Device Manager user groups and user roles are (see Table 2.1):
System Administrator and Local System Administrator. The System Administrator is

responsible for creating and deleting user accounts and has access all Device Manager
functionality, including storage configuration and data management as well as user
operations. The System Administrator can control access permissions for Device Manager
users on an object-by-object basis, such as access to a logical group, host, or LDEV.
The user within a user-defined user group whose assigned role is Local System
Administrator has the same operating permissions as the System Administrator, but only
for the resources that the user group can access. The Local System Administrator can
create or delete user accounts within a user group, and configure other users within a
user group.
Storage Administrator and Local Storage Administrator. The Storage Administrator can
perform all storage configuration and data management operations, but cannot perform
Device Manager user-management operations such as creating or deleting user accounts.
The users within a user-defined user group whose assigned role is Local Storage
Administrator have the same operating permissions as users whose role is Storage
Administrator, but only for the resources that the user group can access. Local Storage
Administrators can create storage groups within a user group or configure LUN security
for storage.
Guest and Local Guest. The Guest user can view the resources that Device Manager
manages, including alerts and historical performance data collected by Device Manager,
but does not have permission to perform operations on resources by using Device
Manager. The System Administrator can specify the objects (e.g., storage subsystems or
array groups) that can be viewed by users whose role is Guest.
The users within a user-defined user group whose assigned role is Local Guest have view
permissions for the resources that the user group can access. A user whose role is Local
Guest cannot view the storage subsystem information, alerts, or reports.
16
Chapter 2 HiCommand Device Manager Operations
See section 6.3 for instructions on performing user group operations. See section 6.2 for
instructions on performing user account operations.
Table 2.1
HiCommand Device Manager User Roles
User Role
Description
System Administrator
Manages Device Manager user accounts and user groups.

Can access all Device Manager functionality and resources.
Storage Administrator
Configures and manages storage subsystems.

Can access all Device Manager functionality and resources, but cannot configure user
accounts.
Guest
Can view all Device Manager resources.
Local System Administrator
Manages user accounts within a user group. Also performs operations on the users in the user
group.
Can use all Device Manager functionality to access the resources assigned to the user group.
The physical information of a storage subsystem is not assigned to the user-defined user
group. Therefore, a user whose role is Local System Administrator cannot add or delete a
storage subsystem, perform operations in a Physical View display or alert screen, or view a
report.
Local Storage Administrator
Can use Device Manager functionality, except for configuring user accounts, to access the
resources assigned to the user group.
Like Local System Administrator, a user whose role is Local Storage Administrator cannot add
or delete a storage subsystem, perform operations in a Physical View display or alert, or view
a report.
Local Guest
Can view only the resources assigned to the user group.
Peer
Reserved for use by Device Manager Agent only.
Note: HiCommand Device Manager users with the authority to administer other users
cannot give other users greater authority than their own level of authority.
17
2.2
Storage Management Operations

HiCommand Device Manager allows you to perform storage management operations for the
storage on the subsystems which have been added to HiCommand Device Manager.
18
Storage Groups. HiCommand Device Manager allows you to create and manage groups
of LUNs (volume paths). The LUNs assigned to a storage group can be manipulated as a
group. Storage groups must contain logical devices from the same storage subsystem. A
storage group can contain only LUNs, not other groups.
Logical Groups. HiCommand Device Manager allows you to create and manage one or
more storage groups under a logical group. A logical group can contain storage groups
containing LUNs or additional logical groups. This additional level of grouping creates a
file-system approach to storage management and allows you to tailor your HiCommand
Device Manager system to your operational environment.
User Groups. HiCommand Device Manager allows you to create and manage one or
more user groups. Each user group is associated with one or more logical groups, hosts,
and LDEVs, which will be visible to the users in the user group. When you add a new user
and specify a user-defined user group for the new user, this user will only be able to
access the resources (logical groups, hosts, LDEVs) associated with that user group.
2.3
Subsystem and Volume Configuration Operations

The HiCommand Device Manager 3.1 Web Client enables you to view and manage the
configuration of Hitachi TagmaStore USP Hitachi Lightning 9900 V Series (9900V), Hitachi
Lightning 9900, Hitachi Thunder 9500 V Series, Hitachi Thunder 9200, and Sun StorEdge
T3 array storage subsystems from a web browser.
HiCommand Device Manager 3.5 provides the following functions for all supported storage
subsystems:
Subsystem Discovery. When you add a subsystem to HiCommand Device Manager, the
HiCommand Device Manager Server discovers the storage subsystem on the
HiCommand Device Manager system network and determines its identity (e.g., serial
number, IP address) and configuration.
Configuration Display. HiCommand Device Manager displays detailed configuration

information for each storage subsystem added, including: logical volume and physical
disk drive information, array groups, RAID levels, ports, cache memory, microcode
levels, and other subsystem-specific information (e.g., capacity for 9200 and T3, number
and type of back-end array processors (ACPs) for 9900V and 9900).
LUN Scan. The LUN Scan operation (see section 8.3) examines all LUNs on the subsystem
and automatically creates a hierarchy of logical groups and storage groups organized by
port to contain all of the existing LUNs on the subsystem. The LUN Scan also causes
Device Manager to register unique hosts for all WWNs in the subsystem. The attributes of
the host registered by Device Manager are updated when the Device Manager agent
reports information about the host.
A LUN Scan must be performed according to the following sequence:
(a) During HiCommand Device Manager initial setup, a LUN Scan should be performed
(selected) only after all hosts (name and WWNs) have been registered to the Device
Manager Server. Hosts are registered to the Device Manager Server by manually
entering them via the Web Client or Device Manager's Command Line Interface (CLI),
or by being notified from the Device Manager Agent.
(b) When storage on an existing subsystem has been assigned to a new host(s) not
recognized by the HiCommand Device Manager, ensure that the host(s) are
registered to the Device Manager Server before performing a LUN Scan operation.
(c) If there are no new hosts, you can perform a LUN Scan operation immediately after
a subsystem discovery and after a subsystem Refresh operation.
Refresh. The Refresh operation (see section 10.1.4) rediscovers a storage subsystem.
Perform a Refresh operation when changes have been made to the storage subsystem
other than through the HiCommand Device Manager system.
Alert Presentation. HiCommand Device Manager displays SNMP traps, errors, and other
conditions for each storage subsystem which has been added to the HiCommand Device
Manager Server (see section 5.5).
Path Assignment. HiCommand Device Manager allows you to add and delete volume
paths (i.e., port, LUN) for the devices on the storage subsystems (see sections 8.4 and
8.5).
19
2.3.1
Configuration Operations for the TagmaStore USP Subsystem

HiCommand Device Manager supports the following subsystem and volume configuration
functions for the TagmaStore USP subsystem:
Configure ports. HiCommand Device Manager allows you to configure the host mode
and fibre topology settings for the fibre-channel ports on the TagmaStore USP
subsystem.
Configure adapters. HiCommand Device Manager allows you to configure the speed
mode for the fibre-channel adapters on the TagmaStore USP subsystem.
Create/Delete LDEVs. HiCommand Device Manager allows you to create new LDEVs and
delete existing LDEVs on the TagmaStore USP subsystem.
Configure LUN Expansion (LUSE). HiCommand Device Manager allows you to configure
custom-size LUSE volumes on the TagmaStore USP subsystem. A LUSE device is a
combined LU which can be from 2 to 36 times larger than a standard OPEN-x LU. LUSE
devices are created from unallocated LDEVs.
You can create a TagmaStore USP LUSE device that does not have a volume path (see
section 8.6). You can also create a TagmaStore USP LUSE device when allocating a
volume path to an LDEV (see section 8.4) or when adding storage to a storage group (see
section 7.6.2).
Add/Delete volume paths. HiCommand Device Manager allows you to add and delete
volume paths (i.e., ports, host storage domains, or LUNs) for the LDEVs on the
connected TagmaStore USP subsystems.
Note on High Availability: HiCommand Device Manager allows you to configure
multiple paths to volumes as needed for path failover capability.
For details about TagmaStore USP LUN management, see the LUN Management User's
Guide.
20
Universal Volume Manager: In a TagmaStore USP subsystem, volumes of another

storage subsystem connected via a SAN can be handled as virtual TagmaStore USP
volumes. This feature is called the Universal Volume Manager. The following shows an
example of system configuration using the Universal Volume Manager.
Figure 2.1
System Configuration (When Using Universal Volume Manager)
When using Universal Volume Manager, you can manage volumes of the other storage
subsystem as virtual TagmaStore USP volumes by mapping them to the TagmaStore USP
subsystem. In this case, the storage subsystem connected to the TagmaStore USP
subsystem is called an external subsystem. Of the volumes that the external subsystem
manages, those volumes mapped to the TagmaStore USP subsystem are called external
volumes.
The volumes that the TagmaStore USP subsystem manages using Universal Volume Manager
are called internal volumes.
A port for connecting the TagmaStore USP subsystem to the external subsystem is called an
external port.
For details about Universal Volume Manager, see the External Storage Management User's
Guide.
21
Configuration Operations for the Lightning 9900 V Series Subsystem

The Lightning 9900 V Series subsystem provides many benefits and advantages as well as
advanced new features for the user, including double or more scalability from the 9900
subsystem in both capacity and performance. The 9900V subsystem supports an intermix of
fibre-channel, ESCON, and FICON host attachment for heterogeneous environments and
provides high performance, high reliability, and high scalability in network-attached storage
(NAS) and storage-area network (SAN) environments. The 9900V subsystem employs and
improves upon the key characteristics of generations of successful Hitachi disk storage
subsystems to achieve the highest level of performance and reliability currently available.
The advanced components, functions, and features of the Lightning 9900 V Series represent
an integrated approach to data retrieval and storage management.
HiCommand Device Manager supports the following subsystem and volume configuration
functions for the Hitachi Lightning 9900V subsystem:
Configure Ports. HiCommand Device Manager allows you to configure the host mode
and fibre topology settings for the fibre-channel ports on the Lightning 9900V subsystem
(see section 10.3.1).
Configure Adapters. HiCommand Device Manager allows you to configure the speed
mode for the fibre-channel adapters on the 9900V subsystem (see section 10.3.4).
Standard mode is the default mode. High-speed mode provides faster access speed by
using more processors to handle data access. However, high-speed mode limits the
number of available ports to one port on the channel adapter (CHA) board.
delete existing LDEVs on the Hitachi 9900V subsystem (see sections 10.5.3, 10.5.4). You
can create standard OPEN-x LDEVs or custom-size Virtual LVI/LUN devices which are
smaller than standard LDEVs (minimum size = 36,000 KB for other than OPEN-V,
48,000 KB for OPEN-V).
Configure LUN Expansion (LUSE). HiCommand Device Manager allows you to configure
custom-size LUSE volumes on the Hitachi 9900V subsystem. A LUSE device is a combined
LU which can be from 2 to 36 times larger than a standard OPEN-x LU. LUSE devices are
created from unallocated LDEVs.
You can create a 9900V LUSE device that does not have a volume path (see section 8.6).
You can also create a 9900V LUSE device when allocating a volume path to an LDEV (see
section 8.4) or when adding storage to a storage group (see section 7.6.2).
Add/Delete Volume Path. HiCommand Device Manager allows you to add and delete
volume paths (i.e., port, host storage domain, LUN) for the LDEVs on the connected
9900V subsystems.
For further information on 9900V LUN management, please refer to the Hitachi Lightning
9900 V Series LUN Manager Users Guide (MK-92RD105).
22
2.3.2
Configuration Operations for the Lightning 9900 V Series Subsystem

The Hitachi Lightning 9900 subsystem provides high-speed response, continuous data
availability, scalable connectivity, and expandable capacity for heterogeneous storage
environments. The Lightning 9900 is designed for use in 724 data centers that demand
high-performance, non-stop operation. The 9900 is compatible with industry-standard
software and supports concurrent attachment to multiple host systems and platforms. The
9900 subsystem can operate with multihost applications and host clusters and is designed to
handle very large databases as well as data warehousing and data mining applications that
store and retrieve terabytes of data. The Lightning 9900 can be configured for all-open,
multiplatform, or all-mainframe operations.
HiCommand Device Manager 3.5 supports the following subsystem and volume configuration
functions for the Hitachi Lightning 9900 V subsystem:
and fibre topology settings for the fibre-channel ports on the Lightning 9900 V
subsystem (see section 10.3.1).
Configure Adapters. HiCommand Device Manager allows you to configure the speed
mode for the fibre-channel adapters on the Lightning 9900 subsystem (see section
10.3.4). Standard mode is the default mode. High-speed mode provides faster access
speed by using more processors to handle data access. However, high-speed mode limits
the number of available ports to half of the ports on the channel adapter board.
Configure LUN and WWN Groups. HiCommand Device Manager allows you to configure
the LUN groups and WWN groups on the Lightning 9900 subsystem, including adding,
deleting, and modifying LUN groups and WWN groups (see sections 10.3.2 and 10.3.3).
delete existing LDEVs on the Lightning 9900 subsystem (see sections 10.5.3 and 10.5.4).
You can create standard OPEN-x LDEVs or custom-size Virtual LVI/LUN devices which are
smaller than standard LDEVs (minimum size = 36,000 KB).
LUN Expansion (LUSE). HiCommand Device Manager allows you to configure customsize LUSE volumes on the Lightning 9900 subsystem. A LUSE device is a combined LU
which can be from 2 to 36 times larger than a standard OPEN-x LU. LUSE devices are
created from unallocated LDEVs.
You can create a 9900 LUSE device only when allocating a volume path to an LDEV (see
section 8.4) or when adding storage to a storage group (see section 7.6.2). You cannot
create a 9900 LUSE device that does not have a volume path.
volume paths (i.e., port, LUN) for the LDEVs on the connected 9900 subsystems.
For further information on 9900 LUN management, please refer to the Hitachi Lightning
9900 LUN Manager Users Guide (MK-90RD003).
23
2.3.3
Configuration Operations for the Thunder 9500 V Series Subsystem

The Hitachi Thunder 9500 V Series subsystem is a high-performance, medium-capacity
storage array with added features designed to reduce the possibility of data loss due to the
failure of any single component. Disk array installation and setup are simplified using the
Resource Manager 9500V program included with the subsystem. Many parts are replaceable
while the disk array is online. Cache memory has a battery backup to preserve cache
contents in the event of a power failure.
functions for the Hitachi Thunder 9500 V Series subsystem:
and fibre topology settings for the fibre-channel ports on the Thunder 9500V subsystem
Create/Delete Array Groups. HiCommand Device Manager allows you to create new
array groups and delete existing array groups on the Thunder 9500V subsystem (see
sections 10.4 and 10.4.3).
Create/Delete LDEVs. HiCommand Device Manager allows you to create new LDEVs
(internal LUs) and delete existing LDEVs on the Thunder 9500 V subsystem (see sections
10.5.3 and 10.5.4).
Configure Spare Drives. HiCommand Device Manager allows you to configure the spare
drives on the Thunder 9500V subsystem (see section 10.4.4).
LUN Expansion (LUSE). HiCommand Device Manager allows you to configure customsize LUSE volumes on the Thunder 9500V subsystem. A LUSE device is a combined LU
which can be larger than a standard LU. LUSE devices are created from unallocated
LDEVs. This function corresponds to the LUN Expansion function (however, the size
expansion of one LU is not supported). The LUN Expansion functionality that increases
the size of an LU without combining with other LDEVs is not supported.
You can create a 9500V LUSE device that does not have a volume path (see section 8.6).
You can also create a 9500V LUSE device when allocating a volume path to an LDEV (see
volume paths (i.e., port, LUN) for the LDEVs on the connected 9500V subsystems.
For further information on 9500V LUN management, please refer to the Hitachi Thunder
9500 V Series Resource Manager 9500V Users Guide (MK-92DF605).
Note: The 9500V subsystem provides two functions to increase the size of an LU: Unified
LU, and LU Expansion. HiCommand Device Manager supports the Unified LU function,
which concatenates different LDEVs to create a larger size LU. The LU Expansion
function, which increases LU size without concatenating other LDEVs, is not yet
supported.
24
2.3.4
Configuration Operations for the Thunder 9200 Subsystem

The Hitachi Thunder 9200 is a high-performance, medium-capacity storage array with
added features designed to reduce the possibility of data loss due to the failure of any single
component. Disk array installation and setup are simplified using the Resource Manager 9200
program included with the subsystem. Many parts are replaceable while the disk array is
online. Cache memory has a battery backup to preserve cache contents in the event of a
power failure.
functions for the Hitachi Thunder 9200 subsystem:
and fibre topology settings for the fibre-channel ports on the Thunder 9200 subsystem
Create/Delete Array Groups. HiCommand Device Manager allows you to create new
array groups and delete existing array groups on the Thunder 9200 subsystem (see
sections 10.4 and 10.4.3).
Create/Delete LDEVs. HiCommand Device Manager allows you to create new LDEVs
(internal LUs) and delete existing LDEVs on the Thunder 9200 subsystem (see sections
10.5.3 and 10.5.4).
WARNING: Make sure that only one Web Client session is formatting LUs on the same
9200 subsystem. If multiple Web Clients are formatting multiple LUs at the same time,
this can cause the 9200 to become unavailable to the servers using it.
drives on the Thunder 9200 subsystem (see section 10.4.4).
LUN Expansion (LUSE). HiCommand Device Manager allows you to configure customsize LUSE volumes on the Thunder 9200 subsystem. A LUSE device is a combined LU
which can be larger than a standard LU. LUSE devices are created from unallocated
LDEVs. This function corresponds to the integrated functions of LUs in the Thunder
9200. The LUN Expansion functionality that increases the size of an LU without
combining with other LDEVs is not supported.
You can create a 9200 LUSE device that does not have a volume path (see section 8.6).
You can also create a 9200 LUSE device when allocating a volume path to an LDEV (see
volume paths (i.e., port, LUN) for the LDEVs on the connected 9200 subsystems.
For further information on 9200 LUN management, please refer to the Hitachi Thunder
9200 Resource Manager 9200 Users Guide (MK-90DF505).
Note: The 9200 subsystem provides two functions to increase the size of an LU: Unified
LU, and LU Expansion. HiCommand Device Manager supports the Unified LU function,
which concatenates different LDEVs to create a larger size LU. The LU Expansion
function, which increases LU size without concatenating other LDEVs, is not yet
supported.
25
2.3.5
Configuration Operations for the Sun StorEdge T3 Array

The Sun StorEdge T3 disk tray is a high-performance storage device that provides a RAID
architecture for modular, scalable data storage. The StorEdge T3 disk tray contains the
controller card and nine disk drives with fibre-channel connectivity to the data host. The
disk tray includes redundant, hot-swappable components and automatic notification of
failed components. The disk tray can be used either as a standalone storage unit or as a
building block, interconnected with other StorEdge T3 disk trays and configured in various
ways to provide a storage solution optimized to the host application.
The StorEdge T3 supports either one or two array groups either with, or without, a spare
drive. Each array group may contain exactly one LU, and the LU is mounted on (connected
to) the single port of the T3. For example, if all nine drives of a T3 are configured into a
single array group, the size of LDEV is 585 GB (for the standard 73-GB disk drives). Or, you
can configure two array groups to create two LDEVs: one group of five disk drives, and a
second group of four disk drives. A third example would be two four-drive array groups and
one spare drive (4+4+1).
In the optional partner-pair configuration, one T3 is physically placed on top of another, and
the two T3 units are interconnected via cables. In this configuration, the pair of T3s may be
managed externally as a single unit, appearing to be a single storage array with 18 disk
drives, two controllers, and two ports. With up to two array groups and two LDEVs per T3
array, a partner-paired T3 unit can have between two and four LDEVs.
In the partner-pair configuration, the T3 supports the multipath option. When the multipath
option is on, LDEVs on either individual T3 array may be exposed through the port on the
partner T3 in addition to the port on the T3 in which the LU physically exists.
Note: HiCommand Device Manager cannot turn the T3 multipath option on or off. This must
be done using the T3s standard telnet interface (please refer to the T3 user
documentation).
In most cases, a new T3 array is configured with one large LU. If this is your desired
configuration, no additional steps are necessary with HiCommand beyond discovering the
array and performing the LUN Scan. If you want to reconfigure the array, you will have to
delete the existing LDEV and array group before reconstructing the array as desired.
functions for the Sun StorEdge T3 array:
26
Create/Delete Array Group. HiCommand Device Manager allows you to create new
array groups and delete existing array groups on the Sun StorEdge T3 array (see
sections 10.4.2 and 10.4.3).
Create/Delete LDEV. HiCommand Device Manager allows you to create new LDEVs and
delete existing LDEVs on the Sun StorEdge T3 storage array (see sections 10.5.3 an d
10.5.4).
drive on the Sun StorEdge T3 storage array (see section 10.4.2). On the T3, you can add
a spare drive (optionally) at the same time as new array group creation. The spare drive
is deleted when you delete the array group which is associated with the spare drive.
volume paths (i.e., port, LUN) for the LDEVs on the connected T3 arrays.
27
2.4
Data Management Operations

HiCommand Device Manager allows you to perform data management operations such as
LUN security and data replication/backup (e.g., TrueCopy, ShadowImage) on the subsystems
which have been added to HiCommand Device Manager.
Note: The data management function must be installed and available on the storage
subsystem. If you need assistance, please contact the Hitachi Data Systems Support Center.
2.4.1
Data Management Operations for the TagmaStore USP Subsystem

LUN Security. HiCommand Device Manager enables you to perform the following LUN
security functions on the TagmaStore USP subsystem:
Secure/Unsecure Volumes. HiCommand Device Manager allows you to secure and

unsecure volumes (LUNs) as needed (i.e., add host(s) to or remove host(s) from a host
storage domain). After a LUN has been secured, only hosts with the specified WWNs are
permitted to access the LUN.
For details about LUN security, see the LUN Manager User's Guide.
Data Replication/Backup. HiCommand Device Manager allows you to perform the following
data replication/backup (copy) operations on the TagmaStore USP subsystem:
2.4.2
Set/Cancel Command Device. The command device is an LU used exclusively for

communicating with the CCI software on the host to control ShadowImage and/or
TrueCopy operations. For details about the command device, see the Hitachi Lightning
9900 V Series and Lightning 9900 Command Control Interface (CCI) User and
Reference Guide (MK-90RD011).
TrueCopy. TrueCopy allows you to perform synchronous and asynchronous remote copy
operations. For details about TrueCopy, see the Hitachi TrueCopy User's Guide.
ShadowImage. ShadowImage allows you to perform local (subsystem-internal) copy

operations which can provide a maximum of nine copies of a primary volume (P-VOL).
For details about ShadowImage, see the ShadowImage User's Guide.
Data Management Operations for the Lightning 9900 V Series Subsystem

security functions on the 9900V subsystem:

unsecure volumes (LUNs) as needed (i.e., add host(s) to or remove host(s) from a host
storage domain). After a LUN has been secured, only hosts with the specified WWNs are
permitted to access the LUN.
For further information on LUN security, please refer to the Hitachi Lightning 9900 V
Series LUN Manager Users Guide (MK-92RD105).
28
data replication/backup (copy) operations on the 9900V subsystem:
2.4.3

TrueCopy operations. For further information on the command device, please refer to
the Hitachi Lightning 9900 V Series and Lightning 9900 Command Control Interface
(CCI) User and Reference Guide (MK-90RD011).
operations. For further information on TrueCopy, please refer to the Hitachi Lightning
9900 V Series TrueCopy User and Reference Guide (MK-92RD108).

operations which can provide up to nine copies of a primary volume (P-VOL). For further
information on ShadowImage, please refer to the Hitachi Lightning 9900 V Series
ShadowImage Users Guide (MK-92RD110).
Data Management Operations for the Lightning 9900 Subsystem

security (Hitachi SANtinel) functions on the 9900 subsystem.
Configure LUN Groups. HiCommand Device Manager allows you to configure LUN
groups, including adding, deleting, and modifying LUN groups.
Configure WWN Groups. HiCommand Device Manager allows you to configure WWN
groups, including adding, deleting, and modifying WWN groups. The WWNs assigned to a
WWN group can be manipulated as a group.

unsecure volumes (LUNs) as needed. After a LUN has been secured, only hosts with the
specified WWNs are permitted to access the LUN.
For further information on 9900 LUN security, please refer to the Hitachi Lightning
9900 LUN Manager Users Guide (MK-90RD003).
data replication/backup (copy) operations on the 9900 subsystem:

the Hitachi Lightning 9900 V Series and Lightning 9900 Command Control Interface
(CCI) User and Reference Guide (MK-90RD011).
operations. For further information on TrueCopy, please refer to the Hitachi Lightning
9900 TrueCopy User and Reference Guide (MK-90RD051).

operations which can provide up to nine copies of a primary volume (P-VOL). For further
information on ShadowImage, please refer to the Hitachi Lightning 9900 ShadowImage
Users Guide (MK-90RD031).
29
2.4.4
Data Management Operations for the Thunder 9500 V Series Subsystem

security functions on the Thunder 9500 V subsystem:

unsecure volumes (LUNs) as needed. After a LUN has been secured, only the specified
WWN(s) is/are permitted to access the LUN.
For further information on 9500V LUN security, please refer to the Hitachi Thunder
9500 V Series SANtinel Users Guide (MK-92DF613).
data replication/backup (copy) operations on the 9500V subsystem:
30

the Hitachi Thunder 9500 V Series Command Control Interface (CCI) User and
Reference Guide (MK-92DF609).
operations. For further information on TrueCopy, please refer to the Hitachi Thunder
9500 V Series Synchronous TrueCopy Users Guide (MK-92DF608).

operations. For further information on ShadowImage, please refer to the Hitachi
Thunder 9500 V Series ShadowImage Users Guide (MK-92DF607).
QuickShadow. QuickShadow enables you to perform logical snapshot data replication

within the Thunder 9500 V subsystem to provide up to fourteen copies (V-VOLs) of each
primary volume (P-VOL). For further information on QuickShadow, please refer to the
Hitachi Thunder 9500 V Series QuickShadow 9500V Users Guide (MK-92DF666).
2.4.5
Data Management Operations for the Thunder 9200 Subsystem

security function on the 9200 subsystem:

unsecure volumes (LUNs) as needed. After a LUN has been secured, only the specified
WWN(s) is/are permitted to access the LUN.
For further information on 9200 LUN security, please refer to the Hitachi Thunder 9200
Resource Manager 9200 Users Guide (MK-90DF505).
data replication/backup (copy) operations on the 9200 subsystem:

the Hitachi Thunder 9200 Command Control Interface (CCI) User and Reference Guide
(MK-91DF557).
operations. For further information on TrueCopy, please refer to the Hitachi Thunder
9200 Synchronous TrueCopy Users Guide (MK-92DF579).

operations. For further information on ShadowImage, please refer to the Hitachi
Thunder 9200 ShadowImage Users Guide (MK-91DF541).
31
2.5
Link-and-Launch Operations
The HiCommand Device Manager link-and-launch feature allows administrators to easily
move across storage management software for a full view of their storage resources. For
information on the requirements for link-and-launch operations, see section 4.2.
HiCommand Device Manager provides link-and-launch integration with the following
software applications:
HiCommand Tuning Manager (see section 5.7.1)
Hitachi Dynamic Link Manager (HDLM) (see section 5.7.2)
Protection Manager (see section 5.7.3)
Provisioning Manager (see section 5.7.4)
Storage Navigator (see section 5.7.5)
NAS Blade Manager (see section 5.7.6)
Disk Array Management Program (DAMP) (see section 5.7.7)
Universal Volume Manager (see section 4.3.1)
DAMP (for Web) (see section 4.3.2)
Note: For information on adding a customized URL link-and-launch button to your Device
Manager installation, refer to the HiCommand Device Manager Command Line Interface
(CLI) User's Guide. Specifically, refer to the addURLLink, GetURLLink, and DeleteURLLink
API commands to obtain a better understanding of this functionality.
32
2.6
Report Operations
HiCommand Device Manager provides a built-in reporting function which allows the user to
generate reports in HTML format and comma-separated value (CSV) format (see Chapter 11).
The HiCommand Device Manager reports include:
Physical Configuration of Storage Subsystem report: Physical configuration of the

storage arrays being managed by HiCommand Device Manager
Storage Utilization by Host report: Storage utilization organized and presented by host
Storage Utilization by Logical Group report: Storage utilization organized and

presented by logical group
Users and Permissions report: HiCommand Device Manager users and permissions
33
2.7
System Security Operations

HiCommand Device Manager can be deployed securely in a variety of operational
environments, including private LAN, virtual private network (VPN), corporate intranet, and
even public internet. The security features for HiCommand Device Manager
communications (e.g., between Web Client and Server) can be customized for your
operational environment.
HiCommand Device Manager provides an end-to-end security context between the user and
HiCommand Device Manager Server which prevents message tampering and provides
privacy, user authentication, and nonrepudiation. Messages between the HiCommand
Device Manager Web Client and HiCommand Device Manager Server are secured when the
server is running in security mode 2 (SSL/TSL). For information about the server.properties
setting, please refer to the HiCommand Device Manager Server Installation and
Configuration Guide. The HiCommand Suite Common Component single sign-on feature
(see section 1.4) maintains user authentication across HiCommand products.
HiCommand Device Manager also provides an audit log of all operations and allows you to
combine and archive the audit logs for historical analysis. The HiCommand Suite Common
Component integrated logging feature (see section 1.4) provides a common log repository for
the various logs of the HiCommand suite products.
For further information on the HiCommand Device Manager security operations, please
refer to the HiCommand Device Manager Server Installation and Configuration Guide
(MK-91HC002).
34
Chapter 3
Installing the Device Manager Web Client
This chapter describes the requirements and procedures for installing the HiCommand
Device Manager Web Client software and the Java environment.
Requirements for Web Client operations (see section 3.1)
Preparing to access the Web Client (see section 3.2)
Installing the Java software environment (see section 3.3)
Configuring Java software for Client/Server operations (see section 3.4)
Upgrading the Java GUI (see section 3.5)
35
3.1
Requirements for Web Client Operations

The requirements for HiCommand Device Manager Web Client operations are:
HiCommand Device Manager Server. The HiCommand Device Manager Server must be
installed, configured, and fully operational. Please refer to the HiCommand Device
Manager Server Installation and Configuration Guide (MK-91HC002).
Note on Tuning Manager integration: For integration with HiCommand Tuning
Manager (single sign-on, common logging), the HiCommand Device Manager Server
(version 2.3 and higher) and the HiCommand Tuning Manager Server (version 1.1 and
higher) must be installed on the same server.
Note on Provisioning Manager integration: For integration with HiCommand
Provisioning Manager (single sign-on, common logging), the HiCommand Device
Manager Server and the HiCommand Provisioning Manager must be installed on the
same server.
Platform for HiCommand Device Manager Web Client. HiCommand Device Manager
3.5 supports the following operating systems for the Web Client:
Microsoft Windows 2000 Professional, Windows 2000 Server, Windows 2000

Advanced Server, and Windows 2000 Datacenter Server (Service Pack 3 or later)
Microsoft Windows XP Professional
Microsoft Windows Server 2003, Standard Edition, Windows Server 2003,

Enterprise Edition, Windows Server 2003, Datacenter Edition, and Windows Server
2003, Web Edition (32-bit processor version only)
Sun Solaris 8 or 9, SPARC platform only
Web Browser for HTML GUI. HiCommand Device Manager 3.5 supports the following
web browsers for the Web Client:
For Windows: Internet Explorer 6.0 or later
For Solaris: Netscape Navigator 6.2.3 or 7.0
Environment variable setting for Web Client in Solaris. When Web Client is used in
Solaris, the environment variable PATH must contain the entry for the Netscape
directory to enable launching the help and report functions and other applications.
Java execution environment. The HiCommand Device Manager Web Client requires
the following Java software environment:
Java Runtime Environment (JRE) version 1.4.2
Java Web Start (JWS) version 1.4.2
Note: Installing JRE version 1.4.2 automatically installs JWS 1.4.2.
36
Agent (recommended, optional). The HiCommand Device Manager Agent is

recommended but not required for Device Manager operations. If the host agent is
installed, Device Manager will display usage and file system statistics for the storage
assigned to the host. For details on the Device Manager Agent, please refer to the
HiCommand Device Manager Agent Installation Guide (MK-92HC019).
Chapter 3 Installing the Device Manager Web Client
Storage subsystems. Before adding a storage subsystem to HiCommand Device Manager

using the Web Client (or other client), you must make sure that the subsystem is
configured for Device Manager operations. For subsystem configuration requirements,
see the HiCommand Device Manager Server Installation and Configuration Guide
(MK-91HC002). See section 4.4 for copy pair requirements.
Important: HiCommand Device Manager displays but does not allow you to manage
mainframe volumes (e.g., 3390-3).
Link-and-launch. HiCommand Device Manager Web Client provides link-and-launch

functionality with several other software applications (e.g., HiCommand Tuning
Manager, Protection Manager, Provisioning Manager, NAS Manager, Storage Navigator,
HDLM, and DAMP). See section 4.2 for the requirements for Device Manager link-andlaunch operations.
37
3.2
Preparing to Access the Web Client

Before accessing the HiCommand Device Manager Web Client software, you need to
complete the following tasks.
1. Server installation. Make sure that the HiCommand Device Manager Server has been
installed and configured properly as described in the HiCommand Device Manager
Server Installation and Configuration Guide (MK-91HC002).
Note: HiCommand Device Manager Server installation (version 2.3 and higher) includes
installation of the HiCommand Suite Common Component.
HiCommand Tuning Manager integration: For integration with HiCommand Tuning
Manager (single sign-on and common logging), the HiCommand Device Manager Server
and the HiCommand Tuning Manager Server (version 1.1 or higher) must be installed on
the same server. See section 4.2 for detailed requirements.
HDLM integration: For link-and-launch integration for HDLM, the HDLM software must
be installed on the desired host(s). See section 4.2 for detailed requirements.
Protection Manager integration: For link-and-launch integration for Protection
Manager, Protection Manager must be installed on each host. See section 4.2for detailed
requirements.
Provisioning Manager integration: For integration with Provisioning Manager (single
sign-on and common logging), the HiCommand Device Manager Server and Provisioning
Manager must be installed on the same server. See section 4.2for detailed requirements.
Copy pair operations: If you plan to perform copy pair operations (ShadowImage,
TrueCopy, and/or QuickShadow) using Device Manager, the CCI software must be
installed on each host that will be managing copy pairs. See section 4.4 for detailed
requirements.
2. Server location. Write down the URL (IP address and/or host name) of the HiCommand
Device Manager Server and the port specified in the Server properties file (default =
23015). You will need this information to log in to the Device Manager Server.
Note: If you are not able to connect to the HiCommand Device Manager Server home
page, please see the troubleshooting information in Table 12.1.
3. Device Manager Agent. The HiCommand Device Manager Agent is optional. If you will
be using the Device Manager Agent, install the Agent on the applicable host(s). For
details, see the HiCommand Device Manager Agent Installation Guide (MK-90HC019).
4. Release Notes, Readme. Always read the HiCommand Device Manager Release Notes
and/or ReadMe file(s) before beginning.
38
3.3
Installing the Java Software Environment

HiCommand Device Manager utilizes client-server architecture to support application
distribution management. This web-distribution framework is used to install and
automatically update the Java GUI on a user's computer system.
Important: To host the HiCommand Device Manager Web Client, the Java 2 Runtime
Environment (JRE) and Java Web Start (JWS) software products must be installed first.
The Java Web Start software allows you to launch Java-based applications like the Java
GUI directly from the web. A Java-based application can be launched in three different
ways:
From a Web browser by selecting (clicking on) a link
From the Java Web Start built-in application manager, which tracks recently used
applications and provides quick access to favorite applications
From desktop icons or the Start menu (Windows systems only)
Note on upgrading: If the Java GUI is already installed and you have upgraded the Device
Manager version, see section 3.5 for information on upgrading the Java GUI.
3.3.1
Installing Java Software on a Windows System

HiCommand Device Manager 3.5 Web Client requires Java Runtime Environment (JRE)
version 1.4.2 and Java Web Start version 1.4.2.
Note: HiCommand Device Manager is approved for use with JRE version 1.4.1_02. Although
JRE version 1.4.2 is available from the Sun JRE website, HiCommand Device Manager does
not currently support it.
To install JRE and JWS on a Windows system:
1. Download the platform-specific installer for JRE version 1.4.2 from the Sun JRE website.
2. Read the Installation Instructions and Release Notes for JRE provided on the website.
3. Install the JRE 1.4.2 software using the JRE installer. Make sure that you read the
Readme file for the JRE software.
Note: Installation of JRE 1.4.2 includes installation of Java Web Start 1.4.2.
39
3.3.2
Installing Java Software on a Solaris System

HiCommand Device Manager 3.5 Web Client requires Java Runtime Environment (JRE)
version 1.4.2 and Java Web Start (JWS) version 1.4.2.
Note: The examples in the following instructions are for common installations. If your
system is set up differently, please make the necessary changes.
To install JRE and JWS on a Solaris system:
1. Download the platform-specific installer for JRE version 1.4.2 from the Sun JRE website.
Note: Installation of JRE 1.4.2 includes installation of Java Web Start 1.4.2.
2. Read the Installation Instructions and Release Notes for JRE provided on the website.
3. Install the JRE 1.4.2 software using the JRE installer. Make sure that you read the
Readme file for the JRE software.
40
3.4
Configuring Java Software for Client/Server Operations

You can configure Java Web Start and the applications launched from it using the Java
Web Start application manager.
You need to configure the Java Web Start software as follows:
Setting up the proxy (see section 3.4.1)
Setting up the log output (see section 3.4.2)
Setting up JRE when different JRE versions have been installed (see section 3.4.3)
Clearing the cache in Java Web Start (see section 3.4.4)
To start the Java Web Start application manager:
For Windows systems, select the Java Web Start shortcut on the desktop, or select
Java Web Start in the Programs menu.
For Solaris systems, execute the javaws command from the Java Web Start
installation directory.
Figure 3.1 shows the Java Web Start application manager.
Figure 3.1
Java Web Start Application Manager Window
41
3.4.1
Setting up the Proxy

You need to set up the proxy in Java Web Start in the following cases:
When accessing the Device Manager Server via a proxy
When a proxy is being used except for communications with a Device Manager Server
To change the proxy configuration in the Java Web Start software:

1. Start the Java Web Start application manager.
2. Select the File menu, and select Preferences.
3. On the Java Web Start Preferences panel, select the General tab.
When Java Web Start is installed, Use Browser is selected, and the proxy address and
port number configured in the browser are displayed on the right side. If automatic
configuration is used for the browser proxy configuration (e.g., automatic configuration
in Internet Explorer), Java Web Start does not configure its proxy properly. Manual
configuration is required for this case.
4. Select the Manual button.
5. In the HTTP Proxy and HTTP Port boxes, enter the address and port of the proxy server,
respectively.
6. In the No Proxy Hosts box, enter the URL of the Device Manager Server. (Use commas to
separate multiple hosts in this box.)
7. Select the OK button, and exit the Java Web Start application manager.
3.4.2
Setting up the Log Output

The Java Web Start has functionality for outputting, to a log file, messages sent to the
standard output. You can output the Java GUI's logs to a file using this functionality and
setting properties about the client in the Device Manager Server. For further information on
property settings for clients in Device Manager, see the HiCommand Device Manager Server
Installation and Configuration Guide (MK-91HC002).
If you launch Hitachi Dynamic Link Manager (HDLM) from the HiCommand Device Manager
Web Client (see section 2.5), Java Web Start collects these logs as well. To collect the
logs, you must set up log collection in Java Web Start.
To set up the Java Web Start log output options:
3. On the Java Web Start Preferences panel, select the Advanced tab.
4. If desired, select the Show Java Console box to display the messages that are output to
the log. This setting is optional.
42
5. In the Output Options box, select Log Output, and then enter the log file name in the
Log File Name field. This setting is required.
To enter the log file name, either type the desired file name in the Log File Name field,
or select the Choose Log File Name button to select an existing log file name.
6. Select OK to save your changes, and exit the Java Web Start application manager.
3.4.3
Setting up JRE when Different JRE Versions Have Been Installed

JWS uniquely manages the version of each installed JRE. All JREs are usable by default.
Therefore, when there are multiple versions of JRE and some of these versions are the same
as or higher than the version required for a Java application, JWS determines which version
of JRE is to be used. Because of this, you must set up JWS so that it uses the correct version
of JRE to execute Java applications.
To set up Java Web Start when different versions of JREs have been installed:
3. On the Java Web Start Preferences panel, select the Java tab.
4. Select the Find button.
5. Select the Next button.
6. Specify the JRE 1.4.2 installation directory, and then select the Next button. A dialog
box appears, notifying you that the JRE is found.
7. Select the Next button. You return to the Preferences dialog box. Confirm that 1.4.2 is
added in the Java Runtime Versions list.
8. In the Java Runtime Versions list, select the Enabled check box for JRE 1.4.2, and clear
the check boxes for other versions.
43
3.4.4
Clearing the Cache in Java Web Start

If a previous version of the Java GUI was installed, you may not be able to download the
latest version of it, even when upgrading Device Manager. In such a case, you must clear the
cache in Java Web Start in order to download the latest version of the Java GUI from the
Device Manager Server.
Caution: The following operation clears all resources downloaded by Java Web Start. To
start applications using Java Web Start, you will need to download those resources again.
The Java GUI will be downloaded automatically when you log in to the Device Manager
Server.
To clear the cache in Java Web Start:
2. Select the File menu, and then select Preferences.
3. On the Java Web Start Preferences panel, select the Advanced tab.
4. Select the Clear Folder button to open the Clear Applications Folder panel.
5. Select the Yes button.
44
3.5
Upgrading the Java GUI

When you upgrade your Java GUI, check the required versions of the Java Runtime
Environment (JRE) software and Java Web Start (JWS) software, and upgrade the JRE
and JWS software according to the Device Manager version. Table 3.1 lists and describes the
required JRE and JWS versions for each version of Device Manager, and indicates the
required action for upgrading the Java GUI.
After upgrading the JRE and JWS software to the required version, you can start using the
Java GUI. You do not need to manually update the Java GUI. Each time the Java GUI is
invoked, the Java Web Start software checks to ensure that the locally cached application
is the latest version available from the HiCommand Device Manager Server. If not, it
downloads and invokes the newer version.
Table 3.1
Upgrading the Web Client Java GUI
Device Manager
Version
Required JRE
Required JWS
Required Action for Web Client Java GUI
03-50
1.4.2
1.4.2
From v3.1 to 03-50: upgrade JRE and JWS
3.1
1.4.1
1.2
From v3.0 to v3.1: none
3.0
1.4.1_02
1.2
From v2.4 to v3.0: upgrade JRE and JWS
2.4
1.3.1_06
1.0.1
2.3
1.3.1_06
1.0.1
From v2.2 to v2.3: upgrade JRE
2.2
1.3.1_03
1.0.1
2.1
1.3.1_03
1.0.1
From v2.0 to v2.1: upgrade JRE
Note: If you install HiCommand Device Manager version 3.1 over version 1.1 (or earlier), all
volumes in each logical group will appear as CVS volumes. Additionally, no disk usage
information will be displayed. Hitachi recommends that perform a refresh for all storage
subsystems that were discovered by the previous version of HiCommand.
45
46
Chapter 4
Preparing for and Starting Device Manager

Operations
This chapter describes the preparation required before using Device Manager and provides
instructions for starting Device Manager operations:
Preparing to start HiCommand Device Manager operations (see section 4.1)
Link-and-launch requirements (see section 4.2)
Copy pair requirements (see section 4.4)
Logging in to HiCommand Device Manager (see section 4.5)
Starting HiCommand Device Manager operations (see section 4.6)
47
4.1
Preparing to Start HiCommand Device Manager Operations

Before starting Device Manager operations, you must perform the following tasks:
Device Manager Server. Make sure that the Device Manager Server is installed,
configured, and fully operational. Write down the IP address of the Device Manager
Server. For further information on the Server, please refer to the HiCommand Device
Manager Server Installation and Configuration Guide (MK-91HC002).
Note: Make sure to read the Release Notes and ReadMe file(s) for Device Manager.
License Key. You must register the license key of the storage subsystem you want to
manage in Device Manager. Write down the license key or obtain the license key file.
Web Client Environment. Make sure that the JRE and JWS software have been installed
and configured properly on the Web Client system as described in Chapter 3.
Storage Subsystems. Make sure that the storage subsystems are configured for
HiCommand Device Manager operations as specified in the HiCommand Device Manager
Server Installation and Configuration Guide.
Write down the IP address of each storage subsystem that you want to manage using
HiCommand Device Manager. You will need the IP address to add the subsystem to
HiCommand Device Manager.
Important: Always make sure that only one HiCommand Device Manager Server at a
time is actively managing a single storage subsystem.
Hosts with Device Manager Agent. Hosts on which the Device Manager Agent is installed
are recognized automatically by the Web Client. Make sure to run the Device Manager
Agent after installing the Device Manager Server.
For further information on the Agent, refer to the HiCommand Device Manager Agent
Installation Guide.
Note: Device Manager 3.5 recognizes NAS-attached hosts.
48
Hosts without Device Manager Agent. For each host that will not have the Device
Manager Agent installed, write down the port WWN(s). You will need the WWNs when
you add the hosts manually to HiCommand Device Manager.
Link-and-Launch Operations. HiCommand Device Manager provides link-and-launch

functionality for the following applications:
HiCommand Tuning Manager
Hitachi Dynamic Link Manager (HDLM)
9900V Storage Navigator
9900V NAS Blade
9500V Disk Array Management Program (DAMP)
Registered third-party applications
Chapter 4 Preparing for and Starting Device Manager Operations
Third-Party Applications. To perform link-and-launch operations, ensure that the linkand-launch requirements are met. See section 4.2.
Exclusive Access to Subsystems. The Device Manager Server requires exclusive access
to a storage subsystem. You must make sure that a single storage subsystem is always
managed by a single Device Manager Server. Do not build a system configuration where
multiple Device Manager Servers may be able to manage the same storage subsystem.
If Device Manager and another management tool (e.g., USP or 9900V Storage Navigator
or SVP, or 9500V Resource Manager) modify the subsystem configuration at the same
time, the operation(s) may not be performed properly. Before using Device Manager Web
Client (or CLI) to modify the configuration of a subsystem, make sure that the subsystem
is not being accessed by any other management tool. The USP, 9900V, or 9900 SVP must
be in View mode (not in Modify mode).
49
4.2
Link-and-Launch Requirements
HiCommand Tuning Manager Requirements
For integration with HiCommand Tuning Manager (single sign-on, common logging), the
HiCommand Device Manager Server (version 2.3 and higher) and the HiCommand
Tuning Manager Server (version 1.1 and higher) must be installed on the same server.
The Device Manager application start-up information must be set to HiCommand Suite
Common Component. For instructions on setting the application start-up information,
(MK-91HC002).
Hitachi Dynamic Link Manager (HDLM) Requirements
HDLM and the Device Manager Agent must be installed on the management-target host
of Device Manager. Refer to the HDLM manual for the host platform (e.g., the Hitachi
Freedom Storage Hitachi Dynamic Link Manager (HDLM) Users Guide for Sun Solaris
Systems (MK-92DLM114).
HiCommand Protection Manager Requirements
HiCommand Protection Manager and the Device Manager Agent must be installed on the
management-target host of Device Manager. For details about Protection Manager, see a
user's guide for Protection Manager, such as the HiCommand Protection Manager Console User's Guide.
HiCommand Provisioning Manager Requirements
The HiCommand Device Manager Server (version 3.5 or later) and HiCommand
Provisioning Manager (version 3.5 or later) must be installed on the same server.
The Device Manager application start-up information must be set to HiCommand Suite
Common Component. For details about how to set the application start-up information,
(MK-91HC002).
Storage Navigator Requirements
50
Storage Navigator must be installed on the Lightning 9900V that is being managed by
Device Manager.
The Storage Navigator functions (e.g., FlashAccess, TrueCopy) must be installed and
enabled on the storage subsystem. Device Manager only displays functions that are
installed and enabled.
Caution: When using Web Client on a Solaris system, the following configurations are
required for calling the Storage Navigator functionality:
(a) Specifying Netscape used for Storage Navigator:
To enable Netscape to start, create the shell script netscapeforSN as follows:
Create a shell script named netscapeforSN, and code the following as

appropriate for your environment:
LD_LIBRARY_PATH= path-to-Netscape-supported-by-StorageNavigator $*
(Enter a single space after LD_LIBRARY_PATH=.)
The following example shows the coding when Netscape starts under
/usr/dt/appconfig/netscape/netscape:
#!/usr/bin/sh
LD_LIBRARY_PATH= /usr/dt/appconfig/netscape/netscape $*
Specify the execution permissions for the shell script netscapeforSN.
Modify the environment variable PATH so that the shell script netscapeforSN is
executed by entering netscapeforSN on the command line.
(b) Setting up the Netscape plug-in:

In the plugins directory for Netscape, create a symbolic link to the Java plug-in file
libjavaplugin_oji.so.
cd directory-storing-Netscape/plugins
ln -s /usr/local/j2re1_4_2/pligin/sparc/ns610/libjavaplugin_oji.so
After the setup finishes, restart the browser.

For details, see the Sun Microsystems web site.
Third-Party Software Application Requirements
Device Manager allows the Link-and-Launch of a URL per storage subsystem from the
Physical View of a storage subsystem. For details, please refer to the HiCommand
Device Manager Command Line Interface (CLI) User's Guide. Specifically, refer to the
addURLLink, GetURLLink, and DeleteURLLink API commands to obtain a better
understanding of this functionality.
51
4.3
Linkage with Related Products

The settings used to link Device Manager with Universal Volume Manager and DAMP (for Web)
are described in this section.
4.3.1
Linkage with Universal Volume Manager

Important: In Device Manager version 03-50, the Universal Volume Manager functionality is
applied only to TagmaStore USP among various subsystems. In this manual, storage to
which the Universal Volume Manager functionality is applied is called TagmaStore USP
hereafter.
Device Manager distinguishes internal volumes contained in TagmaStore USP and external
volumes to which LUs in the external subsystems have been mapped, and displayed them
separately in the TagmaStore USP management window. Thus, for example, if you want to
allocate reliable storage to a host, you can select a volume from the internal volumes. If you
want to allocate lower bit-cost storage for use as S-VOL of the copy pair functionality, you
can select a volume from the external volumes.
From a perspective of the external subsystem connected to TagmaStore USP, it is
impossible to identify that a certain LU is already used as the external volume for
TagmaStore USP. So, if you remove the LUN or LUN security settings for an external volume
in the external subsystem's management window, TagmaStore USP LU might also be
deleted. To avoid such a problem, HiCommand Device Manager displays which LU is used as
the external volume, also in the external subsystem's management window. To display
whether an LU in the external subsystem is the external volume, make sure that
HiCommand Device Manager has already found both TagmaStore USP and the external
subsystem.
The following describes the procedures for linking with Universal Volume Manager.
To link up with Universal Volume Manager:
1. Use HiCommand Device Manager to find TagmaStore USP and other external
subsystems.
HiCommand Device Manager manages the found TagmaStore USP and external
subsystems. Storage Navigator starts as the management window for TagmaStore USP.
2. Use Storage Navigator to set a TagmaStore USP port as the external port.
For details on how to set up ports, see the Universal Volume Manager User's Guide.
3. Specify an external subsystem port to be connected to the external port.
Device Manager manages the TagmaStore USP external port as a specific host. The
external port operates as a host for external volumes in the external subsystem. The
users can manage the external volumes that are allocated to the external port, as the
volumes of the specific host.
4. Specify an external volume in the external subsystem. Select the port specified in step
3, and then add storage. When you add storage, select the host that is identified as the
external port, and then add the LUN security.
52
5. Perform the LUN assignment and LUN security assignment for the specific host, which is
also the external port.
By using Storage Navigator that starts as the subsystem management window for
TagmaStore USP, map the external volumes that are set in the external subsystem as
an internal volume of TagmaStore USP.
After performing the above steps, you can use the external volumes set in the external
subsystem as well as LUs contained in TagmaStore USP.
Note: When setting a port or LU in the subsystems that are not supported by HiCommand
Device Manager, see the manual for the external subsystem's management tool.
Note: For details on notes on using external volumes, see the Universal Volume Manager
User's Guide.
4.3.2
4.3.2.1
Linkage with DAMP (for Web)

Prerequisites and Procedures
To perform DAMP launching, the DAMP (for Web) version must be 10.00 or later.
Install DAMP (for Web) on the machine where the HiCommand Device Manager Server is
installed.
Another Web server is necessary for using DAMP (for Web). In the following steps, the
Hitachi Web Server (HiCommand Base) is assumed to be a DAMP (for Web) Web server.
To launch DAMP (for Web):

1. Install DAMP (for Web).
2. Execute the alias information setting command (HWSAlias) in the following format:
In Windows:
installation-directory-of-Device-Manager-Server\HiCommandServer\
HWSAlias.bat set damp "installation-directory-of-DAMP (for Web)"
In Solaris:
/opt/HiCommand/HiCommandServer/
HWSAlias.sh set damp "installation-directory-of-DAMP (for Web)"
Caution:
Make sure that the path name specified in installation-directory-of-DAMP-(for-Web)
ends with a forward slash (/).
Caution:
Enclose installation-directory-of-DAMP-(for-Web) in double quotation marks (").
53
Caution:
In Windows, replace \ with / in the path name that is to be specified in installationdirectory-of-DAMP (for Web).
For example: C:/Program Files/DA Manager Web/
3. Specify the DAMP (for Web) URL in the launchapp.damp.url property of the
launchapp.properties file, in the following format:
launchapp.damp.url=http//{host-name|IP-address}:portID/program/DeviceManager/damp
Note: To use a local host, specify its IP address in {host-name|IP-address}.

4. Restart HiCommand Suite Common Component.
5. Restart HiCommand Device Manager Server.
Note: If you uninstall HiCommand Device Manager or DAMP (for Web) after setting alias
information for DAMP (for Web), the alias information cannot be deleted. To delete the alias
information, execute the following command:
In Windows:
C:\Program Files\HiCommand\DeviceManager\HiCommandServer\
HWSAlias.bat del damp
In Solaris:
/opt/HiCommand/HiCommandServer/
HWSAlias.sh del damp
4.3.2.2
Storage Subsystem Information to Be Registered Using DAMP (for Web)
To operate storage subsystems by launching DAMP, the storage subsystem information

must be registered in advance by using DAMP (for Web).
To register a unit name of the storage subsystem by using DAMP (for Web), use the IP
address with an H added to the front. (Example: If the IP address is 10.208.108.123, the
unit name will be H10.208.108.123).
The IP address used for a unit name is IP Address 1 or IP Address 2 from when
HiCommand Device Manager performed discovery.
54
4.4
4.4.1
Copy Pair Requirements

General Requirements
For details on the system configuration required to display the ShadowImage, TrueCopy, and
QuickShadow settings for the storage subsystems, see the HiCommand Device Manager
Server Installation and Configuration Guide (MK-91HC002).
Requirements for the Host
The following versions of Device Manager Agent must be installed on the host:
For the Thunder 9500V or for using copy pair information for QuickShadow: 3.0 or
later
For using the function for generating configuration definition files for copy pairs: 3.1
or later
For the TagmaStore USP: 3.5 or later
For cases other than above: 2.3 or later
The CCI software must be installed on each host which manages TrueCopy,
ShadowImage, and/or QuickShadow copy pair(s).
The LDEVs that will become the P-VOLs and S-VOLs must be assigned to the Host because
of command device security.
If pair management is performed by the central management method, the host that
manages the LDEVs centrally needs to meet the following requirements:
The target host must recognize the command device.
LUN security must be set for the target host.
Requirements for the Storage Subsystem
The applicable feature (ShadowImage, TrueCopy, and/or QuickShadow) must be

installed.
When TrueCopy is used, the remote control unit (RCU) must be set up in advance.
When ShadowImage is used, the system parameters must be set up in advance.
Command device security must be installed (therefore Resource Manager is a prerequisite) for this functionality.
Requirements for the Command Device
The target host must recognize the command device.
LUN security for the command device must be set for the target host.
The command device must not be mounted.
55
General Requirements for P-VOLs (SP-VOLs)
When pair management is performed for each host, the Device Manager Agent must
recognize the LDEV. If pair management is performed by the central management
method, Device Manager does not need to recognize the LDEV. When the Last Updated
column displays a date and time, it means that Device Manager Agent recognizes the
LDEV.
LUN security must be set for the target host.
The LDEV must be an OPEN system LDEV.
The LDEV must not be a command device.
The storage subsystem containing the LDEV must have a valid command device.
General Requirements for S-VOLs
56
When pair management is performed for each host, the LDEV must be recognized by
Device Manager Agent and must not be mounted. If pair management is performed by
the central management method, Device Manager does not need to recognize the LDEV.
If the LDEV is not mounted, the File System column for the LDEV is blank (storage group
information displayed under Logical Groups and Hosts views).
The LDEV must not be a command device.
LUN security must be set for the selected host.
The LDEVs capacity must be the same as the selected P-VOLs capacity.
For the TagmaStore USP, Thunder 9500V and 9200, the device emulation type must be
the same as the selected P-VOL.
For a USP, 9900V, or 9900 LUSE volume, the P-VOL and S-VOL must have the same
number of LDEVs contained in the LUSE.
For the Thunder 9500V and 9200, the number of data disks in the P-VOL and S-VOL must
be the same.
For the TagmaStore USP, any internal volume to which an external volume has been
mapped must not be in IO Suppression mode.
4.4.2
TrueCopy Requirements
Requirements for the Device Manager Server
The LDEVs which will become the P-VOLs and S-VOLs must be managed by the same Device
Manager Server.
Requirements for a TrueCopy P-VOL in the TagmaStore USP
The requirements for the TagmaStore USP LDEV that will be a TrueCopy P-VOL are:
The LDEV must not be a TrueCopy P-VOL, S-VOL, SP-VOL, or S-VOL of the SP-VOL.
Note: If you want to use a ShadowImage S-VOL as the P-VOL for a TrueCopy copy pair,
the status of the ShadowImage copy pair must be Split.
The MCU-RCU path must already be defined (e.g., using the Storage Navigator or the
SVP).
Any internal volume to which an external volume has been mapped must not be in the IO
Suppression mode.
Requirements for a TrueCopy P-VOL in the 9900V or 9900

The requirements for the 9900V/9900 LDEV that will be a TrueCopy P-VOL are:
The LDEV must not be a TrueCopy P-VOL, S-VOL, SP-VOL, or S-VOL of the SP-VOL.
Note: If you want to use a ShadowImage S-VOL as the P-VOL for a TrueCopy copy pair,
the status of the ShadowImage copy pair must be Split.
The MCU-RCU path must already be defined (e.g., using the Storage Navigator or Remote
Console software or the SVP).
Requirements for a TrueCopy P-VOL in the Thunder 9500V

The requirements for the Thunder 9500V LDEV that will be a TrueCopy P-VOL are:
The LDEV must not be a TrueCopy P-VOL or S-VOL.
The RAID level must be RAID1, RAID5, or RAID0 + 1.
An LUSE volume must consist of 16 or fewer LUs. However, you cannot specify the LUSE
volume as a P-VOL if the microcode is smaller than X657/A.
Requirements for a TrueCopy P-VOL in the Thunder 9200

The requirements for the Thunder 9200 LDEV that will be a TrueCopy P-VOL are:
The LDEV must not be a ShadowImage S-VOL.
The RAID level must be RAID1, RAID5, or RAID0 + 1.
The LDEV must not be a LUSE volume.
57
Requirements for a TrueCopy S-VOL

The requirements for the LDEV that will be a TrueCopy S-VOL are:
58
The selected P-VOL must not already be assigned to a TrueCopy copy pair.
For the TagmaStore USP, Lightning 9900V, or 9900 Series, the RCU of the S-VOL must
be specified for the MCU of the selected P-VOL. For details on RCU settings (remote copy
connection, ports, MCU-RCU paths), see the HiCommand Device Manager Server
Installation and Configuration Guide.
For the Thunder 9500V and 9200, paths for TrueCopy must be configured for the LDEV.
For the Thunder 9500V, the selected S-VOL must be a LUSE volume that consists of 16 or
fewer LUs. However, you cannot specify the LUSE volume as a S-VOL if the microcode is
smaller than X657/A.
For the Thunder 9200, the selected S-VOL must not be a LUSE volume.
The requirements for the storage subsystems that contain the selected LDEVs are:
For the Thunder 9500 V, the P-VOL and S-VOL must be in 9500V subsystems. For the
Thunder 9200, the P-VOL and S-VOL must be in 9200 subsystems. The TagmaStore
USP, Lightning 9900V and 9900 support mixed-subsystem pairs (e.g., 9900V-to9900).)
For the Thunder 9500V and 9200, the copy type cannot be TrueCopy Async.
For the Thunder 9500V and 9200, the RAID level for the P-VOL and S-VOL must be
RAID5 (2D + 1P ~ 15D + 1P).
4.4.3
ShadowImage Requirements
Requirements for a ShadowImage P-VOL (SP-VOL) in the TagmaStore USP
The requirements for the TagmaStore USP LDEV that will be a ShadowImage P-VOL (or SPVOL) are:
The LDEV must not be a ShadowImage leaf volume (second layer S-VOL).
If the LDEV is a ShadowImage P-VOL, there must not be more than two S-VOLs.
If the LDEV is a ShadowImage SP-VOL, there must not be more than one S-VOL.
Any internal volume to which an external volume has been mapped must not be in the IO
Suppression mode.
Requirements for a ShadowImage P-VOL (SP-VOL) in the 9900V or 9900

The requirements for the 9900V/9900 LDEV that will be a ShadowImage P-VOL (or SP-VOL)
are:
The LDEV must not be a ShadowImage leaf volume (second layer S-VOL).
If the LDEV is a ShadowImage P-VOL, there must not be more than two S-VOLs.
If the LDEV is a ShadowImage SP-VOL, there must not be more than one S-VOL.
Requirements for a ShadowImage P-VOL in the Thunder 9500V

The requirements for the 9500V LDEV that will be a ShadowImage P-VOL are:
The LDEV must not be a ShadowImage P-VOL or S-VOL (cascade is available on the
TagmaStore USP, Lightning 9900V, and 9900).
Requirements for a ShadowImage P-VOL in the Thunder 9200 Series

The requirements for the 9200 LDEV that will be a ShadowImage P-VOL are:
The LDEV must not be a ShadowImage P-VOL or S-VOL (cascade is available on the
TagmaStore USP, Lightning 9900V, and 9900).
Requirements for a ShadowImage S-VOL

The requirements for the LDEV that will be a ShadowImage S-VOL are:
The LDEV must reside in the same storage subsystem as the selected P-VOL.
For the TagmaStore USP, Lightning 9900V, and 9900, there must not be more than two
S-VOLs already assigned to the selected P-VOL. If an SP-VOL is selected as the P-VOL,
there must not be more than one S-VOL already assigned to the selected SP-VOL.
For the Thunder 9500V and 9200, the LDEV must not be a ShadowImage P-VOL or S-VOL.
For the Thunder 9500V and Thunder 9200, the default controller must be the same as
that for the selected P-VOL.
59
4.4.4
QuickShadow Requirements
Requirements for a QuickShadow P-VOL
The requirements for an LDEV that will be a QuickShadow P-VOL are:
The LDEV must be displayed as a QuickShadow P-VOL on the Detailed Information LDEV-number dialog box, and the display for Copy Status must be Simplex.
The number of V-VOLs must not exceed 14.
The LDEV must not be a ShadowImage P-VOL or S-VOL.
If the microcode is smaller than X657/A, the LDEV must not be a TrueCopy P-VOL or SVOL.
Requirements for a QuickShadow S-VOL

The requirements for an LDEV that will be a QuickShadow S-VOL are:
60
The LDEV must be displayed as a V-VOL of the selected QuickShadow P-VOL on the
Detailed Information - LDEV-number dialog box, and the status of the copy pair must be
Simplex.
4.5
Logging in to HiCommand Device Manager for the First Time after Installation
After you have prepared for HiCommand Device Manager operations as described in 4.1,
4.2, and 4.4 above, you can start HiCommand Device Manager operations. The System
Administrator must log in first.
To log in to HiCommand Device Manager:
1. Launch the web browser, and enter the URL for the Device Manager Server:
http://Device-Manager-server-address:port-number/DeviceManager/
Device-Manager-server-address = IP address or host name of Device Manager Server
(e.g., localhost)
port-number = port number of the HiCommand Common Web Service (default = 23015)
Note: Use https and port 23016 (default) for SSL. For details on port numbers, see the
HiCommand Device Manager Server Installation and Configuration Guide.
The values in Device-Manager-server-address and port-number are the values that
were specified during the installation. For details, see the HiCommand Device Manager
If the IP address is 172.16.45.1 and the port number is 23015 (which is the default
value), enter the URL as follows:
http://172.16.45.1:23015/DeviceManager/
The Device Manager Login panel is displayed (see Figure 4.1). If you are accessing Device
Manager for the first time after installation, the Please input your License Key warning
appears. Select the License button.
If the license key for this installation has already been entered, go to step 4.
2. On the Version Information for Device Manager panel (see Figure 4.2), register the
license key of the storage subsystem you want to manage in Device Manager. Enter the
license key or specify the license key file, and then choose the Save button to register
the license. Then, choose the Close button. You are returned to the Device Manager
Login panel.
3. On the Device Manager Login panel, enter your user ID (login name) and password, and
then select Login. The password is case-sensitive.
4. The HiCommand Device Manager main window appears (see Figure 4.3). This window
provides access to all HiCommand Device Manager functions. See section 4.6 for
instructions on starting HiCommand Device Manager operations.
Important: To operate the Device Manager correctly, the Device Manager Server and
Java GUI versions must be the same. Check the versions by performing the following
procedures:
To check the Device Manager server version, select About in the menu bar on the
HiCommand Device Manager main window.
To check the Java GUI version, select About in the menu bar in the Physical View,
or click the About button on the user administration window.
If the Java GUI version is earlier than the Device Manager Server version, clear the
cache in Java Web Start (see section 3.4.4), and then re-install the Java GUI.
61
Note: If a popup window is opened (for example, by executing a method from the main
window), and no operation is performed on it for 60 minutes or more, then the popup
window will become inoperable. In such a case, re-open the popup window and then retry
the operation.
Figure 4.1
62
HiCommand Device Manager Login Panel Showing License Warning
Figure 4.2
Version Information for Device Manager Panel
63
Figure 4.3
64
HiCommand Device Manager Main Window Initial Start-Up
4.6
Starting HiCommand Device Manager Operations

After you have installed HiCommand Device Manager, prepared for HiCommand Device
Manager operations, and logged in to the HiCommand Device Manager Server, you are
ready to start HiCommand Device Manager operations. This section provides an overview of
the tasks required to set up and start using HiCommand Device Manager.
Caution: For efficient creation of your HiCommand Device Manager environment, it is very
important to perform the following tasks in the following sequence.
To start HiCommand Device Manager operations:
1. Log in to HiCommand Device Manager as a System Administrator (see section 5.2). The
System Administrator should log in first to set up the users and access privileges.
2. Add the desired user groups and users, and assign user access capabilities (see sections
6.3 and 6.2).
Note: To prevent unauthorized access, make sure to either change the default System
Administrator login or add at least one System Administrator and then delete the default
System Administrator.
3. Create the logical group hierarchy for your storage groups (see section 7.3). If desired,
you can use the group hierarchy created by the LUN Scan operations, instead of creating
your own logical groups, and you can reconfigure your group hierarchy as needed (e.g.,
add and delete groups, change the level/parent of a group).
Storage groups can be nested within logical groups or at the top level as needed. A
logical group cannot be nested within a storage group.
Example of how to use logical groups:
For copy pair operations, you should consider creating a logical group for LUs that are
reserved or pooled for copy operations. You could then create a storage group for each
subsystem within the top-level logical group for copy volumes.
4. Add each host that will be managing storage (name and WWNs) to Device Manager by
either installing/running the Device Manager host agent on each host, or by entering
each host manually using the Device Manager Web Client (see section 9.3) or CLI.
Caution: It is recommended that you add all hosts before performing a LUN Scan
operation. If you do not enter the hosts before performing a LUN Scan, the LUN Scan will
automatically create a unique host name (HOST_0, HOST_1, etc.) for each WWN. This
can create a significant number of hosts depending on the size of the environment.
5. Add the connected storage subsystems to the Device Manager Server (see section
10.1.2). Volumes that the System Administrator or the Storage Administrator are allowed
to manage are placed in a logical group called All Storage that is created by Device
Manager.
Caution: The Device Manager Server requires exclusive access to a storage subsystem
(see section 4.1). You must make sure that a single storage subsystem is always managed
by a single Device Manager Server, and that Device Manager and another management
tool (e.g., 9900V Storage Navigator or SVP, 9500V Resource Manager) do not modify the
same subsystem at the same time. For TagmaStore USP and 9900V/9900, the SVP must
be in View mode.
65
6. Perform a LUN Scan operation on each newly-discovered subsystem. The LUN Scan
operation creates the LUN Scan logical group hierarchy and categorizes the existing LUNs
into subgroups organized by subsystem and port (see section 8.3). If the LUN Scan finds a
WWN which has not already been added to Device Manager, the LUN Scan creates a
unique host (HOST_0, HOST_1, etc.) for that WWN.
7. Review the list of hosts (see Chapter 9), and verify that all hosts to be managed have
been added. If the LUN Scan automatically created host names, you can rename these
hosts to more easily identify them, combine WWNs that are on a single physical host,
and delete the extraneous hosts as needed.
8. After completing steps (2) through (7), you are ready to perform storage operations (see
section 7.6), such as adding and moving storage, adding and deleting volume paths,
configuring LUN security, and managing copy pairs.
9. When you are finished performing Device Manager operations, make sure to log out to
prevent unauthorized access (see section 5.2 for instructions).
66
Chapter 5
Performing Device Manager System Operations
This chapter describes HiCommand Device Manager system operations. These include:
Using the Device Manager main window (see section 5.1)
Logging in and out of Device Manager (see section 5.2)
Viewing the version and license type information (see section 5.3)
Viewing the user profile information (see section 5.4)
Performing alert operations (see section 5.5)
Viewing the task list (see section 5.6)
Launching other applications (see section 5.7)
Note: After a window is opened (for example, by executing a method from the main
window), you cannot operate the window if 60 minutes or more passed without operating
the window. In this case, close and then re-open the window, and perform the operation
from the start.
Note: For information on the warning messages output by Device Manager Web Client, see
section 12.3.
67
5.1
Using the HiCommand Device Manager Main Window

Note: The Main Window is locked after 60 minutes if you open a popup window (to execute a
method, for example), but take no further action. If this occurs, close and reopen the popup
window, and then perform the operation again from the beginning.
Note: Use the links and buttons provided in the Device Manager frames to perform GUI
operations. Do not use Web browser functions, such as Reload or Back, as these functions
may display an inappropriate window. For example, if you are using Internet Explorer as
your Web browser, right-clicking a link in the Device Manager's information frame and
choosing Open in the popup window will produce a blank window. If you have been using
browser functions, click Refresh in the navigation frame or press the F5 key to refresh the
screen. If a popup window is open, close and reopen it.
Note: For information on the warning messages output by Device Manager Web Client, see
section 12.4.
The HiCommand Device Manager main window (see Figure 5.1) provides access to all
HiCommand Device Manager functions. To open the HiCommand Device Manager main
window, open the web browser, and log in to HiCommand Device Manager.
Figure 5.1
68
Frames on the HiCommand Device Manager Main Window
Chapter 5 Performing Device Manager System Operations
The HiCommand Device Manager main window consists of the following components:
Menu-bar frame (see section 5.1.1). The menu-bar frame, or menu bar, provides
commands concerning overall operations of Device Manager, such as logging out and
showing the version information. When a command is selected, the associated popup
window appears.
Navigation frame (see section 5.1.2). The navigation frame displays and allows you to
select the desired object for which you want to perform Device Manager operations.
When an object is selected in the navigation frame, the method and information frames
display the subwindows for the selected object.
Method frame. The method frame displays the available operations for the object
selected in the navigation frame. When an operation is selected in the method frame,
Device Manager displays either a popup window or a subwindow in the information frame
to allow you to perform the selected operation.
Information frame. The information frame displays the detailed information for the
selected object (navigation frame) and/or operation (method frame) and allows you to
select the settings for and perform the selected operation.
The information frame displays the location of the selected management object within
the Device Manager object hierarchy, starting from the root object in the navigation
frame (Device Manager) and with the objects separated by right angle brackets (>).
For example, when you select host_0 in the navigation frame, the information frame
displays: Device Manager > Hosts > host_0
Note on Display of Capacity: The rules for calculating the capacity and the display
format are as follows, unless otherwise specified in the description of items.
The capacity is calculated in kilobytes.
The unit of display changes according to the capacity. If the capacity exceeds 1 GB,
the MB display changes to the GB display. If the capacity exceeds 1 TB, the GB
display changes to the TB display.
For the MB display, the fractional portion of the value is truncated. For the GB and
TB displays, the value is truncated to two decimal places.
Popup windows. The popup windows display the detailed information for the operation
selected in the method frame and allow you to select the settings for and perform the
selected operation.
Each popup window displays the location of the selected management object within the
Device Manager object hierarchy, starting from the root object in the navigation frame
(Device Manager) and with the objects separated by right angle brackets (>).
For example, when you select Hosts in the navigation frame and then select Add Host in
the method frame, the popup window displays: Device Manager > Hosts
69
5.1.1
Menu Bar
The menu bar on the HiCommand Device Manager main window (refer to Figure 5.1)
provides access to the following functions:
70
Tools. Opens a window that allows you to launch other programs. If you want to launch
other web applications from the Device Manager Web Client, register the applications at
the Device Manager Server, and the Web Client will then display the registered programs
in the Tools window (see section 5.7). For details on registering web applications, see
the HiCommand Device Manager Server Installation and Configuration Guide.
Logout. Allows you to log out of HiCommand Device Manager
Close. Allows you to close the browser
Profile. Displays user information
About. Displays the Device Manager version and license information, and allows you to
enter your license key when required
Help. Displays the Device Manager online help.
5.1.2
Navigation Frame
The navigation frame on the Device Manager main window (refer to Figure 5.1) allows you to
select a target on which you want to perform an operation. When an item is selected in this
frame, the subwindows to start the selected operation are displayed in the method frame
and the information frame.
The Refresh button allows you to refresh the information displayed in the navigation frame.
Important: The information on the Device Manager main window is not automatically
updated. After you perform a Device Manager operation, select the Refresh button to
display the latest information.
The navigation frame displays the following items:
Device Manager. Displays the objects that can be managed by Device Manager in the
navigation frame and in the information frame. The objects that can be managed by
Device Manager are:
Logical Groups. Displays the method frame and information frame subwindows for
performing logical group operations (see Chapter 7)
All Storage or My Storage. Displays the method frame and information frame
subwindows for managing the storage in the All Storage or My Storage group (see
Chapter 8)
Subsystems. Displays the method frame and information frame subwindows for
performing storage subsystem operations (see Chapter 10)
Hosts. Displays the method frame and information frame subwindows for performing
host operations (see Chapter 9)
User Management. Displays the method frame and information frame subwindows
for performing user management operations (see Chapter 6)
Alerts. Displays the method frame and information frame subwindows for performing
alert operations (see section 5.5)
Reports. Displays the method frame and information frame subwindows for
performing report operations (see Chapter 11)
Tasks. Displays the method frame and information frame subwindows for viewing
and managing tasks (see section 5.6)
71
5.1.3
Popup Windows
The popup windows display detailed information, or the items enabling Device Managers
various operations. Figure 5.2 shows an example of a popup window (dialog box).
Figure 5.2
Example of a Popup Window
The common items displayed on all popup windows are described below:
Object address. Displays the location of the object selected in the navigation frame
within the Device Manager object hierarchy, starting from the root object (Device
Manager) and with the objects separated by right angle brackets (>).
For example, when you select host_0 in the navigation frame, the popup window
displays: Device Manager > Host > host_0
72
Window name. Displays the name of the popup window
Help. Displays the online help for the popup window
5.2
5.2.1
Logging in and out of HiCommand Device Manager

Logging In to Device Manager
Each HiCommand Device Manager user must log in as a user to whom access privileges are
assigned by the user management of Device Manager. The System Administrator (or Local
System Administrator) is responsible for assigning user access privileges.
To log in to HiCommand Device Manager:
1. Launch the web browser, and enter the URL for the Device Manager Server:
http://Device-Manager-server-address:port-number/DeviceManager/
Device-Manager-server-address = IP address or host name of Device Manager Server
(e.g., localhost)
port-number = enter the port number of the Common Web Service of the HiCommand
series (default = 23015)
The values in Device-Manager-server-address and port-number are the values that
were specified during the installation. For details, see the HiCommand Device Manager
2. The Device Manager Login panel appears (see Figure 5.3).
If the license key for this installation has already been entered, enter your user ID
(login name) and password, and then select Login.
If you are accessing Device Manager for the first time after installation, the Please
input your License Key warning appears (Figure 4.1). Click the License button. The
Version Information for Device Manager panel appears. Type your license key or the
full path of the license file. Click the Save button, and then click the Close button.
In the Device Manager Login panel, type your user ID (login name) and password, and
then click Login.
3. The HiCommand Device Manager main window appears (see section 5.1). This window
provides access to all HiCommand Device Manager functions. See section 4.6 for
instructions on starting HiCommand Device Manager operations.
Important: For Device Manager to work properly, the Device Manager Server must be
the same version as the Java GUI. Check the versions by performing the following
procedures:
To check the Device Manager server version, select About in the menu bar on the
HiCommand Device Manager main window.
To check the Java GUI version in Web Client, select About in the menu bar on the
Physical View, or click the About button on the user administration window.
If the Java GUI is an earlier version than the Device Manager Server, clear the
Java Web Start (JWS) cache (see section 3.4.4), and then re-install the Java GUI.
73
Figure 5.3
74
HiCommand Device Manager Login Panel
5.2.2
Logging out of Device Manager

Each HiCommand Device Manager user must log out of HiCommand Device Manager when
finished performing operations to prevent unauthorized use of HiCommand Device
Manager. HiCommand Device Manager maintains an audit log of all user actions to enable
verification and traceability of HiCommand Device Manager operations.
WARNING: When you log out of Device Manager, you will also be logged out of other
HiCommand Suite products and the Java GUI (the panel for browsing and setting detailed
information about the subsystem, or the panel for setting user access permissions and
operating privileges). If you log out of Device Manager before completion of tasks you
executed in the Java GUI, the processing may be canceled and inconsistencies may occur in
the system. Finish all the tasks, and then log out from Device Manager.
To log out of HiCommand Device Manager:
1. On the HiCommand Device Manager main window, select Logout in the menu bar.
2. When the confirmation panel appears (see Figure 5.4), select OK to log out, or select
Cancel to cancel your request to log out of HiCommand Device Manager.
Figure 5.4
Logging out of HiCommand Device Manager
75
5.3
Viewing Version and License Type Information

The Version Information for the Device Manager panel (see Figure 5.5) displays the Device
Manager version, the license type, the subsystem serial number associated with the license
key, and the licensed capacity. In this panel, you can enter your license key when required
(e.g., during first login after installation).
Figure 5.5
Version Information for Device Manager Panel
You can open the Version Information for Device Manager panel in two ways:
Before logging in to Device Manager, select the License button on the HiCommand
Device Manager Login panel (refer to section 4.5).
After logging in to Device Manager, select the About command in the menu bar.
Note: To check whether the versions of the HiCommand Device Manager Server and the
HiCommand Device Manager Web Client match, select the Help command in the menu bar,
and then select Index.
76
5.4
Viewing User Profile Information

The Show User Profile panel (see Figure 5.6) shows the user information for the logged-in
user. To open the Show User Profile panel, select the Profile command in the Web Client
menu bar.
Figure 5.6
Show User Profile
77
5.5
Performing Alert Operations

The HiCommand Device Manager alert operations include:
Viewing alerts (see section 5.5.1). System Administrators, Storage Administrators, and
Guests can view storage subsystem alerts.
Monitoring alerts (see section 5.5.2). System Administrators, Storage Administrators, and
Guests can monitor storage subsystem alerts.
Deleting alerts (see section 5.5.3). System Administrators and Storage Administrators
can delete alerts.
The Alerts object in the navigation frame (see Figure 5.7) provides access to the alert
operations. When Alerts is selected, the method frame displays the List Objects and
Monitor Alerts commands, and the information frame displays the List Objects Alerts
subwindow.
Figure 5.7
78
Alerts
5.5.1
Viewing Alerts
HiCommand Device Manager allows you to view a list of all alerts for all subsystems, the
detailed information for a specific alert, and the alerts for a specific subsystem. Note that
Local System Administrators, Local Storage Administrators, and Local Guests do not have
access rights to these functions.
Viewing all alerts
To view a list of all alerts for all subsystems, select the Alerts object in the navigation
frame. The list displays a maximum of 100 alerts in chronological order (starting with the
most recent alert). The List Objects Alerts subwindow in the information frame (refer to
Figure 5.7) displays the following information for each alert:
Description: description of the alert
Severity: severity of the alert
Source: subsystem name (subsystem-name@IP-address)
Time of alert: date (yyyy/mm/dd) and time (hh:mm:ss) of the alert
Viewing details on a specific alert

To view the detailed information for a specific alert:
1. Select the Alerts object in the navigation frame to display the List Objects Alerts
subwindow in the information frame.
2. Select the desired alert in the information frame. The Detailed Information Alert
panel (see Figure 5.8) displays the following information for the selected alert:
Number: serial number assigned to the alert by the Device Manager Server
Type: type of alert: Server (alert detected by server polling), or Trap (alert
reported from the device)
Source: subsystem name
Severity: severity of the alert
Component: location
Description: description of the alert
Action To Take: handling method
Data: supplemental information
Time Of Alert: occurrence date and time of the alert
79
Figure 5.8
Detailed Information Alert Panel
Viewing the alerts for a specific subsystem. To view the alerts for a specific subsystem,
display the properties for the subsystem (see section 10.1.3), and note the number of red
vertical alert bars in the Alerts indicator for the selected subsystem. When you click an alert
bar, a dialog box listing the alerts appears.
80
5.5.2
Monitoring Alerts
HiCommand Device Manager allows you to monitor the subsystem alerts and view
information about alerts in real-time as they occur. Local System Administrators, Local
Storage Administrators, and Local Guests do not have access to this function.
To monitor alerts and view information about them as they occur:
1. Select Alerts in the navigation frame (refer to Figure 5.7).
2. Select the Monitor Alerts command in the method frame to open the Monitor Alerts
panel (see Figure 5.9). The Close button stops monitoring and closes this panel.
When an alert occurs, the Monitor Alerts panel notifies you and displays the time of the
alert (see Figure 5.10). Select the Confirm button to acknowledge the alert and
continue monitoring.
When you want to stop monitoring alerts, select the Close button.
Figure 5.9
Monitor Alerts Panel Showing Monitoring
81
Figure 5.10 Monitor Alerts Panel Showing Occurrence of Alerts
82
5.5.3
Deleting Alerts
HiCommand Device Manager allows the System Administrators, Storage Administrators,
Local System Administrators, and Local Storage Administrators to delete alerts from the
HiCommand Device Manager Server. Guests, Local System Administrators, Local Storage
Administrators, and Local Guests do not have access to this function.
To delete one or more alerts from the HiCommand Device Manager Server:
1. Select Alerts in the navigation frame (refer to Figure 5.7) to display the list of alerts in
the information frame.
2. Select the checkbox for each alert that you want to delete. To select all checkboxes,
select the Select All button. To clear (deselect) all checkboxes, select the Unselect All
button.
3. After you have selected the alert(s) that you want to delete, select the Delete button.
The selected alert(s) are deleted from the Device Manager Server.
83
5.6
Viewing the Task List

HiCommand Device Manager allows the logged-in user to view task information within the
access range permitted for that user. However, task information about operations performed
from the Java GUI in Device Manager (User Administration panel or Port Controller panel,
for example) is not displayed.
To view the Device Manager task list, select the Tasks object in the navigation frame to
display the open the List Objects - Tasks subwindow in the information frame (see Figure
5.11). The following information is shown for each item in the list:
Operation: name of the operation performed by the user
Subsystem: name of the subsystem involved in the operation
Logical Group: name of the logical group(s) involved in the operation
Start Time: date and time that the operation was started
Figure 5.11 Viewing the Task List
84
5.7
Launching Other Applications from Device Manager

HiCommand Device Manager provides link-and-launch functionality for the following
applications:
HiCommand Tuning Manager (see section 5.7.1)
Hitachi Dynamic Link Manager (HDLM) (see section 5.7.2)
HiCommand Protection Manager (see section 5.7.3)
HiCommand Provisioning Manager (see section 5.7.4)
Storage Navigator (see section 5.7.5)
NAS Blade Manager (see section 5.7.6)
Launching DAMP (see section 5.7.7)
Launching a Third-Party Application (see section 5.7.8)
Note: If you click Logout on the menu bar of another HiCommand Suite products that you
launched using the link-and-launch feature, you will also be logged out of Device Manager. If
you then attempt a link-and-launch operation, try to use the Java GUI or open a report
window, an error panel appears. If you launched more than one HiCommand Suite
products, make sure that no operations are in progress in any of the programs before you log
out.
5.7.1
Launching HiCommand Tuning Manager

Tuning Manager collects information on the performance and capacity of the servers,
databases, and storage subsystems connected in a SAN environment, and centrally controls
the performance of the entire storage network.
5.7.2
When Device Manager and Tuning Manager are installed on the same server, Tuning
Manager is automatically displayed in the Device Manager's Tools window. Select Tuning
Manager to open another window and display the Tuning Manager GUI. For details on
working with Tuning Manager, see the HiCommandTM Tuning Manager Administrator's
Guide. A future release of the Tuning Manager will support access corresponding to the
HiCommand access (i.e., My Storage definitions).
Launching Hitachi Dynamic Link Manager (HDLM)

HDLM manages access paths to storage for the Hitachi Freedom Storage family of disk array
subsystems. HDLM provides functions for distributing workload across paths and switching to
an alternate path if a failure occurs on the path in use. Networks dedicated to data transfer,
such as storage area networks (SANs), can use HDLM to provide enhanced access to storage.
When a Device Manager agent and Dynamic Link Manager are installed on a managementtarget host of Device Manager in Device Manager a Dynamic Link Manager button appears in
the Show Properties Host Name subwindow for the host. For instructions on displaying the
Show Properties Host Name subwindow for a host, see section 9.4. To launch the Dynamic
Link Manager GUI, select Dynamic Link Manager.
85
5.7.3
Launching Protection Manager

Protection Manager controls backup and recovery of databases that use the volume
replication features (ShadowImage and Hitachi Open Multiple Raid Coupling Feature
(HOMRCF), for example) provided by Hitachi storage subsystems. By providing integrated
control of storage subsystems, backup products, database products and other applications,
Protection Manager simplifies procedures related to data integrity.
When a Device Manager agent and Protection Manager are installed on a management-target
host of Device Manager, a Protection Manager button appears in the Show Properties
subwindow of Device Manager for the host running Protection Manager. For details on
displaying a host's Show Properties subwindow, see section 9.4. Clicking the Protection
Manager button launches the GUI for Protection Manager.
5.7.4
Launching Provisioning Manager

Provisioning Manager provides functionality for managing a group of disks in a storage
subsystem as a single large data storage pool.
When the Device Manager Server and Provisioning Manager are installed on the same server,
a link to Provisioning Manager appears in the Device Manager's Tools window. Clicking the
Provisioning Manager link opens the Provisioning Manager GUI in a new window.
86
5.7.5
Launching 9900V Storage Navigator

When Storage Navigator is installed on a Lightning 9900V that has been registered with
Device Manager, the Web Client displays the Storage Navigator drop-down list in the
Physical View for the 9900V storage subsystem (see section 10.2.2). System Administrators,
Storage Administrators, and Guest users can directly access the desired Storage Navigator
functionality using this drop-down list.
Caution: When using Web Client on a Solaris system, the following configurations are
required for launching the 9900V Storage Navigator functionality:
1. Specifying Netscape used for Storage Navigator. To enable Netscape to start, create
the shell script netscapeforSN as follows:
(a) Create a shell script named netscapeforSN, and code the following as appropriate
for your environment:
LD_LIBRARY_PATH= path-to-Netscape-supported-by-Storage-Navigator $*
(Enter a single space after LD_LIBRARY_PATH=.)
The following example shows the coding when Netscape starts under
/usr/dt/appconfig/netscape/netscape:
#!/usr/bin/sh
LD_LIBRARY_PATH= /usr/dt/appconfig/netscape/netscape $*
(b) Specify the execution permissions for the shell script netscapeforSN.
(c) Modify the environment variable PATH so that the shell script netscapeforSN is
executed when netscapeforSN is executed on the command line.
2. Setting up Netscape plug-in. In the plugins directory for Netscape, create a symbolic
link to the Java plug-in file, libjavaplugin_oji.so.
cd Netscape-installation-directory/plugins
ln -s /usr/local/j2re1_4_2/plugin/sparc/ns610/libjavaplugin_oji.so .
After setup of the plug-in finishes, restart the browser.

For details, see the following Sun Web site:
http://java.sun.com/j2se/1.4.2/jre/install-solaris.html
87
When licensed, the following Storage Navigator functions can be accessed directly from
Device Manager:
Login
Information/Status
LUN Expansion
FlashAccess
Performance Management (Performance Monitor, CruiseControl, and Prioritized Port

Control)
TrueCopy
ShadowImage
Extended Copy Manager
Open LDEV Guard
Note: If the logged-in Device Manager user is a Guest, Login is the only available function.
Note: Functions other than Login and Information/Status are available only to licensed
users.
Figure 5.12 Link-and-Launch Command for 9900 V Storage Navigator
88
5.7.6
Launching NAS Blade Manager (TagmaStore USP and Lightning 9900 V)

When a NAS-CHA running NAS Manager resides on a RAID500 or Lightning 9900V subsystem
managed by Device Manager, System Administrators and Storage Administrators can launch
NAS Manager from Web Client. NAS Manager launches from either of two windows,
depending on the subsystem:
Physical View dialog box for Lightning 9900V

In the Physical View dialog box for Lightning 9900V, select NAS-CHA from the
NAS/Management drop-down list. This launches NAS Manager. For details on how to
open the Physical View dialog box, see section 10.2.2.
Show Properties - Subsystem Name subwindow for TagmaStore USP or Lightning 9900 V
In the Show Properties - Subsystem Name subwindow for TagmaStore USP or Lightning
9900 V, click the NAS/Management button. The Select Nas/Management Port Controller
dialog box appears (see Figure 5.13). Select NAS-CHA, and then click the OK button to
launch NAS Manager. For details on how to open the Show Properties - Subsystem Name
subwindow, see section 10.1.3.
Figure 5.13 Select Nas/Management Port Controller Dialog Box
89
5.7.7
Launching DAMP (Thunder 9500V and Thunder 9200)

When a Thunder 9500 V or Thunder 9200 subsystem is being managed by Device Manager,
System Administrators, Storage Administrators, and Guests can launch DAMP from Web
Client. A DISK ARRAY MANAGEMENT PROGRAM button appears in the Thunder 9500V or
Thunder 9200 Physical View dialog box. Click this button to launch DAMP. If you are logged
in as a System Administrator or Storage Administrator, DAMP starts in administration mode.
If you are logged in as a Guest, DAMP starts in standard mode. For details on how to open
the Physical View dialog box, see section 10.2.
Note: To start DAMP from a Web Client, in the Device Manager Server you must set up
linkage with DAMP. For details on how to set up, see the HiCommand Device Manager
Note: Device Manager's URLLink feature is used to launch DAMP. When you add a Thunder
9500V or Thunder 9200 subsystem to Device Manager, the URLLink is set automatically to
point to DAMP. If you execute a command to change this URLLink, DAMP will fail to start. For
details on the URLLink feature, see section 5.7.8. If DAMP cannot start because the URLLink
was changed by the command, refresh information about Thunder 9500V or Thunder 9200.
The URLLink setting will back to DAMP.
5.7.8
Launching a Third-Party Application

Device Manager provides a URLLink feature that enables link-and-launch access from the
Physical View dialog box and Show Properties - Subsystem Name subwindow to a URL specific
to the storage subsystem. Only System Administrators and Storage Administrators can use
URLLink. For details, see the HiCommand Device Manager Command Line Interface (CLI)
User's Guide. Specifically, refer to the AddURLLink, GetURLLink, and DeleteURLLink
API commands to obtain a better understanding of this functionality.
Note: If you execute a command to set URLLink for Thunder 9500V or Thunder 9200 on
which a Web Client is enabled to start DAMP, refreshing information about that Thunder
9500V or Thunder 9200 changes the URLLink setting back to DAMP. If you want to specify an
application other than DAMP as a link destination, you must perform the following:
To specify an application other than DAMP as a link destination:
1. In the Device Manager Server, modify the setting for linkage with DAMP. For details
about how to modify the setting, see the HiCommand Device Manager Server
Installation and Configuration Guide.
2. Restart the Device Manager Server.
3. Refresh information about the storage subsystem for which you want to specify the link
destination to an application other than DAMP.
4. Execute the command that sets up URLLink.
Note: URLs that you set using URLLink are displayed in the HTML source code.
90
5.7.9
Importing a Server Certificate into a Browser

By importing a server certificate into the browser, you can avoid the warning dialog box that
is otherwise displayed at the start of a browser session when a server certificate or
Certificate Authority cannot be trusted.
The warning dialog box includes instructions for importing a server certificate into the
browser.
The warning dialog is displayed when the following Java GUI dialog boxes of the
HiCommandTM Device Manager display an HTML version of Help:
Physical View
User Administration
User Properties
User Group Administration
User Group Properties
91
92
Chapter 6
Performing User Management Operations
This chapter describes HiCommand Device Manager user management operations.
Overview of User Management Operations (see section 6.1)
User Account Operations (see section 6.2)
User Group Operations (see section 6.3)
93
6.1
Overview of User Management Operations

The HiCommand Device Manager user management operations include:
User account operations (see section 6.2)
User group operations (see section 6.3)
User account operations. The System Administrator (or Local System Administrator) can
edit user accounts. The Storage Administrator (or Local Storage Administrator) and Guests
(or Local Guests) cannot edit user accounts. Device Manager maintains the user databases
and logs of the operations performed by all users. All users except for Guests (or Local
Guests) can change their attributes (first names, last names, and descriptions) and
passwords. Guests (or Local Guests) can view their attributes.
User group operations. The System Administrator (or Local System Administrator) of Device
Manager can create and delete user groups and view and edit the attributes of user groups.
By creating a user group, the System Administrator (or Local System Administrator) can
control the users access to resources (hosts and logical devices) managed by Device
Manager. User groups are closely related with logical groups, and they inherit the
hierarchical structure of the logical groups.
The User Management object in the Device Manager Web Client navigation frame (see
Figure 6.1) provides access to the user management operations.
Figure 6.1
94
User Management
Chapter 6 Performing User Management Operations
6.2
User Account Operations

The System Administrator (or Local System Administrator) can perform user account
operations. The Local System Administrator can perform user account operations for users in
the assigned user group and its descendant user groups. Storage Administrators and Local
Storage Administrators can edit their own user attributes. Guests and Local Guests can view
their own user attributes.
HiCommand Device Manager maintains a database of authorized users and an audit log of
all user actions. HiCommand Device Manager allows all users except Guests and Local
Guests to change their own password and user properties (first name, last name, and
description). System users are users who are assigned to a system user group (Admin,
StorageAdmin, Guest). Local users are users who are assigned to a user-defined user group
with the role of Local System Administrator, Local Storage Administrator, or Local Guest.
The HiCommand Device Manager user account operations include:
Adding a user (System Administrator or Local System Administrator only) (see section
6.2.1)
Viewing and editing user properties (see section 6.2.2)
Changing your password (see section 6.2.3)
Deleting a user (System Administrator or Local System Administrator only) (see section
6.2.4)
The User Administration panel (see Figure 6.2) allows the System Administrator or Local
System Administrator to add and delete HiCommand Device Manager users and edit
HiCommand Device Manager user properties as needed. To open the User Administration
panel, log in as a System or Local Administrator, select the User Management object in the
navigation frame, and then select Users in the information frame. (If you are not logged in
as a System or Local Administrator, the User Properties panel opens when you click Users.)
The User Administration panel lists each user by user ID (login name) and user group.
The New button allows you to add a new HiCommand Device Manager user. The Edit button
allows you to edit the information for the selected HiCommand Device Manager user. The
Delete button allows you to delete the selected HiCommand Device Manager user.
95
Figure 6.2
96
User Administration Panel
6.2.1
Adding a User
The System Administrator can add new HiCommand Device Manager users as needed. The
Local Administrator can add new users to the assigned user group and its descendant user
groups. The Storage Administrator, Local Storage Administrator, Guests, and Local Guests do
not have access to this function.
Note: Before adding a new user, make sure that the desired user group has been added (see
section 6.3.1). After a new user has been added, you cannot change the assigned user group.
To add a new HiCommand Device Manager user:
1. Log in to HiCommand Device Manager as a System Administrator or Local Administrator.
2. Select the User Management object in the navigation frame, and then select Users in
the information frame to open the User Administration panel (refer to Figure 6.2).
3. Select New to open the User Properties panel (see Figure 6.3).
4. Enter the following information for the new HiCommand Device Manager user:
Login Name.
Note: The login name (user ID) must be 4-25 bytes in length and is case-sensitive
(i.e., USER1 and user1 cannot both be used). You can use the following
characters:
A - Z, a - z, 0 - 9, #, +, -, _, ., @
Description (optional) (e.g., job title)

The description can contain Basic_Latin and may be a maximum of 255 bytes.
Password, and Confirm Password.

Note: The password is case-sensitive and must be 4-25 bytes in length. You can use
the following characters:
A - Z, a - z, 0 - 9, !, #, $, %, &, ', (, ), *, +, -, ., =, @, \, ^, _, |
First Name (optional)

You can use Basic_Latin. This may be a maximum of 50 bytes in length.
Last Name (optional)

You can use Basic_Latin. This may be a maximum of 50 bytes in length.
User Group. Select one of the system user groups (Admin, Guest, StorageAdmin) or a
user-defined user group.
Role (user-defined groups only). Select Local System Administrator, Local Storage
Administrator, or Local Guest. The Local System Administrator can modify user
accounts, descendant user groups, and storage associated with the specified user
group. The Local Storage Administrator can modify storage associated with the
specified user group. The Local Guest user can only view storage information for the
specified user group.
Note: The Basic_Latin refers to the following:
Basic_Latin: Unicode 0020 to Unicode 007E
97
5. Select Save to save your changes. HiCommand Device Manager adds the new user
record and returns you to the User Administration panel, which now displays the new
HiCommand Device Manager user.
Figure 6.3
Add a New User
Note: If User Account information fails to launch as designed, verify that JRE (Java
Runtime Environment)-Web Start is present and has been configured properly. JRE-Web
Start is also the place to look if there are launch problems with Physical view for subsystems
other than the TagmaStore USP.
98
6.2.2
Viewing and Editing User Properties

All HiCommand Device Manager users except for Guests and Local Guests can view and edit
their own user properties. Guests and Local Guests can view their own user properties. The
System Administrator can edit the user properties of all users. The Local System
Administrator can edit the user properties of the users in the specified user group and its
descendant user groups.
To view and edit the HiCommand Device Manager user properties:
1. Log in to HiCommand Device Manager.
3. If you are not logged in as a System Administrator, the User Properties panel opens (see
Figure 6.4). If you are logged in as a System Administrator or Local System
Administrator, the User Administration panel opens. Select the desired user, and then
select Edit to open the User Properties panel.
4. Make the desired changes (if any) on the User Properties panel. All users can edit their
own first name, last name, and description. For instructions on changing the password,
see section 6.2.3.
Note: The login name cannot be modified.
5. Select Save to save your changes. HiCommand Device Manager updates the user
record. If you are logged in as a System Administrator or Local System Administrator, you
are returned to the User Administration panel.
Figure 6.4
Edit Properties
99
6.2.3
Changing Your Password

All HiCommand Device Manager users except for Guests and Local Guests can change their
own password. The System Administrator can change the passwords of all users. Local
System Administrators can change the passwords of the users in the specified user group and
its descendant user groups. Guests and Local Guests do not have access to this function. You
cannot change your login name.
To change your HiCommand Device Manager Web Client user password:
1. Log in to HiCommand Device Manager.
3. If you are logged in as a System Administrator or Local System Administrator, the User
Administration panel opens. Select the user whose password you wish to change, and
then select Edit to open the User Properties panel. If you are not logged in as a Storage
Administrator, the User Properties panel opens.
4. On the User Properties panel, select Change Password to open the Change Password
panel (see Figure 6.5).
5. Enter the new password in the Password and Confirm Password fields, and select Save.
Note: The password is case-sensitive and must be 4-25 bytes. You can use the following
characters (Unicode characters from 0020 to 007E):
A - Z, a - z, 0 - 9, !, #, $, %, &, ', (, ), *, +, -, ., =, @, \, ^, _, |.
6. Select Save to close the User Properties panel. HiCommand Device Manager changes
the password in the HiCommand Device Manager system database. If you are logged in
as a System Administrator or Local System Administrator, you are returned to the User
Administration panel.
Figure 6.5
100
Change Password
6.2.4
Deleting a User
The System Administrator can delete existing HiCommand Device Manager users as needed.
The Local System Administrator can delete existing users in the assigned user group and its
descendant user groups. The Storage Administrator Local Storage Administrator, Guest, and
Local Guest do not have access to this function.
Caution: The HaUser (Peer group) must not be deleted. If you delete HaUser, the Device
Manager Agent cannot transmit information to the Device Manager Server.
Caution: The hbase (Peer group) must not be deleted. The hbase is the account to be used
by Device Manager.
Caution: Before you can delete a HiCommand Device Manager user, that user must not be
logged in to HiCommand Device Manager and must have been logged out for several (up to
ten) minutes. If these requirements are not met, HiCommand Device Manager will not
allow you to delete the user.
To delete a user from the HiCommand Device Manager Server:
1. Make sure that the user to be deleted is not logged in to HiCommand Device Manager
and has been logged out for at least ten minutes.
2. Log in to HiCommand Device Manager as a System Administrator or Local System
Administrator.
4. Select the user to be deleted, and then select Delete.
5. When the confirmation panel appears (see Figure 6.6), select YES to delete the user, or
select NO to cancel your request to delete the user. You are returned to the User
Administration panel.
Figure 6.6
Delete User Confirmation
101
6.3
User Group Operations

The System Administrator and Local Administrator can perform user group operations. The
user group operations enable the System Administrator and Local Administrator to control
access to resources (storage and hosts) on HiCommand Device Manager. The System
Administrator has access to all user groups. The Local System Administrator has access to
the assigned user group and its descendant user group(s). The Storage Administrator, Local
Storage Administrators, Guests, and Local Guests do not have access to this function.
The user group is closely related to the logical group and inherits the logical group
hierarchy. For example, if logical group A has a subgroup B, and user group A is assigned to
logical group A and user group B is assigned to logical group B, users in user group A have
access to all resources (hosts and LDEVs) for both user group A and user group B. The Local
Administrator for user group A can control users in both user group A and user group B. User
group B is a descendant of user group A.
The HiCommand user group operations include:
Adding a user group (see section 6.3.1)
Viewing and editing user group properties (see section 6.3.2)
Deleting a user group (see section 6.3.3)
The User Group Administration panel (see Figure 6.7) allows you to manage user groups. To
open the User Group Administration panel, log in as System Administrator or Local
Administrator, select User Management in the navigation frame, and then select User
Groups in the information frame. The New button allows you to add a new user group. The
Edit button allows you to edit the selected user group. The Delete button allows you to
delete the selected user group.
102
Figure 6.7
User Group Administration Panel
103
6.3.1
Adding a User Group

The System Administrator can add new user groups as needed. The Local System
Administrator can add new descendant user groups to the assigned user group. The Storage
Administrator, Local Storage Administrator, Guest, and Local Guest do not have access to
this function.
Note: Before adding a new user group, make sure that the logical group to be associated
with the user group has been added to the HiCommand Device Manager (see section 7.3).
After a new user group has been added, you cannot change its assigned logical group.
To add a new HiCommand Device Manager user group:
Administrator.
2. Select the User Management object in the navigation frame, and then select User
Groups in the information frame to open the User Group Administration panel (refer to
Figure 6.7).
3. Select New to open the User Group Properties panel (see Figure 6.8).
4. Enter the name for the new user group (mandatory) and a description (optional). The
group name must be no more than 25 bytes and the description no more than 255 bytes
in length. You can use Basic_Latin. The group name must not contain spaces or any of
the following characters:
", ', /, ?, >, <, ;, :, !, @, #, $, %, ^, &, *, (, ), +, |, {, }, [, ], ~, Euro currency sign.
Note: Basic_Latin refers to the following: Unicode 0020 to Unicode 007E

5. Select the Logical Group tab, and select the logical group to be associated with the new
user group. The selected logical group will be the home group of the new user group,
and all LUNs and subgroups in this logical group will be accessible to users in the new
user group.
6. Select the Host tab, and select the hosts to be associated with the new user group.
Note: If you are using TagmaStore USP Universal Volume Manager, and a storage
subsystem has been added to Device Manager incorrectly, an External port may appear
as a host under Inaccessible hosts and Accessible hosts. For details on adding storage
subsystems, see section 10.1.2.
You must not associate an External port with a user group.
To find out whether a host listed under Inaccessible hosts or Accessible hosts is an
External port, look up the WWN of the host in the Show Properties - Host name
subwindow, and then use Storage Navigator to view port information for the storage
subsystem (TagmaStore USP) with that External port. If the WWN of the External port
matches the WWN of the host you looked up, that host is an External port.
If the External port is associated with a user group and you refresh the TagmaStore USP
subsystem, the External port disappears from the Inaccessible hosts or Accessible hosts
list and its user group is disassociated.
7. Select the LDEV tab, select the subsystem, and select the LDEVs to be associated with
the new user group.
104
8. When the group, host, and LDEV information for the new group is correct, select Save to
save your changes. HiCommand Device Manager adds the new user group and returns
you to the User Group Administration panel, which now displays the new user group.
Figure 6.8
Add a New User Group
105
6.3.2
Viewing and Editing User Group Properties

The System Administrator can edit the user group properties and change the resources of all
user-defined user groups. The system-defined user groups (Admin, StorageAdmin, Guest)
cannot be modified. The Local System Administrator can modify the user group properties
and change the resources of the assigned user group and its descendant user groups.
To view and edit the HiCommand user group properties:
1. Log in to HiCommand Device Manager as System Administrator or Local System
Administrator.
2. Select the User Management object in the navigation frame, and then select User
Groups in the information frame to open the User Group Administration panel (refer to
Figure 6.7).
3. Select the desired user group, and select Edit to open the User Group Properties panel
(see Figure 6.9).
4. Make the desired changes (if any) on the User Group Properties panel. You can edit the
Description and the information on the Host and LDEV tabs. You cannot edit the group
name or the logical groups associated with the user group.
Note: If you are using TagmaStore USP Universal Volume Manager, pay close attention
to host allocation. See the note under step 6 in section 6.3.1.
5. Select Save to save your changes and update the user group record.
106
Figure 6.9
Edit User Group Properties
107
6.3.3
Deleting a User Group

The System Administrator can delete existing user-defined user groups as needed. The
system-defined user groups (Admin, StorageAdmin, Guest) cannot be deleted. The Local
System Administrator can delete descendant user groups of the assigned user group. The
Storage Administrator, Local Storage Administrator, Guest, and Local Guest do not have
access to this function.
Note: Before you can delete a user group, users belonging to that user group must not be
logged in to HiCommand Device Manager and must have been logged out for several (up to
ten) minutes.
To delete a user group from the HiCommand Device Manager Server:
1. Make sure that users belonging to the user group to be deleted are not logged in to
HiCommand Device Manager and have been logged out for at least ten minutes.
Administrator.
3. Select the User Management object in the navigation frame, and select User Groups in
4. Select the user group to be deleted, and then select Delete.
Note: If the selected user group has descendant user groups, those user groups will also
be deleted.
Note: Users in the selected user group and its descendant groups (if any) will be
deleted.
5. When the confirmation panel appears (see Figure 6.10), select YES to delete the
specified user group, or select NO to cancel your request to delete the user group.
108
Figure 6.10 Delete User Group Confirmation
109
110
Chapter 7
Performing Logical Group Operations
This chapter describes logical group operations:
Overview of Logical Groups (see section 7.1)
Viewing the list of logical groups (see section 7.2)
Adding a logical group (see section 7.3)
Viewing and editing the logical group properties (see section 7.4)
Removing a logical group (see section 7.5)
Storage group operations (see section 7.6)
111
7.1
Overview of Logical Groups

The Logical Groups object in the navigation frame (see Figure 7.1) provides access to the
logical group operations. The logical group operations include:
Viewing the list of logical groups (see section 7.2)
Adding a logical group (see section 7.3)
Viewing and editing the logical group properties (see section 7.4)
Deleting a logical group (see section 7.5)
Storage group operations (see section 7.6)
Figure 7.1
Logical Groups
HiCommand Device Manager allows you to create a hierarchy of logical groups and assign
storage to these groups. Logical groups can contain one or more logical groups and/or one or
more storage groups. Storage groups contain LUNs (paths to volumes). Storage groups can be
nested within logical groups or at the top level. A logical group cannot be nested within a
storage group.
112
Chapter 7 Performing Logical Group Operations
Logical groups can be classified as follows:
Parent or child group: When logical groups are arranged in a hierarchical structure, a
higher-level group in the hierarchy can be called a parent group, and a lower-level group
in the hierarchy can be called a child group. A parent group is always a logical group,
whereas a child group can be either a logical group (e.g., mid-level) or a storage group.
Storage group: A group for which paths to storage have been set is called a storage
group. A storage group is a collection of any user-specified storage units (LUNs).
Although a storage group can be placed under a logical group or at the top of a
hierarchy, a logical group cannot be placed under a storage group.
Empty group: A logical group that has no contents is called an empty group. An empty
group can be converted to a storage group by placing storage under it. It can also be
converted to a parent group by placing one or more logical groups under it.
The All Storage or My Storage logical group contains all LDEVs that are under the
management of the logged-in user. If you are logged in as a system user (System
Administrator, Storage Administrator, or Guest), the All Storage group is displayed. If you
are logged in as a local user (Local System Administrator, Local Storage Administrator, or
Local Guest), the My Storage group is displayed. This group is always present and cannot be
deleted. The All Storage/My Storage group is organized by storage subsystem, and each
subsystem group contains an Allocated storage group and an Unallocated storage group.
Allocated group: Displays the LUs/LDEVs in the specified subsystem that are available to
the logged-in user and have one or more paths assigned to them. When you add a new
subsystem or perform a Refresh on an existing subsystem (see section 10.1.4),
LUs/LDEVs that have paths assigned to them are placed in this group.
Unallocated group: Displays the LUs/LDEVs that are available to the logged-in user and
do not have any paths assigned to them. When you add a new subsystem or perform a
Refresh on an existing subsystem (see section 10.1.4), HiCommand Device Manager
places the LUs/LDEVs that do not have any paths assigned to them in this group.
The LUN Scan logical group is created when you perform the first LUN Scan operation (see
section 8.3). The LUN Scan group contains a logical group for each subsystem on which a LUN
Scan operation has been performed. Each LUN Scan subsystem group contains storage groups
of LUNs organized by port. The groups within the LUN Scan group are normal logical groups
and storage groups that can be operated on (e.g., renamed, deleted, etc.).
113
7.2
Viewing the List of Logical Groups

All HiCommand Device Manager users can view the list of logical groups for which they have
access permission. To view the list of logical groups, select the Logical Groups object in the
navigation frame. You can expand the tree hierarchy as needed (click on + ) to display the
child group(s) and/or storage group(s) contained within the parent group(s).
When the Logical Groups object is selected in the navigation frame, the method frame
displays the List Objects operation, and the information frame displays the list of objects
(logical groups and/or storage groups) at the top level of the logical group hierarchy.
When a logical group is selected in the navigation frame, the method frame displays the List
Objects, Modify Properties, and Remove Group operations, and the information frame
displays the following subwindows:
Logical Group subwindow: Displays the properties of the selected logical group:
Name: name of the group
Parent group: name of the parent group(s) with nested groups separated by a slash
(/) character (e.g., /Enterprise/MIS Dept/E-Mail)
Number of LUNs: total number of LUNs in the group, including the LUNs in all child
groups
Configured capacity: total capacity of the storage in the group, including the
storage in all child groups
Subsystem: subsystem(s) containing the storage in the group, including the storage
in all child groups
If the Logical Groups object is selected in the navigation frame, this subwindow is not
displayed.
Object List subwindow: Displays a list of objects contained within the selected group. If
a parent group is selected in the navigation frame, this subwindow displays the child
groups (logical groups and/or storage groups) contained within the selected group. If a
storage group is selected in the navigation frame, this subwindow displays the LUN(s)
contained in the storage group.
Note on Display of Capacity: The rules for calculating the capacity and the display format
are as follows, unless otherwise specified in the description of items.
114
The unit of display changes according to the capacity. If the capacity exceeds 1 GB, the
MB display changes to the GB display. If the capacity exceeds 1 TB, the GB display
changes to the TB display.
For the MB display, the fractional portion of the value is truncated. For the GB and TB
displays, the value is truncated to two decimal places.
7.3
Adding a Logical Group

Logical groups can contain one or more logical groups and/or storage groups. The System
Administrator, Local System Administrator, Storage Administrator, and Local Storage
Administrator can add logical groups. Guest and Local Guest users do not have access to this
function.
Note: In Web Client, increasing the amount of data that is displayed in the window increases
the amount of memory that is used. To avoid a memory shortage, we recommend that you
do not create more than 1,000 logical groups.
To add a logical group to HiCommand Device Manager:
1. Log in to HiCommand Device Manager as a System Administrator, Storage
Administrator, Local System Administrator, or Local Storage Administrator.
2. Select the Logical Groups object in the navigation frame, expand the tree as needed
(click on + ), and then select the desired parent group for the group that you want to
add. To add a logical group at the top level, select the Logical Groups object.
3. Select the Add Group button in the information frame to open the Add Group panel (see
Figure 7.2). The parent group that you selected in the navigation frame (if any) is
automatically entered on this panel.
Note: Panel and dialog box mean the same thing.
4. In the Parent Group field on the Add Group panel, select the desired parent group for
the new group, if not already selected. Select None to add a new group at the top level.
5. In the Group Name field on the Add Group panel, enter the desired name for the new
group. You cannot create a group with the same name as another group on the same
level, and you cannot use LUN SCAN as a group name. The group name can contain
spaces and is not case-sensitive. For example, if GROUP 1 already exists, you cannot
add group 1 at the same level.
The group name can be a maximum of 50 bytes. You can use the following characters:
A - Z, a - z, 0 - 9, -, _, ., @
The group name may include spaces, but cannot consist only of spaces. Leading or
trailing spaces are discarded.
6. In the Icon field on the Add Group panel, select the desired icon for the new group.
7. When the information displayed on the Add Group panel is correct, select OK to add the
specified new group (or select Cancel to cancel your request to add a new group).
115
Figure 7.2
116
Adding a New Group
7.4
Viewing and Editing Logical Group Properties

The System Administrator, Local System Administrator, Storage Administrator, and Local
Storage Administrator can edit the logical group properties. Guest and Local Guest users do
To view and edit the logical group properties:
(click on + ), and select the group for which you want to view or edit the properties.
2. In the method frame, select the Modify Properties operation to open the Modify
Properties panel (see Figure 7.3). The Modify Properties panel displays and allows you to
change the parent group, group name, and icon for the selected group.
3. Edit the properties of the logical group (parent group, group name, icon) as needed.
Note on changing the name: You cannot use LUN SCAN as a group name, and you
cannot have two groups with the same name on the same level. The group name can
contain spaces and is not case-sensitive. For example, if GROUP 1 already exists at the
same level as the selected group, you cannot use the name GROUP 1 or group 1.
The group name can be a maximum of 50 bytes. You can use the following characters:
A - Z, a - z, 0 - 9, -, _, ., @
The group name may include spaces, but cannot consist only of spaces. Leading or
Note on changing the parent group: If the group being edited or any of its child groups
is assigned to a user group, and you move the group by changing its parent group, the
following changes will be applied:
When a logical group above the group being moved is associated with a user group,
the resources of the group being moved are removed from the associated user
group. In addition, the resources of any groups below the group being moved are
also removed from the associated user group.
When a new parent group or any logical group above a new parent group is
associated with a user group, the resources of the group being moved are added to
the resources of the new higher-level user group. In addition, the resources of the
groups below the group being moved are also added to the resources of the new
higher-level user group.
See section 6.3 for further information on user group operations.

4. Select OK to save your changes (if any) to the group properties and close the panel, or
select Cancel to close the panel without saving changes.
117
Figure 7.3
118
Viewing and Editing Logical Group Properties
7.5
Removing a Logical Group

Storage Administrator can remove a logical group. Guest and Local Guest users do not have
Note: For instructions on removing a storage group (contains LUNs) or a parent group which
contains one or more storage groups, see section 7.6.6.
To remove a group from HiCommand Device Manager:
(click on + ), and select the group that you want to remove.
2. In the method frame, select the Remove Group operation.
3. HiCommand Device Manager displays and asks you to confirm the requested remove
logical group operation (see Figure 7.4). If the selected group contains any subgroups,
the subgroup(s) are listed (see Figure 7.5).
4. Select OK to remove the specified logical group and its subgroups (if any) (or select
Cancel to cancel your request to remove the group).
Figure 7.4
Removing an Empty Logical Group
119
Figure 7.5
120
Removing a Parent Logical Group
7.6
Storage Group Operations

The System Administrator, Storage Administrator, Local System Administrator, and Local
Storage Administrator can perform storage group operations. Guest and Local Guest users
can only view the storage group information.
A HiCommand Device Manager storage group is a user-defined set of LUNs that can be
manipulated as a group. When you view the contents of a storage group, you can view
property information on the selected storage group and information on the LDEVs managed
under that storage group. You can add, remove, and move storage in a storage group, and
you can change the security properties of a storage group.
The HiCommand Device Manager storage group operations include:
Viewing the contents of storage groups (see section 7.6.1)
Adding storage to a storage group (see section 7.6.2)
Moving storage from one group to another (see section 7.6.3)
Modifying LUN security for a group (see section 7.6.4)
Removing storage from a group (see section 7.6.5)
Removing a storage group (see section 7.6.6)
Note: For instructions on adding storage groups, see section 7.3.

Note: When an error occurs during a storage group operation, HiCommand Device Manager
might ask you to perform the Refresh operation. If you do not have Refresh privileges (if you
are a Local System Administrator or Local Storage Administrator), ask the HiCommand
Device Manager System Administrator or Storage Administrator to perform the Refresh
operation.
Note on Display of Capacity: The rules for calculating the capacity and the display format
are as follows, unless otherwise specified in the description of items.
The unit of display changes according to the capacity. If the capacity exceeds 1 GB, the
MB display changes to the GB display. If the capacity exceeds 1 TB, the GB display
changes to the TB display.
For the MB display, the fractional portion of the value is truncated. For the GB and TB
displays, the value is truncated to two decimal places.
121
7.6.1
Viewing the Contents of a Storage Group

When you view the contents of a storage group, you can view property information on the
selected storage group and information on the LDEVs managed under that storage group.
To view the contents of a storage group:
Administrator, Local System Administrator, or Local Storage Administrator to perform
storage group operations. Guest and Local Guest users can only view the contents of a
storage group.
(click on + ), and then select the desired storage group (see Figure 7.6).
The method frame displays the operations that can be performed on the selected group:
Modify Properties (see section 7.4)
Remove Group (see section 7.6.6)
The information frame displays the following information and operations for the storage
in the selected group:
Logical group information: name and icon, parent group, number of LUNs,
configured capacity, subsystem, and list of LDEVs in the group (see step 3)
Add Storage (see section 7.6.2)
Move Storage (see section 7.6.3)
Modify Security (see section 7.6.4)
Delete Storage (see section 7.6.5)
3. To view detailed information for an LDEV in the storage group, select the LDEV to open
the Detailed Information LDEV-number panel (see Figure 7.7).
Table 7.1 lists and describes the information displayed on the Detailed Information
LDEV-number panel.
122
Figure 7.6
Viewing the Contents of a Storage Group
123
Figure 7.7
124
Detailed Information LDEV-Number Panel
Table 7.1
Detailed Information LDEV-Number Panel Information (continues on the next page)
Item
Description
Detailed Information
LDEV
Logical device number. For the LUSE volume, the numbers of logical devices that make up the
LUSE volume are displayed in the drop-down list.
Type
Displays the LDEV type. This item is displayed only for TagmaStore USP and Thunder 9500V.
ACP
Displays the array control processor.
Array Group
Displays the array group number.
RAID Level
Displays the RAID level.
Capacity
Displays the logical device capacity.
EMU Type
Displays the emulation type (TagmaStore USP, 9900V, and 9900 only, emulation-type x numberof-LDEVs is shown for a LUSE volume). No value is displayed for Thunder 9500V or 9200. OPEN
is shown for T3.
Copy Type
Displays a copy type; ShadowImage, TrueCopy, or QuickShadow. This item is not displayed for T3.
Volume Attr
Displays the volume attribute. This item is not displayed for T3.
CMD DEV
Displays the command device status. This item is not displayed for T3.
Path Information
LDEV
Displays the logical device number.
Port/HSD/LUN
Displays the port (cluster+port number), host storage domain (HSD) nickname, and logical unit
number. HostStorageDomain (HSD) is displayed only for the TagmaStore USP, Lightning 9900V,
and Thunder 9500V (LUN Management mode).
Port/LUN
Displays the port (cluster+port number) and logical unit number. This item is not displayed for
TagmaStore USP, Lightning 9900V, or Thunder 9500V (LUN Management mode).
Group
Displays the name of storage group to which the path belongs.
Host
Displays host-name: World-Wide-Name.
File System
Displays the mount point on the host.
Host Bus/TID/LUN
Displays SCSI information recognized by the host.
Capacity
Displays the volume capacity.
% Used
Displays the percentage of use of the volume. The unit is %.

For detailed information about the displayed item, see %Used in section 8.2.1.
Last Updated
Displays the date and time when Device Manager Agent performed last update.
Pair Information
This item is not displayed for T3.
Copy Type
Displays a copy type; ShadowImage, TrueCopy, or QuickShadow. This item is not displayed for T3.
Copy Status
Displays the copy status when volumes are paired.
Fence Level
Displays the recovery settings used when a failure occurs during execution of TrueCopy.
Split Time
Displays the time when a snap shot is obtained when Copy Type is QuickShadow. A blank is
displayed for other than QuickShadow. This item is displayed only for Thunder 9500V.
125
Table 7.1
Detailed Information LDEV-Number Panel Information (continued)
Item
Description
P-VOL
Displays P-VOL information.
LDEV
Displays the logical device number of the primary volume.
Type
Displays the model name of the storage subsystem to which the primary volume belongs.
Serial No.
Displays the serial number of the storage subsystem to which the primary volume belongs.
ArrayGroup
Displays the number of the array group to which the primary volume belongs.
S-VOL
Displays S-VOL information.
LDEV
Displays the logical device number of the secondary volume.
Type
Displays the model name of the storage subsystem to which the secondary volume belongs.
Serial No.
Displays the serial number of the storage subsystem to which the secondary volume belongs.
Array Group
Displays the number of the array group to which the secondary volume belongs.
Guard Mode Information
For TagmaStore USP, displays Data Retention information.

For Lightning 9900V and Thunder 9500V, displays OPEN LDEV GUARD information.
Attribute
Displays the attribute of the logical device.
S-VOL
Displays the S-VOL Disable attribute.
Mode
Displays the INCH bit attribute.
External Storage
Information
If an internal volume of TagmaStore USP is selected, this item displays information on the
external volume that is mapped to the internal volume.
If an external volume is selected, this item displays information on the internal volume to which the
external volume is mapped.
If neither case applies, the message No External Storage Information found appears.
126
External LU(s); the

substance of this volume
Displays information on the external volume that corresponds to the internal volume. This table is
displayed only if an internal volume of TagmaStore USP is selected. For a LUSE, multiple lines
will be displayed.
LDEV
Displays the LDEV number.
External Subsystem
Displays the name of the external subsystem.
External LDEV
Displays the LDEV number of the external subsystem.
External Subsystem
Vendor
Displays the name of the external subsystem vendor.
Assigned LU(s); using

this volume
Displays information on the internal volume to which the external volume is mapped. This table is
displayed only if an external volume is selected. If the internal volume to which an external volume
is mapped is sliced (CVS), multiple lines will be displayed.
Assigned Subsystem
Displays the subsystem name of the internal volume to which an external volume is mapped.
Assigned LDEV
Displays the LDEV numbers of the internal volume to which an external volume is mapped.
7.6.2
Adding Storage to a Storage Group

Storage Administrator can add storage to a storage group. Guest and Local Guest users do
When you add storage, you add one or more LUNs (access paths) to a storage group. You can
add allocated and/or unallocated storage to a storage group. During this process you can
optionally create LUSE device(s) and secure the LUNs to host WWNs.
Note: In Web Client, increasing the amount of data that is displayed in the window increases
the amount of memory that is used. To avoid a memory shortage, we recommend that you
do not add more than 1,000 storage units to a storage group.
Note: If an error occurs when a Local System Administrator or Local Storage Administrator
attempts to add storage, depending on the state of the storage associated with the storage
subsystem, these users may no longer be able to recognize the storage. If such an error
occurs under these circumstances, you should ask the System Administrator or Storage
Administrator to perform a refresh and a LUN Scan, and move the affected storage to an
appropriate storage group.
To add storage to a storage group:
(click on + ), and then select the storage group to which you want to add storage (see
Figure 7.8).
3. Select the Add Storage button in the information frame.
If the selected storage group is empty, the Add Storage (Define Host/Port Connections
step) wizard opens. You will perform steps 5, 6, 7, 8, 9, and 10.
If the selected storage group contains LUNs with the same ports and hosts assigned to
them, the Storage addition operations panel opens (see Figure 7.9). Select the desired
type of storage addition operation, and then select OK to open the Add Storage wizard.
Storage is added with the same port and the same security. (Only LDEV and LUN
are specified): When add storage using the same ports and security settings, you
simply inherit the existing settings for the ports and security settings, and assign
only the LDEVs and LUNs. Select this method when you wish to increase capacity
while creating logical groups on a per-host basis without changing the ports and
security settings. You will perform steps 5, 6, 8, and 9.
Storage is added to another port with the same LDEV and the same security (only
a port and LUN are specified): To add storage to other ports using the same LDEVs
and security settings, you simply assign ports and LUNs to the same LDEVs. Select
this method when you wish to configure switchover paths for existing LUNs. You will
perform steps 4, 8, and 9.
Note: You cannot select this method in the following cases:
For a T3 that does not enable multi-path support.
127
When using the Lightening 9900 series and selecting a LUN group in the Assign LUN(s)
panel (see Figure 7.18).
The usual storage addition (all parameters are specified): Select this method when
you wish to add storage using the normal procedure. You will perform steps 5, 6, 7,
8, 9, and 10.
4. Select Ports Step. The Select Ports panel (see Figure 7.10) allows you to select the
desired port(s) for the storage to be added. Click the Detail button for TagmaStore
USP, Lightning 9900V, or Thunder 9500V (LUN Management mode) to view host storage
domain (HSD) information for the ports. When the port information is correct, select
Next to continue, and go to step 8.
Note: For TagmaStore USP, Lightning 9900V, and Thunder 9500V (LUN Management
Mode), if security is set for the storage group, you can select only the same WWN in the
HSD or ports that have not been used. When security is not set, you can select ports that
have not been set for a storage group.
5. Define Host/Port Connections Step. The Define Host/Port Connections panel (see
Figure 7.11) allows you to select the desired subsystem (empty group only), port(s),
and/or host/port connection(s) for the storage to be added. The Detail buttons
(TagmaStore USP, 9900V, and 9500V) display the host storage domain information for
the ports (See Figure 7.12) When the port and host/port information is correct, select
Next to continue.
Note: You will be able to assign each LUN to different host/port connections, so make
sure to define all desired host/port connections.
Note: Each TagmaStore USP and 9900V port has its own host storage domains with LUN
security settings. The same WWN can only be assigned to one host storage domain on
each port.
Note: For an external port, the Port checkbox appears inactive and cannot be selected.
Note: For TagmaStore USP, 9900V, 9900, and 9500V (LUN Management mode), if you
select security from Host: WWN, you must select View Available Port and then select
Port. Similarly, if you select a port from Port, you must select View Available Host:
WWN and then select Host: WWN.
For Lightning 9900, you can also set a WWN group as security.
The NAS-CHA ports (TagmaStore USP and Lightning 9900V) and mainframe ports (9900V
or 9900) are unavailable.
For TagmaStore USP, 9900V, and 9500V (LUN Management mode), when WWNs are
selected, you can only select ports that satisfy either of the following conditions:
There is a host storage domain whose security settings completely match to those of
all the selected WWNs.
The host storage domain that belongs to the corresponding port does not contain any
of the selected WWNs.
For T3s that enable multi-path support, you can set only the storage subsystem and
ports. Always select both ports when setting.
For T3s that disable multi-paths support, if you add storage to an empty logical group,
you can set only the storage subsystem. If you add storage to an existing storage group,
there are no items in this dialog box that can be set.
128
6. Allocate Storage Step. The Allocate Storage panel (see Figure 7.13) allows you to enter
the ID(s) of the LDEV(s) that you want to add in any of the following three ways:
Enter LDEVs: Enter the desired LDEV(s), and then select Next.
Browse LDEVs: Display a list of available LDEVs on the selected subsystem (see
section 8.2). The Info buttons display the detailed information for each LDEV (see
Figure 7.14). Select the desired LDEV(s), and then select Next.
Find Storage: Enter the total capacity that you want to add, or enter the number
and type of storage devices that you want to add. If desired, you can also specify
the RAID level, disk size, and/or ACP pair (see Figure 7.15).
If you used one of the Find Storage options, the Storage Found panel displays the
storage that matches your search criteria (see Figure 7.15). The displayed list does
not include internal volumes to which external volumes are mapped. To allocate
such volumes, select Enter LDEVs or Browse LDEVs.
Select Next to continue, or select Back to go back to the Allocate Storage panel.
7. Define LUs step (optional). The Define LUs panel (see Figure 7.16) allows you to create
LUSE devices (not applicable to the T3 array). If you do not want to create LUSE devices,
select Next to continue.
To optionally create LUSE devices from unallocated LDEVs, select the desired LDEVs for
each LUSE device, and select the Create LUSE button. See section 8.6 for LUSE device
requirements. When the LUSE information is correct, select Next to continue.
Note on representative LDEV number for a LUSE volume: For Thunder 9500V and
9200, specify the LDEV number of the representative LDEV. For TagmaStore USP,
Lightning 9900V, and Lightning 9900, the smallest number among the LDEVs used to
configure the LUSE volume is selected automatically as the representative LDEV for the
new LUSE volume.
8. Assign Host/Port Connections Step. The Assign Host/Port Connections panel (see Figure
7.17) (not applicable to the T3 array) allows you to set the association between the
volume path and an LDEV.
The host/port connection(s) that you selected on the Define Host/Port Connection panel
are displayed. Select the desired LDEV/LU(s), select the desired host/port connection(s),
and select Add. Repeat as needed. When you are finished assigning connections, select
Next to continue.
9. Assign LUNs Step. The Assign LUN(s) panel (see Figure 7.18) (not applicable to the T3
array) allows you to select the desired LUNs for the storage being added.
The LDEVs/LUs and host/port connections that you selected on the Assign Host/Port
Connections panel are displayed. Verify the preselected LUNs, or enter the desired
LUNs. When you are finished assigning LUNs, select Finish.
Note for Lightning 9900: If you set only ports in the Define Host/Port Connections
panel (Define Host/Port Connections Step), you can register the LUN into a LUN group at
the same time you assign the LUN. To register a LUN into a LUN group, select the target
LUN group. Select Unregistered if you do not wish to register the LUN into a LUN group.
129
10. Summary of Changes Step. The Summary of Changes panel (see Figure 7.19) displays
the requested add storage operations and asks you to confirm the requested operations.
Select Confirm to add the storage as specified, or select Cancel to cancel your request
to add storage. If you need to make any changes, select Back to return to the previous
panel(s).
Note: For the Thunder 9200 subsystem, the DAMP GUI can be used to preset (reserve)
LUN security to a LUN that does not actually exist. If this tool is used and an affected
LUN is used when Device Manager adds storage, LUN security on the storage subsystem
may be configured in a manner not intended by the Device Manager user. If you are
using Device Manager, you should not use the DAMP GUI functionality.
Figure 7.8
130
Add Storage Selecting the Group
Figure 7.9
Add Storage Selecting the Storage Addition Operation
131
Figure 7.10 Add Storage Selecting Ports
Figure 7.11 Add Storage Defining Host/Port Connections

132
Note: You can only select the subsystem if the selected storage group is empty.
Figure 7.12 Add Storage Viewing 9900 V HSD Information
133
Figure 7.13 Add Storage Allocating Storage
Figure 7.14 Add Storage Browsing for LDEVs
134
Figure 7.15 Add Storage Storage Found
Figure 7.16 Add Storage Defining LUs
135
Figure 7.17 Add Storage Assigning Host/Port Connection
Figure 7.18 Add Storage Assigning LUNs
136
Figure 7.19 Add Storage Confirmation (Summary of Changes)
137
7.6.3
Moving Storage from One Group to Another

Storage Administrator can move storage (LUNs) from one storage group to another. Guest
and Local Guest users do not have access to this function.
When you move storage, you move the selected LUNs (paths) from the source storage group
to the target storage group. Both storage groups (source and target) must be on the same
storage subsystem. The access paths to the LUs are not affected by this operation.
Note: For instructions on creating a new group, see section 7.3.
To move one or more LUNs (paths) from one storage group to another:
1. Log in to HiCommand Device Manager as System Administrator, Storage Administrator,
Local System Administrator, or Local Storage Administrator.
2. If you will be moving LUN(s) that are not yet assigned to any user-defined storage group,
select the All Storage or My Storage object in the navigation frame, and select the
Allocated group that contains the LUN(s) that you want to move.
If you will be moving LUNs from a user-defined storage group, you can start from either
the Logical Groups object or the Hosts object in the navigation frame:
From Logical Groups, select the storage group that contains the LUN(s) that you
want to move.
From Hosts, select a host that is associated with the storage group that contains the
LUN(s) that you want to move.
3. From a user-defined storage group: Select the desired LUN(s), and select Move Storage.
From the Allocated group: Select the desired LDEV(s), and select Move to Group.
4. On the Select Logical Group panel (see Figure 7.20), select the desired target storage
group, and select OK to continue. Empty groups and groups with LUNs in the same
subsystem as the selected LUN(s) are available for selection.
5. If any of the selected LDEVs has more than one volume path, the Select Paths panel
opens (see Figure 7.21). Select the desired path(s) to be registered to the target group,
and then select OK.
6. When the confirmation panel appears (see Figure 7.22), select OK to move the LUN(s) as
specified, or select Cancel to cancel your request to move the LUN(s).
WARNING: If an error occurs while you are moving a storage unit (LUN) to another
storage group, the same LUN may exist in both the source and target storage groups at
the same time. In this case, delete the duplicate LUN from the source storage group. Do
not release the LUN when you delete the LUN.
138
Figure 7.20 Move Storage Selecting the Target Group
139
Figure 7.21 Move Storage Selecting the Path(s)
Figure 7.22 Move Storage Confirmation
140
7.6.4
Modifying LUN Security for a Group

Storage Administrator can modify the LUN security of the LUN(s) in a storage group. Guest
and Local Guest users do not have access to this function.
When you add a host WWN to a LUN, you secure that LUN to that WWN. When you remove a
host WWN from a LUN, you unsecure that LUN from that WWN. For TagmaStore USP and
9900V, a secured group (i.e., a logical group containing secured LUNs) constitutes one host
group (host storage domain) on a port of the specified subsystem. When you reach the
maximum number of host groups on a port, you must use another port for securing storage.
The 9900V supports a maximum of 128 host groups per port and 8,192 host groups for the
entire subsystem.
Note: For TagmaStore USP and 9900V, the LUN Manager feature must be enabled. For
9900, the Hitachi SANtinel feature must be enabled. For 9500V, the LUN Security or the LUN
Management feature must be enabled. For 9200, the LUN Security feature must be enabled.
For T3, you cannot modify storage security.
Caution for 9900 LUN groups: An error may occur when you attempt to modify security for
or delete a portion of storage belonging to a LUN group, depending on the specifications of
the 9900 subsystem. To perform operations on a portion of storage within a LUN group, first
remove the storage from the LUN group, and then perform the desired operation.
To modify the LUN security of one or more LUN(s):
(click on + ), and then select the storage group for which you want to modify LUN
security (refer to Figure 7.8).
3. In the information frame, select the desired LUN(s), and then select the Modify Security
button to start the Modify Security wizard.
4. Select Hosts Step. The Select Hosts panel (see Figure 7.23) displays the available host(s)
and allows you to select the host(s) that you want to secure and/or unsecure from the
selected LUN(s). After selecting the desired host(s), select Next to continue.
5. Select WWNs Step. The Select WWNs panel (see Figure 7.24) displays the WWN(s) for
the selected host(s) and allows you to select the WWN(s) that you want to secure to the
LUN(s). After selecting the desired WWN(s), select Next to continue.
The security property that can be set depends on the selected paths and the status of
the WWNs.
(a) If the selected WWNs are not assigned to all of the selected paths, the security
properties that can be set are as follows:
Not assigned (Current Status)
Assign this security to all selected paths
141
(b) If the selected WWNs are assigned to all of the selected paths, the security
Assigned to all paths (Current Status)
Delete this security from all selected paths
(c) If the selected WWNs are assigned to only some of the selected paths, the security
Assigned to some paths (Current Status)
Assign this security to all selected paths
Delete this security from all selected paths
(d) If the selected WWNs belong to the HSDs assigned to one of the selected paths or
belong to the HSDs that do not contain the selected paths, you cannot set security.
In this case, Not assigned (Current Status) appears with the inactive status.
6. Warning for HSD (TagmaStore USP, 9900V, 9500V LUN Management mode). If you
modify the security for storage that belongs to a host storage domain (HSD), the security
of all storage belonging to that HSD changes. For this reason, Device Manager lists all
storage units that will be affected by your requested LUN security change (see Figure
7.25). Select Next to continue, or select Back to return to the previous panel(s).
the requested LUN security changes and asks you to confirm the requested operations.
Select Confirm to modify the LUN security as specified, or select Cancel to cancel your
request. If you need to make any changes, select Back to return to the previous
panel(s).
WARNING: If you change or remove the LUN security set for an external volume, the
internal volume to which that external volume is mapped might become unavailable. In
this case, a warning message is displayed. For details on messages, see section 12.3.8.
142
Figure 7.23 Modify Security Selecting Hosts
Figure 7.24 Modify Security Selecting WWNs

143
Figure 7.25 Modify Security Warning
Figure 7.26 Modify Security Confirmation (Summary of Changes)
144
7.6.5
Deleting Storage from a Group

Storage Administrator can delete storage (LUNs) from an existing storage group. Guest and
Local Guest users do not have access to this function.
When you delete storage, you remove the selected LUN(s) from the storage group. During
the delete storage operation, you can choose to keep or delete the LUN(s) (access paths)
themselves.
Note: To remove paths from LUs, use the unallocate operation (see section 8.5).
Note: If you delete a LUN, any ports in the storage subsystem that belong to that LUN are
reset. This port reset causes any I/O being sent between the hosts and the LUN via such
ports to be canceled. Before deleting a LUN, make sure that no access is underway from the
hosts through the ports that belong to the LUN to be deleted.
Note for 9900 LUN group: When you delete storage belonging to a LUN group, you must
select all storage in that LUN group. If you wish to delete only a portion of such storage, you
must first remove the desired LUNs from the LUN group, and then delete the storage.
To delete storage (LUNs) from a storage group:
2. You can start the delete storage operation from either the Logical Groups object or the
Hosts object in the navigation frame:
From Logical Groups, select the storage group that contains the LUN(s) that you
want to delete.
From Hosts, select a host that is associated with the storage group that contains the
LUN(s) that you want to delete.
3. In the information frame, select the LUN(s) to be deleted, and then select Delete
Storage. If the Delete Storage button is not available, at least one of the selected
LUN(s) is a command device or a copy pair volume and cannot be deleted.
4. The Delete Storage Confirmation panel (see Figure 7.27) lists the LUNs to be deleted
and allows you to either keep or delete the access paths to the LDEVs.
When you select Keep access path, the path is removed from the storage group, but the
path itself remains registered and the logical unit to which the path is set remains in the
allocated group.
If you do not select Keep access path, the path is removed from the storage group and
from the LU, and the LU to which the path was set is moved to the Unallocated group.
Caution: Before deleting a path, make sure that the path is no longer in use.
Note for LUSE: If the LDEVs and paths to be deleted are in a LUSE volume and all paths
of the LUSE volume will be deleted, Device Manager allows you to delete the LUSE
volume if desired. To delete the LUSE volume, select the Delete LUSE button. To retain
the LUSE volume, select the Keep LUSE button.
145
Restrictions for deleting access paths:
For TagmaStore USP and Lightning 9900V, you cannot delete the last volume path
of a logical device specified as a copy pair volume.
For Lightning 9900, you cannot delete the last volume path of a logical device set to
a command device or a logical device specified as a copy pair volume.
For Thunder 9500V (microcode before 0655 only) and Thunder 9200, you cannot
delete any volume path of a logical device set to a command device or a logical
device specified as a copy pair volume.
For 9900, storage (LDEVs) defined for ShadowImage or TrueCopy may not have any
port or LUN assigned. Device Manager cannot be used to delete storage that has not
been configured with an assigned port or LUN. The SVP console must be used to
delete such storage.
5. If you chose to delete the access paths, read the warning (under Storage List in the
Delete Storage - Confirmation panel) about stopping I/O processing from all hosts to the
specified LUN(s). Select YES I have confirmed it to confirm deletion of the specified
path(s).
6. Select OK to delete the specified LUN(s) from the specified group and, if applicable, to
remove the specified path(s) from the LDEVs/LUs. Select Cancel to cancel your request
to delete the storage.
LDEVs/LUs with no remaining paths are now listed in the Unallocated group of the
subsystem (under All Storage/My Storage in the navigation frame).
146
Figure 7.27 Delete Storage Confirmation
147
7.6.6
Removing a Storage Group

Storage Administrator can delete storage groups. Guest and Local Guest users do not have
When a storage group is removed, both the volume paths and the data are deleted from the
storage group that is being removed.
WARNING: Data is lost if the LUN is released. The data saved on the LDEVs in the storage
group is lost. Before deleting a storage group, you should back up the data that is stored on
the LDEVs in the storage group. In addition, you should check that you will no longer have
any need to use the storage in that storage group.
Note: If you delete a LUN, within the storage subsystem any ports to which that LUN belongs
are reset. This port reset causes any I/O being sent between the hosts and the LUN via such
ports to be canceled. Before deleting a LUN, make sure that no access is underway from the
hosts through the port to which the LUN to be deleted belongs.
To remove a storage group or a logical group that contains a storage group:
(click on + ), and then select the group that want to remove (refer to Figure 7.8).
3. Select the Remove Group operation in the method frame.
Note: If the selected group does not contain any storage, see section 7.5 for details on
deleting a logical group.
4. The Remove Logical Group Confirmation panel (see Figure 7.28) lists the LUNs in the
group to be deleted and allows you to either keep or delete the paths to the LUs.
When you select Keep access path, the group is removed, but the path remains
registered and the logical unit to which the path is set remains in the allocated group.
If you do not select Keep access path, the paths are removed from all LUs in the group,
and the LUs are moved to the Unallocated group.
Note for LUSE: If all paths of the LUSE volume will be deleted, Device Manager allows
you to delete or keep the LUSE volume if desired. To delete the LUSE volume, select the
Delete LUSE button. To retain the LUSE volume, select the Keep LUSE button, except
for the Lightning 9900. For 9900 LUSE is deleted at the same time that the path is
deleted. Canceling the LUSE deletion for 9900 cannot be performed.
148
Restrictions for deleting access paths:
For TagmaStore USP and Lightning 9900V, you cannot delete the last volume path
of a logical device specified as a copy pair volume.
For Lightning 9900, you cannot delete the last volume path of a logical device set to
a command device or a logical device specified as a copy pair volume.
For Thunder 9500V (microcode before 0655 only) and Thunder 9200, you cannot
delete any volume path of a logical device set to a command device or a logical
device specified as a copy pair volume.
For 9900, storage (LDEVs) defined for ShadowImage or TrueCopy may not have any
port or LUN assigned. Device Manager cannot be used to delete storage that has not
been configured with an assigned port or LUN. The SVP console must be used to
delete such storage.
5. If you chose to delete the access paths, read the warning (under Storage List in the
Remove Logical Group - Confirmation panel) about stopping I/O processing from all hosts
to the specified LUN(s). Select YES I have confirmed it to confirm deletion of the
specified path(s).
6. WARNING: The delete LUSE operation is destructive. Read and observe the important
warning carefully, and select OK only if it is acceptable to lose the data on the LUSE.
7. Select OK to delete the specified group and, if applicable, to remove the specified
path(s) from the LDEVs/LUs. Select Cancel to cancel your request to delete the group.
You are notified when the remove group operation is complete. LDEVs/LUs with no
remaining paths are now listed in the Unallocated group of the subsystem.
149
Figure 7.28 Remove Logical Group Confirmation
150
Chapter 8
All Storage/My Storage Operations
This chapter describes All Storage/My Storage logical group operations:
Overview of All Storage/My Storage Operations (see section 8.1)
Viewing the All Storage/My Storage group (see section 8.2)
Performing a LUN Scan operation (see section 8.3)
Allocating Storage (see section 8.4)
Unallocating Storage (see section 8.5)
Creating LUSE devices (see section 8.6)
Deleting LUSE devices (see section 8.7)
151
8.1
Overview of All Storage/My Storage Operations

The All Storage or My Storage logical group is created automatically by Device Manager and
is different from groups created by the user. All Storage appears when you log in to Device
Manager as a System Administrator, Storage Administrator, or Guest. When you log in to
Device Manager as a Local System Administrator, Local Storage Administrator, or Local
Guest, My Storage is displayed. The All Storage/My Storage group is always displayed and
cannot be deleted. All Storage/My Storage includes all LDEVs that the logged-in user can
manage organized into a group for each storage subsystem.
The Allocated and Unallocated groups for each subsystem are also created automatically by
Device Manager. If you add a new storage subsystem, Device Manager places the existing
LUNs in the Allocated group, and places the LDEVs without any allocated paths in the
Unallocated group. The All Storage/My Storage group and its subgroups cannot be deleted.
The All Storage/My Storage group displays the subsystems and storage that can be accessed
by the logged-in user, provides detailed information on their properties, and allows you to
configure paths to LDEVs (allocate/unallocate storage).
152
Chapter 8
8.2
Viewing the All Storage/My Storage Group

The All Storage/My Storage group is created automatically by Device Manager and includes
all LDEVs that the logged-in user is permitted to manage. The navigation frame displays the
All Storage group for system users or the My Storage group for local users.
When the All Storage or My Storage object is selected in the navigation frame, the
information frame displays the following information for the All Storage or My Storage group
(see Figure 8.1):
Number of LDEVs = total number of LDEVs in the All Storage or My Storage group
(including all subsystems)
Allocated capacity* = total capacity of the LDEVs in the group with set paths
Unallocated capacity* = total capacity of the LDEVs in the group without set paths
The Object List lists the subsystems in the group and displays the name, number of
LDEVs, allocated capacity, and unallocated capacity for each subsystem.
When the All Storage/My Storage object is expanded, Device Manager displays a group for
each storage subsystem available to the logged-in user. When a subsystem group under the
All Storage or My Storage object is selected, the information frame displays the following
information for the subsystem (see Figure 8.2):
Name = name of the subsystem
Number of LDEVs = total number of LDEVs/LUs in the subsystem
Configured capacity* = total capacity of the LDEVs/LUs in the subsystem (allocated and
unallocated)
The Object List lists the allocated and unallocated groups for the subsystem and displays
the number of LDEVs and capacity for each group
When you select and expand a subsystem group in the All Storage/My Storage group, Device
Manager displays the Allocated storage group(see section 8.2.1) and Unallocated storage
group(see section 8.2.2) for the selected subsystem.
153
154
Figure 8.1
All Storage or My Storage
Figure 8.2
Viewing a Subsystem Group in All Storage/My Storage
Chapter 8
8.2.1
Viewing the Allocated Group for a Subsystem

When the Allocated storage group for a subsystem is selected (see Figure 8.3), the method
frame provides access to the LUN Scan operation for the selected subsystem. For
instructions on performing a LUN Scan operation, see section 8.3.
When the Allocated storage group for a subsystem is selected, the information frame
displays the following information:
Number of LDEVs = number of allocated LDEVs/LUs in the subsystem
Allocated Capacity* = total capacity of the allocated LDEVs/LUs in the subsystem
The Allocate Storage button allows you to add paths to the selected LDEV(s) (see section
8.4).
The Unallocate Storage button allows you to remove paths from the selected LDEV(s) (see
section 8.5).
The Move to Group button allows you to move the selected LDEV(s) to a storage group
(same as move storage operation, see section 7.6.3).
The Object List lists the LDEVs/LUs in the allocated group for the subsystem and displays
detailed information for each LDEV/LU (see Table 8.1). To view the detailed information for
a specific LDEV, select the desired LDEV to open the Detailed Information panel (refer to
Figure 7.7 in section 7.6.1). The Object List has a sort function. To the right of each column
header are two sort buttons that let you sort the contents in ascending or descending order.
Click either button to sort the items in that column. An icon indicating whether the list is
sorted in ascending or descending order appears to the left of the column header you used
as the sort key.
Note: The GB and TB capacity values are rounded down to two decimal places, and the MB
capacity values are rounded down to whole numbers. Therefore, the capacity shown on the
Device Manager window may be less than the actual capacity available.
155
Figure 8.3
156
Chapter 8
Viewing the Allocated Group for a Subsystem (9900 V)
Table 8.1
Allocated Group Information under All Storage/My Storage (continues on the following pages)
Column
Description
LDEV
LDEV number. The icon indicates LUN security status. For LUN expansion or LUSE, only a
representative LDEV number is displayed.
Select the link to display the Detailed Information panel for the LDEV (refer to Figure 7.7 in section
7.6.1).
Type
Displays the LDEV type. This column is only displayed for TagmaStore USP and Thunder 9500 V.
For TagmaStore USP:
#AT = LDEV to which an external volume is mapped and that is connected to an SATA drive
#- = LDEV to which an external volume is mapped and that is connected to an unidentified type of
drive
- = LDEVs other than those above
For Thunder 9500V:

AT = LDEV connected to an SATA drive
FC = LDEV connected to an FC drive
- = LDEV connected to an unidentified type of drive, or a subsystem that does not have a function
for identifying FC and AT.
Port / HSD / LUN or

Port / LUN
Ports, host storage domains, and LUNs for TagmaStore USP, 9900V, and 9500V in LUN
Management mode.
Ports and LUNs for 9900, 9500V in LUN Security mode, 9200, and Sun StorEdge T3.
LUN Group
LUN group name for a Lightning 9900. Not shown for any other storage products.
Group
Name of the storage group to which the volume path (LUN) belongs.
Host
Host name and WWN. If there are multiple paths, multiple hosts and WWNs are displayed.
Note: When a host is displayed in red text, this indicates that the host is not listed in the Device
Manager host table (i.e., it has not been added to Device Manager).
File System
Mount point (e.g., D:\ for Windows, /mnt/RAID for Solaris). When a volume is mounted on multiple
mount points, all mount points are displayed, separated by commas. Displayed only when the Device
Manager Agent is installed on the host.
EMU Type
Device emulation type for TagmaStore USP, Lightning 9900V, or Lightning 9900. For LUSE, displays
emulation type and number of LDEVs in the LUSE.
Not shown for Thunder 9500V or Thunder 9200.
Displays OPEN for Sun StorEdge T3.
Capacity
LDEV capacity. Values in GB and TB are rounded down to two decimal places. Values in MB are
rounded down to whole numbers. So, the value shown here may be less than the actual capacity.
For TagmaStore USP, Lightning 9900V, and Lightning 9900, this field also displays the size of an
intermediate HRX volume.
157
Table 8.1
Allocated Group Information under All Storage/My Storage (continued)
Column
Description
% Used
Displays the volume usage. The unit is %.

This item is updated when the Device Manager agent reports the volume usage to the Device Manager
server.
Use the following expression to obtain the storage usage:
Amount of used file system capacity established on the target storage storage capacity x 100 (%)
The usage cannot be calculated when the values required for calculation are incorrectly obtained. In
this case, -- appears. To calculate the usage, see the following conditions:
The Device Manager agent is running on the host.
When Device Manager agent is not running, the usage is displayed as blank.
When Windows is used for the platform of the host using the storage
When the following conditions are satisfied, -- appears. Otherwise, the usage is displayed.
- A drive letter has not been assigned to the LU.
- The LU has not been directory-mounted.
- The LU has multiple partitions and, among the disks in the LU, there is a disk to which a drive letter
has not been assigned or that has not been directory-mounted. However, when the LU or part of the
LU that has multiple partitions is under the dynamic disk configuration, -- might appear.
When Solaris is used for the platform of the host using the storage
- The target LU has been incorporated into a volume manager (VxVM, SVM, or SDS).
- The LU has not been mounted.
When Linux is used for the platform of the host using the storage
- The target LU has been incorporated into a volume manager (LVM).
- The LU has multiple partitions and part of the LU (even one partition) has been incorporated into a
volume manager.
- The LU or part of the LU that has multiple partitions has not fully been mounted.
When HP-UX or AIX is used for the platform of the host using the storage
The usage is not displayed, -- appears.
One LU might have multiple values for the usage % Used. As such, please note the following:
If storage is identified concurrently by more than one host, Web Client displays the usage of the
storage for the host (Device Manager agent) that reported the most recent data. The host that reports
the most recent information may report the usage of the storage as --. In this case, the usage is
displayed as -- even if another host is using the storage, unless that host reports the storage usage.
If storage is identified as multiple devices by a single host, the largest value from the multiple devices is
displayed as the storage usage.
Volume Attr
Displays volume attribute for LUN Expansion (LUSE), Virtual LVI/LUN (CVS), QuickShadow.
LUSE = LUSE volume
CVS = Volume created with the Virtual LVI/LUN (or CVS) function
LUSE (CVS) = LUSE volume consisting of CVS volumes
V-VOL = V-volume used in QuickShadow
POOL = QuickShadow data pool volume
GUARD = Data Retention or Open LDEV Guard volume
External = External volume
IO Suppression = Volume in IO suppression mode, to which an external volume is mapped
Cache Through = Volume in Cache Through mode, to which an external volume is mapped
None = Ordinary volume
CMD DEV
158
Chapter 8
Displays whether the LDEV is a command device (CMD DEV, or blank).
Table 8.1
Allocated Group Information under All Storage/My Storage (continued)
Column
Description
Copy Type
Displays copy type:

SI = ShadowImage
TC (Sync) = TrueCopy Synchronous
TC (Async) = TrueCopy Asynchronous
TC = TrueCopy with unidentifiable synchronous mode*
QS = QuickShadow
Unpaired = unpaired
Blank = pair status unknown
*Displayed when the subsystem containing the TrueCopy P-VOL has not been registered in Device
Manager. If, the target subsystem (S-VOL) is a TagmaStore USP or Lightning 9900V, this column
displays either TC (Sync) or TC (Async), because Device Manager can obtain information about
synchronous mode.
Copy Role
Copy role: P-VOL, S-VOL, or Blank = ordinary volume
Copy Status
Copy status:
Simplex = SMPL status
Pair = PAIR status
Copying = COPY (PD), COPY (RS), COPY (SP), or COPY status
Reverse-Copying = COPY (RS-R) copy status
Split = PSUS or PSUS (SP) copy status
Suspended = PSUE copy status
Error in LUSE = PDUB copy status
Suspending = Suspending status
Deleting = Deleting status
Blank = copy status is unknown.
External Subsystem
Displays the external subsystem name. This column is displayed only for TagmaStore USP.
External subsystem name = Displayed when all the following conditions are met:
- The volume is an internal volume to which an external volume is mapped.
- Device Manager has managed the external subsystem.
- If a Local user is logging in, an external volume has been allocated to the user.
External system model#External subsystem serial number = Displayed when all the following
conditions are met:
- The user is logging in as a System user.
- Device Manager has not managed the external subsystem.
- The model that Universal Volume Manager can acquire its serial number.
External system model = Displayed when all the following conditions are met:
- The model that Universal Volume Manager cannot acquire its serial number.
Unknown = Displayed when all of the following conditions are satisfied:
- The volume must be an internal volume to which an external volume is mapped.

- You must have logged on as a Local user.
- The external volume must be allocated to the log-in user.
Blank = Displayed when the volume is other than the internal volume to which an external volume is
mapped.
Last Updated
Time of the last Agent update. Displayed only when Device Manager Agent is installed on the host.
159
8.2.2
Viewing the Unallocated Group for a Subsystem

When the Unallocated storage group for a subsystem is selected (see Figure 8.4), the
information frame displays the following information:
Number of LDEVs = number of unallocated LDEVs/LUs in the subsystem
Unallocated Capacity* = total capacity of the unallocated LDEVs/LUs in the subsystem
The Allocate Storage button allows you to add paths to the selected LDEV(s) (see section
8.4).
The Create LUSE button allows you to create LUSE devices (see section 8.6).
The Delete LUSE button allows you to delete LUSE devices (see section 8.7).
The Object List lists the LDEVs/LUs in the unallocated group for the subsystem and displays
detailed information for each LDEV/LU (see Table 8.2). To view the detailed information for
a specific LDEV, select the desired LDEV to open the Detailed Information panel (refer to
Figure 7.7 in section 7.6.1). The Object List has a sort function. To the right of each column
header are two sort buttons that let you sort the contents in ascending or descending order.
Click either button to sort the items in that column. An icon indicating whether the list is
sorted in ascending or descending order appears to the left of the column header you used
as the sort key.
Note: The GB and TB capacity values are rounded down to two decimal places, and the MB
capacity values are rounded down to whole numbers. Therefore, the capacity shown on the
Device Manager window may be less than the actual capacity available.
160
Chapter 8
Figure 8.4
Viewing the Unallocated Group for a Subsystem (9900 V)
161
Table 8.2
Unallocated Group Information under All Storage/My Storage (continues on the next page)
Column
Description
LDEV
LDEV number. For LUSE, only a representative LDEV number is displayed. Select the link to display the
Detailed Information panel for the LDEV (refer to Figure 7.7 in section 7.6.1).
Type
Displays the LDEV type. This column is only displayed for TagmaStore USP and Thunder 9500 V.
For TagmaStore USP:
#AT = LDEV to which an external volume is mapped and that is connected to an SATA drive
#- = LDEV to which an external volume is mapped and that is connected to an unidentified type of
drive
- = LDEVs other than those above
For Thunder 9500V:

AT = LDEV connected to an SATA drive
FC = LDEV connected to an FC drive
- = LDEV connected to an unidentified type of drive, or a subsystem that does not have a function for
identifying FC and AT.
Capacity
LDEV capacity. Values in GB and TB are rounded down to two decimal places. Values in MB are
rounded down to whole numbers. So, the value shown here may be less than the actual capacity.
For TagmaStore USP, Lightning 9900V, and 9900, this field also displays the size of an intermediate
HRX volume. For more information on the HRX intermediate volume, see the documentation for the
storage subsystem that you use.
EMU Type
Device emulation type for TagmaStore USP, 9900V or 9900. For LUSE, this item indicates emulation
type and number of LDEVs in the LUSE.
Not shown for Thunder 9500V or Thunder 9200.
Displays OPEN for Sun StorEdge T3.
Default controller
Default port controller (9500V, 9200 only)
Volume Attr
Displays volume attribute for LUN Expansion (LUSE), Virtual LVI/LUN (CVS), QuickShadow.
LUSE = LUN Expansion or LUSE volume
CVS = Volume created with the Virtual LVI/LUN (or CVS) function
LUSE (CVS) = LUSE volume consisting of CVS volumes
V-VOL = V-volume used in QuickShadow
POOL = QuickShadow data pool volume
GUARD = Data Retention or Open LDEV Guard volume
External = External volume
IO Suppression = Volume in IO suppression mode, to which an external volume is mapped
Cache Through = Volume in Cache Through mode, to which an external volume is mapped
None = Ordinary volume

CMD DEV
Displays whether the LDEV is a command device (CMD DEV, or blank).
Copy Type
Displays copy type:

SI = ShadowImage
TC (Sync) = TrueCopy Synchronous
TC (Async) = TrueCopy Asynchronous
TC = TrueCopy with unidentifiable synchronous mode*
Unpaired = unpaired
None = pair status unknown
*Displayed when the subsystem containing the TrueCopy P-VOL has not been registered in Device
Manager. If, the target subsystem (S-VOL) is a TagmaStore USP or Lightning 9900V, this column
displays either TC (Sync) or TC (Async), because Device Manager can obtain information about
synchronous mode.
Copy Role
162
Chapter 8
Copy role: P-VOL, S-VOL, or Blank = ordinary volume
Table 8.2
Unallocated Group Information Under All Storage/My Storage (continued)
Column
Description
Copy Status
Copy status:
Simplex = SMPL status
Pair = PAIR status
Copying = COPY (PD), COPY (RS), COPY (SP), or COPY status
Reverse-Copying = COPY (RS-R) copy status
Split = PSUS or PSUS (SP) copy status
Suspended = PSUE copy status
Error in LUSE = PDUB copy status
Suspending = Suspending status
Deleting = Deleting status
None = copy status is unknown.
External Subsystem
Displays the external subsystem name. This column is displayed only for TagmaStore USP.
External subsystem name = Displayed when all the following conditions are met:
- Device Manager has managed the external subsystem.
- If a Local user is logging in, an external volume has been allocated to the user.
External system model#External subsystem serial number = Displayed when all the following
conditions are met:
- The model that Universal Volume Manager can acquire its serial number.
External system model = Displayed when all the following conditions are met:
- The model that Universal Volume Manager cannot acquire its serial number.
Unknown = Displayed when all of the following conditions are satisfied:
- The volume must be an internal volume to which an external volume is mapped.

- You must have logged on as a Local user.
- The external volume must be allocated to the log-in user.
Blank = Displayed when the volume is other than the internal volume to which an external volume is
mapped.
163
8.3
Performing a LUN Scan Operation

The System Administrator (or Storage Administrator) can perform LUN Scan operations.
Guests, Local System Administrators, Local Storage Administrators, and Local Guests do not
have access to this function.
After initial subsystem discovery, none of the LUNs defined on the storage array are
associated with a (user-defined) storage group. When you perform a LUN Scan after adding a
subsystem and its associated hosts, Device Manager creates a hierarchy of logical groups and
storage groups to contain all of the existing LUNs on the subsystem. The LUN Scan operation
creates the LUN Scan top-level group and a logical group for the subsystem inside the LUN
Scan group, and then places the LUNs into storage groups organized by port and security.
The LUNs in the LUN Scan group can be moved to new or existing storage groups as desired.
The LUN Scan also causes Device Manager to register the hosts that have WWNs associated
with the LUNs. The attributes of the host registered by Device Manager are updated when
the Device Manager Agent reports information about the host.
When you execute a LUN Scan on the Lightning 9900, Device Manager places LUNs that
belong to the same LUN group in the same storage group, and creates a temporary host for
each WWN in the WWN group and registers the WWN in the host.
Note: If you display the contents of the LUN SCAN group while LUN Scan is being executed
and before the operation is completed, the value displayed for number of LUNs may be less
than the actual number. To display the correct LUN count, display the contents of the LUN
SCAN group again after LUN Scan ends.
Note: If you change the displayed name of a storage subsystem from the Web Client after
LUN Scan execution, the logical group name in the LUN SCAN group is not updated. If you
execute another LUN Scan on a subsystem after changing the subsystem name, Device
Manager creates a logical group having a different name from the existing logical group.
To perform a LUN Scan operation:
1. Log in to HiCommand Device Manager as a System Administrator or Storage
Administrator.
2. Before performing the LUN Scan operation, make sure that all hosts and their WWNs are
registered and that the subsystem name is as desired. If not, add the hosts and change
the subsystem name now (see section 10.1.3), so that the logical groups and storage
groups created by the LUN Scan operation reflect the desired subsystem name. Device
Manager automatically creates a host for one WWN in the storage subsystem when the
LUN Scan operation is performed. Device Manager also automatically determines the
host names. Before performing the LUN Scan operation, make sure that all hosts and
their WWNs are registered.
If the subsystem name has been changed since the last time a LUN Scan was performed,
make sure the names of the logical groups in the LUN Scan group have been updated to
match the new subsystem name. If the subsystem name in the LUN Scan group does not
match the new subsystem name and another LUN Scan is executed, a separate logical
group will be created in the LUN Scan group using the new subsystem name.
164
Chapter 8
3. Select and expand the All Storage or My Storage object in the navigation frame, select
the desired subsystem, and then select the Allocated group (refer to Figure 8.3).
4. In the method frame, select the LUN Scan operation.
5. When the LUN Scan Confirmation panel appears (see Figure 8.5), select OK to perform
the LUN scan operation, or select Cancel to cancel your request to perform a LUN Scan.
HiCommand Device Manager scans the selected subsystem for LUNs not assigned to any
storage group and places these LUNs into the LUN Scan group. The detected LUNs are
also added to the Allocated group.
6. When the LUN Scan operation is complete, you can view the updated list of LUNs in the
LUN Scan storage groups for the subsystem (under Logical Groups, see section 7.6.1) or
in the Allocated storage group for the subsystem (under All Storage/My Storage) (see
section 8.2.1).
After the LUN Scan operation, you can leave the LUNs in the LUN Scan storage groups
and manage the storage there, or you can create your own logical groups and move the
LUNs from the LUN Scan group into your customized groups. To move LUNs to another
group, select the desired LUNs in the LUN Scan group, and then select Move Storage
(see section 7.6.3 for instructions).
Figure 8.5
Performing a LUN Scan Confirmation
165
8.4
Allocating Storage
Storage Administrator can allocate storage. Guest and Local Guest users do not have access
to this function.
When you allocate storage, you assign one or more access paths (port/LUN) to LDEV(s), and
you can optionally secure the new LUN(s) to host WWN(s). You can allocate LDEVs that are
unallocated or already allocated.
Note: You can also assign a volume path when you add a storage to a storage group (see
section 7.6.2).
To allocate storage:
2. Select and expand the All Storage or My Storage object in the navigation frame, and
then select the subsystem and group (Allocated or Unallocated) that contains the
LDEV(s) that want to allocate.
3. Select the desired LDEV(s), and select the Allocate Storage button to open the Add
Storage wizard.
4. For instructions on using the Add Storage wizard to allocate storage, please refer to
section 7.6.2.
166
Chapter 8
8.5
Unallocating Storage
Storage Administrator can unallocate storage. Guest and Local Guest users do not have
When you unallocate storage, you remove one or more access paths from an LDEV. When you
unallocate a LUSE device, you can also optionally delete the LUSE device to make the
individual LDEVs available for use.
Note: for command device and copy pair volumes:
For TagmaStore USP and Lightning 9900V, you cannot unallocate the last volume path from
a logical device that is specified as a copy pair volume.
For the Lightning 9900, you cannot unallocate the last volume path from a logical device
that is specified as a command device or as a copy pair volume.
For the Thunder 9500V (microcode before 0655) and 9200, you cannot unallocate any
volume paths from a logical device that is specified as a command device or as a copy pair
volume.
To unallocate storage:
the subsystem that contains the LDEV(s) that want to unallocate, and then select the
Allocated group.
3. Select the desired LDEV(s), and select the Unallocate Storage button.
4. When the confirmation panel appears (see Figure 8.6), read and observe the important
warning. Select OK to go ahead and delete the specified path(s), or select Cancel to
cancel your request to unallocate storage.
5. If you selected a volume with more than one path, Device Manager displays the paths
and asks you to select the path(s) to be deleted (see Figure 8.7). Select the desired
path(s), and select OK to continue, or select Cancel to cancel your request to unallocate
storage.
6. If all paths of a LUSE device will be deleted, Device Manager allows you to keep or
delete the LUSE device (see Figure 8.8) (9900 LUSE is always deleted, see below).
WARNING: The delete LUSE operation is destructive. Read and observe the important
warning on the LUSE Confirmation panel.
To delete the LUSE volume, check the Yes I have confirmed it box, and then select
the Delete LUSE button only if it is acceptable to lose the data on the LUSE volume.
To retain the LUSE volume, select the Keep LUSE button, except for the Lightning
9900. For 9900 LUSE is deleted at the same time that the path is deleted.
Canceling the LUSE deletion for 9900 cannot be performed.
167
You are notified when the unallocate storage operation is complete. LDEVs/LUs with no
remaining paths are now listed in the Unallocated group of the subsystem.
Figure 8.6
168
Chapter 8
Unallocate Storage Confirmation
Figure 8.7
Unallocate Storage Selecting the Path(s)
169
Figure 8.8
170
Chapter 8
Unallocate Storage LUSE Confirmation
8.6
Creating LUSE Devices

WARNING: The create LUSE device operation is destructive. The data stored on the
LDEVs/LUs that will be combined to make the LUSE device will be lost. The user is
responsible for backing up the data before performing this operation.
Storage Administrator can create LUSE devices on the Hitachi storage subsystems. Guest and
Note: If you use DAMP to create a LUSE volume from two or more LUs that have allocated
LUNs, or if you allocate LUNs to LUs other than the Main LU after you create a LUSE volume,
Device Manager displays the allocated LUNs for the LUs, except the Main LU. For these LUNs,
the size is not displayed, and you will not be able to delete or perform other operations on
them. In this case, use the DAMP to delete the target LUNs that can no longer be used, and
refresh the display from Device Manager.
LUSE devices are created from unallocated LDEVs. Device Manager allows you to create LUSE
devices in several ways:
For the Lightning 9900, you can create a LUSE volume when allocating a volume path
(see section 8.4) and when adding storage to a storage group (see section 7.6.2). You
cannot create a 9900 LUSE volume that does not have an allocated volume path.
For the TagmaStore USP, Lightning 9900V, Thunder 9500V, and Thunder 9200, you can
create a LUSE device that is not added to a storage group and does not have an
allocated volume path (instructions in this section). The 9900 does not allow this. You
can also create a LUSE device when allocating a volume path to an LDEV (see section
8.4) or when adding storage to a storage group (see section 7.6.2).
Requirements: LUSE devices have the following requirements:
Common requirements
An LDEV set as a command device cannot be used.
An LDEV registered as an external volume cannot be used.
TagmaStore USP, Lightning 9900V, and Lightning 9900 LUSE requirements:
The LDEVs in a LUSE device must be located in the same control unit (CU).
The LDEVs in a LUSE device must be the same size.
The LDEVs in a LUSE device must be the same emulation type (e.g., OPEN-3,
OPEN-8, OPEN-9, OPEN-K, OPEN-E, OPEN-L, OPEN-M, and OPEN-V).
The LDEVs in a LUSE device must be the same RAID level.
The LDEVs in a LUSE device must be either Customized Volumes or Normal Volumes
(intermixing of custom and normal volumes is not allowed). For TagmaStore USP or
Lightning 9900V, an intermix of LDEVs and pre-existing LUSE devices is allowed when
all LDEVs are the same size and emulation type (e.g., OPEN-3 + OPEN-3*3 LUSE =
OPEN-3*4 LUSE).
A volume reserved for Volume Migration (TagmaStore USP), CruiseControl

(Lightning 9900V), or Hitachi Internal Hierarchical Storage Management (HIHSM)
(Lightning 9900) cannot be used for a LUSE device.
171
A volume assigned to a TrueCopy or ShadowImage copy pair cannot be used for a

LUSE device.
Depending on the type of a storage subsystem, the following features must be

enabled:
For TagmaStore USP: LUN Manager and LUN Expansion
For Lightning 9900V: LUN Management and LUSE
For Lightning 9900: LUN Manager, Hitachi SANtinel, and LUSE
When you are using Universal Volume Manager on a TagmaStore USP subsystem,
you cannot create a LUSE device that intermixes internal volumes without external
volumes mapped, and internal volumes to which external volumes are mapped.
When you are using Universal Volume Manager on a TagmaStore USP subsystem, the
internal volumes to which external volumes are mapped must have the same IO
Suppression mode and Cache Through mode.
9500V and 9200 LUSE requirements:
The default controller for the LDEVs in a LUSE device must be same.
RAID 0 volumes cannot be used for a LUSE device.
The maximum LUSE device size is 2 TB.
A LUSE device that is created by DAMP tool cannot be used as a LUSE device.
A blocked or unformatted volume cannot be used for a LUSE device.
A volume assigned to a TrueCopy, ShadowImage, or QuickShadow copy pair cannot

be used for a LUSE device.
For 9200 LDEV #0 can be used as main LDEV and sub-LDEV (microcode 055E and
later).
The Resource Manager and LUN Security features must be enabled.
To create LUSE devices in the Unallocated storage group (TagmaStore USP, Lightning
9900V, Thunder 9500V, or Thunder 9200):
WARNING: The create LUSE device operation is destructive. Make sure that you have
backed up the data on the LDEVs/LUs that will be combined to make the LUSE device.
the subsystem for which you want to create LUSE devices, and then select the
Unallocated group.
3. Select the desired LDEVs for the LUSE devices, and select the Create LUSE button. You
can select LDEVs and pre-existing LUSE devices when all LDEVs are the same size and
emulation.
4. On the Create LUSE panel, select the devices, and use the Create LUSE button to
create the desired LUSE device(s) (see Figure 8.9). Use the Cancel LUSE button as
needed to remove LUSE LUs and re-enable the LDEVs/LUs in the LDEV list.
172
Chapter 8
For Thunder 9500V and 9200, specify the LDEV number of the representative LDEV for
the LUSE device. For TagmaStore USP and Lightning 9900V, the smallest LDEV number
in the LUSE volume automatically becomes the representative LDEV number of a new
LUSE volume.
Note: You cannot delete/reconstruct existing LUSE devices during this procedure. You
must delete a LUSE device first in order to use the individual LDEVs.
Note: For an LDEV that is being used as an external volume, the checkbox appears
inactive and cannot be selected.
5. When the information on the Create LUSE panel is correct, select OK, or select Cancel
to cancel your request to create LUSE device(s).
6. When the confirmation panel appears (see Figure 8.10), review the information, and
read and observe the important warning.
If it is acceptable to create the LUSE device(s) and lose the data on the LDEVs/LUs to be
in the LUSE device(s), check the Yes I have confirmed it box, and then select Confirm.
To cancel your request to create the LUSE device(s), select Cancel.
Figure 8.9
Create LUSE Selecting LDEVs
173
Figure 8.10 Create LUSE Confirmation and Warning
174
Chapter 8
8.7
Deleting LUSE Devices

WARNING: The delete LUSE device operation is destructive. The data stored on the LUSE
device will be lost. The user is responsible for backing up the data before performing this
operation.
Storage Administrator can delete LUSE devices on Hitachi storage subsystems. Guest and
For the TagmaStore USP, Lightning 9900V, Thunder 9500V, and Thunder 9200 subsystems,
you can also delete LUSE devices optionally during the unallocate storage operation (see
section 8.5).
Note: This operation cannot be performed on Lightning 9900. A 9900 LUSE volume is
automatically deleted when the last access path is removed (see section 8.5).
Note: For the Thunder 9500V and 9200, you can only delete the last LUSE that was created.
To delete one or more LUSE devices:
2. WARNING: The create LUSE device operation is destructive. Make sure that the LUSE
devices to be deleted are no longer in use and that the data has been backed up.
the subsystem for which you want to create LUSE devices, and then select the
Unallocated group.
4. Select the desired LUSE device(s), and then select the Delete LUSE button.
5. When the Delete LUSE Confirmation panel appears (see Figure 8.11), review the
information, and read and observe the important warning.
If it is acceptable to delete the LUSE device(s) and lose the data on those device(s),
check the Yes I have confirmed it box, and then select Confirm.
To cancel your request to delete the LUSE device(s), select Cancel.
175
Figure 8.11 Delete LUSE - Confirmation and Warning
176
Chapter 8
Chapter 9
Performing Host Operations
This chapter describes HiCommand Device Manager host operations:
Overview of HiCommand Device Manager host operations (see section 9.1)
Viewing the list of hosts (see section 9.2)
Adding a host (see section 9.3)
Viewing host properties and volume information (see section 9.4)
Modifying host properties (see section 9.5)
Updating host information (see section 9.6)
Managing copy pairs (see section 9.7)
Removing a host (see section 9.8)
177
9.1
Overview of HiCommand Device Manager Host Operations

A computer system that uses storage on a subsystem is referred to as a host. The Device
Manager Agents installed on these hosts periodically send information about the hosts and
the storage used by the hosts to the Device Manager Server. This enables monitoring of how
the hosts use the storage in the storage subsystems managed by Device Manager.
In Device Manager, a world wide name (WWN) or a group of world wide names can be
handled as a host. If you have not installed the Device Manager Agent on a host, you can set
a Device Manager host on a physical host basis. Also, you can set a Device Manager host on a
basis of a group of WWNs that access a specific storage in a storage subsystem managed by
Device Manager.
The external port used in Universal Volume Manager of TagmaStore USP operates external
volumes that are managed by the external storage subsystem, in the same way as a host.
Therefore, Device Manager manages the external port as a host.
The HiCommand Device Manager host operations are performed by the System
Administrator, Storage Administrator, Local System Administrator, and Local Storage
Administrator. Guest and Local Guest users can only view the host information.
The Hosts object in the navigation frame (see Figure 9.1) provides access to the host
operations.
178
Chapter 9
Figure 9.1
Hosts
179
9.2
Viewing the List of Hosts

All HiCommand Device Manager users can view the list of hosts for which they have access
permission. To view the list of hosts, select the Hosts object in the navigation frame, and
then expand the tree hierarchy under the Hosts object by clicking on + (see Figure 9.1).
Note: When Universal Volume Manager of TagmaStore USP is used, the external port for
TagmaStore USP appears in a list of hosts.
When the Hosts object is selected

When the Hosts object is selected in the navigation frame, the method frame displays
the following operations:
Add Hosts (see section 9.3)
List Objects (described in this section)
When the Hosts object is selected in the navigation frame, the information frame
displays the list of hosts. The name, IP address, and storage capacity are displayed for
each host.
When a specific host is selected

When a host is selected in the navigation frame, the method frame displays the
following operations:
Add Storage (same as add storage to a storage group, see section 7.6.2)
List Objects (described in this section)
Modify Properties (see section 9.4)
Remove Host (see section 9.8)
When a host is selected in the navigation frame, the Show Properties host-name
subwindow in the information frame displays the following information and operations
for the selected host (see section 9.4):
Name: name of the host
IP address: IP address of the host
Capacity: total capacity of the storage in the host, including the storage in all
subsystems managed by Device Manager
World Wide Names: WWNs associated with the host
Type: Host type

For the external port, Storage Port (subsystem-name/port-name) is displayed. For
normal hosts, nothing is displayed.
180
Delete Storage (same as delete storage from a storage group, see section 7.6.5)
Move Storage (same as move storage from one group to another, see section 7.6.3)
Refresh (see section 9.6)
List of hosts that centrally manage the copy pairs accessible from the selected host
List of volumes allocated to the host organized by storage group
Chapter 9
9.3
Adding a Host
There are two ways to add hosts to your HiCommand Device Manager system:
9.3.1
By executing a LUN Scan operation (see section 9.3.1)
By adding hosts manually (see section 9.3.2)
Adding Hosts by Executing a LUN Scan

When you execute a LUN Scan operation on a storage subsystem, Device Manager detects the
WWNs and automatically registers a temporary host per WWN. The names of the temporary
hosts are host_serial-number (e.g., host_1, host_2, etc.), except for the WWNs in a WWN
group. For the WWNs in a Lightning 9900 WWN group, Device Manager uses a naming
convention that indicates the WWN group name: WWN-group-name_serial-number. For
example, the WWNs in the WWN group called Finance would be named Finance_1,
Finance_2, Finance_3, etc. (instead of host_1, host_2, etc.). For details on the LUN Scan
operation, see section 8.3.
If the Device Manager Agent is installed on a host, the Agent sends detailed information
about the host to the Device Manager Server, and the Device Manager Server registers the
new host according to the information received from the Device Manager Agent. If the new
host contains a WWN that was detected during a LUN Scan, Device Manager moves the WWN
from the temporary host created during the LUN Scan (e.g., host_1 or Finance_1) to the
new host registered. After the WWN has moved, the temporary host becomes empty and
should be deleted. For details on deleting a host, see section 9.8.
You can rename the hosts created during LUN Scan to more easily identify them, combine
WWNs that are on a single physical host, and delete the extraneous hosts as needed.
181
9.3.2
Adding Hosts Manually

Storage Administrator can add hosts to HiCommand Device Manager. Guest and Local Guest
users do not have access to this function.
When you manually add a host, you identify the host system and its associated WWNs to the
HiCommand Device Manager system. Once a host has been added to Device Manager, you
can use this information to secure LUNs using the WWNs of this host.
To add a host to HiCommand Device Manager:
2. Select the Hosts object in the navigation frame (refer to Figure 9.1), and then select the
Add Host operation in the method frame to open the Add Host panel (see Figure 9.2).
3. Enter the name for the new host.
Note: The host name is not case-sensitive. For example, if HOST1 is already
registered, you cannot use host1 for a new host. The host name can be a maximum of
50 bytes. You can use the following characters:
A - Z, a - z, 0 - 9, -, _, ., @
The host name may include spaces, but cannot consist only of spaces. Leading or trailing
spaces are discarded.
4. To add the WWN(s) associated with the new host, select the Add button, enter the
WWN, and select OK (see Figure 9.3). Repeat to add each WWN for this host.
Note: You must enter at least one WWN for the new host. Enter a WWN in the following
format. You can omit periods (.).
XX.XX.XX.XX.XX.XX.XX.XX
(XX: two hexadecimal digits)
5. When you are finished adding WWNs, review the information on the Add Host panel. If
the information is correct, select OK to add the specified host (or select Cancel to
cancel your request to add a new host).
182
Chapter 9
Figure 9.2
Add Host Entering the Name
Figure 9.3
Add Host Entering the WWN(s)
183
9.4
Viewing Host Properties and Volume Information

All HiCommand Device Manager users can view host properties and the detailed information
for the volumes (storage) allocated to each host.
To view the host properties and detailed information for the volumes allocated to that host:
1. Select and expand the Hosts object in the navigation frame (refer to Figure 9.1).
2. Select the desired host in the navigation frame.
The method frame provides the following operations: Add Storage (see section 7.6.2),
Modify Properties (see section 9.4), Remove Host (see section 9.8).
The Show Properties host-name subwindow in the information frame displays the
following properties for the selected host (see Figure 9.4): Name, IP address, Capacity
(total capacity of storage (volumes) allocated to the host), Type (host type), and WWNs
assigned to the host.
The information frame provides the following operations: Delete Storage (refer to
section 7.6.5), Move Storage (refer to section 7.6.3), Refresh (see section 9.6). Delete
Storage and Move Storage are displayed when storage (volumes) is allocated to the
selected host. Refresh is displayed when Device Manager Agent (2.3 or a later version) is
installed in the selected host.
If storage has been allocated to the host. The information frame lists the volumes
accessible to the host organized by storage group and displays the LDEV number and
path (e.g., port, host storage domain (HSD), LUN) for each volume.
If copy pairs are managed for the selected host. When the copy pair requirements
are met (e.g., CCI and Device Manager Agent on the host, command device, LUN
security, etc.) (see section 4.4), the information frame provides the following
operations for managing copy pairs:
Create Pair
Modify Pair (available only when one or more copy pairs are managed by the host)
Delete Pair (available only when one or more copy pairs are managed by the host)
View Pair (available only when one or more copy pairs are managed by the host)
Note: The Create Pair, Modify Pair, and Delete Pair buttons do not appear when
you have logged on as a Guest or Local Guest.
If copy pairs are managed in a batch configuration. The Replication Management

Console drop-down list shows the hosts that manage copy pairs that meet the
requirements. Also, you can manage copy pairs from the information frame by using
the following commands:
Create Pair
Modify Pair
Delete Pair
View Pair
Note: The Create Pair, Modify Pair, and Delete Pair button does not appear when
you have logged on as a Guest or Local Guest.
184
Chapter 9
If HDLM is installed on the selected host. When the Device Manager Agent and
HDLM are installed on the selected host, the information frame displays the Dynamic
Link Manager button for launching HDLM. For details on launching HDLM, see
sections 4.2 and 5.7.2, and refer to the HDLM user documentation.
Note: To launch HDLM so that it comes up displaying a specific volume path, select
the desired volume path in the Show Properties information frame, and then select
the Dynamic Link Manager button.
If Protection Manager has been installed in the selected host. When the Device
Manager Agent and HDLM are installed on the selected host, the information frame
displays the Protection Manager button for launching the Protection Manager. For
details on launching the Protection Manager, see sections 4.2 and 5.7.3, as well as
the documentation for the Protection Manager.
3. To view detailed information for a specific volume allocated to the selected host, select
the desired LDEV to open the Detailed Information LDEV-number panel (see Figure
9.5). For details on the information displayed on this panel, see section 7.6.1.
Figure 9.4
Viewing Host Properties
185
Figure 9.5
186
Chapter 9
Detailed Information LDEV-Number Panel
9.5
Modifying Host Properties

Storage Administrator can modify (edit) existing host properties as needed. Guest and Local
Guest users cannot change the host properties, but can view them.
To modify the properties of a Device Manager host:
3. Select the Modify Properties operation in the method frame to open the Modify panel
for the selected host (see Figure 9.6).
4. Modify the host properties as needed on the Modify host-name panel. Note that you
cannot delete or add a WWN when the external port is selected.
To rename the host, edit the name in the Name field. The host name can be a
maximum of 50 bytes. You can use the following characters:
A - Z, a - z, 0 - 9, -, _, ., @
The host name may include spaces, but cannot consist only of spaces. Leading or
To delete WWNs, select the WWNs, and then select Delete. If only one WWN is set
for the host, you cannot use the Modify host-name panel to delete the WWN. To
delete the last WWN, you must delete the host (see section 9.8).
To add a WWN to the host, select Add, enter the WWN on the Add WWN panel (see
Figure 9.7), and select OK to return to the Modify host-name panel. Repeat this
step until you have entered all the desired WWNs. Enter a WWN in the following
format:
XX.XX.XX.XX.XX.XX.XX.XX
(XX: two hexadecimal digits) (You can omit periods)
5. When you are finished modifying the host attributes, check the information specified on
the Modify host-name panel. If the entered information is correct, select OK to save
your changes, or select Cancel to cancel your request to modify the host properties.
6. If you renamed the host and/or deleted WWNs, Device Manager asks you to confirm the
modify host properties operation.
If you added one or more WWNs to a host to which storage is allocated, Device Manager
displays a list of the storage (volumes) for which LUN security is set for the host (see
Figure 9.8). Select at least one checkbox for the storage for which you want to set the
LUN security by using the newly added WWN(s).
Note for HSD: For Thunder 9500V in LUN Management mode, TagmaStore USP, and
Lightning 9900V, any changes to the LUN security setting for storage belonging to a host
storage domain (HSD) will apply to all storage in the same host storage domain. If this
occurs (change LUN security for storage in an HSD), Device Manager notifies you and lists
the storage that will be affected by the specified LUN security changes. Select the OK
button to proceed to the final confirmation panel for the edit host properties operation,
or select Cancel to return to the list of LUNs in the Modify Properties panel.
187
7. After you have selected/confirmed the associated LUN security changes (if any), Device
Manager asks you for final confirmation (see Figure 9.9). Select OK to modify the host
properties as specified, or select Cancel to cancel your request to modify the host.
You are notified when the operation is complete.
188
Figure 9.6
Modify Host Properties
Figure 9.7
Modify Host Properties Adding a WWN
Chapter 9
Figure 9.8
Modify Host Properties Selecting LUN Security Changes
189
Figure 9.9
190
Chapter 9
Modify Host Properties Confirming LUN Security Changes
9.6
Updating (Refreshing) Host Information

Storage Administrator can update the host information reported by the Device Manager
Agent. Guest and Local Guest users can view the host information, but cannot update the
host properties.
When you update information about a host, Device Manager updates the information
displayed in the Last Updated, % Used, and File System fields for storage allocated to the
selected host. Device Manager also updates the copy status for the volumes that are
managed by the selected host and paired by ShadowImage, QuickShadow, and TrueCopy. For
details about the system configuration for displaying information about ShadowImage,
QuickShadow, and TrueCopy, see the HiCommand Device Manager Server Installation and
Configuration Guide (MK-91HC002).
Caution: The update host information function requires that the Device Manager Agent
version 2.3 (02-30) or later be installed on that host.
To update host information:
3. Select the host in the navigation frame for which you want to update the host
information (see Figure 9.10).
4. Select the Refresh button in the Show Properties host-name subwindow in the
information frame. The Refresh Host - Confirmation panel appears (see Figure 9.11).
Note: The View Pair Information panel also provides access to the update host
information function. Select the host, for batch management of pairs select the target
host from the Replication Management Console drop-down list, select the View Pair
button, and select the Refresh button. The Refresh Host Confirmation panel appears.
5. Check the information in the Refresh Host - Confirmation panel. If the information is
correct, select the OK button to update the host information, or select Cancel to cancel
your request to modify the host.
Caution: If a copy pair for ShadowImage or QuickShadow for Thunder 9500V is detected
during the update of host information, the Copy Type field for that copy pair is left blank. In
this case, you must update the information about the storage subsystem. For details on
updating the storage subsystem information, see section 10.1.4.
Caution: When you update the host information, the status of the copy pairs managed by
the host is updated, but the modification of the configuration definition file is not reflected.
In this case, you must update the storage subsystem information. For details on updating the
storage subsystem information, see section 10.1.4. For details on the configuration
definition file, see the Command Control Interface (CCI) System Administrator's Guide.
191
Figure 9.10 Refresh Host Refresh Button
192
Chapter 9
Figure 9.11 Refresh Host Confirmation
193
9.7
Managing Copy Pairs

Storage Administrator can manage ShadowImage, TrueCopy, and QuickShadow copy pairs.
Guest and Local Guest users do not have access to these functions.
Before creating copy pairs, see section 9.7.3, Notes on Copy Pair Operations.
The copy pair operations include:
Creating copy pairs (see section 9.7.1)
Modifying copy pairs (see section 9.7.2)
Deleting copy pairs (see section 9.7.4)
Note: See section 4.4 for important information on ShadowImage, TrueCopy, and
QuickShadow requirements (e.g., command device with LUN security, CCI installed on the
host, P-VOLs, S-VOLs, MCU-RCU paths).
9.7.1
Creating Copy Pairs

WARNING: The create copy pair operation is destructive. The data on the LDEV that will
become an S-VOL will be lost. The user is responsible for backing up the data before
performing this operation.
Storage Administrator can create copy pairs. Guest and Local Guest users do not have access
to this function.
When a copy pair is created, the P-VOL and S-VOL status is changed to Copying during the
initial copy operation, and then to Pair when the initial copy is complete. For details on
creating pairs, see the ShadowImage, TrueCopy, or QuickShadow manual for the subsystem.
Caution for AIX: For hosts on the AIX platform, the operating system stores disk
management information on the volumes. When you allocate a P-VOL and its S-VOL(s) to the
same host, disk management information that the operating system stored in the volumes is
copied from the P-VOL to the S-VOL. This may prevent the operating system from correctly
identifying these volumes. If this happens, execute the recreatevg command, or execute
the dlmrecreatevg command if HDLM is in use. For details about these commands, see the
Hitachi Dynamic Link Manager User's Guide (for AIX).
194
Chapter 9
To create one or more copy pairs:

1. Log in to Device Manager as a System Administrator, Storage Administrator, Local System
Administrator, or Local Storage Administrator.
WARNING: The create pair operation is destructive. Make sure that the LDEVs that will
become S-VOLs are no longer in use and that the data has been backed up.
3. In the navigation frame select the host that contains the P-VOL(s) of the copy pair(s)
that you want to create (refer to Figure 9.4).
4. In the information frame, select the checkbox for each volume that will become the
P-VOL of a new copy pair to be created (see Figure 9.12). You can only create pairs of
one copy type at a time (TrueCopy Sync, TrueCopy Async, ShadowImage, or
QuickShadow), so make sure to select P-VOLs for one copy type only.
5. Select Create Pair to open the Create Pair wizard (see Figure 9.13). If copy pairs are
managed in a batch management configuration, select the host that manages copy pairs
from the Replication Management Console drop-down list, and then select the Create
Pair button to open the Create Pair wizard.
If the Create Pair button is not enabled, one or more of the copy pair requirements for
the selected host and/or P-VOL(s) have not been met (see section 4.4).
6. Choose Pair(s) Step. The Choose Pair(s) panel (see Figure 9.13) displays the selected PVOL(s) in the P-VOL box and allows you to choose the desired copy type and S-VOL(s) for
the copy pair(s) to be created.
On the Choose Pair(s) panel, choose the copy type and S-VOL for each pair as follows:
(a) In the P-VOL box, select the P-VOL of the pair to be created.
Note: For the TagmaStore USP, Lightning 9900V and Lightning 9900, if you select a
ShadowImage-controlled S-VOL to be the P-VOL of a new TrueCopy-controlled
volume pair, the status of the ShadowImage-controlled pair must be Split.
(b) In the Copy Type list box, select the desired copy type for all pairs that you are
creating now. You can only create pairs of one copy type at a time: TrueCopy Sync,
TrueCopy Async, ShadowImage, or QuickShadow. After you have added one pair to
the Copy Pairs box, the Copy Type box will only display the type of that pair.
(c) In the S-VOL field, select the Select button to open the Select S-VOL panel of the
Create Pair wizard.
(d) In the Host (WWN) list box, select the host for the S-VOL of the pair to be created,
and then select the List LDEV button. The Host list box displays only the eligible
hosts (e.g., Device Manager Agent and CCI installed, command device with LUN
security set for that host).
(e) In the LDEV List box, select the LDEV that you want to set as the S-VOL for the
selected P-VOL, and then select OK (see Figure 9.14). The LDEV List box displays
only the eligible LDEVs.
195
(f) Make sure that the S-VOL field contains the selected LDEV, and select the Create
button to add the selected S-VOL to the selected P-VOL. The Copy Pairs P-VOLs
and S-VOLs box now displays the pair to be added.
To delete a pair from the Copy Pairs - P-VOLs and S-VOLs field, select the check
box for the pair that you want to delete, and then select the Remove button.
(g) Repeat steps (a)(f) until you have selected all the copy pairs to be created, and
select Next to go to the next step of the Create Pair wizard.
7. Define Pair(s) Step. The Define Pair(s) panel (see Figure 9.15) displays the pair(s) that
you have chosen and allows you to define the parameters for each pair.
The View Pair Information box provides access to the detailed host pair configuration
information to assist you in defining the copy pair(s). To check the existing pair
information, select a host, and then select the View button to open the View Pair
Information panel for the selected host (see Figure 9.16).
When pair management is performed for each host: The target host for creating a
copy pair, or the host to which the LDEV that was selected as the S-VOL has been
allocated, is displayed.
When pair management is performed by central management: The host selected

from the Replication Management Console drop-down list is displayed.
On the Define Pair(s) panel, define the parameters for the copy pairs as follows. After
defining the parameters for all copy pairs, select Finish.
Group. Select the desired copy group for all copy pairs being created, or create a new
group if desired. For details on copy groups, see the ShadowImage or TrueCopy manual
for the storage subsystem.
The following combinations of copy pairs cannot be registered to the same copy group or
to an existing copy group.
The LDEVs making up the copy pair are allocated to different hosts.
Copy pairs of level 1 and level 2 when using ShadowImage cascade
Copy pairs of different copy types
TagmaStore USP copy pairs, Lightning 9900V/9900 copy pairs, and Thunder
9500V/9200 copy pairs
Copy pairs of different fence levels
To create a new copy group, select the New button, and then use the New Copy Group
panel (see Figure 9.17) to specify the group name, P-VOL, S-VOL, CCI (HORCM) instance
name for each host, and port number for the new group.
Pair Name. Enter the desired name for the pair. The name must not be longer than 31
characters. You can use the following characters to specify the name:
A - Z, a - z, 0 - 9, -, _, ., @
If the name is omitted, the following name is automatically set:
HCMD-CPxxxx
(xxxx: hexadecimal)
Caution: You cannot use a hyphen (-) at the beginning of the pair name.
196
Chapter 9
Fence Level (TrueCopy Sync only). Select the desired fence level (Never, Data, or
Status). For details on fence level, see the TrueCopy manual for the subsystem.
Copy Pace (ShadowImage and TrueCopy only). Select the desired pace for the initial
copy operation: slower, medium, or faster for USP/9900V/9900; 1-15 for 9500V/9200.
Caution: For Thunder 9500V and Thunder 9200, specify 15 for Copy Pace. Specifying
a value other than 15 causes a warning message to appear. Contact the System
Administrator if you want to modify this value.
The faster the copy pace (e.g., 15 tracks or fast), the shorter the period of time
required for copying. However, a fast copy pace may affect the I/O performance of the
storage subsystem (only during the initial copy operation).
the requested create pair operation(s) and asks you to confirm the requested
operation(s). Review the operation(s) carefully, and select OK to confirm the
operation(s), or select Cancel to cancel your request. If you need to make any changes,
select Back to return to the previous panel(s).
9. HiCommand Device Manager displays the new S-VOL(s) and warns you that the data on
these volumes will be lost (see Figure 9.19). Select Confirm to start the requested
create pair operation(s), or select Cancel to cancel your request to create the pair(s).
You are notified when the create copy pair operation(s) is/are complete.
197
Figure 9.12 Create Pair Selecting the P-VOLs
198
Chapter 9
Figure 9.13 Create Pair Choose Pair(s) Step
Figure 9.14 Create Pair Selecting the S-VOL(s)
199
Figure 9.15 Create Pair Define Pair(s) Step
Figure 9.16 Create Pair View Pair Information

Note: The displayed host is the host that manages copy pairs. If pair management is
performed by a central management method, the host that manages copy pairs centrally is
displayed.
200
Chapter 9
Figure 9.17 Create Pair Defining a New Copy Group
Figure 9.18 Create Pair Confirmation Step
201
Figure 9.19 Create Pair Warning of Data Loss
202
Chapter 9
9.7.2
Modifying Copy Pairs

Storage Administrator can modify TrueCopy and ShadowImage copy pairs. Guest and Local
Guest users do not have access to this function.
Table 9.1 shows the operations that you can perform when you modify a copy pair. For
resync and restore operations you can specify the copy pace. For details on splitting,
resynchronizing, and restoring copy pairs, see the ShadowImage, TrueCopy, or QuickShadow
manual for the subsystem (e.g., the Hitachi Lightning 9900TM V ShadowImage Users Guide).
Note: See section 4.4 for important information on copy pair requirements (e.g., P-VOLs,
S-VOLs, SP-VOLs, etc.).
Table 9.1
Requirements for Modify Pair Operations
Target of Operation
Operations that Can Be Performed
Copy group
If one or more copy pairs in the group are in the Suspend or Error In LUSE status:
For TrueCopy Sync and TrueCopy Async, select Resync.
For ShadowImage, select Resync or Restore.
If all copy pairs in the group are in the Split status:
For TrueCopy Sync and TrueCopy Async, select Resync.
For ShadowImage and QuickShadow, select Resync or Restore.
If all copy pairs in the group are in the Pair, Copying, or Reverse-Copying status,
select Split.
Other than above:
For TrueCopySync and TrueCopy Async, select Split or Resync.
For ShadowImage and QuickShadow, select Split, Resync, or Restore.
Copy pair
QuickShadow P-VOL
and TrueCopy cascade
pairs (Thunder 9500V
only)
If the copy pair is in the Pair, Copying, or Suspended status, select Split or
Resync.
Other pairs
If the copy pair is in the Split or Suspended status:
In other cases, select Split, Resync, or Restore.
For TrueCopy Sync and Async, select Resync.

For ShadowImage and QuickShadow, select Resync or Restore.
If the copy pair is in Error In LUSE status (USP/9900V/9900 TrueCopy Sync/Async
only), select Resync.
Other than above
For TrueCopySync and TrueCopy Async, select Split or Resync.
For ShadowImage and QuickShadow, select Split, Resync, or Restore.
Caution: When using QuickShadow, the Restore operation cannot be performed on the copy
pair that shares the same P-VOL. The Restore operation cannot be selected on the copy
group that contains multiple copy pairs that share the same P-VOL.
Note: If you want to change the status of a USP/9900V/9900 ShadowImage copy pair whose
S-VOL is a P-VOL for TrueCopy, the status of the TrueCopy pair must be Split.
203
Table 9.2 lists the requirements for performing operations on ShadowImage cascaded pairs
(USP/9900V/9900 only). The first cascade level is called L1, and the second level is called
L2. Example of cascaded pairs for LDEV1, LDEV2, and LDEV 3: LDEV1 and LDEV2 is the pair
for L1, and LDEV2 and LDEV3 is the pair for L2. LDEV2 is an S-VOL for L1 and a P-VOL for L2.
Table 9.2
Requirements for Operations on ShadowImage Cascade Pairs
Operation
Required Status
Split operation for L1 pair
L2 pair status must be Pair, Copying, Split, or Suspended.
Split operation for L2 pair
L1 pair status must be Split.
Resync operation for L1 pair
Resync operation for L2 pair
L1 pair status must be Pair, Copying, Reverse-Copying, Split, or Suspended.
Restore operation for L1 pair
Restore operation for L2 pair
Not allowed.
To modify one or more copy pairs:

3. In the navigation frame select the host that manages the copy pair(s) that you want to
modify (see Figure 9.20). If pair management is performed by the central management
method, select the desired host under Hosts.
4. Select Modify Pair to open the Modify Pair wizard (see Figure 9.21). If copy pairs are
managed in a batch management configuration, select the host that manages copy pairs
from the Replication Management Console drop-down list, and then select the Modify
Pair button to open the Modify Pair wizard.
5. Select Modify Pair(s) Step. The Select Modify Pair(s) panel (see Figure 9.21) allows you
to select the copy group(s) and/or copy pair(s) for which you want to modify the status.
When you are finished selecting copy groups/pairs, select Next.
Note: You can only perform one type of operation at a time (split, resync, or restore), so
make sure to select copy groups/pairs for one operation type only.
6. Modify Pair(s) Step. The Modify Pair(s) panel (see Figure 9.22) allows you to select the
desired Operation (split, resync, or restore) and Copy Pace (for resync or restore) for
the selected copy group(s)/pair(s). When you are finished selecting the operation and
copy pace for the pair(s), select Finish.
Operation: Split, Resync, or Restore. For requirements on performing the Split, Resync,
and Restore operations, refer to Table 9.1. For requirements for performing Split,
Resync, and Restore operations for ShadowImage cascade pairs, refer to Table 9.2.
Copy Pace: Select the desired pace for the resync or restore operation (ShadowImage
and TrueCopy only): slower, medium, or faster for USP/9900V/9900; 1-15 for
9500V/9200.
204
Chapter 9
Caution: For Thunder 9500V and Thunder 9200, specify 15 for Copy Pace. Specifying
a value other than 15 causes a warning message to appear. Contact the System
Administrator if you want to modify this value.
Note: If you want to change the status of a USP/9900V/9900 ShadowImage copy pair
whose S-VOL is a P-VOL for TrueCopy, the status of the TrueCopy pair must be Split.
Note: The Copy Pace value does not appear for a copy pair that was created using other
management tools (e.g., Storage Navigator, SVP) or that was created by another Device
Manager Server. If you use any other management tool to modify the Copy Pace value,
the modified value will not be applied.
the requested modify pair operation(s) and asks you to confirm the operation(s). If you
selected a copy group, ALL PAIRS appears for Pair.
Review the operation(s) carefully, and select Confirm to confirm the operation(s), or
select Cancel to cancel your request. If you need to make any changes, select Back to
return to the previous panel(s).
8. If you selected the split operation, Device Manager warns you that the data on the S-VOL
may not be complete if you split a pair during I/O processing on the P-VOL (see Figure
9.24). Read the warning carefully, and select OK if there is no problem, or select Cancel
to cancel your request to split the pair(s).
You are notified when the modify copy pair operation(s) is/are complete.
205
Figure 9.20 Modify Pair Selecting the Host
206
Chapter 9
Figure 9.21 Modify Pair Select Modify Pair(s) Step

displayed.
Figure 9.22 Modify Pair(s) Step

207
Figure 9.23 Modify Pair Summary of Changes Step
Figure 9.24 Modify Pair Warning of I/O Activity on P-VOL
208
Chapter 9
9.7.3
Notes on Copy Pair Operations

Table 9.3
Items to Consider before Creating Copy Pairs
Item
Description
Existing copy pair
A copy pair can be created by using Remote Console, Storage Navigator, SVP, or the
CCI library. However, there is no HORCM configuration file created for CCI control for
the copy pair created by the above management tools. Therefore, the status of the
copy pair cannot be changed or deleted by using the HiCommand Device Manager
Server. To change or delete the status of a copy pair by using the HiCommand
Device Manager Server, delete the copy pair by using the appropriate management
tool, and then create the copy pair again by using the HiCommand Device Manager
Server.
HORCM configuration file

(horcm.conf)
When using Windows, store the HORCMconfiguration file in the system directory.
When using Solaris, HP-UX, AIX, or Linux, store the HORCM configuration file in
the /etc directory.
If the environment variable is specified and the HORCM configuration file is stored in a
location other than the one specified above, the HORCM configuration file cannot be
managed by the HiCommand Device Manager Server.
The Windows system directory can be checked by using the echo "%SystemRoot%"
command.
It might take some time to add a storage subsystem or refresh operations when both
of the following conditions are satisfied:
Device Manager Agent and CCI are installed on the host that the HiCommand
Device Manager Server recognizes.
There is an unused HORCM configuration file on the host, or a lot of unused copy
pairs are defined in the HORCM configuration file.
In such a case, disable the unused HORCM configuration file or the unused copy
pair definitions in the HORCM configuration file, by using the following methods:
Disabling an unused HORCM configuration file

Set the instance number of the unused HORCM configuration file to the Device
Manager Agent's property server.agent.rm.exclusion.instance, stop Device
Manager Agent, and then restart Device Manager Agent.
Disabling an unused copy pair definitions in the HORCM configuration file

Delete the unused copy pair definition in the HORCM configuration file, or make
the definition a comment line.
Central management method
When a single host centrally manages the creation, status change, and deletion of
copy pairs, disable the command device security functionality on the host that
manages the copy pairs.
If the command device security functionality is enabled, an LU not recognized by the
host cannot be managed by the copy pair.
Medium volume
Copy pair information cannot be acquired when the same port is assigned to the opensystem volume and the medium volume. If the storage subsystem using the copy pair
functionality is using the medium volume, prepare a dedicated port for the medium
volume in order to separate the port for the open-system volume.
209
Table 9.4
Notes on Copy Pair Operations (continued on the next page)
Item
Description
Creating copy pair
When a ShadowImage and TrueCopy copy pair is created for one LU, or when a
ShadowImage cascaded copy pair is defined, use different combinations of group
names and pair names for each copy pair.
When creating a new copy pair, make sure that the pair definition for that LU has not
already been defined.
If there is an invalid pair definition, delete the corresponding copy pair definition from
the HORCM configuration file as necessary.
Displaying a copy pair
The copy pace value is not displayed for copy pairs created by other management
tools such as Storage Navigator and SVP, or copy pairs created by another
HiCommand Device Manager Server. Also, when copy pace values are changed by
other management tools, the changed values do not apply.
Cascaded copy pair
When using Lightning 9900 or the Lightning 9900V series, the following conditions
must be satisfied to operate the cascaded copy pair:
The first tier of the cascade is called L1, and the second is L2.
For example, when pairs are cascaded in the order LDEV1, LDEV2, and LDEV3, the
L1 pair is LDEV1 and LDEV2, and the L2 pair is LDEV2 and LDEV3.
When performing Split operations for the L1 pair:

The L2 pair status must be one of the following: Pair, Copying, Split, or Suspended
When performing Split operations for the L2 pair:

The L1 pair status must be Split.
When performing Resync operations for the L1 pair:

When performing Resync operations for the L2 pair:

The L1 pair status must be one of the following: Pair, Copying, Reverse-Copying,
Split, or Suspended
When performing Restore operations for the L1 pair:

LDEV with multiple paths assigned
When a copy pair is created using an LDEV with multiple paths assigned, the
HiCommand Device Manager Server automatically determines the port for the pair
volume specified in the HORCM configuration file. The HiCommand Device
Manager Server selects the ports in alphabetical ascending order of their names.
For example, when the LDEV where the paths via CL1-A and CL2-A are assigned is
selected to create a copy pair, CL1-A is specified as the HORCM configuration file. If
the path via CL1-A is deleted, this copy pair will become inoperable. In such a case,
the HORCM configuration file needs to be edited directly.
For details on editing the HORCM configuration file, see the Command Control
Interface (CCI) User and Reference Guide.
210
Chapter 9
Table 9.4
Notes on Copy Pair Operations (continued)
Item
Description
Error code 7774
Error code 7774 occurs when Device Manager Agent fails to create a HORCM
configuration file, start the HORCM instance, or execute the pair creation or status
change command.
In this case, the error messages output by Web Client and the causes are as follows:
(a) This ConfigFile could not be modified.
Cause 1: The HORCM configuration file could not be created because Device
Manager Agent could not recognize the LU specified for the copy pair.
Action 1: Update the database by refreshing the storage subsystem or the host.
Cause 2: The HORCM configuration file could not be created because Device
Manager Agent could not recognize the command device.
Action 2: Assign the command device to the host that is running Device Manager
Agent, and then refresh the host.
(b) This HORCM instance could not be started (see Note 1).
Detailed message: starting HORCM inst instance-number.
HORCM inst instance-number has failed to start.
Cause 1: The specified instance port-number is being used by another application.
Action 1: Check the usage status of the port numbers by executing the netstat
command, and then specify an unused port number.
Cause 2: Disk space is insufficient. Each instance requires about 100 KB of free disk
space.
Action 2: Check the free disk space, and then make more free disk space by deleting
any unnecessary files.
Could not create pair pair-name:group-name (see Note 2).
Detailed message: paircreate: [EX_CMDIOE] Control command I/O error Refer to the
command log (/HORCM/log123/horcc_japan.log) for details.
Cause 1: The maximum number of copy pairs that can be created on the device has
been reached. More than 1000 pairs can be created for Lightning 9900 and the
Lightning 9900V series, but only 31 for Thunder 9200 and the Thunder 9500V series.
Action 1: Delete any unnecessary copy pairs. Check the number of copy pairs by
using SVP or Storage Navigator.
Cause 2: When using TrueCopy, the remote path was blocked.
Action 2: Check the remote path status by using SVP, Storage Navigator, or DAMP
(for Web), and then release the blockage.
(d) The ConfigFile of this instance number does not exist.
Cause 1: An inconsistency occurred between the host status and the database of the
Action 1: Update the database by refreshing the storage subsystem and executing
HiScan on the target host. If the same error still occurs, restart Device Manager
Agent.
HiScan command
When the HiScan command is executed on a host that recognizes an LU which the
HiCommand Device Manager Server is using to create or delete a copy pair, the
pair status displayed in Web Client might be incorrect. In such a case, refresh the
storage subsystem from Web Client. However, the copy pace display is not restored. If
the copy pace display is needed, reset the copy pace by changing the copy pair
status.
211
Note 1: An error might occur when attempting to create a copy pair by using an LU that
satisfies the following conditions:
A path using CL1-A (for the Lightning 9900V or the Lightning 9900 series) or CTL0-A (for
the Thunder 9500V or the Thunder 9200 series) was assigned to the LU, and a path that
used LUN0 was also assigned to the LU.
The host used for creating the copy pair recognizes the above path. In such a case,
assign a different port to that of the above path or use an LUN other than LUN0, and
then re-create the copy pair.
Note 2: The [EX_xxxxx] displayed in the detailed message is a CCI error message. For details
on CCI error messages, see the Command Control Interface (CCI) User and Reference Guide.
If the situation does not improve, even after performing the above operations, contact the
Support Center.
212
Chapter 9
Table 9.5
Notes on Managing the Host
Item
Description
Shutting down the host or stopping

Device Manager Agent
When operating a copy pair, shutting down the host that recognizes that copy pair, or
stopping Device Manager Agent, will cause the copy pair operation to time out
within 15 minutes. Make sure that the host or Device Manager Agent restarts, and
then perform the copy pair operation again.
HORCM instance
The HORCM instance that was started by Device Manager Agent in Windows
cannot be fully operated, including finishing.
To avoid this, the Device Manager Agent service (hdvmagt) permissions must be
changed from LocalSystem to Administrator. When you want to operate the HORCM
instance, change the hdvmagt service permissions as shown above.
Changing the host's IP address or

host name
If a copy pair is created when ipaddress is specified for

server.horcmconfigfile.hostname in the server.properties file, changing the host's IP
address will make the copy pair inoperable.
If a copy pair is created when hostname is specified for
server.horcmconfigfile.hostname in the server.properties file, changing the host name
will make the copy pair inoperable.
In such a case, refresh the storage subsystem by following this procedure:
1. Modify the configuration definition file on the applicable host
2. Restart Device Manager Agent on the applicable host
3. Modify the HORCM configuration file on the host of the copy pair source against the
applicable host of the copy pair destination.
AIX host
For AIX hosts, the OS stores disk management information on the volume. Therefore,
when P-VOL and S-VOL are assigned to the same host, the disk management
information stored on the volume is copied from P-VOL to S-VOL, and the OS might
not be able to recognize the volume as normal. In such a case, execute the recreatevg
command to re-create the volume group.
When using Hitachi Dynamic Link Manager, execute the dlmrecreatevg command to
re-create the volume group.
For details on these commands, see the AIX system documentation or the manual
Hitachi Dynamic Link Manager (AIX).
Refreshing the storage subsystem
Performing discovery or refresh operations for the storage subsystem will update
information about the HORCM configuration file and information about copy pairs
recognized by each host. If the system cannot communicate normally with the host
during the operation, the information about the copy pair recognized by that host and
information about the HORCM configuration file might be lost. In such a case, the
Modify Pair button in the host management window is not displayed and the
information about the copy pair recognized by the host is not displayed.
Thunder 9500 V
If the copy pair functionality (for example, the Create Pair button) on Thunder 9500V is
not displayed, perform the following operations:
Note that CCI must be installed on the host managed by HiCommand Device
Manager.
Specify HiCommand Device Manager Agent in the host settings of the

server.properties file.
Check the switch partition.
Make sure that the command device is not mounted.
Restart Device Manager Agent and execute the hiscan command on the
Update the storage subsystem and execute LUN Scan.
Read the horcm.cont.txt file under the c:\HORCM\etc\horcm.conf directory on the

server where CCI is installed (see the MU# field description).
213
9.7.3.1
Using CCI or Protection Manager to Manage Existing Copy Pairs

If a copy pair is already managed by CCI, the copy pair can be managed by DeviceManager
after Device Manager is installed. Similarly, if the copy pair is managed by Protection
Manager, the copy pair can be managed by Device Manager after Device Manager is
installed.
Note: When Device Manager is installed, the Device Manager Agent property must be
configured if the installation drive of CCI in Windows is different from the installation drive
of Device Manager Agent.
When you directly use CCI or exclude the copy pair managed by Protection Manager from
Device Manager operations, the following action is required:
Check the HORCM instance number of CCI managing the copy pair.
In the following property in the Device Manager Agent property file, enter the HORCM
instance that you want to exclude from Device Manager operations. Separate HORCM
instances by commas if you want to enter multiple HORCM instances.
Property file name: server.properties
Property name: server.agent.rm.exclusion.instance
Example:
server.agent.rm.exclusion.instance=0, 1, 2
9.7.3.2
Restart the Device Manager Agent service (daemon)
Using Web Client to Create a Configuration Definition File for CCI

Device Manager Web Client allows you to create a configuration definition file. This
configuration definition file is used when CCI is used to create copy pairs.
Note: This function is provided for system administrators who use CCI to manage copy pairs.
Caution:
214
You cannot use the configuration definition file created by this function to create a
copy pair by using Device Manager.
You cannot use Device Manager to delete an invalid configuration file if the file
was created by this function. To delete or edit such a configuration file, execute the
appropriate CCI command from a host.
An invalid configuration file or a configuration file that is not used for operating
copy pairs may affect system performance - for example, when discovering a
subsystem or refreshing information. To delete such a configuration file, execute the
appropriate CCI command from a host.
Requirements for the function for creating the configuration definition file:
The storage subsystem and host satisfy the requirements described in this manual.
The version of Device Manager agent installed on the host is 03-01 or later.
Chapter 9
Using the function for creating the configuration definition file:

To create a configuration definition file:
1. Stop the HiCommand Single Sign On Service.
2. Set the value of client.outputhorcmfunction.enabled in the client.properties file to true.
3. Start the HiCommand Single Sign On Service.
4. Start the operation for creating a copy pair.
Caution:
When managing pairs by each host:
Device Manager Agent 03-01 or later must be installed on the host to be used.
When managing pairs by central management:
Device Manager Agent 03-01 or later must be installed on the host that centrally
manages the pairs.
Perform the operation in the same manner as when creating a copy pair to display the Step:
Summary Of Changes dialog box.
Note: In the Step: Define Pair(s) dialog box, you need not specify the fence level and copy
pace. Even if you specify these items, they are not applied in the configuration definition
file.
In the Step: Summary Of Changes dialog box, click Cancel (Output HORCM) to stop creating a
copy pair, and then start creating the configuration definition file.
When creation of the configuration definition file finishes, a dialog box appears notifying you
of the finish. Check the display, and then click the Close button.
In the View Pair Information dialog box, you can view the HORCM instance number, pair
group name, and pair name of the created configuration definition file.
Caution:
For a copy pair of Shadow Image or QuickShadow, Device Manager sets the MU number in
the configuration definition file to 0. (Note that, for TrueCopy, the MU number is not set
because this number is not necessary.) When you use a configuration definition file created
by Device Manager to create a copy pair, make sure that you change this value to an
appropriate value.
9.7.4
Deleting Copy Pairs

Storage Administrator can delete TrueCopy and ShadowImage copy pairs. Guest and Local
Guest users do not have access to this function.
215
When a copy pair is deleted, the P-VOL and S-VOL are changed to Simplex status, and the
storage subsystem stops replicating the P-VOL updates on the S-VOL. For details on deleting
copy pairs, see the TrueCopy, ShadowImage, or QuickShadow manual for the subsystem.
Note: See section 4.4 for important information on copy pair requirements (e.g., P-VOLs,
S-VOLs, SP-VOLs, etc.).
To delete one or more copy pairs:
3. In the navigation frame select the host that manages the copy pair(s) that you want to
delete (refer to Figure 9.20). If pair management is performed by the central
management method, select the desired host under Hosts.
4. Select the Delete Pair button to open the Delete Pair wizard (see Figure 9.25). If copy
pairs are managed in a batch management configuration, select the host that manages
copy pairs from the Replication Management Console drop-down list, and then select
the Delete Pair button to open the Delete Pair wizard.
5. Select Delete Pair(s) Step. The Select Delete Pair(s) panel (see Figure 9.25) allows you
to select the copy group(s) and/or copy pair(s) that you want to delete. When you are
finished selecting groups/pairs, select Next.
the requested delete pair operation(s) and asks you to confirm the operation(s). If you
selected a copy group, ALL PAIRS appears for Pair.
Review the operation(s) carefully, and select Confirm to confirm the operation(s), or
select Cancel to cancel your request. If you need to make any changes, select Back to
return to the previous panel(s).
7. Device Manager warns you that the data on the S-VOL may not be complete if you delete
a pair during I/O processing on the P-VOL (see Figure 9.24). Read the warning carefully,
and select OK if there is no problem, or select Cancel to cancel your request to delete
the pair(s).
You are notified when the delete copy pair operation(s) is/are complete.
216
Chapter 9
Figure 9.25 Delete Pair Select Delete Pair(s) Step

displayed.
217
Figure 9.26 Delete Pair Confirmation (Summary of Changes Step)

displayed.
218
Chapter 9
9.8
Removing a Host
Storage Administrator can remove (delete) an existing HiCommand Device Manager host, as
long as it is not securing any LUNs. Guest and Local Guest users do not have access to this
function. Note that you cannot delete the external port.
If any WWN(s) of the host you want to remove are set for LUN security for any storage group,
you must delete the WWN from the storage group before you can remove the host.
To remove a host from the HiCommand Device Manager system:
3. Select the host to be removed, and then select the Remove Host operation in the
method frame.
4. HiCommand Device Manager displays the LUN security changes associated with the
remove host operation (if any) (see Figure 9.27) and asks you to confirm the operation.
Select the OK button to remove the host, or select Cancel to cancel your request to
remove the host.
Figure 9.27 Remove Host Confirmation
219
220
Chapter 9
Chapter 10 Performing Subsystem Operations

This chapter describes HiCommand Device Manager subsystem operations in the following
sections:
Subsystem operations (see section 10.1):
Viewing the list of subsystems (see section 10.1.1)
Adding a storage subsystem (see section 10.1.2)
Viewing and editing storage subsystem properties (see section 10.1.3)
Performing a Refresh operation (see section 10.1.4)
Handling a change to the IP address of a subsystem (see section 10.1.5)
Deleting a storage subsystem (see section 10.1.6)
Physical View operations (see section 10.2)
Viewing detailed information for Lightning 9900V (see section 10.2.1)
Viewing detailed information for Lightning 9900 (see section 10.2.3)
Viewing detailed information for Thunder 9500V (see section 10.2.4)
Viewing detailed information for Thunder 9200 (see section 10.2.5)
Viewing detailed information for T3 (see section 10.2.6)
Viewing detailed LDEV information (see section 10.2.7)
Port operations (see section 10.3):
Configuring the ports (9900V, 9900, 9500V, and 9200) (see section 10.3.1)
Managing LUN groups (9900 only) (see section 10.3.2)
Managing WWN groups (9900 only) (see section 10.3.3)
Configuring the fibre-channel adapters (9900V and 9900) (see section 10.3.4)
Array group operations (see section 10.4):
Creating an array group on the 9500V and 9200 (see section 10.4.1)
Creating an array group (with or without spare drive) on the T3 (see section 10.4.2)
Configuring spare drives on the 9500V and 9200 (see section 10.4.4)
Deleting an array group (9500V, 9200, and T3) (see section 10.4.3)
LDEV operations (see section 10.5):
Allocating storage (see section 10.5.1)
Unallocating storage (see section 10.5.2)
Creating an LDEV (see section 10.5.3)
Deleting an LDEV (see section 10.5.4)
Setting a command device (see section 10.5.5)

221
10.1 Subsystem Operations

System Administrators and Storage Administrators can add storage subsystems to Device
Manager, delete storage subsystems from Device Manager, and edit the attributes of storage
subsystems. Guests can only view information about storage subsystems. Local System
Administrators, Local Storage Administrators, and Local Guests cannot manipulate storage
subsystems.
The HiCommand Device Manager subsystem operations include:
Viewing the list of storage subsystems (see section 10.1.1)
Adding a storage subsystem (see section 10.1.2)
Viewing and editing storage subsystem properties (see section 10.1.3)
Performing a Refresh operation (see section 10.1.4)
Handling a change to the IP address of a subsystem (see section 10.1.5)
Deleting a storage subsystem (see section 10.1.6)
10.1.1 Viewing the List of Storage Subsystems

The Subsystems object in the Device Manager Web Client navigation frame (see Figure 10.1)
displays a list of the storage subsystems being managed by Device Manager and provides
access to the storage subsystem operations.
When the Subsystems object is selected in the navigation frame, the method frame displays
the Add Subsystem operation (see section 10.1.2), and the information frame displays the
list of subsystems. You can view the information about a storage subsystem by selecting the
link for the subsystem name in this list.
When a subsystem is selected in the navigation frame, the method frame displays the
following operations:
Modify Properties (see section 10.1.3)
Refresh (see section 10.1.4)
Remove Subsystem (see section 10.1.6)
Show Properties (see section 10.1.3)
When a subsystem is selected in the navigation frame, the Show Properties subwindow in
the information frame displays the properties of the subsystem (see section 10.1.3). The
Physical View button opens the Physical View for the selected subsystem (see section 10.2).
222
Figure 10.1 Subsystems

Note: The total size (Configured Capacity) that is displayed is not the total size of the
physical disk. It is the total available memory, which means the total of the sizes of all
logical devices on the machine. Thus, this total size is increased or decreased by creating or
deleting logical devices.
223
10.1.2 Adding a Storage Subsystem

The System Administrator and Storage Administrator can add a subsystem to HiCommand
Device Manager. Guests, Local System Administrators, Local Storage Administrators, and
Local Guests do not have access to this function.
When you add a subsystem, HiCommand Device Manager locates the subsystem, performs
an initial configuration check, creates a logical group for the subsystem in the All Storage/
My Storage group, creates the Allocated and Unallocated storage groups under the
subsystem, and lists the LUNs in the Allocated group (each LDEV/LU on a separate line with
path(s) listed) and the LDEVs/LUs without paths in the Unallocated group (each LDEV/LU on
a separate line).
Note: The add subsystem operation is complex and may take a while.
Note: If you are using TagmaStore USP Universal Volume Manager, note the following
points when you configure an external subsystem under Device Manager:
If an external subsystem is added to Device Manager, but TagmaStore USP is not added,
Device Manager will be unable to recognize that the external subsystem is connected as
an external system. Ensure that when you add an external subsystem to Device Manager,
you also add TagmaStore USP.
If you add the external subsystem to Device Manager after adding TagmaStore USP, you
must perform a refresh operation on TagmaStore USP. This enables Device Manager to
acquire information to recognize the external subsystem.
To add a storage subsystem to HiCommand Device Manager:

1. Log in to Device Manager as a System Administrator or Storage Administrator.
2. Make sure that all hosts associated with the new subsystem have already been added to
Device Manager. If not, add each host by either installing/running the host agent, or by
entering the host name and its WWNs using the Web Client (see section 9.3) or CLI.
Note: Before continuing, please confirm that the hosts are shown under Hosts.
3. Select the Subsystems object in the navigation frame (refer to Figure 10.1), and then
select the Add Subsystem operation in the method frame.
4. On the Add Subsystem panel, select the type of subsystem to be added (e.g., HDS9900V)
(see Figure 10.2). The displayed information depends on the selected type of storage
subsystem.
5. Enter the IP address(es) or host name of the subsystem. You can input a maximum of 50
bytes using the following characters:
A - Z, a - z, 0 - 9, -, _, ., @
Note: The host name may include spaces, but cannot consist only of spaces. Leading or
trailing spaces are discarded. Also, if an IP address conversion server (e.g., firewall)
exists between the Device Manager Server and the subsystem, specify the IP address that
is accessible from the Device Manager Server.
224
6. Enter the other required information on the Add Subsystem panel:
For TagmaStore USP and 9900V, enter the user ID and password (for Storage
Navigator).
For the 9900, enter the SNMP community name (e.g., public) for the subsystem. You
can input a maximum of 15 bytes, using the following characters:
A - Z, a - z, 0 - 9
For the 9500V and 9200 subsystem, enter the user ID and password if the Password
Protection feature is enabled on the subsystem.
For the T3, enter the user name and password.

Note: For T3 the user ID is usually root, and the default password must be
changed, so make sure to enter the correct password. The T3 is predefined to not
prompt a guest user for a password. Do not specify guest for the user ID for a T3
that is managed by Device Manager. Guest users for the T3 have only view
permission, so specifying guest for the user ID disables the setting of the T3 in
Device Manager.
For the user ID and password, you can use the following characters:
A - Z, a - z, 0 - 9, -, _, ., @
A user ID or password may include spaces, but cannot consist only of spaces. Leading
or trailing spaces are discarded.
The user ID can be a maximum of 25 bytes, and the password a maximum of 40
bytes.
225
7. When you are finished entering the information for the subsystem to be added, select
OK to add the subsystem. HiCommand Device Manager locates the subsystem on the
network and performs the subsystem discovery. While this operation is in process, you
can perform other operations (including discovering other subsystems).
You are notified when the add subsystem operation is complete. The name of the new
subsystem is in the following format:
<storage-subsystem-type>@<storage-subsystem-IP-address>
(e.g., HDS9980V@172.16.45.1).
8. Before performing a LUN Scan operation on the new subsystem, change the name of the
storage subsystem, if desired, using the Modify Properties panel (see section 10.1.3). If
you perform a LUN Scan, then change the name, and then perform another LUN Scan,
you will have two groups for the same subsystem in the LUN Scan logical group.
9. After changing the subsystem name, you can perform a LUN Scan operation on the newly
discovered subsystem (see section 8.3). When a subsystem is added for the first time, its
existing LUNs do not belong to any (user-defined) group in Device Manager. The LUN
Scan creates a hierarchy of logical groups and storage groups organized by port to
contain all LUNs on the subsystem. When you execute LUN Scan, Device Manager also
registers all hosts with a WWN related to the LUNs. The attributes of the hosts
registered by Device Manager are updated when host information is reported by the
Device Manager Agents. For details on host operations, see Chapter 9.
Figure 10.2 Add Subsystem (9900V)
226
10.1.3 Viewing and Editing Storage Subsystem Properties

The System Administrator and Storage Administrator can view and edit the subsystem
properties. Guest users can only view the subsystem properties. Local users (the Local
System Administrator, Local Storage Administrators, and Local Guests) do not have access to
these functions.
To view and edit the properties of a storage subsystem:
1. Log in to Device Manager as a System Administrator or Storage Administrator if you want
to edit the subsystem properties. You can log in as Guest if you only want to view the
subsystem properties.
2. Select the Subsystems object in the navigation frame (refer to Figure 10.1), and select
the desired subsystem. The Show Properties subwindow in the information frame
displays the following subsystem properties (see Figure 10.3):
Name: the name of the subsystem
Type: the type (vendor model) of the subsystem (e.g., HDS9980V)
Serial number: the (vendor) serial number of the subsystem
IP address (TagmaStore USP, 9900 V, 9900, and T3): the IP address of the
subsystem
IP address 1 and IP address 2 (9500 V, 9200): the two IP addresses of the subsystem
Microcode DKC: the microcode level of the disk controller
Microcode SVP (TagmaStore USP, 9900 V, and 9900): the microcode level of the
service processor (SVP)
Configured Capacity: the configured capacity of the subsystem, not the total size of
the physical disks. Configured Capacity is the total available memory, which means
the total of the sizes of all logical devices on the machine. Thus, the Configured
Capacity increases or decreases when logical devices are created or deleted.
Security (9500 V): the status of the security option for 9500V
Total Cache: the total cache capacity of the storage subsystem
Multipath support (T3): the status of the multipath option (on or off)
Alerts: the number of red vertical bars indicates the number of alerts for the
storage subsystem If you click a red vertical bar, a list of the alerts appears. (See
section 5.5 for details on alerts.)
Note: The Physical View button opens the Physical View for the selected subsystem (see
section 10.2).
Note: If you are using the URLLink feature in Device Manager, a URLLink name button
appears (see section 5.7.8). Clicking the URLLink name button launches a Web
application specified using the URLLink feature. If you are logged in as a Guest, this
button is inactive. If the URLLink destination points to DAMP, the URLLink name button
appears only in the Physical View dialog box, not in the Show Properties subwindow.
227
Note: When a NAS-CHA running NAS Manager resides on the storage subsystem, a
NAS/Management button appears. Clicking the NAS/Management button opens the
Select Nas/Management Port Controller dialog box. Select NAS-CHA, and then click the
OK button to launch NAS Manager (see section 5.7.6). If you are logged in as a Guest,
this button does not appear.
3. To modify the subsystem properties, select the Modify Properties operation in the
method frame to open the Modify Properties panel for the subsystem (see Figure 10.4).
You can change the following subsystem properties:
Name: Enter a name of no more than 50 bytes. You can use full-width characters
and the following half-width characters:
A - Z, a - z, 0 - 9, -, _, ., @
The name can include spaces, but cannot consist only of spaces. Leading or trailing
Note on LUN Scan: If you change the subsystem name after a LUN Scan, the names
of the corresponding logical groups in the LUN Scan group are not updated. You need
to rename those groups to match the new subsystem name. If you do not and then
execute another LUN Scan on the renamed subsystem, a second set of logical groups
will be created in the LUN Scan group using the new subsystem name.
IP Address 1 and IP Address 2 (displayed for 9500V and 9200): When one of the
items is not specified, you can enter the IP address for the item that is not
specified.
User ID (not displayed for 9900): Enter the user ID for the subsystem. Enter no
more than 25 bytes, using the following characters:
A - Z, a - z, 0 - 9, -, _, ., @
New Password (not displayed for 9900): Enter the new password for accessing the
subsystem using Device Manager. Enter no more than 40 bytes, using the following
characters:
A - Z, a - z, 0 - 9, -, _, ., @
For TagmaStore USP, Lightning 9900V, and T3, the user ID is required and the
password is optional.
For Thunder 9500V and 9200, the user ID and password take effect only when the
Password Protection option is enabled on the storage subsystem. Even if this option
is enabled, you can omit entering a user ID and password. When this option is
enabled, the storage subsystem is locked while Device Manager is issuing a command
for the storage subsystem.
4. When you are finished modifying the properties, select OK to modify the properties as
specified, or select Cancel to cancel your request to modify the properties.
228
Figure 10.3 Viewing Storage Subsystem Properties
229
Figure 10.4 Modify Properties (9900V)
230
10.1.4 Performing a Refresh Operation

The System Administrator and Storage Administrator can perform Refresh operations.
A Refresh operation rediscovers the storage subsystem. You should perform a Refresh
operation when changes have been made to a storage subsystem other than through the
HiCommand Device Manager system (e.g., after adding new disk drives, after adding new
ShadowImage pairs using CCI or Storage Navigator).
Caution: Perform a Refresh operation after the subsystem microcode is updated.
WARNING: After the microcode is updated, the SVP tuning parameters must be set and the
SVP must be rebooted before you use Device Manager to refresh the subsystem. If you
refresh the subsystem after the SVP tuning parameters are set but without the SVP reboot,
the disk unit (DKU) and logical unit number (LUN) information is deleted from the refreshed
storage subsystem.
Caution: You do not need to stop the Device Manager Server in order to replace the
microcode of a subsystem. However, you must ensure that no Device Manager refresh or
setup operations (such as add storage, delete storage, create logical devices, delete logical
devices, or set host mode) are being executed on the corresponding storage subsystem.
During microcode replacement, an error may be output to the trace log or error log by
polling on the storage subsystem. This error will no longer be output once replacement of
the microcode has terminated normally.
Note: While a storage subsystem is being refreshed, if you shut down the host using a
volume of the corresponding storage subsystem or shut down its agents, it may take about
15 minutes to complete the refresh operation.
Note: In TagmaStore USP, if you enable the automatic refresh function in the Device
Manager Server properties, Device Manager automatically performs a refresh operation when
the mode is changed from Modify to View in the Physical View for TagmaStore USP.
Note: If you are using TagmaStore USP Universal Volume Manager, each time you add an
external subsystem after adding TagmaStore USP, you must refresh the TagmaStore USP
subsystem.
To perform a Refresh operation:
2. Select and expand the Subsystems object in the navigation frame, and then select the
desired subsystem (refer to Figure 10.1).
3. In the method frame, select the Refresh button.
4. When the Refresh Storage Subsystem Confirmation panel appears (see Figure 10.5),
select OK to refresh the subsystem information, or select Cancel to cancel your request
to refresh the subsystem information.
You are notified when the Refresh operation is complete.
231
Figure 10.5 Refresh Storage Subsystem Confirmation
232
10.1.5 Handling a Change to the IP Address of a Subsystem

When the IP address of a subsystem is changed, the System Administrator or Storage
Administrator must re-register that subsystem as follows:
1. Back up the databases on the Device Manager Server. For details on database backup,
(MK-91HC002).
2. Log in to Device Manager as a System Administrator or a Storage Administrator.
3. Add the storage subsystem to Device Manager, making sure to enter the new IP address
on the Add Subsystem panel (see section 10.1.2 for instructions).
4. After the storage subsystem discovery is complete, check the storage subsystem
properties to verify that the new IP address is displayed.
Note: When you change the IP address of the storage subsystem, even if you re-register
the subsystem using the new IP address, the following information will not be updated.
Subsystem name used in Web Client. To change the subsystem name, enter the
new name on the Modify Properties panel for the subsystem (see section 10.1.3 for
instructions).
Name of the subsystem group in LUN SCAN. To change the name of the logical
group in the LUN SCAN group, enter the new name on the Modify Properties panel
for the logical group (see section 7.4 for instructions).
233
10.1.6 Deleting a Storage Subsystem

The System Administrator and Storage Administrator can delete a storage subsystem from
HiCommand Device Manager. Guests, Local System Administrators, Local Storage
Note: If you remove a storage subsystem, all related volumes, components, and storage
groups are also removed from Device Manager, but the removal operation has no effect on
the storage subsystem itself.
Note: If you remove a storage subsystem that has alert information and then attempt to
display the alert information for the removed subsystem, ARRAY.HDSxxxx is displayed as
the source. In this case, either delete the alert information if it is not needed, or add the
storage subsystem to Device Manager again.
To delete a subsystem from the HiCommand Device Manager system:
Administrator.
3. In the method frame, select the Remove Subsystem button.
4. When the Remove Subsystem Confirmation panel appears (see Figure 10.6), select OK
to delete the subsystem, or select Cancel to cancel your request to delete the
subsystem.
5. If the subsystem is associated with any logical groups, Device Manager displays an
important warning. After reading the warning, select YES to go ahead and delete the
subsystem, or select NO to cancel your request to delete the subsystem.
You are notified when the delete subsystem operation is complete.
234
Figure 10.6 Remove Subsystem Confirmation
235
10.2 Physical View Operations

The System Administrator, Storage Administrator, and Guest can perform Physical View
operations. Local users (Local System Administrator, Local Storage Administrator, Local
Guest) do not have access to this function.
Note: To display a Physical View panel, JRE version 1.4.2 must be installed. The Physical
View panels cannot be displayed if JRE is not installed. For details on JRE, see section 0.
Note: To display a Physical View panel for TagmaStore USP, Storage Navigator must be
installed on TagmaStore USP that is to be managed by Device Manager
The Physical View of each subsystem provides access to the subsystem-based link-and-launch
applications (e.g., 9900V Storage Navigator, 9900V NAS/Manage, 9500V and 9200/DAMP, and
URLs for customer-defined third-party software applications) (see section 2.5). The Physical
View also provides access to the port, array group, and LDEV operations for the subsystem
(see sections 10.3, 10.4, and 10.5).
The Physical View operations include:
Viewing and configuring detailed information for TagmaStore USP (see section 10.2.1)
Viewing detailed information for Lightning 9900V (see section 10.2.2)
Viewing detailed information for Lightning 9900 (see section 10.2.3)
Viewing detailed information for Thunder 9500V (see section 10.2.4)
Viewing detailed information for Thunder 9200 (see section 10.2.5)
Viewing detailed information for T3 (see section 10.2.6)
Viewing detailed LDEV information (see section 10.2.7)
Note: The total size that is displayed is not the total size of the physical disk. It is the total
available memory, which means the total of the sizes of all logical devices on the machine.
Thus, this total size is increased or decreased by creating or deleting logical devices.
236
10.2.1 Viewing Detailed Information for TagmaStore USP

The System Administrator and Storage Administrator can view and configure detailed
information for TagmaStore USP by using the Physical View for TagmaStore USP. Guests
can only view the detailed information for TagmaStore USP in the Physical View for
TagmaStore USP. Local users do not have access to this function.
Note: In TagmaStore USP, if you enable the automatic refresh function in the Device
Manager Server properties, Device Manager automatically performs a refresh operation when
the mode is changed from Modify to View in the Physical View for TagmaStore USP.
To view detailed information about TagmaStore USP:
1. Log in to Device Manager as a System Administrator, Storage Administrator, or Guest.
3. In the Show Properties subwindow, select the Physical View button to open the Physical
View for the selected TagmaStore USP.
In the Physical View for TagmaStore USP, you can view and configure (for example, set
up a port, set up a channel adapter, create an LDEV, and set up LUN security) the
detailed information about TagmaStore USP. For details about operation, see the
Remote Console - Storage Navigator User's Guide.
10.2.2 Viewing Detailed Information for Lightning 9900 V

operations. Local users do not have access to this function.
To view detailed information for a Lightning 9900V subsystem:
Administrator, or Guest.
desired Lightning 9900V subsystem (refer to Figure 10.1).
3. In the Show Properties subwindow, select the Physical View button to open the
Physical View for the selected Lightning 9900V subsystem (see Figure 10.7).
The CONFIGURATION button is selected in the initial window, which displays the
subsystem properties (e.g., serial number, IP address, microcode, configured capacity).
4. On the Physical View, you can select the desired port to open the Port Information
panel. For example, to view the information for the CL1-A port, select the A button
inside the Cluster 1 frame. For details on the Port Information panel, see section 10.3.
5. On the Physical View, you can select the PORT CONTROLLERS button to open the Port
Controller panel. For details on the Port Controller panel, see section 10.3.4.
6. To view array group information, select the ARRAY GROUPS button (see Figure 10.8).
7. On the ARRAY GROUPS view, you can select the VIEW button for the desired frame to
open the Frame Information (level 1) panel (see Figure 10.9).
237
Important: The Lightning 9900V has the capability to integrate two array groups and
handle them as a single array group. This is called a discrete VDEV configuration (see
Figure 10.10). A discrete VDEV configuration logically integrates two sets of 2D+2D
(RAID1) into a single set of 2D+2D (RAID1) by integrating two array groups.
For discrete VDEV configuration, Coupled is displayed in the parity group list along with
the remote parity group (e.g., Coupled:1-2). If you select a parity group of a discrete
VDEV configuration in the Frame Information (level 1) panel, Frame Information (level 2)
panel displays information only for array groups belonging to the representative VDEV.
No information appears for array groups that do not belong to the representative VDEV.
For a discrete VDEV configuration, the Frame Information panel displays the information
shown in Figure 10.11.
Note: For a 7D+1P array group, Coupled appears next to the parity group number (refer
to Figure 10.9 (e.g., Parity Group 1-2(Coupled:2-2)). In this case, information about
the parity group indicated by Coupled (example: 2-2) is not displayed.
8. On the Frame Information (level 1) panel, you can select the desired array group to open
the Frame Information (level 2) panel (see Figure 10.12).
9. On the Frame Information (level 2) panel, you can select the desired array group to open
the LDEV Information panel. For details on this panel, see section 10.2.7.
10. On the Physical View, select the DISKS button to view the disk information (see Figure
10.13).
Figure 10.7 Physical View for Lightning 9900 V (Configuration)
238
The 9900V Physical View (Configuration) displays the following information and buttons:
Model: the type (vendor model) of the subsystem (e.g., HDS9980V)
Serial: the (vendor) serial number of the subsystem
IP address: the IP address of the subsystem
Microcode SVP: the microcode level of the service processor
Configured Capacity: the configured capacity of the subsystem (the total capacity of all
LDEVs, not the total capacity of the physical disks). The Configured Capacity increases
or decreases when logical devices are created or deleted.
PORT CONTROLLERS button: opens the Port Controller panel (see section 10.3.4)
Port buttons (e.g., A under Cluster 1 for port CL1-A): opens the Port Information panel
for the selected port (see section 10.3)
239
Figure 10.8 Physical View for Lightning 9900 V (Array Groups)

The 9900V Physical View (Array Groups) displays the following information and buttons:
Array Groups: Displays the number of array groups and capacity for each array control
processor (ACP) and the total number of array groups and total capacity for all ACPs
Note: For the Lightning 9900V storage subsystem, 0 GB appears for the capacity of an
array group for which a mainframe emulation type (e.g., 3390-3) is set.
Note: The displayed capacity of the array group is truncated to two decimal places. This
may cause the total capacity of the array group to be less than the sum of the capacity
of the array groups. However, this does not mean that the actual available capacity has
been reduced.
240
VIEW button: opens the Frame Information (level 1) panel for the selected frame (see
Figure 10.9)
Figure 10.9 Frame Information Panel for Lightning 9900 V (Level 1)

The 9900V Frame Information (level 1) panel displays the subsystem name, ACP number,
frame number, and list of parity groups (maximum 32) for the frame that you selected using
the VIEW button on the Physical View. The Lightning 9900V has a maximum of 512 array
groups on one chassis (the parts displayed in pair both at the top and bottom of the frame).
The Frame Information (level 1) panel displays up to 32 parity groups, each of which can
have up to 16 array groups.
Selecting a parity group opens the Frame Information (level 2) panel (see Figure 10.12).
Note: If you use disk units of Lightning 9900 for Lightning 9900V, the Frame Information
(level 1) panel displays up to 12 parity groups in line. Because the actual device has only one
virtual device in one parity group, the Frame Information (level 2) panel always displays only
one array group.
241
Figure 10.10 Discrete VDEV Configuration for Lightning 9900 V
242
Figure 10.11 Frame Information Panel for Discrete VDEV Configuration
243
Figure 10.12 Frame Information Panel for Lightning 9900 V (Level 2)

The Frame Information (level 2) panel displays the subsystem name, ACP number, frame
number, and list of array groups (16 maximum) for the parity group that you selected on the
Frame Information (level 1) panel. The following information is displayed for each array
group:
Array group ID
Number of disks in the array group and their capacity (4 x 72 GB: four 72-GB disk drives)
Capacity of the array group
Selecting an array group opens the LDEV Information panel (see section 10.2.7).
Note: If you use disk units of Lightning 9900 for Lightning 9900V, the Frame Information
(level 1) panel displays up to 12 parity groups in line. Because the actual device has only one
virtual device in one parity group, the Frame Information (level 2) panel always displays only
one array group.
244
Figure 10.13 Physical View for Lightning 9900 V (Disks)

The Disks view of the 9900V Physical View displays the following information and buttons:
ACP: Displays the number of disks and capacity for each array control processor and the
total number of disks and total capacity for all ACPs
Note: If 9900 disk units are attached to the Lightning 9900V, the Disks view displays six
disk units (three units on each side) in total in the maximum configuration. In the Array
Groups view, virtual devices and parity groups appear to be in a one-to-one relationship.
If you use disk units of Lightning 9900 in six frames of Lightning 9900V, for example,
up to 12 parity groups (blue icons) are displayed.
In the Disks view, when 9900V disk units are used, the number of installed disks and the
total number of installable disks are displayed for each chassis.
245
10.2.3 Viewing Detailed Information for Lightning 9900

To view detailed information for a Lightning 9900 subsystem:
desired Lightning 9900 subsystem (refer to Figure 10.1).
Physical View for the selected Lightning 9900 subsystem (see Figure 10.14).
The CONFIGURATION button is selected in the initial window, which displays the
subsystem properties (e.g., serial number, IP address, microcode, configured capacity).
panel. For example, to view the information for the CL1-A port, select the A button
inside the Cluster 1 frame. For details on the Port Information panel, see section 10.3.
5. On the Physical View, you can select the PORT CONTROLLERS button to open the Port
Controller panel. For details on the Port Controller panel, see section 10.3.4.
6. To view array group information, select the ARRAY GROUPS button (see Figure 10.15).
7. On the ARRAY GROUPS view, you can select the VIEW button for the desired frame to
open the Frame Information panel (see Figure 10.16).
8. On the Frame Information panel, you can select the desired array group to open the
LDEV Information panel. For details on the LDEV Information panel, see section 10.2.7.
9. On the Physical View, select the DISKS FRONT or DISKS BACK button (DISKS button for
Lightning 9910) to view the disk information (see Figure 10.17).
246
Figure 10.14 Physical View for Lightning 9900 (Configuration)

The 9900 Physical View (Configuration) displays the following information and buttons:
Model: the type (vendor model) of the subsystem (e.g., HDS9960)
Microcode SVP: the microcode level of the service processor
Configured Capacity: the configured capacity of the subsystem (the total capacity of all
LDEVs, not the total capacity of the physical disks). The Configured Capacity increases
or decreases when logical devices are created or deleted.
VIEW button: opens the Frame Information panel (see Figure 10.9)
247
Figure 10.15 Physical View for Lightning 9900 (Array Groups)

The 9900 Physical View (Array Groups) displays the following information and buttons:
Array Groups: displays the number of array groups and capacity for each array control
processor (ACP) and the total number of array groups and total capacity for all ACPs
Note: For the Lightning 9900 storage subsystem, 0 GB appears for the capacity of an
array group for which a mainframe emulation type (e.g., 3390-3) is set.
Note: The displayed capacity of the array group is truncated to two decimal places. This
may cause the total capacity of the array group to be less than the sum of the capacity
of the array groups. However, this does not mean that the actual available capacity has
been reduced.
248
VIEW button: opens the Frame Information panel for the selected frame (see Figure
10.9)
Figure 10.16 Frame Information Panel for Lightning 9900

The Frame Information panel displays the subsystem name, ACP number, frame number, and
list of array groups for the selected frame. The following information is displayed for each
array group:
Array group ID
Number of disks in the array group and their capacity (4 x 72 GB: four 72-GB disk drives)
Capacity of the array group
Selecting an array group opens the LDEV Information panel (see section 10.2.7).
249
Figure 10.17 Physical View for Lightning 9900 (Disks)

The Disks view of the 9900 Physical View displays the following information and buttons:
250
ACP: displays the number of disks and capacity for each array control processor and the
total number of disks and total capacity for all ACPs
10.2.4 Viewing Detailed Information for Thunder 9500 V

To view detailed information for a Thunder 9500V subsystem:
desired Thunder 9500V subsystem (refer to Figure 10.1).
Physical View for the selected Thunder 9500V subsystem (see Figure 10.18).
The Physical View displays the following information for the selected 9500V:
CONFIGURATION: displays the model, serial number, IP addresses, DKC microcode,

configured capacity, total cache, security option
Legend for FC disk layout grid: Grouped (assigned to an array group of the FC drive),
Current Group (assigned to the selected array group of the FC drive), Unused,
Spare
Disks & Arrays: displays the total number of disks, the total number of array groups,
and a list of the existing array groups
The NEW button allows you to add a new array group (see section 10.4.1).
The DELETE button allows you to delete an array group (see section 10.4.3).
The SPARE button allows you to set a spare drive (see section 10.4.4).
The VIEW button displays the LDEV Information panel (see section 10.2.7).
The DISK ARRAY MANAGEMENT PROGRAM button launches the Disk Array
Management Program.
panel. For example, to view the information for port A in CHA-0, select the A button in
the CHA 0 box. For details on the Port Information panel, see section 10.3.
251
Figure 10.18 Physical View for Thunder 9500 V

The 9500V Physical View displays the following information:
252
Configuration:
Model: the type (vendor model) of the subsystem (e.g., HDS9570V)
IP addresses: the two IP addresses of the subsystem
Configured Capacity: the configured capacity of the subsystem (the total capacity
of all LDEVs, not the total capacity of the physical disks). The Configured Capacity
increases or decreases when logical devices are created or deleted.
Security Option: status of the security option: No Security, LUN Security, LUN
Management, or Unknown
Legend for FC disk layout grid: Grouped (assigned to an array group of the FC drive),
Current Group (assigned to the selected array group of the FC drive), Unused,
Spare
Legend for SATA disk layout grid: Grouped (assigned to an array group of the SATA
drive), Current Group (assigned to the selected array group of the SATA drive),
Unused, Spare
Disks & Arrays:
Disks: displays the total number of disks
Array groups: displays the total number of array groups
View Array Group: displays a list of the existing array groups. When you select an
array group, the Delete and View buttons are enabled, and the disks in the selected
array group are highlighted in the disk layout grid.
10.2.5 Viewing Detailed Information for Thunder 9200

To view detailed information for a Thunder 9200 subsystem:
desired Thunder 9200 subsystem (refer to Figure 10.1).
Physical View for the selected Thunder 9200 subsystem (see Figure 10.19).
The Physical View displays the following information for the selected 9200:
CONFIGURATION: displays the model, serial number, IP addresses, DKC microcode,

configured capacity, total cache.
Legend for disk layout grid: Grouped (assigned to an array group), Current Group
(assigned to the selected array group), Unused, Spare
and a list of the existing array groups
The SPARE button allows you to set a spare drive (see section 10.4.4).
panel. For example, to view the information for port A in CHA-0, select the A button in
the CHA 0 box. For details on the Port Information panel, see section 10.3.
253
Figure 10.19 Physical View for Thunder 9200

The 9200 Physical View displays the following information:
254
Configuration:
Model: the type (vendor model) of the subsystem (e.g., HDS9200)
IP addresses: the two IP addresses of the subsystem
Disks & Arrays:
10.2.6 Viewing Detailed Information for T3

To view detailed information for a T3 subsystem:
desired T3 subsystem (refer to Figure 10.1).
Physical View for the selected T3 subsystem (see Figure 10.20).
The Physical View displays the following information for the selected T3:
CONFIGURATION: displays the model, serial number, IP address, microcode,

configured capacity, total cache, multipath support
and a list of the existing array groups.
4. On the Physical View, you can select the port (e.g., 1 button in the u1ctr box) to open
the Port Information panel. For details on the Port Information panel, see section 10.3.
255
Figure 10.20 Physical View for T3

The T3 Physical View displays the following information:
256
Configuration:
Model: the type (vendor model) of the subsystem (e.g., SUNT300)
Microcode: the microcode level of the disk controller
Multipath Support: the status of multipath support (enabled or disabled)
Disks & Arrays:
10.2.7 Viewing Detailed LDEV Information

The System Administrator, Storage Administrator, and Guest can view the detailed LDEV
information. Local users do not have access to this function.
To view the detailed LDEV information:
3. Select the Physical View button to open the Physical View of the subsystem, and then
open the LDEV Information panel as follows:
For 9900V, select the VIEW button for the desired frame, select the desired parity
group on the Frame Information (level 1) panel, select the desired array group on
the Frame Information (level 2) panel, and then select the desired array group.
For 9900, select the VIEW button for the desired frame, select the desired array
group on the Frame Information panel, and then select the desired array group.
For 9500V, 9200, and T3, select the desired array group, and then select VIEW.
4. The LDEV Information panel consists of the following three display areas:
Storage Detail list (upper left): Displays a list of logical devices in the selected array
group. Select the desired LDEV in this list to display the detailed LDEV information.
Each LDEV row displays the LDEV number and size (MB, fractional portion truncated).
If a path has been set, the port is also displayed. If the LDEV is part of a LUSE
volume, the following is displayed: (LUSE: representative-logical-device-number).
For Lightning 9900V and 9900, the capacity of an HRX intermediate volume is also
displayed (capacity in MB and Cyl). For more information on the HRX intermediate
volume, see the documentation for the storage subsystem that you use.
Array Group Info (upper right): Displays the detailed information for the selected
array group: ACP (9900V and 9900 only), array group name, disk size (smallest
physical disk size in the array group for 9500V and 9200), RAID level, Type (9500V
only) emulation type (9900V and 9900 only), free space, largest space (largest
amount of contiguous free space in the array group).
LDEV information (lower part). Displays the detailed information for the selected
LDEV. Provides the Detail tab (see Figure 10.21) Path Info tab (see Figure 10.22) and
Pair Info tab (see Figure 10.23)(see descriptions below).
257
The LDEV Information panel provides the following buttons:
ALLOCATE: Allows you to allocate a path to the selected logical device.
UNALLOCATE: Allows you to release the path that is allocated to the selected LDEV.
Select the checkbox of the desired path on the Path Info tab to activate this button.
CREATE LDEV: Allows you to create logical devices in an array group.
DELETE LDEV: Allows you to delete the selected logical device from the array group.
Select a logical device to which no path is set to activate this button.
LDEV CONFIG: Allows you to set a command device. Selecting a logical device that
can be set as a command device activates the LDEV CONFIG button.
Figure 10.21 LDEV Information Panel Detail Tab

The Detail tab of the LDEV Information panel displays the following information. You can
sort the displayed information by selecting the desired column heading.
LDEV: LDEV number. For a LUSE volume, you can select a logical device number from
the drop-down list of the logical devices that make up the LUSE volume. Selecting a
logical device displays its information.
Capacity: capacity of the logical devices. For a LUSE volume, displays the capacity of
the LUSE volume instead of the capacity of individual logical devices.
For 9900V and 9900, also displays the capacity of the HRX intermediate volume.
258
The capacity values are in megabytes with the fractional portions cut off. Therefore, the
displayed value may be less than the actual available capacity. For an HRX intermediate
volume, the capacity in cylinders (number-of-cylinders Cyl) is displayed alongside the
capacity in megabytes. For more information on the HRX intermediate volume, see the
documentation for the storage subsystem that you use.
EMU Type: emulation type (9900V, 9900 only) (e.g., OPEN-9)
Copy Type: SI (ShadowImage), TC(Sync) (TrueCopy Synchronous), TC(Async) (TrueCopy

Asynchronous), TC (TrueCopy whose synchronization mode is unknown*), QS
(QuickShadow), Unpaired, none (pair status unknown). This item is not displayed for T3.
* Displayed when the subsystem containing the primary volume is not registered with
Device Manager. However, if the subsystem containing the secondary volume is a 9900V,
the synchronization mode information is available as TC(Sync) or TC(Async).
Volume Attr: CVS (custom volume size created by Virtual LVI/LUN), LUSE, LUSE (CVS)
(LUSE volume made up of CVS volumes), V-VOL (V-VOL for QuickShadow), POOL
(QuickShadow data pool), GUARD (Data Retention or Open LDEV Guard is set up), none
(normal volume). This item is not displayed for T3.
CMD DEV: CMD DEV, or none (not a command device). This item is not displayed for T3.
Guard Mode(Attribute): attribute of the logical device (Lightning 9900V and Thunder
9500 V only))
Guard Mode(S-VOL): S-VOL Disable attribute (Lightning 9900V only)
Guard Mode(Mode): the INH bit attribute (Lightning 9900 V and Thunder 9500 V only)
Figure 10.22 LDEV Information Panel Path Info Tab
259
The Path Info tab of the LDEV Information panel displays the following information. You can
sort the displayed information by selecting the desired column heading.
LDEV: LDEV number. For a LUSE volume, displays only the representative LDEV number.
To select the path of the logical device to be the target of ALLOCATE or UNALLOCATE,
select the checkbox of the path.
Port/HSD/LUN or Port/LUN: port, host storage domain, and logical unit number for
Lightning 9900V and Thunder 9500V in LUN Management mode. This item displays the
port and logical unit number for Thunder 9500V in LUN Security mode, Lightning 9900,
Thunder 9200, and T3.
Group: name of the storage group to which the volume path belongs
Host: host name and WWN
Filesystem: mount point on the host (displayed only when Device Manager Agent is
installed on the host)
Host Bus/TID/LUN: SCSI information that the host recognizes (displayed only when
Device Manager Agent is installed on the host)
Capacity: capacity of the LDEV. For Lightning 9900V and 9900, this item also displays the
capacity of an HRX intermediate volume.
The displayed values are in megabytes with the fractional portions cut off. Therefore,
the displayed value may be less than the actual available capacity. For an HRX
intermediate volume, the capacity in cylinders (number-of-cylinders Cyl) is displayed
alongside the capacity in megabytes. For more information on the HRX intermediate
volume, see the documentation for the storage subsystem that you use.
260
% Used: usage percentage of a volume (displayed only when Device Manager Agent is
installed on the host). For more details about % Used, see section 8.2.1.
Last Updated: time of the last update performed by Device Manager Agent (only when
Device Manager Agent is installed on the host).
Figure 10.23 LDEV Information Panel Pair Info Tab

The Pair Info tab of the LDEV Information panel displays the following information (not
displayed for T3). You can sort the information by selecting the desired column heading.
Copy Type: SI (ShadowImage), TC(Sync) (TrueCopy Synchronous), TC(Async) (TrueCopy

Asynchronous), TC (TrueCopy whose synchronization mode is unknown*), QS
(QuickShadow), Unpaired, none (pair status unknown). This item is not displayed for T3.
Note on TC: Displayed when the subsystem containing the primary volume is not
registered with Device Manager. However, if the subsystem containing the secondary
volume is a 9900V, the synchronization mode information is available. When TC is
displayed, copy information is not available, and Copy Status displays no value.
Copy Status: Simplex (SMPL), Pair (PAIR), Copying (COPY(PD), COPY(RS), COPY(SP), or
COPY), Reverse-Copying (COPY(RS-R), Split (PSUS or PSUS(SP)), Suspended (PSUE),
Error in LUSE (PDUB), Suspending (Suspending), Deleting (Deleting), none displayed
(copy status is unknown).
For details on the meaning of each pair status description, please refer to the applicable
manual (e.g., the Hitachi Thunder 9500 V Series ShadowImage Users Guide).
Fence Level: setting concerning recovery that is performed when a failure occurs in
execution of TrueCopy. For details, see the applicable TrueCopy manual.
Split Time: time when a snapshot is obtained when Copy Type is QuickShadow. This item
is displayed only for Thunder 9500V.
LDEV(P-VOL): logical device number of the primary volume
Type(P-VOL): model name of the subsystem to which the primary volume belongs.
Displays Unknown if the storage subsystem to which the primary volume belongs is not
discovered.
261
Serial No.(P-VOL): serial number of the subsystem to which the primary volume belongs.
For Thunder 9200, Thunder 9500V, and Lightning 9900, displays Unknown if the
storage subsystem to which the primary volume belongs is not discovered.
AG(P-VOL): number of the array group to which the primary volume belongs
LDEV(S-VOL): logical device number of the secondary volume
Type(S-VOL): model name of the subsystem to which the secondary volume belongs.
Displays Unknown if the storage subsystem to which the secondary volume belongs is not
discovered.
Serial No.(S-VOL): serial number of the subsystem to which the secondary volume
belongs. For Thunder 9500V, this item displays Unknown if the storage subsystem to
which the secondary volume belongs is not discovered.
AG(S-VOL): number of the array group to which the secondary volume belongs
Note: To display or update the following information, you must update (refresh) the storage
subsystem information:
ShadowImage and TrueCopy settings for Lightning 9900V
ShadowImage settings for Thunder 9500V and Thunder 9200
For details on the system configuration required to display the ShadowImage and TrueCopy
settings of subsystems, see the HiCommand Device Manager Server Installation and
Configuration Guide.
262
10.3 Port Operations

The HiCommand Device Manager port operations include:
Configuring the ports (9900V, 9900, 9500V, and 9200) (see section 10.3.1)
Managing LUN groups (9900 only) (see section 10.3.2)
Managing WWN groups (9900 only) (see section 10.3.3)
Configuring the fibre-channel adapters (9900V and 9900) (see section 10.3.4)
Note: The NAS-CHA ports (9900V) and mainframe ports (9900V or 9900) are unavailable.
Note: To perform an operation on a port for TagmaStore USP, use the Physical View for
TagmaStore USP (see section 10.2.1).
10.3.1 Configuring Ports (9900 V, 9900, 9500 V, and 9200)

The System Administrator and Storage Administrator can configure the fibre-channel ports
on the Lightning 9900 V Series, Lightning 9900, Thunder 9500 V Series, and Thunder
9200 subsystems. Guests, Local System Administrators, Local Storage Administrators, and
Local Guests do not have access to this function.
Table 10.1 lists the available arbitrated loop-port address (AL-PA) values ranging from 01 to
EF.
Table 10.1
Available AL-PA Values
EF
CD
B2
98
72
55
3A
25
E8
CC
B1
97
71
54
39
23
E4
CB
AE
90
6E
53
36
1F
E2
CA
AD
8F
6D
52
35
1E
E1
C9
AC
88
6C
51
34
1D
E0
C7
AB
84
6B
4E
33
1B
DC
C6
AA
82
6A
4D
32
18
DA
C5
A9
81
69
4C
31
17
D9
C3
A7
80
67
4B
2E
10
D6
BC
A6
7C
66
4A
2D
0F
D5
BA
A5
7A
65
49
2C
08
D4
B9
A3
79
63
47
2B
04
D3
B6
9F
76
5C
46
2A
02
D2
B5
9E
75
5A
45
29
01
D1
B4
9D
74
59
43
27
CE
B3
9B
73
56
3C
26
263
To configure the ports:

2. Select the Subsystems object in the navigation frame, select the desired subsystem, and
then select the Physical View button.
3. On the Physical View, select the desired port (e.g., for 9900V port CL1-A, click on A in
Cluster 1) to open the Port Information panel (see Figure 10.24).
4. On the Port Information panel, change the port settings as desired. For details on the
port information and settings for each subsystem, see the descriptions below.
Note: If you change the Topology (Connection) setting from Point-to-Point to FC-AL,
the attributes displayed by Web Client may not change because it takes time for the
change to take effect in the subsystem. In such a case, wait for up to a minute after
changing the setting, and then refresh the storage subsystem (see section 10.1.4). The
updated Topology (Connection) value should appear.
Note: If you change the Fibre Addr setting, the new setting may not take effect
immediately. In such a case, make sure that the specified port is connected to a fiber
network, and then refresh the subsystem information (see section 10.1.4).
5. After making the desired changes to the port settings, select OK to change the port
settings as specified, or select Cancel to cancel your request to change the settings.
6. When the Confirmation panel appears, review the requested operations, and select YES
to change the port settings, or select NO to cancel your request.
You are notified when the port change operation is complete.
WARNING: If you change the attributes of a port, the host currently accessing the port may
no longer be able to access the storage. Before changing the settings, you must stop all I/O
operations with the host. If you use Device Manager to change the port settings while I/O
operations between the host and the subsystem are underway, the I/O operations may
terminate abnormally. For Thunder 9200, when a logical unit number is set, an I/O
operation between the host and the 9200 subsystem may terminate abnormally.
For the Thunder 9200, HiCommand Device Manager notifies you that the subsystem will be
rebooted so that the new port settings become effective. Select OK to reboot the 9200
subsystem and change the port settings, or select Cancel to cancel your request to change
the port settings and not reboot the 9200 subsystem.
264
Figure 10.24 Port Information Panel for the Lightning 9900 V

Lightning 9900 V Series: For further information on the 9900V port settings, please refer
to the 9900 V Configuration Guide for the attached platform (e.g., the Hitachi Lightning
9900 V Series Windows NT Configuration Guide), or contact your Hitachi Data Systems
team.
Port name: Ports with lower-case characters are activated for 9900V with a 16-port
channel adapter. For a port with lower-case characters that exists in a channel adapter
on cluster 1, CL3-x is displayed as the port name. For a port with lower-case characters
that exists in a channel adapter on cluster 2, CL4-x is displayed as the port name.
Port settings:
LUN security: Enable or disable LUN security for all LUNs on the port. To secure
LUNs, select Enabled. If no LUN security at all is desired, you can select Disabled.
Topology (Fabric): On, Off
Topology (Connection): FC-AL, Point-to-Point
Fibre Addr: In fabric environments, the port address is assigned automatically by

fabric switch port number and is not controlled by the 9900V port settings. In
arbitrated loop environments, the port address is set by entering an AL-PA (or loop
ID). Refer to Table 10.1 for the available AL-PA values.
Channel speed: 1 GB/s, 2 GB/S, or auto (cannot be modified for some port types)
265
Host storage domain settings:

Host Storage Domain Name: Displays and allows you to change the HSD name: maximum
of eight characters, cannot begin or end with a space nor consist of spaces only. The
HSD name cannot contain full-width characters or half-width Kana characters, or any
of the following characters:
", /, <, >, :, ;, *, ?, |, \, ,
Host Mode: Solaris, HP, AIX, Windows, NetWare, etc. Select the host mode for
the connected platform to enable the host to see all LUNs on the port.
Note: If Device Manager cannot recognize the host mode specified for the host
storage domain, Unknown is displayed.
Lun Security: Host name/WWN for each WWN in the selected host storage domain
WWN Info button: Displays the WWN(s) registered to the port (Figure 10.25)
Figure 10.25 WorldWideName Information Panel for the 9900 V
266
Port Information Panel for Lightning 9900: For further information on the 9900 port
settings, please refer to the 9900 Configuration Guide for the attached platform (e.g., the
Hitachi Lightning 9900TM HP-UX Configuration Guide), or contact your Hitachi Data Systems
team.
LUN security: Enable or disable LUN security for all LUNs on the port. To secure LUNs,
select Enabled. If no LUN security at all is desired, you can select Disabled.
Topology (Fabric): On, Off
Topology (Connection): FC-AL, Point-to-point
Fibre address. In fabric environments, the port address is assigned automatically by

fabric switch port number and is not controlled by the 9900 port settings. In arbitrated
loop environments, the port address is set by entering an AL-PA (or loop ID). Refer to
Table 10.1 for the available AL-PA values.
Host mode: Solaris, HP, AIX, Windows, NetWare, etc. Select the host mode for the
connected platform to enable the host to see all LUNs on the port.
Note: If Device Manager cannot recognize the host mode that is specified for the port,
Unknown is displayed.
Modify LUN Group: Opens the Modify LUN Group panel (see section 10.3.2)
Modify WWN Group: Opens the Modify WWN Group panel (see section 10.3.3)
WWN Info button: Displays the WWN(s) registered to the port and the WWN Group to
which each WWN belongs (if any)
267
Port Information Panel for Thunder 9500 V Series: For further information on the 9500V
port settings, please refer to the 9500 V Configuration Guide for the attached platform
(e.g., the Hitachi Thunder 9500 V Series Solaris Configuration Guide), or contact your
Hitachi Data Systems account team.
Topology (Fabric): on or off (you cannot change this item)
Topology (Connection): Loop, or Point-to-Point
Fibre address: In fabric environments, the port address is assigned automatically by

fabric switch port number and is not controlled by the 9500V port settings. In arbitrated
loop environments, the port address is set by entering an AL-PA (also called loop ID).
Refer to Table 10.1 for the available AL-PA values.
Port Option: Optional settings on the port that describe how the host accesses the port.
Multiple options can be selected.
Host Storage Domain Name (LUN Management mode): Displays and allows you to change
the HSD name: maximum of eight characters, cannot begin or end with a space nor
consist of spaces only. It cannot contain full-width characters or half-width Kana
characters, or any of the following characters:
", /, <, >, :, ;, *, ?, |, \, ,
Host mode: Standard, Open VMS, Wolfpack, TRESPASS, etc. Select the host mode for the
Note: If Device Manager cannot recognize the host storage domain or the host mode that
is specified for the port, Unknown is displayed.
268
Extended Host Mode (Host Mode2): Optional settings on the port that describe how the
host accesses the port. Multiple options can be selected.
WWN Info button: Displays the WWN(s) registered to the port
Port Information Panel for Thunder 9200: For further information on the 9200 port
settings, please refer to the 9200 Configuration Guide for the attached platform (e.g., the
Hitachi Thunder 9200 Solaris Configuration Guide), or contact your Hitachi Data Systems
team.
Topology (Fabric): on or off (you cannot change this item)
Topology (Connection): Loop, or Point-to-Point
Fibre address. In fabric environments, the port address is assigned automatically by

fabric switch port number and is not controlled by the 9200 port settings. In arbitrated
loop environments, the port address is set by entering an AL-PA (also called loop ID).
Refer to Table 10.1 for the available AL-PA values.
Port Option: Optional settings on the port that describe how the host accesses the port.
Multiple options can be selected.
Host mode: Standard, Open VMS, Wolfpack, TRESPASS, etc. Select the host mode for the
Note: If Device Manager cannot recognize the host mode that is specified for the port,
Unknown is displayed.
Extended Host Mode (Host Mode2): Optional settings on the port that describe how the
host accesses the port. Multiple options can be selected.
WWN Info button: Displays the WWN(s) registered to the port
269
10.3.2 Managing LUN Groups

The System Administrator and Storage Administrator can manage LUN groups on the 9900
subsystem. Guests, Local System Administrators, Local Storage Administrators, and Local
Guests do not have access to this function.
The Modify LUN Group panel (see Figure 10.26) allows you to add, modify, and delete LUN
groups for each 9900 port. To open the Modify LUN Group panel, open the Port Information
panel for the desired port (see section 10.3.1), and select the MODIFY LUN GROUP button.
Figure 10.26 Modify LUN Group Panel

The Select LUN Group drop-down list box allows you to select the desired LUN group. The
DELETE THIS GROUP button allows you to delete the selected LUN group. The ADD NEW
GROUP button allows you to add a new LUN group to the selected port. The SAVE button
saves your changes on this panel and returns you to the Port Information panel.
270
LUN tab: The Ungrouped list box displays the LUN(s) that can be added to the selected
LUN group. The Grouped list box displays the LUN(s) in the selected LUN group. The
ADD>> button moves the selected LUN(s) to the Grouped list. The <<DELETE button
moves the selected LUN(s) to the Ungrouped list.
WWN tab: The Unsecured list box displays the WWN(s) that can be added to the
selected LUN group. The Secured list box displays the WWN(s) in the selected LUN
group. The ADD>> button moves the selected WWN(s) to the Secured list. The
<<DELETE button moves the selected WWN(s) to the Unsecured list.
WWN Group tab: The Unsecured list displays the WWN group(s) that can be added to
the selected LUN group. The Secured list box displays the WWN group(s) in the selected
LUN group. The ADD>> button moves the selected WWN group(s) to the Secured list.
The <<DELETE button moves the selected WWN group(s) to the Unsecured list.
Add LUN Group. To add a new LUN group:

3. On the Physical View, select the desired port (e.g., for 9900 port CL1-A, click on A in
Cluster 1) to open the Port Information panel.
4. Select MODIFY LUN GROUP to open the Modify LUN Group panel (refer to Figure 10.26).
5. Select ADD NEW GROUP, enter the desired name for the new LUN group, and select OK.
The name must be no more than 8 bytes and consist of Basic_Latin (Unicode 0020 to
007E). It must not contain spaces or any of the following characters:
;, :, ,, /, ", |, *, <, >, ?, \
LUN group names are case-sensitive. You cannot input a name that is already in use.
6. On the LUN tab of the Modify LUN Group panel, add the desired LUN(s) to the new LUN
group: select the desired LUN(s) in the Ungrouped list, and select ADD>> to move the
selected LUN(s) to the Grouped list (see Figure 10.27). If necessary, use the <<DELETE
button to move LUN(s) back into the Ungrouped list.
7. On the WWN tab of the Modify LUN Group panel, add the desired WWN(s) to the new
LUN group: select the desired host WWN(s) in the Unsecured list, and select ADD>> to
move the selected WWN(s) to the Secured list (see Figure 10.28). If necessary, use the
<<DELETE button to move WWN(s) back into the Unsecured list.
8. On the WWN Group tab of the Modify LUN Group panel, add the desired WWN group(s)
to the new LUN group: select the desired WWN group(s) in the Unsecured list, and
select ADD>> to move the selected WWN group(s) to the Secured list (see Figure 10.29).
If necessary, use <<DELETE to move WWN group(s) back into the Unsecured list.
9. When you have added all desired LUN(s), WWN(s), and WWN group(s) to the new LUN
group, select SAVE, or select CANCEL to cancel your request to add a new LUN group.
WARNING: Read the important warning on host access, and make sure to take the
affected LUN(s) (listed on the confirmation panel) offline before continuing.
10. When the confirmation panel appears, select YES to add the new LUN group, or select
NO to cancel your request to add the new LUN group.
271
Figure 10.27 Add New LUN Group Selecting the LUN(s)
Figure 10.28 Add New LUN Group Selecting the WWN(s)
272
Figure 10.29 Add New LUN Group Selecting the WWN Group(s)
Modify LUN Group. To modify an existing LUN group:
5. Select the desired LUN group, and make the desired changes to the LUN group. Select
the LUN tab to add/delete LUN(s), select the WWN tab to add/delete WWN(s), and
select the WWN Group tab to add/delete WWN group(s).
6. When the Modify LUN Group panel displays the desired changes for the selected LUN
group, select SAVE, or select CANCEL to cancel your request to modify the LUN group.
7. WARNING: Read the important warning on host access, and make sure to take the
8. When the confirmation panel appears, select YES to modify the LUN group, or select NO
to cancel your request to modify the LUN group.
273
Delete LUN Group. To delete a LUN group:

Cluster 1) to open the Port Information panel (see Figure 10.24).
5. Select the desired LUN group, select the DELETE THIS GROUP button, and select YES on
the confirmation panel, or select NO to cancel your request to delete the LUN group.
If you selected YES, the LUN group to be deleted is no longer displayed on the Modify
LUN Group panel.
6. When you are finished deleting LUN groups, select SAVE on the Modify LUN Group panel
to delete the LUN group(s), or select CANCEL to cancel your request to delete the LUN
group(s).
7. WARNING: Read the important warning on host access, and make sure to take the
8. When the confirmation panel appears, select YES to delete the LUN group. To cancel
your request to delete the LUN group, select NO on the confirmation panel, and then
select Cancel on the Modify LUN Group panel.
274
10.3.3 Managing WWN Groups

The System Administrator and Storage Administrator can manage LUN groups on the 9900
subsystem. Guests, Local System Administrators, Local Storage Administrators, and Local
Guests users do not have access to this function.
The Modify WWN Group panel (see Figure 10.30) allows you to add, modify, and delete WWN
groups for each 9900 port. To open the Modify WWN Group panel, open the Port Information
panel for the desired port (see section 10.3.1), and select the Modify WWN Group button.
Figure 10.30 Modify WWN Group Panel

The Select WWN Group drop-down list box allows you to select the desired WWN group. The
DELETE THIS GROUP button allows you to delete the selected WWN group. The ADD NEW
GROUP button allows you to add a new WWN group to the selected port. The Unsecured list
box displays the WWN(s) which can be added to the selected WWN group. The Secured list
box displays the WWN(s) in the selected WWN group. The ADD>> button moves the selected
WWN(s) to the Secured list. The <<DELETE button moves the selected WWNs to the
Unsecured list. The SAVE button saves your changes on this panel and returns you to the
Port Information panel.
275
To add a new WWN group:

4. Select MODIFY WWN GROUP to open the Modify WWN Group panel (refer to Figure
10.30).
Select ADD NEW GROUP, enter the name for the new WWN group, and select OK.
The name must be no more than 8 bytes and consist of Basic_Latin (Unicode 0020 to
007E). It must not contain spaces or any of the following characters:
;, :, ,, /, ", |, *, <, >, ?, \
LUN group names are case-sensitive. You cannot input a name that is already in use.
5. On the Modify WWN Group panel select the desired host WWN(s) in the Unsecured list,
and select ADD>> to move the selected WWN(s) to the Secured list. If necessary, use
the <<DELETE button to move WWN(s) back into the Unsecured list.
6. When the Secured list displays the desired WWN(s) for the new group, select SAVE, or
select CANCEL to cancel your request to add a new WWN group.
7. When the confirmation panel appears, select YES to add the new WWN group, or select
NO to cancel your request to add the new WWN group.
To modify an existing WWN group:
4. Select the desired WWN group, and use the ADD>> and <<DELETE buttons to add
WWN(s) to and delete WWN(s) from the selected WWN group.
5. When the Secured list displays the desired WWN(s) for the selected WWN group, select
SAVE, or select CANCEL to cancel your request to modify the WWN group.
6. When the confirmation panel appears, select YES to modify the WWN group, or select
NO to cancel your request to modify the WWN group.
276
To delete a WWN group:

4. Select MODIFY WWN GROUP to open the Modify WWN Group panel (refer to Figure
10.30).
5. Select the desired WWN group, and select the DELETE THIS GROUP button.
6. When the confirmation panel appears, select YES, or select NO to cancel your request to
delete the WWN group.
If you selected YES, the group to be deleted is no longer displayed on the Modify WWN
Group panel.
7. Select SAVE on the Modify WWN Group panel to continue, or select CANCEL to cancel
your request to delete the WWN group.
8. When the confirmation panel appears, select YES to delete the WWN group. To cancel
your request to delete the WWN group, select NO on the confirmation panel, and then
select CANCEL on the Modify WWN Group panel.
277
10.3.4 Configuring the Fibre-Channel Adapters (9900 V, 9900)

WARNING: Before changing the setting of a channel adapter, make sure that the subsystem
is equipped with channel adapters capable of high-speed mode, and that you are aware of
the impact and the procedure for connecting hosts to a channel adapter in high-speed mode.
The System Administrator and Storage Administrator can configure the fibre-channel
adapters on the Lightning 9900 V Series and Lightning 9900 subsystems. Guests, Local
System Administrators, Local Storage Administrators, and Local Guests do not have access to
this function.
The three types of fibre-channel adapters for the Lightning 9900V are 4-port, 8-port, and
16-port adapters. You can set the Fibre PCB mode only for 4-port Fibre Channel adapters.
Standard mode is the default channel adapter mode. High-speed mode provides faster
access speed by using more processors to handle data access. However, high-speed mode
limits the number of available ports on the channel adapter card (one port for 9900V, half of
the ports for 9900). Servers or switches attached to these ports must be changed for this
configuration. Once the subsystem and attached servers or switches are configured for highspeed mode, you can use HiCommand Device Manager to change the mode of the channel
adapter. Please contact your Hitachi Data Systems representative for assistance in planning
and implementing high-speed port access.
For details on the channel adapter settings, please refer to the applicable LUN Manager
Users Guide (Hitachi Lightning 9900 V Series LUN Manager Users Guide (MK-92RD105)).
To configure the speed mode of the fibre-channel adapters in the 9900V or 9900 subsystem:
3. Select Port Controllers to open the Port Controller panel (see Figure 10.31).
4. Make the desired channel adapter mode changes, and select OK.
5. Before changing the Fibre PCB mode, Device Manager displays a warning that you cannot
change the Fibre PCB mode while I/O operations with the host are underway. You must
stop the host, change the Fibre PCB mode, and then restart the host.
After reviewing the information displayed in the warning message and stopping the
hosts, select OK. To cancel your request to change the Fibre PCB mode, select CANCEL.
6. When the confirmation panel appears (see Figure 10.32), review the changes carefully.
Select YES to change the modes as specified, or select NO to cancel your request.
You are notified when the operation is complete. You can now restart the host(s).
278
Figure 10.31 Changing the Channel Adapter Mode (9900 V)
279
Figure 10.32 Changing the Channel Adapter Mode Confirmation
280
10.4 Array Group Operations

The HiCommand Device Manager array group operations include:
Creating an array group on the 9500V and 9200 (see section 10.4.1)
Creating an array group (with or without a spare drive) on the T3 (see section 10.4.2)
Deleting an array group (9500V, 9200, T3) (see section 10.4.3)
Configuring spare drives on the 9500V and 9200 (see section 10.4.4)
10.4.1 Creating an Array Group on the Thunder 9500 V and 9200 Subsystems
The System Administrator and Storage Administrator can create new array groups on the
9500V and 9200 subsystem. Guests, Local System Administrators, Local Storage
When you create a new array group on the 9500V or 9200, you select the RAID level, width,
depth, and disks for the new array group. The spare drives on the 9500V/9200 are configured
separately (see section 10.4.4).
Note: To use a new 9500V or 9200 array group, you must create LDEV(s) in the group (see
section 10.5.3).
WARNING: Make sure that only one Web Client session is creating array groups on the same
9200 subsystem at the same time. If multiple Web Clients are creating multiple array groups
at the same time, this can cause the 9200 to become unavailable to the servers using it.
To create a new array group in an existing Thunder 9500V or 9200 subsystem:
3. Select NEW in the Disks & Arrays box. The Create Array Group panel displays the
current array group configuration (G= disk in an FC drive making up the array group; U=
unused disk in an FC drive; S= spare disk in an FC drive; A_G= disk in an SATA drive
making up the array group; A_U= unused disk in an SATA drive; A_S= spare disk in an
SATA drive).
4. Select the desired RAID level, width, and depth, and then select (check) the disk that
you want to assign as the top disk in the new array group. The other disks are selected
automatically according to the RAID level, width, and depth settings (see Figure 10.33).
5. When the information displayed on the Create Array Group panel is correct, select OK.
6. When the confirmation panel appears (see Figure 10.34), select YES to create the new
array group, or select NO to cancel your request to create a new array group.
281
Figure 10.33 Create Array Group Selecting Array Group Parameters
282
Figure 10.34 Create Array Group Confirmation

Table 10.2
Acceptable RAID Level and Width Value Combinations (9200 and 9500 V)
RAID Level
Width
Thunder 9200
Thunder 9530V and

Thunder 9570V
Thunder 9580V and

Thunder 9585V
RAID0
2D to 5D
2D to 11D
2D to 16D
RAID0+1
2D + 2P
2D + 2P
2D + 2P
3D + 3P
3D + 3P
4D + 4P
4D + 4P
5D + 5P
5D + 5P
6D + 6P
7D + 7P
8D + 8P
RAID1
RAID5
1D + 1P
(2D to 4D) + 1P
(2D to 10D) + 1P
(2D to 15D) + 1P
283
284
Table 10.3
Acceptable RAID Level and Depth Value Combinations (9200 and 9500 V)
RAID Level
Depth
Thunder 9200
Thunder 9530V and

Thunder 9570V
Thunder 9580V and

Thunder 9585V
RAID0
1 to 2
1 to 5
1 to 222
RAID0+1
1 to 2
1 to 111
RAID1
1 to 2
1 to 5
1 to 222
RAID5
1 to 3
1 to 148
10.4.2 Creating an Array Group on the StorEdge T3 Array

The System Administrator and Storage Administrator can create new array groups on the T3
array. Guests, Local System Administrators, Local Storage Administrators, and Local Guests
do not have access to this function.
A single T3 array can have a maximum of two array groups, one LDEV per array group, and
one spare drive (drive 9 only). When you create a new array group on the T3, you select the
RAID level, width, and disks for the new array group. If desired, you can also create a spare
drive at the same time as the new array group (if drive 9 is available).
On the T3, you can only define a spare drive at the same time that you create an array
group. If you create two array groups on the array, the spare drive is available to both array
groups and can back up either group in case of a drive failure, but the spare drive is still
associated with one of the array groups. If you delete the array group with which the spare
drive was created, the spare drive is also deleted. As a result the remaining array group can
no longer use the spare drive. You must create a second array group with the spare drive to
regain use of the spare drive.
Note: Array group creation on the T3 array may take a while (up to an hour) to complete,
depending on the size and RAID type of the array group being creating. This performance is
the same as when you create an array group using the T3s management interface.
Note: To use the new array group, you must create an LDEV in the group (see section
10.5.3).
To create a new array group for the StorEdge T3 array (with or without a spare drive):
3. Select NEW in the Disks & Arrays box. The Create Array Group panel displays the
current array group configuration (G=grouped, U=unused, S=spare).
4. Select the desired RAID level and width, and select (check) the unused disk that you
want to assign as the top disk in the new array group. The other disks are automatically
selected according to the RAID level and width selections (see Figure 10.35).
5. If you want to create a spare drive with the new array group, check the Use Spare box.
6. When the information displayed on the Create Array Group panel is correct, select OK.
7. When the confirmation panel appears (see Figure 10.36), select YES to create the new
array group, or select NO to cancel your request to create a new array group.
285
Figure 10.35 Create Array Group (T3)
Figure 10.36 Create Array Group (T3) Confirmation

286
Table 10.4
Acceptable RAID Level and Width Value Combinations (T3)
RAID Level
Width
RAID0
3 to 9
RAID1
3 to 9
RAID5
2 to 9
10.4.3 Deleting an Array Group (9500 V, 9200, and T3)

WARNING: The delete array group operation is destructive. The data stored on the devices
in the array group will be lost. The user is responsible for backing up the data before
performing this operation.
The System Administrator and Storage Administrator can delete an array group on the 9500V
subsystem, 9200 subsystem, and T3 array. Guests, Local System Administrators, Local
Storage Administrators, and Local Guests do not have access to this function. When you
delete an existing array group, the data on the disks in the array group is deleted, and the
disks are then displayed as unused disks.
You cannot delete an array group that contains a logical device. To delete such an array
group, make a backup of the data, and then delete the logical device(s) from the array
group (see section 10.5.4).
Caution: For the T3, if you created a spare drive concurrently with the array group, deleting
the array group also deletes the spare drive. In such a case, remaining array groups can no
longer use the spare drive.
To delete an array group on the 9500V, 9200, or T3 array:
2. Make sure that the LDEVs in the array group to be deleted are no longer in use and have
been backed up and deleted.
4. In the Disks & Arrays box, select the array group that you want to delete, and then
select DELETE.
selected array group, or select NO to cancel your request to delete an array group.
6. Device Manager displays a warning message. Check the warning message carefully. If it is
acceptable to delete the array group and lose the data, select the OK button. To cancel
your request to delete the array group, select CANCEL.
287
Figure 10.37 Delete Array Group Confirmation
10.4.4 Configuring Spare Drives on the Thunder 9500 V and 9200 Subsystems
The System Administrator and Storage Administrator can configure (add and release) the
spare drives on the 9500V and 9200 subsystems. Guests, Local System Administrators, Local
Storage Administrators, and Local Guests do not have access to this function.
When you configure the spare drives on the 9500V/9200, you can add new spare drive(s)
and/or release existing spare drive(s). When you release a spare drive, the drive changes to
unused and is available for assignment to a new array group.
Note: The following shows the maximum number of spare drives.
For Thunder 9585V (microcode 1658 or later) and Thunder 9580 V (microcode 1658 or
later): 30
For Thunder 9585V (under microcode 1658) and Thunder 9580 V (under microcode
1658): 15
For Thunder 9570V and Thunder 9530 V: 15
For Thunder 9200: 5
In the case of a T3, you create and delete the spare drive when you create or delete an
array group (see sections 10.4.2 and 10.4.3).
To add and/or release one or more spare drives in a 9500V or 9200 subsystem:
3. Select SPARE in the Disks & Arrays box. The Spare Drive panel displays the current
spare drive configuration (see Figure 10.38).
4. Select (check) the unused disk(s) that you want to configure as new spare drive(s), and
deselect (uncheck) the spare drive(s) that you want to release.
Caution: You cannot use disks 0-4 in UNIT0 as spare drives.
288
Caution: If an array group has been created, the size of the disk that is specified as a
spare drive must at least equal the size of the existing array group (minimum size of a
physical disk that constitutes the array group).
Note: An error is displayed if the physical disk specified for a spare drive is smaller than
the physical disk used for the array group. Use the DAMP to check the size of the disk
used for the array group, and make sure to specify a spare drive with the same or larger
capacity.
An attempt to create a spare drive may result in the error DMES059542: The specified
drive cannot be used as a spare drive. In such a case, use the DAMP to check the
physical disk size, then specify for the spare drive a disk that is at least as large.
5. When the information on the Spare Drive panel is correct, select OK, or select Cancel to
cancel your request to create/release spare drive(s).
Figure 10.38 Spare Drive Panel (9500V)
289
10.5 LDEV Operations

The HiCommand Device Manager LDEV operations include:
Allocating storage (see section 8.4)
Unallocating storage (see section 8.5)
Creating an LDEV (see section 10.5.3)
Deleting an LDEV (see section 10.5.4)
Setting a command device (see section 10.5.5)
Note: To perform operation on a port for TagmaStore USP, use the Physical View for
TagmaStore USP (see section 10.2.1).
10.5.1 Allocating Storage (Adding Volume Paths)

System Administrators and Storage Administrators can allocate storage. Guests, Local System
Administrators, Local Storage Administrators, and Local Guests do not have access to this
function.
When you allocate storage, you assign one or more access paths (port/LUN) to LDEV(s), and
you can optionally secure the new LUN(s) to host WWN(s). You can allocate LDEVs that are
unallocated or already allocated.
To allocate storage:
Administrator.
2. Select and expand the Subsystems object in the navigation frame, open the Physical
View for the desired subsystem, and then open the LDEV Information panel for the array
group that contains the LDEV(s) that want to allocate (see section 10.2.7).
Note: You can also allocate storage by starting from the All Storage/My Storage object
(see section 8.4). Under All Storage/My Storage, select the desired subsystem, and then
select the storage group (Allocated or Unallocated) that contains the desired LDEV(s).
3. Select the desired LDEV, and then select Allocate to open the Add Storage wizard.
4. Define Host/Port Connections Step. The Define Host/Port Connections panel (see
Figure 10.39) allows you to select the desired port(s) and (optionally) the desired host
WWN(s) to secure to the LDEV. After defining the port(s) and host/port connection(s),
select Next to continue.
5. Assign Host/Port Connections Step. The Assign Host/Port Connections panel (see Figure
10.40) allows you to assign the LDEV to the desired port(s) and/or host/port
connection(s). After assigning the desired connection(s), select Next to continue.
6. Assign LUNs Step. The Assign LUNs panel (see Figure 10.41) allows you to assign the
desired LUN to each new path. You can use the preselected LUN or select the desired
LUN for each path. After assigning the desired LUN(s), select Finish to continue.
290
the requested allocate storage operations and asks you to confirm the requested
operations. If you need to make any changes, select Back to return to the previous
panel(s). Select Confirm to add the specified path(s) to the LDEV, or select Cancel to
cancel your request to allocate storage.
Figure 10.39 Allocate Storage Define Host/Port Connections
291
Figure 10.40 Allocate Storage Assign Host/Port Connections
Figure 10.41 Allocate Storage Assign LUNs
292
Figure 10.42 Allocate Storage Confirmation
293
10.5.2 Unallocating Storage (Removing Volume Paths)

System Administrators and Storage Administrators can unallocate storage. Guests, Local
System Administrators, Local Storage Administrators, and Local Guests do not have access to
this function.
When you unallocate storage, you remove one or more access paths from an LDEV. When you
unallocate a LUSE device, you can also optionally delete the LUSE device to make the
individual LDEVs available for use.
For the Lightning 9900 V, you cannot unallocate the last volume path from a logical device
that is specified as a copy pair volume.
For the Lightning 9900, you cannot unallocate the last volume path from a logical device
that is specified as a command device or as a copy pair volume.
For the Thunder 9500 V (microcode before 0655) and Thunder 9200, you cannot
unallocate any volume paths from a logical device that is specified as a command device or
as a copy pair volume.
Note: If you want to unallocate LUNs for more than one LDEV/LU, use the Allocated group
for the subsystem (see section 8.5). If you use the Physical View, you can only unallocate
LUNs for one LDEV at a time.
To unallocate storage:
1. Log in to HiCommand Device Manager as a System Administrator, or Storage
Administrator.
group that contains the LDEV(s) that want to unallocate (see section 10.2.7).
Note: You can also unallocate storage by starting from the All Storage/My Storage
object (see section 8.4). Under All Storage/My Storage, select the desired subsystem,
and then select the Allocated storage group.
3. Select the desired LDEV, and then select Unallocate. If you started from All Storage/My
Storage, you can select multiple LDEVs to unallocate (see section 8.4).
specified path(s), or select NO to cancel your request to unallocate storage.
5. If you selected LUSE device(s), Device Manager allows you to keep or delete the LUSE
device(s) (see Figure 10.44). Select Delete LUSE to delete the LUSE device(s) and the
path(s), or select Keep LUSE to keep the LUSE device(s) and delete only the path(s).
You are notified when the unallocate storage operation is complete.
294
Figure 10.43 Unallocate Storage Confirmation
Figure 10.44 Unallocate Storage Delete LUSE or Keep LUSE
295
10.5.3 Creating an LDEV

The System Administrator and Storage Administrator can create an LDEV on an array group.
When you create an LDEV, you select an existing array group with free space and specify the
desired LDEV parameters: device size and emulation type for 9900 V and 9900, device size
and controller for 9500 V and 9200. There are no parameters to be specified for T3.
HiCommand Device Manager automatically adds the new LDEV to the Unallocated group for
the subsystem (in All Storage or My Storage). Logical devices created using Web Client are
formatted when they are created.
WARNING: Make sure that only one Web Client session is formatting LUs on the same 9200
subsystem at the same time. If multiple Web Clients are formatting multiple LUs at the same
time, this can cause the 9200 to become unavailable to the servers using it.
Caution: While the restore processing is underway using CCI of a Lightning 9900 subsystem,
logical device creation on that Lightning 9900 will result in an error. Logical device
creation must not be executed while restore processing is underway using CCI.
For the 9900V and 9900 subsystems, you can create an LDEV that is a standard LU, or you
can create a custom-size LDEV that is smaller than the standard LU (minimum capacity
36 MB). Table 10.5 lists the maximum capacities for the standard LU types on the 9900V and
9900 subsystems.
Note: LUSE devices, which are larger than standard LU types, are created from existing
unallocated LDEVs (see section 7.6.2 or 8.6).
In addition to the listed emulation types, the Lightning 9900V supports another emulation
type called OPEN-V that enables you to create a logical device whose size is (maximum size
of free space - size required for the control area). The size required for the control area
depends on the size of the volume to be created (maximum of 200 MB).
Table 10.5
Maximum Capacities of Standard LU Types
LU Type
OPEN-K
OPEN-3
OPEN-8
OPEN-9
OPEN-E
Maximum Capacity
1788 MB
2347 MB
7007 MB
7042 MB
13893 MB
Note: The 9900V and 9900 subsystems may not support the same LU types. Some LU types
are not available on some platforms. Please ask your Hitachi Data Systems representative for
the latest information on LU type support.
HiCommand Device Manager uses the following convention for capacity values:
KB = 1024 bytes
MB = 1024 KB
GB = 1024 MB
TB = 1024 GB
296
To create a new LDEV:

group in which you want to create a new LDEV (see section 10.2.7):
For 9900V, select Array Groups, select View on the desired frame, select the
desired parity group on the Frame Information (level 1) panel, and then select the
desired array group on the Frame Information (level 2) panel.
For 9900, select Array Groups, select View on the desired frame, and then select
the desired array group on the Frame Information panel.
For 9500V and 9200, select the desired array group, and then select VIEW.
For T3, select the desired array group under Array Groups, and then select VIEW.
3. On the LDEV Information panel for the desired array group (any tab), select the CREATE
LDEV button (refer to Figure 10.21).
4. For 9900V, 9900, 9500V, and 9200, the Create LDEV panel opens (see Figure 10.45).
Enter the desired parameters, and then select OK.
For 9900V/9900, select the device emulation type, and enter the desired device size
(refer to Table 10.5). The size cannot be larger than the size of the selected device
type, except for OPEN-V (refer to the Hitachi Lightning 9900 V Series LUN Manager
User's Guide (MK-92RD105) for details).
For 9500V/9200, enter the desired device size, and select the desired default
controller.
Note: The LDEV capacity will be equal to or larger than the specified device size,
because the device size is rounded up at the 9500V/9200 subsystem.
Note: The Create LDEV panel is not displayed for T3, because the device size is
preset to the array group size.
5. When the confirmation panel appears (see Figure 10.46), select YES to create the LDEV,
or select NO to cancel your request to create the LDEV.
You are notified you when the operation is complete and displays the LDEV ID of the new
LDEV. The new LDEV is displayed on the LDEV Information panel and is also listed in the
Unallocated group for the subsystem (under All Storage or My Storage).
297
Figure 10.45 Create LDEV Specifying the LDEV Parameters (9900 V)
Figure 10.46 Create LDEV Confirmation
298
10.5.4 Deleting an LDEV

WARNING: The delete LDEV operation is destructive. The data on the LDEV to be deleted
will be lost. The user is responsible for backing up the data before performing this
operation.
The System Administrator and Storage Administrator can delete LDEVs. Guests, Local System
Administrators, Local Storage Administrators, and Local Guests do not have access to this
function.
When you delete an LDEV, the free space in the array group increases by the size of the
LDEV deleted. The following LDEVs cannot be deleted:
An LDEV to which a volume path is assigned
An LDEV used as a command device
An LDEV specified as a copy volume (P-VOL, S-VOL, or SP-VOL)
An LDEV that has been set as a LUSE volume in a Thunder 9500V or 9200
In a Thunder 9500V or Thunder 9200, you can delete only the last LDEV that was created.
To delete an LDEV:
2. Make sure that the LDEV to be deleted is no longer in use, that the data has been backed
up, and that all access paths to the LDEV have been removed.
group in which you want to delete an LDEV (see section 10.2.7):
For 9900V, select Array Groups, select View on the desired frame, select the
desired parity group on the Frame Information (level 1) panel, and then select the
desired array group on the Frame Information (level 2) panel.
For 9900, select Array Groups, select View on the desired frame, and then select
the desired array group on the Frame Information panel.
For 9500V and 9200, select the desired array group, and then select VIEW.
For T3, select the desired array group under Array Groups, and then select VIEW.
4. On the LDEV Information panel for the desired array group, select the desired LDEV, and
then select the DELETE LDEV button (refer to Figure 10.21). If the DELETE LDEV button
is not available, one or more paths to the LDEV still exist.
5. When the confirmation panel appears (see Figure 10.47), select YES to delete the LDEV,
or select NO to cancel your request to delete the LDEV.
6. Device Manager displays a warning message. Check the warning message carefully. If it is
acceptable to delete the LDEV and lose the data, select the OK button. To cancel your
request to delete the LDEV, select CANCEL.
299
Figure 10.47 Delete LDEV Confirmation
10.5.5 Setting a Command Device

The System Administrator and Storage Administrator can set and cancel a command device
on a Hitachi storage subsystem. Guests, Local System Administrators, Local Storage
A command device is an LU dedicated to communication between the Command Control
Interface (CCI) software installed on the host and the Hitachi storage subsystem. CCI enables
the user to issue ShadowImage, TrueCopy, Data Retention, and Open LDEV Guard commands
from the host to the subsystem via the command device.
Note: The T3 does not support command devices.
If you are setting a command device on the Lightning 9900V or 9900, or Thunder 9500V, you
can also set security for the command device. This LUN security setting enables you to limit
the logical devices that can be used as a command device to ones that are identified by the
host and to prevent unwanted access from the server host(s) that utilize the device.
To specify a logical device as a command device, the logical device must satisfy the
following conditions:
300
For the Lightning 9900V and Lightning 9900:
A volume path must be assigned to the logical device (9900 only).
The logical device must not be reserved for Hitachi CruiseControl.
The device emulation type must be an OPEN-x type (e.g., OPEN-3, not 3390-3C).
There is no limitation on the number of command devices per subsystem.
Command device security can be set. For 9900, when you delete a command device,
its security properties are released. You cannot set or release only the security
properties of a 9900 command device.
For the Thunder 9500V and Thunder 9200:
The minimum capacity for the logical device is 33 MB.
The logical device must not be a LUSE volume or within a LUSE volume.
The maximum number of command devices is two per storage subsystem.
A volume path for a command device cannot be deleted. However, when you use the
Thunder 9500 V (microcode 0655 or later), a volume path for a command device
can be deleted.
When you use Thunder 9500V (microcode X657/A or later), you can set command
device security. When you use Thunder 9200, or versions of Thunder 9500V with
microcodes earlier than X657/A, you cannot set command device security.
To set or cancel a command device:

then select the Physical View button to open the Physical View.
3. From the Physical View, open the LDEV Information panel for the array group containing
the LDEV that want to set or cancel as a command device (see section 10.2.7).
4. On the LDEV Information panel, select the logical device that you want to set or cancel
as a command device, and select the LDEV CONFIG button to open the LDEV
Configuration panel (see Figure 10.48 and Figure 10.49).
5. To set the device as a command device, select Use this LDEV as a command device.
To cancel a command device, clear the Use this LDEV as a command device checkbox.
6. Lightning 9900V, Thunder 9500V, and Lightning 9900 only: To set security for the
command device, select Assign Command Device Security. To cancel the security
setting, clear the Assign Command Device Security box.
Note: For the 9900, you can specify command device security only while you are setting
a command device. To specify security for a device that has already been defined as a
command device, you must first cancel its setup as a command device, and then reset
the command device with the desired command device security setting.
7. Select OK to save your changes and close the LDEV Configuration panel, or select
CANCEL to close the LDEV Configuration panel without saving any changes. When the
command device operation completes, Device Manager displays a confirmation panel.
301
Figure 10.48 LDEV Configuration Set Command Device
Figure 10.49 LDEV Configuration Set Command Device
302
Chapter 11 Performing Report Operations

This chapter describes the different types of HiCommand Device Manager reports that you
can run:
Overview of HiCommand Device Manager Reports (see section 11.1)
Physical configuration of storage subsystem (see section 11.2)
Storage utilization by host (see section 11.3)
Storage utilization by logical group (see section 11.4)
Users and permissions (not available to guest users) (see section 11.5)
303
11.1 Overview of HiCommand Device Manager Reports

The HiCommand Device Manager System users can perform report operations. Local users
do not have access to this function.
To access the reports, select the Reports object in the Device Manager navigation frame
(see Figure 11.1). The Reports subwindow in the information frame lists and provides access
to the HiCommand Device Manager reports. The reports are available in HTML format or
comma-separated value (CSV) format which can be used in a spreadsheet program (e.g.,
Microsoft Excel software).
Note on Unicode (UTF-8) for CSV reports: Device Manager uses the Unicode (UTF-8) code
system to output reports in CSV format. If the output CSV file contains Japanese characters
and is imported to a spreadsheet program that does not support Unicode (UTF-8), the
displayed information may contain code system errors. In such a case, open the file with a
program that supports Unicode (UTF-8), such as Windows Notepad, and then convert it to
the appropriate character code system.
Note: If you repeat CSV output for the report facility, the font size on the Web browser may
change. This has no adverse effect on the program, and you can continue operations.
304
Figure 11.1 Reports
305
11.2 Physical Configuration of the Storage Subsystem Report

The Physical Configuration of Storage Subsystem report displays and provides detailed
information on the physical configuration of each subsystem added to the HiCommand
Device Manager Server. The HTML report (see Figure 11.2) shows a graphic representation of
the subsystems configuration and components. The CSV report (see Figure 11.3) provides
the detailed subsystem information as comma-separated values.
Figure 11.2 Physical Configuration of Storage Subsystem Report HTML
306
Figure 11.3 Physical Configuration of Storage Subsystem Report CSV
307
11.3 Storage Utilization by Host Report

The Storage Utilization by Host report displays storage utilization statistics and detailed
storage information for each host added to the HiCommand Device Manager Server (see
Figure 11.4). The storage utilization statistics for each host include capacity (GB) currently
in use by host operating system(s) and percentage of capacity in use by host(s). The storage
information for each host includes allocated storage displayed by storage group and LUN.
Note: The host Agent provides the storage utilization statistics. If the Agent is not installed
on a host, Device Manager will not receive storage utilization statistics for that host.
Figure 11.4 Storage Utilization by Host Report (HTML)
308
11.4 Storage Utilization by Logical Group Report

The Storage Utilization by Logical Group report (see Figure 11.5) displays the following
information:
For each subsystem added to the HiCommand Device Manager Server: subsystem name,
model, serial number, IP address, configured capacity, allocated capacity, and
percentage of allocated capacity in use by the host operating system(s).
For each logical group added to the HiCommand Device Manager Server: group name
and level, capacity, and percentage of capacity in use by the host operating system(s).
Note: The host Agent provides the storage utilization statistics. If the Agent is not installed
on a host, HiCommand Device Manager will not receive utilization data for the storage
accessed by that host.
Figure 11.5 Storage Utilization by Logical Group Report (HTML)
309
11.5 Users and Permissions Report

The Users and Permissions report (see Figure 11.6) displays the following information for the
HiCommand Device Manager users:
User groups managed by the HiCommand Device Manager Server. (The Peer group is
reserved for use by the Device Manager Agent only.)
Number of users in each group
Properties of each user (login name, last name, first name, description)
Figure 11.6 Users and Permissions Report (HTML)
310
Chapter 12 Troubleshooting
This chapter describes Web Client troubleshooting:
Information on troubleshooting operations (see section 12.1)
General information on troubleshooting (see section 12.2)
Information on warning messages output from Device Manager (see section 12.3)
Information on error messages (see section 12.4)
Information on calling the Support Center (see section 12.5)
311
12.1 Troubleshooting Operations

If there is a problem with the HiCommand Device Manager Web Client interface, first make
sure that the problem is not being caused by the PC or LAN hardware or software, and try
restarting the PC.
312
For general troubleshooting information for the Device Manager Web Client, see section
12.2.
For information on the warning messages output by Device Manager Web Client, see
section 12.3.
For a description of the error messages displayed by the Web Client, see section 12.4.
If you need to call the Hitachi Data Systems Support Center, see section 12.5 for
instructions.
12.2 General Troubleshooting

If you are having trouble with the HiCommand Device Manager Web Client, first make sure
the problem is not occurring at the HiCommand Device Manager Server. Please refer to the
HiCommand Device Manager Server Installation and Configuration Guide (MK-91HC002) for
further information on troubleshooting HiCommand Device Manager Server problems.
Important: Make sure to read the HiCommand Device Manager ReadMe file. Always make
sure that only one HiCommand Device Manager Server at a time is actively managing a
single subsystem.
Table 12.1 provides general troubleshooting information for the HiCommand Device
Manager Web Client. In general, difficulties installing and running the Web Client can be due
to problems with the Java Web Start software and/or with proxies on the local network.
Table 12.1
General Troubleshooting Information (continues on the following pages)
Problem
Description
Cannot find the HiCommand Device

Manager Server login window.
Make sure that the HiCommand Device Manager Server system and software
are up and running.
When running the Web Client on the same system as the Server, a potential
hazard is the resolution of the host localhost. Generally localhost resolves to the
loopback address (127.0.0.1), which can cause problems for the Java Web Start
software. Use the primary local IP address instead.
Cannot load the HiCommand Device

Manager Server home page. Error
message: The requested item could not
be loaded by the proxy. Proxy servers
network connection was refused by the
server: <IP address>:<port number>.
The server may not be accepting
connections or may be busy. Try
connecting again later.
The browser may have a proxy in place that is not allowing the traffic to go
through.
For Internet Explorer browser: Go to Tools->Internet Options, select Connections,
select LAN Settings button, then select the Advanced button on the Local Area
Network (LAN) Settings. In the Exceptions section, enter the IP address of the
Device Manager Server (123.456.78.9). Entries must be separated by semicolons.
Click OK all the way out, and restart the browser.
For Netscape browser: select Edit > Preferences, select Advanced category,
click on + to expand, and select Proxies. Select Manual Proxy Configuration,
and select View. Enter the IP address in the box under Exceptions.
Note: If the browser is not set to Use a proxy server, this is not the source of the
problem. Look for other network connectivity issues such as firewalls and routers.
Solaris installation fails with

messages InterBase Server was not
properly installed. Try re-installing
InterBase Server... and InterClient was
not installed properly.
You may be using the graphical installation mode without an adequate windowing
environment on your system, or without the executable /usr/dt/bin/dtterm in your
path. Use the command-line installation mode instead by invoking the installer from
a command prompt.
The File Download panel appears when

you invoke the Java GUI.
The Java Web Start software may have been previously installed and removed.
When JWS was removed, the association between the file extension .JNLP and
the JWS application may not have been removed. When the link to the .JNLP file is
selected, the operating system tries to run but does not find JWS. To resolve this
situation, run the installer for JWS again (the full Java Web Start Installer).
Cannot add subsystem. Failed during

initialization (was unable to find the
device).
Verify that you can you ping the IP address from the HiCommand Device
Manager Server workstation (not client workstation).
DESCRIPTION: Add Subsystem fails

with error message: Failed during
initialization of SNMP connection at IP
Address 123.456.78.9 CAUSE:
For example:
/cdrom/cdrom0/solaris/install.sh -i console
Verify the SNMP configuration on the SVP, and make sure that the correct
community name is specified in HiCommand Device Manager (should match
community name entered when configuring the SNMP Agent). A common
community name is public (HiCommand Device Manager default). Make sure
that Access by IP address is not limited, or Access is limited by IP address and the
313
Cannot connect to the device.
HiCommand Device Manager Server is added to the list.

For further information on SNMP troubleshooting for HiCommand Device
Manager, please refer to the HiCommand Device Manager Server Installation
and Configuration Guide (MK-91HC002). For further information on USP, 9900 V,
and 9900 SNMP configuration, please refer to the Remote Console Users Guide
for the subsystem.
Subsystem discovery does not complete

successfully.
For USP, 9900 V, and 9900, make sure that another management tool (e.g.
Storage Navigator, Remote Console) is not connected to the subsystem.
HiCommand Device Manager and another management tool cannot both access
the same subsystem at the same time.
Cannot connect with storage

subsystem.
On the HiCommand Device Manager Server check for LAN problems and/or
SNMP problems. Please refer to the HiCommand Device Manager Server
Installation and Configuration Guide for further information on SNMP
troubleshooting.
Make sure that the USP, 9900 V, or 9900 SVP is in View mode.
Very slow subsystem discovery process.
Microcode level on 9900 does not support FTP transfer mechanism. The FTP port
in 9900 SVP must be enabled. To start up FTP daemon, left click on ftp demon
icon in task bar.
Note: The FTP daemon is not usually running on the SVP.
314
9900 subsystem discovery does not

finish.
HiCommand Device Manager may not be able to connect to the 9900 subsystem
by SNMP. Please contact your network administrator.
Slow SNMP response.
Microcode level on subsystem does not support command complete.
Cannot add/delete volume paths.

Cannot convert unallocated LUs.
For USP and 9900, make sure that the LUN Manager feature is enabled.
Cannot secure/unsecure LUs.
Make sure that the LUN security feature is enabled:

For USP LUN Manager
For 9900V LUN Management
For 9900 LUN Security (Hitachi SANtinel)
For 9500V LUN Security or LUN Management
For 9200LUN Security
Java GUI does not receive alert

messages from HiCommand Device
Manager Server.
Make sure that the Java Web Start software has been configured for
Client/Server operations (do not use proxy) as described in section 3.4.
You entered the correct password, but

HiCommand Device Manager tells
you that the password you entered was
not correct.
Log off and then log back in to HiCommand Device Manager, making sure to
enter the correct password on the HiCommand Device Manager Login panel. Do
not use the Java Web Start User Authentication panel. Always log in using the
HiCommand Device Manager Login panel.
The error The storage array is under

configuring by another user is output on
USP or 9900V operation.
Please wait at least 5 minutes, and then retry. If this error continues to occur,
please contact the Hitachi Data Systems Support Center.
The create LDEV operation on a T3

takes a very long time (e.g., an hour).
HiCommand Device Manager may determine that the array group needs to be
initialized and will initialize it. This can take up to an hour to perform. Normally it is
not necessary, and the create LDEV operation will complete quickly.
The Dynamic Link Manager button is

not displayed in the Host view.
When HDLM is installed on the host, the Device Manager Server receives
notification from a Device Manager Agent and recognizes that HDLM is installed in
that host. Therefore, if the Device Manager Server is not running when a Device
Manager Agent starts, the Dynamic Link Manager button is not displayed on the
Show Properties - Host Name subwindow for the host. In this case, make sure that
the Device Manager Server is running, and restart the Device Manager Agent. It
For 9900V, make sure that the LUN Management feature is enabled.
For the Thunder 9500V, make sure that the LUN Security or LUN Management
feature is enabled.
For 9500V and 9200 make sure that the Resource Manager feature is enabled and
that the microcode level is correct.
takes a few minutes for the Device Manager Server to recognize HDLM after the
Agent starts. Wait for a while, and refresh the Show Properties - Host Name
subwindow.
The Protection Manager button is not
displayed in the Host view.
When the Protection Manager is installed on the host, the Device Manager Server
receives notification from a Device Manager Agent and recognizes that the
Protection Manager is installed in that host. Therefore, if the Device Manager
Server is not running when a Device Manager Agent starts, the Protection
Manager button is not displayed on the Show Properties - Host Name subwindow.
In this case, make sure that the Device Manager Server is running, and restart the
Device Manager Agent. It takes a few minutes for the Device Manager Server to
recognize the Protection Manager after the Agent starts. Wait for a while, and
refresh the Show Properties - Host Name subwindow.
The window display for Web Client fails.
The window display in Web Client might fail (e.g., when the specific data display
area in size increases). In this case, refresh the window, or restart Web Client.
The pair operation of the host cannot be

performed.
When a pair is created if the IP address is set in the

server.horcmconfigfile.hostname of the server.properties, the pair operation
cannot be performed when you change the host IP address or host name.
Perform the following procedure to refresh the storage subsystem:
1. Modify the configuration definition file on the host.
2. Restart the Device Manager agent on the host.
3. Modify the configuration definition file on the other host of the pair.
For details on the server.properties setting, see the HiCommand Device
Manager Server Installation and Configuration Guide.
Copy pair functions (e.g.,

Create Pair button) do not appear for
the 9500V.
Check the following:

CCI must be installed on the host being managed from Device Manager.
Run the agent on the host setting the server.properties file.
Check the switch zoning.
Make sure that the command device is not mounted.
Restart the Agent, and run hiscan to the Device Manager Server.
Refresh the subsystem, and then perform a LUN Scan.
Read the horcm.conf.txt file located on the server on which CCI is installed, in the
c:\HORCM\etc\horcm.conf directory (see the description of the MU# field).
If you still cannot resolve the problem, please contact the Hitachi Data Systems
Support Center.
A gray window with no text or buttons is

displayed.
When a Web Client machine uses the NVIDIA GeForce2 GTS video card, this
problem can occur due to a problem in the video driver. If this problem occurs,
move the window so that the window text is off the screen, and then pull it back to
the center of the screen to display it again.
To work around this issue until NVIDIA provides an updated driver, perform the
following steps:
a) Shut down the HiCommand Device Manager Web Client.
b) Open the Display control panel.
c) Under the Settings tab, click the Advanced button.
d) Under the Troubleshooting tab, move the slider bar all the way to the left,
towards NONE.
e) Save the new setting.
f) Restart the HiCommand Device Manager Web Client.
315
An error occurs when a copy pair is

created.
During the pair creation, when the Device Manager Agent cannot create a
configuration definition file, cannot start the HORCM (CCI) instance, or cannot execute
the pair creation command, an error (error code: 7774) occurs:
This ConfigFile could not be modified.
Cause: The inconsistency occurred between the host status and the Device
Manager server database. The LU number, TID, and port number from DevNum
and Serial cannot be resolved since the device does not recognize the target
LDEV for the pair creation.
Action: Refresh the storage subsystem or execute HiScan on the host to update
the database.
This HORCM instance could not be started.
Detailed message: starting HORCM inst 111 HORCM inst 111 has failed to start.
Cause 1: The port being used has been specified in the port number of the
instance.
Action 1: Check the port number usage by using the command such as the netstat
command, and then specify the unused port number.
Cause 2: The disk capacity is insufficient.
Action 2: Confirm the free space by using the command such as the df command,
and then reserve the disk capacity by using a method such as deleting any
unnecessary files.
Could not create pair "pair-name":"group-name".
Detailed message: paircreate: [EX_CMDIOE] Control command I/O error Refer to
the command log(/HORCM/log123/horcc_japan.log) for details.
Cause 1: The number of the pairs that were created on the device reaches the
maximum number of pairs. For the TagmaStore USP, Lightning 9900 V, and
Lightning 9900, you can create more than 1000 pairs. However, for Thunder
9500 V and Thunder 9200, you can create a maximum of 31 pairs.
Action 1: Delete any unnecessary pairs. Use SVP, Storage Navigator, and DAMP
to check the number of pairs.
Cause 2: The remote path is taken offline when using TrueCopy.
Action 2: Use SVP, Storage Navigator, and DAMP to check the remote path
status. The [EX_CMDIOE] in the detailed message indicates the CCI error
message. For details, see the CCI manual.
316
The pair operation time-out occurs.
During the pair operation, if the host that recognizes the pair is shut down or the agent
stops, the pair operation time-out will occur within 15 minutes. Re-try the pair operation
after the host and the agent are restarted.
The pair operation or the display of

the pair information cannot be
performed when a storage
subsystem is added or its
information is refreshed.
When you add or refresh a storage subsystem, the information about the pair that
each host recognizes and the information about the configuration definition file is also
updated. If the host is stopping or the communication cannot be performed
successfully, the information about the pair that each host recognizes and the
information about the configuration definition file might be lost. When you cannot
perform the pair operation or the display of the pair information, check the host
settings, and then refresh the storage subsystem.
When a Device Manager server is

running in a cluster environment, the
Web Client operation error occurred
abruptly or the operation being
executed resulted in an error.
If failover occurs when a Device Manager server is running in a cluster environment,

the Web Client operation error occurs. In this case, log in Web Client again.
The operation being executed also results in an error. If that operation relates to the
configuration modification for the storage subsystem, refresh the storage subsystem
after logging in Web Client again, and then check the operation result.
On the host in a cluster

environment, the information about
the file system displayed in Web
Client becomes incorrect.
In a cluster environment, when the error occurs in the active host and the standby host
inherits the operation being executed, the file system information might remain in the
window that displays the properties on the active host.
Physical View does not display.
Verify the Java software environment (see section 3.3). If necessary, remove the
Java software, reboot, and reinstall the Java software (see section 3.3).
After upgrading the Web client, all

the volumes in each logical group
appear as CVS volumes, and no
disk usage information is displayed.
This occurs when you install HiCommand Device Manager version 3.1 over version
1.1 (or earlier). To correct, perform a REFRESH for all storage subsystems that were
discovered by the previous version of HiCommand.
Error dialog, disconnection from

server is not always displayed.
Depending on your network environment, this message may not always display if the
Java application of the Web Client is disconnected from a HiCommand Device
Manager server.
The Web client becomes disabled

after pressing the Escape [Esc] key.
Do not use the [Esc] key while using the Web client. If you accidentally use the [Esc]
key, click Refresh or press F5.
The status of copy pairs is not

correctly reported to the Web client.
When a pair is being created or deleted by the HiCommand Device Manager web
client, and HiScan is executed simultaneously on a host where one of the allocated
LUs is included in that pair, the status of the pair may not be reported correctly on the
web client. If this happens, refresh the storage subsystem.
The plus (+) symbol in front of an

item in the navigation pane
sometimes disappears when you
select that item, without displaying
contents for that item.
To improve display performance, software does not pre-check for child objects below a
specific object. This is a design compromise rather than a bug.
Alternatively, in a cluster environment using Microsoft Cluster Server, when a storage

subsystem is moved between the management-target hosts, the file system
information might not be reflected promptly in the window that displays the host
properties.
317
12.3 Warning Messages Output from Device Manager

Warning messages, described below, appear if an operation from a Device Manager server
may affect subsequent operations (such as when user data is lost), or affect I/O from hosts.
Warning messages are output before such an operation is executed.
12.3.1 When User Data Is Deleted

If an operation from a Device Manager server deletes user data, the following warning
message appears:
The data of the volume specified for the secondary volume data will be lost. Confirm that
this is OK.
Continuing this operation will delete the data of a volume specified to be a secondary
volume. Back up the data if necessary, and then continue the operation.
12.3.2 When an Error Occurs in I/O from Hosts

If an operation from Device Manager may cause an error in I/O from hosts, the following
warning message appears:
Confirm that no host and external port is performing I/O processing on any of the aaa.
If I/O processing is being performed, the processing might terminate abnormally. Are
you sure you want to continue?
Continuing this operation may affect I/O to aaa. Confirm that hosts and external ports
are not performing I/O operations on aaa, and then continue the operation:
Confirm that no host and external port is performing I/O processing with the LUNs of this
port. This operation may damage the file system and will prevent other hosts and
external ports not assigned to the host storage domain aaa from accessing the LUNs. Are
you sure you want to continue?
Make sure that hosts or external ports are not issuing I/O on any LUNs that use a port
subject to this operation, and then continue the operation. Executing the operation
during I/O operation from a host or external ports may damage the file system. Also, as
a result of this operation, only the host and external ports whose host storage domain is
aaa become accessible to the LUNs. Note that if you execute this operation, you may
need to execute Disconnect Volume in Storage Navigator.
Changing the port settings may prevent other hosts and external ports from accessing
the storage. Are you sure you want to continue?
For example, depending on hardware, the servers and HBAs cannot recognize the LUNs
using the subject port unless a specific host mode is selected for the port. For details on
how to change the port settings, see the manual for the corresponding storage
subsystem.
The mode cannot be switched if a host is currently performing I/O operation with the
LUNs of the port. To proceed, shut down the host, change the mode, and then reboot the
host. Are you sure you want to continue?
Confirm that the host has shut down, and then continue the operation.
318
12.3.3 When LUN Security Automatically Takes Effect

If an operation from Device Manager may cause an error in host I/O, the following warning
message appears:
This operation will change the port's LUN security, which may prevent other hosts and
external ports from accessing LUNs with the following ports. Are you sure you want to
continue?
When LUN security takes effect, the servers and HBAs that are currently recognizing the LUN
using the subject port may no longer be able to recognize that LUN. In such a case, you need
to set LUN security for such servers and HBAs. Note that if you execute this operation, you
may need to execute Disconnect Volume in Storage Navigator.
12.3.4 When Access from Hosts Is Disabled

When a storage subsystem is restarted to make the setting take effect, the following
The subsystem will be rebooted to confirm the setup. Any I/O operations with the host will
end. If the subsystem is used as an external subsystem, make sure that you perform a
"Disconnect subsystem" operation at Storage Navigator. Are you sure you want to continue?
Confirm that hosts are not issuing I/Os on any LUNs for the storage subsystem subject to this
operation, and then continue the operation. If the subsystem is used as an external
subsystem, make sure that you execute Disconnect subsystem in Storage Navigator.
12.3.5 When Data in an S-VOL (Secondary Volume) Becomes Incomplete

When the pair status is changed to SPLIT during I/O operation on a P-VOL (primary volume),
the following warning message appears:
If this operation is performed during I/O processing on the primary volume, the data of the
secondary volume may be corrupted. Make sure that no I/O processing is being performed on
the primary volume before you proceed. Are you sure you want to continue?
Confirm that hosts are not issuing I/Os on any primary volume (P-VOL), and then continue
the operation.
12.3.6 When I/Os to P-VOL (Primary Volume) Are Affected

When the copy pace is set to a value other than the recommended value, the following
For the Thunder 9500V or Thunder 9200, set the copy pace for ShadowImage and
TrueCopy to 15. For QuickShadow, set the copy pace to Faster. Because changing
this value affects I/O operations on the P-VOL (primary volume), contact a System
Administrator.
319
12.3.7 When Pair Setting Cannot Be Performed

When a volume specified as a copy pair is deleted, you may not be able to set a pair. In such
a case, the following warning message appears:
Deleting pair volumes or command devices may disable later modification of the pair volume
settings. Are you sure you want to continue?
If the following conditions required for setting a pair are not satisfied because a LUN is
deleted, you can no longer set a pair. Confirm the changes, and then perform the operation.
For pair volumes:
The host recognizes the pair volumes, and LUN security is set for that host.
For command devices:
The host that recognizes a pair volume also recognizes the command device, and
LUN security is set for that host.
12.3.8 When an Internal Volume Mapped with an External Volume Becomes Invalid
An internal volume mapped with an external volume may become invalid when the external
volume is deleted or security setting is changed. In this case the following warning message
appears:
An assigned volume of Universal Volume Manager may be invalid. Are you sure you want to
continue?
A volume assigned by Universal Volume Manager may be invalid. Check the changes. Note
that if you execute this operation, you may need to execute Disconnect Volume in Storage
Navigator.
12.3.9 When an Attempt Is Made to Create a LUSE Volume Using Volumes from Multiple External
Subsystems
When creating a LUSE volume by using internal volumes to which external volumes are
mapped, the following warning message appears when you specify volumes from multiple
external subsystems:
You are creating a LUSE with multiple external subsystems or an unknown external subsystem.
(LDEV = LDEV-number)
A LUSE with multiple external subsystems is not recommended. Select LDEVs with the same
external subsystem.
320
12.4 Error Messages

HiCommand Device Manager displays an error message when an error condition occurs. The
error message includes the error code, error level (indicates the severity of the error), and
error message. The error code range indicates the type of error.
The HiCommand Device Manager Error Codes document (MK-92HC016) lists and describes
the HiCommand Device Manager error messages and provides instructions for resolving the
error conditions. If you are unable to resolve an error condition, please call the Hitachi Data
Systems Support Center for assistance (see section 12.5).
Note: HiCommand Device Manager sends all error notifications, including Server errors, to
the HiCommand Device Manager client (e.g., Web Client, CLI, third-party application).
321
12.5 Calling the Support Center

If you need to call the Hitachi Data Systems Support Center, make sure to provide as much
information about the problem as possible, including the circumstances surrounding the
error or failure and the exact content of any error messages displayed on the HiCommand
Device Manager PC and/or host system.
The worldwide Hitachi Data Systems Support Centers are:
322
Hitachi Data Systems North America/Latin America

San Diego, California, USA
1-800-348-4357
Hitachi Data Systems Europe

Contact Hitachi Data Systems Local Support
Hitachi Data Systems Asia Pacific

North Ryde, Australia
61-2-9325-3300
Acronyms and Abbreviations

ACP
AG
AL
API
array control processor (back-end array processor on the 9900V and 9900)
array group
arbitrated loop
application program interface
CCI
CHA
CLI
cmd dev
CSV
CU
CVS
Command Control Interface

channel adapter
command line interface
command device
comma-separated value
control unit
customized volume size (another term for Virtual LUN)
DAMP
DKC
DKU
Disk Array Management Program (applicable to 9500V)

disk controller (applicable to 9900V and 9900 subsystems)
disk unit
ESCON
Enterprise System Connection
FC
FTP
fibre channel
file transfer protocol
GB
GUI
gigabyte (1024 MB)

graphical user interface
HA
HBA
HDD
HDLM
HIHSM
HOMRCF
HORCM
HRX
HSD
HTML
http
high availability
host bus adapter
hard disk drive
Hitachi Dynamic Link Manager
Hitachi Internal Hierarchical Storage Management
Hitachi Open Multiple Raid Coupling Feature
Hitachi Open Remote Copy Manager (name of CCI executable)
Hitachi RapidXchange
host storage domain
hypertext markup language
hypertext transfer protocol
IP
internet protocol
JRE
JWS
Java Runtime Environment

Java Web Start software
KB
kilobyte (1024 bytes)
323
324
LAN
LDEV
LU
LUN
LUSE
local-area network
logical device
logical unit
logical unit number, logical unit
LUN Expansion, LU Size Expansion
MB
MCU
MRCF
megabyte (1024 KB)

main control unit (for TrueCopy)
Multiple RAID Coupling Feature (another term for ShadowImage)
NAS
network-attached storage
OS
operating system
PA
PC
PCB
PG
P-VOL
port address
personal computer
printed circuit board
parity group
primary volume (for TrueCopy or ShadowImage)
RAID
RCU
redundant array of independent disks

remote control unit (for TrueCopy)
SAN
SCSI
SI
SNMP
SP-VOL
SSL
SSO
S-VOL
SVP
storage-area network
small computer systems interface
ShadowImage
simple network management protocol
secondary-primary volume (for ShadowImage cascade)
secure socket layer
single sign-on
secondary volume (for TrueCopy or ShadowImage)
service processor (component of 9900V and 9900)
TB
TC
TCA
TCP/IP
terabyte (1024 GB)

TrueCopy
TrueCopy Asynchronous
transmission control protocol/internet protocol
VDEV
VM
VPN
VxVM
virtual device
Volume Manager, volume manager
virtual private network
VERITAS Volume Manager
WWN
worldwide name
Acronyms and Abbreviations

HiCommand DeviceManager PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

HiCommand DeviceManager PDF

Загружено:

Авторское право:

Доступные форматы

Hitachi HiCommand Device Manager

Web Client Users Guide

2004 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED

Hitachi HiCommand Device Manager Web Client Users Guide

HP-UX is a registered trademark of the Hewlett-Packard Development Company, L.P.

Notice of Export Controls

Document Revision Level

Revision 1, supersedes and replaces MK-91HC001-0

Revision 2, supersedes and replaces MK-91HC001-1

Revision 3, supersedes and replaces MK-91HC001-2

Revision 4, supersedes and replaces MK-91HC001-3

Revision 5, supersedes and replaces MK-91HC001-4

Revision 6, supersedes and replaces MK-91HC001-5

Revision 7, supersedes and replaces MK-91HC001-6

Revision 8, supersedes and replaces MK-91HC001-7

Revision 9, supersedes and replaces MK-91HC001-8

Revision 10, supersedes and replaces MK-91HC001-9

Revision 11, supersedes and replaces MK-91HC001-10

Source Documents for this Revision

3020-3-E61(E) (06.15.04) (t-code)

Changes in this Revision

Added information to the 9900V Storage Navigator Requirements section in Chapter 4.

Added information to the Viewing all alerts section in Chapter 5.

Added information to the Launching Protection Manager section in Chapter 5.

Added Instructions for creating a configuration file for CCI.

Added allocated group information to Chapter 8.

Updated approximately 60 figures.

Added information on linkage with related products (see section 4.3).

Added information about logging in to Device Manager (see section 4.5).

Added notes on Copy Pair operations (see section 9.7.3).

Added tables to Create Array Group information (see section 10.4).

HiCommand Device Manager Agent Installation Guide (MK-92HC019)

HiCommand Device Manager Server Installation and Configuration Guide (MK-91HC002)

HiCommand Tuning Manager Reference Guide (MK-92HC022)

Hitachi Thunder 9200 Resource Manager 9200 Users Guide (MK-90DF505)

Hitachi Thunder 9500 V Series QuickShadow 9500V Users Guide (MK-92DF666)

Hitachi Lightning 9900 V Series LUN Manager Users Guide (MK-92RD105)

Hitachi Lightning 9900 LUN Manager Users Guide (MK-90RD003)

Hitachi Lightning 9900 V Series LUN Manager Users Guide (MK-92RD105)

Hitachi Lightning 9900 V Series ShadowImage Users Guide (MK-92RD110)

Hitachi TagmaStoreTM Universal Storage Platform Universal Volume Manager Users

has a background in data processing and understands peripheral storage device

Hitachi Lightning 9900 V Series User and Reference Guide

Hitachi Lightning 9900 User and Reference Guide

Hitachi Thunder 9500 V Series User and Reference Guide

Hitachi Thunder 9200 User and Reference Guide

Sun StorEdge T3 Disk Tray Configuration Guide

Hitachi HiCommand Device Manager Web Client Users Guide

1 KB (kilobyte) is 1,024 bytes.

1 MB (megabyte) is 1,0242 bytes.

1 GB (gigabyte) is 1,0243 bytes.

1 TB (terabyte) is 1,0244 bytes.

Overview of HiCommand Device Manager .......................................................................1

Overview of HiCommand Device Manager .................................................. 2

HiCommand Device Manager Operations.......................................................................15

User Groups and User Access Levels.........................................................

Hitachi HiCommand Device Manager Web Client Users Guide

Installing the Device Manager Web Client .........................................................................35

Preparing for and Starting Device Manager Operations...................................................47

Preparing to Start HiCommand Device Manager Operations............................ 48

Performing Device Manager System Operations ..............................................................67

Requirements for Web Client Operations ................................................... 36

Using the HiCommand Device Manager Main Window ................................... 68