VSP PerformanceGuide

Product Version

Document Organization

Getting Help

FASTFIND LINKS

Contents

Hitachi Virtual Storage PlatformPerformance Guide

MK-90RD7020-00

ii

Hitachi VSP Performance Guide

Copyright © 2010 Hitachi, Ltd. All rights reserved.

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

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

Some 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 about feature and product availability.

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

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

ShadowImage and TrueCopy are registered trademarks of Hitachi Data Systems.

AIX, ESCON, FICON, FlashCopy, IBM, MVS/ESA, MVS/XA, OS/390, S/390, VM/ESA, VSE/ESA, z/OS, zSeries, z/VM, and zVSE are registered trademarks or trademarks of International Business Machines Corporation.

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

Microsoft product screen shot(s) reprinted with permission from Microsoft Corporation.

iii


Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ixIntended audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiProduct version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiDocument revision level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiSource documents for this revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiChanges in this revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiReferenced documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiDocument organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiiiDocument conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvConvention for storage capacity values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiAccessing product documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xixGetting help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xixComments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xix

1 Performance improvement of storage system . . . . . . . . . . . . . . . . 1-1Performance Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Cache Residency Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

2 About monitoring performance . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Monitoring resource availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Prestaging specific data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Priority mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Bind mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

3 Interoperability of Performance Monitor and other products . . . . . . 3-1Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Powering off the storage system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Viewing the Monitor Performance window . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Viewing the WWN monitoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Replacing the microprogram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

iv


4 Monitoring CUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Displaying CUs to be monitored . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Adding or removing CUs to be monitored . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Selecting CUs to be monitored from parity group . . . . . . . . . . . . . . . . . . . . . . 4-2Confirming the status of CUs to be monitored . . . . . . . . . . . . . . . . . . . . . . . . 4-3

5 Monitoring WWNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Displaying WWNs to be monitored . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Adding or removing WWNs to be monitored . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Adding new WWNs to ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Editing the WWN nickname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Connecting WWNs to ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Deleting WWNs from monitoring target objects . . . . . . . . . . . . . . . . . . . . . . . 5-4

6 Monitoring operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Performing Monitoring Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Starting monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Stopping monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

7 Setting statistical storage ranges . . . . . . . . . . . . . . . . . . . . . . . . . 7-1About statistical storage ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Viewing statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Setting the storing period of statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

8 Working with graphs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1Basic operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2Objects that can be displayed in graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3Usage rates of processor blade(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4Usage rate of a data recovery and reconstruction processor . . . . . . . . . . . . . . 8-5Usage rate of cache memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5Write pending statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6Access paths usage statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6Throughput of storage system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7Size of data transferred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9Response times. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10Cache hit rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11Back-end performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13Hard disk drive usage statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14Hard disk drive access rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14ShadowImage usage statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15

v


9 Changing display of graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1Graph operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2Changing displayed items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2Changing a display period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2Adding a new graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3Deleting graph panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

10 Creating virtual cache partitions . . . . . . . . . . . . . . . . . . . . . . . . 10-1About virtual cache partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Cache capacity for a CLPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3Cache partitioning rules and guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4Partitioning cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5

Cache partition work flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5Creating a CLPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6Migrating resources to and from a CLPR . . . . . . . . . . . . . . . . . . . . . . . . 10-7Deleting a CLPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8

Troubleshooting Virtual Partition Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8

11 Estimating cache size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1About cache size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2Calculating cache size for open systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2Calculating cache size for mainframe systems . . . . . . . . . . . . . . . . . . . . . . . 11-4Cache Residency Manager extents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5Cache Residency Manager system specifications. . . . . . . . . . . . . . . . . . . . . . 11-6

12 Managing resident cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1Cache Residency Manager rules, restrictions, and guidelines . . . . . . . . . . . . . 12-2Launching Cache Residency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4Viewing Cache Residency information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5Placing specific data into Cache Residency Manager cache . . . . . . . . . . . . . . 12-5Placing LDEV(s) into Cache Residency Manager cache. . . . . . . . . . . . . . . . . . 12-7Releasing specific data from Cache Residency Manager cache . . . . . . . . . . . . 12-9Releasing LDEV(s) from Cache Residency Manager cache . . . . . . . . . . . . . . . 12-9Changing mode after Cache Residency is registered in cache. . . . . . . . . . . . 12-11

13 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2Calling the Hitachi Data Systems Support Center . . . . . . . . . . . . . . . . . . . . . 13-2

A Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1About the Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2Preparing for using the Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

vi


Installing the Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2On UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2On Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

Export Tool limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3Requirements for using the Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . A-3Installing the Export Tool on a Windows computer . . . . . . . . . . . . . . . . . . A-5Installing the Export Tool on a UNIX computer . . . . . . . . . . . . . . . . . . . . . A-5

Using the Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5Preparing a command file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6Preparing a batch file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9Using the Export Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10

Running the batch file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10File formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11Processing time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11Termination code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12Log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13Error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13

Export Tool command reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14Export Tool command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14Syntax descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15Writing a script in the command file . . . . . . . . . . . . . . . . . . . . . . . . . A-15Viewing the online Help for subcommands . . . . . . . . . . . . . . . . . . . . . A-16

Subcommand list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-16svpip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-16retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-18show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-18group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-20short-range. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-36long-range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-39outpath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-42option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-42apply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-43set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-44help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-45Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-46

Exported files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-48Monitoring data exported by the Export Tool . . . . . . . . . . . . . . . . . . . . . A-48Resource usage and write-pending rate statistics . . . . . . . . . . . . . . . . . . A-49Parity groups, external volume groups, or V-VOL groups statistics . . . . . . A-53Volumes in parity/external volume groups or V-VOL groups statistics . . . . A-54Volumes in parity groups, external volume groups, or V-VOL groups (at volumes controlled by a particular CU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-56

Port statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-58Host bus adapters connected to ports statistics . . . . . . . . . . . . . . . . . . . A-58Volumes (LU) statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-59

vii


All host bus adapters connected to ports . . . . . . . . . . . . . . . . . . . . . . . . A-60Processor blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-60Remote copy operations by TC/TCz (whole volumes) . . . . . . . . . . . . . . . A-61Remote copy operations by TC and TCz (for each volume (LU)) . . . . . . . . A-61Remote copy by TC and TCz (volumes controlled by a particular CU) . . . . A-62Remote copy by UR and URz (whole volumes) . . . . . . . . . . . . . . . . . . . . A-64Remote copy by UR and URz (at journals) . . . . . . . . . . . . . . . . . . . . . . . A-65Remote copy by UR and URz (for each volume (LU)). . . . . . . . . . . . . . . . A-66Remote copy by UR and URz (at volumes controlled by a particular CU) . . A-67

Causes of Invalid Monitoring Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-68Troubleshooting the Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-69

Messages issued by the Export tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-71

B Performance Monitor GUI reference . . . . . . . . . . . . . . . . . . . . . . B-1Performance Monitor main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3Edit Monitoring Switch wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5

Edit Monitoring Switch window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5Confirm window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6

Monitor Performance window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7Edit CU Monitor Mode wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-16

Edit CU Monitor Mode window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-16Confirm window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-19

View CU Matrix window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-21Select by Parity Groups window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-23Parity Group Properties window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-25Edit WWN wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-26

Edit WWN window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-26Confirm window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-27

Edit WWN Monitor Mode wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-27Edit WWN Monitor Mode window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-27Confirm window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-31

Delete Unused WWNs window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-32Add New Monitored WWNs wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-33

Add New Monitored WWNs window. . . . . . . . . . . . . . . . . . . . . . . . . . . . B-33Confirm window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-37

Add to Ports wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-38Add to Ports window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-38Confirm window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-41

Monitor window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-42Edit Time Range window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-44Edit Performance Objects window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-45Add Graph window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-54

C Virtual Partition Manager GUI reference . . . . . . . . . . . . . . . . . . . C-1Partition Definition tab (Subsystem selected) . . . . . . . . . . . . . . . . . . . . . . . . . C-2

viii


Partition Definition tab, Cache Logical Partition window (CLPR selected) . . . . . . C-3Partition Definition tab, Cache Logical Partition window (CLPR information) . . . C-4Select CU dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7

D Cache Residency Manager GUI reference . . . . . . . . . . . . . . . . . . . D-1Cache Residency window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2Multi Set dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7Multi Release dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-9

Glossary

Index

Preface ix


PrefacePreface

This document describes and provides instructions for using the performance management features of the Hitachi Virtual Storage Platform (VSP) storage system. The performance management features include Hitachi Performance Monitor, Hitachi Virtual Partition Manager, and Hitachi Cache Residency Manager.

Please read this document carefully to understand how to use these products, and maintain a copy for reference purposes.

This preface includes the following information:

□ Intended audience

□ Product version

□ Document revision level

□ Source documents for this revision

□ Changes in this revision

□ Referenced documents

□ Document organization

□ Document conventions

□ Convention for storage capacity values

□ Accessing product documentation

□ Getting help

□ Comments

x Preface


Intended audienceThis document is intended for system administrators, Hitachi Data Systems representatives, and authorized service providers who are involved in installing, configuring, and operating the Hitachi Virtual Storage Platform storage system.

Readers of this document should meet the following requirements:

• You should have a background in data processing and understand RAID storage systems and their basic functions.

• You should be familiar with the Hitachi Virtual Storage Platform storage system, and you should have read the Hitachi Virtual Storage Platform User and Reference Guide.

• You should be familiar with the Storage Navigator software for the Hitachi Virtual Storage Platform, and you should have read the Storage Navigator User Guide.

• You should be familiar with performance monitoring and management of RAID storage systems.

Product versionThis document revision applies to Hitachi VSP microcode 70-01-0x or later.

Document revision level

Source documents for this revision• Not applicable.

Changes in this revision• Not applicable.

Referenced documentsHitachi Virtual Storage Platform documentation:

• Provisioning Guide for Mainframe Systems, MK-90RD7021

• Provisioning Guide for Open Systems, MK-90RD7022

• Hitachi ShadowImage® for Mainframe User Guide, MK-90RD7023

• Hitachi ShadowImage® User Guide, MK-90RD7024

• Hitachi Storage Navigator User Guide, MK-90RD7027

• Hitachi Storage Navigator Messages, MK-90RD7028

• Hitachi TrueCopy® for Mainframe User Guide, MK-90RD7029

Revision Date Description

MK-90RD7020-00 October 2010 Initial release

Preface xi


• Hitachi TrueCopy® User Guide, MK-90RD7030

• Hitachi Universal Replicator for Mainframe User Guide, MK-90RD7031

• Hitachi Universal Replicator User Guide, MK-90RD7032

• User and Reference Guide, MK-90RD7042

Document organizationThe following table provides an overview of the contents and organization of this document. Click the chapter title in the left column to go to that chapter. The first page of each chapter provides links to the sections in that chapter.

Chapter Description

Chapter 1, Performance improvement of storage system

Provides an overview of performance monitoring and management of the Hitachi Virtual Storage Platform storage system.

Chapter 2, About monitoring performance

Provides instructions for preparing for Performance Monitor operations.

Chapter 3, Interoperability of Performance Monitor and other products

Describes the interoperability considerations for Performance Monitor.

Chapter 4, Monitoring CUs Provides instructions for monitoring control units (CUs) using Hitachi Performance Monitor.

Chapter 5, Monitoring WWNs Provides instructions for monitoring WWNs using Hitachi Performance Monitor.

Chapter 6, Monitoring operation

Provides instructions for monitoring operations using Hitachi Performance Monitor.

Chapter 7, Setting statistical storage ranges

Provides instructions for setting statistical storage ranges using Hitachi Performance Monitor.

Chapter 8, Working with graphs

Provides instructions for working with graphs of performance data.

Chapter 9, Changing display of graphs

Provides instructions for changing display of graphs of performance data.

Chapter 10, Creating virtual cache partitions

Provides instructions for creating virtual cache partitions using Hitachi Virtual Partition Manager.

Chapter 11, Estimating cache size

Provides instructions for estimating cache size using Hitachi Cache Residency Manager.

Chapter 12, Managing resident cache

Provides instructions for performing Cache Residency Manager operations.

Chapter 13, Troubleshooting Provides troubleshooting information for Performance Monitor, Virtual Partition Manager, and Cache Residency Manager.

Appendix A, Export Tool Provides instructions for using the Export Tool.

Appendix B, Performance Monitor GUI reference

Describes the Hitachi Storage Navigator windows and dialog boxes for Performance Monitor.

Appendix C, Virtual Partition Manager GUI reference

Describes the Hitachi Storage Navigator windows and dialog boxes for Virtual Partition Manager.

xii Preface


Document conventionsThe terms “Virtual Storage Platform” and “VSP” refer to the Hitachi Virtual Storage Platform storage system, unless otherwise noted.

This document uses the following typographic conventions:

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

Appendix D, Cache Residency Manager GUI reference

Describes the Hitachi Storage Navigator windows and dialog boxes for Cache Residency Manager.

Chapter Description

Convention Description

Bold Indicates text on a window or dialog box, including window and dialog box names, menus, menu options, buttons, fields, and labels. Example: Click OK.

Italic Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: copy source-file target-fileNote: Angled brackets (< >) are also used to indicate variables.

screen/code Indicates text that is displayed on screen or entered by the user. Example: # pairdisplay -g oradb

< > angled brackets Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: # pairdisplay -g <group>Note: Italic font is also used to indicate variables.

[ ] square brackets Indicates optional values. Example: [ a | b ] indicates that you can choose a, b, or nothing.

{ } braces Indicates required or expected values. Example: { a | b } indicates that you must choose either a or b.

| vertical bar Indicates that you have a choice between two or more options or arguments. Examples:[ a | b ] indicates that you can choose a, b, or nothing.{ a | b } indicates that you must choose either a or b.

Icon Meaning Description

Tip Provides helpful information, guidelines, or suggestions for performing tasks more effectively.

Note Calls attention to important and/or additional information.

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

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

Preface xiii


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

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

Accessing product documentationThe Hitachi Virtual Storage Platform user documentation is available on the Hitachi Data Systems Support Portal: https://hdssupport.hds.com. Please check this site for the most current documentation, including important updates that may have been made after the release of the product.

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

CommentsPlease send us your comments on this document: [email protected]. Include the document title, number, and revision. Please refer to specific sections and paragraphs whenever possible.

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

Physical capacity unit Value

1 KB 1,000 bytes

1 MB 1,0002 bytes

1 GB 1,0003 bytes

1 TB 1,0004 bytes

1 PB 1,0005 bytes

1 EB 1,0006 bytes

Logical capacity unit Value

1 KB 1,024 bytes

1 MB 1,024 KB or 1,0242 bytes

1 GB 1,024 MB or 1,0243 bytes

1 TB 1,024 GB or 1,0244 bytes

1 PB 1,024 TB or 1,0245 bytes

1 EB 1,024 PB or 1,0246 bytes

1 block 512 bytes

https://hdssupport.hds.com



xiv Preface


Performance improvement of storage system 1–1


1Performance improvement of storage

system

The Hitachi Virtual Storage Platform (herein after referred to as VSP) includes a suite of Hitachi Performance Monitor software products that allow you to monitor and tune storage system performance.

□ Performance Monitor

□ Cache Residency Manager

1–2 Performance improvement of storage system


Performance Monitor Performance Monitor feature provides usage statistics about physical hard disk drives, volumes, processors, or other resources in your storage system. Performance Monitor also provides statistics about workloads on disk drives and traffic between hosts and the storage system. The Monitor Performance window provides a line graph indicating changes in the usage rates, workloads, or traffic. You can view information in the window and analyze trends in disk I/Os and detect peak I/O time. If system performance is poor, you can use information in the window to detect bottlenecks in the system.When using Performance Monitor, you must specify the volumes to be monitored in (control units). Therefore, depending on your storage system configuration, the list may show performance statistics for some volumes but not other volumes. This can occur if the range of used CUs does not match the range of CUs monitored by Performance Monitor.

To use Performance Monitor, purchase the license key for Performance Monitor program product and install the license key into the Storage Navigator computer. For details about the license key and installing program products, see Hitachi Storage Navigator User Guide.

To correctly display performance statistics of a parity group and a LUSE volume, specify the following:

• All volumes belonging to the parity group as the monitoring targets.

• All volumes making up the LUSE volume as the monitoring targets.

Cache Residency ManagerThe Cache Residency Manager feature allows you to store frequently accessed data in the storage system's cache memory. Cache Residency Manager increases the data access speed for the cache-resident data by enabling read and write I/Os to be performed at the higher front-end access speeds. Cache Residency Manager operations are performed using the licensed VSP Hitachi Storage Navigator software. The Hitachi Storage Navigator software communicates directly with the VSP storage system via a local-area network (LAN). The Storage Navigator software provides detailed Cache Residency Manager information and allows you to configure and perform Cache Residency Manager operations for the data stored on the VSP. For more information on using Storage Navigator, see the Hitachi Storage Navigator User Guide.

To use Cache Residency Manager, purchase the license key for Hitachi Cache Residency Manager or Cache Residency Manager for Mainframe program product and install the license key into the Storage Navigator computer. For details about the license key and installing program products, see Hitachi Storage Navigator User Guide.

Cache Residency Manager supports prestaging of data. This option places specific data in the Cache Residency Manager cache before it is accessed by the host. When prestaging is selected, the host locates the prestaged data in the Cache Residency Manager cache from the first access, thus enhancing its access performance.

About monitoring performance 2–1


2About monitoring performance

This topic describes the overview of Performance Monitor and Cache Residency Manager.

□ Monitoring resource availability

□ Prestaging specific data

□ Priority mode

□ Bind mode

2–2 About monitoring performance


Monitoring resource availabilityPerformance Monitor tracks your storage system so that you can obtain statistics about:

• resources in your storage system

• workloads on disk and ports

If your system encounters some problem (for example, if server hosts suffer delayed response times), Performance Monitor can help you detect the cause of the problem.

Prestaging specific dataCache Residency Manager supports prestaging of data. This option places specific data in the Cache Residency Manager cache before it is accessed by the host. When prestaging is selected, the host is able to find the prestaged data in the Cache Residency Manager cache from the first access, thus enhancing its access performance.

You can use the prestaging function to make data available from the Cache Residency Manager cache the first time the host accesses the data. Both priority mode and bind mode permit prestaging. Prestaging occurs under any of the following circumstances:

• When prestaging is performed from the SVP or from Storage Navigator.

• When the power is turned on.

Figure 2-1 Cache Residency Manager cache area

Caution: Increase total storage system cache capacity when using Cache Residency Manager to avoid data access performance degradation for non-Cache-Residency data. Cache Residency Manager is available only on VSP storage systems configured with at least 512MB of cache. The Hitachi Data Systems representative configures the maximum allowable Cache Residency Manager area when the cache is installed.



• When cache maintenance is performed.

Priority modeThe Cache Residency Manager software allows you to set the priority mode. The main advantage of Cache Residency Manager priority mode is that read data is transferred at host data transfer speed. In priority mode the Cache Residency Manager extents are used to hold read data for specific extents on volumes. Write data is write duplexed in cache other than Cache Residency Manager, and the data is de-staged to the disk drive when disk utilization is low.

In Priority Mode (normal mode), the total capacity of cache required is:

standard cache + Cache Residency Manager cache + additional cache

The following table lists the standard cache capacity values for priority mode operations. These requirements the standard cache capacity required to prevent the access performance from degrading. For further information on the calculating procedures of required cache size for using Cache Residency Manager if the priority mode is set, see Estimating cache size on page 11-1.

Table 2-1 Priority mode cache capacity requirements

Note: Notes of Cache Residency Manager show as follows:

• If you have accessed the Cache Residency Manager area for input and output before the prestaging operation is performed from the SVP or Storage Navigator, the host may not be able to find data in the cache at the first I/O access after Cache Residency Manager is configured.

• In order to prevent the response time of host I/O being slow, the prestaging operation may be interrupted when the cache load is heavy.

• If you specify the Cache Residency Manager setting on the volume during the quick formatting, do not use the prestaging function. If you want to use the prestaging function after the quick formatting processing completes, first you need to release the setting and then specify the Cache Residency Manager setting again, with the prestaging setting enabled this time. For information about the quick formatting, see Provisioning Guide for Open Systems or Provisioning Guide for Mainframe Systems.

• When external volumes are set in the storage system, execute the disconnect external storage system operation to the external storage system before turning off the power supply of the storage system. If you turn off the power supply of the storage system without executing the disconnect external storage system operation to the external storage system and then turn on the power supply again, the prestaging processing is aborted. If the prestaging processing is aborted, perform the prestaging operation from SVP or Storage Navigator.

Added cache capacity for area to set in priority mode Standard cache capacity

4,096 MB 4,096 MB

8,192 MB 8,192 MB



Bind modeThe Cache Residency Manager software allows you to set the bind mode. In bind mode, the Cache Residency Manager extents are used to hold read and write data for specific extent(s) on volume(s). Any data written to the Cache Residency Manager bind area is not de-staged to the disk. To ensure data integrity, write data is duplexed in the Cache Residency Manager area, which consumes a significant amount of the Cache Residency Manager cache.

In Bind Mode, the total capacity of cache required is:

standard cache + Cache Residency Manager cache

The following table specifies the cache requirements for bind mode operations. For further information on calculating procedures for required cache size for using Cache Residency Manager if the bind mode is set, see Estimating cache size on page 11-1.The primary advantage of bind mode is that all targeted read and write data is transferred at host data transfer speed. In addition, the accessibility of read data is the same as Cache Residency Manager priority mode; write operations do not have to wait for available cache segments; and there will be no back-end contention caused by destaging data.

Table 2-2 Bind mode cache requirements

16,384 MB 16,384 MB

32,768 MB 32,768 MB

Added cache capacity for area to set in priority mode Standard cache capacity

System Type RAID Level or Volume Type

Capacity Specifications

Cache Residency Cache

Requirement

OPEN Systems RAID 5 (3390) or RAID 6

Slot capacity: 264 KBCache segment capacity: 16.5 KBCache segments needed per slot: 48 (slot capacity / cache segment capacity)

3 times the space required for user data: 1 slot = 3 × 264 KB = 792 KB = 48 cache segments

RAID 1, or external volumes





Cache Residency Manager bind data that has write attributes is normally not destaged. However, this data will be destaged in the following cases:

• During cache blockage that is caused by certain maintenance operations (e.g., cache upgrades) or that is caused by cache failure.

• If the storage system is powered off.

• If the volume is deleted from Cache Residency Manager bind mode.

Changing the mode without cache extension requires reconfiguring of Cache Residency Manager (i.e., release the data from cache, and then place the data back in cache with the desired mode).

Mainframe(e.g., 3390-3, 3390-9)

RAID 5 mainframe or RAID 6

Slot capacity: 66 KBCache segment capacity: 16.5 KBCache segments needed per slot: 12 (slot capacity / cache segment capacity)Note: Even though a track for mainframe is 56 KB, because cache is divided into 16.5 KB segments, it requires 4 segments.


RAID 1 mainframe, or external volumes



System Type RAID Level or Volume Type

Capacity Specifications

Cache Residency Cache

Requirement



Interoperability of Performance Monitor and other products 3–1


3Interoperability of Performance

Monitor and other products

This topic describes the interoperability of Performance Monitor and other products.

□ Maintenance

□ Powering off the storage system

□ Viewing the Monitor Performance window

□ Viewing the WWN monitoring data

□ Replacing the microprogram

3–2 Interoperability of Performance Monitor and other products


MaintenanceIf the storage system is undergoing following maintenance operations during monitoring, the monitoring data might contain extremely large values.

• Adding on, replacing, or removing cache memories.

• Adding on, replacing, or removing disk drives.

• Changing the system configuration.

• Replacing the micro program.

Powering off the storage systemIf the storage system is powered off during monitoring, monitoring stops while the storage system is powered off. When the storage system is powered up again, monitoring continues. However, Performance Monitor cannot display information about the period while the storage system is powered off. Therefore, the monitoring data immediately after powering on again might contain extremely large values.

Viewing the Monitor Performance window• You will be able to view usage statistics that have been obtained for the

last three months (i.e., 93 days) in long range monitoring, and for the last 15 days in short range monitoring. You will not be able to view usage statistics that expired after these storing periods because such statistics are erased from the storage system. In short range, monitoring results are stored for the last 8 hours to 15 days depending on the specified gathering interval. If the storing period has passed since a monitoring result was obtained, the result is erased from the storage system and you will not be able to view that monitoring result.

• In long range, monitoring data are constantly collected. In short range, monitoring data are collected only when the monitoring switch set to ON.

• In short range, if I/O workloads between hosts and the storage system become heavy, the storage system gives higher priority to I/O processing than monitoring processing, therefore, a part of monitoring data might be missing. In case that monitoring data are missing frequently, use the Edit Monitoring Switch window to change the Sample Interval longer. For details, see Starting monitoring on page 6-2.

• Short range monitoring data and long range monitoring data may have some margin of error.

• If the SVP is overloaded, more time than the gathering interval allots might be required for updating the display of monitoring data. In this case, some portion of monitoring data will not be displayed in the window. For example, suppose that the gathering interval is 1 minute. In this case, if the display in the Performance Management window is updated at 9:00 and the next update occurs at 9:02, the window (including the graph) does not display the monitoring result for the

Interoperability of Performance Monitor and other products 3–3


period of 9:00 to 9:01. This situation occurs when you use a Storage Navigator computer, as well as when following maintenance operations are performed for the storage system.

• Adding on, replacing, or removing cache memories.

• Adding on, replacing, or removing disk drives.

• Changing the system configuration.

• Replacing the micro program.

Viewing the WWN monitoring dataTo start monitoring traffic between host bus adapters and storage system ports, you must make settings before starting monitoring. For details, see topics between Displaying WWNs to be monitored on page 5-2 and Deleting WWNs from monitoring target objects on page 5-4.

Replacing the microprogramAfter the microprogram was replaced, the monitoring data is not stored until a service engineer releases the SVP from Modify mode. Therefore, inaccurate monitoring data may be displayed temporarily.

3–4 Interoperability of Performance Monitor and other products


Monitoring CUs 4–1


4Monitoring CUs

This topic describes how to set up CUs to be monitored.

□ Displaying CUs to be monitored

□ Adding or removing CUs to be monitored

□ Selecting CUs to be monitored from parity group

□ Confirming the status of CUs to be monitored

4–2 Monitoring CUs


Displaying CUs to be monitoredUse the Performance Monitor window to display the list of CUs to be monitored.

1. In the Storage Navigator main window.

2. Select Performance Monitor in Explorer, and select Performance Monitor in the tree.

The Performance Monitor window opens.

3. Select the Monitored CUs tab.

CUs to be monitored are listed in the tab.

Adding or removing CUs to be monitoredUse the Performance Monitor window to add or remove CUs to be monitored. If this operation is performed, the monitoring result will be deleted.

1. Display the Storage Navigator main window.



3. Display the Monitored CUs tab.

4. Click Edit CU Monitor Mode.

The Edit CU Monitor Mode window opens.

5. Add or remove CUs to be monitored.

To add CUs to monitoring target objects, select CUs from the Unmonitored CUs field and click the Add. To remove CUs from monitoring target objects, select CUs from the Monitored CUs field and click the Remove.

6. Click Finish to display the Confirm window.

7. Click Apply in the Confirm window.

A warning message appears, asking whether you continue this operation although graph data is deleted.

8. Click OK to close the message.

Settings that you have made are registered in the system.

Selecting CUs to be monitored from parity groupUse the Performance Monitor window to select CUs to be monitored.




3. Display Monitored CUs tab.

Monitoring CUs 4–3




5. Click Select by Parity Groups in the Unmonitored CUs field.

the Select by Parity Groups window opens. The available parity group IDs and number of CUs are displayed in the window.

6. Select the parity group ID in the list, click Detail.

The Parity Group Properties window opens. CUs and the number of LDEVs are displayed.

7. After confirming the property of the parity group, click Close.

The Select by Parity Groups window opens.

8. Select the parity group to be monitoring target in the Select by Parity Groups window, click OK.

CUs in the parity group are selected in the Unmonitored CUs field. To monitor these CU, see Adding or removing CUs to be monitored on page 4-2.

Confirming the status of CUs to be monitored Use the View CU Matrix window to display statuses of CUs edited in the Edit Monitoring CUs window.




3. Display the Monitored CUs tab.



5. Click View CU Matrix in the Edit CU Monitor Mode window.

The View CU Matrix window opens. Following CUs are displayed in the Monitored CUs window.

• Monitored CUs

• Set monitored CUs

• Release Monitored CUs

6. Click Close.


4–4 Monitoring CUs


Monitoring WWNs 5–1


5Monitoring WWNs

This topic describes how to set up WWNs to be monitored.

□ Displaying WWNs to be monitored

□ Adding or removing WWNs to be monitored

□ Adding new WWNs to ports

□ Editing the WWN nickname

□ Connecting WWNs to ports

□ Deleting WWNs from monitoring target objects

5–2 Monitoring WWNs


Displaying WWNs to be monitoredUse the Performance Monitor window to display the list of WWNs to be monitored.




3. Select the Monitored WWNs tab.

WWNs to be monitored are listed in the tab.

Adding or removing WWNs to be monitoredUse the Performance Monitor window to add or remove WWNs to be monitored.




3. Display the Monitored WWNs tab.

4. Click Edit WWN Monitor Mode.

The Edit WWN Monitor Mode window opens.

5. Add or Remove WWNs to be monitored.

If you add WWNs to monitoring s, select WWNs from the Unmonitored WWNs field and click Add. If you remove WWNs from monitoring s, select WWNs from the Monitored WWNs field and click the Remove.



If WWNs are removed, a warning message appears.


Setting that you have made are registered in the system.

Adding new WWNs to portsUse Performance Monitor to monitor WWNs not connected to DKC.





4. Click Add New Monitored WWN.

The Add New Monitored WWNs window opens.

Monitoring WWNs 5–3


5. Specify the WWN information, and then click Add.

The added WWN is displayed in Selected WWNs.

Specify three values of a WWN.

• HBA WWN

The hexadecimal number of 16 digits.

• WWN Name

The nickname to distinguish the host bus adapter from others. WWN Name is less than 64 digits and consist of alphanumeric characters and a portion of characters of symbol.

• The list of ports in Available Ports

The target ports list. However, the ports of the mainframe system are not displayed in the list because they are not supported for Performance Monitor.

6. If necessary, specify the unnecessary WWNs in Selected WWNs, click Remove.

Specified WWNs are deleted.




Editing the WWN nicknameUse the Performance Monitor window to edit the nickname of a WWN to be monitored.





4. Select a WWN to edit, click Edit WWN.

Edit WWN window opens. If you select a WWN to edit, select one WWN in the list. If you select multiple WWNs and click Edit WWN, an error occurs.

5. Specify values in HBA WWN and WWN Name fields.

• HBA WWN

The hexadecimal number of 16 digits. The value of HBA WWN must be unique in DKC.

• WWN Name

The nickname to distinguish the host bus adapter from others. WWN Name is less than 64 digits and consist of alphanumeric characters and a portion of characters of symbol.


5–4 Monitoring WWNs




Connecting WWNs to portsUse the Performance Monitor window to connect the WWNs to be monitored to ports.





4. Select the WWN to connect to the port, click Add to Ports.

The Add to Ports window opens. If you select a WWN to connect, select one WWN in the list. If you select multiple WWNs and click Add to Ports, an error occurs.

5. Select a port to connect in Available Ports, and then click Add. However, the ports of the mainframe system are not displayed in the list because they are not supported for Performance Monitor.

The added WWN and the port are specified for the Selected WWNs.

6. If necessary, select unnecessary row of a WWN and port in Selected WWNs, and then click Remove.

WWNs are deleted.




Deleting WWNs from monitoring target objectsUse the Performance Monitor window to delete WWNs that are being monitored.





4. Click Delete Unused WWNs to display the Confirm window.


A warning message appears, asking whether you want to delete WWN.



Monitoring operation 6–1


6Monitoring operation

This topic describes how to start and stop the monitoring operation.

□ Performing Monitoring Operation

□ Starting monitoring

□ Stopping monitoring

6–2 Monitoring operation


Performing Monitoring OperationThis topic describes how to start or stop the monitoring operation.

• To start the monitoring operation, see Starting monitoring on page 6-2.

• To stop the monitoring operation, see Stopping monitoring on page 6-2.

Starting monitoringTo start monitoring the storage system, start Performance Monitor and open the Edit Monitoring Switch window. If this operation is performed, the monitoring result will be deleted.




3. Click Edit Monitoring Switch in the Performance Monitor window.

The Edit Monitoring Switch window opens.

4. Click Enable in the Monitoring Switch field.

5. Select the collecting interval in the Sample Interval.

Specify the interval to obtain usage statistics about the storage system for short range monitoring. This option is activated when you specify Enable for Current Status. If CUs to be monitored are 64 or less, you can specify the value between 1 and 15 minutes by minutes, and the default setting is 1 minute. For example, if you specify 1 minute for the gathering interval, Performance Monitor collect statistics (such as I/O rates and transfer rates) every one minute.

If CUs to be monitored are 65 or more, the gathering interval can be specified to the value 5, 10 or 15 minutes (in the 5 minuted interval), and default is 5 minutes. For example, if you specify the gathering interval to 5 minutes, Performance Monitor gathers statistics (such as I/O rate and transfer rate) every 5 minutes.



A warning message appears, asking whether you continue this operation although graph data is deleted.

8. Click OK to start monitoring.

When statistics are collected, a heavy workload is likely to be placed on servers. Therefore, the client processing might slow down.

Stopping monitoringStop monitoring the storage system in the Edit Monitoring Switch window.


Monitoring operation 6–3




3. Click Edit Monitoring Switch in the Performance Monitor window.

The Edit Monitoring Switch window opens.

4. Click Disable in the Monitoring Switch field.

The Sample Interval list is grayed out and becomes ineffective.


6. Click Apply in the Confirm window to stop monitoring.

6–4 Monitoring operation


Setting statistical storage ranges 7–1


7Setting statistical storage ranges

This topic describes statistical storage ranges.

□ About statistical storage ranges

□ Setting the storing period of statistics

7–2 Setting statistical storage ranges


About statistical storage rangesPerformance Monitor collects and stores statistics for two time periods (ranges): short range and long range. The difference between the two ranges and the statistics they target are as follows:

• Short range

If the number of CUs to be monitored is 64 or less, statistics are collected at a user-specified interval between 1 and 15 minutes, and stored between 1 and 15 days.

If the number of CUs to be monitored is 65 or more, statistics are collected at a user-specified intervals of 5, 10 or 15 minutes, and stored between 8 hours and 1 day.

• Long range

Statistics are collected at fixed 15-minute (0, 15, 30, and 45 minutes of every hour), and stored for 93 days (i.e., 3 months).

Usage statistics about storage system resources are collected and stored in long range, in parallel with in short range. However, some of usage statistics about resources cannot be collected in long range.

Viewing statisticsUse the Monitor Performance window to view statistics within short and long storage ranges. All statistics, except some information related to Volume Migration, can be viewed in short range (for the storing period corresponding to the collecting interval setting). In addition, usage statistics about storage system resources can be viewed in both short range and long range because they are monitored in both ranges. When viewing usage statistics about resources, you can specify the range to view and which part of the storing period to depict on lists and graphics.

Setting the storing period of statisticsUse the Monitor Performance window to set the storing period of statistics.




3. Click Monitor Performance in the Performance Monitor window.

The Monitor Performance window opens.

4. Select Long-Range or Short-Range in the Data Range as the periods (ranges) for collecting and storing statistics.

5. Select Set Range or Use Real Time in the Time Range as the periods (ranges) for displaying statistics.

If Long-Range is selected, you can specify only Set Range. If Short-Range is selected, you can select Set Range or Use Real Time.

Setting statistical storage ranges 7–3


Performance Monitor saves the statistics obtained up to 1440 times in SVP. Therefore, you can estimate the storing period of statistics with "gathering interval multiplied by 1440". For example, if you specify one minute for the gathering interval, the statistics for one day can be stored at the maximum from the following formula:

1 minute x 1440 = 1440 minutes = 24 hours = 1 day

This storing period is the range of display in the Monitor Performance windows. When you specify one minute for the gathering interval like the example above, Performance Monitor can display the statistics for one day (i.e., 24 hours) in the list and graph at the maximum. Also, when you specify 15 minutes for the gathering interval, Performance Monitor can display the statistics for 15 days in the list and graph at the maximum.

7–4 Setting statistical storage ranges


Working with graphs 8–1


8Working with graphs

This topic describes how to display graphs of statistics.

□ Basic operation

□ Objects that can be displayed in graphs

□ Usage rates of processor blade(s)

□ Usage rate of a data recovery and reconstruction processor

□ Usage rate of cache memory

□ Write pending statistics

□ Access paths usage statistics

□ Throughput of storage system

□ Size of data transferred

□ Response times

□ Cache hit rates

□ Back-end performance

□ Hard disk drive usage statistics

□ Hard disk drive access rates

□ ShadowImage usage statistics

8–2 Working with graphs


Basic operation Use Monitor Performance window to display graphs.




3. Click Monitor Performance in the Performance Monitor window.

The Monitor Performance window opens.

4. Select Long-Range or Short-Range as the storing period of statistics in the Data Range: field.

5. Select Set Range or Use Real Time as the displaying period of statistics in the Time Range: field. However, Use Real Time can be specified when Short-Range is selected.

Specify items to display graphs in the Performance Objects: field.

6. Select items in the Object: field.

Select items in the left field and then select detailed items in the right field. Detailed item changes by the items selected in the left field.

7. Select items in the Monitor Data: field.

Select items in the left field and then select detailed items in the right field.

8. Select the item to display graph in the Performance Object Selection: field.

Select the LDEV in the Available Objects field.

9. Click Add.

The added LDEV is displayed in the Selected Objects field.

10.To delete the unnecessary LDEV, select the LDEV and click Remove.

11.Click Apply.

The line graph is displayed on the graph panel in the Monitor window.

• A graph is displayed on the left of a graph panel, a explanatory note is displayed on a right of a graph panel.

• Up to 4 graph panels can be displayed.

• The graph panel can be maximized or minimized if you click the icon in the upper right of the graph panel.

• Up to 8 lines can be displayed in one graph panel.

• Up to 16 graphs can be displayed in all graph panels.

• In the graph panel, the unit of scale on vertical axis can be changed.

By using the list on the upper left of the graph panel, adjust the scale to display the maximum value of the graph. If the graph is too big, the display may not be able to displaying properly. For example, the line of the graph is too thick, or the graph panel is painted out in the color of the graph.



• If you locate the mouse cursor to each point of the graph, a detailed value is displayed with the tool chip.

• When you click the explanatory note on the right of the graph panel, you can display or hide points on the graph panel. However, If the graph is displayed only the one point on X axis, the graph is always displayed. Therefore you cannot switch the display of the point to non-display by clicking the explanatory note.

12.To close the graph, click Delete Graph or the icon which closes the window of the upper right corner in the graph panel.

Objects that can be displayed in graphs Set items to display graph in the Performance Objects: field of the Monitor Performance window. The outline of target objects and monitoring data that can be displayed in graphs is shown as follows:

Monitoring target object Monitoring data

Controller Usage rates of processor blade (%).

Usage rates of DRR (%).

Cache Usage rates of cache (%).

Write pending rates (%).

Access Path Usage rates of access path between CHA and ESW (%).

Usage rates of access path between DKA and ESW (%).

Usage rates of access path between MP Blade and ESW (%).

Usage rates of access path between cache and ESW (%).

Port Throughput (IOPS).

Data transfer (MB/s).

Response time (ms).

WWN Throughput of WWN (IOPS).

Data transfer of WWN (MB/s).

Response time of WWN (ms).

Throughput of port (IOPS).

Data transfer of port (MB/s).

Response time of port (ms).



Usage rates of processor blade(s)

Function

The usage rate of the processor blade (MP blade for short) shows the usage rate of a processor blade assigned to a logical device. If a usage rate of a processor blade is high, I/Os concentrate to a processor blade. Examine the distribution of I/Os to other processor blades.

Storing period

Short-Range or Long-Range can be specified.

Logical Device Total throughput (IOPS).

Read throughput (IOPS).

Write throughput (IOPS).

Cache hit (%).


Response time (ms).

Back transfer (count/sec).

Drive usage rate (%).

Drive access rate (%).

Usage rates of ShadowImage (%).

Parity Group Total throughput (IOPS).



Cache hit (%).


Response time (ms).


Drive usage rate (%).

LUN Total throughput (IOPS).



Cache hit (%).


Response time (ms).


External Storage Data transfer of logical devices (MB/s).

Response time of logical devices (ms).

Data transfer of parity groups (MB/s).

Response time of parity groups (ms).

Monitoring target object Monitoring data



Selecting of monitoring objects

Select monitoring objects in Performance Objects: field. The combination of items is shown as follows.

Usage rate of a data recovery and reconstruction processor

Function

A data recovery and reconstruction processor (DRR) is a microprocessor (located on the DKAs and channel adapters) that is used to generate parity data for RAID 5 or RAID 6 parity groups. The DRR uses the formula "old data + new data + old parity" to generate new parity.

If the monitor data shows high DRR usage overall, this can indicate high write penalty condition. Please consult your Hitachi Data Systems representative about high write penalty conditions.

Storing period




Usage rate of cache memory

Function

When you display monitoring results in a short range, the window displays the usage rates about the cache memory for the specified period of time.

Storing period

Short-Range can be specified.

Item on left side of Object: field

Item on right side of Object: field

Item on left side of Monitor Data:

field

Item on right side of Monitor Data:

field

Controller MP Usage Rate (%) None




field


field

Controller DRR Usage Rate (%) None



Selecting of Monitoring Objects


Write pending statistics

Function

The write pending rate indicates the ratio of write pending data to the cache memory capacity. The Monitor Performance window displays the average and the maximum write pending rate for the specified period of time.

Storing period




Access paths usage statistics

Function

An access path is a path through which data and commands are transferred within a storage system.

In a storage system, channel adapters control data transfer between hosts and the cache memory. Disk adapters control data transfer between the cache memory and hard disk drives. Data transfer does not occur between channel adapters and disk adapters. Data is transferred via the ESW (PCI Express Switch adapter) to the cache memory.

When hosts issue commands, the commands are transferred via channel adapters to the shared memory (SM). The content of the shared memory is checked by disk adapters.

Performance Monitor tracks and displays the usage rate for the following access paths.




field


field

Cache None Usage Rate (%) None




field


field

Cache None Write Pending Rate (%)

None



• Access paths between channel adapters and the cache switch (CHA ESW)

• Access paths between disk adapters and the cache switch (DKA ESW)

• Access paths between the cache switch and the cache memory (Cache ESW)

• Access paths between the MP blade and the cache switch (MP Blade ESW)

Storing period




Throughput of storage system

Function

Total throughput is the sum of I/Os per second. The read throughput is I/Os to the disk per second when the file read processing is performed. The write throughput is I/Os to the disk per second when the file write processing is performed.

Figure 8-1 Access paths




field


field

Access Path CHA ESW Usage Rate (%) None

DKA ESW Usage Rate (%) None

MP Blade ESW Usage Rate (%) None

Cache ESW Usage Rate (%) None



Throughput in the following modes can be displayed.

• Sequential access mode

• Random access mode

• Cache fast write (CFW) mode

• Total value in the above-mentioned mode

Storing period







field


field

Port None Throughput (IOPS) None

WWN WWN Throughput (IOPS) None

Port Throughput (IOPS) None

Logical Device None Total Throughput (IOPS)

Total

Sequential

Random

CFW

Read Throughput (IOPS)

Total

Sequential

Random

CFW

Write Throughput (IOPS)

Total

Sequential

Random

CFW



Size of data transferred

Function

The amount of data per second transferred from the host server. The transferred data of reading or writing process can be monitored.

Storing period




Parity Group None Total Throughput (IOPS)

Total

Sequential

Random

CFW


Total

Sequential

Random

CFW


Total

Sequential

Random

CFW

LUN None Total Throughput (IOPS)

Total

Sequential

Random

CFW


Total

Sequential

Random

CFW


Total

Sequential

Random

CFW




field


field



Response times

Function

Time (in milliseconds) for replying from an external volume group when I/O accesses are made from the VSP storage system to the external volume group. The average response time in the period specified at Monitoring Term is displayed.

Items that can be monitored response times are ports, WWNs, LDEVs, parity groups, LUNs, and external storages (parity groups and LDEVs).

Storing period







field


field

Port None Data Trans. (MB/s) None

WWN WWN Data Trans. (MB/s) None

Port Data Trans. (MB/s) None

Logical Device None Data Trans. (MB/s) Total

Read

Write

Parity Group None Data Trans. (MB/s) Total

Read

Write

LUN None Data Trans. (MB/s) Total

Read

Write

External Storage Parity Group Data Trans. (MB/s) Total

Read

Write

Logical Device Data Trans. (MB/s) Total

Read

Write



Cache hit rates

Function

The cash hit rate is a rate that the input or output data of the disk exists in the cache. The cash hit rate is displayed for the sequential access mode, the random access mode, the cache fast write (CFW) mode, and the entire these modes.

• Read hit ratio

For a read I/O, when the requested data is already in cache, the operation is classified as a read hit. For example, if ten read requests have been made from hosts to devices in a given time period and the read data was already on the cache memory three times out of ten, the read hit ratio for that time period is 30 percent. A higher read hit ratio implies higher processing speed because fewer data transfers are made between devices and the cache memory.

• Write hit ratio

For a write I/O, when the requested data is already in cache, the operation is classified as a write hit. For example, if ten write requests were made from hosts to devices in a given time period and the write data was already on the cache memory three cases out of ten, the write




field


field

Port None Response Time (ms) None

WWN WWN Response Time (ms) None

Port Response Time (ms) None

Logical Device None Response Time (ms) Total

Read

Write

Parity Group None Response Time (ms) Total

Read

Write

LUN None Response Time (ms) Total

Read

Write

External Storage Parity Group Response Time (ms) Total

Read

Write

Logical Device Response Time (ms) Total

Read

Write



hit ratio for that time period is 30 percent. A higher write hit ratio implies higher processing speed because fewer data transfers are made between devices and the cache memory.

Storing period







field


field

Logical Device None Cache Hit (%) Read (Total)

Read (Sequential)

Read (Random)

Read (CFW)

Write (Total)

Write (Sequential)

Write (Random)

Write (CFW)

Parity Group None Cache Hit (%) Read (Total)

Read (Sequential)

Read (Random)

Read (CFW)

Write (Total)

Write (Sequential)

Write (Random)

Write (CFW)

LUN None Cache Hit (%) Read (Total)

Read (Sequential)

Read (Random)

Read (CFW)

Write (Total)

Write (Sequential)

Write (Random)

Write (CFW)



Back-end performance

Function

The back-end transfer can be monitored. The back-end transfer is the number of data transfers between the cache memory and the hard disk drive. The graph contains following information.

• Cache to Drive

The number of data transfers from the cache memory to hard disk drives.

• Drive to Cache Sequential

The number of data transfers from hard disk drives to the cache memory in sequential access mode

• Drive to Cache Random

The number of data transfers from hard disk drives to the cache memory in random access mode

Storing period







field


field

Logical Device None Back Trans. (count/sec)

Total

Cash to Drive

Drive to Cash (Sequential)

Drive to Cash (Random)

Parity Group None Back Trans. (count/sec)

Total

Cash to Drive



LUN None Back Trans. (count/sec)

Total

Cash to Drive





Hard disk drive usage statistics

Function

The usage rates of the hard disk drive of each LDEV or parity group can be displayed.

Storing period




Hard disk drive access rates

Function

The hard disk drive access rate shows the access rate of each hard disk drive (HDD).

The rate of the file reading Read (Sequential) or the file writing Write (Sequential) processing of HDD in the sequential access mode is displayed.

The rate of file reading Read (Random) or file writing Write (Random) processing of HDD in the random access mode is displayed.

Storing period

Long-Range or Short-Range can be specified.






field


field

Logical Device None Drive Usage Rate (%)

None

Parity Group None Drive Usage Rate (%)

None



ShadowImage usage statistics

Function

The access rate of volume by ShadowImage can be displayed the percentage of the processing of the program to all the processing of the physical drives, for each volume. This value is found by dividing access time to physical drives by the program by all the access time to physical drives.

Storing period







field


field

Logical Device None Drive Access Rate (%)

Read (Sequential)

Read (Random)

Write (Sequential)

Write (Random)




field


field

Logical Device None ShadowImage (%) None



Changing display of graphs 9–1


9Changing display of graphs

This topic describes how to change displaying of graphs.

□ Graph operation

□ Changing displayed items

□ Changing a display period

□ Adding a new graph

□ Deleting graph panel

9–2 Changing display of graphs


Graph operationInformation displayed in the graph can be changed. The following operation can be performed.

• Displayed items in the graph can be changed

For details, see Changing displayed items on page 9-2.

• Displayed periods in the graph can be changed

For details, see Changing a display period on page 9-2

• Add new graph

For details, see Adding a new graph on page 9-3.

• Delete graph panel

For detail, see Deleting graph panel on page 9-3.

Changing displayed itemsUse Edit Performance Objects window to change displayed items in the graph.

1. Display graph in the Monitor Performance window.

For details, see Basic operation on page 8-2.

2. Click Edit Performance Objects.

The Edit Performance Objects window opens.

3. Change displayed items in the information setting field at the left of the window.


4. Click Add.

Items are added in the Selected Objects field.

5. If you want to delete the item, select the item and then click Remove.

6. Click OK

The graph is displayed.

Changing a display periodUse Edit Time Range window to change a display period in the graph.



2. Click Edit Time Range.

The Edit Time Range window opens.

3. Input the date when the display of the graph begins in the From: field. Input the date when the display of the graph is ended in the To: field.

4. Click OK

The graph is displayed.

Changing display of graphs 9–3


Adding a new graph Use Monitor Performance window to add a new graph.



2. Click Add Graph.

The Add Graph window opens.

3. Change displayed items in the information setting field at the left of the window.


4. Click Add.

Items are added in the Selected Objects field.

5. If you want to delete the item, select the item and then click Remove.

6. Click OK

The graph is added.

Deleting graph panelA graph panel can be deleted from the Monitor Performance window.



2. Click Delete Graph or the icon that close the window displayed in the upper right of the graph panel.

3. A warning message appears, asking whether you want to delete the graph panel.


The graph panel is deleted.

9–4 Changing display of graphs


Creating virtual cache partitions 10–1


10Creating virtual cache partitions

This topic provides detailed instructions for dividing storage system cache memory into virtual cache logical partitions (CLPRs) using Hitachi Virtual Partition Manager software.

□ About virtual cache partitions

□ Cache partitioning rules and guidelines

□ Partitioning cache

□ Troubleshooting Virtual Partition Manager

10–2 Creating virtual cache partitions


About virtual cache partitions If one storage system is shared with multiple hosts, one host reading or writing a large amount of data can require enough of the storage system’s cache memory to affect other users. The Hitachi Virtual Partition Manager function allows improved I/O performance by dividing storage system cache memory into multiple virtual cache memories (cache logical partitions or CLPRs).

Partitioning cache dedicates cache resources for exclusive use by specific applications to maintain priority and quality of service for business-critical applications. Storage administrators can secure and/or restrict access to storage resources to ensure confidentiality for specific applications. By dedicating resources to each partition as needed, a high quality of service can be maintained for all users.

Partitioning cache supports Application Optimized Storage™ solutions from Hitachi Data Systems to match data to appropriate storage resources based on availability, performance, capacity, and cost. It improves flexibility by allowing dynamic changes to cache partitions while in use.

The following illustrates the use of cache memory within a corporation. In this example, cache memory is partitioned into three segments of 40 GB, each of which is allocated to a branch office. The host of branch A has a heavy I/O load. Because the cache memory is partitioned, that heavy I/O load does not impact the cache memory for the other two branches.



Cache capacity for a CLPRA CLPR is a pool of the cache and parity groups in the storage system. Partitioning cache into one or more CLPRs allows storage administrators to dedicate individual CLPRs to a different host, preventing I/O contention for cache memory.

Before partitioning cache memory into CLPRs, calculate how much cache capacity will be needed on your storage system, and then install any needed additional cache memory. It will be difficult to add more cache memory after partitioning cache into CLPRs.

To determine whether you need additional cache capacity, refer to the following table and formulas. The recommended cache capacity for an internal volume is determined by the storage capacity assigned to the cache logical partition.

Table 10-1 CLPR data capacity and recommended cache capacity

To calculate CLPR data capacity:

number of 3D+1P parity groups x capacity of one HDD x 3 + number of 6D+2P parity groups x capacity of one HDD x 6 + number of 7D+1P parity groups x capacity of one HDD x 7 + number of 2D+2D parity groups x capacity of one HDD x 2

To calculate the cache capacity for a CLPR:

cache capacity (GB) = recommended cache capacity (GB) + ceiling (Cache Residency Manager capacity (MB) / 2,048) x 2 GB

CLPR data capacity Processor blade Recommended cache capacity

Less than 2,900 GB 2 8 GB or more

4 16 GB or more

6 24 GB or more

8 32 GB or more

2,900 GB or more 2 or 4 16 GB or more

6 24 GB or more

8 32 GB or more

14,400 GB or more 2, 4 or 6 24 GB or more

8 32 GB or more

128,000 GB or more 2, 4, 6 or 8 32 GB or more

182,000 GB or more 40 GB or more







When you use an external volume or a virtual volume, you cannot use the above formula. If you use an external volume, calculate the capacity of parity group that is associated to the CLPR, and then calculate the cache capacity according to the data capacity and the recommended capacity in the above table. If you use a virtual volume, calculate the total LDEV capacity of the virtual volume that is associated to the CLPR, and then calculate the cache capacity according to the data capacity and the recommended capacity in the above table. To check the LDEV capacity of the virtual volume, see the LDEV dialog box in the Basic Information Display dialog box of the Storage Navigator subwindow. For further information about Storage Navigator subwindow, see the Hitachi Storage Navigator User Guide.

When adding cache memory, use either the Standard Cache Access Model mode or the High Performance Cache Access Model mode. If your storage system has any additional printed circuit boards (PCBs), you must use the High Performance Cache Access Model mode. For more information about adding cache memory, contact the Hitachi Data Systems Support Center.

After installing and partitioning cache memory in one or more CLPRs, you may want to use Cache Residency Manager software to manage your cache. For more information, see the Performance Guide.

Cache partitioning rules and guidelinesObserve the following rules, restrictions, and guidelines when creating cache logical partitions:

Rules• In order to partition cache, Virtual Partition Manager must be enabled on

your system.

• CLPR0 is the default CLPR in a storage system. If you have not yet created any cache logical partitions, all cache belongs to CLPR0.

• Usually, you can create a CLPR if the sybsystem has 4 GB cache. However, when creating a CLPR while using Cache Residency Manager, the remaining cache size, which is calculated by subtracting Cache Residency Manager size from the cache size of CLPR0, must be 8 GB or more.

• Adding or changing CLPR definitions or configurations may take hours to implement and can not be canceled or modified until all changes are complete. For assistance or for more information, contact your Hitachi Data Systems account team.

Restrictions

The following operations are not allowed when multiple CLPRs are involved:

• Creating LUSE volumes across multiple CLPRs. If you forcibly perform this operation and create a LUSE across multiple CLPRs, the LUSE volumes cannot be used for TrueCopy or TrueCopy for Mainframe pair volumes.



• ShadowImage Quick Restore operations that affect multiple CLPRs.

• Volume Migration manual migration operations that affect multiple CLPRs.

• A parity group containing LDEVs assigned to Cache Residency Manager cache extents (cache areas) cannot be migrated to another CLPR. See the Performance Guide for more information about cache extents.

• If you are using Universal Replicator, Universal Replicator data volumes and journal volumes can belong to different CLPRs. All journal volumes in the same journal must belong to the same CLPR. If not, an error occurs.

Guidelines• Install any needed additional cache memory before partitioning cache.

It will be difficult to add additional cache memory after partitioning cache into CLPRs.

• If the cache capacity of defined CLPR is decreased by the Cache Residency Manager cache area, cancel the setting of bind mode or priority mode of Cache Residency Manager, change the cache capacity of CLPR, and then set the bind mode or priority mode again.

• When the Cache Residency Manager is used with CLPR, we recommend that you decide the remaining cache capacity of each CLPR after subtraction of cache capacity for Cache Residency Manager according to Table 10-1 CLPR data capacity and recommended cache capacity on page 10-3.

• Best practice is to create cache logical partitions either during the initial installation and setup or during a maintenance window, because cache logical partition operations can significantly degrade host performance. If you must perform such operations on a production machine, use Hitachi Performance Monitor to verify that the write pending rate, including spikes, is well below 30%. See the Performance Guide for more information.

Partitioning cache

Cache partition work flows

Creating a CLPR1. Create a CLPR (see Creating a CLPR on page 10-6).

2. Migrate resources to the new CLPR (see Migrating resources to and from a CLPR on page 10-7).

Removing a CLPR1. Migrate resources from the CLPR that is to be removed (see Migrating

resources to and from a CLPR on page 10-7).

2. Delete the CLPR (see Deleting a CLPR on page 10-8).



Creating a CLPRBefore creating a CLPR, review Cache partitioning rules and guidelines on page 10-4.

1. Click Settings>Environmental Setting> Partition Definition on the menu bar of the Storage Navigator main window.

2. Click to change the mode from View to Modify.

3. In Virtual Partition Manager, open the Partition Definition window, and select a CLPR in the Partition Definition tree.

4. In the Cache Logical Partition window, right-click a CLPR from the Partition Definition tree and select Create CLPR. This adds a cache logical partition to the Partition Definition tree. The maximum number of CLPRs that can be manually created is 31 (not including CLPR0).

5. Select the newly created CLPR to open the Cache Logical Partition window.

6. In the Detail for CLPR Subsystem section, do the following:

• In CLPR Name, type the name of the cache logical partition, in up to 16 alphanumeric characters.

• In Cache Size, select the cache capacity. You may select from 4 to 508 GB, in 2 GB increments. The default value is 4 GB. The size of the cache is allocated from CLPR 0, but you must leave at least 8 GB remaining in CLPR 0.



• In Cache Residency Manager Size, select the cache capacity. You may select from 4 to 508 GB, in 2-GB increments. The default value is 4 GB. The size of the cache is allocated from CLPR0, but you must leave at least 8 GB remaining in CLPR0.

• In Num of Cache Residency Manager Areas, type the desired capacity for the Cache Residency Manager area. The range of values is 0 to 16384 and the default value is 0.

7. Click Apply. The progress bar is appeared. The change in cache capacity is reflected in this cache logical partition and in CLPR0.

8. To change the settings of an existing CLPR, repeat steps 5 through 7.

At this point, the CLPR has no parity groups. You can now migrate resources to the new CLPR (see Migrating resources to and from a CLPR on page 10-7).

Migrating resources to and from a CLPRAfter adding a CLPR, you must migrate resources (parity groups) from existing CLPRs to the new CLPR. Before deleting a CLPR, you must first migrate resources from that CLPR to CLPRs that will not be deleted.

When migrating resources to and from cache logical partitions:

• You can migrate resources only within the same CU.

• All interleaved parity groups must be in the same CLPR.

• LUSE volumes cannot be set across more than one CLPR.

• If a parity group contains one or more LDEVs that have defined Cache Residency Manager extents, you cannot migrate that parity group to another CLPR.

To migrate resources to and from a CLPR

1. Click Settings>Environmental Setting>Partition Definition on the menu bar of the Storage Navigator main window.


3. Access the Logical Partition window, then select a CLPR from the Partition Definition tree.

4. In the Cache Logical Partition window, click Select CU to choose a CU.

5. Specify how you want to view information the CLPR resource list. In the Select CU dialog box, choose one of the following:

• All CUs: Shows the information about all CUs on the CLPR resource list.

• Choose Specific CU, then specify the LDKC and the CU. This shows only CLPRs from the selected CU.

• Unallocated: Shows information about only the CUs unallocated to CLPR on the CLPR resource list.



6. Click Set to close the dialog box.

7. From the Cache Logical Partition Resource List, select one or more parity groups to be migrated, then select Cut.

8. On the Partition Definition tree, right-click the CLPR to which you want to migrate resources, and then select Paste Resources.

9. Click Apply. The progress bar is appeared.

Deleting a CLPR Before deleting CLPR, be sure to migrate any resources (e.g., parity groups) to CLPR that will not be deleted (see Migrating resources to and from a CLPR on page 10-7 for more information).

Unnecessary CLPRs may be deleted, but CLPR0 cannot be deleted.

To delete a CLPR:

1. Click Settings>Environmental Setting>Partition Definition on the menu bar of the Storage Navigator main window.


3. Select a CLPR in the Partition Definition tree to open the Cache Logical Partition window.

4. Right-click the CLPR that you want to delete and select Delete CLPR.

5. Click Apply. The progress bar is appeared.

Troubleshooting Virtual Partition Manager

Displaying an error message

If the settings contain a discrepancy after clicking Apply, an error message will appear. After closing the message, you can later refer to the error detail.

To display an error message:



1. Right-click a CLPR on the Partition Definition tree, then select Error Detail to open the message.

2. Review the message and click OK to close the message.

General troubleshooting

The following table provides general troubleshooting instructions for Virtual Partition Manager operations.

Table 10-2 General troubleshooting for Virtual Partition Manager operations

Error Cause

When you attempt to migrate a parity group to another CLPR, an LU warning message appears.

LUSE volumes cannot be set across more than one CLPR.

The CLPR name cannot be changed.

You cannot assign the same name to more than one CLPR. The name you entered is already being used or is reserved by a system. Enter another name.

The parity group in a CLPR cannot be migrated to another CLPR.

• Only open-system parity groups can be migrated. • Make sure that all interleaved parity groups

belong to the same CLPR.• Make sure to click Apply when creating a new

CLPR.



Estimating cache size 11–1


11Estimating cache size

This topic describes how to estimate the cache size required for using Cache Residency Manager.

□ About cache size

□ Calculating cache size for open systems

□ Calculating cache size for mainframe systems

□ Cache Residency Manager extents

□ Cache Residency Manager system specifications

11–2 Estimating cache size


About cache sizeThe required cache size for using Cache Residency Manager differs according to operation modes or RAID levels. For example, if the bind mode is set, RAID1 storage systems require twice the size of cache for the user data to use Cache Residency Manager. However, RAID5 or RAID6 storage systems require three times the size of cache. If external volumes are used, twice the cache size for the user data is required to use Cache Residency Manager.

If the priority mode or the bind mode is set, the cache size is calculated assuming that one slot has the following values.

• For open-systems volumes:

• For OPEN-V, one slot is 264 KB (512 LBAs).

• For other than OPEN-V, one slot is 66 KB (128 LBAs).

• For mainframe (3390) volumes:

• One slot is 66 KB (128 LBAs).

Calculating cache size for open systems1. Calculate the converted values of the starting address and the ending

address.

For all specified LDEVs: a. For OPEN-V

Number of LBAs = LDEV size (KB)×2

Convert the LDEV size to the number of LBAs.

Number of slots = ceil (Number of LBA ÷ 512)

Round up the value that is calculated from the formula enclosed by ceil().

Converted value of starting address = 0

Converted value of ending address = (Number of slots × 512) - 1 b. For emulation types other than OPEN-V:

Number of LBAs = LDEV size (KB) × 2

Convert the LDEV size to the number of LBAs

Number of slots = ceil (Number of LBAs ÷ 96)

Note: If a RAID5 or RAID6 volume area is changed from priority mode to bind mode and no cache is added, then only 33% of the user data will fit in the area previously assigned for priority mode, and the remaining 67% is used to save read/write data.

If a RAID1 volume area is changed from priority mode to bind mode and no cache is added, then only 50% of the user data will fit in the area previously assigned for priority mode, and the remaining 50% is used to save read/write data.

Changing the mode without cache extension requires reconfiguring Cache Residency Manager.



Round up the value that is calculated from the formula enclosed by ceil().


Converted value of ending address = (Number of slots × 96) - 1

If the volumes are specified:a. for OPEN-V

Starting value = floor (Setting value of starting address (LBA) ÷ 512)

Round down the value that is calculated from the formula enclosed by floor(). "Setting value of starting address (LBA)" is the value which is input on the Cache Residency window.

Ending value = floor (Setting value of ending address (LBA) ÷ 512)

Round down the value that is calculated from the formula enclosed by floor(). "Setting value of ending address (LBA)" is the value which is input on the Cache Residency window.

Converted value of starting address = Starting value × 512

Converted value of ending address = ((Ending value + 1) × 512) - 1b. For emulation types other than OPEN-V:

Starting value = floor (Setting value of starting address (LBA) ÷ 96)

Round down the value that is calculated from the formula enclosed by floor(). "Setting value of starting address (LBA)" is the value which is input on the Cache Residency window.

Ending value = floor (Setting value of ending address (LBA) ÷ 96)

Round down the value that is calculated from the formula enclosed by floor(). "Setting value of ending address (LBA)" is the value which is input on the Cache Residency window.

Converted value of starting address = Starting value × 96

Converted value of ending address = ((Ending value + 1) × 96) - 1

2. Calculate the number of addresses between the starting address and the ending address calculated in step 1.a. For OPEN-V:

Number of addresses = Converted value of ending address - Converted value of starting address + 1

Calculate the number of LBAs that are used by the user data.b. For emulation types other than OPEN-V:

Number of LBAs = Converted value of ending address - Converted value of starting address + 1

Calculate the number of LBAs that are used by the user data.

Number of slots = Number of LBAs ÷96

Convert the number of LBAs to the number of slots.

Number of addresses = Number of slots × 128

Convert the number of slots with 128 LBA.



3. Calculate the required cache size according to the operation modes, or the RAID levels to use Cache Residency Manager.a. Where the bind mode is set:

For RAID1

Required cache size = No. of addresses × (512 + 16) × 2 ÷ 1,024

The unit is KB.

For RAID type other than RAID1:

Required cache size = No. of addresses × (512 + 16) × 3 ÷ 1,024

The unit is KB.b. Where the priority mode is set:

Required cache size = Number of addresses × (512 + 16) ÷ 1,024

The unit is KB.

Calculating cache size for mainframe systems1. Calculate the converted values of the starting address and the ending

address.a. For all specified LDEVs:

Setting value of ending address (CC) = floor (((LDEV size × 15) - 1) ÷ 15)

Round down the value that is calculated from the formula enclosed by floor(). "Setting value of ending address (CC)" is the value which is input on the Cache Residency window.

Setting value of ending address (HH) = ((LDEV size × 15) - 1) Mod 15

The remainder will be the setting value of ending address (HH).

"Setting value of ending address (HH)" is the value which is input on the Cache Residency window.


Converted value of ending address = Setting value of ending address (CC) × 15 + Setting value of ending address (HH)

"Setting value of ending address (CC)" and "Setting value of ending address (HH)" is the value which is input on the Cache Residency window.

b. If the volumes are specified:

Converted value of starting address = Setting value of starting address (CC) × 15 + Setting value of starting address (HH)


Converted value of ending address = Setting value of ending address (CC) × 15 + Setting value of ending address (HH)




2. Calculate the number of addresses between the starting address and the ending address calculated in step 1:

Number of addresses = Converted value of ending address - Converted value of starting address + 1

Calculate the number of addresses of cache that are used by the user data.

3. Calculate the required cache size according to the operation modes, or the RAID levels to use Cache Residency.a. Where the bind mode is set:

For RAID1

Required cache size = (Number of addresses × ((128 × (512 + 16)) × 2) ÷ 1,024

The unit is KB.b. Where the priority mode is set:

Required cache size = (Number of addresses × (128 × (512 + 16))) ÷ 1,024

The unit is KB.

Cache Residency Manager extentsThe Cache Residency Manager cache areas (called cache extents) have the following parameters:

• The cache extents are dynamic and can be added and deleted at any time.

• The VSP supports a maximum of 1,024 addressable cache extents per LDEV and per storage system.

• For mainframe volumes, each Cache Residency Manager cache extent must be defined on contiguous tracks, with a minimum size of one cache slot (or track) and a maximum size of one LVI. This is equivalent to 66 KB.

• For OPEN-V volumes, Cache Residency Manager cache extents must be defined in logical blocks using logical block addresses (LBAs), with a minimum size of 512 LBAs (equivalent to 264 KB). However, in most cases you will assign an entire open-system volume for Cache Residency. If the remaining cache memory is less than 256 MB, Cache Residency Manager is not available.



• You can prestage the data to the resident cache area. If prestaging is not used, the data will be loaded into the Cache Residency Manager extents when the first "miss" occurs. If prestaging is used, performance may be affected for a short time while the data is read into Cache Residency Manager cache.

• All write I/Os to Cache Residency Manager data are duplex writes, guaranteeing full data integrity. The Cache Residency Manager data remains fixed in cache until you manually delete it. Deletion of Cache Residency Manager extents will destage any write data to the affected volume(s).

• It is possible to expand the amount of Cache Residency Manager cache without canceling the existing Cache Residency Manager settings. call the Support Center.

Cache Residency Manager system specifications

Caution: Prestaging of Cache Residency Manager data should not be performed during peak activity.

ItemSpecification

Open system Mainframe system

Emulation Type OPEN-VOPEN-3, 8, 9, E, L

3380-3, 3A, 3B, 3C, KA, KB, KC3390-3, 3A, 3B, 3C, 3R, 9, 9A, 9B, 9C, L, LA, LB, LC, M, MA, MB, MC

Supported volumes LUN Expansion (LUSE) volumeVirtual LUN volume

Virtual LVI volume

Unit of cache area allocation

For OPEN-V, at least 512 LBAs: Equivalent to 264 KBFor other than OPEN-V, at least 96 LBAs: Equivalent to 66 KB

At least one cache slot (or track): Equivalent to 66 KB.Up to 1 LDEV.

Number of cache areas

Per storage system: 16,384Per LDEV: 4,096

Managing resident cache 12–1


12Managing resident cache

This topic provides information and instructions for using Cache Residency Manager software to manage resident cache.

□ Cache Residency Manager rules, restrictions, and guidelines

□ Launching Cache Residency

□ Viewing Cache Residency information

□ Placing specific data into Cache Residency Manager cache

□ Placing LDEV(s) into Cache Residency Manager cache

□ Releasing specific data from Cache Residency Manager cache

□ Releasing LDEV(s) from Cache Residency Manager cache

□ Changing mode after Cache Residency is registered in cache

12–2 Managing resident cache


Cache Residency Manager rules, restrictions, and guidelines

Rules• Cache Residency Manager must be enabled on Storage Navigator.

• Administrator or Cache Residency Manager write access to the Storage Navigator software is required to perform Cache Residency Manager operations. Users without write access can view Cache Residency Manager information for the connected storage system but cannot set or change options.

• Do not attempt to allocate Cache Residency Manager cache beyond the allocated capacity.

• Do not apply Cache Residency Manager settings to volumes reserved for Volume Migration.

• Do not attempt to allocate Cache Residency Manager cache redundantly over the cache area that is already allocated to an LDEV.

• Do not apply or refer to Cache Residency Manager settings to volumes from the host and Storage Navigator at the same time. You can apply the settings from the host if you use Cache Manager.

• If you specify the Cache Residency Manager setting on the volume during quick formatting, do not use the prestaging function. If you want to use the prestaging function after the quick formatting processing completes, release the setting and then specify the Cache Residency Manager setting again, with the prestaging setting enabled this time. For information about quick formatting, see the Provisioning Guide for Open Systems or the Provisioning Guide for Mainframe Systems.

• Do not perform the ShadowImage quick restore operation or the Volume Migration operation on a Cache Residency Manager volume. Also, do not specify the Cache Residency Manager setting on the volume on which the ShadowImage quick restore or Volume Migration operation is performed. These operations swap the internal locations of the source and target volumes, which causes a loss of data integrity. For additional information, see the Hitachi ShadowImage® User Guide and/or contact the Hitachi Data Systems Support Center.

• To set Cache Residency Manager for a LUSE volume, you must set Cache Residency Manager for an LDEV that is a component of the LUSE volume. To determine the LDEV for which you want to set Cache Residency, you must know the exact number of LBAs in each LDEV that is a component of the LUSE volume.

To identify the exact number of LBAs in a LDEV, first display the Storage Navigator main window and search for the parity group to which the LDEV belongs according to the LDKC, control unit (CU), and LDEV numbers. For further information about the Basic Information Display window, see the Hitachi Storage Navigator User Guide.

Note: The number of LBAs displayed on the Cache Residency window is different from the actual number of LDEVs, and does not match the number of LBAs recognized by the host.



As illustrated in Figure 12-1 Example of LBA Value Setting When Using LUSE on page 12-3, the LUSE volume is composed of three LDEVs, i.e., 00:01 (1,000 LBAs), 00:02 (1,002 LBAs), and 00:03 (1,020 LBAs). If you see from the host and want to set Cache Residency Manager to 500 LBAs starting from No. 1,020 LBA, you may set the Cache Residency Manager to 500 LBAs starting from No. 20 LBA of the 2nd LDEV because the first LDEV size is 1,000 LBAs.

The following operations automatically reset Cache Residency Manager cache:

• When LDEVs that is partly or wholly assigned to Cache Residency Manager is deleted.

• When the parity group containing LDEVs that are assigned to Cache Residency Manager is deleted.

Restrictions• The Cache Residency Manager bind mode is not available to external

volumes whose Cache mode is set to Disable (which is the mode that disables the use of the cache when there is an I/O request from the host).

• You cannot allocate pool-VOLs and V-VOLs for Cache Residency Manager. For further information about pool-VOLs and V-VOLs, see the Hitachi Copy-on-Write Snapshot User Guide, the Provisioning Guide for Open Systems, or the Provisioning Guide for Mainframe Systems

• You cannot allocate the journal volumes for Cache Residency Manager. For additional information about the journal volumes, see the Hitachi Universal Replicator User Guide or the Hitachi Universal Replicator for Mainframe User Guide.

• You cannot allocate the remote command device for Cache Residency Manager. For further information about the remote command device, see the Hitachi Universal Volume Manager User Guide.

Figure 12-1 Example of LBA Value Setting When Using LUSE



Guidelines• Performing Cache Residency Manager operations on many LDEVs during

host I/O may cause the host I/O response time to become slow. To avoid degradation of response time, set only one LDEV at a time.

• Deleting data from cache during host I/O may cause the response time of host I/O to become slow. To avoid degradation of host response time, limit the amount of data you delete in one operation as follows:

If the host timeout period is set to 10 seconds or shorter, limit the total amount of data to:

• 1 GB or less for open systems

• 1,000 cylinders or less for mainframe systems

If the host timeout period is set to 11 seconds or longer, limit the total amount of data to:

• 3 GB or less for open systems

• 3,000 cylinders or less for mainframe systems

• If you use Cache Residency Manager to set the bind mode, while the mode setting of the battery back-up system is de-staging, you run a risk that should the electric power be shut off, battery power may also run out before the de-staging processing is completed. To avoid this risk, do not set the bind mode if the mode setting of the battery back-up system is de-staging. Contact your system manager for information about the current mode setting of the battery back-up system.

Launching Cache Residency1. Log on to the primary SVP. When you successfully log on to the primary

SVP, the Storage Navigator main window opens.

2. On the menu bar of the Storage Navigator main window, click Actions> Other function>Cache Residency.



3. In the Cache Residency window, click .Change the mode between the view mode and modify mode.

Viewing Cache Residency informationThe Cache Residency information can be viewed in the following fields in the Cache Residency window.

• CU:LDEV tree

• LDEV information table

• Cache information area

Placing specific data into Cache Residency Manager cacheThis procedure places specific data from one or more LDEVs into Cache Residency Manager cache.

1. In the Cache Residency window, select the desired CLPR from the CLPR: list.

2. In the CU:LDEV tree, select the LDKC and the CU containing the desired LDEV, and then select the desired LDEV.



The LDEV information table shows the information for the selected LDEV. A dash (-) in the Mode column indicates an area not already allocated to Cache Residency Manager cache.

3. Select an unallocated area in the LDEV information table as the area to place specific data from one or more LDEVs into Cache Residency Manager cache. The starting and ending addresses of the selected area are displayed in the Start and End fields.

4. In the Cache Residency window, select options to apply to all selected LDEVs:a. In the Cache Residency Mode box, select the desired mode (Bind

or Priority).b. Select the desired Prestaging Mode setting (Yes or No). To set the

prestaging function, the Prestaging check box must already be selected.

c. Verify the starting and ending addresses of the area to be placed in Cache Residency Manager cache in the Start and End fields. Edit as needed. Make sure that the Select All Area box is NOT checked.

5. If you do not want to apply the same options to any other LDEV, make sure that the Multi Set / Release box is not checked, click Set, and then click OK on the confirmation dialog box. The requested Cache Residency Manager operation appears in blue in the LDEV information table.

To apply the same options and data range to additional LDEVs:a. On the Cache Residency window, select the Multi Set / Release

box, click Set, and then click OK. The Multi Set dialog box opens showing the data range and options selected on the Cache Residency window.

Note: For OPEN-V LUs, Cache Residency Manager identifies a logical area in units of 512 blocks. If you enter 0 or 1 as the starting LBA and a value less than 511 as the ending LBA, Cache Residency Manager automatically changes the ending block address to 511.

Caution: Make sure to select the correct options because the options cannot be changed after data is added to cache. To change between bind/priority modes, or to enable/disable the prestaging function, release the cache extent that you want to change, and then place the data back into Cache Residency Manager cache with the desired settings.



b. In the Multi Set dialog box, select the desired LDKC and CU image, and select the desired LDEV(s). The data range and options displayed in the dialog box will be applied to all selected LDEVs.

c. Click Set to return to the Cache Residency window. The requested Cache Residency Manager operations appear in blue in the LDEV information table.

6. Repeat steps (2)-(5) until all desired operations are listed. The Release is unavailable until you apply (or cancel) your requested operation(s).

7. Verify the Prestaging setting:

• To enable prestaging, select Prestaging.

• To disable prestaging, clear Prestaging.

8. To start the operation(s), click Apply. If Prestaging was selected, respond to the Yes/No confirmation. To continue with prestaging, click Yes. To continue without it, click No.

9. Monitor the Cache Residency window to make sure that the operation(s) complete successfully. The cache information area shows the progress of the requested operation(s).

Placing LDEV(s) into Cache Residency Manager cacheThis procedure places ALL data on one or more LDEVs into Cache Residency Manager cache.

1. In the Cache Residency window, select the desired CLPR from the CLPR list.




The LDEV information table shows the information for the selected LDEV. A dash (-) in the Mode column indicates an area not already allocated to Cache Residency Manager cache.

3. In the Cache Residency window, select desired options:a. In the Cache Residency Mode box, select the desired mode (Bind

or Priority).b. Select the desired Prestaging Mode setting (Yes or No). To set the

prestaging function, the Prestaging check box must already be selected.

c. Check the Select All Area box. Leave the Start and End fields blank.

4. If you do not want to apply the same options to any other LDEVs, make sure that the Multi Set / Release box is not checked, click Set, and then click OK on the confirmation dialog box. The requested operation appears in blue in the LDEV information table.

To apply the same options to additional LDEVs:a. In the Cache Residency window, select the Multi Set / Release

box, click Set, and then click OK. The Multi Set dialog box opens showing the data range and options selected on the Cache Residency window.

b. In the Multi Set dialog box, select the desired CU image, and select the desired LDEV(s). The options displayed on the dialog box will be applied to all selected LDEVs.

c. Click Set to return to the Cache Residency window. The requested Cache Residency Manager operations appears in blue in the LDEV information table.

5. Repeat steps (2)-(4) until all desired operations are listed. The Release is unavailable until you apply (or cancel) your requested operation(s).




7. To start the operation(s), click Apply:

• If Prestaging was selected, respond to the Yes/No confirmation. To continue with prestaging, select Yes. To continue without it, select No.

• To cancel the operation, click Cancel and click OK on the confirmation.


Caution: Make sure to select the correct options, because the options cannot be changed after a cache extent is added. To change between bind/priority modes, or to enable/disable the prestaging function, release the cache extent that you want to change and then place the data back into Cache Residency Manager cache with the desired settings.



Releasing specific data from Cache Residency Manager cache

This procedure releases specific data area(s) on one or more LDEVs from Cache Residency Manager cache.



The LDEV information table shows the information for the selected LDEV. The Mode column indicates Prio or Bind for each data area that is allocated to Cache Residency Manager cache.

3. Select the data area(s) that you want to release from Cache Residency Manager cache. This enables the Release.

4. Click Release, and click OK on the confirmation message.

The requested operation is displayed in blue in the LDEV information table.

5. Repeat steps (2)-(4) for each LDEV for which you want to release specific data from Cache Residency Manager cache. The Set is unavailable until you apply (or cancel) your requested operation(s).





• If Prestaging was selected, respond to the Yes/No confirmation. To continue with prestaging, select Yes. To continue without it, select No.


8. When the delete confirmation message appears, click OK to begin the deletion, or click Cancel to cancel your request to delete data.


When the data has been released, the verification window will appear.

Releasing LDEV(s) from Cache Residency Manager cacheThis procedure releases ALL data on one or more LDEVs from Cache Residency Manager cache.





The LDEV information table shows the information for the selected LDEV. The Release is available if the selected LDEV has data that is stored in Cache Residency Manager cache (indicated by Prio or Bind in the Mode column).

3. If you do not want to release any other LDEVs from Cache Residency Manager cache, make sure that the Multi Set / Release box is not checked, click Release, and then click OK on the confirmation dialog box. The requested operation appears in blue in the LDEV information table.

To release additional LDEVs from Cache Residency Manager cache:a. Check the Multi Set / Release box, click Release, and then click

OK on the confirmation message.

b. In the Multi Release dialog box, select the desired LDKC and CU image, and select the desired LDEV(s) to release from Cache Residency Manager cache.

c. Click Release to return to the Cache Residency window. The requested Cache Residency Manager operations appear in blue in the LDEV information table.

4. Repeat steps (2) and (3) until all desired operations are listed.




Note: The Set is unavailable until you apply (or cancel) your requested operation(s).




• If Prestaging was selected, respond to the Yes/No confirmation. To continue with prestaging, click Yes. To continue without it, click No.



Changing mode after Cache Residency is registered in cache

If Cache Residency is registered in the cache, the following mode options appear gray and are unavailable for change:

• Cache Residency Mode (Bind, Priority)

• Prestaging Mode (Yes, No)

To change the mode options:

1. Release the specific data from the Cache Residency cache. For details, see Releasing specific data from Cache Residency Manager cache on page 12-9.

2. Restore the data with the new settings. For details, see Placing specific data into Cache Residency Manager cache on page 12-5.



Troubleshooting 13–1


13Troubleshooting

This topic provides references to sources of troubleshooting information and contact information for the Hitachi Data Systems Support Center.

□ Troubleshooting

□ Calling the Hitachi Data Systems Support Center

13–2 Troubleshooting


Troubleshooting For troubleshooting information on the VSP, see the Hitachi Virtual Storage Platform User and Reference Guide.

For troubleshooting information on the Storage Navigator software, see the Hitachi Storage Navigator User Guide.

For information on Storage Navigator error codes, see the Hitachi Storage Navigator Messages.

Calling the Hitachi Data Systems Support Center If you need to call the Hitachi Data Systems Support Center make sure you can provide as much information about the problem as possible. Include the circumstances surrounding the error or failure, the Storage Navigator configuration information saved in the floppy diskette(s) by the FD Dump Tool, the exact content of messages displayed on the Storage Navigator, and severity levels and reference codes displayed on the Status tab of the Storage Navigator main window (see the Hitachi Storage Navigator Messages).

Export Tool A–1


AExport Tool

This topic explains using the Export Tool to export into files the monitoring data collected on your storage system.

□ About the Export Tool

□ Preparing for using the Export Tool

□ Using the Export Tool

□ Export Tool command reference

□ Exported files

□ Causes of Invalid Monitoring Data

□ Troubleshooting the Export Tool

A–2 Export Tool


About the Export ToolUse the Export Tool to export the monitoring data (statistics) shown in the Monitor Performance window to text files. You can also use the Export Tool to export monitoring data on remote copy operations performed by TrueCopy, TrueCopy for Mainframe, Universal Replicator, and Hitachi Universal Replicator software for Mainframe. After exporting monitoring data to text files, you can import the monitoring data into word processor documents such as Microsoft Word. You can also import the monitoring data into spreadsheet or database software that can be used to more easily analyze the monitoring data.

Example of a text file

Following is an example of a text file imported into spreadsheet software:

Preparing for using the Export Tool

Installing the Export Tool• On UNIX on page A-2

• On Windows on page A-3

On UNIX

Installation does not require that you uninstall a previous installation. A new installation will overwrite the older program.

1. Log on as a superuser.

2. Mount the CD.

Export Tool A–3


3. Create a directory (for example: /monitor).

# mkdir /monitor

4. Change the directory to the created directory.

#cd /monitor

5. Copy the CD-ROM to the created directory.

For HP-UX system: # cp/ <CD-ROM MountPoint>/program/monitor/HP_UX/export.tar

For Solaris: # cp/ <CD-ROM MountPoint>/program/monitor/solaris/export.tar

For Linux: # cp/ <CD-ROM MountPoint>/program/monitor/HP_UX/export.tar

6. Execute the program file.

# tar xvf export.tar

On Windows

If the Export Tool has previously been installed, you must first install it by removing all of the files and directories in the \monitor directory created in step 3 below.

1. Log on with administrator privileges.

2. Insert the CD-ROM.

3. At the C: prompt, create a directory (for example: \monitor).

#mk dir C:\monitor

4. Change the directory to the created directory.

# cd C:\monitor

5. Copy the CD-ROM to the created directory.

#copy <CD-ROM directory letter>:\program]monitor\win_nt\export.exe

6. Execute the program file.

# export

Export Tool limitationsThe Export Tool functions are as follows:

• Do not run multiple instances of the Export Tool simultaneously. If you run multiple instances, SVP may become overloaded and a timeout error may occur.

• The monitoring data about remote copy operations performed by TrueCopy, TrueCopy for Mainframe, Universal Replicator, and Hitachi Universal Replicator software for Mainframe cannot be exported.

Requirements for using the Export ToolThe following components are required to use the Export Tool (for more information, see the Hitachi Storage Navigator User Guide:

A–4 Export Tool


• A Windows computer or a UNIX computer

The Export Tool runs on Windows computers and UNIX computers that can run Storage Navigator software. If your Windows or UNIX computer is unable to run Storage Navigator, your computer is unable to run the Export Tool.

• The Java Runtime Environment (JRE)

To be able to use the Export Tool, you must install Java Runtime Environment on your Windows or UNIX computer. If your computer runs Storage Navigator, JRE is already installed on your computer and you can install the Export Tool. If your computer does not run Storage Navigator but contains an appropriate version of JRE, you can install the Export Tool on your computer.

The JRE version required for running the Export Tool is the same as the JRE version required for running Storage Navigator.

A user ID exclusively for use with the Export Tool

If you want to use the Export Tool, you must create a user ID that will be used exclusively with the Export Tool. When you create the user ID, note the following:

• Permissions of VSP programs

If you use the Export Tool only to save the monitoring data into files, do not assign any permission to the user ID for use with the Export Tool. If a user ID having permission is used with the Export Tool, the storage system configuration might be changed in an unfavorable way by an unidentified user.

If you use the Export Tool not only to save monitoring data but also to start or stop monitoring and to change the gathering interval by the set subcommand, the user ID needs to have at least one of permissions for Performance Monitor, TrueCopy, TrueCopy for Mainframe, Universal Replicator, and Hitachi Universal Replicator software for Mainframe.

• User types

You can specify any user type for the user ID for use with the Export Tool.

If you specify storage administrator for the user ID, all the monitoring data described from Table A-5 Files with statistics about resource usage and write pending rates on page A-49 to Table A-8 Files with statistics about volumes in parity groups, external volume groups, or V-VOL groups (at volumes controlled by a particular CU) on page A-56can be saved into files.

• The Export Tool program

The Export Tool is contained in CD-ROM Disc 2, which is named Host PP. For detailed information about how to install the Export Tool, see:

• Installing the Export Tool on a Windows computer on page A-5

• Installing the Export Tool on a UNIX computer on page A-5

Export Tool A–5


Installing the Export Tool on a Windows computerTo install the Export Tool on a Windows computer:

1. Create a folder on your Windows computer. In later steps, you will install the Export Tool on the new folder.

2. Insert the Export Tool installation media into the CD-ROM drive.

3. Locate the self-extracting file export.exe in the folder \program\monitor\win_nt in your CD-ROM disc, and then copy export.exe to the new folder that you created earlier.

4. Double-click export.exe on your computer. The Export Tool is installed. Also, a new folder named export is created.

Installing the Export Tool on a UNIX computerTo install the Export Tool on a UNIX computer:

1. Create a directory on your UNIX computer. In later steps, you will install the Export Tool on the new directory.

2. Mount the Export Tool installation media.

3. Do one of the following:

• If you are using Solaris, locate the archive file export.tar in the directory /program/monitor/solaris in your CD-ROM disc, and then copy export.tar to the new directory that you created earlier.

• If you are using HP-UX, locate the archive file export.tar in the directory /program/monitor/HP-UX in your CD-ROM disc, and then copy export.tar to the new directory that you created earlier.

4. Decompress export.tar on your computer. The Export Tool is installed. Also, a new directory named export is created.

Using the Export ToolTo be able to export monitoring data, you must prepare a command file and a batch file. This topic explains how to prepare a command file and a batch file, and then explains how to run the Export Tool.

Note: Following are notes of the export tool install:

• The export folder contains several files, including runUnix.bat. It is recommended that you delete runUnix.bat because this file is no longer needed.

• The Export Tool program is a Java class file and is located in the export\lib directory.

Note: Following are notes of the export tool install:

• The export directory contains several files including runWin.bat. We recommend that you delete runWin.bat because this file is no longer needed.

• The Export Tool program is a Java class file and is located in the export/lib directory.

A–6 Export Tool


Preparing a command fileTo run the Export Tool, you must write scripts for exporting monitoring data. When writing scripts, you need to write several subcommands in a command file. When you run the Export Tool, the subcommands in the command file execute sequentially and then the monitoring data is saved in files.

Example of a command file

svpip 158.214.135.57 ; Specifies IP address of SVPlogin expusr passwd ; Logs user into SVPshow ; Outputs storing period to standard ; outputgroup PhyPG Long ; Specifies type of data to be ; exported and type of ; storing periodgroup RemoteCopy ; Specifies type of data to be ; exportedshort-range 200610010850:200610010910 ; Specifies term of data to be ; exported for data stored ; in short rangelong-range 200609301430:200610011430 ; Specifies term of data to be ; exported for data stored ; in long rangeoutpath out ; Specifies directory in which files ; will be savedoption compress ; Specifies whether to compress filesapply ; Executes processing for saving ; monitoring data in files

In the above scripts, the semicolon (;) indicates the beginning of a comment. Characters from a semicolon to the end of the line are regarded as a comment.

The scripts in this command file are explained as follows:

• svpip 158.214.135.57

This script specifies that you are logging into SVP whose IP address is 158.214.135.57. You must log into SVP when using the Export Tool.

The svpip subcommand specifies the IP address of SVP. You must include the svpip subcommand in your command file. For detailed information about the svpip subcommand, see svpip on page A-16.

• login expusr passwd

This script specifies that you use the user ID expusr and the password passwd to log into SVP.

The login subcommand logs the specified user into SVP. You must include the login subcommand in your command file. For detailed information about the login subcommand, see login on page A-18.

Caution: When you write the login subcommand in your command file, you must specify a user ID that should be used exclusively for running the Export Tool. See Requirements for using the Export Tool on page A-3 for reference.

Export Tool A–7


• show

The show subcommand checks SVP to find the period of monitoring data stored in SVP and the data collection interval (called gathering interval in Performance Monitor), and then outputs them to the standard output (for example, the command prompt) and the log file.

Performance Monitor collects statistics by the two types of storing periods: in short range and in long range. The show subcommand displays the storing periods and the gathering intervals for these two types of monitoring data.

The following is an example of information that the show subcommand outputs:

Short Range From: 2006/10/01 01:00 - To: 2006/10/01 15:00 Interval: 1min.Long Range From: 2006/09/01 00:00 - To: 2006/10/01 15:00 Interval: 15min.

Short Range indicates the storing period and gathering interval of the monitoring data stored in short range. Long Range indicates those of the monitoring data stored in long range. In the above example, the monitoring data in short range is stored every 1 minute in the term of 1:00-15:00 on Oct. 1, 2006. Also, the monitoring data in long range is stored every 15 minutes in the term of Sep. 1, 2006, 0:00 through Oct. 1, 2006, 15:00. When you run the Export Tool, you can export monitoring data within these periods into files.

All the monitoring items are stored in short range, but a part of monitoring items is stored in both the short range and long range. For details on monitoring items that can be stored in long range, see long-range on page A-39.

The use of the show subcommand is not mandatory, but it is recommended that you include the show subcommand in your command file. If an error occurs when you run the Export Tool, you might be able to find the error cause by checking the log file for information issued by the show subcommand. For detailed information about the show subcommand, see show on page A-18.

• group PhyPG Long and group RemoteCopy

The group subcommand specifies the type of data that you want to export. Specify a operand following group to define the type of data to be exported. Basically, monitoring data stored in short range is exported. But you can direct to export monitoring data stored in long range when you specify some of the operands.

The example script group PhyPG Long in Preparing a command file on page A-6 specifies to export usage statistics about parity groups in long range. Also, the script group RemoteCopy specifies to export statistics about remote copy operations by TrueCopy and TrueCopy for Mainframe in short range. You can describe multiple lines of the group subcommand to export multiple monitoring items at the same time.

For detailed information about the group subcommand, see group on page A-20.

• short-range 200610010850:200610010910 and long-range 200609301430:200610011430

A–8 Export Tool


The short-range and long-range subcommands specify the term of monitoring data to be exported. Use these subcommands when you want to narrow the export-target term within the stored data. You can specify both the short-range and long-range subcommands at the same time. The difference between these subcommands is as follows:

• The short-range subcommand is valid for monitoring data in short range. You can use this subcommand to narrow the export-target term for all the monitoring items you can specify by the group subcommand.

Specify a term within "Short Range From XXX To XXX" which is output by the show subcommand.

• The long-range subcommand is valid for monitoring data in long range. You can use this subcommand only when you specify the PhyPG, PhyLDEV, PhyProc, or PhyESW operand with the Long option in the group subcommand. (The items that can be saved by these operands are the monitoring data displayed in the Physical tab of the Performance Management window with selecting longrange.)

Specify a term within "Long Range From XXX To XXX" which is output by the show subcommand.

In the example file of Preparing a command file on page A-6, the script short-range 200610010850:200610010910 specifies the term 8:50-9:10 on Oct. 1, 2006. This script is applied to the group RemoteCopy subcommand in this example. When you run the Export Tool, it will export the statistics about remote copy operations by TrueCopy and TrueCopy for Mainframe in the term specified by the short-range subcommand.

Also, in Preparing a command file on page A-6, the script long-range 200609301430:200610011430 specifies the term from Sep. 30, 2006, 14:30 to Oct. 1, 2006, 14:30. This script is applied to the group PhyPG Long subcommand in this example. When you run the Export Tool, it will export the usage statistics about parity groups in the term specified by the long-range subcommand.

If you run the Export Tool without specifying the short-range or long-range subcommand, the monitoring data in the whole storing period (data in the period displayed by the show subcommand) will be exported.

• For detailed information about the short-range subcommand, see short-range on page A-36.

• For detailed information about the long-range subcommand, see long-range on page A-39.

• outpath out

This script specifies that files should be saved in the directory named out in the current directory.

The outpath subcommand specifies the directory in which files should be saved. For detailed information about the outpath subcommand, see outpath on page A-42.

• option compress

Export Tool A–9


This script specifies that the Export Tool should compress monitoring data in ZIP files.

The option subcommand specifies whether to save files in ZIP format or in CSV format. For detailed information about the option subcommand, see option on page A-42.

• apply

The apply subcommand saves monitoring data in files. For detailed information about the apply command, see apply on page A-43.

When you install the Export Tool, the command.txt file will be stored in the export directory. This file contains sample scripts for your command file. It is recommended that you customize scripts in command.txt according to your needs. For detailed information about subcommand syntax, see Export Tool command reference on page A-14.

Preparing a batch fileUse a batch file to run the Export Tool. The Export Tool starts and saves monitoring data in files when you execute the batch file.

The installation directory for the Export Tool (that is, the export directory) contains two default batch files: runWin.bat and runUnix.bat. If your computer runs Windows, use runWin.bat. If your computer runs UNIX, use runUnix.bat.

The following examples illustrate scripts in runWin.bat and runUnix.batbatch files. These batch files include a command line that executes a Java command. When you execute the batch file, the Java command executes the subcommands specified in the command file and then saves monitoring data in files.

Example batch file for Windows computers: (runWin.bat):

Java -classpath "./lib/JSanExport.jar;./lib/JSanRmiServerSx.jar" -Xmx536870912 -Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain<LF>pause<LF>

Example batch file for UNIX computers: (runUnix.bat):

#! /bin/sh<LF>Java -classpath "./lib/JSanExport.jar:./lib/JSanRmiServerSx.jar" -Xmx536870912 -Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain<LF>

In the above scripts, <LF> indicates the end of a command line.

If the computer running the Export Tool communicates directly with SVP, you usually do not need to change scripts in runWin.bat and runUnix.bat. However, you might need to edit the Java command script in a text editor in some occasions, for example:

• if the name of your command file is not command.txt

• if you moved your command file to a different directory

• if you do not want to save log files in the log directory

A–10 Export Tool


• if you want to name log files as you like

If the computer that runs the Export Tool communicates with SVP via a proxy host, edit the Java command script in a text editor. to specify the host name (or the IP address) and the port number of the proxy host. For example, if the host name is Jupiter and the port number is 8080, the resulting command script would be as shown in the following examples:

Example of specifying a proxy host on Windows: (runWin.bat)

Java -classpath "./lib/JSanExport.jar;./lib/JSanRmiServerSx.jar" -Dhttp.proxyHost=Jupiter -Dhttp.proxyPort=8080 -Xmx536870912 -Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain <LF>pause <LF>

Example of specifying a proxy host on UNIX: (runUnix.bat):

#! /bin/sh <LF>Java -classpath "./lib/JSanExport.jar:./lib/JSanRmiServerSx.jar" -Dhttp.proxyHost=Jupiter -Dhttp.proxyPort=8080 -Xmx536870912 -Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain <LF>


If the IP address of the proxy host is 158.211.122.124 and the port number is 8080, the resulting command script is as follows:

Example batch file for Windows computers (runWin.bat):

Java -classpath "./lib/JSanExport.jar;./lib/JSanRmiServerSx.jar" -Dhttp.proxyHost=158.211.122.124

-Dhttp.proxyPort=8080 -Xmx536870912 -Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain <LF>pause <LF>

Example batch file for UNIX computers: (runUnix.bat)

#! /bin/sh <LF>Java -classpath "./lib/JSanExport.jar:./lib/JSanRmiServerSx.jar" -Dhttp.proxyHost=158.211.122.124 -Dhttp.proxyPort=8080 -Xmx536870912 -Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain <LF>


For detailed information about syntax of the Java command, see Java on page A-46.

Using the Export Tool

Running the batch file

To run the Export Tool and save monitoring data in files, you need to execute your batch file by entering. To execute your batch file, you need to enter the name of the batch file at the command prompt and then pressing the <Enter> key. On If you are using a Windows computer, you can double-click the batch file to execute the batch file.

Export Tool A–11


c:\WINDOWS> cd c:\export c:\export> runWin.bat

When the Export Tool starts exporting monitoring data, dots (...) are issued to the standard output (for example, the command prompt). The dots increment as export processing continues. If an internal error occurs, the exclamation mark (!) is issued to the standard output and the Export Tool attempts to restart exporting data. If the export processing restarts, dots reappear and increment until export processing finishes.

Example of command prompt outputs from the Export Tool

[ 2] svpip 158.214.135.57 [ 3] login User = expusr, Passwd = [****************] : :[ 6] group Port : :[20] apply Start gathering port data Target = 16, Total = 16+----+----+----+----+----+----+----+----+----+----+...........................! ................................. End gathering port data

When the Export Tool finishes successfully, the monitoring data files are usually compressed in ZIP-format archive files. Access If you want to obtain the CSV text files, by you need to decompress ZIP files and extracting them CSV files out of the ZIP files. If the operating system on your computer does not include a feature for decompressing ZIP files, you need to obtain software for decompressing files.

For a complete list of files to be saved by the Export Tool, see Using the Export Tool on page A-5.

File formats

If you specify the nocompress operand for the option subcommand, the Export Tool saves files in CSV format instead of ZIP format (For detailed information, see option Subcommand option on page A-42). When files are saved in CSV format instead of ZIP format, the file saving process could take longer and the resulting files could be larger.

Processing time

Files saved by the Export Tool are often very large. The total file size for all the files can be as large as approximately 2 GB. For this reason, the exporting process might take a lot of time. If you want to export statistics spanning a long period of time, it is recommended that you run the Export Tool multiple times for different periods, rather than run only once to export the entire time span as a single large file. For example, if you want to export statistics spanning 24 hours, run the tool eight times to export statistics in three3- hour increments.

A–12 Export Tool


The following provides estimates of the time required for exporting monitoring data files using different operands in the group subcommand:

Table A-1 Estimate of time required for exporting files

Termination code

If you want to use a reference to a termination code in your batch file, do the following:

• To use such a reference in a Windows batch file, write %errorlevel% in the batch file.

• To use such a reference in a UNIX Bourne shell script, write %? in the shell script.

• To use such a reference in a UNIX C shell script, write %status in the shell script.

A reference to a termination code is used in the following example of a Windows batch file. If this batch file executes and the Export Tool returns the termination code 1 or 3, the command prompt displays a message that indicates the set subcommand fails.

Operand for the group

subcommand

Estimated time Remarks

Port 5 minutes This estimate assumes that the Export Tool should save statistics about 128 ports within a 24-hour period.

PortWWN 5 minutes This estimate assumes that the Export Tool should save statistics about 128 ports within a 24-hour period.

LDEV 60 minutes This estimate assumes that:• The Export Tool should save statistics about

8,192 volumes within a 24-hour period.• The Export Tool is used eight times. Each time the

Export Tool is used, the tool obtains statistics within a 3-hour period.

LU 60 minutes This estimate assumes that:• The Export Tool should save statistics about

12,288 LUs within a 24-hour period.• The Export Tool is used eight times. Each time the

Export Tool is used, the tool obtains statistics within a 3-hour period.

Note:

• The estimated time that includes the transfer time of the network might take a lot of time depending on the transmission speed of the network.

• To be shorten the acquisition time, specify the option of the group command to narrow acquisition objects. For details about the group command, see group on page A-20.

Export Tool A–13


Java -classpath "./lib/JSanExport.jar;./lib/JSanRmiServerSx.jar" -Xmx536870912 -Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain 8if %errorlevel%==1 echo THE SET SUBCOMMAND FAILED 8if %errorlevel%==3 echo THE SET SUBCOMMAND FAILED 8pause 8

The "8" symbol indicates the end of a command line.

Log files

Whenever the Export Tool runs, the Export Tool creates a new log file on your computer. Therefore, if you run the Export Tool repeatedly, the size of free space on your computer will be reduced. To secure free space on your computer, you are strongly recommended to delete log files regularly. For information about the directory containing log files, see Java on page A-46.

The Export Tool returns a termination code when the Export Tool finishes.

Table A-2 Termination codes returned by the export tool

Error handling

When an internal error occurs during export processing, the exclamation mark (!) appears to signal the error. If this happens, the Export Tool will make up to three more attempts at processing. You can change the maximum number of retries by using the retry subcommand (see retry on page A-17)

You can change the maximum number of retries by using the retry subcommand. For detailed information about the retry subcommand, see retry on page A-17.

If export processing does not finish through three retries or if an internal error occurs other than those listed in the following table, the Export Tool does not retry the processing. In this case, you need to quit the command prompt and then run the Export Tool again.

Termination code Meaning

0 The Export Tool finished successfully.

1 An error occurred when the set subcommand (see set on page A-44) executed, because an attempt to switch to Modify mode failed. Some other user might have been logged on in Modify mode.

2 Either one of the following two errors occurred;• A command file has been corrupted or could not be read.• An error occurred when a command was parsed.

3 An error occurred due to more than one reason. One of the reasons is that an attempt to switch to Modify mode failed when the set subcommand (see set on page A-44) executed. Some other user might have been logged on in Modify mode.

4 The user ID has none of the permissions for Performance Monitor, TrueCopy, TrueCopy for Mainframe, Universal Replicator, and Hitachi Universal Replicator software for Mainframe.

A–14 Export Tool


For more information about how to solve errors with the Export Tool, see Troubleshooting the Export Tool on page A-69

Errors for which export tool retries processing

Export Tool command referenceThis topic provides the syntax of the Export Tool subcommands that you can write in your command file and the Java command that should be used in your batch file. Subcommand list on page A-16 lists the subcommands explained in this topic. The Java command is explained in Java on page A-46

Export Tool command syntaxThis topic explains the syntax of Export tool subcommands that you can write in your command file. This topic also explains the syntax of the Java command that should be used in your batch file.

Conventions

The following conventions are used to explain syntax:

Error message ID Cause of error

0001 4001 An error occurred during SVP processing.

0001 5400 Because SVP is busy, the monitoring data cannot be obtained.

0001 5508 An administrator is changing a system environment file.

0002 2016 Array is refreshing, or the settings by the user are registered.

0002 5510 The storage system is in internal process, or some other user is changing configuration.

0002 6502 Now processing.

0002 9000 Another user has lock.

0003 2016 A service engineer is accessing the storage system in Modify mode.

0003 2033 SVP is not ready yet, or an internal processing is being executed.

0003 3006 An error occurred during SVP processing.

0405 8003 The storage system status is invalid.

5205 2003 An internal process is being executed, or maintenance is in progress.

5205 2033 SVP is now updating the statistics data.

5305 2033 SVP is now updating the statistics data.

5305 8002 The storage system status is invalid.


bold Indicates characters that you must type exactly as they are shown.

italics Indicates a type of an operand. You do not need to type characters in italics exactly as they are shown.

Export Tool A–15


Syntax descriptions

Writing a script in the command file

Notes on writing script in the command file

When you write a script in your command file, be aware of the following:

• Ensure that only one subcommand is used in one line.

• Empty lines in any command file will be ignored.

• Use a semicolon (;) if you want to insert a comment in your command file. If you enter a semicolon in one line, the remaining characters in that line will be regarded as a comment.

Following are examples of comments in a command file:

;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; COMMAND FILE: command.txt ;;;;;;;;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;svpip 158.214.135.57 ; IP address of SVPlogin expusr "passwd" ; Log onto SVP

[ ] Indicates one or more operands that can be omitted.If two or more operands are enclosed by these square brackets and are delimited by vertical bars (|), you can select one of the operands.

{ } Indicates that you must select one operand from the operands enclosed by the braces. Two or more operands are enclosed by the braces and are delimited by vertical bars (|).

... Indicates that a previously used operand can be repeated.

| Vertical bar delimiter, indicating you can select one of the operands enclosed in square brackets.

This syntax... Indicates you can write this script...

connect ip-address connect 123.01.22.33

destination [directory] destinationdestination c:\temp

compress [yes|no] compresscompress yescompress no

answer {yes|no} answer yesanswer no

ports [name][...] portsports port-1ports port-1 port-2


A–16 Export Tool


Viewing the online Help for subcommands

You can display the online Help to view the syntax of subcommands when you are working at the command prompt. To be able to view the online Help, you must use the help subcommand of the Export Tool (. For detailed information about how to use the help subcommand, see help on page A-45).

Subcommand list

svpip

Description

This subcommand specifies the IP address or the host name of SVP.

Syntax

svpip {ip-address|host-name}

Subcommand Function

svpip on page A-16

Specifies the IP address of SVP to be logged in.

retry on page A-17

Makes settings on retries of export processing.

login on page A-18

Logs the specified user into SVP.

show on page A-18

Checks SVP to find the period of monitoring data stored in SVP and the data collection interval (that is called "gathering interval"), and then outputs them to the standard output and the log file.

group on page A-20

Specifies the type of data that you want to export.

short-range on page A-36

Specifies the term of monitoring data to be exported for short-range monitoring data.

llong-range on page A-39

Specifies the term of monitoring data to be exported for long-range monitoring data.

outpath on page A-42

Specifies the directory in which files should be saved.

option on page A-42

Specifies whether to save files in ZIP format or in CSV format.

apply on page A-43

Saves monitoring data in files.

set on page A-44 Starts or ends monitoring of the storage system, and specifies the gathering interval in short-range monitoring.

help on page A-45

Displays the online help for subcommands.

Java on page A-46

Starts the Export tool and writes monitoring data into files.

Export Tool A–17


Operands

Example

The following example specifies the IP address of SVP as 158.214.127.170.

svpip 158.214.127.170

retry

Description

This subcommand makes settings on retries of export processing.

When an internal error occurs during export processing, the Export Tool stops processing and then retries export processing. By default, the Export Tool can retry processing up to three times, but you can change the maximum number of retries by using the retry subcommand.

By default, the interval between one retry and the next retry is two minutes. You can change the interval by using the retry subcommand.

The retry subcommand must execute before the login subcommand executes.

Syntax

retry [time=m] [count=n]

Operands

Operand Description

ip-address Specifies the IP address of SVP. If SVP is managed with IPv6 (Internet Protocol Version 6), you must specify the ip-address operand to match the format of IPv6. If the Export Tool runs on Windows XP, the interface identifier (for example, "%5") must be added to the end of the specified IP address.

host-name Specifies the host name of SVP. If the host name includes any character that is neither an alphanumeric nor a period, the host name must be enclosed by double quotation marks (").

Operand Description

time=m Specifies the interval between retries in minutes, where m is a value within the range of 1 to 59.If this operand is omitted, the interval between retries is two minutes.

count=n Specifies the maximum number of retries.If n is 0, the number of retries is unlimited.If this operand is omitted, the maximum number of retries is 3.

A–18 Export Tool


Example

If the following command file is used, the interval between retries is 5 minutes and the maximum number of retries is 10.

svpip 158.214.135.57 retry time=5 count=10login expusr passwd show group Portshort-range 200604010850:200604010910outpath outoption compressapply

login

Description

This e subcommand uses a user ID and a password to log the specified user in SVP.

The svpip subcommand must execute before the login subcommand executes.

The login subcommand fails if monitoring data does not exist in SVP.

Syntax

login userid password

Operands

Example

This example logs the user expusr into SVP whose IP address is 158.214.127.170. The password is pswd.

svpip 158.214.127.170 login expuser pswd

show

Description

This subcommand outputs the following information to the standard output (for example, to the command prompt):

• the period during which monitoring data was collected onto SVP (storing period)

Operand Description

userid Specifies the user ID for SVP.If the user ID includes any non-alphanumeric character, the user ID must be enclosed by double quotation marks (").Be sure to specify a user ID that should be used exclusively with the Export Tool. For detailed information, see Requirements for using the Export Tool on page A-3.

password Specifies the password of the user.If the password includes any non-alphanumeric character, the password ID must be enclosed by double quotation marks (").

Export Tool A–19


• the interval at which the monitoring data was collected (gathering interval).

Performance Monitor collects statistics by the two types of storing periods: in short range and in long range. In short-range monitoring, the monitoring data between 8 hours and 15 days is stored in SVP, and in long-range monitoring, the monitoring data up to 3 months is stored in SVP. For details on the two storing periods, see short-range on page A-36 and long-range on page A-39.

Storing periods output by the show subcommand are the same as the information displayed in the Monitoring Term area of the Monitor Performance window.

The login command must execute before the show subcommand executes.

Syntax

show

Outputs

The show subcommand displays the storing period and the gathering interval for these two types of monitoring data: in short range and in long range. For example, the show subcommand outputs the following information:

Short Range From: 2006/10/01 01:00 - To: 2006/10/01 15:00 Interval: 1min.Long Range From: 2006/09/01 00:00 - To: 2006/10/01 15:00 Interval: 15min.

Short Range indicates the storing period and gathering interval of the monitoring data stored in short range. Long Range indicates those of the monitoring data stored in long range. When you run the Export Tool, you can export the monitoring data within these periods into files. If you use the short-range or long-range subcommand additionally, you can narrow the term of data to be exported (see short-range on page A-36 or long-range on page A-39).

From indicates the starting time for collecting monitoring data. To indicates the ending time for collecting monitoring data.

Figure A-1 The monitoring term area

A–20 Export Tool


Interval indicates the interval at which the monitoring data was collected (gathering interval). For example, Interval 15min. indicates that monitoring data was collected at 15-minute intervals.

group

Description

The group subcommand specifies the type of monitoring data that you want to export. This command uses an operand (such as PhyPG and PhyLDEV above) to specify a type of monitoring data.

Table A-3 Operands of the group subcommand and saved monitoring data on page A-21 shows the monitoring data that can be saved into files by each operand, and the saved ZIP files. For details on the monitoring data saved in these files, refer to the tables indicated in the See column. In the future enhancement, the monitoring items may be added or changed. In this case, the exported file is added or new monitoring items are added on the right in the exported file.

Export Tool A–21


Table A-3 Operands of the group subcommand and saved monitoring data

Operand GUI operation Monitoring data saved in the file Saved ZIP file See

PhyPG Select Parity Groups from Object list in Performance Objects field in Monitor Performance window.

Usage statistics about parity groups

PhyPG_dat.zip (*1)

Table A-5 Files with statistics about resource usage and write pending rates on page A-49

PhyLDEV Select Logical Device from Object list in Performance Objects field in Monitor Performance window.

Usage statistics about volumes

PhyLDEV_dat.zip (*1)

PhyExG Usage conditions about external volume groups

PhyExG_dat.zip

PhyExLDEV Usage conditions about external volumes

PhyExLDEV_dat.zip

PhyProc Select Controller from Object list in Performance Objects field in Monitor Performance window.

Usage statistics about processor blades and data recovery and reconstruction processors

PhyProc_dat.zip (*1)

PhyESW Select Access Path from Object list in Performance Objects field in Monitor Performance window.

Usage statistics about access paths, write pending rate, and cache

PhyESW_dat.zip (*1)

PG Select Parity Group from Object list in Performance Objects field in Monitor Performance window.

Statistics about parity groups, external volume groups, or V-VOL groups

PG_dat.zip Table A-6 Files with statistics about parity groups, external volume groups or V-VOL groups on page A-53

A–22 Export Tool


LDEV Select Logical Device from Object list in Performance Objects field in Monitor Performance window.

Statistics about volumes in parity groups, in external volume groups, or in V-VOL groups

LDEV_XXXXX.zip (*2)

Table A-7 Files with statistics about volumes in parity / external volume groups, or in V-VOL groups on page A-55

Port Select Port from Object list in Performance Objects field in Monitor Performance window.

Statistics about ports

Port_dat.zip Table A-9 Files with statistics about ports on page A-58

PortWWN Select WWN from Object list in Performance Objects field in Monitor Performance window.

Statistics about host bus adapters connected to ports

PortWWN_dat.zip Table A-10 Files with statistics about host bus adapters connected to ports on page A-58

LU Select LUN from Object list in Performance Objects field in Monitor Performance window.

Statistics about LUs LU_dat.zip Table A-11 Files with statistics about volumes (LUs) on page A-59

PPCGWWN Select WWN from Object list in Performance Objects field in Monitor Performance window.

All host bus adapters that are connected to ports

PPCGWWN_dat.ZIP

Table A-12 Files with statistics about all host bus adapters connected to ports on page A-60


Export Tool A–23


RemoteCopy

Usage Monitor tab in the TrueCopy and TrueCopy for Mainframe window

Statistics about remote copy operations by TrueCopy and TrueCopy for Mainframe (in complete volumes)

RemoteCopy_dat.zip

Table A-14 Files with statistics about remote copy operations by TC and TCz (In the whole volumes) on page A-61

RCLU Usage Monitor tab in the TrueCopy and TrueCopy for Mainframe window

Statistics about remote copy operations by TrueCopy and TrueCopy for Mainframe (for each volume (LU))

RCLU_dat.zip Table A-15 Files with statistics about remote copy operations by TC and TCz (for each volume (LU)) on page A-62

RCLDEV Usage Monitor tab in the TrueCopy and TrueCopy for Mainframe window

Statistics about remote copy operations by TrueCopy and TrueCopy for Mainframe (for volumes controlled by a particular CU)

RCLDEV_XXXXX.zip (*3)

Table A-16 Files with statistics about remote copy operations by TC and TCz (at volumes controlled by a particular CU) on page A-63

UniversalReplicator

Usage Monitor tab in the Universal Replicator and Hitachi Universal Replicator software for Mainframe window

Statistics about remote copy operations by Universal Replicator and Hitachi Universal Replicator software for Mainframe (for entire volumes)

UniversalReplicator.zip

Table A-17 Files with statistics about remote copy operations by UR and URz (In the whole volumes) on page A-65


A–24 Export Tool


URJNL Usage Monitor tab in the Universal Replicator and Hitachi Universal Replicator software for Mainframe window

Statistics about remote copy operations by Universal Replicator and Hitachi Universal Replicator software for Mainframe (for journals)

URJNL_dat.zip Table A-18 Files with statistics about remote copy operations by UR and URz (at journals) on page A-66

URLU Usage Monitor tab in the Universal Replicator and Hitachi Universal Replicator software for Mainframe window

Statistics about remote copy operations by Universal Replicator and Hitachi Universal Replicator software for Mainframe (for each volume (LU))

URLU_dat.zip Table A-19 Files with statistics about remote copy operations by UR and URz (for each volume (LU)) on page A-67

URLDEV Usage Monitor tab in the Universal Replicator and Hitachi Universal Replicator software for Mainframe window

Statistics about remote copy operations by Universal Replicator and Hitachi Universal Replicator software for Mainframe (for volumes controlled by a particular CU)

URLDEV_XXXXX.zip (*4)

Table A-20 Files with statistics about remote copy operations by UR and URz (at Volumes controlled by a particular CU) on page A-67


Export Tool A–25


You can use the group subcommand more than one time in a command file. For example, you can write the following script:

group PortWWN CL1-A:CL1-Bgroup RemoteCopy

If an operand is used more than one time in a command file, the last operand takes effect. In the example below, the first group subcommand does not take effect, but the second group subcommand takes effect:

group PortWWN CL1-A:CL1-Bgroup PortWWN CL2-A:CL2-B

LDEVEachOfCU

Select Logical Device from Object list in Performance Objects field in Monitor Performance window.

Statistics about volumes in parity groups, in external volume groups, or in V-VOL groups (for volumes controlled by a particular CU)

LDEV_XXXXX.zip (*2)

Table A-8 Files with statistics about volumes in parity groups, external volume groups, or V-VOL groups (at volumes controlled by a particular CU) on page A-56

PhyMPPK Select MPPK from Object list in Performance Objects field in Monitor Performance window.

Usage rates of processor blades

PHY_MPPK.ZIP Table A-13 Performance information on each processor blade on page A-60

Notes:*1: When you specify the PhyPG, PhyLDEV, PhyProc, or PhyESW operand, you can select the storing period of the monitoring data to be exported from short range or long range. When you specify other operands, the monitoring data in short range is exported.*2: A ZIP file whose name begins with LDEV_.*3: A ZIP file whose name begins with RCLDEV_.*4: A ZIP file whose name begins with URLDEV_.


A–26 Export Tool


Syntax

group {PhyPG [Short|Long] [parity-group-id]:[parity-group-id]][…]| PhyLDEV [Short|Long] [parity-group-id]:[parity-group-id]][…]| PhyExG [[exg-id]:[exg-id]][…]| PhyExLDEV [exg-id]:[exg-id]][…]| PhyProc [Short|Long]| PhyESW [Short|Long]| PG [[parity-group-id|V-VOL-group-id|exg-id|Migration-Volume-group-id]: [parity-group-id|V-VOL-group-id|exg-id|Migration-Volume-group-id]][…]| LDEV [[parity-group-id|V-VOL-group-id|exg-id|Migration-Volume-group-id]: [parity-group-id|V-VOL-group-id|exg-id|Migration-Volume-group-id]][.…]|internal|virtual]| Port [[port-name]:[port-name]][...]| PortWWN [port-name]:[port-name]][...]| LU[[port-name.host-group-id]:[port-name.host-group-id]][…]| PPCGWWN[[monitor-target-name:monitor-target-name]][…]| RemoteCopy| RCLU [[port-name.host-group-id]:[port-name.host-group-id]][…]| RCLDEV[[LDKC-CU-id]:[LDKC-CU-id]][…]| UniversalReplicator | URJNL[[JNL-group-id]:[JNL-group-id]][…]| URLU [[port-name.host-group-id]:[port-name.host-group-id]][…]| URLDEVr[[LDKC-CU-id]:[LDKC-CU-id]][…]| LDEVEachOfCU[[[LDKC-CU-id]:[LDKC-CU-id]][…]|internal|virtual]| PhyMPPK }

Export Tool A–27


Operands

Operand Description

PhyPG [Short|Long] [[parity-group-id]:[parity-group-id]][…]

Use this operand to export statistics about parity group usage rates, which are displayed in the Monitor Performance window. When statistics are exported to a ZIP file, the file name will be PhyPG_dat.zip. For details on the statistics exported by this operand, see Table A-5 Files with statistics about resource usage and write pending rates on page A-49.You can use the Short or Long option to select the storing period of the monitoring data to be exported. If you specify Short, the exported file will contain statistics in a short range for up to 15 days. If you specify Long, the exported file will contain statistics in a long range for up to three months (i.e., up to 93 days). If neither Short nor Long is specified, statistics in both the short and long range are exported.When you specify variables parity-group-id, you can narrow the range of parity groups whose monitoring data are to be exported. parity-group-id is a parity group ID. The colon (:) indicates a range. For example, 1-1:1-5 indicates parity groups from 1-1 to 1-5.Ensure that the parity-group-id value on the left of the colon is smaller than the parity-group-id value on the right of the colon. For example, you can specify PhyPG 1-1:1-5, but you cannot specify PhyPG 1-5:1-1. Also, you can specify PhyPG 1-5:2-1, but you cannot specify PhyPG 2-1:1-5.If parity-group-id is not specified, the monitoring data of all the parity groups will be exported.

PhyLDEV [Short|Long][[parity-group-id]:[parity-group-id]][…]

Use this operand when you want to export statistics about volume usage rates, which are displayed in the Monitor Performance window. When statistics are exported to a ZIP file, the file name will be PhyLDEV_dat.zip. For details on the statistics exported by this operand, see Table A-5 Files with statistics about resource usage and write pending rates on page A-49.You can use the Short or Long option to select the storing period of the monitoring data to be exported. If you specify Short, the exported file will contain statistics in short range for up to 15 days. If you specify Long, the exported file will contain statistics in long range for up to three months (i.e., up to 93 days). If neither Short nor Long is specified, statistics in both the short and long range are exported.When you specify variables parity-group-id, you can narrow the range of parity groups whose monitoring data are to be exported. parity-group-id is a parity group ID. The colon (:) indicates a range. For example, 1-1:1-5 indicates parity groups from 1-1 to 1-5.Ensure that the parity-group-id value on the left of the colon is smaller than the parity-group-id value on the right of the colon. For example, you can specify PhyLDEV 1-1:1-5, but you cannot specify PhyLDEV 1-5:1-1. Also, you can specify PhyLDEV 1-5:2-1, but you cannot specify PhyLDEV 2-1:1-5.If parity-group-id is not specified, the monitoring data of all the volumes will be exported.

A–28 Export Tool


PhyExG [[exg-id]:[exg-id]][…]

Use this operand when you want to export statistics about external volume groups, which are displayed in the Monitor Performance window. When statistics are exported to a ZIP file, the file name will be PhyExG_dat.zip. For details on the statistics exported by this operand, see Table A-5 Files with statistics about resource usage and write pending rates on page A-49.When you specify variables exg-id, you can narrow the range of external volume groups whose monitoring data are to be exported. exg-id is an ID of an external volume group. The colon (:) indicates a range. For example, E1-1:E1-5 indicates external volume groups from E1-1 to E1-5.Ensure that the exg-id value on the left of the colon is smaller than the exg-id value on the right of the colon. For example, you can specify PhyExG E1-1:E1-5, but you cannot specify PhyExG E1-5:E1-1. Also, you can specify PhyExG E1-5:E2-1, but you cannot specify PhyExG E2-1:E1-5.If exg-id is not specified, the monitoring data of all the external volume groups will be exported.

PhyExLDEV[[exg-id]:[exg-id]][…]

Use this operand when you want to export statistics about volumes in external volume groups, which are displayed in the Monitor Performance window. When statistics are exported to a ZIP file, the file name will be PhyExLDEV_dat.zip. For details on the statistics exported by this operand, see Table A-5 Files with statistics about resource usage and write pending rates on page A-49.When you specify variables exg-id, you can narrow the range of external volume groups whose monitoring data are to be exported. exg-id is an ID of an external volume group. The colon (:) indicates a range. For example, E1-1:E1-5 indicates external volume groups from E1-1 to E1-5.Ensure that the exg-id value on the left of the colon is smaller than the exg-id value on the right of the colon. For example, you can specify PhyExLDEV E1-1:E1-5, but you cannot specify PhyExLDEV E1-5:E1-1. Also, you can specify PhyExLDEV E1-5:E2-1, but you cannot specify PhyExLDEV E2-1:E1-5.If exg-id is not specified, the monitoring data of all the external volumes will be exported.

PhyProc[Short|Long]

Use this operand when you want to export the following statistics, which are displayed in the Monitor Performance window:• Usage rates of processor blades• Usage rates of DRRs (data recovery and reconstruction

processors)When statistics are exported to a ZIP file, the file name will be PhyProc_dat.zip. For details on the statistics exported by this operand, see Table A-5 Files with statistics about resource usage and write pending rates on page A-49.You can use the Short or Long option to select the storing period of the monitoring data to be exported. If you specify Short, the exported file will contain statistics in short range for up to 15 days. If you specify Long, the exported file will contain statistics in long range for up to three months (i.e., up to 93 days). If neither Short nor Long is specified, statistics in both the short and long range are exported.

Operand Description

Export Tool A–29


PhyESW[Short|Long]

Use this operand when you want to export the following statistics, which are displayed in the Monitor Performance window:• Usage rates of access paths between channel adapters and cache

memories• Usage rates of access paths between disk adapters and cache

memories• Usage rates of access paths between processor blades and cache

switches• Usage rates of access paths between cache switches and cache

memories• Usage rates of cache memories• Size of the allocated cache memoriesWhen statistics are exported to a ZIP file, the file name will be PhyESW_dat.zip. For details on the statistics exported by this operand, see Table A-5 Files with statistics about resource usage and write pending rates on page A-49.You can use the Short or Long option to select the storing period of the monitoring data to be exported. If you specify Short, the exported file will contain statistics in short range for up to 15 days. If you specify Long, the exported file will contain statistics in long range for up to three months (i.e., up to 93 days). If neither Short nor Long is specified, statistics in both the short and long range are exported.

PG [[parity-group-id|V-VOL-group-id|exg-id|Migration-Volume-group-id]: [parity-group-id|V-VOL-group-id|exg-id|Migration-Volume-group-id]][…]

Use this operand when you want to export statistics about parity groups, external volume groups, V-VOL groups, or migration volume groups which are displayed in the Monitor Performance window. When statistics are exported to a ZIP file, the file name will be PG_dat.zip. For details on the statistics exported by this operand, see Table A-5 Files with statistics about resource usage and write pending rates on page A-49.When you specify variables parity-group-id, exg-id, V-VOL-group-id, or Migration-Volume-group-id, you can narrow the range of parity groups, external volume groups, V-VOL groups, or migration volume groups, whose monitoring data are to be exported. parity-group-id is a parity group ID. exg-id is an ID of an external volume group. V-VOL-group-id is V-VOL group ID. Migration-Volume-group-id is a migration volume group ID. The colon (:) indicates a range. For example, 1-1:1-5 indicates parity groups from 1-1 to 1-5. E1-1:E1-5 indicates external volume groups from E1-1 to E1-5. V1-1:V5-1 indicates V-VOL groups from V1-1 to V5-1. X1-1:X5-1 indicates V-VOL groups from X1-1 to X5-1. M1-1:M5-1 indicates migration volume groups from M1-1 to M5-1.Ensure that the parity-group-id, exg-id, V-VOL-group-id, or Migration-Volume-group-id value on the left of the colon is smaller than the parity-group-id, exg-id, V-VOL-group-id, or Migration-Volume-group-id value on the right of the colon. For example, you can specify PG 1-1:1-5, but you cannot specify PG 1-5:1-1. Also, you can specify PG 1-5:2-1, but you cannot specify PG 2-1:1-5.If neither of parity-group-id, exg-id, V-VOL-group-id, nor Migration-Volume-group-id is specified, the statistics of all the parity groups, external volume groups, V-VOL groups, and migration volume groups will be exported.

Operand Description

A–30 Export Tool


LDEV [[[parity-group-id|V-VOL-group-id|exg-id|Migration-Volume-group-id]: [parity-group-id|V-VOL-group-id|exg-id|Migration-Volume-group-id]][…] |internal|virtual]|

Use this operand when you want to export statistics about volumes, which are displayed in the Monitor Performance window. When statistics are exported to a ZIP file, multiple ZIP files whose names are beginning with LDEV_ will be output. For details on the statistics exported by this operand, see Table A-9 Files with statistics about ports on page A-58.When you specify variables parity-group-id, exg-id, V-VOL-group-id, or Migration-Volume-group-id, you can narrow the range of parity groups, external volume groups, V-VOL groups, or migration volume groups whose monitoring data are to be exported. parity-group-id is a parity group ID. exg-id is an ID of an external volume group.-olume-group-id is a migration volume group ID. The colon (:) indicates a range. For example, 1-1:1-5 indicates parity groups from 1-1 to 1-5. E1-1:E1-5 indicates external volume groups from E1-1 to E1-5. V1-1:V5-1 indicates V-VOL groups from V1-1 to V5-1. X1-1:X5-1 indicates V-VOL groups from X1-1 to X5-1. M1-1:M5-1 indicates migration volume groups from M1-1 to M5-1.Ensure that the parity-group-id-, exg-id, V-VOL-group-id, or Migration-Volume-group-id value on the left of the colon is smaller than the parity-group-id, exg-id, V-VOL-group-id, or Migration-Volume-group-id value on the right of the colon. For example, you can specify LDEV 1-1:1-5, but you cannot specify LDEV 1-5:1-1. Also, you can specify LDEV 1-5:2-1, but you cannot specify LDEV 2-1:1-5.If internal is specified, you can export statistics about volumes in the parity group. If virtual is specified, you can export statistics about volumes in the external volume group, V-VOL group, or migration volume group.If neither of parity-group-id, exg-id, nor V-VOL-group-id, nor Migration-Volume-group-id is specified, the statistics of all the parity groups, external volume groups, V-VOL groups, and migration volume groups will be exported.Either one of the following values can be specified:• parity-group-id, exg-id, V-VOL-group-id, or Migration-Volume-

group-id• internal• virtual

Port [[port-name]:[port-name]][…]

Use this operand when you want to export port statistics, which are displayed in the Monitor Performance window. When statistics are exported in a ZIP file, the file name will be Port_dat.zip. For details on the statistics exported by this operand, seeTable A-9 Files with statistics about ports on page A-58.When you specify variables port-name, you can narrow the range of ports whose monitoring data are to be exported. port-name is a port name. The colon (:) indicates a range. For example, CL3-a:CL3-c indicates ports from CL3-a to CL3-c.Ensure that the port-name value on the left of the colon is smaller than the port-name value on the right of the colon. The smallest port-name value is CL1-A and the largest port-name value is CL4-r. The following formula illustrates which value is smaller than which value:CL1-A < CL1-B < … < CL2-A < CL2-B < … < CL3-a < CL3-b < … < CL4-a < … < CL4-rFor example, you can specify Port CL1-C:CL2-A, but you cannot specify Port CL2-A:CL1-C. Also, you can specify Port CL3-a:CL3-c, but you cannot specify Port CL3-c:CL3-a.If port-name is not specified, the monitoring data of all the ports will be exported.

Operand Description

Export Tool A–31


PortWWN[[port-name]:[port-name]][…]

Use this operand when you want to export statistics about host bus adapters (WWNs) connected to ports, which are displayed in the Monitor Performance window. When statistics are exported in a ZIP file, the file name will be PortWWN_dat.zip. For details on the statistics exported by this operand, see Table A-9 Files with statistics about ports on page A-58.When you specify variables port-name, you can narrow the range of ports whose monitoring data are to be exported. port-name is a port name. The colon (:) indicates a range. For example, CL3-a:CL3-c indicates ports from CL3-a to CL3-c.Ensure that the port-name value on the left of the colon is smaller than the port-name value on the right of the colon. The smallest port-name value is CL1-A and the largest port-name value is CL4-r. The following formula illustrates which value is smaller than which value:CL1-A < CL1-B < … < CL2-A < CL2-B < … < CL3-a < CL3-b < … < CL4-a < … < CL4-rFor example, you can specify PortWWN CL1-C:CL2-A, but you cannot specify PortWWN CL2-A:CL1-C. Also, you can specify PortWWN CL3-a:CL3-c, but you cannot specify PortWWN CL3-c:CL3-a.If port-name is not specified, the monitoring data of all the host bus adapters will be exported.

LU[[port-name.host-group-id]:[port-name.host-group-id]][…]

Use this operand when you want to export statistics about LU paths, which are displayed in the Monitor Performance window. When statistics are exported in a ZIP file, the file name will be LU_dat.zip. For details on the statistics exported by this operand, see Table A-11 Files with statistics about volumes (LUs) on page A-59.When you specify variables port-name.host-group-id, you can narrow the range of LU paths whose monitoring data are to be exported. port-name is a port name. host-group-id is the ID of a host group (that is, a host storage domain). The host group (host storage domain) ID must be a hexadecimal numeral. The colon (:) indicates a range. For example, CL1-C.01:CL1-C.03 indicates the range from the host group #01 of the CL1-C port to the host group #03 of the CL1-C port.Ensure that the value on the left of the colon is smaller than the value on the right of the colon. The smallest port-name value is CL1-A and the largest port-name value is CL4-r. The following formula illustrates which port-name value is smaller than which port-name value:CL1-A < CL1-B < … < CL2-A < CL2-B < … < CL3-a < CL3-b < … < CL4-a < … < CL4-rFor example, you can specify LU CL1-C.01:CL2-A.01, but you cannot specify LU CL2-A.01:CL1-C.01. Also, you can specify LU CL1-C.01:CL1-C.03, but you cannot specify LU CL1-C.03:CL1-C.01.If port-name.host-group-id is not specified, the monitoring data of all the LU paths will be exported.

Operand Description

A–32 Export Tool


PPCGWWN[[Monitor-target-name]:[Monitor-target-name]][…]

Use this operand when you want to export statistics about all host bus adapters connected to ports, which are displayed in the Monitor Performance window. When statistics are exported in a ZIP file, the file name will be PPCGWWN_dat.zip. For details on the statistics exported by this operand, see Table A-12 Files with statistics about all host bus adapters connected to ports on page A-60.When you specify variables monitor-target-name, you can narrow the range of monitoring target groups whose monitoring data are to be exported. Monitor-target-name is the name of an monitoring target group. If the name includes any non-alphanumeric character, the name must be enclosed by double quotation marks ("). The colon (:) indicates a range. For example, Grp01:Grp03 indicates a range of SPM groups from Grp01 to Grp03.Ensure that the monitor-target-name value on the left of the colon is smaller than the monitor-target-name value on the right of the colon. Numerals are smaller than letters and lowercase letters are smaller than uppercase letters. In the following formulae, values are arranged so that smaller values are on the left and larger values are on the right:• 0 < 1 < 2 < …< 9 < a < b < …< z < A < B < … < Z• cygnus < raid < Cancer < Pisces < RAID < RAID5If monitor-target-name is not specified, the monitoring data of all the host bus adapters will be exported.

RemoteCopy Use this operand when you want to export statistics about remote copy operations which are displayed in the Usage Monitor tab in the TC and TrueCopy for Mainframe window. By using this operand, you can export monitoring data about remote copy operations performed by TrueCopy and TrueCopy for Mainframe in the whole volumes. When statistics are exported to a ZIP file, the file name will be RemoteCopy_dat.zip. For details on the statistics exported by this operand, see Table A-14 Files with statistics about remote copy operations by TC and TCz (In the whole volumes) on page A-61.

Operand Description

Export Tool A–33


RCLU[[port-name.host-group-id]:[port-name.host-group-id]][…]

Use this operand when you want to export statistics about remote copy operations displayed in the Usage Monitor tab in the TC and TrueCopy for Mainframe window. By using this operand, you can export monitoring data about remote copy operations performed by TrueCopy and TrueCopy for Mainframe at each volume (LU). When statistics are exported to a ZIP file, the file name will be RCLU_dat.zip. For details on the statistics exported by this operand, see Table A-15 Files with statistics about remote copy operations by TC and TCz (for each volume (LU)) on page A-62.When you specify variables port-name.host-group-id, you can narrow the range of LU paths whose monitoring data are to be exported, where port-name is a port name andhost-group-id is the ID of a host group. The host group ID must be a hexadecimal numeral. The colon (:) indicates a range. For example, CL1-C.01:CL1-C.03 indicates the range from the host group #01 of the CL1-C port to the host group #03 of the CL1-C port.Ensure that the value on the left of the colon is smaller than the value on the right of the colon. The smallest port-name value is CL1-A and the largest port-name value is CL4-r. The following formula illustrates which port-name value is smaller than which port-name value:CL1-A < CL1-B < … < CL2-A < CL2-B < … < CL3-a < CL3-b < … < CL4-a < … < CL4-rFor example, you can specify RCLU CL1-C.01:CL2-A.01, but you cannot specify RCLU CL2-A.01:CL1-C.01. Also, you can specify RCLU CL1-C.01:CL1-C.03, but you cannot specify RCLU CL1-C.03:CL1-C.01.If port-name.host-group-id is not specified, the monitoring data of all the volumes (LUs) will be exported.

RCLDEV[[LDKC-CU-id]:[LDKC-CU-id]][…]|

Use this operand when you want to export statistics about remote copy operations which are displayed in the Usage Monitor tab in the TC and TrueCopy for Mainframe window. By using this operand, you can export monitoring data about remote copy operations performed by TrueCopy and TrueCopy for Mainframe at volumes controlled by each CU. When statistics are exported to a ZIP file, multiple ZIP files whose names are beginning with RCLDEV_ will be output. For details on the statistics exported by this operand, see Table A-16 Files with statistics about remote copy operations by TC and TCz (at volumes controlled by a particular CU) on page A-63.When you specify variables LDKC-CU-id, you can narrow the range of LDKC:CUs that control the volumes whose monitoring data are to be exported. LDKC-CU-id is an ID of a LDKC:CU. The colon (:) indicates a range. For example, 000:105 indicates LDKC:CUs from 00:00 to 01:05.Ensure that the LDKC-CU-id value on the left of the colon is smaller than the LDKC-CU-id value on the right of the colon. For example, you can specify RCLDEV 000:105, but you cannot specify RCLDEV 105:000.If LDKC-CU-id is not specified, the monitoring data of all the volumes will be exported.

Operand Description

A–34 Export Tool


UniversalReplicator

Use this operand when you want to export statistics about remote copy operations which are displayed in the Usage Monitor tab in the UR and URz window. By using this operand, you can export monitoring data about remote copy operations performed by Universal Replicator and Hitachi Universal Replicator software for Mainframe in the whole volume. When statistics are exported to a ZIP file, the file name will be UniversalReplicator.zip. For details on the statistics exported by this operand, see Table A-17 Files with statistics about remote copy operations by UR and URz (In the whole volumes) on page A-65.

URJNL[[JNL-group-id]:[JNL-group-id]][…]

Use this operand when you want to export statistics about remote copy operations which are displayed in the Usage Monitor tab in the UR and URz window. By using this operand, you can export monitoring data about remote copy operations performed by Universal Replicator and Hitachi Universal Replicator software for Mainframe at each journal. When statistics are exported to a ZIP file, the file name will be URJNL_dat.zip. For details on the statistics exported by this operand, see Table A-18 Files with statistics about remote copy operations by UR and URz (at journals) on page A-66.When you specify variables JNL-group-id, you can narrow the range of journals whose monitoring data are to be exported. JNL-group-id is a journal number. The colon (:) indicates a range. For example, 00:05 indicates journals from 00 to 05.Ensure that the JNL-group-id value on the left of the colon is smaller than the JNL-group-id value on the right of the colon. For example, you can specify URJNL 00:05, but you cannot specify URJNL 05:00.If JNL-group-id is not specified, the monitoring data of all the journal volumes will be exported.

URLU[[port-name.host-group-id]:[port-name.host-group-id]][…]

Use this operand when you want to export statistics about remote copy operations which are displayed in the Usage Monitor tab in the UR and URz window. By using this operand, you can export monitoring data about remote copy operations performed by Universal Replicator and Hitachi Universal Replicator software for Mainframe at each volume(LU). When statistics are exported to a ZIP file, the file name will be URLU_dat.zip. For details on the statistics exported by this operand, see Table A-19 Files with statistics about remote copy operations by UR and URz (for each volume (LU)) on page A-67.When you specify variables port-name.host-group-id, you can narrow the range of LU paths whose monitoring data are to be exported, where port-name is a port name and host-group-id is the ID of a host group. The host group ID must be a hexadecimal numeral. The colon (:) indicates a range. For example, CL1-C.01:CL1-C.03 indicates the range from the host group #01 of the CL1-C port to the host group #03 of the CL1-C port.Ensure that the value on the left of the colon is smaller than the value on the right of the colon. The smallest port-name value is CL1-A and the largest port-name value is CL4-r. The following formula illustrates which port-name value is smaller than which port-name value:CL1-A < CL1-B < … < CL2-A < CL2-B < … < CL3-a < CL3-b < … < CL4-a < … < CL4-rFor example, you can specify URLU CL1-C.01:CL2-A.01, but you cannot specify URLU CL2-A.01:CL1-C.01. Also, you can specify URLU CL1-C.01:CL1-C.03, but you cannot specify URLU CL1-C.03:CL1-C.01.If port-name.host-group-id is not specified, the monitoring data of all the volumes (LUs) will be exported.

Operand Description

Export Tool A–35


Examples

The following example exports statistics about host bus adapters:

URLDEV [[LDKC-CU-id]:[LDKC-CU-id]][…]

Use this operand when you want to export statistics about remote copy operations which are displayed in the Usage Monitor tab in the UR and URz window. By using this operand, you can export monitoring data about remote copy operations performed by Universal Replicator and Hitachi Universal Replicator software for Mainframe at volumes controlled by each CU. When statistics are exported to a ZIP file, multiple ZIP files whose names are beginning with URLDEV_ will be output. For details on the statistics exported by this operand, see Table A-20 Files with statistics about remote copy operations by UR and URz (at Volumes controlled by a particular CU) on page A-67.When you specify variables LDKC-CU-id, you can narrow the range of LDKC:CUs that control the volumes whose monitoring data are to be exported. LDKC-CU-id is an ID of a LDKC:CU. The colon (:) indicates a range. For example, 000:105 indicates LDKC:CUs from 00:00 to 01:05.Ensure that the LDKC-CU-id value on the left of the colon is smaller than the LDKC-CU-id value on the right of the colon. For example, you can specify URLDEV 000:105, but you cannot specify URLDEV 105:000.If LDKC-CU-id is not specified, the monitoring data of all the volumes will be exported.

LDEVEachOfCU[[[LDKC-CU-id]:[LDKC-CU-id]][…]| internal|virtual]

Use this operand when you want to export statistics about volumes which are displayed in the Monitoring Performance window. By using this operand, you can export monitoring data at volumes controlled by a particular CU. When statistics are exported to a ZIP file, multiple ZIP files whose names are beginning with LDEV_ will be output. For details on the statistics exported by this operand, see Table A-8 Files with statistics about volumes in parity groups, external volume groups, or V-VOL groups (at volumes controlled by a particular CU) on page A-56.When you specify variables LDKC-CU-id, you can narrow the range of LDKC:CUs that control the volumes whose monitoring data are to be exported. LDKC-CU-id is an ID of a LDKC:CU. The colon (:) indicates a range. For example, 000:105 indicates LDKC:CUs from 00:00 to 01:05.Ensure that the LDKC-CU-id value on the left of the colon is smaller than the LDKC-CU-id value on the right of the colon. For example, you can specify LDEVEachOfCU 000:105, but you cannot specify LDEVEachOfCU 105:000.If internal is specified, you can export statistics about volumes in the parity group. If virtual is specified, you can export statistics about volumes in the external volume group, V-VOL group, or migration volume group.If LDKC-CU-id, internal or virtual is not specified, the monitoring data of all the volumes will be exported. Either one of LDKC-CU-id, internal, or virtual can be specified.

PhyMPPK Use this operand when you want to export statistics about perfomance information on each processor blades. When statistics are exported to a ZIP file, the filename is PHY_MPPK.ZIP. For details on the statistics exported by this operand, see Table A-13 Performance information on each processor blade on page A-60.

Operand Description

A–36 Export Tool


group PortWWN

The following example exports statistics about three ports (CL1-A, CL1-B, and CL1-C):

group Port CL1-A:CL1-C

The following example exports statistics about six ports (CL1-A to CL1-C, and CL2-A to CL2-C)

group Port CL1-A:CL1-C CL2-A:CL2-C

The following example exports statistics about the parity group 1-3:

group PG 1-3:1-3

The following example exports statistics about the parity group 1-3 and other parity groups whose ID is larger than 1-3 (for example, 1-4 and 1-5):

group PG 1-3:

The following example exports statistics about the external volume groups E1-1 to E1-5:

group PG E1-1:E1-5

The following example exports statistics about the parity group 1-3 and other parity groups whose ID is smaller than 1-3 (for example, 1-1 and 1-2):

group LDEV:1-3

The following example exports statistics about LU paths for the host group (host storage domain) ID 01 for the port CL1-A:

group LU CL1-A.01:CL1-A.01

short-range

Description

Use this subcommand to specify a term of monitoring data to be exported into files. Use this subcommand when you want to narrow the export-target term within the stored data.

The short-range subcommand is valid for monitoring data in short range. Short-range monitoring data appears in the following windows:

• The Monitor Performance window when Short-range is selected as the storing period

• The Usage Monitor tab in the TC and TCz windows

• The Usage Monitor tab in the UR and URz windows

All the monitoring items are stored in short range. Therefore, you can use the short-range subcommand whichever operand you specify to the group subcommand. If you run the Export Tool without specifying the short-range subcommand, the data stored in the whole monitoring term will be exported.

Export Tool A–37


The login subcommand must execute before the short-range subcommand executes.

Syntax

short-range [[yyyyMMddhhmm][{+|-}hhmm]:[yyyyMMddhhmm][{+|-}hhmm]]

Operands

The value on the left of the colon (:) specifies the starting time of the period. The value on the right of the colon specifies the ending time of the period. Specify the term within "Short Range From XXX To XXX" which is output by the show subcommand.

If no value is specified on the left of the colon, the starting time for collecting monitoring data is assumed. If no value is specified on the right of the colon, the ending time for collecting monitoring data is assumed. The starting and ending times for collecting monitoring data are displayed in the Monitoring Term area in the Monitor Performance window.

Figure A-2 Starting and Ending Time for Collecting Monitoring Data

Operand Description

yyyyMMddhhmm

yyyyMMdd indicates the year, the month, and the day. hhmm indicates the hour and the minute.If yyyyMMddhhmm is omitted on the left of the colon, the starting time for collecting monitoring data is assumed. If yyyyMMddhhmm is omitted on the right of the colon, the ending time for collecting monitoring data is assumed.

+hhmm Adds time (hhmm) to yyyyMMddhhmm if yyyyMMddhhmm is specified. For example, 200601230000+0130 indicates Jan. 23, 2006. 01:30.Adds time to the starting time for collecting monitoring data, if yyyyMMddhhmm is omitted.

A–38 Export Tool


Examples

The examples below assume that:

• the starting time for collecting monitoring data is Jan. 1, 2006, 00:00,

• the ending time for collecting monitoring data is Jan. 2, 2006, 00:00.

short-range 200601010930:200601011730

The Export Tool saves monitoring data within the range of Jan. 1, 9:30-17:30.

short-range 200601010930:

The Export Tool saves monitoring data within the range of Jan. 1, 9:30 to Jan. 2, 00:00.

shortrange:200601011730


short-range +0001:


short-range -0001:


shortrange:+0001

-hhmm Subtracts time (hhmm) from yyyyMMddhhmm if yyyyMMddhhmm is specified. For example, 200601230000-0130 indicates Jan. 22, 2006. 22:30.Subtracts time from the ending time for collecting monitoring data, if yyyyMMddhhmm is omitted.If the last two digit of the time on the left or right of the colon (:) is not a multiple of the sampling interval, the time will automatically be changed so that the last two digits is a multiple of the sampling interval. If this change occurs to the time on the left of the colon, the time will be smaller than the original time. If this change occurs to the time on the right of the colon, the time will be larger than the original time. The following are the examples:• If the time on the left is 10:15, the time on the right is

20:30, and the sampling interval is 10 minutes:The time on the left will be changed to 10:10 because the last two digits of the time is not a multiple of 10 minutes. The time on the right will remain unchanged because the last two digits of the time is a multiple of 10 minutes.

• If the time on the left is 10:15, the time on the right is 20:30, and the sampling interval is 7 minutes:The time on the left will be changed to 10:14 because the last two digits of the time is not a multiple of 7 minutes. The time on the right will be changed to 20:35 because of the same reason.

Operand Description

Export Tool A–39



shortrange:-0001


short-range +0101:-0101


short-range 200601010900+0130:200601011700-0130


short-range 200601010900-0130:200601011700+0130


short-range 200601010900-0130:


long-range

Description

The long-range subcommand is used to specify a monitoring term (time range) for collecting monitoring data to be exported into files. Use this subcommand when you want to narrow the export-target term within the stored data.

The long-range subcommand is valid for monitoring data in long range. The monitoring data in long range is the contents displayed in the Physical tab of the Performance Management window with selecting long-range as the storing period.

The monitoring items whose data can be stored in long range are limited. The following table shows the monitoring items to which the long-range subcommand can be applied, and also shows the operands to export those monitoring items.

Monitoring Data Operands of the group subcommand

Usage statistics about parity groups PhyPG Long

Usage statistics about volumes PhyLDEV Long

Usage statistics about channel processors and data recovery and reconstruction processors

PhyProc Long

Usage statistics about access paths and write pending rate

PhyESW Long

A–40 Export Tool


If you run the Export Tool without specifying the long-range subcommand, the data stored in the whole monitoring term will be exported.

The login subcommand must execute before the long-range subcommand executes.

Syntax

long-range [[yyyyMMddhhmm][{+|-}ddhhmm]:[yyyyMMddhhmm][{+|-}ddhhmm]]

Operands

The value on the left of the colon (:) specifies the starting time of the period. The value on the right of the colon specifies the ending time of the period. Specify the term within "Long Range From XXX To XXX" which is output by the show subcommand.

If no value is specified on the left of the colon, the starting time for collecting monitoring data is assumed. If no value is specified on the right of the colon, the ending time for collecting monitoring data is assumed. The starting and ending times for collecting monitoring data are displayed in the Monitoring Term area in the Monitor Performance window.

Figure A-3 Starting and Ending Time for Collecting Monitoring Data

Operand Description

yyyyMMddhhmm

yyyyMMdd indicates the year, the month, and the day. hhmm indicates the hour and the minute.If yyyyMMddhhmm is omitted on the left of the colon, the starting time for collecting monitoring data is assumed. If yyyyMMddhhmm is omitted on the right of the colon, the ending time for collecting monitoring data is assumed.

+ddhhmm Adds time (ddhhmm) to yyyyMMddhhmm if yyyyMMddhhmm is specified. For example, 200601120000+010130 indicates Jan. 13, 2006. 01:30.Adds time to the starting time for collecting monitoring data, if yyyyMMddhhmm is omitted.

Export Tool A–41


Examples

The examples below assume that:

• the starting time for collecting monitoring data is Jan. 1, 2006, 00:00,

• the ending time for collecting monitoring data is Jan. 2, 2006, 00:00.

long-range 200601010930:200601011730


long-range 200601010930:


longrange:200601011730


long-range +000015:


long-range -000015:


longrange:+000015


longrange:-000015


long-range +000115:-000115


long-range 200601010900+000130:200601011700-000130

-ddhhmm Subtracts time (ddhhmm) from yyyyMMddhhmm if yyyyMMddhhmm is specified. For example, 200601120000-010130 indicates Jan. 10, 2006. 22:30.Subtracts time from the ending time for collecting monitoring data, if yyyyMMddhhmm is omitted.Ensure that mm is 00, 15, 30, or 45. If you do not specify mm in this way, the value on the left of the colon (:) will be rounded down to one of the four values. Also, the value on the right of the colon will be rounded up to one of the four values. For example, if you specify 200601010013:200601010048, the specified value is regarded as 200601010000:200601010100.

Operand Description

A–42 Export Tool



long-range 200601010900-000130:200601011700+000130


long-range 200601010900-000130:


outpath

Description

The outpath subcommand specifies the directory to which monitoring data will be exported.

Syntax

outpath [path]

Operands

Examples

The following example saves files in the directory C:\Project\out on a Windows computer:

outpath "C:\\Project\\out"

The following example saves files in the out directory in the current directory:

outpath out

option

Description

This subcommand specifies the following:

• whether to compress monitoring data in ZIP files

Operand Description

path Specifies the directory in which files will be saved.If the directory includes any non-alphanumeric character, the directory must be enclosed by double quotation marks ("). If you want to specify a back slash (\) in the character string enclosed by double quotation marks, repeat the back slash twice such as \\.If the specified directory does not exist, this subcommand creates a directory that has the specified name.If this operand is omitted, the current directory is assumed.

Export Tool A–43


• whether to overwrite or delete existing files and directories when saving monitoring data in files

Syntax

option [compress|nocompress] [ask|clear|noclear]

Operands

Example

The following example saves monitoring data in CSV files, not in ZIP files:

option nocompress

apply

Description

The apply subcommand saves monitoring data specified by the group subcommand into files.

The login subcommand must execute before the apply subcommand executes.

The apply subcommand does nothing if the group subcommand executes.

The settings made by the group subcommand will be reset when the apply subcommand finishes.

Syntax

apply

Operand Description

The two operands below specify whether to compress CSV files into ZIP files. If none of these operands is specified, compress is assumed.

compress Compresses data in ZIP files. To extract CSV files out of a ZIP file, you will need to decompress the ZIP file.

nocompress Does not compress data in ZIP files and saves data in CSV files.

The three operands below specify whether to overwrite or delete an existing file or directory when the Export Tool saves files. If none of these operands is specified, ask is assumed.

ask Displays a message that asks whether to delete existing files or directories.

clear Deletes existing files and directories and then saves monitoring data in files.

noclear Overwrites existing files and directories.

A–44 Export Tool


set

Description

The set subcommand starts or ends monitoring the storage system (i.e., starts or ends collecting performance statistics). The set subcommand also specifies the gathering interval (interval of collecting statistics) in short range monitoring.

If you want to use the set subcommand, you must use the login subcommand (see login on page A-18 to log on to SVP. Ensure that the set subcommand executes immediately before the Export Tool finishes.

Executing the set subcommand generates an error in the following conditions:

• Some other user is being logged onto SVP in Modify mode.

• Maintenance operations are being performed at SVP.

If an error occurs, do the following:

• Ensure that all the users who are logged onto SVP are not in Modify mode. If any user is logged on in Modify mode, ask the user to switch to View mode.

• Wait until maintenance operations finish at SVP, so that the set subcommand can execute.

Syntax

set [switch={m|off}]

Note: Following are notes of the set command.

• Batch files can include script that should execute when an error occurs. For information about writing such a script in your batch file, refer to Notes in Using the Export Tool on page A-10.

• When the set subcommand starts or ends the monitoring or changes the gathering interval after the Monitor Performance window is started, the contents displayed in the Monitor Performance window does not change automatically in conjunction with the set subcommand operation. To display the current monitoring status in the Monitor Performance window, click File, and then Refresh on the menu bar of the Storage Navigator main window.

• If you change the specified gathering interval during a monitoring, the previously gathered monitoring data will be deleted.

Export Tool A–45


Operands

Examples

The following command file saves port statistics and then ends monitoring ports:

svpip 158.214.135.57 login expusr passwd show group Portshort-range 200604010850:200604010910applyset switch=off

The following command file starts monitoring remote copy operations. The sampling time interval is 10 minutes:

svpip 158.214.135.57 login expusr passwd set switch=10

help

Description

The help subcommand displays the online help for subcommands.

If you want to view the online help, It is recommended that you create a batch file and a command file that are exclusively used for displaying the online help. For detailed information, refer to Example below.

Syntax

help

Example

In this example, a command file (cmdHelp.txt) and a batch file (runHelp.bat) are created in the C:\export directory on a Windows computer:

• Command file (c:\export\cmdHelp.txt):

help

• Batch file (c:\export\runHelp.bat):

Java -classpath "./lib/JSanExport.jar;./lib/JSanRmiServerSx.jar" -Xmx536870912 -Dmd.command=cmdHelp.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain 8pause <LF>

In the above script, <LF> in this batch file example indicates the end of a command line.

Operand Description

switch={m|off}

To start monitoring, specify the gathering interval (interval of collecting statistics) of monitoring data at m. Specify a value between 1 and 15 in minutes. m is the gathering interval in short range monitoring by Performance Monitor. The gathering interval in long range is fixed to 15 minutes.To end monitoring, specify off.If this operand is omitted, the set subcommand does not make settings for starting or ending monitoring.

A–46 Export Tool


In this example, you must do one of the following to view the online Help:

• Double-click runHelp.bat with the mouse.

• Go to the c:\export directory at the command prompt, enter runHelp or runHelp.bat and then press the <Enter> key.

Java

Description

This command starts the Export Tool and exports monitoring data into files. To start the Export Tool, write this Java command in your batch file and then run the batch file.

Syntax

Java -classpath class-pathrproperty-parameters sanproject.getmondat.RJMdMain

Operands

Operand Description

class-path Specifies the path to the class file of the Export Tool.The path must be enclosed in double quotation marks (").

Export Tool A–47


Examples

The following example assumes that the computer running the Export Tool communicates with SVP via a proxy host. In the following example, the host name of the proxy host is Jupiter, and the port name of the proxy host is 8080:

Java -classpath "./lib/JSanExport.jar;./lib/JSanRmiServerSx.jar" -Dhttp.proxyHost=Jupiter -Dhttp.proxyPort=8080 -Xmx536870912 -Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain <LF>

In the following example, a log file named export.log will be created in the log directory below the current directory when the Export Tool executes:

property-parameters

You can specify the following parameters. At minimum you must specify -Dmd.command. • -Dhttp.proxyHost=host-name-of-proxy-host, or -

Dhttp.proxyHost=IP-address-of-proxy-hostSpecifies the host name or the IP address of a proxy host. You must specify this parameter if the computer that runs the Export Tool communicates with SVP via a proxy host.

• -Dhttp.proxyPort=port-number-of-proxy-hostSpecifies the port number of a proxy host. You must specify this parameter if the computer that runs the Export Tool communicates with SVP via a proxy host.

• -Xmxmemory-size(bytes)Specifies the size of memory to be used by JRE when the Export Tool is being executed. You must specify this parameter. The memory size must be 536870912, as shown in the Example later in this topic. If an installed memory size is smaller than the recommended size of the PC running Storage Navigator, you must install more memory before executing the Export Tool.If an installed memory size is larger than the recommended memory size of the PC running Storage Navigator, you can specify a memory size larger than as shown in the Example. However, to prevent lowering of execution speed, you do not set oversized memory size.

• -Dmd.command=path-to-command-fileSpecifies the path to the command file

• -Dmd.logpath=path-to-log-fileSpecifies the path to log files. A log file will be created whenever the Export Tool executes.If this parameter is omitted, log files will be saved in the current directory.

• -Dmd.logfile=name-of-log-fileSpecifies the name of the log file.If this parameter is omitted, log files are named exportMMddHHmmss.log. MMddHHmmss indicates when the Export Tool executed. For example, the log file export0101091010.log contains log information about Export Tool execution at Jan. 1, 09:10:10.

Operand Description

A–48 Export Tool


Java -classpath "./lib/JSanExport.jar;./lib/JSanRmiServerSx.jar" -Xmx536870912 -Dmd.command=command.txt -Dmd.logfile=export.log -Dmd.logpath=log sanproject.getmondat.RJMdMain <LF>

In the above script, <LF> indicates the end of a command line.

Exported filesThe Export Tool saves the exported monitoring data into text files in CSV (comma-separated value) format, in which values are delimited by commas. Many spreadsheet applications can be used to open CSV files.

The Export Tool by default saves the CSV text files in compressed (ZIP) files. To use a text editor or spreadsheet software to view or edit the monitoring data, first decompress the ZIP files to extract the CSV files. You can also configure the Export Tool to save monitoring data in CSV files instead of ZIP files.

Monitoring data exported by the Export ToolThe following table shows the correspondence between the Performance Management windows and the monitoring data that can be exported by the Export Tool. For details on the data contained in the corresponding ZIP files and CSV files, refer to the tables indicated in the links in the Monitoring data column.

Table A-4 Performance management windows and monitoring data saved by the Export Tool

GUI operation Monitoring data

Select Parity Groups from Object list in Performance Objects field in Monitor Performance window.

Resource usage and write-pending rate statistics on page A-49Parity groups, external volume groups, or V-VOL groups statistics on page A-53

Select Logical Devices from Object list in Performance Objects field in Monitor Performance window.

Resource usage and write-pending rate statistics on page A-49Volumes in parity/external volume groups or V-VOL groups statistics on page A-54Volumes in parity groups, external volume groups, or V-VOL groups (at volumes controlled by a particular CU) on page A-56

Select Access Path from Object list in Performance Objects field in Monitor Performance window.

Resource usage and write-pending rate statistics on page A-49

Select Cache from Object list in Performance Objects field in Monitor Performance window.

Resource usage and write-pending rate statistics on page A-49

Select Controller from Object list in Performance Objects field in Monitor Performance window.

Resource usage and write-pending rate statistics on page A-49Processor blades on page A-60

Export Tool A–49


Resource usage and write-pending rate statisticsThe following table shows the file names and types of information in the Monitor Performance window that can be saved to files using the Export Tool. These files contain statistics about resource usage and write pending rates.

Table A-5 Files with statistics about resource usage and write pending rates

Select Port from Object list in Performance Objects field in Monitor Performance window.

Port statistics on page A-58

Select LUN from Object list in Performance Objects field in Monitor Performance window.

Volumes (LU) statistics on page A-59

Select WWN from Object list in Performance Objects field in Monitor Performance window.

Host bus adapters connected to ports statistics on page A-58All host bus adapters connected to ports on page A-60

Usage Monitor tab in the TC and TCz window

Remote copy operations by TC/TCz (whole volumes) on page A-61

Remote copy operations by TC and TCz (for each volume (LU)) on page A-61

Remote copy by TC and TCz (volumes controlled by a particular CU) on page A-62

Usage Monitor tab in the UR and URz window

Remote copy by UR and URz (whole volumes) on page A-64

Remote copy by UR and URz (at journals) on page A-65

Usage Monitor tab in the UR and URz window (continued)

Remote copy by UR and URz (for each volume (LU)) on page A-66

Remote copy by UR and URz (at volumes controlled by a particular CU) on page A-67

GUI operation Monitoring data

ZIP file CSV file Data saved in the file

PhyPG_dat.zip PHY_Long_PG.csv Usage rates for parity groups in long range

PHY_Short_PG.csv Usage rates for parity groups in short range

PhyLDEV_dat.zip

PHY_Long_LDEV_x-y.csv Usage rates for volumes in a parity group in long range

PHY_Short_LDEV_x-y.csv Usage rates for volumes in a parity group in short range

PHY_Short_LDEV_SI_x-y.csv

Usage rates for ShadowImage volumes in a parity group in short range

A–50 Export Tool


PhyExG_dat.zip

PHY_ExG_Response.csv If external storage volumes are mapped to the volume groups of VSP, this file includes the average response time for the volume groups including external storage volumes (milliseconds).

PHY_ExG_Trans.csv If external storage volumes are mapped to the volume groups of VSP, this file includes the amount of transferred data for volume groups including external storage volumes (KB/sec).

PHY_ExG_Read_Response.csv

If external storage volumes are mapped to the volume groups of VSP, this file includes the average read response time for the volume groups including external storage volumes (milliseconds).

PHY_ExG_Write_Response.csv

If external storage volumes are mapped to the volume groups of VSP, this file includes the average write response time for the volume groups including external storage volumes (milliseconds).

PHY_ExG_Read_Trans.csv If external storage volumes are mapped to the volume groups of VSP, this file includes the amount of read transferred data for volume groups including external storage volumes (KB/sec).

PHY_ExG_Write_Trans.csv If external storage volumes are mapped to the volume groups of VSP, this file includes the amount of write transferred data for volume groups including external storage volumes (KB/sec).


Export Tool A–51


PhyExLDEV_dat.zip

PHY_ExLDEV_Response_x-y.csv

If external storage volumes are mapped to the volume groups of VSP, this file includes the average response time for external storage volumes in the volume group x-y (milliseconds).

PHY_ExLDEV_Trans_x-y.csv

If external storage volumes are mapped to the volume groups of VSP, this file includes the amount of data transferred for external storage volumes in the volume group x-y (KB/sec).

PHY_ExLDEV_Read_Response_x-y.csv

If external storage volumes are mapped to the volume groups of VSP, this file includes the average reading response time for external storage volumes in the volume group x-y (milliseconds).

PHY_ExLDEV_Write_Response_x-y.csv

If external storage volumes are mapped to the volume groups of VSP, this file includes the average writing response time for external storage volumes in the volume group x-y (milliseconds).

PHY_ExLDEV_Read_Trans_x-y.csv

If external storage volumes are mapped to the volume groups of VSP, this file includes the amount of reading data transferred for external storage volumes in the volume group x-y (KB/sec).

PHY_ExLDEV_Write_Trans_x-y.csv

If external storage volumes are mapped to the volume groups of VSP, this file includes the amount of writing data transferred for external storage volumes in the volume group x-y (KB/sec).

PhyProc_dat.zip

PHY_Long_MP.csv Usage rates for processor blades in long range

PHY_Short_MP.csv Usage rates for processor blades in short range

PHY_Long_DRR.csv Usage rates for DRRs (data recovery and reconstruction processors) in long range

PHY_Short_DRR.csv Usage rates for DRRs (data recovery and reconstruction processors) in short range


A–52 Export Tool


PhyESW_dat.zip

PHY_Long_CHA_ESW.csv Usage rates for access paths between channel adapters and cache memories in long range

PHY_Long_DKA_ESW.csv Usage rates for access paths between disk adapters and cache memories in long range

PHY_Short_CHA_ESW.csv Usage rates for access paths between channel adapters and cache memories in short range

PHY_Short_DKA_ESW.csv Usage rates for access paths between disk adapters and cache memories in short range

PHY_Long_MPPCB_ESW.csv

Usage rates for access paths between processor blades and cache memories in long range

PHY_Short_MPPCB_ESW.csv

Usage rates for access paths between processor blades and cache memories in short range

PHY_Long_ESW_Cache.csv Usage rates for access paths between cache switches and cache memories in long range

PHY_Short_ESW_Cache.csv

Usage rates for access paths between cache switches and cache memories in short range

PHY_Long_Write_Pending_Rate.csv

Write pending rates in long range in the entire system

PHY_Short_Write_Pending_Rate.csv

Write pending rates in short range in the entire system

PHY_Short_Cache_Usage_Rate.csv

Usage rates for cache memory in each the entire system

PHY_Long_Write_Pending_Rate_z.csv

Write pending rates in long range in each processor blade

PHY_Short_Write_Pending_Rate_z.csv

Write pending rates in short range in each processor blade

PHY_Short_Cache_Usage_Rate_z.csv

Usage rates for cache memory in each processor blade

PHY_Cache_Allocate_z.csv The allocated size of the cache memory in each processor blade (MB)This value does not correspond with the total capacity of cache because the value is same as the allocated size of the cache memory that is managed by a processor blade.

Notes: • The letters "x-y" in CSV file names indicate a parity group or external volume

group.• The letter "z" in CSV file names indicate a name of processor blade.• Both long range and short range statistics are stored for resource usage and write

pending rates.• You can select Long-Range or Short-Range from Data Range field in the

Monitor Performance window


Export Tool A–53


Parity groups, external volume groups, or V-VOL groups statisticsThe following table shows the file names and types of information in the Monitor Performance window that can be exported to files using the Export Tool. These files contain statistics about parity groups, external volume groups, or V-VOL groups.

Table A-6 Files with statistics about parity groups, external volume groups or V-VOL groups


PG_dat.zip

PG_IOPS.csv The number of read and write operations per second

PG_TransRate.csv The size of data transferred per second (KB/sec)

PG_Read_TransRate.csv

The size of the read data transferred per second (KB/sec)

PG_Write_TransRate.csv

The size of the write data transferred per second (KB/sec)

PG_Read_IOPS.csv

The number of read operations per second

PG_Seq_Read_IOPS.csv

The number of sequential read operations per second

PG_Rnd_Read_IOPS.csv

The number of random read operations per second

PG_CFW_Read_IOPS.csv

The number of read operations in "cache-fast-write" mode per second

PG_Write_IOPS.csv

The number of write operations per second

PG_Seq_Write_IOPS.csv

The number of sequential write operations per second

PG_Rnd_Write_IOPS.csv

The number of random write operations per second

PG_CFW_Write_IOPS.csv

The number of write operations in "cache-fast-write" mode per second

PG_Read_Hit.csv The read hit ratio

PG_Seq_Read_Hit.csv

The read hit ratio in sequential access mode

A–54 Export Tool


Volumes in parity/external volume groups or V-VOL groups statistics

The following table shows the file names and types of information in the Monitor Performance window that can be exported to files using the Export Tool. These files contain statistics about volumes in parity/external volume groups or V-VOL groups.

PG_dat.zip (cont.)

PG_Rnd_Read_Hit.csv

The read hit ratio in random access mode

PG_CFW_Read_Hit.csv

The read hit ratio in "cache-fast-write" mode

PG_Write_Hit.csv The write hit ratio

PG_Seq_Write_Hit.csv

The write hit ratio in sequential access mode

PG_Rnd_Write_Hit.csv

The write hit ratio in random access mode

PG_CFW_Write_Hit.csv

The write hit ratio in "cache-fast-write" mode

PG_BackTrans.csv The number of data transfer operations between cache memories and hard disk drives (i.e., parity groups, external volume groups, or V-VOL groups) per second

PG_C2D_Trans.csv

The number of data transfer operations from cache memories and hard disk drives (i.e., parity groups, external volume groups, or V-VOL groups)

PG_D2CS_Trans.csv

The number of data transfer operations from hard disk drives (i.e., parity groups, external volume groups, or V-VOL groups) to cache memories in sequential access mode

PG_D2CR_Trans.csv

The number of data transfer operations from hard disk drives (i.e., parity groups, external volume groups, or V-VOL groups) to cache memories in random access mode

PG_Response.csv The average response time (microsecond) at parity groups, external volume groups, or V-VOL groups

PG_Read_Response.csv

The average read response time (microsecond) at parity groups, external volume groups, or V-VOL groups

PG_Write_Response.csv

The average write response time (microsecond) at parity groups, external volume groups, or V-VOL groups

Note: In the future enhancement, The format of columns of these files is planned to change.

By the change of the format, only as for a virtual volume of Dynamic Provisioning, the parity group number and LDEV number are described in parallel.


Export Tool A–55


Table A-7 Files with statistics about volumes in parity / external volume groups, or in V-VOL groups


LDEV_IOPS.zip LDEV_IOPS_x-y.csv The number of read and write operations per second

LDEV_TransRate.zip LDEV_TransRate_x-y.csv

The size of data transferred per second (KB/sec)

LDEV_Read_TransRate.ZIP

LDEV_Read_TransRate_x-y.csv

The size of read data transferred per second (KB/sec)

LDEV_Write_TransRate.ZIP

LDEV_Write_TransRate_x-y.csv

The size of write data transferred per second (KB/sec)

LDEV_Read_IOPS.zip LDEV_Read_IOPS_x-y.csv

The number of read operations per second

LDEV_Seq_Read_IOPS.zip

LDEV_Seq_Read_IOPS_x-y.csv


LDEV_Rnd_Read_IOPS.zip

LDEV_Rnd_Read_IOPS_x-y.csv


LDEV_CFW_Read_IOPS.zip

LDEV_CFW_Read_IOPS_x-y.csv


LDEV_Write_IOPS.zip

LDEV_Write_IOPS_x-y.csv

The number of write operations per second

LDEV_Seq_Write_IOPS.zip

LDEV_Seq_Write_IOPS_x-y.csv


LDEV_Rnd_Write_IOPS.zip

LDEV_Rnd_Write_IOPS_x-y.csv


LDEV_CFW_Write_IOPS.zip

LDEV_CFW_Write_IOPS_x-y.csv


LDEV_Read_Hit.zip LDEV_Read_Hit_x-y.csv The read hit ratio

LDEV_Seq_Read_Hit.zip

LDEV_Seq_Read_Hit_x-y.csv


LDEV_Rnd_Read_Hit.zip

LDEV_Rnd_Read_Hit_x-y.csv


LDEV_CFW_Read_Hit.zip

LDEV_CFW_Read_Hit_x-y.csv


LDEV_Write_Hit.zip LDEV_Write_Hit_x-y.csv

The write hit ratio

LDEV_Seq_Write_Hit.zip

LDEV_Seq_Write_Hit_x-y.csv


LDEV_Rnd_Write_Hit.zip

LDEV_Rnd_Write_Hit_x-y.csv


LDEV_CFW_Write_Hit.zip

LDEV_CFW_Write_Hit_x-y.csv


LDEV_BackTrans.zip LDEV_BackTrans_x-y.csv

The number of data transfer operations between cache memories and hard disk drives (i.e., volumes) per second

A–56 Export Tool


Volumes in parity groups, external volume groups, or V-VOL groups (at volumes controlled by a particular CU)

The following table shows the file names and types of information in the Monitor Performance window that can be exported to files using the Export Tool. These files contain statistics about volumes in parity groups, external volume groups, or V-VOL groups (at volumes controlled by a particular CU).

Table A-8 Files with statistics about volumes in parity groups, external volume groups, or V-VOL groups (at volumes controlled by a particular

CU)

LDEV_C2D_Trans.zip LDEV_C2D_Trans_x-y.csv

The number of data transfer operations from cache memories and hard disk drives (i.e., volumes)

LDEV_D2CS_Trans.zip

LDEV_D2CS_Trans_x-y.csv

The number of data transfer operations from hard disk drives (i.e., volumes) to cache memories in sequential access mode

LDEV_D2CR_Trans.zip

LDEV_D2CR_Trans_x-y.csv

The number of data transfer operations from hard disk drives (i.e., volumes) to cache memories in random access mode

LDEV_Response.zip LDEV_Response_x-y.csv

The average response time (microseconds) at volumes

LDEV_Read_Response.ZIP

LDEV_Read_Response_x-y.csv

The average read response time (microseconds) at volumes

LDEV_Write_Response.ZIP

LDEV_Write_Response_x-y.csv

The average write response time (microseconds) at volumes

Note: The letters "x-y" in CSV filenames indicate a parity group. For example, if the filename is LDEV_IOPS_1-2.csv, the file contains the I/O rate for each volume in the parity group 1-2.



LDEV_IOPS.zip LDEV_IOPS_xx.csv The number of read and write operations per second

LDEV_TransRate.zip LDEV_TransRate_xx.csv The size of data transferred per second (KB/sec)

LDEV_Read_IOPS.zip LDEV_Read_IOPS_xx.csv The number of read operations per second

LDEV_Seq_Read_IOPS.zip LDEV_Seq_Read_IOPS_xx.csv


LDEV_Rnd_Read_IOPS.zip LDEV_Rnd_Read_IOPS_xx.csv


LDEV_CFW_Read_IOPS.zip

LDEV_CFW_Read_IOPS_xx.csv


LDEV_Write_IOPS.zip LDEV_Write_IOPS_xx.csv The number of write operations per second

Export Tool A–57


LDEV_Seq_Write_IOPS.zip

LDEV_Seq_Write_IOPS_xx.csv


LDEV_Rnd_Write_IOPS.zip

LDEV_Rnd_Write_IOPS_xx.csv


LDEV_CFW_Write_IOPS.zip

LDEV_CFW_Write_IOPS_xx.csv


LDEV_Read_Hit.zip LDEV_Read_Hit_xx.csv The read hit ratio

LDEV_Seq_Read_Hit.zip LDEV_Seq_Read_Hit_xx.csv The read hit ratio in sequential access mode

LDEV_Rnd_Read_Hit.zip LDEV_Rnd_Read_Hit_xx.csv The read hit ratio in random access mode

LDEV_CFW_Read_Hit.zip LDEV_CFW_Read_Hit_xx.csv


LDEV_Write_Hit.zip LDEV_Write_Hit_xx.csv The write hit ratio

LDEV_Seq_Write_Hit.zip LDEV_Seq_Write_Hit_xx.csv


LDEV_Rnd_Write_Hit.zip LDEV_Rnd_Write_Hit_xx.csv


LDEV_CFW_Write_Hit.zip LDEV_CFW_Write_Hit_xx.csv


LDEV_BackTrans.zip LDEV_BackTrans_xx.csv The number of data transfer operations between cache memories and hard disk drives (i.e., volumes)

LDEV_C2D_Trans.zip LDEV_C2D_Trans_xx.csv The number of data transfer operations from cache memories and hard disk drives (i.e., volumes)

LDEV_D2CS_Trans.zip LDEV_D2CS_Trans_xx.csv The number of data transfer operations from hard disk drives (i.e., volumes) to cache memories in sequential access mode

LDEV_D2CR_Trans.zip LDEV_D2CR_Trans_xx.csv The number of data transfer operations from hard disk drives (i.e., volumes) to cache memories in random access mode

LDEV_Response.zip LDEV_Response_xx.csv The average response time (microseconds) at volumes

Note: 1 microsecond is one-million of 1 second. The letters "xx" in CSV filenames indicate a CU image number. For example, if the filename is LDEV_IOPS _10.csv, the file contains the I/O rate (per second) of the volumes controlled by the CU whose image number is 10.


A–58 Export Tool


Port statisticsThe following table shows the file names and types of information in the Monitor Performance window that can be exported to files using the Export Tool. These files contain statistics about ports.

Table A-9 Files with statistics about ports

Host bus adapters connected to ports statisticsThe following table shows the file names and types of information in the Monitor Performance window that can be exported to files using the Export Tool. These files contain statistics about host bus adapters connected to ports.

Table A-10 Files with statistics about host bus adapters connected to ports


Port_dat.zip

Port_IOPS.csv The number of read and write operations per second at ports

Port_KBPS.csv The size of data transferred per second at ports (KB/sec)

Port_Response.csv The average response time (microseconds) at ports

Port_Initiator_IOPS.csv

The number of read and write operations per second at Initiator/External ports

Port_Initiator_KBPS.csv

The size of data transferred per second at Initiator/External ports (KB/sec)

Port_Initiator_Response.csv

The average response time (microseconds) at Initiator/External ports


PortWWN_dat.zip

PortWWN_xx_IOPS.csv

The I/O rate (that is, the number of read and write operations per second) for HBAs that are connected to a port

PortWWN_xx_KBPS.csv

The size of data transferred per second (KB/sec) between a port and the HBAs connected to that port

PortWWN_xx_Response.csv

The average response time (microseconds) between a port and the HBAs connected to that port

Notes: • The letters "xx" in CSV filenames indicate a port name. For example, if the filename

is PortWWN_1A_IOPS.csv, the file contains the I/O rate for each host bus adapter connected to the CL1-A port.

• If files are exported to a Windows computer, CSV filenames may end with numbers (for example, PortWWN_1A_IOPS-1.csv and PortWWN_1a_IOPS-2.csv).

Export Tool A–59


Volumes (LU) statisticsThe following table shows the file names and types of information in the Monitor Performance window that can be exported to files using the Export Tool. These files contain statistics about volumes (LUs).

Table A-11 Files with statistics about volumes (LUs)


LU_dat.zip

LU_IOPS.csv The number of read and write operations per second

LU_TransRate.csv The size of data transferred per second (KB/sec)

LU_Read_TransRate.csv

The size of read data transferred per second (KB/sec)

LU_Write_TransRate.csv

The size of write data transferred per second (KB/sec)

LU_Read_Response.csv

The average read response time (microseconds)

LU_Write_Response.csv

The average write response time (microseconds)

LU_Seq_Read_IOPS.csv


LU_Rnd_Read_IOPS.csv


LU_Seq_Write_IOPS.csv


LU_Rnd_Write_IOPS.csv


LU_Seq_Read_Hit.csv


LU_Rnd_Read_Hit.csv


LU_Seq_Write_Hit.csv


LU_Rnd_Write_Hit.csv


LU_C2D_Trans.csv The number of data transfer operations from cache memories and hard disk drives (i.e., LUs)

LU_D2CS_Trans.csv

The number of data transfer operations from hard disk drives (i.e., LUs) to cache memories in sequential access mode

LU_D2CR_Trans.csv

The number of data transfer operations from hard disk drives (i.e., LUs) to cache memories in random access mode

LU_Response.csv The average response time (microseconds) at volumes (LUs)

A–60 Export Tool


All host bus adapters connected to portsThe following table shows the file names and types of information in the Monitor Performance window that can be exported to files using the Export Tool. These files contain statistics about all host bus adapters connected to ports.

Table A-12 Files with statistics about all host bus adapters connected to ports

Processor bladesThe following table shows the file names and types of information in the Monitor Performance window that can be exported to files using the Export Tool. The file contains statistics about usage rates of Processor blades.

Table A-13 Performance information on each processor blade


PPCGWWN_dat.zip

PPCGWWN_NotGrouped_IOPS.csv

The I/O rate (that is, the number of read and write operations per second) for all HBAs that are connected to ports

PPCGWWN_NotGrouped_KBPS.csv

The transfer rate (KB/sec) for all HBAs that are connected to ports

PPCGWWN_NotGrouped_Response.csv

The average response time (microseconds), for all HBAs that are connected to ports


PHY_MPPK.ZIP PHY_MPPK_x.y.csv

Performance information on each processor bladeThe performance information on each processor blade are output in the following formats:• Performance information of LDEVs

Kernel-type (*1);LDEV;LDEV-number;Usage-rate• Performance information of journals

Kernel-type (*1);JNLG; Journal-number;Usage-rates

• Performance information of external volumesKernel-type (*1);ExG;External-volume-group-number;Usage-rate

Caution:• Performance information are displayed up to 100

items in order with high working ratio.• The sum of the working ratio of this information

does not corresponde with the sum of the working ratio of MP blades.

*1 : The kernal type is any one of the following types:Open-Target, Open-Initiator, Open-External, MF-Target, MF-External, BackEnd, or System.

Export Tool A–61


Remote copy operations by TC/TCz (whole volumes)The following table shows the file names and types of information in the Usage Monitor tab in the TC and TCz window that can be exported to files using the Export Tool. These files contain statistics about remote copy operations (whole volumes) by TrueCopy and TrueCopy for Mainframe.

Table A-14 Files with statistics about remote copy operations by TC and TCz (In the whole volumes)

Remote copy operations by TC and TCz (for each volume (LU))The following table shows the file names and types of information in the Usage Monitor tab in the TC and TCz window that can be exported to files using the Export Tool. These files contain statistics about remote copy operations (for each volume (LU)) by TrueCopy and TrueCopy for Mainframe.


RemoteCopy_dat.zip

RemoteCopy.csv

The following data in the whole volumes are saved:• The total number of remote I/Os (read and write

operations). • The total number of remote write I/Os.• The number of errors that occur during remote I/

O• The number of initial copy remote I/Os. • The average response time (milliseconds) for

initial copy.• The average transfer rate (KB/sec) for initial copy

remote I/Os. • The number of update copy remote I/Os. • The average transfer rate (KB/sec) for update

copy remote I/Os.• The average response time (milliseconds) for

update copy• The percentage of completion of copy operations

(i.e., number of synchronized pairs / total number of pairs)

• The number of tracks that have not yet been copied by the initial copy or resync copy operation

A–62 Export Tool


Table A-15 Files with statistics about remote copy operations by TC and TCz (for each volume (LU))

Remote copy by TC and TCz (volumes controlled by a particular CU)

The following table shows the file names and types of information in the Usage Monitor tab in the TC and TCz window that can be exported to files using the Export Tool. These files contain statistics about remote copy operations (volumes controlled by a particular CU) by TrueCopy and TrueCopy for Mainframe.


RCLU_dat.zip

RCLU_All_RIO.csv The total number of remote I/Os (read and write operations)

RCLU_All_Read.csv The total number of remote read I/Os

RCLU_All_Write.csv The total number of remote write I/Os

RCLU_RIO_Error.csv The number of errors that occur during remote I/O

RCLU_Initial_Copy_RIO.csv The number of initial copy remote I/Os

RCLU_Initial_Copy_Hit.csv The number of hits of initial copy remote I/Os

RCLU_Initial_Copy_Transfer.csv

The average transfer rate (KB/sec) for initial copy remote I/Os

RCLU_Initial_Copy_Response.csv

The average response time (milliseconds) for the initial copy of each volume (LU)

RCLU_Migration_Copy_RIO.csv

The number of migration copy remote I/Os

RCLU_Migration_Copy_Hit.csv The number of hits of migration copy remote I/Os

RCLU_Update_Copy_RIO.csv The number of update copy remote I/Os

RCLU_Update_Copy_Hit.csv The number of hits of update copy remote I/Os

RCLU_Update_Copy_Transfer.csv

The average transfer rate (KB/sec) for update copy remote I/Os

RCLU_Update_Copy_Response.csv

The average response time (milliseconds) for the update copy of each volume (LU)

RCLU_Restore_Copy_RIO.csv The number of restore copy remote I/Os

RCLU_Restore_Copy_Hit.csv The number of hits of restore copy remote I/Os

RCLU_Pair_Synchronized.csv The percentage of completion of copy operations (i.e., number of synchronized pairs / total number of pairs)

RCLU_Out_of_Tracks.csv The number of tracks that have not yet been copied by the initial copy or resync copy operation

Export Tool A–63


Table A-16 Files with statistics about remote copy operations by TC and TCz (at volumes controlled by a particular CU)


RCLDEV_All_RIO.zip RCLDEV_All_RIO_xx.csv The total number of remote I/Os (read and write operations)

RCLDEV_All_Read.zip RCLDEV_All_Read_xx.csv The total number of remote read I/Os

RCLDEV_All_Write.zip RCLDEV_All_Write_xx.csv The total number of remote write I/Os

RCLDEV_RIO_Error.zip RCLDEV_RIO_Error_xx.csv The number of errors that occur during remote I/O

RCLDEV_Initial_Copy_RIO.zip RCLDEV_Initial_Copy_RIO_xx.csv

The number of initial copy remote I/Os

RCLDEV_Initial_Copy_Hit.zip RCLDEV_Initial_Copy_Hit_xx.csv

The number of hits of initial copy remote I/Os

RCLDEV_Initial_Copy_Transfer.zip

RCLDEV_Initial_Copy_Transfer_xx.csv

The average transfer rate (KB/sec) for initial copy remote I/Os

RCLDEV_Initial_Copy_Response.zip

RCLDEV_Initial_Copy_Response_xx.csv

The average response time (milliseconds) for initial copy at volumes

RCLDEV_Migration_Copy_RIO.zip

RCLDEV_Migration_Copy_RIO_xx.csv

The number of migration copy remote I/Os

RCLDEV_Migration_Copy_Hit.zip

RCLDEV_Migration_Copy_Hit_xx.csv

The number of hits of migration copy remote I/Os

RCLDEV_Update_Copy_RIO.zip

RCLDEV_Update_Copy_RIO_xx.csv

The number of update copy remote I/Os

RCLDEV_Update_Copy_Hit.zip RCLDEV_Update_Copy_Hit_xx.csv

The number of hits of update copy remote I/Os

RCLDEV_Update_Copy_Transfer.zip

RCLDEV_Update_Copy_Transfer_xx.csv

The average transfer rate (KB/sec) for update copy remote I/Os

RCLDEV_Update_Copy_Response.zip

RCLDEV_Update_Copy_Response_xx.csv

The average response time (milliseconds) for the update copy at volumes

A–64 Export Tool


Remote copy by UR and URz (whole volumes)The following table shows the file names and types of information in the Usage Monitor tab in the UR and URz window that can be exported to files using the Export Tool. These files contain statistics about remote copy operations (whole volumes) by Universal Replicator and Hitachi Universal Replicator software for Mainframe.

RCLDEV_Restore_Copy_RIO.zip

RCLDEV_Restore_Copy_RIO_xx.csv

The number of restore copy remote I/Os

RCLDEV_Restore_Copy_Hit.zip RCLDEV_Restore_Copy_Hit_xx.csv

The number of hits of restore copy remote I/Os

RCLDEV_Pair_Synchronized.zip

RCLDEV_Pair_Synchronized_xx.csv

The percentage of completion of copy operations (i.e., number of synchronized pairs / total number of pairs)

RCLDEV_Out_of_Tracks.zip RCLDEV_Out_of_Tracks_xx.csv The number of tracks that have not yet been copied by the initial copy or Resync copy operation

Note: • The letters "xx" in CSV filenames indicate a CU image number. For example, if the

filename is RCLDEV_All_RIO_10.csv, the file contains the total number of remote I/Os of the volumes controlled by the CU whose image number is 10.


Export Tool A–65


Table A-17 Files with statistics about remote copy operations by UR and URz (In the whole volumes)

Remote copy by UR and URz (at journals)The following table shows the file names and types of information in the Usage Monitor tab in the UR and URz window that can be exported to files using the Export Tool. These files contain statistics about remote copy operations (at journals) by Universal Replicator and Hitachi Universal Replicator software for Mainframe.


UniversalReplicator.zip

UniversalReplicator.csv

The following data in the whole volumes are saved: • The number of write I/Os per second. • The amount of data that are written per

second (KB/sec)• The initial copy hit rate (percent)• The average transfer rate (KB/sec) for initial

copy operations • The number of asynchronous remote I/Os

per second at the primary storage system• The number of journals at the primary

storage system• The average transfer rate (KB/sec) for

journals in the primary storage system• The remote I/O average response time

(milliseconds) on the primary storage system

• The number of asynchronous remote I/Os per second at the secondary storage system

• The number of journals at the secondary storage system

• The average transfer rate (KB/sec) for journals in the secondary storage system

• The remote I/O average response time (milliseconds) on the secondary storage system

A–66 Export Tool


Table A-18 Files with statistics about remote copy operations by UR and URz (at journals)

Remote copy by UR and URz (for each volume (LU))The following table shows the file names and types of information in the Usage Monitor tab in the UR and URz window that can be exported to files using the Export Tool. These files contain statistics about remote copy operations (for each volume (LU)) by Universal Replicator and Hitachi Universal Replicator software for Mainframe.


URJNL_dat.zip

URJNL_Write_Record.csv The number of write I/Os per second

URJNL_Write_Transfer.csv The amount of data that are written per second (KB/sec)

URJNL_Initial_Copy_Hit.csv The initial copy hit rate (percent)

URJNL_Initial_Copy_Transfer.csv The average transfer rate (KB/sec) for initial copy operations

URJNL_M-JNL_Asynchronous_RIO.csv

The number of asynchronous remote I/Os per second at the primary storage system

URJNL_M-JNL_Asynchronous_Journal.csv

The number of journals at the primary storage system

URJNL_M-JNL_Asynchronous_Copy_Transfer.csv

The average transfer rate (KB/sec) for journals in the primary storage system

URJNL_M-JNL_Asynchronous_Copy_Response.csv

The remote I/O average response time (milliseconds) on the primary storage system

URJNL_R-JNL_Asynchronous_RIO.csv

The number of asynchronous remote I/Os per second at the secondary storage system

URJNL_R-JNL_Asynchronous_Journal.csv

The number of journals at the secondary storage system

URJNL_R-JNL_Asynchronous_Copy_Transfer.csv

The average transfer rate (KB/sec) for journals in the secondary storage system

URJNL_dat.zip (continued)

URJNL_R-JNL_Asynchronous_Copy_Response.csv

The remote I/O average response time (milliseconds) on the secondary storage system

URJNL_M-JNL_Data_Used_Rate.csv Data usage rate (percent) for master journals

URJNL_M-JNL_Meta_Data_Used_Rate.csv

Metadata usage rate (percent) for master journals

URJNL_R-JNL_Data_Used_Rate.csv Data usage rate (percent) for restore journals

URJNL_R-JNL_Meta_Data_Used_Rate.csv

Metadata usage rate (percent) for restore journals

Export Tool A–67


Table A-19 Files with statistics about remote copy operations by UR and URz (for each volume (LU))

Remote copy by UR and URz (at volumes controlled by a particular CU)

The following table shows the file names and types of information in the Usage Monitor tab in the UR and URz window that can be exported to files using the Export Tool. These files contain statistics about remote copy operations (at volumes controlled by a particular CU) by Universal Replicator and Hitachi Universal Replicator software for Mainframe.

Table A-20 Files with statistics about remote copy operations by UR and URz (at Volumes controlled by a particular CU)


URLU_dat.zip

URLU_Read_Record.csv The number of read I/Os per second

URLU_Read_Hit.csv The number of read hit records per second

URLU_Write_Record.csv

The number of write I/Os per second

URLU_Write_Hit.csv The number of write hit records per second

URLU_Read_Transfer.csv

The amount of data that are read per second (KB/sec)

URLU_Write_Transfer.csv

The amount of data that are written per second (KB/sec)

URLU_Initial_Copy_Hit.csv

The initial copy hit rate (percent)

URLU_Initial_Copy_Transfer.csv

The average transfer rate (KB/sec) for initial copy operations


URLDEV_Read_Record.zip URLDEV_Read_Record_xx.csv

The number of read I/Os per second

URLDEV_Read_Hit.zip URLDEV_Read_Hit_xx.csv The number of read hit records per second

URLDEV_Write_Record.zip URLDEV_Write_Record_xx.csv

The number of write I/Os per second

URLDEV_Write_Hit.zip URLDEV_Write_Hit_xx.csv The number of write hit records per second

URLDEV_Read_Transfer.zip

URLDEV_Read_Transfer_xx.csv

The amount of data that are read per second (KB/sec)

URLDEV_Write_Transfer.zip

URLDEV_Write_Transfer_xx.csv

The amount of data that are written per second (KB/sec)

URLDEV_Initial_Copy_Hit.zip

URLDEV_Initial_Copy_Hit_xx.csv

The initial copy hit rate (percent)

URLDEV_Initial_Copy_Transfer.zip

URLDEV_Initial_Copy_Transfer_xx.csv

The average transfer rate (KB/sec) for initial copy operations

A–68 Export Tool


Causes of Invalid Monitoring DataIf the value of monitoring data in CSV files is less than 0 (zero), consider the following causes:

Note: The letters "xx" in CSV filenames indicate a CU image number. For example, if the filename is URLDEV_Read_Record_10.csv, the file contains the number of read I/Os (per second) of the volumes controlled by the CU whose image number is 10.


Invalid values of monitoring data Probable causes

The monitoring data in the CSV file includes "-1".

The value "-1" indicates that Performance Monitor failed to obtain monitoring data. Probable reasons are:Performance Monitor attempted to obtain statistics when an operation for rebooting the disk array is in progress.Performance Monitor attempted to obtain statistics when a heavy workload is imposed on the disk array.There is no volume in a parity group.Just after the CUs to be monitored were added, the Export Tool failed to save files that contain monitoring data for all volumes or journal volumes used by remote copy software (i.e., TrueCopy, TrueCopy for Mainframe, Universal Replicator, or Hitachi Universal Replicator software for Mainframe). For details about the files, see Table A-14 Files with statistics about remote copy operations by TC and TCz (In the whole volumes) on page A-61, Table A-17 Files with statistics about remote copy operations by UR and URz (In the whole volumes) on page A-65, andTable A-18 Files with statistics about remote copy operations by UR and URz (at journals) on page A-66.If Disable is selected to stop monitoring in the Monitoring Switch field on the Monitoring Options window and longrange is specified as the gathering interval, the monitoring data for the period when Performance Monitor stops monitoring is "-1". If you added the CU during monitoring, specified longrange as the gathering interval, and collected monitoring data, the value "-1" is displayed as the monitoring data before the CU was added.


The value "-3" indicates that Performance Monitor failed to obtain monitoring data for the following reason:If IOPS is 0 (zero), the Response Time that is included in the monitoring data for LUs, LDEVs, ports, WWNs, or external volumes is "-3". Because IOPS is 0 (zero), the average response time becomes invalid.


The value "-4" indicates that Performance Monitor failed to obtain monitoring data for the following reason:If the period for the monitoring data that is specified with the Export Tool does not match the collecting period for monitoring data, the Export Tool cannot collect the monitoring data. If data of SVP is updated while the monitoring data is being collected, the collected monitoring data near the collection start time is "-4".

Export Tool A–69


Troubleshooting the Export ToolThe following table explains possible problems with the Export Tool and probable solutions to the problems.


When the CU number is not the monitoring target object, Performance Monitor cannot obtain monitoring data from the CU. If the PG, LDEV, LU, RCLU, RCLDEV, URLU, or URLDEV operand is specified, the value of the monitoring data is "-5". To solve this problem, specify the CU as the monitoring target object by using the Monitoring Options window of Performance Monitor (not by using the Export Tool). If the RemoteCopy, UniversalReplicator, or URJNL operand is specified, the value "-5" is not output in the monitoring data though the CU number is not the monitoring target object. In this case, data on monitored CUs are summed up and output into the CSV file.

Invalid values of monitoring data Probable causes

Possible problems Probable causes and recommended action

You cannot run the batch file.

The path to the Java Virtual Machine (Java.exe) might not be defined in the PATH environment variable. If this is true, you must add that path to the PATH environment variable. For information about how to add a path to the environment variable, refer to the documentation for your operating system.An incorrect version of Java Runtime Environment (JRE) might be installed on your computer. To check the JRE version, enter the following command at the Windows command prompt or the UNIX console window:Java -versionIf the version is incorrect, install the correct version of JRE.

The Export Tool stops and the processing does not continue.

• The command prompt window might be in pause mode. The command prompt window will be in pause mode if you click the command prompt window when the Export Tool is running. To cancel pause mode, activate the command prompt window and then press the <ESC> key. If a timeout of RMI occurs during pause mode, the login will be canceled and an error will occur when you cancel pause mode after the timeout. The error message ID will be (0001 4011).

• If a memory size is not specified in a batch file, the Out Of Memory Error occurs in JRE, the Export Tool might stop and the processing might not continue. Confirm whether the specified memory size is correct or not.

The command prompt window was displaying progress of the export processing, but the window stopped displaying progress before the processing stopped. The progress information does not seem to be updated anymore.

A–70 Export Tool


An error occurs and the processing stops.

If the error message ID is (0001 4011), the user is forcibly logged off and the processing stops because the Export Tool did not issue any request to SVP. The computer running the Export Tool could be slow. Confirm whether you are using a computer that is not supported, or whether the computer is slow. Run the Export Tool again. If the error persists, contact the Hitachi Data Systems Support Center for more information.If the error message ID is (0002 5510), probable error causes and solutions are:• An internal processing is being performed in the disk

array. Alternatively, another user is changing configurations. Wait for a while and then run the Export Tool again.

• Maintenance operations are being performed on the disk array. Wait until the maintenance operations finish and then run the Export Tool again.

If the error message ID is none of the above, see Messages issued by the Export tool on page A-71


For details on invalid monitoring data, see Causes of Invalid Monitoring Data on page A-68.

• When the Export Tool terminated abnormally due to error, the row of Check License is shown as UnmarshalException in the log file.

• The Export Tool terminated abnormally because the processing did not continue. version unmatched is shown in the log file.

It might be unsuitable combination of DKCMAIN/SVP program version and Export Tool version. Confirm whether versions of these programs are correct.

When a CSV file is opened, the parity group ID and volume ID appear as follows:• The parity group

IDs appear as dates

• The volume IDs appear with a decimal point

To display a CSV file correctly, you need to perform following operations: 1. Start Microsoft Excel.2. On the menu bar, select Data, Import External Data, and Import Text File, and specify a CSV file to import. The Text Import.zip - Step 1 of 3 dialog box is displayed3. In the Text Import.zip - Step 1 of 3 dialog box, click Next. Text Import.zip - Step 2 of 3 dialog box is displayed4. In the Text Import.zip - Step 2 of 3 dialog box, check only Comma in the Delimiter area, and click Next. The Text Import.zip - Step 3 of 3 dialog box is displayed5. In the Text Import.zip - Step 3 of 3 dialog box, select all columns of Date preview, and check Text in the Column data format area on the upper right of this dialog box.6. Click Finish. The imported CSV file is displayed.


Export Tool A–71


Messages issued by the Export toolIf an error occurs when running the Export Tool, error messages are issued to the standard output (for example, the command prompt) and the log file. The following table lists the Export Tool messages and recommended actions against errors.

When you executed the Export Tool with many volumes specified, the Export Tool terminated abnormally while gathering monitoring data.

Because too many volumes are specified, a timeout error might have occurred due to a heavy workload imposed on the computer where the Export Tool was running. The error message ID is (0001 4011). Specify fewer volumes. It is recommended that the number of volumes to be specified is 16,384 or less.


Export Tool messages Probable causes and recommended action

Connection to the server has not been established.

Connection to the server has not been established. Use the login subcommand.

Execution stops. Execution stops. Remove errors.

Illegal character: "character" An illegal character is used. Use legal characters.

Invalid length: token The length is invalid. Specify a value that has a correct length.

Invalid range: range The specified range is invalid. Specify the correct range.

Invalid value: "value" The specified value is invalid. Specify a correct value.

Login failed An attempt to log into SVP failed. Probable causes are:1. An incorrect operand is used for the svpip subcommand.2. An incorrect operand is used for the login subcommand.3. The specified user ID is used by another person, and the person is being logged in.4. Two users are currently displaying the Monitor Performance window.5. Two users are currently executing the Export Tool.If the error cause does not apply to any one of above, see Troubleshooting the Export Tool on page A-69.If the error cause is either 4 or 5 above, do one of the following:• Ask one of the users to display another window.• Ask one of the users to log off.• Wait for one of the users to quit the Export Tool.

Missing command file The command file is not specified. Specify the name of the command file correctly.

Missing group name No operand is specified in the group subcommand. Specify operands for the subcommand.

Missing host name No host name is specified. Specify a host name.

Missing output directory No directory is specified for saving files. Specify the directory for saving files.

A–72 Export Tool


Missing password The Export Tool cannot find the user ID, which is used to log into SVP. Specify the password.

Missing svpip The svpip subcommand is not used. Use the svpip command.

Missing time range Specify the time range.

Missing user ID The Export Tool cannot find the user ID, which is used to log into SVP. Specify the user ID.

Out of range: range The value is outside the range. If the short-range subcommand or the long-range subcommand is used, specify a value within the range from the monitoring start time to the monitoring end time.If the set subcommand is used with the switch operand, specify a value within the range of 1 to 15.

Permission Denied. The user ID does not have the required permission.The user ID needs to have at least one of permissions for Performance Monitor, TrueCopy, TrueCopy for Mainframe, Universal Replicator, and Hitachi Universal Replicator software for Mainframe.

RMI server error (part-code, error-number)

An error occurs at the RMI server. For detailed information, see the Hitachi Storage Navigator Messages.

Unable to display help message

The Export Tool cannot display the online help due to a system error.

Unable to get serial number The Export Tool cannot obtain the serial number due to a system error.

Unable to get time range for monitoring

SVP does not contain monitoring data.

Unable to read command file: file

The Export Tool cannot read the command file. Specify the name of the command file correctly.

Unable to use the command: command

The specified subcommand is unavailable.

Unable to use the group name: operand

The specified operand of the group subcommand is unavailable.

Unknown host: host The Export Tool cannot resolve the host name. Specify the correct host name.

Unsupported command: command

The Export Tool does not support the specified command. Specify a correct command.

Unsupported operand: operand

The specified operand is not supported. Correct the specified operand.

Unsupported option: option The specified option is not supported. Correct the specified option.

Some file exists in path. What do you do? clear(c)/update(u)/stop(p) You selected "action". Is it OK? (y/n)

Files exist in path.If you want to clear the files, press the <c> key.If you want to overwrite the files, press the <u> key.If you want to stop the operation, press the <p> key.When you press a key, a message appears and asks whether to perform the specified action.To perform the specified action, press the <y> key.To cancel the specified action, press the <n> key.


Export Tool A–73


Specify the following subcommand before login subcommand: retry

The retry subcommand is written in an incorrect position in the command file.Write the retry subcommand before the login subcommand.

Start gathering group data Target = xxx, Total = yyy End gathering group data

The Export Tool starts collecting data specified by the group subcommand.The number of target objects is xxx and the total number is yyy (refer to Note below).The Export Tool ends collecting data.Note: For example, suppose that the storage system contains 100 parity groups and the command file contains the following command line: group PG 1-1:1-2The Export Tool displays the message "Target=2, Total=100", which means that the group subcommand specifies two parity groups and that the total number of parity groups in the storage system is 100.

Syntax error: "line" A syntax error is detected in a command line in your command file. Check the command line for the syntax error and then correct the script.Some operands must be enclosed by double quotation marks ("). Check the command line to find whether double quotation marks are missing.

[login]version unmatched The export tool version does not correspond to SVP version. Upgrade the export tool to match the export tool version with SVP version.


A–74 Export Tool


Performance Monitor GUI reference B–1


BPerformance Monitor GUI reference

This topic provides reference information about the Performance Monitor GUI.

□ Performance Monitor main window

□ Edit Monitoring Switch wizard

□ Monitor Performance window

□ Edit CU Monitor Mode wizard

□ View CU Matrix window

□ Select by Parity Groups window

□ Parity Group Properties window

□ Edit WWN wizard

□ Edit WWN Monitor Mode wizard

□ Delete Unused WWNs window

□ Add New Monitored WWNs wizard

□ Add to Ports wizard

□ Monitor window

□ Edit Time Range window

□ Edit Performance Objects window

B–2 Performance Monitor GUI reference


□ Add Graph window



Performance Monitor main window

• Summary on page B-4

• Monitored CUs tab on page B-4

• Monitored WWNs tab on page B-5



This is the main window for monitoring performance on your storage system. From this window you can set up monitoring parameters, start and stop monitoring, and view performance graphs. This window is available when Performance Monitor is selected in the Storage Navigator main window.

Summary

The summary information of monitoring is displayed.

Monitored CUs tab

Use this tab to view information about the CUs that are currently being monitored.

Item Description

Monitoring Switch Monitoring statuses of following:• Enabled: Performance Monitor is monitoring the

storage system.• Disabled: The storage system is not being monitored.

Sample Interval Current sampling interval, from 1 to 15 minutes, for which statistics are collected during short-range monitoring. This value is available when Enabled is selected in the Monitoring Switch field. If Disabled is selected, a hyphen appears.

Number of Monitored CUs Number, from 0 to 255, of CUs currently being monitored.

Number of Monitored LDEVs

Number, from 0 to 65280, of LDEVs currently being monitored.

Number of Monitored WWNs

Number, from 0 to 2048, of WWNs currently being monitored.

Monitor Performance Click to open the window where you can specify the monitoring objects and monitoring period. Up to 8 objects can be specified in one graph panel. Up to 16 objects can be specified in 4 graph panels.

Edit Monitoring Switch Click to open the Edit Monitoring Switch window where you can start or stop performance monitoring, and specify how often to monitor statistics.

Item Description

CU Number of monitored CUs.

Number of LDEVs Number of LDEVs included in the monitored CUs.

Selected N of M N: Number of selected CUs.M: Total count of CUs.

Edit CU Monitor Mode Click to open the Edit CU Monitor Mode window, where you can change the monitoring status.

View CU Matrix Click to open the View CU Matrix window, where you can view following monitoring statuses of CUs.• CU which is being monitored• CU which is scheduled to be monitored• CU which is scheduled to be released from

monitoring.



Monitored WWNs tab

Use this tab to view information about the WWNs that are currently being monitored.

*Appears when you click More Actions.

Edit Monitoring Switch wizard

Edit Monitoring Switch windowUse this window to start and stop performance monitoring and to specify the sampling interval for how often to monitor statistics.

Export Displays the window for outputting table information.

Item Description

Item Description

Port ID Name of the port of the monitored WWN.

HBA WWN Host bus adapter ID of the monitored WWN.

WWN Name A WWN name is up to 64 alphanumeric characters and some signs.

Status Following statuses of the port connected with WWN.• Normal: All WWNs connected with the port are

monitoring target objects.• Non-Integrity: The WWN is not monitored for

the corresponding port, but monitored for other ports.

Selected N of M N: Number of selected WWNs.M: Total count of WWNs.

Edit WWN Monitor Mode Click to open the Edit WWN Monitor Mode window.

Add New Monitored WWN Click to open the Add New Monitored WWN window.

Edit WWN Click to open the Edit WWN window.

Delete Unused WWNs* Click to open Delete Unused WWNs window.

Add to Ports* Click to open the Add to Ports window.

Export* Displays the window for outputting table information.



Monitoring Switch

Specify the monitoring status.

• Enable: Performance Monitor is monitoring the storage system

• Disable: Performance Monitor is not monitoring the storage system.

Sample Interval

Specify the time interval of collecting statistics.

• If the number of CUs to be monitored is 64 or less, you can specify from 1 to 15 minutes at intervals of 1 minute. Default is blank.

• If 65 or more CUs are monitored, you can specify from 5 to 15 minutes at intervals of 5 minutes. Default is blank.

Confirm windowUse this window to confirm the specified monitoring information and to assign a task name to the editing task.



Monitoring Switch Setting table

Confirm the monitoring switch information to be changed.

Monitor Performance windowUse this window to specify the monitoring period and monitoring objects that will be displayed in graphs

Item Description

Monitoring Switch: Following monitoring statuses of the storage system.Enable: Performance Monitor is monitoring the storage systemDisable: Performance Monitor is not monitoring the storage system.

Sample Interval: Time interval of collecting statistics.



Data Range

Specify a range of statistics. Short-Range is default when there is monitor data collected with Short-Range. However, Long-Range is default when there is no monitor data collected with Short-Range.

• Short-Range: Graphs are displayed according to the value specified in the Sample Interval field in the Edit Monitoring Switch window.

• Long-Range: Graphs are displayed 0, 15, 30, or 45 minutes on every hour.

Time Range

Specify the storing period of statistics

• Set Range: Select this option to specify start and ending times to set a time range for which monitoring statistics will be collected.

• Use Real Time: Select this option to view statistics in real time mode, where statistics are updated at the value of the Sample Interval you specify on the Edit Monitoring Switch window. This option is available when the short range mode is selected. When this option is selected, you cannot change the date field in the Set Range option.



Performance Objects

Add

Adds objects to display the graph.

Item Description

Object: Types of objects to display on graphs. The list on the left specifies a large classification of monitoring objects. The list on the right specifies a small classification of monitoring objects.

Monitor Data: Performance data specified in the Object field. The list on the left specifies a large classification of performance data. The list on the right specifies a small classification of performance data.For details, see Object and Monitor Data combinations on page B-11

Performance Object Selection:

Objects that can be displayed in graphs. For details, see Available Objects table on page B-15.

Selected N of M N: Number of selected objects.M: Total count of objects.



Selected Objects table

Apply

Accepts the settings and displays the graph.

Cancel

Cancels the current operation and closes this window.

Help

Opens the help topic for this window.

Item Description

Object: Object types selected in the Performance Objects area.

Monitor Data: Monitor data types selected in the Performance Objects area.

Object ID: IDs of the selected objects.

Selected N of M N: Number of selected objects.M: Total count of objects.

Remove: Selected row(s) can be deleted from the table.



Object and Monitor Data combinations

The following table shows the possible Object and Monitor Data combinations that can be selected in the Performance Objects area of the Monitor Performance window.

• If Controller is selected on the left side of the Object field, the item on the right side of Monitor Data field is blank.

• If Cache is selected on the left side of the Object field, items on the right side of the Object and Monitor Data is blank field.

• If Access Path is selected on the left side of the Object field, the item on the right side of the Monitor Data field is blank.

• If Port is selected on the left side of the Object field, the item on left side of the Object and Monitor Data fields are blank.

• If WWN is selected on the left side of the Object field, the item on the right side of the Monitor Data field is blank.

Item on right side of Object field

Item on left side of Monitor Data field

Unit of monitoring data

MP Usage Rate %

DRR Usage Rate %



Unit of monitoring

data

None Usage Rate %

None Write Pending Rate %




CHA ESW Usage Rate %

DKA ESW Usage Rate %

MP Blade ESW Usage Rate %

Cache ESW Usage Rate %




None Throughput IOPS

None Data Trans. MB/s

None Response Time ms



• If Logical Device is selected on the left side of the Object field, the item on the right side of the Object field is blank.




WWN Throughput IOPS

Data Trans. MB/s

Response Time ms

Port Throughput IOPS

Data Trans. MB/s

Response Time ms


Item on right side of Monitor Data field


Total Throughput Total IOPS

Sequential

Random

CFW

Read Throughput Total IOPS

Sequential

Random

CFW

Write Throughput Total IOPS

Sequential

Random

CFW

Cache Hit Read (Total) %

Read (Sequential)

Read (Random)

Read (CFW)

Write (Total)

Write (Sequential)

Write (Random)

Write (CFW)

Data Trans. Total MB/s

Read

Write

Response Time Total ms

Read

Write



• If Parity Group is selected on the left side of the Object field, the item on the right side of the Object field is blank.

Back Trans. Total count/sec

Cache To Drive

Drive To Cache (Sequential)

Drive To Cache (Random)

Drive Usage Rate None %

Drive Access Rate Read (Sequential) %

Read (Random)

Write (Sequential)

Write (Random)

ShadowImage None %








Sequential

Random

CFW


Sequential

Random

CFW


Sequential

Random

CFW


Read (Sequential)

Read (Random)

Read (CFW)

Write (Total)

Write (Sequential)

Write (Random)

Write (CFW)


Read

Write



• If LUN is selected on the left side of the Object field, the item on the right side of the Object field is blank.


Read

Write


Cache To Drive











Sequential

Random

CFW


Sequential

Random

CFW


Sequential

Random

CFW


Read (Sequential)

Read (Random)

Read (CFW)

Write (Total)

Write (Sequential)

Write (Random)

Write (CFW)


Read

Write


Read

Write



• If External Storage is selected on the left side of the Object field, following items can be selected.

Available Objects table

The items appearing in the Available Objects table depend on the objects selected in the Performance Objects fields.


Cache To Drive






Item on right side of Object

field



Unit of monitoring

data

Logical Device Data Trans. Total MB/s

Read

Write


Read

Write

Parity Group Data Trans. Total MB/s

Read

Write


Read

Write

Monitoring object Item Description

Port Port ID Name of the port.

WWN/WWN HBA WWN Worldwide name of the host bus adapter. A WWN is a 16-digit hexadecimal number used as the unique identifier for a host bus adapter.

WWN Name Nickname of the host bus adapter. A WWN name is up to 64 alphanumeric characters and some signs.



Edit CU Monitor Mode wizard

Edit CU Monitor Mode windowThis window contains information about all the CUs in the storage system, in table format, indicating which are monitored and which are unmonitored. Use this window to add and remove CUs as monitoring target objects.

WWN/Port Port ID Name of the port.

HBA WWN WWN of the host bus adapter. A WWN is a 16-digit hexadecimal number used as the unique identifier for a host bus adapter.


Logical Device LDEV ID ID of the volume, in the following format: LDKC:CU:LDEV.

LDEV Name Name of the LDEV. LDEV Name is the combination of fixed characters and numbers.

Parity Group Parity Group ID ID of the parity group.

LUN Port ID Name of the port.

Host Group Name Name of the host group.

LUN ID ID of the LUN.

External Volume Parity Group ID Parity group ID of the external volume.

Controller/MP MP Blade ID/MP ID ID of a processor blade and processor.

Controller/DRR DRR ID ID of a data recovery and reconstruction processor.

Cache MP Blade ID ID of a processor blade.

Cache Name of the cache.

Access Paths Access Paths Name of the access path.




Unmonitored CUs table



A table of the CUs that are going to be unmonitored.

Add

Click to add CUs to Monitored CUs table.

Remove

Click to remove CUs from Monitored CUs table.

Monitored CUs table

A table of the CUs that are going to be monitored.

Item Description

CU Unmonitored CU number.

Number of LDEVs Number of LDEVs included in the unmonitored CUs.

Current Monitor Mode - Enabled: The CU is a monitoring target object.- Disabled: The CU is not a monitoring target object.

Select by Parity Group Click to open the Select by Parity Group window, where you can select CUs from parity groups.



Confirm windowUse this window to confirm the edited CU monitoring mode information and to assign a task name to the editing task.

Item Description

CU Number of a CU which is going to be monitored.

Number of LDEVs: Number of LDEVs included in the monitored CUs.

Current Monitor Mode - Enabled: The CU is a monitoring target object.- Disabled: The CU is not a monitoring target object.

View CU Matrix Click to open the View CU Matrix window, where you can view following monitoring statuses of CUs.• CU which is being monitored• CU which is scheduled to be monitored• CU which is scheduled to be released from monitoring.



Selected CUs to Enable Monitor table

Confirm the information about the CUs to be monitored.

Item Description

CU CUs to be monitored.

Number of LDEVs Number of LDEVs in the CU to be monitored.

Total Total count of CUs.




Selected CUs to Disable Monitor table

Information about the CUs not to be monitored.

View CU Matrix windowUse this window to view a matrix of the monitoring status of all the CUs in one LDKC. The cell markers indicate the monitoring status of the individual CUs.

Item Description

CU CUs not to be monitored.

Number of LDEVs Number of LDEVs in the CU not to be monitored.

Total Total count of CUs.




Monitored CUs table

Item Description

Monitored Target Depicts the monitored target object.

Monitored CUs The table consists of cells representing CUs. One cell corresponds to one CU. Each row consists of 16 cells (CUs). A set of 16 rows represents CUs for one logical DKC (LDKC). The table header row shows the last digit of each CU number in the form of +n (where n is an integer from 0 to 9, or a letter from A to F).

Number of Monitored CUs Total count of monitored CUs.

Monitored CUsCell marker indicating that the CU is being monitored.



Close

Closes this window.

Help


Select by Parity Groups windowUse this window to monitor CUs in the parity group. Use this window when you monitor CUs included in a specific parity group. When you select a parity group and click Detail in this window, you can view the CUs in the parity group. When you select the parity group and click OK, the CUs are selected in the Unmonitored CUs table.

Set Monitored CUsCell marker indicating that the CU is scheduled to be monitored.

Release Monitored CUsCell marker indicating that the CU is scheduled to be released from monitoring.

Item Description



Available Parity Groups table

OK

Click to select CUs of the parity group. When you select a parity group and click OK, CUs of the parity group are selected in the Unmonitored CUs table.

Item Description

Parity Group ID ID of the parity group.

Number of CUs Number of CUs included in the parity group.

Selected N of M N: Number of selected parity groups.M: Total count of parity groups.

Detail Click to display the Parity Group Properties window to view information about the CUs in the selected parity group.



Cancel

Cancels this operation and closes this window.

Help


Parity Group Properties windowUse this window to view information about the CUs in the parity group selected in the previous window.

Parity Group Properties

Item Description

Parity Group ID ID of the parity group.



CUs table

Close

Closes this window.

Help


Edit WWN wizard

Edit WWN windowUse this window to edit the HBA WWN and WWN name of the WWN to be monitored.

HBA WWN

Edit the worldwide name of the host bus adapter. WWNs are 16-digit hexadecimal numbers used to identify host bus adapters.

WWN Name

Edit a WWN name. Use up to 64 alphanumeric characters and some symbols for a WWN name.

Item Description

CU ID of the CU in this parity group.

Number of LDEVs Number of LDEVs included in the individual CUs.

Total Total count of all CUs.



Confirm windowUse this window to confirm the edited HBA WWN and WWN Name and to assign a name to the editing task.

Monitored WWNs table

Confirm the information about the WWNs to be monitored.

Edit WWN Monitor Mode wizard

Edit WWN Monitor Mode windowUse this window to specify WWNs to be monitored or not to be monitored.

Item Description

HBA WWN HBA WWNs to be applied.

WWN Name WWN Names to be applied.

Total Total count of all WWNs.





Unmonitored WWNs table

A table of WWNs that are going to be unmonitored.

Item Description

Port ID Name of the port.

HBA WWN Worldwide name of the host bus adaptor


Current Monitor Mode Monitoring modes indicate whether WWNs are monitoring target objects or not.- Enabled: The WWN is the monitoring target object.- Disabled: The WWN is not the monitoring target object.

Current Status Status of the port connected with WWN.- Normal: All WWNs connected with the port are monitoring target objects.-Non-Integrity: The WWN is not monitored for the corresponding port, but monitored for other ports.




Add

Click to add WWNs to the Monitored WWNs table.

Remove

Click to remove CUs from the Monitored WWNs table.

Monitored WWNs table

A table of WWNs that are going to be unmonitored.

Item Description

Port ID Name of the port.

HBA WWN Worldwide name of the host bus adaptor.


Current Monitor Mode Monitoring modes indicate whether WWNs are monitoring target objects or not.- Enabled: The WWN is the monitoring target object.- Disabled: The WWN is not the monitoring target object.



Confirm windowUse this window to confirm the edited monitoring information.

Current Status Status of the port connected with WWN.- Normal: All WWNs connected with the port are monitoring target objects.-Non-Integrity: The WWN is not monitored for the corresponding port, but monitored for other ports.


Item Description



Selected WWNs to Enable Monitor table

Confirm the information about the WWNs to be monitored.

Selected WWNs to Disable Monitor table

Confirm the information about the WWNs not to be monitored.

Delete Unused WWNs windowUse this window to name the task to delete unused WWNs.

Item Description

Port ID Port name to be monitored.

HBA WWN Worldwide name of the host bus adapter to be monitored.

WWN Name Nickname of WWN to be monitored. The name consists of up to 64 alphanumeric characters and some signs.

Status Status of a WWN to be monitored.- Normal: WWN connected with a port is the monitoring target object.-Non-Integrity: The WWN is not monitored for the corresponding port, but monitored for other ports.

Total Total count of all WWNs

Item Description

Port ID Port name not to be monitored.

HBA WWN Worldwide name of the host bus adapter not to be monitored.

WWN Name Nickname of WWN not to be monitored. The name consists of up to 64 alphanumeric characters and some signs.

Status Status of a WWN not to be monitored.- Normal: The WWN connected with a port is the monitoring target object.-Non-Integrity: The WWN is not monitored for the corresponding port, but monitored for other ports.

Total Total count of all WWNs.



Task Name

Specify the task name.

You can enter up to 32 alphanumeric characters and symbols in all, except for / : , ; * ? ” < > |. The characters are case-sensitive.

“date-window name” is entered as a default.

Add New Monitored WWNs wizard

Add New Monitored WWNs windowUse this window to add new WWNs to be monitored.





HBA WWN

Specify a worldwide name of the host bus adapter. WWNs are 16-digit hexadecimal numbers used to identify host bus adapters.

WWN Name

Specify a worldwide name using up to 64 characters for a WWN name.

Available Ports table

Item Description

Port ID Name of the port available in the storage system.


Number of monitored WWNs in the port.

Number of Unmonitored WWNs:

Number of unmonitored WWNs in the port.




Add

Select a port, then click Add to add the port’s WWNs into the Selected WWNs table.

Selected WWNs table

A list of WWNs to be monitored.

Item Description

Port ID Name of the port selected for monitoring.

HBA WWN WWN selected for monitoring.

WWN Name WWN name is up to 64 alphanumeric characters and some signs.


Remove Select the row to be deleted. Click to remove a row from the table.



Confirm windowUse this window to confirm the new monitoring information.

Selected WWNs table

Confirm the list of combinations of ports and WWNs added as monitoring target objects.

Item Description

Port ID Name of the port selected for monitoring.



Total Total count of all WWNs



Add to Ports wizard

Add to Ports windowUse this window to add a WWN to the port.



HBA WWN

Specify a worldwide name of the host bus adapter. WWNs are 16-digit hexadecimal numbers used to identify host bus adapters.

WWN Name


Available Ports table

A list of available ports in the storage system.

Item Description

Port ID Name of the port available in the storage system.


Number of monitored WWNs in the port.

Number of Unmonitored WWNs

Number of unmonitored WWNs in the port.



Add


Selected WWNs table

A list of WWNs to be monitored.

Selected N of M N: Number of selected Ports.M: Total count of ports.

Item Description

Item Description

Port ID Name of the port selected for monitoring

HBA WWN The WWN selected for monitoring.

WWN Name The WWN name is up to 64 alphanumeric characters and some signs.




Confirm windowUse this window to confirm new WWNs related to ports.

Selected WWNs table

Confirm the information of the WWNs to become the monitoring target objects.

Remove Select the row to be deleted. Click to remove a row from the table.

Item Description

Item Description

Port ID Name of the port selected for monitoring



Monitor windowUse this window to view line graphs of monitored objects.



Total Total counts of all WWNs.

Item Description



Graph panel

Shows line graphs of monitored objects.

Graph display area

Shows graph panels.

Item Description

Graph panel Shows line graphs. The line graph is displayed at the left of the graph panel, and explanatory notes are displayed at the right of the graph panel. Following operations can be performed. • If you locate the mouse cursor to each point of the

graph, a detailed value is displayed with the tool chip.

• When you click the explanatory note on the right of the graph panel, you can display or hide points on the graph panel. However, If the graph is displayed only the one point on X axis, the graph is always displayed. Therefore you cannot switch the display of the point to non-display by clicking the explanatory note.

• Up to 8 graphs can be displayed in one graph panel.

• Line graphs can be displayed up to 16. • Graph panels can be displayed up to 4.

Graph display area Shows graph panels.

Item Description

Vertical Scale: By using the list on the upper left of the graph screen, adjust the scale to display the maximum value of the graph. If the graph is too big, the display may not be able to displaying properly. For example, the line of the graph is too thick, or the graph panel is painted out in the color of the graph.

Edit Performance Objects Opens the Edit Performance Objects window where you can change the objects to be monitored.

Delete Graph Deletes the graph panel.

Item Description

Monitoring Term Shows the monitor period in the bottom left corner of this window. The first monitored time and the latest time are shown. If Use Real Time is selected, the interval is also shown.

Edit Time Range Opens the Edit Time Range window where you can edit the time range for monitoring statistics.

Add Graph Adds a new graph.

Close Closes this window.

Help Opens the help topic for this window.



Edit Time Range windowUse this window to select a date and time range for displaying monitoring data in a performance graph.

Time Range

Specify dates in the From and To fields to define a time range for displaying monitoring data in a performance graph. You can input directly or select from the calender.

When you specify a time range, Performance Monitor calculates the length of the specified period and displays the total time in hours and minutes.

OK

Accepts the time range settings and closes this window.

Cancel


Help


Item Description

From Specify the date and time to start monitoring performance.

To Specify the date and time to stop monitoring performance.



Edit Performance Objects windowUse this window to select the monitoring object for displaying in a performance graph.



Object

Object types to display graphs.The list on the left specifies a large classification of monitoring objects. The list on the right specifies a small classification of monitoring objects.

Monitor Data

Performance data specified in the Object field. The list on the left specifies a large classification of performance data. The list on the right specifies a small classification of performance data.

For the combination of items of Object and Monitor Data fields, see Object and Monitor Data combinations on page B-48.

Performance Object Selection

Objects that can be displayed in graphs.




The columns depend on the object selected. For details, see Available Objects table on page B-53.

Selected N of M:

N: Number of selected WWNs.

M: Total count of WWNs.

Add



Objects to display the graph.



OK

Displays the graph.

Cancel


Help





• If Cache is selected on the left side of the Object field, the item on the right side of the Monitor Data is blank field.


Item Description

Object Object to display the graph.

Monitor Data Type of monitoring data.

Object ID ID of the monitoring object.


Remove Remove the object in this table.




MP Usage Rate %

DRR Usage Rate %



Unit of monitoring

data

None Usage Rate %























WWN Throughput IOPS

Data Trans. MB/s

Response Time ms


Data Trans. MB/s

Response Time ms





Sequential

Random

CFW


Sequential

Random

CFW





Sequential

Random

CFW


Read (Sequential)

Read (Random)

Read (CFW)

Write (Total)

Write (Sequential)

Write (Random)

Write (CFW)


Read

Write


Read

Write


Cache To Drive





Read (Random)

Write (Sequential)

Write (Random)

ShadowImage None %








Sequential

Random

CFW





Sequential

Random

CFW


Sequential

Random

CFW


Read (Sequential)

Read (Random)

Read (CFW)

Write (Total)

Write (Sequential)

Write (Random)

Write (CFW)


Read

Write


Read

Write


Cache To Drive











Sequential

Random

CFW





Sequential

Random

CFW


Sequential

Random

CFW


Read (Sequential)

Read (Random)

Read (CFW)

Write (Total)

Write (Sequential)

Write (Random)

Write (CFW)


Read

Write


Read

Write


Cache To Drive







field



Unit of monitoring

data


Read

Write


Read

Write






Read

Write


Read

Write


field



Unit of monitoring

data
















Add Graph windowUse this window to add the monitoring object to display a graph.

External Storage/Logical Device

LDEV ID ID of the volume, in the following format: LDKC:CU:LDEV.


External Storage/Parity Group

Parity Group ID Parity group ID of the external volume.









Object

Object types to display graphs.The list on the left specifies a large classification of monitoring objects. The list on the right specifies a small classification of monitoring objects.

Monitor Data

Performance data specified in the Object field. The list on the left specifies a large classification of performance data. The list on the right specifies a small classification of performance data.

For the combination of items of Object and Monitor Data fields, see Object and Monitor Data combinations on page B-57.

Performance Object Selection

Objects that can be displayed in graphs.




The columns depend on the object selected. For details, see Available Objects table on page B-62.

Selected N of M

N: Number of selected WWNs.

M: Total count of WWNs.

Add



Objects to display the graph.



OK

Shows the graph.

Cancel


Help





• If Cache is selected on the left side of the Object field, the item on the right side of the Monitor Data is blank field.


Item Description

Object Object to display the graph.

Monitor Data Type of monitoring data.

Object ID ID of the monitoring object.


Remove Remove the object in this table.




MP Usage Rate %

DRR Usage Rate %



Unit of monitoring

data

None Usage Rate %























WWN Throughput IOPS

Data Trans. MB/s

Response Time ms


Data Trans. MB/s

Response Time ms





Sequential

Random

CFW


Sequential

Random

CFW





Sequential

Random

CFW


Read (Sequential)

Read (Random)

Read (CFW)

Write (Total)

Write (Sequential)

Write (Random)

Write (CFW)


Read

Write


Read

Write


Cache To Drive





Read (Random)

Write (Sequential)

Write (Random)

ShadowImage None %








Sequential

Random

CFW





Sequential

Random

CFW


Sequential

Random

CFW


Read (Sequential)

Read (Random)

Read (CFW)

Write (Total)

Write (Sequential)

Write (Random)

Write (CFW)


Read

Write


Read

Write


Cache To Drive











Sequential

Random

CFW





Sequential

Random

CFW


Sequential

Random

CFW


Read (Sequential)

Read (Random)

Read (CFW)

Write (Total)

Write (Sequential)

Write (Random)

Write (CFW)


Read

Write


Read

Write


Cache To Drive







field



Unit of monitoring

data


Read

Write


Read

Write






Read

Write


Read

Write


field



Unit of monitoring

data
















External Storage/Logical Device

LDEV ID ID of the volume, in the following format: LDKC:CU:LDEV.


External Storage/Parity Group

Parity Group ID Parity group ID of the external volume.









Virtual Partition Manager GUI reference C–1


C Virtual Partition Manager GUI

reference

This topic describes the windows that comprise the Virtual Partition Manager GUI.

□ Partition Definition tab (Subsystem selected)

□ Partition Definition tab, Cache Logical Partition window (CLPR selected)

□ Partition Definition tab, Cache Logical Partition window (CLPR information)

□ Select CU dialog box

C–2 Virtual Partition Manager GUI reference


Partition Definition tab (Subsystem selected)Use this tab to view detail about all of the cache logical partitions in the storage system. Information appearing in this tab differs depending on what is selected in the Logical Partition tree.

• When Subsystem is selected, information about the selected storage system appears in the resource list.

• When CLPR is selected, information about cache partition appears in the resource list.

• When a specific CLPR is selected, information about that CLPR appears in the resource list, and the CLPR detail appears below the list.

To access this tab, from the Storage Navigator main window click Go, then Environmental Setting, and then select the Partition Definition tab.

Item Description

Logical Partition tree

A hierarchical list of storage system and cache logical partitions. CLPRs defined in the storage system are indicated by an icon and a unique CLPR number.



Partition Definition tab, Cache Logical Partition window (CLPR selected)

Use this window to view information about all of the cache logical partitions in the storage system. This window opens when you select a CLPR in the Partition Definition tree of the Partition Definition tab.

Resource list Provides information about the item selected in the Logical Partition tree. When Subsystem is selected, the resource list provides the following information: • No.: The storage system resource list number.• Item: The resource type, for example, Storage Partition.• Cache (Num. of CLPRs): The cache capacity, in GM, and

number of cache logical partitions.• Num. of Resources: Number of parity groups.See also: • Partition Definition tab, Cache Logical Partition window (CLPR

selected) on page C-3• Partition Definition tab, Cache Logical Partition window (CLPR

information) on page C-4

Apply Implements the settings made in this window.

Cancel Cancels any settings that were made in this window.

Item Description



Partition Definition tab, Cache Logical Partition window (CLPR information)

The Cache Logical Partition window appears below the resource list when you select a specific CLPR in the Partition Definition tree of the Partition Definition tab. Use this window to view and update CLPR resources. Parity groups, external volume groups, virtual volumes, the cache size, the Cache Residency size and the number of Cache Residency areas are configured to CLPR.

Before changing cache size or cache residency size, please verify that CLPR0 has at least 4 GB remaining after subtracting cache residency size from the cache size.

Item Description

Partition Definition tree

A hierarchical list of the cache logical partitions in the selected storage system. The CLPR identifier, for example CLPR0, appears to the right

of the CLPR icon ( ).

Cache Logical Partition resource list

Information about the CLPR. When a CLPR is selected, the list provides the following information:• No.: Line number.• Resource Type: Resource type, for example, Cache Partition or

Port.• Name: Resource name. If the resource type is Cache Partition,

the CLPR number and CLPR ID appear. • Properties: Capacity, in GB, and number of resources allocated

to the selected CLPR.• Information: Status of the selected CLPR. When the CLPR is

created, Create appears. When the CLPR is deleted, Delete appears.

Apply Implements settings made in this window.

Cancel Cancels any settings made in this window



Item Description

CU Indicates either All CUs or the selected CU number.

Select CU Opens the Select CU dialog box.

Partition Definition tree

A hierarchical list of all of the cache logical partitions in the storage system. The cache logical partition number and name appear to the

right of the CLPR icon ( ).



Cache Logical Partition resource list

When a CLPR is selected in the Partition Definition tree, the Cache Logical Partition resource list show the resource information for the selected CU and CLPR.When CLPR0 is selected in the Cache Logical Partition tree, this list shows all resources not already assigned to other partitions.The resource list provides the following information:• No.: Row number.• Resource Type: Type of CLPR resources. Parity Group or V-VOL

appears in this column.• Address: Resource address.

An address with E (e.g., E1-1) indicates that the parity group contains external volumes.An address with M (e.g., M1-1) indicates that the parity group contains migration volumes.An address with V (e.g., V1-1) indicates that the parity group contains Copy-on-Write Snapshot virtual volumes. An address with X (e.g., X1-1) indicates that the parity group contains Dynamic Provisioning virtual volumes.

• Properties: Properties of the parity group.If a parity group contains internal volumes, the parity group and RAID configuration are shown. If a parity group contains external volumes, the volume capacity is shown, but the RAID configuration is not shown. For virtual volumes (e.g., Copy-on-Write Snapshot or Dynamic Provisioning), the logical volume capacity is shown, but the RAID configuration is not shown.

• Emulation: Emulation type of the resource.

Item Description



Select CU dialog boxUse this dialog box to select how you want CU information to appear on the CLPR resource list. Open the Select CU Dialog box by clicking Select CU on the Cache Logical Partition Window.

Detail For CLPR in Subsystem

When a CLPR is selected in the Partition Definition tree, the CLPR detail appears below the resource list. Use this area to set or change the settings of the specified cache logical partition. You cannot directly change the capacity value of CLPR0. Any changes in the capacity of the other CLPRs are reflected as an opposite change in the capacity of CLPR0.The maximum available cache capacity (installed cache capacity less the cache assigned to other cache logical partitions) is shown for the upper limit of Cache Size, Cache Residency Size, and Num. of Cache Residency Areas. For more information on cache residency, see the Performance Guide.• CLPR Name: Allows you to set or change the name of the cache

logical partition, provided that it is within the selected CU. You can use up to 16 alphanumeric characters.

• Cache Size: Allows you to set or change the cache capacity of each cache logical partition. You may select 4 GB or more up to a maximum size of 508 GB, which is 4 GB smaller than the cache size of the whole storage system. From a default value of 4 GB you may increase the size in 2 GB increments.

• Cache Residency Size: Allows you to set or change the capacity of the Cache Residency cache. You may select nothing (0 GB) to a maximum size of 504 GB, which is the Cache Residency size of the entire storage system. The default value is 0 GB to which you may add capacity in 0.5 GB increments.If you have previously defined cache residency size for this cache logical partition using Cache Residency Manager, the cache residency size selected for this cache logical partition must be greater than that which was previously defined. Please use Cache Residency Manager to verify the size before you set the value for this field).

• Num. of Cache Residency Areas: Allows you to set or change the number of cache residency areas, from 0 to 16,384. The default value is zero (0).If you have previously defined cache residency areas for this cache logical partition using Cache Residency Manager, the number of cache residency areas selected for this cache logical partition must be more than that which was previously defined. Please use Cache Residency Manager to verify the number of areas before you set the value for this field.

Apply Implements settings made in this window.

Cancel Cancels any settings made in this window

Item Description



Item Description

All CUs When selected, information about resources of all CUs appears on the CLPR resource list.

Specific CU When selected, only the information about resources that are associated with the specified CU appears on the CLPR resource list.• Use the LDKC list to specify LDKC.• Use the CU list to specify CU.

Unallocated When selected, only the information about resources that are not assigned with any CU appears on the CLPR resource list.

Set Implements the settings in the storage system.

Cancel Cancels any settings made in this window.

Cache Residency Manager GUI reference D–1


DCache Residency Manager GUI

reference

This topic provides reference information about the Cache Residency Manager GUI.

□ Cache Residency window

□ Multi Set dialog box

□ Multi Release dialog box

D–2 Cache Residency Manager GUI reference


Cache Residency windowThis window provides the Cache Residency Manager information for the connected VSP storage system and provides access to all Cache Residency Manager operations.



Item Description

Prestaging Enables and disables the prestaging function for Cache Residency Manager. If you select the Prestaging check box check box and click Apply, a Yes/No confirmation is displayed. To perform a Cache Residency Manager operation followed by a prestaging operation, click Yes. To perform only the Cache Residency Manager operation, click No.If you clear the Prestaging check box and click Apply, only a Cache Residency Manager operation is performed. If you select this check box later and click Apply, a Yes/No confirmation is displayed. If you click Yes, only the prestaging operation is performed.The Prestaging check box is selected by default. The Prestaging check box is unavailable when the Prestaging Mode is set to No for each cache extent.The Prestaging check box can be selected only when you are logged in to Storage Navigator as a storage administrator.

Tree Lists the LDEVs that are available for Cache Residency Manager operations.The LDEVs are identified by LDKC number, CU number, and LDEV number. For example, LDEV 00:01:48 is LDEV 48 in CU 01 in LDKC 00. An LDEV number ending with # (e.g., 00:00:01#) is an external volume. Only the volumes belonging to the selected CLPR are shown. Volumes that are reserved for Volume Migration and Compatible Hyper PAV alias volumes are not shown, because these volumes are not available for Cache Residency Manager operations.The CU:LDEV Tree uses these icons:

: Indicates an open/expanded folder. An open LDKC folder shows the CUs that belong to that LDKC. An expanded CU folder shows the LDEVs that belong to that CU.

: Indicates an unopened/unexpanded LDKC or CU folder.

:Indicates that the LDEV is an internal volume for which Cache Residency Manager is not set or an external volume whose Cache mode is set to Enable.

: Indicates that the LDEV is an internal volume for which Cache Residency Manager is set or an external volume whose Cache mode is set to Enable.

: Indicates that the LDEV is an external volume where Cache Residency Manager is not set to Disable but Cache mode is set to Disable.

: Indicates that the LDEV is an external volume that has both Cache Residency Manager and Cache mode set to Disable.



LDEV Information table

Items in the LDEV Information table are described in the following table.

CLPR Select the cache logical partition (CLPR) containing the desired CU(s) and LDEV(s).The CLPR is displayed as CLPR-number : CLPR-name. The Cache Residency window then shows the cache information for the selected CLPR and the CUs and volumes belonging to the selected CLPR.If you administer more than one CLPR, use the CLPR list to select a CLPR by name and number. If you administer only one CLPR, the CLPR list shows only the CLPR that you have access to and does not allow you to select other CLPRs.

LDEV ID Provides detailed information and Cache Residency Manager settings for the LDEV selected in the CU:LDEV tree.• LDKC:CU:LDEV: ("#" after the LDEV number

indicates an external volume).• Emulation type:• Volume capacity in MB for open-systems LDEVs,

in cylinders and tracks for mainframe LDEVs• RAID level:

LDEV information The LDEV information table provides detailed information and Cache Residency Manager settings for the LDEV selected in the CU:LDEV tree.LDEV.

Cache information The cache information area provides information on the VSP cache usage. The cache information area also indicates when prestaging operations and cache residency operations are in progress.

Operations Use add data to and release data from Cache Residency Manager cache.

Apply Starts the requested operation(s) with or without prestaging.

Cancel Cancels the requested operation(s) and closes the dialog box.

Item Description

Item Description

LBAs for open-systems LDEVs, CC HH for mainframe LDEVs

Data location on the LDEV indicated by starting and ending addresses. A data location n blue italics indicates a requested operation.

Capacity Capacity of the data stored in Cache Residency Manager cache: MB for open-systems LDEVs, cylinders and tracks for mainframe LDEVs.A capacity in blue italics indicates a requested operation.



Cache Information

Mode Cache Residency Manager cache mode:• PRIO: Priority mode.• BIND: Bind mode.• -: A dash (-) indicates that the area is not allocated for

Cache Residency Manager cache.A cache mode in blue italics indicates a requested operation.

Prestage Setting for the prestaging function:• Blank: Indicates that the prestaging function is not set.• ON: The prestaging function is set.A prestaging mode in blue italics indicates a requested operation.

Available Cache Residency Area in LDEV

Available number of cache extents in the specified LDEV (maximum: 4,096).

Item Description

Item Description

Total Num. of Cache Residency Areas

If you are logged in to Storage Navigator as a storage administrator, this field shows the total number of Cache Residency Manager cache extents that can be set in the selected CU group (maximum: 16,384).

Total Cache Residency Cache Size

If you are logged in to Storage Navigator as a storage administrator, this field shows the total capacity (in MB) of Cache Residency Manager cache extents in the selected CU group (maximum: 512 GB).

Num. of Available Cache Residency Areas

Unused Cache Residency Manager cache area, calculated by subtracting the number of installed Cache Residency Manager cache extents in the CLPR from the maximum number of Cache Residency Manager cache extents (16,384).

Num. of Used Cache Residency Areas

Number of Cache Residency Manager cache extents that are used in the CLPR.

Remaining Cache Residency Size

Amount of Cache Residency Manager cache available for use in the CLPR (pink area on the pie chart).

Used Cache Residency Size

Capacity of Cache Residency Manager cache used in the CLPR (the total of the blue and yellow areas in the pie chart).

Pie chart Blue indicates cache that has been used.Yellow indicates the increase in the specified size of the cache.Pink indicates the remaining amount of available cache.



Operations box

Operation in progress Indicates the operation that is in progress.• Prestaging operation in progress: The progress, in

percentage, of the prestaging operation. The percentage shown in this progress bar does not affect the pie chart nor the values in the Operation box.

• Cache Residency operation in progress: The progress, in percentage, of the Cache Residency Manager operation. The percentage shown in this progress bar does not affect the pie chart nor the values in the Operation box.

Item Description

Item Description

Cache Residency Mode Selects the mode for the data to be added to Cache Residency Manager cache:• Bind: Sets the bind mode. Bind mode is not available

to external volumes whose cache mode is set to Disable (which is the mode that disables the use of the cache when there is an I/O request from the host).

• Priority: Sets priority mode.Once you have requested a Cache Residency Manager operation, the mode options are unavailable. To change the mode for a requested operation, cancel the requested operation and request the operation again with the desired mode selected.

Prestaging Mode Enables or disables the prestaging mode for the requested operation:• Yes: Enables prestaging mode.• No: Disables prestaging mode.The Prestaging Mode options are unavailable when the Prestaging check box is unchecked.Once you have requested a Cache Residency Manager operation, the Prestaging Mode options become unavailable. To change the mode for a requested operation, cancel the requested operation and request the operation again with the desired mode selected.

Start and End Enter the starting and ending addresses for the data to be placed in cache, specified in LBAs for open-systems LDEVs, and in CC HH numbers for mainframe LDEVs.For OPEN-V LUs, logical areas are defined in units of 512 blocks. If you enter 0 or 1 as the starting LBA and a value less than 511 as the ending LBA, Cache Residency Manager automatically changes the ending LBA value to 511.

Select All Area Selects all data areas in the selected LDEV for Cache Residency Manager cache. This check box can be selected only if no data areas in the selected LDEV are assigned to Cache Residency Manager cache. If checked, the starting address and ending address (From and To) fields are cleared.

Available Cache Residency Manager Size

Cache size available for Cache Residency Manager data:• Bind: The available size for bind mode.• Priority: The available size for priority mode.



Multi Set dialog box Use this dialog box to select multiple LDEVs with data that you want to place into Cache Residency Manager cache. The items shown on the Multi Set dialog box reflect the options selected on the Cache Residency window. Only volumes belonging to the selected CLPR are shown.

Multi Set / Release Requests Cache Residency Manager operations for more than one LDEV. When checked, the Multi Set or Multi Release window opens to allow you to set data into or release data from Cache Residency Manager cache for more than one LDEV.When checked, the operation can be applied to multiple LDEVs. When unchecked, the operation is applied to only one LDEV.This feature does not allow you to select and cancel an individual Cache Residency Manager data area specified for an LDEV. You must perform a Release operation to cancel an individual data area.

Set Adds the requested set operation (place data in Cache Residency Manager cache) to the LDEV information table. This button is available when you select a data area that is not in cache in the LDEV table.This button is unavailable when Cache Residency Manager operations to release data from cache have been requested. To enable the Set, either perform the requested release operations, or cancel the requested release operations.

Release Adds the requested release operation (remove data from Cache Residency Manager cache) to the LDEV information table. This button is available when you select a data area that is in cache in the LDEV table.This button is unavailable when Cache Residency Manager operations to set data into cache have been requested. To enable the Release, either perform the requested set operations, or cancel the requested set operations.

Item Description



Item Description

Num. of Available Cache Residency Areas

Number of Cache Residency Manager cache extents that can be created.

Remaining Cache Residency Size

Size of unused Cache Residency Manager caches.

Cache Residency Mode Cache Residency Manager mode (priority or bind) specified by the Cache Residency Mode option on the Cache Residency window.

Prestaging Mode Prestaging mode (yes or no) specified by the Prestaging Mode option on the Cache Residency window.

Range Range of data to be placed into Cache Residency Manager cache. The data range is specified using the Start and End fields on the Cache Residency window. All is displayed if the Select All Area box was checked.

LDKC Selects the LDKC that contains the desired CU and LDEV(s).

CU Selects the CU image that contains the desired LDEV(s). Only CUs owned by the selected CLPR are displayed in the Multi Set dialog box.

LDEV LDEVs in the selected CU image that are available for the Multi Set function. Note that only volumes owned by the CLPR selected from the CLPR list in the Cache Residency window are shown in the LDEV table.

Set Saves the requested Set operations, and closes the dialog box.

Cancel Closes the dialog box without saving the requested operations.



Multi Set LDEV table

Multi Release dialog box Use this dialog box to release Cache Residency Manager data from cache for more than one LDEV. To open this dialog box, In the Cache Residency window, select an LDEV that has all data stored in Cache Residency cache, check the Multi Set/Release box, and then click Release. The Multi Release function applies only to LDEVs that have all data stored in Cache Residency Manager cache. To release individual cache extents, select the cache extents in the LDEV information table and click the Release.

Item Description

LDEV LDEV number. An LDEV number ending with # (e.g., 01#) is an external volume.

Size Size of the LDEV.

Emulation Emulation type of the LDEV.

RAID RAID level of the LDEV. A dash (-) indicates the LDEV is an external volume.

Item Description

LDKC Selects the LDKC containing the desired CU and LDEV(s).

CU Selects the CU image containing the desired LDEV(s). Only CUs owned by the selected CLPR are available.



Multi-Release LDEV table

LDEV LDEVs in the selected CU image that are available for the Multi Release function. Note that only volumes owned by the CLPR selected from the CLPR: list in the Cache Residency window are available

Release Saves the requested Release operations, and closes the dialog box.

Cancel Closes the dialog box without saving the requested operations.

Item Description

Item Description

LDEV LDEV number. An LDEV number ending with # (e.g., 01#) is an external volume.

Emulation Emulation type of the LDEV.

Glossary–1


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

Glossary

This glossary defines the special terms used in this document. Click the letter links below to navigate.

A

access path

A path through which data and commands are transferred within the storage system.

array

Another name for a RAID storage system.

B

back-end director (BED)

The hardware component that controls the transfer of data between the drives and cache. A BED feature consists of a pair of boards. A BED is also referred to as a disk adapter (DKA).

BED

See back-end director (BED).

bind mode

In bind mode the Cache Residency Manager extents are used to hold read and write data for specific extent(s) on volume(s). Data written to the Cache Residency Manager bind area is not destaged to the drives. For bind mode, all targeted read and write data is transferred at host data transfer speed.

Glossary–2



C

cache ESW

Access paths between the cache switch and the cache memory.

cache logical partition (CLPR)

Consists of virtual cache memory that is set up to be allocated to different hosts in contention for cache memory.

capacity

The amount of data storage space available on a physical storage device, usually measured in bytes (MB, GB, TB, etc.).

CCHH

cylinder-cylinder, head-head

CCI

Command Control Interface

CHA ESW

Access paths between channel adapters and the cache switch.

CHA

channel adapter. Another name for a front-end director (FED).

channel adapter (CHA)

Another name for a front-end director. See front-end director (FED).

CHP

channel path; channel processor. The channel processors are the microprocessors on the front-end director features of the Universal Storage Platform V.

CLI

command line interface

CLPR

cache logical partition

command device

A dedicated logical volume used only by Command Control Interface to interface with the storage system. Can be shared by several hosts.

Glossary–3



CRM

Hitachi Cache Residency Manager

CSW

cache switch

CU

control unit

custom volume (CV)

A custom-size volume whose size is defined by the user using Virtual LVI/Virtual LUN.

D

device

A physical or logical unit with a specific function.

disk adapter (DKA)

Another name for back-end director. See back-end director (BED).

disk array

Disk array, or just array, is another name for a RAID storage system.

disk controller (DKC)

The hardware component that manages front-end and back-end storage operations. The term DKC is sometimes used to refer to the entire RAID storage system.

DKA

disk adapter. Another name for a back-end director (BED).

DKA ESW

Access paths between disk adapters and the cache switch.

DKC

disk controller. Can refer to the RAID storage system or the controller components.

DKCMAIN

disk controller main. Refers to the microcode for the RAID storage system.

Glossary–4



DKP

disk processor. Refers to the microprocessors on the back-end director features of the Universal Storage Platform V.

DP

Hitachi Dynamic Provisioning

DP-VOL

Dynamic Provisioning virtual volume. A virtual volume with no memory space used by Dynamic Provisioning.

DRR

data recovery and reconstruction

dynamic provisioning

An approach to managing storage. Instead of “reserving” a fixed amount of storage, it removes capacity from the available pool when data is actually written to disk. Also called thin provisioning.

E

EB

exabyte

ECKD

extended count-key data

emulation

The operation of the Hitachi RAID storage system to emulate the characteristics of a different storage system. For device emulation the mainframe host “sees” the logical devices on the RAID storage system as 3390-x devices. For controller emulation the mainframe host “sees” the control units (CUs) on the RAID storage system as 2105 or 2107 controllers.

RAID storage system operates the same as the storage system being emulated.

external port

A fibre-channel port that is configured to be connected to an external storage system for Universal Volume Manager operations.

ESW

PCI Express Switch adapter.

Glossary–5



Export Tool

Software used to export monitoring data (statistics) shown in the Hitachi Performance Monitor Monitor Performance window to text files.

external volume

A logical volume whose data resides on drives that are physically located outside the Hitachi storage system.

F

FD Dump Tool

Downloads Storage Navigator configuration information onto disk for backup and troubleshooting purposes.

FED

front-end director

front-end director (FED)

The hardware component that processes channel commands from hosts and manages host access to cache. A FED is also referred to as a channel adapter (CHA).

G

GB

gigabyte

GUI

graphical user interface

H

HBA

host bus adapter

HDP

Hitachi Dynamic Provisioning

HDS

Hitachi Data Systems

host group

A group of hosts of the same operating system platform.Also known as a host storage domain.

Glossary–6



host mode

Operational modes that provide enhanced compatibility with supported host platforms. Used with fibre-channel ports on RAID storage systems.

host mode option

Additional options for fibre-channel ports on RAID storage systems. Provide enhanced functionality for host software and middleware.

HUR

Hitachi Universal Replicator

I

IBM

International Business Machines Corporation

initial copy

An initial copy operation is performed when a copy pair is created. Data on the primary volume is copied to the secondary volume.

internal volume

A logical volume whose data resides on drives that are physically located within the storage system. See also external volume.

I/O

input/output

IOPS

I/Os per second

IP

internet protocol

iSNS

internet storage name service

J

JRE

Java Runtime Environment

Glossary–7



K

KB

kilobyte

L

LAN

local-area network

LBA

logical block address

LCP

local control port; link control processor

LDEV

logical device

LDKC

See logical disk controller (LDKC).

license key

A specific set of characters that unlocks an application and allows it to be used.

local copy

See in-system replication.

logical device (LDEV)

An individual logical data volume (on multiple drives in a RAID configuration) in the storage system. An LDEV may or may not contain any data and may or may not be defined to any hosts. Each LDEV has a unique identifier or “address” within the storage system composed of the logical disk controller (LDKC) number, control unit (CU) number, and LDEV number. The LDEV IDs within a storage system do not change.An LDEV formatted for use by mainframe hosts is called a logical volume image (LVI). An LDEV formatted for use by open-system hosts is called a logical unit (LU).

logical disk controller (LDKC)

A group of 255 control unit (CU) images in the RAID storage system that is controlled by a virtual (logical) storage system within the single physical storage system. For example, the Universal Storage Platform V storage system supports two LDKCs, LDKC 00 and LDKC 01.

Glossary–8



logical unit (LU)

A logical volume that is configured for use by open-systems hosts (for example, OPEN-V).

logical unit (LU) path

The path between an open-systems host and a logical unit.

logical volume

See volume.

logical volume image (LVI)

A logical volume that is configured for use by mainframe hosts (for example, 3390-9).

LU

logical unit

LUN

logical unit number

LUSE

Hitachi LUN Expansion; Hitachi LU Size Expansion

LVI

See logical volume image (LVI).

M

MB

megabyte

MF, M/F

mainframe

MHz

megahertz

modify mode

The mode of operation of Storage Navigator that allows changes to the storage system configuration. See also view mode.

MP

microprocessor

Glossary–9



MP blade

Processor blade.

MP blade ESW

Access paths between the MP bland and the cache switch.

monitoring target

An object selected to be monitored using Performance Monitor.

multipathing

A performance and fault-tolerant technique that uses more than one physical connection between the storage system and host system. Also called multipath I/O.

N

NAS

network-attached storage

no.

number

NVS

nonvolatile storage

O

OPEN-x

A logical unit (LU) of fixed size (for example, OPEN-3 or OPEN-9) that is used primarily for sharing data between mainframe and open-systems hosts using Hitachi Cross-OS File Exchange.

OS

operating system

P

pair

Two logical volumes in a replication relationship in which one volume contains original data to be copied and the other volume contains the copy of the original data. The copy operations can be synchronous or asynchronous, and the pair volumes can be located in the same storage system (in-system replication) or in different storage systems (remote replication).

Glossary–10



parity group

See RAID group.

PB

petabyte

PDEV

physical device

prestaging of data

Places specific data in Cache Residency Manager cache before it is accessed by the host. When prestaging is selected, the host locates the prestaged data in the CRM cache from the first access, thus enhancing its access performance.

pool

A set of volumes that are reserved for storing Copy-on-Write Snapshot data or Dynamic Provisioning write data.

pool volume (pool-VOL)

A logical volume that is reserved for storing snapshot data for Copy-on-Write Snapshot operations or write data for Dynamic Provisioning.

POSIX

portable operating system interface for UNIX

primary site

The physical location of the storage system that contains the original data to be replicated and that is connected to one or more storage systems at the remote or secondary site via remote copy connections. A primary site can also be called a “main site” or “local site”.

The term “primary site” is also used for host failover operations. In that case, the primary site is the host computer where the production applications are running, and the secondary site is where the backup applications run when the applications at the primary site fail, or where the primary site itself fails.

prio, priority

priority mode. Used in Cache Residency Manager.

PSUE

Pair suspended-error

PSUS

Pair suspended-split

Glossary–11



P-VOL

Primary volume.

Q

quick format

The quick format feature in Virtual LVI/Virtual LUN in which the formatting of the internal volumes is done in the background. This allows system configuration (such as defining a path or creating a TrueCopy pair) before the formatting is completed. To execute quick formatting, the volumes must be in blocked status.

quick restore

A reverse resynchronization in which no data is actually copied: the primary and secondary volumes are swapped.

R

RAID

redundant array of inexpensive disks

RAID level

The type of RAID implementation. RAID levels include RAID0, RAID1, RAID2, RAID3, RAID4, RAID5 and RAID6.

RCU

See remote control unit (RCU).

remote console PC

A previous term for the personal computer (PC) system that is LAN-connected to a RAID storage system. The current term is Storage Navigator PC.

resync

“Resync” is short for resynchronize.

S

SAN

storage-area network

scripting

The use of command line scripts, or spreadsheets downloaded by Configuration File Loader, to automate storage management operations.

Glossary–12



SCSI

small computer system interface

secondary site

The physical location of the storage system that contains the primary volumes of remote replication pairs at the main or primary site. The storage system at the secondary site is connected to the storage system at the main or primary site via remote copy connections. The secondary site can also be called the “remote site” or “secondary storage system”. See also primary site.

secondary volume (S-VOL)

The volume in a copy pair that is the copy of the original data on the primary volume (P-VOL). The following Hitachi products use the term “secondary volume”: ShadowImage, TrueCopy, Universal Replicator, Universal Replicator for Mainframe, and High Availability Manager.

See also primary volume (P-VOL).

service processor (SVP)

The computer inside a RAID storage system that hosts the Storage Navigator software and is used by service personnel for configuration and maintenance of the storage system.

severity level

Applies to service information messages (SIMs) and Storage Navigator error codes.

SIM

service information message

SM

shared memory

SMPL

simplex

SMTP

simple mail transfer protocol

source volume (S-VOL)

The volume in a copy pair containing the original data that is duplicated on the target volume (T-VOL). The following Hitachi products use the term source volume: ShadowImage for Mainframe, Dataset Replication, IBM FlashCopy.

Glossary–13



SSID

storage subsystem ID. SSIDs are used for reporting information from the CU to the mainframe operating system. Each group of 64 or 256 volumes requires one SSID, so there are one or four SSIDs per CU image. The user-specified SSIDs are assigned during storage system installation and must be unique to all connected host operating environments.

S-VOL

See secondary volume (S-VOL) or source volume (S-VOL).

SVP

See service processor (SVP).

sync

synchronous

T

TB

terabyte

throughput (of storage system)

Total throughput is the sum of I/Os to LDEVs, parity groups, or LUNs. Read throughput is I/Os to the disk per second when the file read processing is performed. Write throughput is I/Os to the disk per second when the file write processing is performed.

In Performance Monitor, throughputs in the following modes can be displayed. - Sequential access mode - Random access mode - CFW (cache fast write) mode - Total value in the above-mentioned mode

total capacity

The aggregate amount of storage space in a data storage system.

V

VDEV

See virtual device (VDEV).

view mode

The mode of operation of Storage Navigator that allows viewing only of the storage system configuration. The two Storage Navigator modes are view mode and modify mode.

Glossary–14



virtual device (VDEV)

A group of logical devices (LDEVs) in a RAID group. A VDEV typically consists of some fixed volumes (FVs) and some free space. The number of fixed volumes is determined by the RAID level and device emulation type.

virtual volume (V-VOL)

The secondary volume in a Copy-on-Write Snapshot pair. When in PAIR status, the V-VOL is an up-to-date virtual copy of the primary volume (P-VOL). When in SPLIT status, the V-VOL points to data in the P-VOL and to replaced data in the pool, maintaining the point-in-time copy of the P-VOL at the time of the split operation.

When a V-VOL is used with Dynamic Provisioning, it is called a DP-VOL.

VOL, vol

volume

volume

A logical device (LDEV), or a set of concatenated LDEVs in the case of LUSE, that has been defined to one or more hosts as a single data storage unit. A mainframe volume is called a logical volume image (LVI), and an open-systems volume is called a logical unit. (LU).

VSP

Hitachi Virtual Storage Platform

V-VOL

virtual volume

Index-1


Index

Aaccess paths and I/O usage rates 8–6

Bback-end performance and I/O usage rates 8–13batch file

preparing for use with Export Tool A–9running for Export Tool A–10using termination codes in Export Tool A–12

bind mode 2–4and cache size requirements 11–2

Ccache

area 1–2capacity recommendations 10–3extents 11–5hit rates and I/O usage rates 8–11managing 12–1memory and I/O usage rates 8–5partitioning 10–1partitioning example 10–2partitions 10–2placing LDEVs into cache 12–7placing specific data into cache 12–5releasing LDEVs from cache 12–9releasing specific data from cache 12–9rules, restrictions, and guidelines 12–2

cache requirementsbind mode 2–4priority mode 2–3

Cache Residency Manager 1–2cache extents 11–5cache requirements 11–1system requirements 11–6

Cache Residency window D–2cache size

estimating 11–1requirements 11–2requirements, calculating for mainframe

systems 11–4

requirements, calculating for open systems 11–2

CLPRcreating 10–6

CLPRscreating 10–5, 10–6deleting 10–8migrating resources 10–7restrictions 10–4

command filepreparing for use with Export Tool A–6

command referenceExport Tool A–14

creating a CLPR 10–6CUs

add to monitoring 4–2and parity groups 4–2remove from monitoring 4–2set up monitoring 4–1viewing 4–2viewing monitoring status 4–3

Ddata prestaging 2–2data recovery and reconstruction processor and I/

O usage rates 8–5data transfer size and I/O usage rates 8–9deleting a CLPR 10–6, 10–8

Eerror handling

Export Tool A–13Export Tool A–1

commands A–14error handling A–13file formats A–11installing on UNIX systems A–2installing on Windows systems A–3limitations A–3log files A–13overview A–2processing time A–11

Index-2


requirements A–3text files A–2uninstalling on a UNIX system A–5uninstalling on a Windows system A–5using A–10

extents 11–5external vollumes and cache size

requirements 11–2

Ggraphs 8–1

adding new graph panel 9–3changing displayed objects 9–2changing displayed period 9–2configuring 9–1creating and viewing 8–2deleting graph panel 9–3display parameters 9–2objects and data than can be graphed 8–3

Hhard disk drive access rates 8–14hard disk drive and I/O usage rates 8–14

II/O usage rates

access paths 8–6back-end performance 8–13cache hit rates 8–11cache memory 8–5data recovery and reconstruction

processor 8–5data transfer size 8–9hard disk drive 8–14hard disk drive access 8–14processor blades 8–4ShadowImage 8–15throughput 8–7write pending 8–6

interleaved parity groups, in CLPRs 10–7interoperability

Performance Monitor with other software 3–1

LLDEVs

placing into cache 12–7releasing from cache 12–9

log filesExport Tool A–13

long range 7–2

Mmainframe systems

calculating cache requirements 11–4managing resident cache 12–1microprogram replacement and monitoring data

retention 3–3

migrating resources 10–7modes

bind 2–4changing after Cache Residency is registerd in

cache 12–11priority 2–3

Monitor Performance window 3–2monitoring

starting 6–2stopping 6–2

monitoring dataviewing 3–3

Oopen systems

calculating cache requirements 11–2OPEN-V LUs 12–6operations not allowed with multiple CLPRs

restrictions 10–4

Ppartitioning cache 10–1Performance Monitor 1–2performance troubleshooting 13–1placing LDEVs into cache 12–7placing specific data into cache 12–5power off 3–2prestaging data 2–2priority mode 2–3

and cache size requirements 11–2processor blades and I/O usage rates 8–4

RRAID levels and cache size requirements 11–2releasing LDEVs from cache 12–9releasing specific data from cache 12–9replace microprogram 3–3resident cache

managing 12–1resource availability 2–2restrictions

operations not allowed with multiple CLPRs 10–4

ShadowImage quick restore operations across multiple CLPRs 10–5

Volume Migration manual migration across multiple CLPRs 10–5

SShadowImage

I/O usage rates 8–15restrictions on quick restore operations across

multiple CLPRs 10–5short range 7–2starting monitoring 6–2statistics 7–1

setting storing period 7–2storage ranges 7–2

Index-3


viewing 7–2stopping monitoring 6–2

Tthroughput and I/O usage rates 8–7troubleshooting

performance 13–1Virtual Partition Manager 10–8

Vviewing monitoring data 3–3virtual cache partitions 10–2Volume Migration

restrictions on manual migration across multiple CLPRs 10–5

Wwrite pending and I/O usage rates 8–6WWNs

adding to monitoring 5–2connecting to ports 5–4editing nickname 5–3removing from monitoring 5–2, 5–4setting up monitoring 5–1viewing 5–2

Index-4


1


MK-90RD7020-00

Hitachi Data Systems

Corporate Headquarters750 Central ExpresswaySanta Clara, California 95050-2627U.S.A.Phone: 1 408 970 [email protected]

Asia Pacific and Americas750 Central ExpresswaySanta Clara, California 95050-2627U.S.A.Phone: 1 408 970 [email protected]

Europe HeadquartersSefton ParkStoke PogesBuckinghamshire SL2 4HDUnited KingdomPhone: + 44 (0)1753 [email protected]

Documents

VSP PerformanceGuide