Hitachi Virtual Storage Platform G200, G400, G600, G800

Hitachi Virtual Storage Platform

G200,

G400, G600, G800

Performance Guide

Product Version

Getting Help

Contents

MK-94HM8012-01

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

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

Some of the features described in this document might not be currently available. Refer to the most recent product announcement for information about feature and product availability, or contact

Hitachi Data Systems Corporation at https://portal.hds.com

.

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

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.

Archivas, Essential NAS Platform, Hi-Track, ShadowImage, Tagmaserve, Tagmasoft, Tagmasolve,

Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform are registered trademarks of Hitachi Data Systems Corporation.

AIX, AS/400, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, ESCON, FICON,

FlashCopy, IBM, Lotus, MVS, OS/390, RS/6000, S/390, System z9, System z10, Tivoli, VM/ESA, z/OS, z9, z10, zSeries, z/VM, and z/VSE are registered trademarks or trademarks of International

Business Machines Corporation.

All other trademarks, service marks, and company names in this document or website are properties of their respective owners.

Microsoft product screen shots reprinted with permission from Microsoft Corporation.

Notice on Export Controls. The technical data and technology inherent in this Document may be subject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Reader agrees to comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain licenses to export, re-export, or import the Document and any Compliant Products.

ii

Hitachi Virtual Storage Platform G200, G400, G600, G800 Performance Guide

Contents

Preface.................................................................................................. ix

Intended audience..................................................................................................... x

Product version..........................................................................................................x

Release notes............................................................................................................ x

Changes in this revision..............................................................................................x

Referenced documents...............................................................................................x

Document conventions.............................................................................................. xi

Convention for storage capacity values...................................................................... xii

Accessing product documentation............................................................................. xiii

Getting help............................................................................................................ xiii

Comments...............................................................................................................xiii

1 Performance management.................................................................... 1-1

Overview of performance management.................................................................... 1-2

System requirements.............................................................................................. 1-2

2 Hitachi Performance Monitor operations................................................. 2-1

Overview of Hitachi Performance Monitor................................................................. 2-2

Data collected by Performance Monitor.............................................................. 2-2

Sampling interval for monitoring........................................................................ 2-2

Maximum storing period for monitoring..............................................................2-3

Performance Monitor data graphs...................................................................... 2-3

Export Tool for Performance Monitor..................................................................2-3

Cautions and restrictions for Performance Monitor.....................................................2-3

Cautions and restrictions for monitoring............................................................. 2-4

Cautions and restrictions for usage statistics.......................................................2-5

Performance monitoring workflow............................................................................2-6

Setting the storing period for the monitoring data..................................................... 2-6

Starting monitoring................................................................................................. 2-7

Monitoring WWNs................................................................................................... 2-8

Adding new WWNs to monitor...........................................................................2-8

Viewing the WWNs that are being monitored......................................................2-9

Removing WWNs to monitor..............................................................................2-9

Adding WWNs to ports.................................................................................... 2-10

Editing the WWN nickname............................................................................. 2-11

iii


Connecting WWNs to ports..............................................................................2-12

Deleting unused WWNs from monitoring targets............................................... 2-13

Monitoring CUs..................................................................................................... 2-13

Displaying CUs to monitor............................................................................... 2-14

Adding and removing CUs to monitor............................................................... 2-14

Selecting CUs to monitor................................................................................. 2-15

Confirming the status of CUs to monitor .......................................................... 2-16

Changing the sampling interval.............................................................................. 2-17

Stopping monitoring..............................................................................................2-18

Using the Performance Monitor data graphs............................................................2-18

About the data graphs.................................................................................... 2-19

Displaying the monitor data on graphs............................................................. 2-19

Adding a new graph........................................................................................2-20

Changing the data displayed on a graph...........................................................2-21

Changing the time period displayed on the graph panel.....................................2-22

Deleting a graph.............................................................................................2-23

3 Hitachi Performance Monitor data.......................................................... 3-1

Monitoring data ..................................................................................................... 3-3

Usage rates of MPs ................................................................................................ 3-7

Usage rate of cache memory................................................................................... 3-7

Write pending rates................................................................................................ 3-8

Storage system throughput..................................................................................... 3-8

Data transfer rate................................................................................................. 3-10

Response times.....................................................................................................3-12

Cache hit rates......................................................................................................3-13

Back-end performance.......................................................................................... 3-15

Drive usage rates..................................................................................................3-16

Data drive access rates..........................................................................................3-17

ShadowImage usage statistics............................................................................... 3-17

Remote I/O (RIO)................................................................................................. 3-18

Pair Synchronized..................................................................................................3-19

Differential Track.................................................................................................. 3-19

Number of Journals...............................................................................................3-20

Data Usage Rate...................................................................................................3-20

Meta Data Usage Rate...........................................................................................3-21

4 Exporting Performance Monitor data...................................................... 4-1

About the Export Tool............................................................................................. 4-2

Preparing to use the Export Tool..............................................................................4-2

Requirements for the Export Tool...................................................................... 4-2

Installing the Export Tool.................................................................................. 4-4

On Windows........................................................................................... 4-4

On UNIX.................................................................................................4-4

Using the Export Tool..............................................................................................4-4

Preparing a command file..................................................................................4-5

Preparing the batch file.....................................................................................4-8

Using the Export Tool....................................................................................... 4-9

Running the batch file............................................................................. 4-9

File formats...........................................................................................4-10

Processing time.....................................................................................4-10

iv


Termination code.................................................................................. 4-11

Log files................................................................................................4-12

Error handling....................................................................................... 4-12

Export Tool command reference.............................................................................4-13

Export Tool command syntax...........................................................................4-13

Subcommand list............................................................................................ 4-15 ip...................................................................................................................4-15

dkcsn.............................................................................................................4-16

retry.............................................................................................................. 4-17

login.............................................................................................................. 4-18 show..............................................................................................................4-18

group.............................................................................................................4-19

range.............................................................................................................4-30

outpath..........................................................................................................4-33

option............................................................................................................4-34 apply............................................................................................................. 4-34

set.................................................................................................................4-35

help...............................................................................................................4-36

Java...............................................................................................................4-37

Exported files........................................................................................................4-39

Monitoring data exported by the Export Tool.................................................... 4-39

Resource usage and write-pending rate statistics.............................................. 4-41

Parity group and external volume group statistics..............................................4-43

Statistics for volumes in parity/external volume groups......................................4-44

Volumes in parity groups or external volume groups (volumes controlled by a particular CU)................................................................................................. 4-46

Port statistics..................................................................................................4-47

Host bus adapters connected to ports statistics.................................................4-48

Volumes (LU) statistics....................................................................................4-48

All host bus adapters connected to ports.......................................................... 4-49

Remote copy operations by TC or GAD (whole volumes)....................................4-50

Remote copy operations by TC or GAD (for each volume (LU)).......................... 4-51

Remote copy by TC or GAD (volumes controlled by a particular CU)................... 4-52

Remote copy by UR (whole volumes)............................................................... 4-53

Remote copy by UR (journals)......................................................................... 4-54

Remote copy by UR (for each volume (LU))......................................................4-55

Remote copy by UR (volumes controlled by a particular CU).............................. 4-56

Causes of Invalid Monitoring Data.......................................................................... 4-56

5 Server Priority Manager operations........................................................ 5-1

Overview of Server Priority Manager........................................................................ 5-2

Performance of high-priority hosts..................................................................... 5-2

Upper-limit control............................................................................................5-2

Threshold control............................................................................................. 5-3

About I/O rates and transfer rates (traffic)......................................................... 5-3

Use cases for Server Priority Manager...................................................................... 5-5

Use case for one-to-one connections..................................................................5-5

Use case for many-to-many connections............................................................ 5-7

Cautions and restrictions for Server Priority Manager............................................... 5-11

Implementing Server Priority Manager: one-to-one connections............................... 5-12

Server Priority Manager workflow: one-to-one connections................................ 5-12

Setting priority for ports: one-to-one connections..............................................5-13

v


Analyzing traffic statistics: one-to-one connections............................................5-14

Setting upper-limit values for non-prioritized ports: one-to-one connections........5-15

Setting a threshold: one-to-one connections..................................................... 5-17

Implementing Server Priority Manager: many-to-many connections.......................... 5-19

Server Priority Manager workflow: many-to-many connections...........................5-19

Setting priority for WWNs: many-to-many connections...................................... 5-20

Monitoring all port-HBA traffic: many-to-many connections................................5-22

Excluding traffic between an HBA and a port from the monitoring target: many-to-many connections.................................................................... 5-24

Analyzing traffic statistics: many-to-many connections.......................................5-25

Setting upper-limit values for non-prioritized WWNs: many-to-many connections 5-27

Setting a threshold for the entire storage system: many-to-many connections.... 5-29

Managing host bus adapters.................................................................................. 5-30

Changing the SPM name of a host bus adapter................................................. 5-30

Replacing a host bus adapter...........................................................................5-32

Working with SPM groups......................................................................................5-34

Creating an SPM group....................................................................................5-34

Deleting an HBA from an SPM group................................................................ 5-35

Switching priority of an SPM group...................................................................5-36

Setting an upper-limit value to HBAs in an SPM group....................................... 5-37

Renaming an SPM group................................................................................. 5-39

Deleting an SPM group....................................................................................5-40

6 Hitachi Virtual Partition Manager operations............................................6-1

Overview of Virtual Partition Manager.......................................................................6-2

CLPR names.....................................................................................................6-2

Use case for cache logical partitioning...................................................................... 6-3

Cache partitioning workflow.....................................................................................6-3

Cautions and restrictions for Virtual Partition Manager............................................... 6-4

Calculating cache capacity....................................................................................... 6-5

Recommended Cache capacity without Dynamic Provisioning, Dynamic Tiering, or active flash ..................................................................................................6-5

Recommended Cache capacity with Dynamic Provisioning, Dynamic Tiering, or active flash

..................................................................................................... 6-6

Recommended Cache capacity with Universal Volume Manager........................... 6-7

Managing CLPRs..................................................................................................... 6-7

Creating a CLPR............................................................................................... 6-7

Migrating resources to and from a CLPR.............................................................6-9

Editing the settings of an existing CLPR............................................................6-10

Deleting a CLPR..............................................................................................6-11

7 Troubleshooting....................................................................................7-1

General troubleshooting resources........................................................................... 7-2

Troubleshooting Performance Monitor...................................................................... 7-2

Troubleshooting the Export Tool for Performance Monitor..........................................7-2

Messages issued by the Export tool....................................................................7-4

Troubleshooting Server Priority Manager.................................................................. 7-7

Troubleshooting Virtual Partition Manager................................................................ 7-7

Calling Hitachi Data Systems customer support ........................................................ 7-7

vi


A Performance Monitor GUI reference.......................................................A-1

Performance Monitor main window.......................................................................... A-3

Edit Monitoring Switch wizard..................................................................................A-5

Edit Monitoring Switch window.......................................................................... A-6

Confirm window for Edit Monitoring Switch.........................................................A-6

Monitor Performance window.................................................................................. A-7

Edit CU Monitor Mode wizard................................................................................. A-21

Edit CU Monitor Mode window......................................................................... A-21

Confirm window for Edit CU Monitor Mode........................................................A-25

View CU Matrix window.........................................................................................A-26

Select by Parity Groups window............................................................................. A-28

Parity Group Properties window............................................................................. A-30

Edit WWN wizard..................................................................................................A-31

Edit WWN window.......................................................................................... A-31

Confirm window for Edit WWN.........................................................................A-32

Edit WWN Monitor Mode wizard............................................................................. A-33

Edit WWN Monitor Mode window..................................................................... A-33

Confirm window for Edit WWN Monitor Mode....................................................A-36

Delete Unused WWNs window............................................................................... A-37

Add New Monitored WWNs wizard......................................................................... A-38

Add New Monitored WWNs window................................................................. A-38

Confirm window for Add New Monitored WWNs................................................A-42

Add to Ports wizard...............................................................................................A-42

Add to Ports window.......................................................................................A-43

Confirm window for Add to Ports..................................................................... A-46

Monitor window.................................................................................................... A-46

Edit Time Range window....................................................................................... A-48

Edit Performance Objects window.......................................................................... A-49

Add Graph window................................................................................................A-63

Wizard buttons..................................................................................................... A-76

Navigation buttons................................................................................................A-76

B Server Priority Manager GUI reference................................................... B-1

Server Priority Manager window...............................................................................B-2

Port tab of the Server Priority Manager main window................................................ B-3

WWN tab of the Server Priority Manager main window.............................................. B-6

Add WWN window................................................................................................ B-11

Change WWN and SPM Name window....................................................................B-12

Add New SPM Group window.................................................................................B-12

Change Upper Limit window.................................................................................. B-13

Rename SPM Group window.................................................................................. B-13

C Virtual Partition Manager GUI reference................................................. C-1

Cache Partition window...........................................................................................C-2

Individual CLPR window.......................................................................................... C-3

Create CLPRs wizard............................................................................................... C-6

Create CLPRs window....................................................................................... C-6

Confirm window for Create CLPRs......................................................................C-7

Migrate CLPR Resources wizard............................................................................... C-9

Migrate CLPR Resources window....................................................................... C-9

Confirm window for Migrate CLPR Resources.................................................... C-10

vii


Edit CLPR wizard...................................................................................................C-12

Edit CLPR window...........................................................................................C-12

Confirm window for Edit CLPR......................................................................... C-13

Change Settings window....................................................................................... C-14

CLPR Properties window........................................................................................C-15

Delete CLPRs window............................................................................................C-16

Index

viii


Preface

This document describes and provides instructions for monitoring and managing the performance of the Hitachi Virtual Storage Platform G200,

G400, G600, G800 (VSP G200, G400, G600, G800) storage system using the following licensed software products: Hitachi Performance Monitor, Hitachi

Server Priority Manager, Hitachi Virtual Partition Manager.

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

□

Intended audience

□

Product version

□

Release notes

□

Changes in this revision

□

Referenced documents

□

Document conventions

□

Convention for storage capacity values

□

Accessing product documentation

□

Getting help

□

Comments

Preface

Hitachi Virtual Storage Platform G200, G400, G600, G800 Performance Guide ix

Intended audience

This document is intended for system administrators and Hitachi Data

Systems representatives and authorized service providers who install, configure, and operate the Hitachi Virtual Storage Platform G200, G400,

G600, G800 storage system.

Readers of this document should be familiar with the following:

• Data processing and RAID storage systems and their basic functions.

• The Hitachi Virtual Storage Platform G200, G400, G600, G800 storage system and the Hardware Reference Guide for your storage system model.

• The Hitachi Command Suite software and the Hitachi Command Suite

User Guide or the Hitachi Device Manager - Storage Navigator software and the Hitachi Virtual Storage Platform G200, G400, G600, G800 System

Administrator Guide.

Product version

This document revision applies to Hitachi Virtual Storage Platform G200,

G400, G600, G800 firmware 83-01-2x or later.

Release notes

The Hitachi Virtual Storage Platform G200, G400, G600, G800 Release Notes are available on the Hitachi Data Systems Portal: https://portal.hds.com

.

Read the release notes before installing and using this product. They may contain requirements or restrictions that are not fully described in this document or updates or corrections to this document.

Changes in this revision

• Added information about monitor data for global-active device.

•

Added information about monitor data for iSCSI initiator ports ( Monitoring data on page 3-3

, Storage system throughput on page 3-8 ,

Data transfer rate on page 3-10 ,

Response times on page 3-12

).

Referenced documents

•

Hitachi Virtual Storage Platform G200, G400, G600, G800 Provisioning

Guide, MK-94HM8014

•

Hitachi Virtual Storage Platform G200, G400, G600, G800 System

Administrator Guide, MK-94HM8016

• Hitachi Device Manager - Storage Navigator Messages, MK-94HM8017

• Hitachi TrueCopy® User Guide, MK-94HM8019 x

Preface


• Hitachi Virtual Storage Platform G200 Hardware Reference Guide,

MK-94HM8020

• Hitachi ShadowImage® User Guide, MK-94HM8021

• Hitachi Virtual Storage Platform G400, G600 Hardware Reference Guide,

MK-94HM8022

• Hitachi Universal Replicator User Guide, MK-94HM8023

• Hitachi Universal Volume Manager User Guide, MK-94HM8024

• Global-Active Device User Guide, MK-92RD8072

• Hitachi Command Suite User Guide, MK-90HC172

• Hitachi Virtual Storage Platform G800 Hardware Reference Guide,

MK-94HM8026

Document conventions

This document uses the following terminology conventions:

Convention

Hitachi Virtual

Storage Platform

G200, G400, G600,

G800

Description

Refers to all models of the Hitachi Virtual Storage Platform G200,

G400, G600, G800 storage systems, unless otherwise noted.

This document uses the following typographic conventions:

Convention Description

Regular text bold

Italic

Screen text

In text: keyboard key, parameter name, property name, hardware label, hardware button, hardware switch

In a procedure: user interface item

Variable, emphasis, reference to document title, called-out term

Command name and option, drive name, file name, folder name, directory name, code, file content, system and application output, user input

< > (angle brackets) Variable (used when italic is not enough to identify variable)

[ ] (square brackets) Optional value

{ } (braces)

| (vertical bar)

Required or expected value

Choice between two or more options or arguments

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

Icon

Tip

Meaning Description

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

Preface

Hitachi Virtual Storage Platform G200, G400, G600, G800 Performance Guide xi

Icon Meaning

Note

Caution

WARNING

Description

Provides information that is essential to the completion of a task.

Warns that failure to take or avoid a specified action can result in adverse conditions or consequences (for example, loss of access to data).

Warns the user of severe conditions, consequences, or both

(for example, destructive operations).

Convention for storage capacity values

Physical storage capacity values (for example, disk drive capacity) are calculated based on the following values:

Physical capacity unit

1 KB

1 MB

1 GB

1 TB

1 PB

1 EB

Value

1,000 bytes

1,000 KB or 1,000

2

bytes

1,000 MB or 1,000

3

bytes

1,000 GB or 1,000

4

bytes

1,000 TB or 1,000

5

bytes

1,000 PB or 1,000

6

bytes

Logical storage capacity values (for example, logical device capacity) are calculated based on the following values:

1 block

1 KB

1 MB

1 GB

1 TB

1 PB

1 EB

Logical capacity unit Value

512 bytes

1,024 bytes

1,024 KB or 1,024

2

bytes

1,024 MB or 1,024

3

bytes

1,024 GB or 1,024

4

bytes

1,024 TB or 1,024

5

bytes

1,024 PB or 1,024

6

bytes xii

Preface


Accessing product documentation

Product documentation is available on Hitachi Data Systems Support

Connect: https://support.hds.com/en_us/documents.html

. Check this site for the most current documentation, including important updates that may have been made after the release of the product.

Getting help

Hitachi Data Systems Support Connect

is the destination for technical support of products and solutions sold by Hitachi Data Systems. To contact technical support, log on to Hitachi Data Systems Support Connect for contact information: https://support.hds.com/en-us/contact-us.html

Hitachi Data Systems Community

is a new global online community for

HDS customers, partners, independent software vendors, employees, and prospects. It is the destination to get answers, discover insights, and make connections. Join the conversation today! Go to community.hds.com

, register, and complete your profile.

Comments

Please send us your comments on this document: [email protected]

.

Include the document title and number, including the revision level (for example, -07), and refer to specific sections and paragraphs whenever possible. All comments become the property of Hitachi Data Systems

Corporation.

Thank you!

Preface

Hitachi Virtual Storage Platform G200, G400, G600, G800 Performance Guide xiii

xiv

Preface


1

Performance management

This chapter provides an overview of performance management of the Hitachi

Virtual Storage Platform G200, G400, G600, G800 storage system and describes the system requirements.

□

Overview of performance management

□

System requirements

Performance management


1-1

Overview of performance management

The Virtual Storage Platform G200, G400, G600, G800 storage system includes a suite of performance management software products that allow you to monitor and tune storage system performance to improve and optimize storage utilization and storage system performance.

• Hitachi Performance Monitor. Performance Monitor allows you to collect and analyze detailed performance and usage statistics for the

Hitachi Virtual Storage Platform G200, G400, G600, G800 storage system as well as statistics about workloads on drives and traffic between the hosts and the storage system. You can view the data in lists and on graphs, and you can export the data for analysis in spreadsheet and other applications.

• Hitachi Server Priority Manager. Server Priority Manager enables you to control port activity to provide high-priority hosts with relatively higher throughput and prevent production servers from experiencing degraded performance. Server Priority Manager monitors the data being collected by Performance Monitor and applies upper-limit control and threshold control according to user-specified settings.

• Hitachi Virtual Partition Manager. Virtual Partition Manager enables you to configure logical cache partitions on the Hitachi Virtual Storage

Platform G200, G400, G600, G800. These cache partitions help to maintain performance for high-priority activities by acting as dedicated storage resources that are independently managed and reserved for specific applications.

Performance management operations can be performed using the Hitachi

Command Suite software and the Command Control Interface software for the Hitachi Virtual Storage Platform G200, G400, G600, G800. For details about Command Control Interface, see the Command Control Interface User

and Reference Guide.

System requirements

• Performance management products. The performance management software products for the Hitachi Virtual Storage Platform G200, G400,

G600, G800 are required for performance management operations.

¢

Hitachi Performance Monitor

¢

¢

Hitachi Server Priority Manager

Hitachi Virtual Partition Manager

• Administrator or write access. Administrator access for Hitachi

Command Suite or write access for the performance management software products is required to perform operations. Users without

Administrator or write access can only view the performance management information and settings.

• License keys. The license keys for the performance management software products must be installed. For details about installing license

1-2



keys, see the Hitachi Virtual Storage Platform G200, G400, G600, G800

System Administrator Guide.

•

Hitachi Device Manager - Storage Navigator secondary window.

You must enable the Hitachi Device Manager - Storage Navigator secondary window before you use Server Priority Manager. For details and instructions, see the Hitachi Virtual Storage Platform G200, G400, G600,

G800 System Administrator Guide.

• Cache memory for Virtual Partition Manager. Use of Virtual Partition

Manager may require installation of additional cache memory in the storage system.



1-3

1-4



2

Hitachi Performance Monitor operations

This chapter describes performance monitoring and provides instructions for performing performance monitoring operations using Hitachi Performance

Monitor.

□

Overview of Hitachi Performance Monitor

□

Cautions and restrictions for Performance Monitor

□

Performance monitoring workflow

□

Setting the storing period for the monitoring data

□

Starting monitoring

□

Monitoring WWNs

□

Monitoring CUs

□

Changing the sampling interval

□

Stopping monitoring

□

Using the Performance Monitor data graphs

Hitachi Performance Monitor operations


2-1

Overview of Hitachi Performance Monitor

Hitachi Performance Monitor enables you to monitor your Hitachi Virtual

Storage Platform G200, G400, G600, G800 storage system and collect detailed usage and performance statistics. You can view the data in lists and on graphs to identify changes in usage rates and workloads, analyze trends in disk I/O, and detect peak I/O times. For example, if there is a decrease in performance, such as delayed host response times, you can use Performance

Monitor to discover the reason for the decrease and determine the actions to take to improve performance.

Performance Monitor collects data about storage system resources such as drives, volumes, and microprocessors as well as statistics about front-end

(host I/O) and back-end (drive I/O) workloads. Data is collected when the

Monitoring Switch is set to Enable, and you specify when and how often the data is collected. Using the Performance Monitor data you can manage and fine-tune the performance of your storage system using the performance management software products for the Hitachi Virtual Storage Platform G200,

G400, G600, G800 storage system.

•

Data collected by Performance Monitor on page 2-2

•

Sampling interval for monitoring on page 2-2

•

Performance Monitor data graphs on page 2-3

•

Export Tool for Performance Monitor on page 2-3

Data collected by Performance Monitor

Performance Monitor allows you to collect the performance and usage statistics for the Hitachi Virtual Storage Platform G200, G400, G600, G800 storage system. All statistics are available for monitoring.

When you monitor the storage system, you control when the statistics are collected (in real time or during a specified period of time) and how often the statistics are collected (from once per minute to once every 15 minutes).

•

Monitoring data on page 3-3

•

Sampling interval for monitoring on page 2-2

•

Maximum storing period for monitoring on page 2-3

Sampling interval for monitoring

The sampling interval is the length of time between data collection events for monitoring. The number of CUs to be monitored determines the options for setting the sampling interval:

• Up to 32 CUs. If there are 32 or fewer CUs to be monitored, you can set the sampling interval from 1 to 15 minutes in increments of 1 minute. For example, when the sampling interval is set to 3 minutes, Performance

Monitor collects statistics once every 3 minutes.

¢

Performance Monitor collects statistics for 1 day when data is collected at 1-minute intervals.

2-2



¢

Performance Monitor collects statistics for up to 15 days when data is collected at 15-minute intervals.

Maximum storing period for monitoring

For a specified sampling interval, the SVP can store a maximum of 1440 data collection events. Based on this number and the sampling interval, you can calculate the maximum storing period for the statistics as the sampling interval multiplied by 1440. For example, if you set the sampling interval to 1 minute, the maximum storing period for the statistics is 1 day (24 hours):

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

If you set the sampling interval to 15 minutes, the maximum storing period for the statistics is 15 days:

15 minutes x 1440 = 21600 minutes = 360 hours = 15 days

This maximum storing period is the maximum range of display in the Monitor

Performance windows. When you specify 1 minute for the sampling interval as in the example above, Performance Monitor displays the statistics for a maximum of 1 day (24 hours) in the lists and graphs. When you specify 15 minutes for the sampling interval, Performance Monitor displays the statistics for a maximum of 15 days in the lists and graphs.

Performance Monitor data graphs

You can view statistics on data graphs. All statistics can be viewed (for the storing period corresponding to the sampling interval setting). Usage statistics about storage system resources, which are monitored, can be viewed. When viewing usage statistics about resources, you can specify the range to view and which part of the storing period to display on lists and graphics.

For details about the Performance Monitor data graphs, see About the data graphs on page 2-19

.

Export Tool for Performance Monitor

The Export Tool software that comes with Performance Monitor allows you to export the monitoring data for analysis, for example using spreadsheet or database software. You can also use Export Tool to save and accumulate data over extended periods of time for long-term analysis and future reference.

For details about Export Tool, see Chapter 4, Exporting Performance Monitor data on page 4-1

.

Cautions and restrictions for Performance Monitor

•

Cautions and restrictions for monitoring on page 2-4

•

Cautions and restrictions for usage statistics on page 2-5



2-3

Cautions and restrictions for monitoring

•

Performance monitoring switch

When the monitoring switch is set to disabled, monitoring data is not collected.

•

Changing the SVP time setting

If the SVP time setting is changed while the monitoring switch is enabled, the following monitoring errors can occur:

¢

Invalid monitoring data appears.

¢

No monitoring data is collected.

If you have changed the SVP time setting, disable the monitoring switch, and then re-enable the monitoring switch. After that, obtain the

monitoring data. For details about the monitoring switch, see Starting monitoring on page 2-7 .

•

WWN monitoring

You must configure some settings before the traffic between host bus adapters and storage system ports can be monitored. For details, see

Adding new WWNs to monitor on page 2-8 ,

Adding WWNs to ports on page 2-10 , and

Connecting WWNs to ports on page 2-12 .

•

Parity group monitoring

To correctly display the performance statistics of a parity group, all volumes belonging to the parity group must be specified as monitoring targets.

•

Storage system maintenance

If the storage system is undergoing the following maintenance operations during monitoring, the monitoring data might not be valid:

¢

¢

¢

¢

¢

Adding, replacing, or removing cache memory

Adding, replacing, or removing data drives

Changing the storage system configuration

Replacing the firmware

Formatting or quick formatting logical devices

¢

Adding, replacing, or removing MP units

•

Storage system power-off

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

•

Firmware replacement

After the firmware is replaced, monitoring data is not stored until the service engineer releases the SVP from Modify mode. Therefore, inaccurate data might be temporarily displayed.

2-4



Cautions and restrictions for usage statistics

•

Retention of usage statistics

Usage statistics for up to the last 15 days are displayed in monitoring.

Usage statistics outside of these ranges are deleted from the SVP.

•

Statistics for periods of high I/O workload

If the host I/O workload is high, the storage system gives higher priority to I/O processing than to monitoring. If this occurs, some monitoring data might be missing. If monitoring data is missing frequently, use the Edit

Monitoring Switch window to lengthen the sampling interval. For details, see

Starting monitoring on page 2-7

.

•

Reverse resync operations

When you run the CCI horctakeover or pairresync-swaps command for a

UR pair, the primary and secondary volumes are swapped. You can collect the before-swapped information immediately after you run any of the commands. Incorrect monitoring data will be generated for a short time but will be corrected automatically when the monitoring data gets updated. The incorrect data will temporarily be generated when the volume used for a secondary volume is used as a primary volume after a

UR pair is deleted.

•

Display of monitoring data immediately after monitoring starts or immediately after the sampling interval is changed

Monitoring data cannot be displayed immediately after monitoring starts or immediately after the sampling interval is changed, because no monitoring data has accumulated. “Immediately after” here means the time within the first two sampling intervals after the monitoring starts or the interval is changed. For instance, if the sampling interval is set or changed to 15 minutes, monitoring data is not accumulated for up to 29 minutes after this setting is made.

•

Display of monitoring data during high SVP workload

If the SVP is overloaded, the system might require more time than the sampling interval allows to update the display of monitoring data. If this occurs, some portion of monitoring data is not displayed. For example, suppose that the sampling interval is 1 minute, and the display in the

Performance Management window is updated at 9:00 and the next update occurs at 9:02. In this case, the window (including the graph) does not display the monitoring result for the period of 9:00 to 9:01. This situation can occur when the following maintenance operations are performed on the storage system or on the Device Manager - Storage Navigator PC:

¢

¢

Adding, replacing, or removing cache memory.

Adding, replacing, or removing data drives.

¢

¢

Changing the storage system configuration.

Replacing the firmware.

•

Pool-VOLs

Pool-VOLs of Thin Image and Dynamic Provisioning are not monitored.

•

Margin of error

The monitoring data may have a margin of error.



2-5

Performance monitoring workflow

1

.

2

.

3

.

4

.

5

.

6

.

7

.

8

.

9

.

Determine the resources to be monitored and the data to be collected, and write down the required information, including control unit (CU) numbers and WWNs of host bus adapters.

Set the storing period for the monitoring statistics. For instructions, see

Setting the storing period for the monitoring data on page 2-6 .

Start performance monitoring. For instructions, see Starting monitoring on page 2-7 .

Add the WWNs to monitor. For instructions, see

Monitoring WWNs on page 2-8

.

Add the CUs to monitor. For instructions, see Monitoring CUs on page

2-13 .

Adjust the sampling interval as needed to increase or decrease the

maximum storing period of statistics. For instructions, see Changing the sampling interval on page 2-17 .

View the monitoring data on graphs. For details, see

Using the

Performance Monitor data graphs on page 2-18 .

Export the monitoring data as needed for analysis and for retention of long-term data. For details, see

Chapter 4, Exporting Performance

Monitor data on page 4-1

.

When you want to stop collecting monitor data, stop monitoring by disabling the monitoring switch. For details, see

Stopping monitoring on page 2-18 .

Setting the storing period for the monitoring data

Before you start the monitoring function, you need to set the storing period for the monitoring data. Data can be collected for up to 15 days.

Prerequisites

• Required role: Storage Administrator (Performance Management)

Procedure

1

.

Display the Monitor Performance window.

In Device Manager - Storage Navigator: a

.

b

.

Select Analytics in Explorer.

Select Performance Monitor in the tree to open the Performance

Monitor window.

c

.

On the Performance Monitor window, click Monitor Performance to open the Monitor Performance window.

In Hitachi Command Suite: a

.

Select the Resources tab, and expand the Storage Systems tree.

2-6



2

.

3

.

b

.

Right-click the target storage system and then select Performance

Monitor.

c

.

On the Performance Monitor window, click Monitor Performance to open the Monitor Performance window

Select Set Range or Use Real Time in the Time Range as the periods

(ranges) for displaying statistics.

You can select Set Range or Use Real Time.

Click Apply to apply the settings to the storage system.

Related topics

•

Performance Monitor main window on page A-3

•

Monitor Performance window on page A-7

Starting monitoring

Caution: When you start monitoring a storage system, all of its previous monitoring statistics are deleted. If you want to keep the previous monitoring statistics, first export the desired data using the Export Tool and then restart monitoring.

After you have set the storing period for the monitoring data, you can start the monitoring function. While the statistics information is being collected, the server workload increases and the client process might slow down.

Prerequisites


Procedure

1

.

Display the Performance Monitor window.


.


b

.


Monitor window.

In Hitachi Command Suite:

2

3

.

.

a

.

b

.



Monitor.

In the Performance Monitor window click Edit Monitoring Switch to open the Edit Monitoring Switch window.

Click Enable in the Monitoring Switch field.

4

.

Select the sampling interval in the Sample Interval. This option is activated when you specify Enable for Current Status.



2-7

5

.

Click Finish.

6

.

In the Confirm window enter your task name in Task Name, and click

Apply to start monitoring.

Note: Monitoring data cannot be displayed for the time within the first two sampling intervals after the monitoring starts because no monitoring data has accumulated. For instance, if the sampling interval is set to 15 minutes, monitoring data is not accumulated for up to 29 minutes after the start of monitoring.

Related topics

•

Edit Monitoring Switch window on page A-6

Monitoring WWNs

This section provides instructions for monitoring WWNs using Hitachi

Performance Monitor:

•

Adding new WWNs to monitor on page 2-8

•

Viewing the WWNs that are being monitored on page 2-9

•

Removing WWNs to monitor on page 2-9

•

Adding WWNs to ports on page 2-10

•

Editing the WWN nickname on page 2-11

•

Connecting WWNs to ports on page 2-12

•

Deleting unused WWNs from monitoring targets on page 2-13

Adding new WWNs to monitor

Prerequisites


Procedure

1

.


In Device Manager - Storage Navigator:

2

.

a

.


b

.


Monitor window.

In Hitachi Command Suite: a b

.

.



Monitor.

In the Performance Monitor window select the Monitored WWNs tab.

2-8



5

.

6

.

3

.

On the Monitored WWNs tab click Edit WWN Monitor Mode to open the Edit WWN Monitor Mode window.

4

.

In the Edit WWN Monitor Mode window select the WWNs in the

Unmonitored WWNs list, and click Add.

Enter your task name in Task Name, and click Finish.

In the Confirm window click Apply to apply the settings to the storage system.

If Go to tasks window for status was checked, the Task window appears.

Related topics

•

Edit WWN Monitor Mode wizard on page A-33

Viewing the WWNs that are being monitored

Prerequisites


Procedure

1

.



.


b

.


Monitor window.


.

.



Monitor.

2

.

In the Performance Monitor window select the Monitored WWNs tab to see the WWNs that are currently being monitored.

Related topics

•


Removing WWNs to monitor

Prerequisites




2-9

Procedure

1

.



.


b

.


Monitor window.


.

.



Monitor.

5

.

6

.

2

.

Click the Monitored WWNs tab.

3

.

On the Monitored WWNs tab click Edit WWN Monitor Mode to open the Edit WWN Monitor Mode window.

4

.

Select the WWNs in the Monitored WWNs list that you want to remove, and click Remove.

Enter your task name in Task Name, and click Finish.

In the Confirm window click Apply.

7

.

When the warning message appears, click OK to close the message. The settings are applied to the storage system.

Related topics

•

Edit WWN Monitor Mode wizard on page A-33

Adding WWNs to ports

If you want to monitor WWNs that are not connected to the storage system, you can add them to ports and set them up for monitoring with Performance

Monitor.

Prerequisites


Procedure

1

.



.


b

.


Monitor window.


.


2-10



2

.

3

.

4

.

b

.


Monitor.

In the Performance Monitor window click the Monitored WWNs tab.

On the Monitored WWNs tab click Add New Monitored WWNs to open the Add New Monitored WWNs window.

Specify the following information for each new WWN:

Item Description

HBA WWN (required)

WWN Name (optional)

Enter the 16-digit hexadecimal number.

Enter the unique name to distinguish the host bus adapter from others. The WWN Name must be less than 64 characters and must consist of alphanumeric characters and at least one symbol.

Port (in Available Ports) In the Available Ports list select the port connected to the WWN.

7

.

8

.

5

.

6

.

Click Add. The added WWN is displayed in Selected WWNs.

If you need to remove a WWN from the Selected WWNs list, select the

WWN and click Remove.

When you are done adding WWNs, click Finish.


Related topics

•

Add New Monitored WWNs wizard on page A-38

Editing the WWN nickname

Prerequisites


Procedure

1

.



2

.

a

.


b

.


Monitor window.


.


b

.


Monitor.

Click the Monitored WWNs tab to see the list of WWNs being monitored.



2-11

3

.

Select the WWN to edit. You can edit only one WWN at a time. If you select multiple WWNs, an error will occur.

4

.

5

.

On the Monitored WWNs tab click Edit WWN to open the Edit WWN window.

On the Edit WWN window edit the HBA WWN and WWN Name fields as needed.

¢

HBA WWN

A 16-digit hexadecimal number. The value of HBA WWN must be unique in the storage system.

6

.

¢

WWN Name

The nickname distinguishes the host bus adapter from others. The

WWN Name must be less than 64 digits and must consist of alphanumeric characters and at least one symbol.

When you are done editing WWNs, click Finish.

7

.


Related topics

•

Edit WWN wizard on page A-31

Connecting WWNs to ports

Prerequisites


2

.

3

.

Procedure

1

.

4

.



.


b

.


Monitor window.


.

.



Monitor.

In the Performance Monitor window click the Monitored WWNs tab.

On the Monitored WWNs tab select the WWN to connect to the port.

Select only one WWN at a time. If you select multiple WWNs, an error occurs.

On the Monitored WWNs tab click Add to Ports to open the Add to

Ports window.

2-12



7

.

8

.

5

.

Select the port to connect in Available Ports, and then click Add.

The selected WWN and port are added to the Selected WWNs list.

6

.

If you need to delete a WWN from the Selected WWNs list, select the

WWN, and then click Remove.

When you are done selecting the WWNs to connect, click Finish.


Related topics

•

Add to Ports wizard on page A-42

Deleting unused WWNs from monitoring targets

Prerequisites


2

.

3

.

Procedure

1

.

4

.



.


b

.


Monitor window.


.


b

.


Monitor.

Click the Monitored WWNs tab.

On the Monitored WWNs tab click Delete Unused WWNs to open the

Delete Unused WWNs window.


Apply.

Related topics

•

Delete Unused WWNs window on page A-37

Monitoring CUs

This section provides instructions for monitoring control units (CUs) using

Hitachi Performance Monitor.

•

Displaying CUs to monitor on page 2-14



2-13

•

Adding and removing CUs to monitor on page 2-14

•

Selecting CUs to monitor on page 2-15

•

Confirming the status of CUs to monitor on page 2-16

Displaying CUs to monitor

Prerequisites


Procedure

1

.



.


b

.


Monitor window.


.

.



Monitor.

2

.

Open the Monitored CUs tab to view the list of CUs.

Related topics

•


Adding and removing CUs to monitor

Use the Performance Monitor window to add or remove CUs to monitor. If this operation is performed, the monitoring result will be deleted.

Caution: Stored monitoring data is deleted when you perform this operation.

Prerequisites


Procedure

1

.

a

.

b

.





Monitor window.

2-14



2

.

3

.

4

.

5

.

6

.


.


b

.


Monitor.

Open the Monitored CUs tab.

On the Monitored CUs tab click Edit CU Monitor Mode to open the Edit

CU Monitor Mode window.

Add or remove CUs to monitor.

To add CUs to monitoring target objects, select CUs from the

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

Remove.

Click Finish.


Apply.

Note: To monitor a parity group, specify the CU numbers of all LDEVs belonging to the parity group. Otherwise the parity group is not subjected to monitoring.

Related topics

•

Edit CU Monitor Mode wizard on page A-21

Selecting CUs to monitor

Prerequisites


Procedure

1

.



.


b

.


Monitor window.


.

.



Monitor.

2

.


3

.

On the Monitored CUs tab click Edit CU Monitor Mode to open the Edit

CU Monitor Mode window.

4

.

Click Select by Parity Groups in the Unmonitored CUs field.



2-15

5

.

The Select by Parity Groups window opens. The available parity group

IDs and number of CUs are displayed.

Select the parity group ID from the list and click Detail.

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

LDEVs are displayed.

6

.

Confirm the properties of the parity group and click Close.

The Select by Parity Groups window opens.

7

.

Select the parity group to be the monitoring target in the Select by

Parity Groups window and click OK.

CUs in the parity group are selected in the Unmonitored CUs field. For information about monitoring these CUs, see

Adding and removing CUs to monitor on page 2-14 .

Related topics

•

Select by Parity Groups window on page A-28

•

Parity Group Properties window on page A-30

•


Confirming the status of CUs to monitor

Prerequisites


2

.

3

.

Procedure

1

.



.


b

.


Monitor window.


.

.



Monitor.


Open the View CU Matrix window using one of the following methods:

¢

¢

On the Monitored CUs tab click View CU Matrix.

In the Reports menu click Performance Monitor then View CU

Matrix.

¢

On the Monitored CUs tab click Edit CU Monitor Mode then View

CU Matrix.

The following CUs are displayed in the Monitored CUs window:

2-16



4

.

¢

¢

Monitored CUs

Set monitored CUs

¢

Release monitored CUs

Click Close.

The Edit CU Monitor Mode window opens.

Related topics

•

View CU Matrix window on page A-26

Changing the sampling interval

You can change the sampling interval for monitoring. For example, if you want to collect statistics over a longer period of time, you can lengthen the sampling interval to increase the storing period (for details see

Maximum storing period for monitoring on page 2-3 ).

Prerequisites


4

.

5

.

Procedure

1

.

2

.

3

.



.


b

.


Monitor window.


.


b

.


Monitor.


Select the desired sampling interval in the Sample Interval. This option is available only when the current monitoring status is Enable.

Click Finish.


Apply to change the sampling interval.

Note: Monitoring data cannot be displayed immediately after the sampling interval is changed, because no monitoring data with the new sampling interval has accumulated. “Immediately after” here means the time within the first two sampling intervals after the interval was changed. For instance, if the sampling interval is changed to 15 minutes,



2-17

monitoring data is not accumulated for up to 29 minutes after the interval was changed.

Related topics

•


Stopping monitoring

When you no longer need to collect monitoring statistics, you can stop the monitoring function. After you stop monitoring, you should consider exporting the monitoring statistics using the Export Tool, because the existing statistics are deleted each time monitoring is restarted.

Prerequisites


4

.

5

.

Procedure

1

.



2

.

3

.

a

.


b

.


Monitor window.


.


b

.


Monitor.


Click Disable in the Monitoring Switch field.

The Sample Interval list is grayed out and becomes ineffective.

Click Finish.


Apply to stop monitoring.

Related topics

•

Edit Monitoring Switch wizard on page A-5

Using the Performance Monitor data graphs

•

About the data graphs on page 2-19

•

Displaying the monitor data on graphs on page 2-19

2-18



•

Adding a new graph on page 2-20

•

Changing the data displayed on a graph on page 2-21

•

Changing the time period displayed on the graph panel on page 2-22

•

Deleting a graph on page 2-23

About the data graphs

The Hitachi Performance Monitor data graphs are displayed on panels with the graph on the left and the legend for the graph on the right. Hitachi

Performance Monitor can display up to eight monitoring objects per graph panel. You can set a maximum of four graph panels with up to 16 monitoring objects.

• You can change the size of each graph panel by clicking the icon in the upper right of the panel.

• You can display the value of each data point by placing the mouse cursor on the data point on the graph.

• You can adjust the unit of scale on the vertical axis using the vertical scale selector on the upper left of the graph. For example, you may need to increase the vertical scale to see data with high values.

In some cases you may need to adjust the vertical scale to display the data properly. For example, if the scale is too small a single data line may be so thick that the entire graph is painted in a single color.

• You can display or hide data points on the graph panel by clicking the legend on the right of the graph. Each graph must display at least one set of data, so you cannot hide all of the data.

• When you are viewing data for the MP units in real time (Time Range is set to Use Real Time), the MP unit names are displayed as text links.

Displaying the monitor data on graphs

Prerequisites


Procedure

1

.

a

.

b

.



.


b

.


Monitor window.




Monitor.



2-19

2

.

Specify the data range and time period to be displayed on the graphs:

3

.

a

.

In the Data Range field, select the data range.

b

.

In the Time Range field, select Set Range to display data from a specific period of time, or select Use Real Time to display real-time data as it is being collected.

c

.

If you selected Set Range, specify the starting date/time and ending date/time for the range of data in the From and To fields.

Specify the monitor data to be displayed on the graphs:

4

.

a b

.

.

In the Performance Objects area 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.

Select items in the Monitor Data field.

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

c

.

Select the monitor data to be graphed in the Available Objects list.

d

.

Click Add to add the monitor data to the Selected Objects list.

e

.

If you need to remove monitor data from the Selected Objects list, select the object and click Remove.

Click Apply to display the selected monitor data on graphs in the

Monitor Performance window.

Related topics

•


•


Adding a new graph

Prerequisites


Procedure

1

.



.

b

.



Monitor window.

c

.



.


2-20



2

.

3

.

4

.

5

.

b

.


Monitor.

c

.


Display the graph panel in the Monitor Performance window.

For details, see


.

Click Add Graph to open the Add Graph window.

If a warning message is displayed when you click the Add Graph button, you are already displaying the maximum number of graphs. To add another graph you need to first delete an existing graph. For details, see

Deleting a graph on page 2-23 .

Specify the monitor data to be graphed by selecting the objects on the left and adding them to the Selected Objects list on the right.

For details, see


.

Click OK to add the specified graph.

Related topics

•


•

Add Graph window on page A-63

•


Changing the data displayed on a graph

Prerequisites


Procedure

1

.

2

.


In Device Manager - Storage Navigator: a b

.

.

Select Analytics in Explorer, and select Performance Monitor in the tree to open the Performance Monitor window.


c

.



.


b c

.

.


Monitor.





2-21

3

.

4

.

5

.

For details, see


.

Click Edit Performance Objects to open the Edit Performance

Objects window.

Edit the monitor data being displayed on the graph by adding objects to and deleting objects from the Selected Objects list on the right.

For details, see


.

Click OK to display the graph with the newly specified monitor data.

Related topics

•


•

Edit Performance Objects window on page A-49

•


Changing the time period displayed on the graph panel

Prerequisites


3

.

4

.

Procedure

1

.

2

.

5

.



.

Select Analytics in Explorer, and select Performance Monitor in the tree to open the Performance Monitor window.

b

.



.

b

.



Monitor.

c

.



For details, see


.

Click Edit Time Range to open the Edit Time Range window.

Enter the desired starting date and time in the From field. Enter the desired end date and time in the To field.

Click OK to display the graph panel with the newly selected time period.

Related topics

•


2-22



•

Edit Time Range window on page A-48

•


Deleting a graph

Prerequisites


Procedure

1

.



.

b

.



Monitor window.

c

.



2

.

a

.

b

.

c

.



Monitor.



For details, see


.

3

.

Click Delete Graph in the lower right, or click the close icon in the upper right corner.

4

.

When the confirmation message appears, click OK to delete the graph.

Related topics

•


•




2-23

2-24



3

Hitachi Performance Monitor data

This chapter provides detailed descriptions of the monitoring data collected and displayed by Hitachi Performance Monitor.

□

Monitoring data

□

Usage rates of MPs

□

Usage rate of cache memory

□

Write pending rates

□

Storage system throughput

□

Data transfer rate

□

Response times

□

Cache hit rates

□

Back-end performance

□

Drive usage rates

□

Data drive access rates

□

ShadowImage usage statistics

□

Remote I/O (RIO)

□

Pair Synchronized

3-1

Hitachi Performance Monitor data


□

Differential Track

□

Number of Journals

□

Data Usage Rate

□

Meta Data Usage Rate

3-2



Monitoring data

The following table lists the objects that can be monitored and specifies the data that is collected for each monitoring object. You can specify the objects that are displayed in the graphs in the Performance Objects in the Monitor

Performance window. When the resource group feature is installed, you can specify the objects to be displayed in the graphs only when the necessary resources specified in the following table are allocated.

The monitoring data for each sampling interval is the average value of the data over the data sampling interval. The sampling interval is 1 to 15 minutes. The monitoring data shows the information by each resource ID even when the volume is in a virtual storage machine (not by virtual ID). For instructions on viewing the monitoring data, see

Using the Performance

Monitor data graphs on page 2-18 .

Object of monitoring

Monitoring data

Controller

Cache

Fibre port

(target)

Fibre port

(initiator) iSCSI port

(target) iSCSI port

(initiator)

WWN

Usage rates of MPs (%)

Usage rates of cache (%)

Write pending rates (%)

Throughput (IOPS)

Data transfer (MB/s)

Response time (ms)

Throughput (IOPS)


Response time (ms)

Throughput (IOPS)


Response time (ms)

Throughput (IOPS)


Response time (ms)

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)

LDEV (base) Total throughput (IOPS)

Read throughput (IOPS)

Necessary resources

None

None

Port

Port

Port

Port

Port

LDEV



3-3

3-4


Monitoring data

LDEV (TC/

GAD)

Write throughput (IOPS)

Cache hit (%)


Response time (ms)

Back transfer (count/sec)

Drive usage rate (%)

1

Drive access rate (%)

1

ShadowImage usage rates (%)

1

RIO (count)

Pair Synchronized (%)

Differential track (count)

Initial copy throughput (count)

LDEV (UR)

Initial copy data transfer (MB/s)

Initial copy response time (ms)

Update copy throughput (count)

Update copy data transfer (MB/s)

Update copy response time (ms)

Write host I/O throughput (IOPS)

Write host I/O data transfer (MB/s)

Initial copy cache hit (%)


Parity group Total throughput (IOPS)


LUN (base)


Cache hit (%)


Response time (ms)


Drive usage rate (%)

1

Total throughput (IOPS)



Cache hit (%)




LDEV

LDEV

Parity group

• Host group

• LDEV


LUN (TC/

GAD)

2

LUN (UR)

2

External storage

Journal

Monitoring data



Response time (ms)


RIO (count)







•

•

Host group

LDEV





•

•

Host group

LDEV



Data transfer between Hitachi Virtual Storage Platform

G200, G400, G600, G800 and external storage per logical device (MB/s)

Response time between Hitachi Virtual Storage

Platform G200, G400, G600, G800 and external storage per logical device (ms)

LDEV

Data transfer between Hitachi Virtual Storage Platform

G200, G400, G600, G800 and external storage per external volume group (MB/s)

Response time between Hitachi Virtual Storage

Platform G200, G400, G600, G800 and external storage per external volume group (ms)



Parity group

None



Master journal throughput (IOPS)

Master journal journal (count/sec)

Master journal data transfer (MB/s)

Master journal response time (ms)



3-5


Monitoring data


Entire storage system (TC/

GAD)

Entire storage system (UR)

Master journal usage data (%)

Master journal meta data usage rate (%)

Restore journal throughput (IOPS)

Restore journal journal (count/sec)

Restore journal data transfer (MB/s)

Restore journal response time (ms)

Restore journal usage data (%)

Restore journal meta data usage rate (%)

RIO (count)













None

None

Master journal throughput (IOPS)

Master journal journal (count/sec)

Master journal data transfer (MB/s)

Master journal response time (ms)

Restore journal throughput (IOPS)

Restore journal journal (count/sec)

Restore journal data transfer (MB/s)

Restore journal response time (ms)

Notes:

1

.

Only information on internal volumes is displayed. Information on external volumes is not displayed.

2

.

The same value is output to all LUNs mapped to the LDEV.

3-6



Usage rates of MPs

Function

The usage rate of the MP shows the usage rate of an MP assigned to a logical device. If a usage rate of an MP is high, I/Os concentrate to an MP. Examine the distribution of I/Os to other MP units.

Storing period

Sample Interval can be specified from 1 to 15 minutes.

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on left side of

Object field

Controller

Item on right side of Object field

MP


Monitor Data field

Usage Rate (%)

Item on right side of Monitor Data field

None

Usage rate of cache memory

Function

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

Storing period





Object field

Cache


None



Usage Rate (%)


None



3-7

Write pending rates

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





Object field

Cache


None



Write Pending Rate

(%)


None

Storage system throughput

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.

Throughput in the following modes can be displayed:

• Sequential access mode

• Random access mode

• Total value in the above-mentioned modes

Storing period




3-8




Object field

Fibre Port

1 iSCSI Port

1

WWN

1

Logical Device

1

Parity Group

1

LUN

3

Target

Initiator

Target

Initiator

WWN

Port

Base


TC/GAD

UR

None

Base

Item on left side of Monitor Data field


Throughput (IOPS) None






Total Throughput

(IOPS)

Total

Sequential

Read Throughput

(IOPS)

Random

Total

Sequential

Random

Write Throughput

(IOPS)

Total

Sequential

Initial copy

Update copy

Write Host I/O

Total Throughput

(IOPS)

Read Throughput

(IOPS)

Write Throughput

(IOPS)

Total Throughput

(IOPS)

Read Throughput

(IOPS)

Random

Throughput (count)

2

Throughput (count)

2

Throughput (IOPS)

Total

Sequential

Random

Total

Sequential

Random

Total

Sequential

Random

Total

Sequential

Random

Total

Sequential



3-9


Object field




Random

Journal

TC/GAD

UR

UR

Write Throughput

(IOPS)

Initial copy

Update copy

Write host I/O

Write host I/O

Master journal

Total

Sequential

Random

Throughput (count)

2

Throughput (count)

2

Throughput (IOPS)

Throughput (IOPS)

Throughput (IOPS)

Entire Storage

System

TC/GAD

Restore journal

Initial copy

Throughput (IOPS)

Throughput (count)

2

UR

Update copy

Write host I/O

Master journal

Throughput (count)

2

Throughput (IOPS)

Throughput (IOPS)

Restore journal Throughput (IOPS)

Notes:

1

.

Volumes that do not accept I/O from the host, such as pool-VOLs, are not monitored.

2

.

The total number of accesses is displayed.

3

.

The same value is output to all LUNs mapped to the LDEV.

Data transfer rate

Function

The amount of data transferred from the host server per second. The data transfer rate for both read data and write data can be monitored.

Storing period




3-10




Object field

Fibre Port* iSCSI Port*

WWN*

Logical Device*

Parity Group*

LUN*

External Storage

Journal

Target

Initiator

Target

Initiator

WWN

Port

Base


TC/GAD

UR

None

Base

TC/GAD

UR

Logical Device

Parity Group

UR



Data Trans. (MB/s)

Data Trans. (MB/s)

Data Trans. (MB/s)

Data Trans. (MB/s)

Data Trans. (MB/s)

Data Trans. (MB/s)

Data Trans. (MB/s)

Initial Copy

Update Copy

Write Host I/O

Initial Copy

Data Trans. (MB/s)

Data Trans. (MB/s)

Initial Copy

Update Copy

Write Host I/O

Initial Copy

Data Trans. (MB/s)

Data Trans. (MB/s)

Write host I/O

Initial copy

Master journal

Restore journal


None

None

None

None

None

None

Total

Read

Write

Data Trans. (MB/s)

Data Trans. (MB/s)

Data Trans. (MB/s)

Data Trans. (MB/s)

Total

Read

Write

Total

Read

Write

Data Trans. (MB/s)

Data Trans. (MB/s)

Data Trans. (MB/s)

Data Trans. (MB/s)

Total

Read

Write

Total

Read

Write

Data Trans. (MB/s)

Data Trans. (MB/s)

Data Trans. (MB/s)

Data Trans. (MB/s)



3-11


Object field





Entire Storage

System

TC/GAD

UR

Initial copy

Update copy

Write host I/O

Data Trans. (MB/s)

Data Trans. (MB/s)

Data Trans. (MB/s)

Initial copy

Master journal

Data Trans. (MB/s)

Data Trans. (MB/s)

Restore journal Data Trans. (MB/s)

*Volumes that do not accept I/O from the host, such as pool-VOLs, are not monitored.

Response times

Function

Time (in milliseconds) for replying from an external volume group when I/O accesses are made from the Hitachi Virtual Storage Platform G200, G400,

G600, G800 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





Object field

Fibre Port* iSCSI Port*

WWN*

Logical Device*

Target

Initiator

Target

Initiator

WWN

Port

Base





Response Time (ms) None






Response Time (ms) Total

Read

3-12




Object field





Parity Group*

LUN*

External Storage

TC/GAD

None

Base

TC/GAD

Logical Device

Parity Group

Initial Copy

Update Copy

Write

Response Time (ms)

Response Time (ms)


Read

Write


Read

Write

Response Time (ms) Initial Copy

Update Copy Response Time (ms)


Read

Write


Read

Journal

Entire Storage

System

UR

TC/GAD

Master Journal

Restore Journal

Initial Copy

Update Copy

Write

Response Time (ms)

Response Time (ms)

Response Time (ms)

Response Time (ms)

UR Master Journal

Restore Journal

Response Time (ms)

Response Time (ms)

* Volumes that do not accept I/O from the host, such as pool-VOLs, are not monitored.

Cache hit rates

Function

The cache hit rate is a rate that the input or output data of the disk exists in the cache. The cache hit rate is displayed for sequential access mode, random access mode, and both of these modes.

• Read hit ratio



3-13

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





Object field

Logical Device*

Parity Group*

LUN*

Item on right side of Objecc field

Base

UR

None

Base



Cache Hit (%)

Initial Copy

Cache Hit (%)

Cache Hit (%)


Read (Total)

Read (Sequential)

Read (Random)

Write (Total)

Write (Sequential)

Write (Random)

Cache Hit (%)

Read (Total)

Read (Sequential)

Read (Random)

Write (Total)

Write (Sequential)

Write (Random)

Read (Total)

Read (Sequential)

Read (Random)

3-14




Object field

Item on right side of Objecc field




Write (Total)

Write (Sequential)

Write (Random)

Journal

UR

UR

Initial Copy

Initial Copy

Cache Hit (%)

Cache Hit (%)

Entire Storage

System

UR Initial Copy Cache Hit (%)

* Volumes that do not accept I/O from the host, such as pool-VOLs, are not monitored.

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 data drive. The graph contains following information.

•

Cache to Drive

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

•

Drive to Cache (Sequential)

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

•

Drive to Cache (Random)

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

Storing period





Object field

Logical Device*


Base



Back Trans. (count/ sec)


Total

Cache to Drive



3-15


Object field





Parity Group*

LUN*

None

Base



Drive to Cache

(Sequential)

Drive to Cache

(Random)

Total

Cache to Drive

Drive to Cache

(Sequential)

Drive to Cache

(Random)

Total

Cache to Drive

Drive to Cache

(Sequential)

Drive to Cache

(Random)


Drive usage rates

Function

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

Storing period





Object field

Logical Device*

Parity Group*


Base

None




None Drive Usage Rate

(%)

Drive Usage Rate

(%)

None

3-16




Object field





*Only information on internal volumes is displayed. Information about external volumes is not displayed.

Data drive access rates

Function

The data drive access rate shows the access rate of each data drive.

The rate of the file reading Read (Sequential) or the file writing Write

(Sequential) processing of the data drive in the sequential access mode is displayed.

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

Storing period





Object field





Logical Device* Base Drive Access Rate

(%)

Read (Sequential)

Read (Random)

Write (Sequential)

Write (Random)


ShadowImage usage statistics

Function

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



3-17

Storing period





Object field





Logical Device* Base ShadowImage (%) None


Remote I/O (RIO)

Function

Information about LDEV performance is shown through the total number of remote I/Os from the P-VOL to the S-VOL of a TrueCopy or global-active device pair.

Storing period





Object field





Logical Device* TC/GAD RIO (count) Total

Write

Error

LUN* TC/GAD RIO (count) Total

Write

Entire Storage

System

TC/GAD RIO (count)

Error

Total

Write

Error


3-18



Pair Synchronized

Function

The synchronization rate between the P-VOL and S-VOL of a TrueCopy or global-active device pair is shown as the pair synchronization rate (%).

Storing period




Item on left side of Object field





Logical Device*

LUN*

TC/GAD

TC/GAD

Pair Synchronized (%) None

Pair Synchronized (%) None

Entire Storage

System

TC/GAD Pair Synchronized (%) None


Differential Track

Function

The synchronization rate between the P-VOL and the S-VOL of a TrueCopy or global-active device pair is shown through the number of differential tracks

(the number of tracks not transmitted from the P-VOL to the S-VOL).

Storing period

Sample Interval can be specified.




Logical Device*


TC/GAD



Differential track

(count)


None



3-19






LUN*

Entire Storage

System

TC/GAD

TC/GAD

Differential track

(count)

Differential track

(count)

None

None


Number of Journals

Function

The total number of journals transferred from the master journal volume to the restore journal volume is shown.

Storing period





Object field

Journal

Entire Storage

System


UR

UR



Master Journal

Restore Journal

Master Journal

Restore Journal


Journal (count/sec)

Journal (count/sec)

Journal (count/sec)

Journal (count/sec)

Data Usage Rate

Function

The current journal data usage rate (%) is shown, with the journal volume data space assumed to be 100%.

Storing period

Sample Interval can be specified.

3-20






Journal




Item on right side of


UR Master Journal

Restore Journal

Data Usage Rate (%)

Data Usage Rate (%)

Meta Data Usage Rate

Function

The meta data usage rate of the current journal is shown, with journal volume meta data space assumed to be 100%.

Storing period





Journal UR



Master Journal

Restore Journal



Meta Data Usage Rate (%)

Meta Data Usage Rate (%)



3-21

3-22



4

Exporting Performance Monitor data

This chapter describes and provides instructions for export the Hitachi

Performance Monitor data for your Hitachi Virtual Storage Platform G200,

G400, G600, G800 storage system using the Export Tool for use in spreadsheet and other applications.

□

About the Export Tool

□

Preparing to use the Export Tool

□

Using the Export Tool

□

Export Tool command reference

□

Exported files

□

Causes of Invalid Monitoring Data

Exporting Performance Monitor data


4-1

About the Export Tool

Use 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,

Universal Replicator, and global-active device. After exporting monitoring data to text files, you can import that data into desktop publishing applications, such as Microsoft Word, or into spreadsheet or database applications for analysis.

Example of a text file

The following example is of a text file imported into spreadsheet software.

Note: In this LU_IOPS.csv file, the last four digits of a table column heading

(such as 0001 and 0002) indicate a LUN. For example, the heading CL1-A.

00(1A-G00).0001 indicates the port CL1-A, the host group ID 00, the host group name 1A-G00, and the LUN 0001.

If you export monitoring data about concatenated parity groups, the resulting

CSV file does not contain column headings for the concatenated parity groups. For example, if you export monitoring data about a concatenated parity group named 1-3[1-4], you will not be able to find 1-3[1-4] in column headings. To locate monitoring data about 1-3[1-4], find the 1-3 column or the 1-4 column. Either of these columns contains monitoring data about

1-3[1-4].

Preparing to use the Export Tool

Requirements for the Export Tool

The following components are required to use the Export Tool. For details, see the Hitachi Command Suite User Guide.

•

Windows computer or a UNIX computer

4-2



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

Note: If a firewall exists between the Hitachi Command Suite computer and the SVP, see the Hitachi Command Suite User Guide. In the topic about setting up TCP/IP for a firewall, the RMI port numbers listed are the only direct communication settings required for the Export Tool.

•

Java Runtime Environment (JRE) software

To use the Export Tool, you must have the JRE software on your Windows or UNIX computer. If your computer runs Hitachi Command Suite, the required version of JRE is already installed (Export Tool uses the same

JRE version as Hitachi Command Suite), and you can install the Export

Tool. If your computer does not run Hitachi Command Suite but contains the required version of JRE, you can install the Export Tool on your computer. If your computer does not have the required JRE version, you need to install JRE before installing Export Tool. See the Hitachi Command

Suite User Guide for the required JRE version.

•

User ID for exclusive use of the Export Tool

Before you can use the Export Tool, you must create a user ID for exclusive use of the Export Tool. Assign only the Storage Administrator

(Performance Management) role to the user ID for the Export Tool. Do not assign any roles other than the Storage Administrator (Performance

Management) role to this user ID. Users who have the Storage

Administrator (Performance Management) role can perform the following operations:

¢

¢

Saving the monitoring data into files

Changing the sampling interval

¢

Starting and stopping monitoring by using the set subcommand

For details about creating user IDs, see Hitachi Command Suite User

Guide.

•

The Export Tool program

Media for the software products contains the Export Tool. For information

about how to install the Export Tool, see Installing the Export Tool on page 4-4

.

Caution:

• Always use the Export Tool version corresponding to the Device Manager

- Storage Navigator software. When the Device Manager - Storage

Navigator software changes, you must install the Export Tool version that is on the Host Feature disk. For the Export Tool version, see the

Readme.txt file on the Host Feature disk.

• Running multiple instances of the Export Tool simultaneously is not supported. If you run multiple instances, the SVP can become overloaded and a timeout error can occur.



4-3

Installing the Export Tool

•

On Windows on page 4-4

•

On UNIX on page 4-4

On Windows

3

.

4

.

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

1

.

2

.

5

.

Log on with administrator privileges.

Create a new folder for the Export Tool application (for example, C:

\Program Files\monitor). If this folder already exists, skip this step.

Insert the software media into the computer.

Locate the \program\monitor\win folder on the media, and copy the self-extracting file export.exe from the media into the new folder you just created.

Double-click export.exe to start the installation. The Export Tool is installed, and a new folder named “export” is created.

Note: Delete runUnix.bat from the export folder (this file is no longer needed).

On UNIX

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

1

.

Log on as a superuser.

You do not need to remove a previous installation of Export Tool. The new installation overwrites the older program.

2

.

Create a new directory for the Export Tool program (for example, / monitor).

Mount the media for the software products.

3

.

4

.

Go to the /program/monitor/UNIX directory on the media, and copy the export.tar file to the new directory you just created.

5

.

Decompress the export.tar file on your computer. The Export Tool is installed into the installation directory.

Note: Delete runWin.bat from the installation directory (this file is no longer needed).

Using the Export Tool

After installing the Export Tool, you must prepare a command file and a batch file before you can export any monitoring data. This section explains how to

4-4



prepare a command file and a batch file, and then how to run the Export

Tool.

Preparing a command file

To run the Export Tool, you must write scripts for exporting monitoring data.

When writing scripts, you must write several subcommands in a command file. When you run the Export Tool, the subcommands in the command file are executed sequentially, and then the monitoring data is saved in files.

When you install the Export Tool, the command.txt file is stored in the installation directory. This file contains sample scripts for your command file.

Customize the scripts in command.txt according to your needs. For details

about subcommand syntax, see Export Tool command reference on page

4-13 .

In the following example of a command file, a semicolon (;) indicates the beginning of a comment, so the characters from a semicolon to the end of the line are comments. The scripts in this sample command file are described in the following example.

Example of a command file

ip 158.214.135.57:1099 ; Specifies the IP address of

; the SVP and the connection port number dkcsn 123456 ; Specifies the target DKC serial

; number.

login expusr ; Logs the user into the SVP show ; Outputs the storing period in

; the SVP to standard output group PhyPG ; Specifies the type of data to

; be exported and the storing

; period group RemoteCopy ; Specifies the type of data to

; be exported range 200610010850:200610010910 ; Specifies the range in

; which files will be saved outpath out ; Specifies the directory in

; which files will be saved option compress ; Specifies whether to

; compress files apply ; Executes processing for

; saving monitoring data in

; files

Scripts in this sample command file

• ip 158.214.135.57:1099

This script specifies that you are logging into the SVP whose IP address is

158.214.135.57 and that 1099 is the port number to connect to the SVP.

You must log into the SVP when using the Export Tool.

The ip subcommand specifies the IP address of the SVP. You must include the ip subcommand in your command file.



4-5

4-6

For detailed information about the ip subcommand, see ip on page

4-15 .

• dkcsn 123456

This script specifies the serial number of the system from which monitored data will be acquired. This subcommand specifies the system to provide the monitored data. Make sure to notate the dkcsn subcommand in the command file.

For detailed information about the dkcsn subcommand, see dkcsn in

dkcsn on page 4-16 .

• login expusr passwd

This script specifies that you use the user ID expusr and the password

passwd to log into the SVP.

The login subcommand logs the specified user into the SVP. You must include the login subcommand in your command file.

For detailed information about the login subcommand, see

login on page

4-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 the Export Tool on page 4-2 for

reference.

• show

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

The show subcommand displays the storing period of monitoring data.

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

Range From: 2006/10/01 01:00 - To: 2006/10/01 15:00

Interval: 1min.

In this example, the monitoring data is stored every 1 minute in the term of 1:00 - 15:00 on October 1, 2006. When you run the Export Tool, you can export monitoring data into the file.

The use of the show subcommand is not required, 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

4-18 .

• group PhyPG and group RemoteCopy

The group subcommand specifies the type of data that you want to export. Specify an operand following group to define the type of data to be exported.

The example script group PhyPG in

Preparing a command file on page 4-5

specifies to export usage statistics about parity groups. Also, the script



group RemoteCopy specifies to export statistics about remote copy operations by TrueCopy and global-active device. 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 4-19

.

• range 200610010850:200610010910

The range subcommand specifies the term of monitoring data to be exported. Use these subcommands when you want to narrow the exporttarget term within the stored data.

You can use this subcommand to narrow the export-target term for all of the monitoring items you can specify by the group subcommand.

Specify a term within "Range From XXX To XXX" which is output by the

show subcommand.

In the sample file in Preparing a command file on page 4-5

, the script range 200610010850:200610010910 specifies the term 8:50-9:10 on

October 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 global-active device in the term specified by the range subcommand.

If you run the Export Tool without specifying the 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 range subcommand, see

range on page 4-30

•

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 4-33

.

• option compress

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

• apply

The apply subcommand saves monitoring data in files. For detailed information about the apply command, see

apply on page 4-34

.

Related topics

•

Preparing to use the Export Tool on page 4-2

•

ip on page 4-15

•

show on page 4-18



4-7

•

group on page 4-19

•

range on page 4-30

•


•

option on page 4-34

•

apply on page 4-34

Preparing the batch file

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

batch 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/JSanRmiApiEx.jar;\

./lib/JSanRmiServerUx.jar" -Xmx536870912 -

Dmd.command=command.txt

-Dmd.logfile=export.log -Dmd.logpath=log

sanproject.getmondat.RJMdMain<CR+LF>

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

#! /bin/sh<LF> java -classpath

"./lib/JSanExport.jar:./lib/JSanRmiApiEx.jar:./lib/

JSanRmiServerUx.jar" -Xmx536870912

-Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain<LF>

In the previous scripts, <CR+LF> and <LF> indicate the end of a command line.

If the computer running the Export Tool communicates directly with the 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 cases, 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 in the log directory

• If you want to name log files as you like

If the computer that runs the Export Tool communicates with the SVP through a proxy host, edit the Java command script in a text editor to specify the host name (or IP address) and the port number of the proxy host. For

4-8



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/

JSanRmiApiEx.jar;./lib/JSanRmiServerUx.jar" -

Dhttp.proxyHost=Jupiter -Dhttp.proxyPort=8080 -Xmx536870912 -

Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain <CR+LF> pause <CR+LF>

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

#! /bin/sh <LF> java -classpath "./lib/JSanExport.jar:./lib/

JSanRmiApiEx.jar:./lib/JSanRmiServerUx.jar" -

Dhttp.proxyHost=Jupiter -Dhttp.proxyPort=8080 -Xmx536870912 -

Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain <LF>

In the preceding scripts, <CR+LF> and <LF> indicates the end of a command line.

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/

JSanRmiApiEx.jar;./lib/JSanRmiServerUx.jar" -

Dhttp.proxyHost=158.211.122.124 -Dhttp.proxyPort=8080 -

Xmx536870912 -Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain <CR+LF> pause <CR+LF>

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

#! /bin/sh <LF> java -classpath "./lib/JSanExport.jar:./lib/

JSanRmiApiEx.jar:./lib/JSanRmiServerUx.jar" -

Dhttp.proxyHost=158.211.122.124 -Dhttp.proxyPort=8080 -

Xmx536870912 -Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain <LF>

In these scripts, <CR+LF> and <LF> indicates the end of a command line.

For detailed information about syntax of the Java command, see

Java on page 4-37 .

Using the Export Tool

Running the batch file

To save monitoring data in files, launch the Export Tool by running the batch file. From a system running UNIX, enter the name of the batch file at the command prompt, and then press the <Enter> key.

From a system running Windows, double-click the batch file to run it.



4-9

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

Dots (...) appear on the screen until the system finishes exporting data. If an internal error occurs, an exclamation mark (!) appears, and then the Export

Tool restarts automatically.

Example of command prompt outputs from the Export Tool:

[ 2] ip 158.214.135.57:1099

[ 3] dkcsn 123456

[ 4] login User = expusr, Passwd = [****************]

:

:

[ 6] group Port

:

:

[20] apply

Start gathering port data

Target = 16, Total = 16

+----+----+----+----+----+----+----+----+----+----+

...........................!

.................................

End gathering port data

By default, the system compresses monitoring data files into a ZIP-format archive file. When you want to view the monitoring data, you can decompress and extract the CSV files from the ZIP archive. If the operating system on your computer does not include a way to extract files from a ZIP archive, you need to obtain software to view the data.

Note: You can change the default method of exporting files to an uncompressed format. However, the resulting files could be significantly larger and take longer to compile. For more information, see option

Subcommand

option on page 4-34 .

For a complete list of files to be saved by the Export Tool, see Using the

Export Tool on page 4-4 .

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 details see

option on page 4-34 ). 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 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, run the Export Tool multiple times for different periods, rather than running it one time 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 three 3-hour increments.

4-10



The next table provides lists time estimates for exporting monitoring data files using different operands in the group subcommand:

Table 4-1 Estimate of time required for exporting files

Operand for the group subcommand

Estimated time

Remarks

Port

PortWWN

LDEV

LU

5 minutes

5 minutes

60 minutes

60 minutes

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

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

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.

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.

*For a 1-minute interval, the number of hours for the data that is stored is proportional to the interval. For example, for a 2-minute interval, data for 48 hours can be stored.

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

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.



4-11

java -classpath "./lib/JSanExport.jar;./lib/

JSanRmiApiEx.jar;./lib/JSanRmiServerUx.jar" -Xmx536870912 -

Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain<CR+LF> if %errorlevel%==1 echo THE

SET SUBCOMMAND FAILED<CR+LF> if %errorlevel%==3 echo THE SET

SUBCOMMAND FAILED<CR+LF> pause<CR+LF>

In the previous scripts, <CR+LF> indicates the end of a command line.

Log files

When 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 should delete the log files regularly. For information about the directory containing the log files, see

Java on page 4-37 .

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

Table 4-2 Termination codes returned by the export tool

0

1

Terminatio n code

2

3

4

Meaning

The Export Tool finished successfully.

An error occurred when the set subcommand (see set on page 4-35

) executed, because an attempt to switch to Modify mode failed. Some other user might have been logged on in Modify mode.

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.

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 4-35 ) executed. Some other user might have been logged on

in Modify mode.

The Storage Administrator (Performance Management) role is not assigned to the user ID.

Error handling

When an internal error occurs during export processing, an exclamation mark

(!) appears to signal an error. By default, the Export Tool makes up to three more attempts at processing. You can change the maximum number of retries by using the retry subcommand. For detailed information about the

retry subcommand, see

retry on page 4-17 .

If export processing does not finish within three retries or if an internal error occurs other than those listed in the following table, the Export Tool stops. If the Export Tool stops, quit the command prompt, and then run the tool again.

4-12



For more information, see

Troubleshooting Performance Monitor on page

7-2 .

Errors for which export tool retries processing

Error message

ID

0001 4001

0001 5400

0001 5508

0002 2016

0002 5510

0002 6502

0002 9000

0003 2016

0003 2033

0003 3006

0405 8003

5205 2003

5205 2033

5305 2033

5305 8002

Cause of error

An error occurred during SVP processing.

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

An administrator is changing a system environment file.

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

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

Now processing.

Other user is accessing the storage system in Modify mode.

Service engineer is accessing the storage system in Modify mode.

The SVP is not ready yet, or an internal process is being executed.

An error occurred during SVP processing.

The storage system status is invalid.

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

The SVP is now updating the statistics data.

Updating the statistics data.

The storage system status is invalid.

Export Tool command reference

This section provides the syntax of the Export Tool subcommands that you can write in your command file and the command that should be used in your

batch file. Subcommand list on page 4-15

lists and provides links to the subcommands explained in this section. The Java command is explained in

Java on page 4-37 .

•

Export Tool command syntax on page 4-13

•

Subcommand list on page 4-15

Export Tool command syntax

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

•

Conventions on page 4-14



4-13

4-14

•

Syntax descriptions on page 4-14

•

Writing a script in the command file on page 4-14

•

Viewing the online Help for subcommands on page 4-15

Conventions

The following conventions are used to explain syntax:

Conventio n bold

italics

[ ]

{ }

...

|

Description

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

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

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.

Syntax descriptions

This syntax...

Indicates you can write this script...

connect ip-address connect 123.01.22.33

destination [directory] destination destination c:\temp

compress [yes|no] compress compress yes compress no

answer {yes|no} answer yes answer no

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

Writing a 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 ;;;;

;;;;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ip 158.214.135.57:51990 ; IP address of the SVP dkcsn 123456 ; Serial No of the DKC login expusr "passwd" ; Log into the SVP

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 more information

about how to use the help subcommand, see help on page 4-36

.

Subcommand list

Subcommand

ip on page 4-15

retry on page 4-17

login on page 4-18 show on page 4-18

group on page 4-19

range on page 4-30


option on page 4-34 apply on page 4-34

set on page 4-35

help on page 4-36

Java on page 4-37

Function

Specifies the IP address of the SVP to log into.

Makes settings on retries of export processing.

Logs the specified user into the SVP.

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

Specifies the type of data that you want to export.

Specifies the term of monitoring data to be exported.

Specifies the directory in which files should be saved.

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

Saves monitoring data in files.

Starts or ends monitoring of the storage system, and specifies the sampling interval.

Displays the online help for subcommands.

Starts the Export tool and writes monitoring data into files.

ip

Description

This subcommand specifies the IP address or the host name of the SVP and the connection port number.



4-15

dkcsn

4-16

Syntax

ip {ip-address|host-name}[:port-no]

Operands

Operand

ip-address host-name port-no

Description

Specifies the IP address of the SVP.

If the SVP is managed with IPv6 (Internet Protocol Version 6), you must specify the ip-address operand to match the format of IPv6.

Specifies the host name of the SVP.

Alphanumeric characters, hyphen, and period can be specified.

Underscore (_) cannot be specified. The host name can include a hyphen but must be enclosed by double quotation marks (").

Specifies the port number when connecting to the SVP.

Only a number can be specified as a port number. Connect using 1099 when not specifying the port number.

Example

The following example specifies the IP address of the SVP in IPv4 as

158.214.127.170 and the port number as 1099.

ip 158.214.127.170:1099

The following example specifies the IP address of the SVP in IPv6 as

2001:0DB8:0:CD30:123:4567:89AB:CDEF and the port number as 1099.

ip [2001:0DB8:0:CD30:123:4567:89AB:CDEF]:1099

Description

This subcommand specifies the serial number of the system which you will take monitoring data.

Syntax

dkcsn serial-no

Operands

Operand

serial-no

Description

Specifies the serial number of the system from which to take monitoring data.

Example

The following example specifies the serial number of the system as 123456.



retry

dkcsn 123456

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

time=m

count=n

Description

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.

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.

Example

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

ip 158.214.135.57 dkcsn 123456 retry time=5 count=10 login expusr passwd show group Port range 200604010850:200604010910 outpath out option compress apply



4-17

login show

4-18

Description

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

The ip subcommand must execute before the login subcommand executes.

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

Syntax

login userid password

Operands

Operand

userid password

Description

Specifies the user ID for the 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 the Export

Tool on page 4-2

.

Specifies the password of the user.

If the password includes any non-alphanumeric character, the password

ID must be enclosed by double quotation marks (").

Example

This example logs the user expusr into the SVP whose IP address is

158.214.127.170. The password is pswd.

ip 158.214.127.170 login expuser pswd

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 on the SVP

(storing period).

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

Performance Monitor collects data between 1 and 15 days in the SVP. The

show subcommand displays the storing period of monitoring data. Note the following example:



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

If using the range subcommand, you can narrow down the data which you want to save. From is the starting time and To is the ending time. Interval shows the sampling interval. For example, if it is Interval 15min, monitoring data is collected every 15 minutes.

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

Performance window.

group

Figure 4-1 The monitoring term area

The login command must execute before the show subcommand executes.

Syntax show

Outputs

The show subcommand displays the storing period and the sampling interval for the monitoring data. For example, the show subcommand outputs the following information:

Range From: 2006/10/01 01:00 - To: 2006/10/01 15:00

Interval: 1min.

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

Interval indicates the interval at which the monitoring data was collected

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

Description

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

Table 4-3 Operands of the group subcommand and saved monitoring data on page 4-20 shows the monitoring data that can be saved into files by each



4-19

operand, and the saved ZIP files. For details on the monitoring data saved in these files, see the tables listed in the See column.

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

Operand

PhyPG

PhyLDEV

PhyExG

PhyExLDEV

PhyProc

PhyCMPK

PG

LDEV

Monitoring data saved in the file

Saved ZIP file

Usage statistics about parity groups

Usage statistics about volumes

Usage conditions about external volume groups

PhyPG_data.ZIP

1

PhyLDEV_dat.ZIP

1

PhyExg_dat.ZIP

Usage conditions about external volumes

Usage statistics about MPs and data recovery and reconstruction processors

PhyExLDEV_dat/PHY_ExLDEB_xxxxx.ZIP

2

PhyProc_dat.ZIP

1

Usage statistics about write pending rate and cache

PhyCMPK_dat.ZIP

1

Statistics about parity groups, external volume groups

PG_dat.ZIP

Statistics about volumes in parity groups, in external volume groups

LDEV_dat/LDEV_XXXXX.ZIP

2

See

Table 4-5 Files with resource usage and write pending rate statistics on page 4-41

LDEVEachOfCU

Port

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

Statistics about ports

LDEVEachOfCU_dat/LDEV_XXXXX.ZIP

3

Port_dat.ZIP

PortWWN

LU

Statistics about host bus adapters connected to ports

PortWWN_dat.ZIP

Statistics about LUs

LU_dat.ZIP

Table 4-6 Files with parity group and external volume group statistics on page 4-43

Table 4-7 Files with statistics about volumes in parity/external volume groups on page

4-44

Table 4-8 Files with statistics about volumes in parity groups or external volume groups

(volumes controlled by a particular CU) on page

4-46

Table 4-9 Files with statistics about ports on page 4-48

Table 4-10 Files with statistics about host bus adapters connected to ports on page 4-48

Table 4-11 Files with statistics about volumes

(LUs) on page 4-49

4-20



Operand

PPCGWWN


All host bus adapters that are connected to ports

Saved ZIP file

PPCGWWN_dat.ZIP

RemoteCopy

RCLU

RCLDEV

Universal

Replicator

URJNL

URLU

URLDEV

PhyMPPK

Statistics about remote copy operations by

TrueCopy and GAD

(in complete volumes)


TrueCopy and GAD

(for each volume

(LU))

RemoteCopy_dat.ZIP

RCLU_dat.ZIP


TrueCopy and GAD

(for volumes controlled by a particular CU)

RCLDEV_dat/RCLDEV_XXXXX.ZIP

4


Universal Replicator

(for entire volumes)

UniversalReplicator.ZIP



(for journals)

URJNL_dat.ZIP



(for each volume

(LU))

URLU_dat.ZIP



(for volumes controlled by a particular CU)

URLDEV_dat/URLDEV_XXXXX.ZIP

5

MP usage rate of each resource

PhyMPPK_dat.ZIP

See

Table 4-12 Files with statistics about host bus adapters belonging to

SPM groups on page

4-50

Table 4-13 Files with statistics about remote copy operations by TC or

GAD (whole volumes) on page 4-50


GAD (for each volume

(LU)) on page 4-51


GAD (volumes controlled by a particular CU) on page 4-52

Table 4-16 Files with statistics about remote copy operations by UR

(In the whole volumes) on page 4-53


(journals) on page 4-54


(for each volume (LU)) on page 4-55


(volumes controlled by a particular CU) on page

4-56

Table 4-12 Files with statistics about host bus adapters belonging to



4-21

Operand


allocated to MP units

Saved ZIP file

Notes:

1

A ZIP file name beginning with PhyExLDEV_dat/PHY_ExLDEV_.

2

A ZIP file name beginning with LDEV_dat/LDEV_.

3

A ZIP file name beginning with LDEVEachOfCU_dat/LDEV_.

4

A ZIP file name beginning with RCLDEV_dat/RCLDEV_.

5

A ZIP file name beginning with URLDEV_dat/URLDEV_.

See

SPM groups on page

4-50

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-B group RemoteCopy

If you use an operand more than one time in a command file, the last operand takes effect. In the following example, the first group subcommand does not take effect, but the second group subcommand takes effect: group PortWWN CL1-A:CL1-B group PortWWN CL2-A:CL2-B

Syntax

group {PhyPG[parity-group-id]:[parity-group-id]][…]|

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

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

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

PhyProc |

PG [[parity-group-id|exg-id]:

[parity-group-id|exg-id]][…]|

LDEV [[[parity-group-id|exg-id]:

[parity-group-id|exg-id]][…]|

LDEVEachOfCU[[[LDKC-CU-id]:[LDKC-CU-

id]][…]|internal|virtual]|

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]:


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

UniversalReplicator |

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

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


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

}

4-22



Operands

Operand Description

PhyPG

[[parity-group-

id]:[parity-

group-id]][…]

PhyLDEV

[[parity-group-

id]:[parity-

group-id]][…]

PhyExG [[exg-

id]:[exg-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 4-5 Files with resource usage and write pending rate statistics on page 4-41

.

The exported file will contain statistics for up to 15 days.

When you specify variables parity-group-id, you can narrow the range of parity groups whose monitoring data are to be exported. paritygroup-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 parity groups will be exported.

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 4-5 Files with resource usage and write pending rate statistics on page 4-41 .


When you specify variables parity-group-id, you can narrow the range of parity groups whose monitoring data are to be exported. paritygroup-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 volumes will be exported.

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 4-5 Files with resource usage and write pending rate statistics on page 4-41

.

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,



4-23


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 external volume groups will be exported.

PhyExLDEV[[e

xg-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 4-5 Files with resource usage and write pending rate statistics on page 4-41 .

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 external volumes will be exported.

PhyProc

PG [[parity-

group-id|exg-

id]: [parity-

group-id|exg-

id][…]

Use this operand when you want to export the usage rates of MPs, which are displayed in the Monitor Performance window.

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 4-5 Files with resource usage and write pending rate statistics on page 4-41 .


Use this operand when you want to export statistics about parity groups or external 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 4-5 Files with resource usage and write pending rate statistics on page 4-41 .

When you specify variables parity-group-id, or exg-id you can narrow the range of parity groups, or external 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. You can check to which group each LDEV belongs in the Logical Devices window. 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.

Ensure that the parity-group-id, or exg-id value on the left of the colon is smaller than the parity-group-id, or exg-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 parity-group-id, nor exg-id is specified, the statistics of all parity groups and external volume groups will be exported.

4-24



Operand

LDEV

[[[parity-

group-id|exg-

id]: [parity-

group-id||exg-

id]][…] |

internal|

virtual]|

LDEVEachOfC

U[[[LDKC-CU-

id]:[LDKC-CU-

id]][…]|

internal|

virtual]

Description

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 4-9 Files with statistics about ports on page 4-48

.

When you specify variables parity-group-id, or exg-id, you can narrow the range of parity groups, or external 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. You can check to which group each LDEV belongs in the Logical Devices window. 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.

Ensure that the parity-group-id, or exg-id value on the left of the colon is smaller than the parity-group-id, or exg-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.

If neither parity-group-id, nor exg-id is specified, the statistics of all parity groups and external volumes will be exported.

Either one of the following values can be specified:

• parity-group-id or exg-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 4-8 Files with statistics about volumes in parity groups or external volume groups

(volumes controlled by a particular CU) on page 4-46

.

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 or V-VOL.

If LDKC-CU-id, internal or virtual is not specified, the monitoring data of all volumes will be exported. Either one of LDKC-CU-id, internal, or virtual can be specified.



4-25

4-26

Operand

Port [[port-

name]:[port-

name]][…]

PortWWN[[po

rt-name]:

[port-name]]

[…]

LU[[port-

name.host-

group-id]:

[port-

name.host-

group-id]][…]

Description

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, see Table 4-9 Files with statistics about ports on page 4-48 .

When you specify variables port-name, you can narrow the range of ports whose monitoring data are to be exported, where port-name is a port name and the colon (:) indicates a range. For example, CL3a: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-r

For 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 ports will be exported.

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 4-9 Files with statistics about ports on page 4-48 .

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:


CL4-a < … < CL4-r

For example, you can specify PortWWN CL1-C:CL2-A, but you cannot specify PortWWN CL2-A:CL1-C. Also, you can specify PortWWN CL3a:CL3-c, but you cannot specify PortWWN CL3-c:CL3-a.

If port-name is not specified, the monitoring data of all host bus adapters will be exported.

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 4-11 Files with statistics about volumes (LUs) on page 4-49

.

When you specify variables port-name.host-group-id, you can narrow the range of LU paths whose monitoring data are to be exported. portname 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:


CL4-a < … < CL4-r

For 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

LU paths will be exported.

PPCGWWN[[M

onitor-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 4-12 Files with statistics about host bus adapters belonging to SPM groups on page 4-50 .

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 formulas, 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 < RAID5

If monitor-target-name is not specified, the monitoring data of all host bus adapters will be exported.

RemoteCopy

Use this operand when you want to export statistics about remote copy operations of TrueCopy or global-active device. By using this operand, you can export monitoring data about remote copy operations performed by TC and GAD 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 4-13 Files with statistics about remote copy operations by TC or GAD (whole volumes) on page 4-50

.

RCLU[[port-

name.host-

group-id]:

[port-

name.host-

group-id]][…]

Use this operand when you want to export statistics about remote copy operations of TrueCopy or global-active device. By using this operand, you can export monitoring data about remote copy operations performed by TC and GAD 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 4-14 Files with statistics about remote copy operations by TC or GAD (for each volume

(LU)) on page 4-51

.



4-27


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.



CL4-a < … < CL4-r

For 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 volumes (LUs) will be exported.

RCLDEV[[LDK

C-CU-id]:

[LDKC-CU-id]]

[…]|

Use this operand when you want to export statistics about remote copy operations of TrueCopy or global-active device. By using this operand, you can export monitoring data about remote copy operations performed by TC and GAD 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 4-15 Files with statistics about remote copy operations by TC or GAD (volumes controlled by a particular CU) on page 4-52 .



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 volumes will be exported.

UniversalRepl icator

URJNL[[JNL-

group-id]:[JNL-

group-id]][…]

Use this operand when you want to export statistics about remote copy operations of UR. By using this operand, you can export monitoring data about remote copy operations performed by Universal Replicator 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 4-16 Files with statistics about remote copy operations by UR (In the whole volumes) on page 4-53 .

Use this operand when you want to export statistics about remote copy operations of UR. By using this operand, you can export monitoring data about remote copy operations performed by Universal Replicator 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 4-17 Files with statistics about remote copy operations by UR (journals) on page 4-54

.

4-28




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 journal volumes will be exported.

URLU[[port-

name.host-

group-id]:

[port-

name.host-

group-id]][…]

URLDEV

[[LDKC-CU-id]:

[LDKC-CU-id]]

[…]

Use this operand when you want to export statistics about remote copy operations of UR. By using this operand, you can export monitoring data about remote copy operations performed by Universal Replicator 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 4-18 Files with statistics about remote copy operations by UR (for each volume (LU)) on page 4-55 .

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.



CL4-a < … < CL4-r

For 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 volumes (LUs) will be exported.

Use this operand when you want to export statistics about remote copy operations which of UR. By using this operand, you can export monitoring data about remote copy operations performed by Universal

Replicator 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 4-19 Files with statistics about remote copy operations by UR (volumes controlled by a particular CU) on page

4-56

.



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.



4-29

range

Operand

PhyMPPK

Description

If LDKC-CU-id is not specified, the monitoring data of all volumes will be exported.

Use this operand when you want to export statistics about the MP usage rate of each resource allocated to MP units. 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 4-12 Files with statistics about host bus adapters belonging to SPM groups on page 4-50

Examples

The following example exports statistics about host bus adapters: 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

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 login subcommand must execute before the range subcommand executes.

4-30



Syntax

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 "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 4-2 Starting and Ending Time for Collecting Monitoring Data

Operand

yyyyMMddhhm m

+hhmm

-hhmm

Description

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.

To save monitoring data up to the sampling end time, omit

yyyyMMddhhmm on the right of the colon. If you specify

yyyyMMddhhmm on the right of the colon, specify date and time at least 30 minutes earlier than the current time. Otherwise, an Out of range error may occur.

Adds time (hhmm) to yyyyMMddhhmm if yyyyMMddhhmm is specified.

For example, 201306230000+0130 indicates June 23, 2013. 01:30.

Adds time to the starting time for collecting monitoring data, if

yyyyMMddhhmm is omitted.

Subtracts time (hhmm) from yyyyMMddhhmm if yyyyMMddhhmm is specified. For example, 201306230000-0130 indicates June 22, 2013.

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



4-31


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.

Examples

The following examples assume that:

• The starting time for collecting monitoring data is Jan. 1, 2013, 00:00.

• The ending time for collecting monitoring data is Jan. 2, 2013, 00:00.

range 201301010930:201301011730

The Export Tool saves monitoring data within the range of Jan. 1,

9:30-17:30.

range 201301010930:

The Export Tool saves monitoring data within the range of Jan. 1, 9:30 to

Jan. 2, 00:00.

range:201301011730


0:00-17:30.

range +0001:


Jan. 2, 00:00.

range -0001:

The Export Tool saves monitoring data within the range of Jan. 1, 23:59 to Jan. 2, 00:00.

range :+0001


0:00-00:01.

range :-0001


0:00-23:59.

4-32



outpath

range +0101:-0101


1:01-22:59.

range 201301010900+0130:201301011700-0130


10:30-15:30.

range 201301010900-0130:201301011700+0130


7:30-18:30.

range 201301010900-0130:


Jan. 2, 00:00.

Description

The outpath subcommand specifies the directory to which monitoring data will be exported.

Syntax

outpath [path]

Operands

Operand

path

Description

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 for example, \\.

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.

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



4-33

option

Description

This subcommand specifies the following:

• whether to compress monitoring data in ZIP files

• whether to overwrite or delete existing files and directories when saving monitoring data in files

Syntax

option [compress|nocompress] [ask|clear|noclear]

Operands

The two operands in the following table specify whether to compress CSV files into ZIP files. If none of these operands is specified, compress is assumed.

Operand compress nocompress

Description

Compresses data in ZIP files. To extract CSV files out of a ZIP file, you will need to decompress the ZIP file.

Does not compress data in ZIP files and saves data in CSV files.

The three operands in the following table specify whether to overwrite or delete an existing file or directory when the Export Tool saves files. If none of these operands is specified, the ask operand is assumed.

ask

Operand clear noclear

Description

Displays a message that asks whether to delete existing files or directories.

Deletes existing files and directories and then saves monitoring data in files.

Overwrites existing files and directories.

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.

4-34



set

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

Description

The set subcommand starts or ends monitoring the storage system (for example, starts or ends collecting performance statistics). The set subcommand also specifies the sampling interval (interval of collecting statistics).

If you want to use the set subcommand, you must use the login

subcommand (see login on page 4-18

to log into the 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 logged into the SVP in Modify mode.

• Maintenance operations are being performed on the SVP.

If an error occurs, do the following:

• Ensure that all users who are logged into the SVP are not in Modify mode.

If any user is logged into the SVP in Modify mode, ask the user to switch to View mode.

• Wait until maintenance operations finish on the SVP, so that the set subcommand can execute.

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, see Notes in

Using the Export Tool on page 4-9

.

• When the set subcommand starts or ends the monitoring or changes the sampling 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 Refresh on the menu bar of the Device Manager - Storage Navigator main window.



4-35

help

4-36

• If you change the specified sampling interval during a monitoring, the previously collected monitoring data will be deleted.

Syntax

set [switch={m|off}]

Operands

Operand

switch={m|

off}

Description

To start monitoring, specify the sampling interval (interval of collecting statistics) of monitoring data at m. Specify a value between 1 and 15 in minutes. m is the sampling interval by Performance Monitor.

To end monitoring, specify off.

If this operand is omitted, the set subcommand does not make settings for starting or ending monitoring.

Examples

The following command file saves port statistics and then ends monitoring ports: ip 158.214.135.57 dkcsn 123456 login expusr passwd show group Port range 200604010850:200604010910 apply set switch=off

The following command file starts monitoring remote copy operations. The sampling time interval is 10 minutes: ip 158.214.135.57 dkcsn 123456 login expusr passwd set switch=10

Description

The help subcommand displays the online help for subcommands.

If you want to view the online help, create a batch file and a command file that are used exclusively for displaying the online help. For details, see the following example.

Syntax help



Java

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/

JSanRmiApiEx.jar;./lib/JSanRmiServerUx.jar" -Xmx536870912 -

Dmd.command=cmdHelp.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain<CR+LF> pause<CR+LF>

In the preceding script, <CR+LF> indicates the end of a command line.

In this example, you must do one of the following to view the online Help:

• Double-click runHelp.bat.

• Go to the c:\export directory at the command prompt, enter runHelp or runHelp.bat, and then press Enter.

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

class-path propertyparameters

Description

Specifies the path to the class file of the Export Tool.

The path must be enclosed in double quotation marks (").

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

Specifies 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 the SVP through a proxy host.

• -Dhttp.proxyPort=port-number-of-proxy-host



4-37

4-38


Specifies the port number of a proxy host. You must specify this parameter if the computer that runs the Export Tool communicates with the SVP through 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 the installed memory size is smaller than the recommended size of the PC running Device Manager - Storage

Navigator, you must install more memory before executing the

Export Tool.

If the installed memory size is larger than the recommended memory size of the PC running Device Manager - 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-file

Specifies the path to the command file

• -Dmd.logpath=path-to-log-file

Specifies 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-file

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

• -Dmd.rmitimeout=timeout(min.)

Specifies the timeout value for communication between the export tool and the SVP:

¢

¢

¢

Default: 20 minutes

Minimum: 1 minute

Maximum: 1,440 minutes (24 hours)

If a request does not come from the export tool within the timeout period, the SVP determines that execution has stopped and disconnects the session with the export tool. Therefore, if the machine on which the export tool is running is slow, export tool sessions may be disconnected unexpectedly. To prevent this from occurring, increase the timeout period by entering a larger value in this parameter.

Examples

The following example assumes that the computer running the Export Tool communicates with the SVP through 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/JSanRmiApiEx.jar;

./lib/JSanRmiServerUx.jar"

-Dhttp.proxyHost=Jupiter -Dhttp.proxyPort=8080 -Xmx536870912

-Dmd.command=command.txt

-Dmd.rmitimeout=20

-Dmd.logpath=log sanproject.getmondat.RJMdMain <CR+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: java -classpath "./lib/JSanExport.jar;./lib/JSanRmiApiEx.jar;\

./lib/JSanRmiServerUx.jar"

-Xmx536870912 -Dmd.command=command.txt -Dmd.logfile=export.log

-Dmd.logpath=log sanproject.getmondat.RJMdMain<CR+LF>

In this script, <CR+LF> indicates the end of a command line.

Exported files

The 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 Tool

The 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, see the tables indicated in the links in the Monitoring data column.

The monitoring data shows the average value of sampling interval. The sampling intervals are 1 to 15 minutes that can be set in the Edit

Monitoring Switch window.

Table 4-4 Performance management windows and monitoring data saved by the Export Tool

GUI operation

Select Parity Groups from Object list in

Performance Objects field in Monitor

Performance window.

Select Logical Devices (Base) from

Object list in Performance Objects field in Monitor Performance window.

Monitoring data

Resource usage and write-pending rate statistics on page 4-41

Parity group and external volume group statistics on page 4-43


Statistics for volumes in parity/external volume groups on page 4-44



4-39

GUI operation Monitoring data

Volumes in parity groups or external volume groups (volumes controlled by a particular

CU) on page 4-46

Remote copy by TC or GAD (volumes controlled by a particular CU) on page 4-52

Select Logical Devices (TC/GAD) from


Select Logical Devices (UR) from


Select Cache from Object list in



Select Controller from Object list in



Select Fibre Port from Object list in



Select LUN Base from Object list in



Select LUN (TC/GAD) from Object list in Performance Objects field in

Monitor Performance window.

Select LUN (UR) from Object list in



Select WWN from Object list in



Remote copy by UR (volumes controlled by a particular CU) on page 4-56



Port statistics on page 4-47

Volumes (LU) statistics on page 4-48

Remote copy operations by TC or GAD (for each volume (LU)) on page 4-51

Remote copy by UR (for each volume (LU)) on page 4-55

Host bus adapters connected to ports statistics on page 4-48

All host bus adapters connected to ports on page 4-49

Remote copy by UR (journals) on page 4-54

Select Journal from Object list in



Select Entire Storage System (TC/

GAD) from Object list in Performance

Objects field in Monitor Performance window.

Select Entire Storage System (UR) from Object list in Performance

Objects field in Monitor Performance window.

Remote copy operations by TC or GAD (whole volumes) on page 4-50

Remote copy by UR (whole volumes) on page

4-53

4-40



Resource usage and write-pending rate statistics

The 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 4-5 Files with resource usage and write pending rate statistics

ZIP file CSV file Data saved in the file

PhyPG_dat.ZIP

PhyLDEV_dat.ZIP

PhyExG_dat.ZIP

PHY_PG.csv

PHY_LDEV_x-y.csv

PHY_LDEV_SI_xy.csv

PHY_ExG_Response.csv

Usage rates for parity groups

Usage rates for volumes in a parity group.

Usage rates for ShadowImage volumes in a parity group.

If external storage volumes are mapped to the volume groups of

Hitachi Virtual Storage Platform G200,

G400, G600, G800, this file includes the average response time for the volume groups including external storage volumes (milliseconds).

PHY_ExG_Trans.csv

PHY_ExG_Read_Response.c

sv



G400, G600, G800, this file includes the amount of transferred data for volume groups including external storage volumes (KB/sec).



G400, G600, G800, this file includes the average read response time for the volume groups including external storage volumes (milliseconds).

PHY_ExG_Write_Response.c

sv



G400, G600, G800, this file includes the average write response time for the volume groups including external storage volumes (milliseconds).

PHY_ExG_Read_Trans.csv



G400, G600, G800, this file includes the amount of read transferred data for volume groups including external storage volumes (KB/sec).

PHY_ExG_Write_Trans.csv



G400, G600, G800, this file includes



4-41

ZIP file CSV file

PhyExLDEV_dat/

PHY_ExLDEV_Resp onse.ZIP

PHY_ExLDEV_Response_xy.csv

Data saved in the file

the amount of write transferred data for volume groups including external storage volumes (KB/sec).



G400, G600, G800, this file includes the average response time for external storage volumes in the volume group x-y (milliseconds).

PhyExLDEV_dat/

PHY_ExLDEV_Tran s.ZIP

PHY_ExLDEV_Trans_x-y.csv If external storage volumes are mapped to the volume groups of


G400, G600, G800, this file includes the amount of data transferred for external storage volumes in the volume group x-y (KB/sec).

PhyExLDEV_dat/

PHY_ExLDEV_Read

_Response.ZIP

PHY_ExLDEV_Read_Respon se_x-y.csv

PhyExLDEV_dat/

PHY_ExLDEV_Writ e_Response.ZIP

PHY_ExLDEV_Write_Respon se_x-y.csv



G400, G600, G800, this file includes the average reading response time for external storage volumes in the volume group x-y (milliseconds).



G400, G600, G800, this file includes the average writing response time for external storage volumes in the volume group x-y (milliseconds).

PhyExLDEV_dat/

PHY_ExLDEV_Read

_Trans.ZIP

PHY_ExLDEV_Read_Trans_x

-y.csv



G400, G600, G800, this file includes the amount of reading data transferred for external storage volumes in the volume group x-y (KB/ sec).

PhyExLDEV_dat/

PHY_ExLDEV_Writ e_Trans.ZIP

PHY_ExLDEV_Write_Trans_ x-y.csv



G400, G600, G800, this file includes the amount of writing data transferred for external storage volumes in the volume group x-y (KB/sec).

Usage rates for MPs.

PhyProc_dat.ZIP

PHY_MP.csv

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

4-42



Parity group and external volume group statistics


Monitor Performance window that can be exported to files using the Export

Tool. These files contain statistics about parity groups and external volume groups.

Table 4-6 Files with parity group and external volume group statistics


PG_dat.ZI

P

PG_IOPS.csv

PG_TransRate.csv

Number of read and write operations per second

Size of data transferred per second (KB/sec)

PG_Read_TransRate.cs

v

Size of read data transferred per second (KB/sec)

PG_Write_TransRate.cs

v

Size of write data transferred per second (KB/sec)

PG_Read_IOPS.csv

Number of read operations per second

PG_Rnd_Read_IOPS.cs

v

PG_Write_IOPS.csv

Number of random read operations per second

Number of write operations per second

PG_Seq_Write_IOPS.cs

v

Number of sequential write operations per second

PG_Rnd_Write_IOPS.cs

v

Number of random write operations per second

PG_Read_Hit.csv

Read hit ratio

PG_Seq_Read_Hit.csv

Read hit ratio in sequential access mode

PG_Rnd_Read_Hit.csv

Read hit ratio in random access mode

PG_Write_Hit.csv

Write hit ratio

PG_Seq_Write_Hit.csv

Write hit ratio in sequential access mode

PG_Rnd_Write_Hit.csv

Write hit ratio in random access mode

PG_BackTrans.csv

Number of data transfer operations between cache memory and data drives (for example, parity groups or external volume groups) per second

PG_C2D_Trans.csv

PG_D2CS_Trans.csv

PG_D2CR_Trans.csv

Number of data transfer operations from cache memory and data drives (for example, parity groups or external volume groups) per second

Number of data transfer operations from data drives

(for example, parity groups or external volume groups) per second to cache memory in sequential access mode

Number of data transfer operations from data drives

(for example, parity groups or external volume groups) per second to cache memory in random access mode



4-43


PG_Response.csv

PG_Read_Response.cs

v

PG_Write_Response.cs

v


Average response time (microsecond) at parity groups or external volume groups

Average read response time (microsecond) at parity groups or external volume groups

Average write response time (microsecond) at parity groups or external volume groups

Note: The parity group number is output in the column header of each performance value in these files.

Statistics for volumes in parity/external volume groups



Tool. These files contain statistics about volumes in parity groups or in external volume groups.

Table 4-7 Files with statistics about volumes in parity/external volume groups


LDEV_dat/

LDEV_IOPS.ZIP

LDEV_dat/

LDEV_TransRate.ZIP

LDEV_IOPS_x-y.csv

LDEV_TransRate_x-y.csv

LDEV_dat/

LDEV_Read_TransRate.

ZIP

LDEV_Read_TransRate_xy.csv

Number of read and write operations per second

Size of data transferred per second (KB/sec)

Size of read data transferred per second (KB/sec)

LDEV_dat/

LDEV_Read_TransRate.

ZIP

LDEV_Write_TransRate_xy.csv

Size of write data transferred per second (KB/sec)

LDEV_dat/

LDEV_Read_IOPS.ZIP

LDEV_dat/

LDEV_Seq_Read_IOPS.

ZIP

LDEV_dat/

LDEV_Rnd_Read_IOPS.

ZIP

LDEV_dat/

LDEV_Write_IOPS.ZIP

LDEV_dat/

LDEV_Seq_Write_IOPS.

ZIP

LDEV_Read_IOPS_x-y.csv

Number of read operations per

LDEV_Seq_Read_IOPS_xy.csv

LDEV_Rnd_Read_IOPS_xy.csv

second

Number of sequential read operations per second

Number of random read operations per second

LDEV_Write_IOPS_x-y.csv

Number of write operations per second

LDEV_Seq_Write_IOPS_xy.csv

Number of sequential write operations per second

4-44




LDEV_dat/

LDEV_Rnd_Write_IOPS.

ZIP

LDEV_Rnd_Write_IOPS_xy.csv

LDEV_dat/

LDEV_Read_Hit.ZIP

LDEV_Read_Hit_x-y.csv

LDEV_dat/

LDEV_Seq_Read_Hit.ZI

P

LDEV_dat/

LDEV_Rnd_Read_Hit.ZI

P

LDEV_Seq_Read_Hit_xy.csv

LDEV_Rnd_Read_Hit_xy.csv

Number of random write operations per second

Read hit ratio

Read hit ratio in sequential access mode

Read hit ratio in random access mode

LDEV_dat/

LDEV_Write_Hit.ZIP

LDEV_dat/

LDEV_Seq_Write_Hit.ZI

P

LDEV_Write_Hit_x-y.csv

LDEV_Seq_Write_Hit_xy.csv

LDEV_dat/

LDEV_D2CR_Trans.ZIP

Write hit ratio

Write hit ratio in sequential access mode

LDEV_dat/

LDEV_Rnd_Write_Hit.ZI

P

LDEV_Rnd_Write_Hit_xy.csv

LDEV_dat/

LDEV_BackTrans.ZIP

LDEV_dat/

LDEV_C2D_Trans.ZIP

LDEV_BackTrans_x-y.csv

Write hit ratio in random access mode

Number of data transfer operations between cache memory and data drives (for example, volumes) per second

LDEV_C2D_Trans_x-y.csv

Number of data transfer operations from cache memory and data drives (for example, volumes) per second

LDEV_dat/

LDEV_D2CS_Trans.ZIP

LDEV_D2CS_Trans_x-y.csv Number of data transfer operations from data drives (for example, volumes) per second to cache memory in sequential access mode

LDEV_D2CR_Trans_x-y.csv Number of data transfer operations from data drives (for example, volumes) per second to cache memory in random access mode

LDEV_dat/

LDEV_Response.ZIP

LDEV_dat/

LDEV_Read_Response.

ZIP

LDEV_dat/

LDEV_Write_Response.

ZIP

LDEV_Response_x-y.csv

LDEV_Read_Response_xy.csv

LDEV_Write_Response_xy.csv

Average response time

(microseconds) at volumes

Average read response time


Average write response time




4-45


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.

Volumes in parity groups or external volume groups (volumes controlled by a particular CU)



Tool. These files contain statistics about volumes in parity groups or external volume groups (volumes controlled by a particular CU).

Table 4-8 Files with statistics about volumes in parity groups or external volume groups (volumes controlled by a particular CU)


LDEVEachOfCU_dat/

LDEV_Read_TransRate.ZIP

LDEV_Read_TransRatexx.csv The size of read data transferred per second (KB/ sec)

LDEVEachOfCU_dat/

LDEV_Write_TransRate.ZIP

LDEV_Write_TransRatexx.csv The size of write data transferred per second (KB/ sec)

LDEVEachOfCU_dat/

LDEV_Read_Response.ZIP

LDEVEachOfCU_dat/

LDEV_Write_Response.ZIP

LDEVEachOfCU_dat/

LDEV_IOPS.ZIP

LDEVEachOfCU_dat/

LDEV_TransRate.ZIP

LDEVEachOfCU_dat/

LDEV_Read_IOPS.ZIP

LDEVEachOfCU_dat/

LDEV_Seq_Read_IOPS.ZIP

LDEVEachOfCU_dat/

LDEV_Rnd_Read_IOPS.ZIP

LDEV_Read_Responsexx.csv

The average read response time (microseconds) at volumes

LDEV_Write_Responsexx.csv The average write response time (microseconds) at volumes

LDEV_IOPSxx.csv

LDEV_TransRatexx.csv

The number of read and write operations per second

The size of data transferred per second (KB/sec)

LDEV_Read_IOPSxx.csv

The number of read operations per second

LDEV_Seq_Read_IOPSxx.csv The number of sequential read operations per second

LDEV_Rnd_Read_IOPSxx.csv The number of random read operations per second

LDEVEachOfCU_dat/

LDEV_Write_IOPS.ZIP

LDEVEachOfCU_dat/

LDEV_Seq_Write_IOPS.ZIP

LDEV_Write_IOPSxx.csv

The number of write operations per second

LDEV_Seq_Write_IOPSxx.csv The number of sequential write operations per second

LDEVEachOfCU_dat/

LDEV_Rnd_Write_IOPS.ZIP

LDEV_Rnd_Write_IOPSxx.csv The number of random write operations per second

4-46




LDEVEachOfCU_dat/

LDEV_Read_Hit.ZIP

LDEVEachOfCU_dat/

LDEV_Seq_Read_Hit.ZIP

LDEVEachOfCU_dat/

LDEV_Rnd_Read_Hit.ZIP

LDEVEachOfCU_dat/

LDEV_Write_Hit.ZIP

LDEVEachOfCU_dat/

LDEV_Seq_Write_Hit.ZIP

LDEVEachOfCU_dat/

LDEV_Rnd_Write_Hit.ZIP

LDEVEachOfCU_dat/

LDEV_BackTrans.ZIP

LDEVEachOfCU_dat/

LDEV_C2D_Trans.ZIP

LDEV_Read_Hitxx.csv

LDEV_Seq_Read_Hitxx.csv

LDEV_Rnd_Read_Hitxx.csv

LDEV_Write_Hitxx.csv

LDEV_Seq_Write_Hitxx.csv

LDEV_Rnd_Write_Hitxx.csv

LDEV_BackTransxx.csv

LDEV_C2D_Transxx.csv

The read hit ratio

The read hit ratio in sequential access mode

The read hit ratio in random access mode

The write hit ratio

The write hit ratio in sequential access mode

The write hit ratio in random access mode

The number of data transfer operations per second between cache memories and data drives (for example, volumes)

The number of data transfer operations per second from cache memories and data drives (for example, volumes)

LDEVEachOfCU_dat/

LDEV_D2CS_Trans.ZIP

LDEVEachOfCU_dat/

LDEV_D2CR_Trans.ZIP

LDEV_D2CS_Transxx.csv

LDEV_D2CR_Transxx.csv

The number of data transfer operations per second from data drives (for example, volumes) to cache memories in sequential access mode

The number of data transfer operations per second from data drives (for example, volumes) to cache memories in random access mode

LDEVEachOfCU_dat/

LDEV_Response.ZIP

LDEV_Responsexx.csv

The average response time


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

Port statistics



Tool. These files contain statistics about ports.



4-47

Table 4-9 Files with statistics about ports

ZIP file

Port_dat.

ZIP

CSV file Data saved in the file

Port_IOPS.csv

Port_KBPS.csv

The number of read and write operations per second at ports during Target connection

The size of data transferred per second at ports during Target connection (KB/sec)

Port_Response.csv

The average response time (microseconds) at ports during Target connection

Port_Initiator_IOPS.cs

v

The number of read and write operations per second at ports during Initiator connection

Port_Initiator_KBPS.c

sv

Port_Initiator_Respon se.csv

The size of data transferred per second at ports during Initiator connection (KB/sec)

The average response time (microseconds) at ports during Initiator connection

Host bus adapters connected to ports statistics



Tool. These files contain statistics about host bus adapters connected to ports.

Table 4-10 Files with statistics about host bus adapters connected to ports


PortWWN_dat.

ZIP

PortWWN_xx_IOPS.cs

v

PortWWN_xx_KBPS.c

sv

The I/O rate (that is, the number of read and write operations per second) for HBAs that are connected to a port

The size of data transferred per second (KB/sec) between a port and the HBAs connected to that port

PortWWN_xx_Respon se.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).

Volumes (LU) statistics



Tool. These files contain statistics about volumes (LUs).

4-48



Table 4-11 Files with statistics about volumes (LUs)


LU_dat.Z

IP

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_TransRat e.csv

The size of read data transferred per second (KB/sec)

LU_Write_TransRat e.csv

The size of write data transferred per second (KB/sec)

LU_Read_Response

.csv

The average read response time (microseconds)

LU_Write_Respons e.csv

The average write response time (microseconds)

The number of sequential read operations per second LU_Seq_Read_IOP

S.csv

LU_Rnd_Read_IOP

S.csv

LU_Seq_Write_IOP

S.csv

LU_Rnd_Write_IOP

S.csv

LU_Seq_Read_Hit.

csv

LU_Rnd_Read_Hit.

csv

LU_Seq_Write_Hit.

csv

LU_Rnd_Write_Hit.

csv

The number of random read operations per second

The number of sequential write operations per second

The number of random write operations per second

The read hit ratio in sequential access mode

The read hit ratio in random access mode

The write hit ratio in sequential access mode

The write hit ratio in random access mode

LU_C2D_Trans.csv The number of data transfer operations per second from cache memories to data drives (for example, LUs)

LU_D2CS_Trans.cs

v

LU_D2CR_Trans.cs

v

LU_Response.csv

The number of data transfer operations per second from data drives (for example, LUs) to cache memories in sequential access mode

The number of data transfer operations per second from data drives (for example, LUs) to cache memories in random access mode

The average response time (microseconds) at volumes

(LUs)

All host bus adapters connected to ports





4-49

Tool. These files contain statistics about all host bus adapters connected to ports.

Table 4-12 Files with statistics about host bus adapters belonging to SPM groups


PPCGWWN_da t.ZIP

PPCGWWN_xx_IOPS.csv

I/O rate (that is, the number of read and write operations per second) for HBAs belonging to an SPM group

PPCGWWN_xx_KBPS.csv

Transfer rate (KB/sec) for HBAs belonging to an SPM group

PPCGWWN_xx_Response.csv Average response time (microseconds) for HBAs belonging to an SPM group

PPCGWWN_NotGrouped_IOP

S.csv

I/O rate (that is, the number of read and write operations per second) for HBAs that do not belong to any SPM group

PPCGWWN_NotGrouped_KBP

S.csv

PPCGWWN_NotGrouped_Res ponse.csv

Transfer rate (KB/sec) for HBAs that do not belong to any SPM group

Average response time (microseconds), for HBAs that do not belong to any SPM group

Notes:

• The letters "xx" in CSV filenames indicate the name of an SPM group.

• If files are exported to a Windows computer, CSV filenames may end with numbers

(for example, PPCGWWN_mygroup_IOPS-1.csv and

PPCGWWN_MyGroup_IOPS-2.csv).

Remote copy operations by TC or GAD (whole volumes)

The following table shows the file names and types of information on the

Usage Monitor tab in the TC or GAD window that can be exported to files using the Export Tool. These files contain statistics about remote copy operations (whole volumes) by TrueCopy and global-active device.

Table 4-13 Files with statistics about remote copy operations by TC or GAD

(whole volumes)


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.

4-50




• 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

(for example, 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

Remote copy operations by TC or GAD (for each volume (LU))


Usage Monitor tab in the TC or GAD 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 global-active device.


(for each volume (LU))


RCLU_dat.Z

IP

RCLU_All_RIO.csv

RCLU_All_Write.csv

RCLU_RIO_Error.csv

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

RCLU_Initial_Copy_Transfer.csv The average transfer rate (KB/sec) for initial copy remote I/Os

RCLU_Initial_Copy_Response.cs

v

RCLU_Update_Copy_RIO.csv

The average response time (milliseconds) for the initial copy of each volume (LU)

The number of update copy remote I/Os

RCLU_Update_Copy_Transfer.cs

v

The average transfer rate (KB/sec) for update copy remote I/Os

RCLU_Update_Copy_Response.

csv

RCLU_Pair_Synchronized.csv

The average response time (milliseconds) for the update copy of each volume (LU)

The percentage of completion of copy operations (for example, number of synchronized pairs / total number of pairs)



4-51


RCLU_Out_of_Tracks.csv


The number of tracks that have not yet been copied by the initial copy or resync copy operation

Remote copy by TC or GAD (volumes controlled by a particular CU)


Usage Monitor tab in the TC or GAD 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 globalactive device.


(volumes controlled by a particular CU)



RCLDEV_dat/

RCLDEV_All_RIO.ZIP

RCLDEV_All_RIO_xx.csv

The total number of remote I/Os (read and write operations)

The total number of remote write I/Os

RCLDEV_dat/

RCLDEV_All_Write.ZIP

RCLDEV_All_Write_xx.csv

RCLDEV_dat/

RCLDEV_RIO_Error.ZIP

RCLDEV_dat/

RCLDEV_Initial_Copy_RIO.ZIP

RCLDEV_dat/

RCLDEV_Initial_Copy_Transfer.

ZIP

RCLDEV_RIO_Error_xx.csv

The number of errors that occur during remote I/O

RCLDEV_Initial_Copy_RIO_xx.csv The number of initial copy remote

I/Os

RCLDEV_Initial_Copy_Transfer_x x.csv

The average transfer rate (KB/ sec) for initial copy remote I/Os

RCLDEV_dat/

RCLDEV_Initial_Copy_Response

.ZIP

RCLDEV_Initial_Copy_Response_ xx.csv


(milliseconds) for initial copy at volumes

RCLDEV_dat/

RCLDEV_Update_Copy_RIO.ZIP

RCLDEV_Update_Copy_RIO_xx.cs

v

The number of update copy remote

I/Os

RCLDEV_dat/

RCLDEV_Update_Copy_Transfer

.ZIP

RCLDEV_Update_Copy_Transfer_ xx.csv

The average transfer rate (KB/ sec) for update copy remote I/Os

4-52





RCLDEV_dat/

RCLDEV_Update_Copy_Respons e.ZIP

RCLDEV_dat/

RCLDEV_Pair_Synchronized.ZIP

RCLDEV_dat/

RCLDEV_Out_of_Tracks.ZIP

RCLDEV_Update_Copy_Response

_xx.csv


(milliseconds) for the update copy at volumes

RCLDEV_Pair_Synchronized_xx.cs

v

The percentage of completion of copy operations (for example, number of synchronized pairs / total number of pairs)

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.

Remote copy by UR (whole volumes)


Usage Monitor tab in the UR window that can be exported to files using the

Export Tool. These files contain statistics about remote copy operations

(whole volumes) by Universal Replicator.

Table 4-16 Files with statistics about remote copy operations by UR (In the whole volumes)


UniversalReplicato r_dat.zip

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



4-53


• 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

Remote copy by UR (journals)




(journals) by Universal Replicator.

Table 4-17 Files with statistics about remote copy operations by UR

(journals)


URJNL_dat.

ZIP

URJNL_Write_Record.csv

URJNL_Write_Transfer.csv

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) URJNL_Initial_Copy_Hit.csv

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

v

URJNL_M-

JNL_Asynchronous_Copy_Response.c

sv

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

URJNL_R-JNL_Asynchronous_RIO.csv The number of asynchronous remote I/Os per second at the secondary storage system

4-54




URJNL_dat.

ZIP

(continued)

URJNL_R-

JNL_Asynchronous_Journal.csv

URJNL_R-

JNL_Asynchronous_Copy_Transfer.cs

v

URJNL_R-

JNL_Asynchronous_Copy_Response.c

sv

URJNL_M-JNL_Data_Used_Rate.csv

URJNL_M-

JNL_Meta_Data_Used_Rate.csv

URJNL_R-JNL_Data_Used_Rate.csv

URJNL_R-

JNL_Meta_Data_Used_Rate.csv


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

Data usage rate (percent) for master journals

Metadata usage rate (percent) for master journals

Data usage rate (percent) for restore journals

Metadata usage rate (percent) for restore journals

Remote copy by UR (for each volume (LU))



Export Tool. These files contain statistics about remote copy operations (for each volume (LU)) by Universal Replicator.

Table 4-18 Files with statistics about remote copy operations by UR (for each volume (LU))


URLU_dat.Z

IP

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


URLU_Write_Hit.csv

The number of write hit records per second

URLU_Read_Transfer.cs

v

URLU_Write_Transfer.cs

v

URLU_Initial_Copy_Hit.c

sv

URLU_Initial_Copy_Tran sfer.csv

The amount of data that are read per second

(KB/sec)

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



4-55

Remote copy by UR (volumes controlled by a particular CU)




(volumes controlled by a particular CU) by Universal Replicator.

Table 4-19 Files with statistics about remote copy operations by UR

(volumes controlled by a particular CU)


URLDEV_dat/

URLDEV_Read_Record.ZIP

URLDEV_dat/

URLDEV_Read_Hit.ZIP

URLDEV_dat/

URLDEV_Write_Record.ZIP

URLDEV_Read_Record_xx.cs

v

URLDEV_Read_Hit_xx.csv

URLDEV_Write_Record_xx.cs

v

The number of read I/Os per second

The number of read hit records per second


URLDEV_dat/

URLDEV_Write_Hit.ZIP

URLDEV_dat/

URLDEV_Read_Transfer.ZI

P

URLDEV_Write_Hit_xx.csv

URLDEV_Read_Transfer_xx.c

sv

The number of write hit records per second

The amount of data that are read per second (KB/sec)

URLDEV_dat/

URLDEV_Write_Transfer.ZI

P

URLDEV_Write_Transfer_xx.c

sv

URLDEV_dat/

URLDEV_Initial_Copy_Hit.Z

IP

URLDEV_Initial_Copy_Hit_xx

.csv

URLDEV_dat/

URLDEV_Initial_Copy_Tran sfer.ZIP

URLDEV_Initial_Copy_Transf er_xx.csv

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

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.

Causes of Invalid Monitoring Data

If the value of monitoring data in CSV files is less than 0 (zero), consider the following causes:

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.

4-56



Invalid values of monitoring data

Probable causes

• 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

(TC, UR, GAD). For details about the files, see

Table 4-13 Files with statistics about remote copy operations by TC or GAD

(whole volumes) on page 4-50

,

Table 4-16 Files with statistics about remote copy operations by UR (In the whole volumes) on page 4-53

, and

Table 4-17 Files with statistics about remote copy operations by UR (journals) on page 4-54 .

• If no CU is specified as a monitoring target, the value (-1) is displayed as the monitoring data.


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 the data of the SVP is updated while the monitoring data is being collected, the collected monitoring data near the collection start time is (-4).


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.



4-57

4-58



5

Server Priority Manager operations

This chapter describes and provides instructions for managing host I/O activity using Hitachi Server Priority Manager.

□

Overview of Server Priority Manager

□

Use cases for Server Priority Manager

□

Cautions and restrictions for Server Priority Manager

□

Implementing Server Priority Manager: one-to-one connections

□

Implementing Server Priority Manager: many-to-many connections

□

Managing host bus adapters

□

Working with SPM groups

Server Priority Manager operations


5-1

Overview of Server Priority Manager

Server Priority Manager allows you to set upper limits of the number of accesses from the server to storage system as well as the amount of data transfer. The upper limits are automatically disabled when the traffic between the server and storage system drops to user-defined levels.

Using Server Priority Manager you can designate prioritized ports (for example, for production servers) and non-prioritized ports (for example, for development servers) and set upper limits and thresholds for the I/O activity of these ports to prioritize I/O operations to host servers requiring highthroughput I/O operations and prevent low-priority activities from negatively impacting high-priority activities.

•

Performance of high-priority hosts on page 5-2

•

Upper-limit control on page 5-2

•

Threshold control on page 5-3

•

About I/O rates and transfer rates (traffic) on page 5-3

Performance of high-priority hosts

In a SAN environment, the storage system is usually connected with many host servers. Some types of host servers often require higher performance than others. For example, production servers such as database and application servers that are used to perform daily tasks of business organizations usually require high performance. If production servers experience decreased performance, productivity in business activities can be negatively impacted. To prevent this from happening, the system administrator needs to maintain the performance of production servers at a relatively high level.

Computer systems in business organizations often include development servers, which are used for developing, testing, and debugging business applications, as well as production servers. If development servers experience decreased performance, development activities can be negatively impacted, but a drop in development server performance does not have as much negative impact to the entire organization as a drop in production server performance. In this case, you can use Server Priority Manager to give higher priority to I/O activity from production servers than I/O activity from development servers to manage and control the impact of development activities.

Related topics

•

Overview of Server Priority Manager on page 5-2

Upper-limit control

Using Server Priority Manager you can limit the number of I/O requests from servers to the storage system as well as the amount of data that can be transferred between the servers and the storage system to maintain

5-2



production server performance at the required levels. This practice of limiting the performance of low-priority host servers is called upper-limit control. The upper-limit control is automatically disabled when traffic between the servers and the storage system drops to user-defined levels called thresholds.

Related topics

•


Threshold control

While upper-limit control can help production servers to perform at higher levels during periods of heavy use, it may not be desirable when production servers are not busy. For example, if the I/O activity on production servers is high between 09:00 and 15:00 hours and decreases significantly after 15:00, upper-limit control for development servers may not be required after 15:00.

To address this situation Server Priority Manager provides threshold control in which upper-limit control is automatically disabled when I/O traffic between production servers and the storage system decreases to a user-specified level. This user-specified level at which upper-limit control is disabled is called the threshold. You can specify the threshold as an I/O rate (number of I/Os per second) and a data transfer rate (amount of data transferred per second).

For example, if you set a threshold of 500 I/Os per second to the storage system, the upper-limit controls for development servers are disabled when the I/O rate of the production servers drops below 500 I/Os per second. If the I/O rate of the production servers goes up and exceeds 500 I/Os per second, upper-limit control is restored on the development servers.

If you also set a threshold of 20 MB per second to the storage system, the upper-limit controls for development servers are disabled when the amount of data transferred between the storage system and the production servers is less than 20 MB per second.

Related topics

•


About I/O rates and transfer rates (traffic)

Server Priority Manager runs based on the I/O rates and data transfer rates, also called traffic, measured by Performance Monitor. Performance Monitor measures I/O rates and transfer rates every second, and calculates the average I/O rate and the average transfer rate for every sampling interval

(specified between 1 and 15 minutes) regularly. These traffic statistics reveal the number of I/Os and amount of data being processed through the ports.

Suppose that 1 minute is specified as the sampling interval and the I/O rate at port 1-A changes as shown in Graph 1 below. When you use Performance

Monitor to display the I/O rate graph for 1A, the line in the graph indicates changes in the average I/O rate calculated every minute (see Graph 2). If



5-3

you select the Detail check box in the Performance Monitor windows, the graph displays changes in the maximum, average, and minimum I/O rates in one minute (see Graph 3).

Using Server Priority Manager you can apply upper limits and thresholds to the average I/O rate or average transfer rate per sampling interval. For example, in the following figures, if you set an upper limit of 150 I/Os to port

1A, the highest data point in the line CL1-A in Graph 2 and in the line Ave. (1 min) in Graph 3 is approximately 150 I/Os. It is possible that the lines Max (1 min.) and Min (1 min.) in Graph 3 might exceed the upper limit.

Figure 5-1 Graph 1: actual I/O rate (measured every second)

Figure 5-2 Graph 2: I/O rate displayed in Performance Monitor

5-4

Figure 5-3 Graph 3: detailed I/O rate displayed in Performance Monitor

Related topics

•




Use cases for Server Priority Manager

This section describes the use cases for implementing Server Priority Manager on the Hitachi Virtual Storage Platform G200, G400, G600, G800 storage system:

•

Use case for one-to-one connections on page 5-5

•

Use case for many-to-many connections on page 5-7

Use case for one-to-one connections

The following figure shows an example of a network, called Network A, in which each adapter is connected to only one port on the storage system. The host bus adapters are connected directly to the storage system ports and are not connected via hubs or switches.

Figure 5-4 Network A: 1-to-1 connections between HBAs and ports

In Network A, ports 1A and 1C are connected to high-priority production servers. Port 2A is connected to a low-priority development server. Therefore, high priority (Prio.) is set to ports 1A and 1C, and low priority (Non-Prio.) is set to port 2A. The following figure shows the priority settings for these ports on the Port tab of the Server Priority Manager main window.

The I/O traffic at the ports is now monitored. When the desired amount of data has been collected, the traffic statistics are reviewed on graphs using the Performance Monitor window. The following figure shows the changes in the I/O rate for the three ports (1A, 1C, and 2A). According to the data, the

I/O rate for ports 1A and 1C was approximately 400 IO/s at first, and the I/O rate for port 2A was approximately 100 IO/s at first. However, as the I/O rate for port 2A gradually increased from 100 IO/s to 200 IO/s, the I/O rate for ports 1A and 1C decreased from 400 IO/s to 200 IO/s, which indicates that



5-5

the performance of the high-priority production servers decreased. If you want to maintain the I/O rate for prioritized ports 1A and 1C at 400 IO/s, you can set an upper limit to the I/O rate for the non-prioritized port 2A.

When an upper limit is set for the first time, it is recommended that the upper limit be approximately 90 percent of the peak traffic. In Network A, the peak I/O rate for the non-prioritized port (2A) is 200 IO/s, so the recommended upper limit for port 2A is 180 IO/s. You can then adjust this value later as needed according to the results of your data analysis.

After upper limit values have been applied, the traffic at the ports is measured to check the result of the upper limits and see whether host performance has improved to a desirable level, in this case 400 IO/s for ports

1A and 1C. If production server performance is not improved to a desirable level, you can adjust the upper limit to a smaller value until the I/O rate for the high priority servers reaches the desirable level.

If you want to allow improved performance for non-prioritized ports when system activity is low, you can apply a threshold. For one-to-one connections threshold values can be set in either of the following two ways:

• Set a threshold to each prioritized port.

In Network A, if you set a threshold of 200 IO/s to port 1A and a threshold of 100 IO/s to port 1C, the upper limit on the non-prioritized port (2A) is disabled when both of the following conditions occur:

The I/O rate for port 1A is 200 IO/s or lower.

The I/O rate for port 1C is 100 IO/s or lower.

• Set one threshold to the entire storage system.

In Network A, if you set a threshold of 500 IO/s to the storage system, the upper limit on the non-prioritized port (2A) is disabled when the sum of the I/O rates for all prioritized ports (1A and 1C) falls below 500 IO/s.

The following table shows the relationship between the thresholds of prioritized ports and the upper limits of non-prioritized ports.

5-6



Table 5-1 Relationship between the thresholds of prioritized ports and the upper limits of non-prioritized ports

Threshold settings

Upper limit is set (non-zero) on the non-prioritized port

Upper limit of the nonprioritized port = 0

Threshold is set to the prioritized port

When thresholds are set on multiple prioritized ports, depending on the transfer rate, the following controls are executed:

• When the I/O rate or transfer rate goes above the threshold in any prioritized port, the upper limits of all nonprioritized ports are in effect.

• When the I/O rate or transfer rate goes below the threshold in all prioritized ports, the upper limits of all nonprioritized ports are not in effect.

Threshold is not set to the prioritized port

The specified upper limit is always in effect.

The threshold control of the prioritized port is not executed.

Use case for many-to-many connections

The following figure shows an example of a network, called Network B, in which a production server and a development server are connected to the storage system in a many-to-many configuration. HBA wwn01 on the production server is connected to ports 1A, 2A, 1C, and 2C, and HBAs wwn02 and wwn03 on the development server are also connected to the same four ports.

Figure 5-5 Network B: many-to-many connections between HBAs and ports



5-7

Before using Server Priority Manager, you must find the WWN (Worldwide

Name) of each host bus adapter in host servers. WWNs are 16-digit hexadecimal numbers used to identify host bus adapters. For details on how to find WWNs, see the Hitachi Virtual Storage Platform G200, G400, G600,

G800 Provisioning Guide.

When using Server Priority Manager, ensure that all host bus adapters connected to ports in the storage system are monitored. Use the WWN tab of the Server Priority Manager main window to monitor host bus adapters. Place host bus adapters connected to each port below the Monitor icons.

In Network B, each of the four ports in the storage system is connected to three host bus adapters (wwn01, wwn02, and wwn03). Place the host bus adapter icons of wwn01, wwn02, and wwn03 below the Monitor icons for all four port icons.

Server Priority Manager is not able to monitor and control the performance of hosts whose host bus adapters are placed below the Non-Monitor icon.

Therefore, make sure to place host bus adapters below the Monitor icons.

Figure 5-6 Host bus adapters being monitored

The priority for the host bus adapters is set using the WWN tab of the Server

Priority Manager main window. In Network B, the production server is high priority (Prio.), and the development server is low priority (Non-Prio.). To give priority to the three host bus adapters, take the following steps:

• On the WWN tab of the Server Priority Manager main window, select one of the four ports that the HBAs are connected to (that is, ports 1A, 1C,

2A, and 2C).

• Set Prio. to wwn01. Also, set Non-Prio. to wwn02 and wwn03.

The following figure shows the priority settings for host bus adapters. When you select port 1A and set the priority for host bus adapters, the same settings are automatically applied to the other ports (ports 1C, 2A, and 2C).

5-8



Figure 5-7 Priority specified in the Server Priority Manager main window

The term prioritized WWN to refers to a high-priority host bus adapter (for example, wwn01). The term non-prioritized port refers to a low-priority host bus adapter (for example, wwn02 and wwn03).

Monitor traffic between host bus adapter and ports. There are two types of traffic statistics: the I/O rate and the transfer rate. The I/O rate is the number of I/Os per second. The transfer rate is the size of data transferred between a host and the storage system per second. When you view traffic statistics in the window, you select either the I/O rate or the transfer rate.

For Network B, you must do the following:

• Measure traffic between port 1A and the three host bus adapters (wwn01, wwn02, wwn03).

• Measure traffic between port 2A and the three host bus adapters (wwn01, wwn02, wwn03).

• Measure traffic between port 1C and the three host bus adapters (wwn01, wwn02, wwn03).

• Measure traffic between port 2C and the three host bus adapters (wwn01, wwn02, wwn03).

The following figure shows these settings on the WWN tab of the Server

Priority Manager main window.

The I/O traffic between the ports and host bus adapters is now monitored.

When the desired amount of data has been collected, the traffic statistics are reviewed on graphs using the Performance Monitor window. The following graph shows the measured I/O rate for the paths between each port and the host bus adapters. According to the data, the I/O rate for the path between port 1A and the prioritized WWN (wwn01) was approximately 400 IO/s at first, and the I/O rate for the path between port 1A and the non-prioritized

WWNs (wwn02 and wwn03) was approximately 100 IO/s at first. However, as the I/O rate for the non-prioritized WWNs gradually increased from 100 IO/s to 200 IO/s, the I/O rate for the prioritized WWN decreased from 400 IO/s to

200 IO/s, which indicates a decrease in the performance of the prioritized

WWN.



5-9

Figure 5-8 Traffic at ports

To maintain a higher I/O rate (400 IO/s) for the prioritized WWN, you can set upper limits on the I/O rate for the non-prioritized WWNs to minimize their effect on the performance of the high-priority production server. When an upper limit is set for the first time, it is recommended that the upper limit value be approximately 90 percent of the peak traffic level. In Network B, the peak I/O rate at the paths between each of the four ports and the nonprioritized WWNs (wwn02 and wwn03) is 200 IO/s, so the recommended upper limit for wwn02 and wwn03 is 720 IO/s (200 × 4 × 0.90). The following figure shows the result of setting the upper limit of 720 IO/s on the paths between port 1A and non-prioritized WWNs wwn02 and wwn03 on the

WWN tab of the Server Priority Manager main window.

Figure 5-9 Upper limits for non-prioritized WWNs in Network B

After upper limits have been applied, the traffic is measured again to check the result of the upper limits and see whether host performance has improved to a desirable level, in this case 400 IO/s for wwn01. If not, you can adjust the upper limit to a smaller value until the I/O rate for wwn01 reaches the desirable level.

If you want to allow higher performance for non-prioritized WWNs when system activity is low, you can apply a threshold. For many-to-many connections you can specify one threshold for the entire storage system, regardless of the number of prioritized WWNs. For example, if there are three prioritized WWNs in the network and the threshold is 100 IO/s, the upper limit on the non-prioritized WWNs is disabled when the sum of the I/O rates for all three prioritized WWNs falls below 100 IO/s.

5-10



The following table shows the relationship between the thresholds of prioritized WWNs and the upper limits of non-prioritized WWNs.

Table 5-2 Relationship between the thresholds of prioritized WWNs and the upper limits of non-prioritized WWNs

Threshold settings

Upper limit is set (non-zero) to the non-prioritized WWN

Upper limit of the nonprioritized WWN = 0

Threshold is set to the prioritized

WWN

When thresholds are set to prioritized

WWNs, depending on the I/O rate or the transfer rate, the following controls are executed.

• If the total value of I/O rate or transfer rate exceeds the threshold in all prioritized WWNs, upper limits of all non-prioritized WWNs are in effect.

• If the total value of I/O rate or transfer rate goes below the threshold in all prioritized WWNs, upper limits of all non-prioritized

WWNs are not in effect.

Threshold is not set to the prioritized WWN

The specified upper limit is always in effect.

The threshold control of the prioritized WWN is not executed.

Cautions and restrictions for Server Priority Manager

•

Real-time monitoring mode

Server Priority Manager cannot be started when Performance Monitor is in real-time mode. Before starting Server Priority Manager, ensure that

Time Range in the Monitor Performance window is not set to Use Real

Time.

•

Remote copy functions

Server Priority Manager monitors the I/O requests between the storage systems for TrueCopy and Universal Replicator remote copy operations and global-active device.

If you set the priority attribute to the storage system port at the secondary site, all I/Os received on the port are controlled as the threshold control, and its performance data is added to the total number of I/Os (or the transfer rate) of all prioritized ports. I/Os on the port will not be limited.

If you set the non-priority attribute to the storage system port at the secondary site, I/O requests from the storage system port at the primary site are not controlled by threshold control, and I/Os on the port will not be limited. On the other hand, I/O requests from a host are controlled by upper limit control, and I/Os on the port will be limited.

•

Statistics for storage system ports at the primary site



5-11

The I/O requests from the storage system ports at the primary site are not controlled by Server Priority Manager.

•

Settings on the Server Priority Manager main window

The Server Priority Manager main window has two tabs: the Port tab and the WWN tab. The settings on only one tab at a time can be applied to the storage system. If you make settings on both tabs, the settings cannot be applied at the same time. When you select Apply, the settings on the last tab on which you made settings are applied, and the settings on the other tab are discarded.

•

Using Command Control Interface

Server Priority Manager operations cannot be performed from the GUI and the CLI (HCS and CCI) at the same time. If you change some settings for Server Priority Manager from CCI, you cannot change those settings from the GUI. If you do, some settings might not appear. Before you change features that use Server Priority Manager, delete all Server

Priority Manager settings from the currently used features.

•

Connecting one HBA to multiple ports

If one host bus adapter is connected to multiple ports and you specify an upper limit of the non-prioritized WWN for one port, the specified upper limit value will be applied to the host bus adapter settings for other connected ports automatically.

•

Setting the connection between host bus adapter and port

To make setting for connecting the host bus adapter's WWN and the port, use the WWN tab of the Server Priority Manager main window.

Alternatively you can use the Monitored WWNs tab of the Performance

Monitor main window. Note that the monitored WWN name displayed in

Performance Monitor is displayed as the SPM name in Server Priority

Manager.

Implementing Server Priority Manager: one-to-one connections

This section describes and provides instructions for implementing Server

Priority Manager for one-to-one connections.

•

Server Priority Manager workflow: one-to-one connections on page 5-12

•

Setting priority for ports: one-to-one connections on page 5-13

•

Analyzing traffic statistics: one-to-one connections on page 5-14

•

Setting upper-limit values for non-prioritized ports: one-to-one connections on page 5-15

•

Setting a threshold: one-to-one connections on page 5-17

Server Priority Manager workflow: one-to-one connections

The workflow for Server Priority Manager depends on the connection between the host bus adapters and the ports. When one-to-one connections are established between host bus adapters and ports, you can manage the

5-12



priority of I/O operations on each port. You can specify upper limit values on the non-prioritized ports. You can also specify threshold values on the prioritized ports or apply one threshold value to the entire storage system.

When traffic drops below this threshold, the upper limits on non-prioritized ports are disabled to allow higher performance on non-prioritized ports during periods of low system activity.

The Port tab of the Server Priority Manager main window is used to manage

Server Priority Manager operations for one-to-one connections.

Workflow for one-to-one connections:

1

2

3

.

.

.

If desired, assign names to the WWNs for ease of identification. For details, see

Changing the SPM name of a host bus adapter on page

5-30

.

Set the priority (Prio or Non-Prio) for the ports of the storage system.

For details, see

Setting priority for ports: one-to-one connections on page

5-13

.

Monitor the I/O traffic at the prioritized and non-prioritized ports to collect data and statistics for analysis. For details, see

Monitoring WWNs on page

2-8

.

4

.

Analyze the traffic statistics that you have collected to determine the appropriate upper limits to set for the non-prioritized ports. For details, see

Analyzing traffic statistics: one-to-one connections on page 5-14 .

5

.

Set upper limits for I/O traffic at the non-prioritized ports to prevent these ports from affecting the prioritized ports. For details, see


.

6

.

Monitor the I/O traffic at the ports again to check the results of applying the upper limits to the non-prioritized ports, and adjust the upper-limit values as needed.

7

.

If desired, apply a threshold to the ports or to the entire storage system to allow higher performance at non-prioritized ports when activity on the prioritized ports or storage system is low. For details, see

Setting a threshold: one-to-one connections on page 5-17 .

Setting priority for ports: one-to-one connections

Prioritized ports are ports on which processing has high priority, and nonprioritized ports are ports on which processing has lower priority. Specify a port that connects to a high-priority host bus adapter as a prioritized port.

Specify a port that connects to a lower-priority host bus adapter as a nonprioritized port.

Prerequisites

• Required role: Storage Administrator (System Resource Management)

• The Device Manager - Storage Navigator secondary window must be enabled.



5-13

Procedure

1

.



.


b

.


Monitor window.


.

.

5

.

6

.

2

.

In the Performance Monitor window, click Server Priority Manager to open the Server Priority Manager window.

3

.

4

.

Click to change to Modify mode.

In the Server Priority Manager window, click Server Priority

Manager . The Server Priority Manager main window appears.

Select the Port tab.

Select All from the list at the top right corner of the window.

7

.

8

9

.

.



Monitor .

Right-click a high-priority port, and in the pop-up menu select Non-Prio -

>> Prio. The Attribute column displays Prio. Repeat this action for each high-priority port.

Right-click a lower-priority port and in the pop-up menu select Prio ->>

Non-Prio. The Attribute column displays Non-Prio. Repeat this action for each lower-priority port. You can set upper limit values only on the

Non-prio. ports.


Now that you have set the port priorities, you can start monitoring the traffic (I/O rates and transfer rates) to collect data for analysis.

Related topics

•


•

Port tab of the Server Priority Manager main window on page B-3

Analyzing traffic statistics: one-to-one connections

You must analyze the traffic statistics to determine the upper limit values that should be applied to I/O rates or transfer rates on non-prioritized ports.

Prerequisites



5-14



Procedure

1

.



.


b

.


Monitor window.


.

.



Monitor .

5

.

6

.

2

.


3

.

4

.






7

.

Display the desired traffic statistics as follows:

¢

To view I/O rates, select IOPS from the list at the upper left corner of the list.

¢

To view transfer rates, select MB/s from the list at the upper left corner of the list.

The list displays the traffic statistics (average and peak I/O rates or transfer rates) of the ports.

8

.

Analyze the data in the list to determine the upper limit values that should be applied to non-prioritized ports and, if desired, the threshold values that should be applied to prioritized ports or the storage system.

9

.

To view the traffic statistics on data graphs, see Displaying the monitor data on graphs on page 2-19 .

To export the traffic statistics (as text in CSV format) for analysis in other applications, see

Using the Export Tool on page 4-4

.

Related topics

•


•


Setting upper-limit values for non-prioritized ports: one-to-one connections

After you analyze traffic statistics, you can set upper limit values for I/O rates or data transfer rates on non-prioritized ports to provide better performance



5-15

for high-priority host servers. For details about upper limit values, see

Upperlimit control on page 5-2 .

When you set an upper limit for the first time, it is recommended that the upper limit value be approximately 90 percent of the peak traffic.

Prerequisites



6

.

7

.

2

.

3

.

Procedure

1

.



.


b

.


Monitor window.


.


b

.


Monitor .

Display the Device Manager - Storage Navigator main window.


4

.

5

.

8

.





Do one of the following:

¢

¢

To limit the I/O rate for the non-prioritized port, select IOPS from the list at the upper left corner of the list.

To limit the transfer rate for the non-prioritized port, select MB/s from the list at the upper left corner of the list.

Locate the non-prioritized port in the list.

9

.

Note: The Attribute column of the list indicates whether ports are prioritized or non prioritized. If you cannot find any non prioritized port in the list, check the list at the top right corner of the window. If the list displays Prioritize, select All or Non Prioritize from the list.


5-16



¢

¢

To limit the I/O rate for the non-prioritized port, double-click the desired cell in the IOPS column in Upper, and enter the upper limit value in the cell.

To limit the transfer rate for the non-prioritized port, double-click the desired cell in the MB/s column in Upper, and enter the upper limit value in the cell.

In the list, either of IOPS or MB/s column is activated depending on the rate selected in step 3 above. You can use either of them to specify the upper limit value for one port. You can specify different types of rates (IOPS or MB/s) for the upper limit values of different non-prioritized ports.

The upper limit value that you entered is displayed in blue.

Caution: If an upper limit of the non-prioritized WWN is set to zero or nearly zero, I/O performance might be lowered. If I/O performance is lowered, the host cannot be connected to the storage system in some cases.

10

.

Click Apply to apply the settings to the storage system. The upper limit value that you entered turns black.

Related topics

•


•

Server Priority Manager window on page B-2

•


Setting a threshold: one-to-one connections

When one-to-one connections are established between HBAs and ports, you can set a threshold value for each prioritized port or one threshold value for the entire storage system. When traffic between high-priority servers and the ports or storage system falls below the specified threshold level, upper limit control is disabled to allow higher performance on non-prioritized ports during periods of low activity on prioritized ports. For details about threshold values, see

Threshold control on page 5-3

.

Prerequisites



Procedure

1

.



.




5-17

5

.

6

.

2

.

b

.


Monitor window.


.

b

.



Monitor .


3

.

4

7

.

.



Manager to open the Server Priority Manager main window.


To set a threshold value for each prioritized port, select the type of rates for the threshold value from the list in the upper left corner of the list.

¢

To use the I/O rates for the threshold value, select IOPS.

¢

To use the transfer rates for the threshold value, select MB/s.

If you want to set one threshold value for the entire storage system, this step is unnecessary.


¢

To set a threshold to each prioritized port, locate the desired prioritized port, which is indicated by Prio. in the Attribute column.

Next, double-click the cell in the IOPS or MB/s column in

Threshold, and then enter the threshold value. In the list, either of

IOPS or MB/s column is activated depending on the rate selected at step 6 above. Repeat this operation to set the thresholds for all prioritized ports. You can use different types of rates (IOPS or MB/s) for thresholds of different prioritized ports.

8

.

Caution: If you enter zero (0) in a cell to disable the upper limit, the cell displays a hyphen (-) and the threshold for the prioritized port becomes ineffective. If the thresholds of all prioritized ports are ineffective, threshold control will not be performed but upper limit control will be performed. If you set thresholds for multiple prioritized ports and the I/O rate or transfer rate goes below the threshold at all prioritized ports, threshold control works in the entire storage system and the upper limits of the non-prioritized ports are disabled.

¢

To set one threshold to the entire storage system, select the All

Thresholds check box. Next, select IOPS or MB/s from the list of right side in All Thresholds and enter the threshold value in the text box. Even if the types of rates for upper limit values and the threshold are different, the threshold control can work for all non-prioritized ports.


5-18



Related topics

•


•


•


Implementing Server Priority Manager: many-to-many connections

This section describes and provides instructions for implementing Server

Priority Manager for many-to-many connections.

•

Server Priority Manager workflow: many-to-many connections on page

5-19

•

Setting priority for WWNs: many-to-many connections on page 5-20

•

Monitoring all port-HBA traffic: many-to-many connections on page 5-22

•

Analyzing traffic statistics: many-to-many connections on page 5-25

•

Setting upper-limit values for non-prioritized WWNs: many-to-many connections on page 5-27

•

Setting a threshold for the entire storage system: many-to-many connections on page 5-29

Server Priority Manager workflow: many-to-many connections

The workflow for using Server Priority Manager depends on the connection between the host bus adapters and the storage system ports. When many-tomany connections are established between HBAs and storage system ports, the server priority cannot be defined by the port, because one port can be connected to multiple adapters and multiple ports can be connected to one adapter. For many-to-many connections, you can specify the priority of I/O operations and the upper limit value for each host bus adapter, and you can specify one threshold value for the entire storage system.

The WWN tab of the Server Priority Manager main window is used to manage

Server Priority Manager operations for many-to-many connections.

Workflow for many-to-many connections:

1

.

2

3

.

.

Find the WWNs of the host bus adapters. For details about finding WWNs, see the Hitachi Virtual Storage Platform G200, G400, G600, G800

Provisioning Guide.

If desired, assign names to the WWNs for ease of identification. For details, see

Changing the SPM name of a host bus adapter on page

5-30

.

If you want to manage multiple host bus adapters as a single group, create SPM groups. For details, see

Creating an SPM group on page

5-34

.



5-19

4

.

Set the priority (Prio or Non-Prio) on the host bus adapters (WWNs).

For details, see

Setting priority for WWNs: many-to-many connections on page 5-20 .

5

.

Monitor the I/O traffic for all prioritized and non-prioritized host bus adapters to collect data and statistics for analysis. For details, see

Monitoring WWNs on page 2-8

.

6

.

7

.

Analyze the traffic statistics that you have collected to determine the appropriate upper limits to set for the non-prioritized WWNs. For details, see

Analyzing traffic statistics: many-to-many connections on page

5-25 .

Set upper limits for traffic on non-prioritized WWNs to prevent these

WWNs from affecting the prioritized WWNs. For details, see Setting upper-limit values for non-prioritized WWNs: many-to-many connections on page 5-27 .

8

.

9

.

Monitor traffic at the ports again to check the results of applying the upper-limit values to the non-prioritized WWNs, and adjust the upperlimit values as needed.

If desired, apply a threshold to the entire storage system to allow higher performance for the non-prioritized WWNs when activity on the storage

system is low. For details, see Setting a threshold for the entire storage system: many-to-many connections on page 5-29 .

Setting priority for WWNs: many-to-many connections

If many-to-many connection is established between HBAs and ports, you need to define the priority of WWNs, measure the traffic between the HBAs and the ports that the HBAs are connected to, and analyze the traffic data.

The HBAs are divided into two types: prioritized WWNs and non-prioritized

WWNs. Specify an HBA on which high-priority processing is performed as a prioritized WWN. Specify an HBA on which lower-priority processing is performed as a non-prioritized WWN.

Note: You cannot change the priority of a WWN that is contained in an SPM group. For details on how to change the attribute of a WWN contained in an

SPM group, see Switching priority of an SPM group on page 5-36

.

Prerequisites



Procedure

1

.



.


5-20



b

.


Monitor window.


2

.

a

.

b

.



Monitor .


7

.

8

.

9

.

5

.

6

.

3

.

4

.

10

.

11

.




Select the WWN tab.


In the upper-left tree, double-click a port.

Double-click Monitor, which is displayed below the specified port.

Check to see if all WWNs of the host bus adapters to be controlled by using Server Priority Manager appear below Monitor.

If some of the WWNs are missing, use the procedure in Monitoring all port-HBA traffic: many-to-many connections on page 5-22

to move all

WWNs to below Monitor.

Click Monitor to display the information of the host bus adapters that are monitored in the list on the right of the tree.

Right-click a host bus adapter (WWN) in the list, and in the pop-up menu select Non-Prio ->> Prio.

The Attribute column of the selected WWN in the list displays Prio. If you want to specify more than one prioritized WWN, repeat this operation.

12

.

Right-click a host bus adapter (WWN) in the list, and in the pop-up menu select Prio ->> Non-Prio.

The Attribute column of the selected WWN in the list displays Non-Prio.

If you want to specify more than one non-prioritized WWN, repeat this operation.

13

.

Note: You cannot change the priority of a WWN which is contained in an

SPM group. For details on how to change the attribute of a WWN

contained in an SPM group, see Switching priority of an SPM group on page 5-36

.

You must set upper limit values for the Non-prio. specified ports. For details, see

Setting upper-limit values for non-prioritized WWNs: manyto-many connections on page 5-27

.

Repeat steps 6 to 11 for ports (except for the port selected in step 6).

If one host bus adapter is connected to multiple ports and you specify the priority of the host bus adapter for one port, the specified priority will be also applied to the host bus adapter settings for other connected ports automatically.



5-21

14

.

In the Server Priority Manager main window, click Apply to apply the settings to the storage system.

For instructions on measuring traffic (that is, I/O rates and transfer rates),

see Starting monitoring on page 2-7 .

Related topics

•


5-19

•

WWN tab of the Server Priority Manager main window on page B-6

Monitoring all port-HBA traffic: many-to-many connections

When many-to-many connections are established between HBAs and ports, you should make sure that all traffic between HBAs and ports is monitored.

Prerequisites



6

.

7

.

8

.

Procedure

1

.

2

.



.


b

.


Monitor window.


.

b

.



Monitor .


3

.

4

.

5

.




Click the WWN tab.

Two trees are displayed on the left side of the WWN tab. The upper-left tree lists ports in the storage system.


In the upper-left tree, double-click a port.

Double-click Non-Monitor below the specified port.

5-22



9

.

If there are any host bus adapters whose traffic with the specified port are not monitored, those host bus adapters are displayed below Non-

Monitor.

Right-click Monitor, and then select Add WWN to open the Add WWN window.

10

.

In the Add WWN window, specify the WWN and the SPM name.

Expand the WWN list to show the WWNs of the host bus adapters that are connected to the port but are not monitored. These host bus adapters are the same as that displayed in step 8. From that list, select a WWN and specify the SPM name (up to 64 characters).

11

.

12

.

Note: It is recommended that you specify the same names for the SPM names and the host bus adapter nicknames defined in LUN Manager for convenience of host bus adapter management. In the Performance

Monitor window, both the SPM names and the nicknames are displayed as the aliases of host bus adapters (WWNs), so if you use the same names, management of the host bus adapters is easier.

Click OK. The selected WWN (of the host bus adapter) is moved from

Non-Monitor to Monitor.

If the specified host bus adapter is connected to other ports, after clicking

OK, a message appears asking whether to change the settings of that host bus adapter for other ports. Apply the same setting to all of the ports.

Repeat steps 9 to 11 to move all host bus adapters from below Non-

Monitor to below Monitor.

Up to 32 host bus adapters (WWNs) can be monitored for one port. If more than 32 host bus adapters are connected to one port, the traffic statistics for all host bus adapters cannot be monitored. Consider the intended use of each host, and place the host bus adapters that do not need to be monitored below Non-Monitor.

Note: When you disconnect a host that has been connected via a cable to your storage system or change the port to the another port of the host, the WWN for the host will remain in the WWN list on the WWN tab. To remove the WWN from the list, you need to delete the WWN using LUN



5-23

Manager. For details, see the Hitachi Virtual Storage Platform G200,

G400, G600, G800 Provisioning Guide.

13

.


14

.

If you add a port or a host bus adapter to the storage system after the settings above, the traffic for the new port or host bus adapter will not be monitored. In this case, follow this procedure again to make sure all traffic between host bus adapters and ports is being monitored.

Related topics

•


5-19

•


Excluding traffic between an HBA and a port from the monitoring target: manyto-many connections

Up to 32 host bus adapters (WWNs) can be monitored for one port. If more than 32 host bus adapters are connected to one port, the traffic statistics for all host bus adapters cannot be monitored. Consider the intended use of each host, and move the host bus adapters that do not need to be monitored to

Non-Monitor.

Prerequisites



Procedure

1

.

2

.



.


b

.


Monitor window.


.


b

.


Monitor .


3

.


5-24



8

.

9

.

4

.



5

.

6

.

7

.

Ensure that the WWN tab is displayed.


In the upper-left tree, double-click a port to which more than 32 host bus adapters are connected.

Double-click Monitor below the specified port.

10

11

.

.

Right-click the WWN of a host bus adapter you want to exclude from the monitoring target and then select Delete WWN from the pop-up menu.

If the selected host bus adapter is connected to multiple ports, when you select the host bus adapter and select the Delete WWN pop-up menu, a message will appear that asks you whether to move the host bus adapter from Monitor to Non-Monitor below all other ports, too.

If the selected host bus adapter is contained in an SPM group, a message will appear that tells you to delete the host bus adapter from the SPM group on ahead. You cannot move a host bus adapter that is contained in an SPM group from Monitor to Non-Monitor. For details on how to

delete a host bus adapter from an SPM group, see Deleting an HBA from an SPM group on page 5-35 .

Click OK for the confirmation message that asks you whether to delete the host bus adapter.

The deleted host bus adapter (WWN) is moved from Monitor to Non-

Monitor.


Related topics

•


5-19

•


•


Analyzing traffic statistics: many-to-many connections

The traffic statistics indicate the number of I/Os via ports from HBAs and the amount of data that has been transferred between ports and HBAs. You must analyze the traffic statistics to determine the upper limit values that should be applied to I/O rates or transfer rates for low-priority HBAs.

The following procedure uses the Server Priority Manager main window to analyze traffic statistics. You can also use the Performance Monitor window to analyze traffic statistics and display a line graph that shows the changes in traffic.

Prerequisites




5-25

5-26


5

.

6

.

7

.

Procedure

1

.

2

.



.


b

.


Monitor window.


.


b

.


Monitor .


3

.

4

.

8

.







¢

¢

To analyze I/O rates, select IOPS from the list at the upper left corner.

To analyze transfer rates, select MB/s from the list at the upper left corner of the list.

Below the Storage System folder in the upper-left tree, click the icon of the port whose traffic statistics you want to collect.

The list displays traffic statistics (I/O rates or transfer rates) about the host bus adapters that connect to the selected port.

The following two types of traffic are shown. The traffic has attributes including the average and maximum values.

¢

Traffic between the host bus adapter and the selected port (shown in

Per Port)

¢

Sum of the traffic between the host bus adapter and all ports connected to the host bus adapter (shown in WWN Total)

The traffic statistics only about the host bus adapters below Monitor appear in the list.

The WWN Total traffic statistics will also be displayed in the list when you click an icon in the lower left tree. If you click the Storage System folder in the lower left tree, the sum of the traffic of the host bus adapters registered on each SPM group is displayed. For details on SPM groups, see

Working with SPM groups on page 5-34 .



9

.

Analyze the information in the list and then determine upper limit values that should be applied to non-prioritized WWNs. If necessary, determine threshold values that should be applied to prioritized WWNs. For details, see

Server Priority Manager workflow: many-to-many connections on page 5-19

.

Related topics

•


5-19

•


•


•


Setting upper-limit values for non-prioritized WWNs: many-to-many connections

After you analyze traffic statistics about prioritized WWNs and non-prioritized

WWNs, you must set upper limit values to I/O rates or transfer rates for nonprioritized WWNs. Upper limit values for I/O rates are used to suppress the number of I/Os from the low priority host servers and thus provide better performance for high-priority host servers. Upper limit values for transfer rates are used to suppress the amount of data that should be transferred between the storage system and the low priority ports, thus providing better performance for high-priority host servers.

When you set an upper limit for the first time, it is recommended that the upper limit be approximately 90 percent of the peak traffic.

Tip: To set the same upper limit value to more than one non-prioritized

WWN, use an SPM group. For details on SPM groups, see Working with SPM groups on page 5-34

.

Note: You cannot set the upper-limit value of a host bus adapter that is contained in an SPM group. The upper limit value of a host bus adapter in an

SPM group is defined by the SPM group settings. For details, see Setting an upper-limit value to HBAs in an SPM group on page 5-37

.

Caution: If an upper limit of the non-prioritized WWN is set to zero or nearly zero, I/O performance might be lowered. If I/O performance is lowered, the host cannot be connected to the storage system in some cases.

Prerequisites





5-27

5-28

Procedure

1

.



.


b

.


Monitor window.


.

.



Monitor .

5

.

6

.

2

.


3

.

4

.






7

8

.

.

¢

¢

To limit the I/O rate of the non-prioritized WWN, select IOPS from the list at the upper left corner.

To limit the transfer rate of the non-prioritized WWN, select MB/s from the list at the upper left corner.

In the upper-left tree, click the icon of the port whose traffic you want to limit below the Storage System folder.

The information about the host bus adapters which connect to the selected port is displayed in the list.

Locate the non-prioritized WWN in the list.

¢

¢

The Attribute column of the list indicates whether WWNs are prioritized or non-prioritized. The Attribute column of a nonprioritized WWN displays Non-Prio.

If you cannot find any non-prioritized WWN in the list, check the list at the top right corner of the window. If the list displays Prioritize, select All or Non-Prioritize.

9

.


¢

¢

To limit the I/O rate of the non-prioritized WWN, double-click the desired cell in the IOPS column in Upper. Next, enter the upper limit value in the cell.

To limit the transfer rate of the non-prioritized WWN, double-click the desired cell in the MB/s column in Upper. Next, enter the upper limit value in the cell.

In the list, either of the IOPS cells or MB/s cells are activated depending on the rate you specified in step 6. You can specify the limit value by using either of the I/O rate or transfer rate for each



host bus adapter. The upper limit value that you entered is displayed in blue. It is allowed that you specify upper limit values by using the

I/O rate for some host bus adapters and specify them by using the transfer rate for the other host bus adapters.

10

.

Note: If one host bus adapter is connected to multiple ports and you specify an upper limit value of the host bus adapter for one port, the specified upper limit value will be applied to the host bus adapter settings for other connected ports automatically.


The upper limit value that you entered turns black.

Related topics

•


5-19

•


Setting a threshold for the entire storage system: many-to-many connections

If threshold control is used, upper limit control is automatically disabled when traffic between production servers and the storage system is reduced to a

specified level. For details, see Upper-limit control on page 5-2

and Server

Priority Manager workflow: many-to-many connections on page 5-19 .

If many-to-many connections are established between host bus adapters and storage system ports, you can set one threshold value for the entire storage system. In this environment, you cannot set individual threshold values for each prioritized WWN.

Prerequisites



Procedure

1

.



.

b

.

a

.


b

.


Monitor window.




Monitor .



5-29

2

.


3

.

4

5

.

.





6

.

Select the All Thresholds check box.

7

.

Select IOPS or MB/s from the All Thresholds list, and do one of the following:

8

.

¢

¢

To specify the threshold value by using the I/O rate, select IOPS from the list below the check box.

To specify the threshold value by using the transfer rate, select MB/s from the list below the check box.

Even if the types of rates differ between the upper limit values and the threshold value, the threshold control is effective for all nonprioritized WWNs.

Enter the threshold in the text box of All Thresholds.

9

.

Caution: If you enter zero (0) in a cell to disable the upper limit, the cell displays a hyphen (-) and the threshold for the prioritized port becomes ineffective. If the thresholds of all prioritized ports are ineffective, threshold control will not be performed but upper limit control will be performed.


Related topics

•


5-19

•


•

Upper-limit control on page 5-2

Managing host bus adapters

You can use Server Priority Manager to change the name assigned to a host bus adapter and replace an existing host bus adapter.

•

Changing the SPM name of a host bus adapter on page 5-30

•

Replacing a host bus adapter on page 5-32

Changing the SPM name of a host bus adapter

Use Server Priority Manager to assign an SPM name to a host bus adapter.

Although you can identify host bus adapters by WWNs, you might be able to identify host bus adapters more easily if you assign SPM names. WWNs are

5-30



16-digit hexadecimal numbers that cannot be changed, whereas SPM names need not be 16-digit hexadecimal numbers and can be changed as needed.

For details about assigning SPM names, see

Monitoring all port-HBA traffic: many-to-many connections on page 5-22 .

Prerequisites



5

.

6

.

Procedure

1

.

2

.



.


b

.


Monitor window.


.


b

.


Monitor.


3

.

4

.



Manager. The Server Priority Manager main window appears.


7

.

In the upper-left tree, select a host bus adapter ( ) from below

Monitor and then right-click the selection.

From the pop-up menu, select Change WWN and SPM Name. The

Change WWN and SPM Name window opens.



5-31

8

.

9

.

Enter a new SPM name in the SPM Name box and then select OK. You can use up to 64 characters for an SPM name.


Related topics

•


•


Replacing a host bus adapter

If you replace an existing host bus adapter, you need to use Server Priority

Manager to delete the host bus adapter being removed and then add the host bus adapter being installed.

When you add a new host bus adapter rather than replacing one, the WWN of the new host bus adapter is automatically displayed below Non-Monitor for the connected port in the list.

Prerequisites



Procedure

1

.



.


b

.


Monitor window.


5-32



2

.

a

.


b

.


Monitor.


3

.

5

.

6

.


4

.




7

.

In the upper-left tree, select the old host bus adapter ( ) from below

Monitor and then right-click the selection.

From the pop-up menu, select Change WWN and SPM Name. The

Change WWN and SPM Name window opens.

8

9

.

.

10

.

11

.

Enter the WWN of the new host bus adapter in the WWN combo box. For details on how to get the WWN the HBA WWN, see the Hitachi Virtual

Storage Platform G200, G400, G600, G800 Provisioning Guide.

You can select the WWN of the newly connected host bus adapter in the

WWN combo box.

If necessary, enter a new SPM name in the SPM Name box. You can use up to 64 characters for an SPM name.

Select OK to close the Change WWN and SPM Name window.


Related topics

•




5-33

Working with SPM groups

You can use Server Priority Manager to create SPM groups to manage multiple host bus adapters as a single group. Each SPM group can contain up to 32 HBAs, and you can create up to 512 SPM groups in the storage system.

All HBAs in an SPM group have the same priority. Prioritized WWNs and nonprioritized WWNs cannot be mixed in the same group.

You can use an SPM group to switch priority of multiple HBAs from prioritized to non-prioritized, or vice versa. You can also use an SPM group to set the same upper limit value to all HBAs in the group.

•

Creating an SPM group on page 5-34

•

Deleting an HBA from an SPM group on page 5-35

•

Switching priority of an SPM group on page 5-36

•

Setting an upper-limit value to HBAs in an SPM group on page 5-37

•

Renaming an SPM group on page 5-39

•

Deleting an SPM group on page 5-40

Creating an SPM group

Prerequisites



A host bus adapter can belong to only one SPM group.

Procedure

1

.



2

.

a

.


b

.


Monitor window.


.

b

.



Monitor.


3

.

4

.




5-34



7

.

8

.

5

.


6

.

In the lower-left tree, select and right-click the Storage System folder.

From the pop-up menu, select Add New SPM Group.

In the Add New SPM Group window, enter the name of the SPM group and then select OK. An SPM group is created and an SPM group icon ( ) is added to the lower-left tree.

9

.

Select an HBA from the upper-left tree and select an SPM group from the lower-left tree. Next, click Add WWN.

Repeat this operation until all desired HBAs are added to the SPM group.

¢

¢

Select a host bus adapter from below Monitor. You cannot add HBAs from below Non-Monitor to SPM groups.

When selecting a host bus adapter that is already contained in some

SPM group from the upper-left tree, the Add WWN button is not activated. Select a host bus adapter that is not contained in any SPM groups.

10

.


Related topics

•


Deleting an HBA from an SPM group

Prerequisites



Procedure

1

.



.


b

.


Monitor window.



5-35

2

.

3

.

4

.





5

.

6

.

In the lower-left tree, double-click the SPM group ( ) that contains the host bus adapter to be deleted.

7

.


.


b

.


Monitor.


8

9

.

.

Below the SPM icon, right-click the icon the host bus adapter ( ) you want to delete.

Select Delete WWN from the pop-up menu.

The selected host bus adapter icon is deleted from the tree.


Related topics

•


Switching priority of an SPM group

All host bus adapters in one SPM group must have the same priority.

Prioritized WWNs and non-prioritized WWNs cannot be mixed in one SPM group.

You can use an SPM group to switch priority of multiple HBAs from prioritized to non-prioritized, or vice versa.

Prerequisites



Procedure

1

.



.

b

.



Monitor window.

5-36



5

.

6

.

7

.

2

.


.


b

.


Monitor.


3

.

4

8

.

.





In the lower-left tree, select and right-click an SPM group ( ).


¢

¢

To switch priority from prioritized to non-prioritized, select Prio ->>

Non-Prio from the pop-up menu.

To switch priority from non-prioritized to prioritized, select Non-Prio -

>> Prio from the pop-up menu.


Related topics

•


Setting an upper-limit value to HBAs in an SPM group

If all host bus adapters in an SPM group are non-prioritized WWNs, you can set an upper limit value to HBA performance (i.e., I/O rate or transfer rate).

You can assign one upper limit value for one SPM group.

For example, suppose that the upper limit value 100 IOPS is assigned to an

SPM group consisting of four host bus adapters. If the sum of the I/O rate of the four host bus adapters reaches 100 IOPS, Server Priority Manager controls the system so that the sum of the I/O rates will not exceed 100

IOPS.

Prerequisites



Procedure

1

.



.




5-37

5

.

6

.

2

.

b

.


Monitor window.


.

b

.



Monitor.


3

.

4

7

.

.





In the lower-left tree, select and right-click the Storage System folder or an SPM group ( ).

If you selected the Storage System folder, take the following steps:

¢

¢

Select IOPS or MB/s from the list at the upper-left corner of the list.

Select IOPS if you want to assign an upper limit to the I/O rate.

Select MB/s if you want to assign an upper limit to the transfer rate.

To assign an upper limit to the I/O rate, enter the upper limit value in the IOPS column of the list. To assign an upper limit to the transfer rate, enter the upper limit value in the MB/s column of the list.

Tip: If you cannot see the IOPS or MB/s column, scroll the list to the left. The column is located at the right side of the list.

If you selected an SPM group ( ), take the following steps:

¢

Right-click the selected SPM group and then select Change Upper

Limit from the pop-up menu. The Change Upper Limit dialog box opens.

5-38

8

.

¢

To assign an upper limit to the I/O rate, enter the upper limit value and then select IOPS from the list. Next, select OK. To assign an upper limit to the transfer rate, enter the upper limit value and then select MB/s from the list. Next, select OK.




To confirm an upper limit value specified for each SPM group, select the

Storage System folder in the lower-left tree on the WWN tab. The SPM groups are displayed in the list and you can confirm each upper limit value.

Related topics

•


Renaming an SPM group

Prerequisites



5

.

6

.

Procedure

1

.

2

.



.


b

.


Monitor window.


.

b

.



Monitor.


3

.

4

.





7

.


Select Rename SPM Group from the pop-up menu. The Rename SPM

Group dialog box opens.



5-39

8

.

Enter the new name and select OK.

9

.


Related topics

•


Deleting an SPM group

Prerequisites



Procedure

1

.



.


b

.


Monitor window.


6

.

7

.

a b

.

.



Monitor.

2

.


3

.

4

5

.

.






Select Delete SPM Group from the pop-up menu.

5-40



8

.


Related topics

•




5-41

5-42



6

Hitachi Virtual Partition Manager operations

This chapter describes and provides instructions for performing cache partitioning operations using Hitachi Virtual Partition Manager.

□

Overview of Virtual Partition Manager

□

Use case for cache logical partitioning

□

Cache partitioning workflow

□

Cautions and restrictions for Virtual Partition Manager

□

Calculating cache capacity

□

Managing CLPRs

Hitachi Virtual Partition Manager operations


6-1

Overview of Virtual Partition Manager

The Hitachi Virtual Storage Platform G200, G400, G600, G800 storage system can connect to multiple hosts and can be shared by multiple users, which can result in conflicts among users. For example, if a host issues many I/O requests or reads or writes a large amount of data, the I/O performance of other hosts may be affected. Virtual Partition Manager allows you to create multiple virtual cache memories called cache logical partitions (CLPRs), each allocated to different hosts, to prevent contention for cache memory and improve I/O performance.

A cache logical partition 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. 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 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.

CLPR names

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

The following table lists the reserved CLPR names and corresponding CLPR

IDs. These CLPR names are reserved with each CLPR ID. You cannot use another CLPR ID. For example, if the CLPR ID is 1, you cannot change the

CLPR name to "CLPR2".

9

10

11

12

7

8

5

6

2

3

4

0

1

CLPR ID

CLPR0

CLPR1

CLPR2

CLPR3

CLPR4

CLPR5

CLPR6

CLPR7

CLPR8

CLPR9

CLPR10

CLPR11

CLPR12

CLPR name

25

26

27

28

21

22

23

24

16

17

18

19

20

CLPR ID

CLPR16

CLPR17

CLPR18

CLPR19

CLPR20

CLPR21

CLPR22

CLPR23

CLPR24

CLPR25

CLPR26

CLPR27

CLPR28

CLPR name

6-2



13

14

15

CLPR ID

CLPR13

CLPR14

CLPR15

CLPR name

29

30

31

CLPR ID

CLPR29

CLPR30

CLPR31

CLPR name

Use case for cache logical partitioning

The following figure shows three branch offices and a total of 128 GB of cache memory partitioned into one 40 GB segment for each office. The host for branch A has a heavy I/O load. Because the cache memory is partitioned, that heavy I/O load cannot affect the cache memory for the other two branches.

Cache partitioning workflow

1

.

2

.

3

.

Calculate the cache capacity required for your needs taking into account other features and functions that also have cache capacity requirements.

For details, see

Calculating cache capacity on page 6-5 .

If needed, work with your Hitachi Data Systems representative to have additional cache memory installed in your Hitachi Virtual Storage Platform

G200, G400, G600, G800 storage system.

Determine an appropriate time to create CLPRs and migrate resources to the new CLPRs. Creating CLPRs and and migrating resources can



6-3

4

.

5

.

significantly degrade host performance and should be performed during the initial installation and setup of the storage system or during a maintenance window.

Create the new CLPRs and migrate resources to the new CLPRs. For details, see

Creating a CLPR on page 6-7

and

Migrating resources to and from a CLPR on page 6-9 .

Manage the CLPRs as needed.

After a CLPR has been created, you can change the CLPR name and CLPR cache capacity. For details, see

Editing the settings of an existing CLPR on page 6-10 .

Cautions and restrictions for Virtual Partition Manager

•

Increased cache memory requirements

Install additional cache memory before partitioning cache. Adding cache memory after CLPRs have been created is difficult and can be

problematic. For details, see Calculating cache capacity on page 6-5

.

•

Impact on host performance

Creating and changing cache logical partitions can significantly degrade host performance and should only be performed during the initial installation and setup of the storage system or during a maintenance window. If you must perform these changes on a production machine, use

Hitachi Performance Monitor to verify that the write pending rate of the

CLPR and CLPR0 satisfy the following formulas on all MP units:

¢

For CLPR with decreased cache capacity

Write pending rate x cache capacity before operation / cache capacity after operation < 30%

The CLPR settings will be suspended if the write pending rate of any one of the MP units allocated to the operation target CLPR or CLPR0 is

50 percent or higher.

• When you move resources in CLPRs, make sure that the writing pending rates of all the MP units for each CLPR are less than 50 percent at both the source and the destination. The process for changing the CLPR settings will be suspended until the write pending rates of all the MP units become less than 50 percent.

•

Duration of cache partition operations

Adding or changing CLPR definitions or configurations can take hours to complete. After a CLPR operation has been started, you cannot cancel or modify the process until the operation is complete.

•

Interoperability restrictions for cache partitioning

Application

ShadowImage

Volume Migration

Behaviors

You cannot use ShadowImage Quick Restore functions that affect multiple CLPRs.

You cannot use Volume Migration when it affects multiple

CLPRs.

6-4



Application Behaviors

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.

Calculating cache capacity

Before you partition cache memory into one or more CLPRs, calculate the cache capacity that you need for the storage system. If necessary, install additional cache memory.

The recommended cache capacity is different for different system configurations. System differences include:

• Number of mounted MP units

• RAID level

• Number of installed drives

• Use of the following specialized applications: Dynamic Provisioning,

Dynamic Tiering, active flash, or Universal Volume Manager

Recommended Cache capacity without Dynamic Provisioning,

Dynamic Tiering, or active flash

The Dynamic Provisioning, Dynamic Tiering, and active flash products require more cache capacity to run. The recommended cache capacity for storage systems that do not use the products is lower.

The following table lists the recommended cache capacity for storage systems that do not use Dynamic Provisioning, Dynamic Tiering, and active flash.

Internal/external VOL for a CLPR

(Total capacity)

1

Less than 4 TB

4 TB or more

16 TB or more

48 TB or more

96 TB or more

160 TB or more

240 TB or more

360 TB or more

600 TB or more

Notes:

Recommended cache capacity for a CLPR

12 GB

16 GB

24 GB

32 GB

40 GB

48 GB

2

56 GB

2

64 GB

2

72 GB

2



6-5

Internal/external VOL for a CLPR

(Total capacity)

1

1

.

2

.


If you are calculating the total capacity of internal/external volumes, note the following for each volume capacity:

¢

Internal volume: For RAID1, add the half of total parity group capacity. For

RAID 5/6, subtract the parity disk capacity from the total parity group capacity and add that amount.

¢

External volume: Add the total capacity of the parity group.

40 GB for VSP G200

Recommended Cache capacity with Dynamic Provisioning, Dynamic

Tiering, or active flash

You have to allocate more cache capacity for each CLPR when Dynamic

Provisioning, Dynamic Tiering, or active flash is in use.

The following table lists the recommended cache capacity for storage systems that use Dynamic Provisioning, Dynamic Tiering, or active flash.

Internal/external/virtual VOL for a

CLPR (Total capacity)

1


Less than 4 TB

4 TB or more

16 TB or more

48 TB or more

96 TB or more

160 TB or more

20 GB

20 GB

24 GB

32 GB

40 GB

48 GB

2

240 TB or more

56 GB

2

360 TB or more

64 GB

2

600 TB or more

72 GB

2

Notes:

1

.

If you are calculating the total capacity of internal/external/virtual volumes, note the following for each volume capacity:

¢

¢

Internal volume: For RAID1, add the half of total parity group capacity. For

RAID 5/6, subtract the parity disk capacity from the total parity group capacity and add that amount.

External volume: Add the total capacity of the parity group.

2

.

¢

Virtual volume: Add the total capacity of LDEV. Check virtual volume LDEV capacity in Logical Device window. For details on Logical Device window, see

Hitachi Virtual Storage Platform G200, G400, G600, G800 Provisioning Guide.

40 GB for VSP G200

6-6



Recommended Cache capacity with Universal Volume Manager

If you are using Universal Volume Manager, sometimes you can allocate less cache capacity to a CLPR. To use less cache capacity, the CLPR that you want to create must meet the following conditions:

• The CLPR uses only external volumes.

• Transfer speed is not important.

• Cache mode of the mapped volume is Disable.

• The CLPR uses only volumes for open systems.

The following table lists the recommended cache when the total external volume capacity with Universal Volume Manager is equal to or more than or less than 128,000 GB.

Total capacity of external volume of CLPR with UVM

Less than 128 TB

128 TB or more

4

4

Number of MP units


4 GB

8 GB

When adding cache memory, use either the Standard Cache Access Model mode or the High Performance Cache Access Model mode. If the 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 customer support.

Managing CLPRs

•


•

Migrating resources to and from a CLPR on page 6-9

•

Editing the settings of an existing CLPR on page 6-10

•

Deleting a CLPR on page 6-11

Creating a CLPR

Caution: Creating CLPRs can significantly degrade host performance and should be performed during the initial installation and setup of the storage system or during a maintenance window.

Before creating a CLPR, read Cautions and restrictions for Virtual Partition

Manager on page 6-4

.

If no CLPRs have been created, the entire cache is displayed as CLPR0. When the first CLPR is created, CLPR1 is added. You can create up to CLPR9 for VSP

G200, CLPR23 for VSP G400, and CLPR31 for VSP G600 and VSP G800.

The default cache capacity is 4 GB. CLPRs can be created by assigning the necessary capacity from CLPR0.



6-7

Prerequisites


Procedure

1

.

Display the Cache Partitions window.


.

Select Administration in Explorer, and select Cache Partitions in the tree to open the Cache Partitions window.


2

3

4

.

.

.

a

.


b

.

Click Cache Partitions and open the Cache Partitions window.

Click Create CLPRs to open the Create CLPRs window. CLPR ID displays the first available CLPR ID or a blank if no CLPR ID is available.

In CLPR Name, enter the CLPR name (maximum 16 alphanumeric characters). Each CLPR name must be unique. You cannot use a CLPR name that is already reserved. If no CLPR ID is available, a blank is displayed.

In Cache Size, select the cache capacity. If no CLPR ID is available, a blank is displayed.

The default size is 4 GB, and you can select 4 GB or higher value in increments of 2 GB. The maximum available capacity (subtracted the total usage capacity of other CLPRs from the total capacity of the storage system) is displayed as the upper limit value.

5

.

Click Add. The created CLPR is added to the Selected CLPRs table.

To delete a CLPR from the Selected CLPRs table, select the CLPR and click Remove. To change the settings of an existing CLPR, select the

CLPR and Change Settings to open the Change Settings window.

6

.

Click Finish.

7

.

Check the settings in the Confirm window, enter the task name in Task

Name, and click Apply.

If Go to tasks window for status is checked, the Tasks window opens.

After creation, a CLPR has no resources (parity groups). To migrate resources to the new CLPR, see

Migrating resources to and from a CLPR on page 6-9 .

Related topics

•

Create CLPRs wizard on page C-6

•

Change Settings window on page C-14

•


•


6-8



Migrating resources to and from a CLPR

Caution: Migrating resources to and from CLPRs can significantly degrade host performance and should be performed during the initial installation and setup of the storage system or during a maintenance window.

After creating a CLPR, you can migrate resources (parity groups) from existing CLPRs to the new CLPR.

When migrating resources to and from CLPRs, multiple parity groups that configure interleaved parity groups must be in the same CLPR.

Prerequisites


Procedure

4

.

5

.

6

.

7

.

8

.

1

.



.

Select Administration in Explorer and select Cache Partitions in the tree to open the Cache Partitions window.


2

3

.

.

a

.


b

.

Click Cache Partitions to open the Cache Partitions window.

On the Cache Partitions tab, click Migrate CLPR Resources to open the Migrate CLPR Resources window.

In the Available Parity Groups table or Available Virtual Volumes table, select the resource that you want to migrate.

Select the migration destination CLPR in the CLPRs table.

Click Set.

The resource selected in the Available Parity Groups table or Available

Virtual Volumes table is migrated to the CLPR selected in the CLPRs table. To check the information of the CLPR, select the CLPR and click

Detail to open the CLPR Properties window.

When you are done adding resources to migrate, click Finish.

On the Confirm window, check the settings carefully.

When you are ready to start the resource migration, enter the task name in the Confirm window, and then click Apply.


Related topics

•

Create CLPRs wizard on page C-6



6-9

Editing the settings of an existing CLPR

You can change the following settings after creating a CLPR:

• CLPR name

• CLPR cache capacity (Cache Size on the GUI)

When you select the "CLPR0" to edit, you can edit only CLPR name, and the other items are inactive.

Prerequisites


4

.

5

.

6

.

Procedure

1

.



2

.

3

.

a

.

Select Administration in Explorer.

b

.

Select Cache Partitions in the tree to open the Cache Partitions window.


.

.



Select the CLPR to be edited, and then click Edit CLPR to open the Edit

CLPR window on the Cache Partitions tab.

Edit the CLPR settings as follows.

a b

.

.

In CLPR Name, edit the CLPR name as needed. You can use up to 16 alphanumeric characters but cannot specify CLPR names that are already reserved. The default is the name set at the time of the CLPR creation.

In Cache Size, edit the CLPR cache capacity as needed. You can select 4 GB or a higher value for the cache capacity of the CLPR and the size can be changed in increments of 2 GB. The default is the value set at the time of the CLPR creation.

The maximum available capacity (subtract the total usage capacity of other CLPRs from the total capacity of the storage system) is displayed as the upper limit value.

When you are done editing the CLPR settings, click Finish.

On the Confirm window, check the settings carefully.

When you are ready to change the settings, enter the task name in the

Confirm window, and then click Apply.


6-10



Deleting a CLPR

You can only delete CLPRs that you created. CLPR0 cannot be deleted. CLPRs to which parity groups or virtual volumes are allocated cannot be deleted.

Prerequisites


Procedure

1

.



2

.

3

.

4

.

a

.

Select Administration in Explorer, and select Cache Partitions in the tree to open the Cache Partitions window.


.


b

.


Select the CLPR that you want to delete, and then click Delete CLPRs in the More Actions on the Cache Partitions tab to open the Delete

CLPRs window.

In the Selected CLPRs table, check the CLPR that you want to delete, and then enter the task name in the Task Name field. If you want to cancel the deletion, click Cancel to go back to the Cache Partitions tab.

Click Apply.




6-11

6-12



7

Troubleshooting

This chapter provides troubleshooting information and instructions for contacting Hitachi Data Systems customer support.

□

General troubleshooting resources

□

Troubleshooting Performance Monitor

□

Troubleshooting the Export Tool for Performance Monitor

□

Troubleshooting Server Priority Manager

□

Troubleshooting Virtual Partition Manager

□

Calling Hitachi Data Systems customer support

Troubleshooting


7-1

General troubleshooting resources

For troubleshooting information on the Hitachi Virtual Storage Platform G200,

G400, G600, G800 storage system, see the hardware guide for your VSP storage system model.

For information on error messages, see the Hitachi Device Manager - Storage

Navigator Messages.

Troubleshooting Performance Monitor

Error Recommended action

Part of monitoring data is missing.

The monitoring data is not updated, even though Monitoring

Switch is set to

Enable.

The WWN of a host bus adapter is displayed in red on the WWN tab.

While displaying Performance Monitor, 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. If you notice that monitoring data is frequently missing, change to a longer collection interval.

If the time setting of the SVP is changed, the monitoring data might not be updated. Set Monitoring Switch to Disable, and set Monitoring Switch to Enable again.

The HBA for the WWN that is displayed in red is connected to two or more ports, but the traffic between the HBA and some of the ports is not monitored by Performance Monitor. When many-to-many connections are established between HBAs and ports, make sure that all traffic between HBAs and ports is monitored. For details, see


Troubleshooting the Export Tool for Performance Monitor

Error

You cannot run the batch file.

The Export Tool stops and the processing does not continue.

The command prompt window was displaying progress of the export

Recommended action

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, see 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 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

7-2

Troubleshooting


Error

processing, but the window stopped displaying progress before the processing stopped. The progress information does not seem to be updated anymore.

An error occurs and the processing stops.

Recommended action

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.

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 within the timeout period specified by the -Dmd.rmitimeout parameter of the Java command

(default: 20 minutes). 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. To continue running the export tool, first increase the value of the -

Dmd.rmitimeout parameter (maximum: 1,440 minutes (24 hours), and then run the export tool. For details about -

Dmd.rmitimeout, see the Operands table for the Java command in

Java on page 4-37 . If the error persists, contact

the Hitachi Data Systems customer support.

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

.

For details on invalid monitoring data, see Causes of Invalid

Monitoring Data on page 4-56 .

The monitoring data in the CSV file includes

(-1).

• When the Export

Tool terminated abnormally due to error, the row of

Check License is shown as

Unmarshal

Exception 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 the DKCMAIN firmware/

Device Manager - Storage Navigator software and Export Tool versions. Confirm whether versions of these programs are correct.

Troubleshooting


7-3


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 displayed

3. In the Text Import.zip - Step 1 of 3 dialog box, click Next.

Text Import.zip - Step 2 of 3 dialog box is displayed

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

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

When you executed the

Export Tool with many volumes specified, the

Export Tool terminated abnormally while collecting 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.

Messages issued by the Export tool

If 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 to resolve errors.

Export Tool messages

Connection to the server has not been established.

Execution stops.

Illegal character: "character"

Invalid length: token

Invalid range: range

Invalid value: "value"

Login failed

Probable causes and recommended action

Connection to the server has not been established. Use the login subcommand.

Execution stops. Remove errors.

An illegal character is used. Use legal characters.

The length is invalid. Specify a value that has a correct length.

The specified range is invalid. Specify the correct range.

The specified value is invalid. Specify a correct value.

An attempt to log into SVP failed. Probable causes are:

1. An incorrect operand is used for the ip subcommand.

2. An incorrect operand is used for the dkcsn subcommand.

3. An incorrect operand is used for the login subcommand.

7-4

Troubleshooting



Serial-No not found

Missing command file

Missing group name

Missing host name

Missing output directory

Missing password

Missing ip

Missing dkcsn

Missing time range

Missing user ID

Out of range: range

Permission Denied.


4. The specified user ID is used by another person, and the person is being logged in.

5. Currently, Server Priority Manager window is in use by another user.

6. Currently, another user is running the Export Tool.

If the error is not caused by the conditions listed above, see

Troubleshooting the Export Tool for Performance

Monitor on page 7-2

.

If the error is caused by the fourth or fifth condition listed above, take one of the following actions:

• Ask the other user to close the Server Priority

Manager window.

• Ask the other user to log off.

• Wait for the other user to quit the Export Tool.

The serial number of the system in which to obtain monitoring data cannot be found.

Specify the serial number of the system connected to the SVP.

The command file is not specified. Specify the name of the command file correctly.

No operand is specified in the group subcommand.

Specify operands for the subcommand.

No host name is specified. Specify a host name.

No directory is specified for saving files. Specify the directory for saving files.

The Export Tool cannot find the user ID, which is used to log into SVP. Specify the password.

The ip subcommand is not used. Use the ip command.

The dkcsn subcommand is not specified. Specify the dkcsn subcommand first.

Specify the time range.

The Export Tool cannot find the user ID, which is used to log into SVP. Specify the user ID.

The value is outside the range.

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

The user ID does not have the required permission.

The user ID needs to have permission for at least one of the following: Performance Monitor, TrueCopy, Universal

Replicator, or global-active device.

Troubleshooting


7-5

Export Tool messages Probable causes and recommended action

RMI server error (part-code, error-number)

Unable to display help message

Unable to get serial number

An error occurs at the RMI server. For detailed information, see the Hitachi Device Manager - Storage

Navigator Messages.

The Export Tool cannot display the online help due to a system error.

The Export Tool cannot obtain the serial number due to a system error.

SVP does not contain monitoring data.

Unable to get time range for monitoring

Unable to read command file: file

Unable to use the command: command

The Export Tool cannot read the command file. Specify the name of the command file correctly.

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

Unsupported operand: operand

Unsupported option: 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.

Specify the following subcommand before login subcommand: retry

The Export Tool does not support the specified command. Specify a correct command.

The specified operand is not supported. Correct the specified operand.

The specified option is not supported. Correct the specified option.

Start gathering group data

Target = xxx, Total = yyy End gathering group data

The retry subcommand is written in an incorrect position in the command file.

Write the retry subcommand before the login subcommand.

The Export Tool starts collecting data specified by the group subcommand.

The number of target objects is xxx and the total number is yyy (see Note below).

The Export Tool ends collecting data.

Note: For example, if the storage system contains 100 parity groups and the command file contains the command line group PG 1-1:1-2, the Export Tool

7-6

Troubleshooting



Syntax error: "line"

[login]version unmatched


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.

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.

The export tool version does not correspond to the

Device Manager - Storage Navigator software version.

Upgrade the export tool to match the export tool and

Device Manager - Storage Navigator software versions.

Troubleshooting Server Priority Manager


The WWN of a host bus adapter is displayed in red on the WWN tab.

The HBA for the WWN that is displayed in red is connected to two or more ports, but the traffic between the HBA and some of the ports is not monitored by Performance Monitor. When many-to-many connections are established between HBAs and ports, make sure that all traffic between HBAs and ports is monitored. For details, see


.

Troubleshooting Virtual Partition Manager

Error

The CLPR name cannot be changed.

The parity group in a CLPR cannot be migrated to another

CLPR.

Cause

You cannot assign the same name to more than one

CLPR. The name you entered is already in use or is a reserved name. Enter another name. For more

information, see CLPR names on page 6-2

.

• Make sure that all interleaved parity groups belong to the same CLPR.

• Make sure to click Apply when creating a new

CLPR.

Calling Hitachi Data Systems customer support

If you need to call the Hitachi Data Systems Support Center, make sure to provide as much information about the error as possible, including:

• The circumstances surrounding the error or failure.

Troubleshooting


7-7

• The exact content of any error messages displayed on the host systems.

• The exact content of any error messages displayed by Device Manager -

Storage Navigator.

• The Device Manager - Storage Navigator configuration information (use the Dump Tool).

• The service information messages (SIMs), including reference codes and severity levels, displayed by Device Manager - Storage Navigator.

The 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://portal.hds.com

7-8

Troubleshooting


A

Performance Monitor GUI reference

This chapter provides detailed 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

A-1

Performance Monitor GUI reference


□

Edit Performance Objects window

□

Add Graph window

□

Wizard buttons

□

Navigation buttons

A-2



Performance Monitor main window

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.

•

Summary on page A-3

•

Monitored CUs tab on page A-4

•

Monitored WWNs tab on page A-5

Summary

The summary information of monitoring is displayed.

Buttons


Server Priority Manager*

Monitor Performance

Edit Monitoring Switch

Click to open the Server Priority Manager window.

Click to open the Monitor Performance window.

Click to open the Edit Monitoring Switch window.

*Appears when the secondary window is enabled in the Edit Information Display Settings window.

Summary information



A-3


Monitoring Switch

Sample Interval

Number of Monitored CUs* Number, from 0 to 64, of CUs currently being monitored.

Number of Monitored

LDEVs

Number of LDEVs currently being monitored:

• VSP G200: 0 to 2,048

• VSP G400 and VSP G600: 0 to 4,096

• VSP G800: 0 to 16,384

Number of Monitored

WWNs*

Number, from 0 to 2048, of WWNs currently being monitored.

*Appears only for VSP G800.

Current monitoring status:

Enabled: Performance Monitor is monitoring the storage system.

Disabled: The storage system is not being monitored.

Current sampling interval, from 1 to 15 minutes, for which statistics are collected during monitoring.

This value is available when Enabled is selected in the

Monitoring Switch field. If Disabled is selected, a hyphen appears.

Monitored CUs tab

Use this tab to view information about the CUs that are monitored. This tab displays only for VSP G800.

Item

Edit CU Monitor Mode

View CU Matrix

Export

Description

Click to open the Edit CU Monitor Mode window.

Click to open the View CU Matrix window.

Displays the window for outputting table information.

Item

CU

Number of LDEVs

Description

Monitored CU number.

Number of LDEVs included in the CU that are monitored.

A-4



Monitored WWNs tab

Use this tab to view information about the WWNs that are currently being monitored.

Item

Port ID

HBA WWN

WWN Name

Status

Description

Name of the port of the monitored WWN.

Host bus adapter ID of the monitored WWN.

A WWN name is up to 64 alphanumeric characters and some signs.

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.

Click to open the Edit WWN Monitor Mode window.

Edit WWN Monitor Mode

Add New Monitored WWNs

Edit WWN

Delete Unused WWNs*

Add to Ports*

Click to open the Add New Monitored WWNs window.

Click to open the Edit WWN window.

Click to open Delete Unused WWNs window.

Click to open the Add to Ports window.

Export* Displays the window for outputting table information.

*Appears when you click More Actions.

Edit Monitoring Switch wizard

Related topics

•

Starting monitoring on page 2-7

•

Stopping monitoring on page 2-18

•


•

Confirm window for Edit Monitoring Switch on page A-6



A-5

Edit Monitoring Switch window

Use this window to start and stop performance monitoring and to specify the sampling interval for how often to monitor statistics.

Setting fields

Item

Monitoring Switch

Sample Interval

Description

Specify the monitoring status.

Enable: Performance Monitor is monitoring the storage system.

Disable: Performance Monitor is not monitoring the storage system.

Specify the time interval of collecting statistics. You can specify from 1 to 15 minutes in intervals of 1 minute. The default is blank.

Confirm window for Edit Monitoring Switch

Use this window to confirm the specified monitoring information and to assign a task name to the editing task.

A-6



Monitoring Switch Setting table

Confirm the monitoring switch information to be changed.

Item

Monitoring Switch

Sample Interval

Description

Following monitoring statuses of the storage system.

Enabled: Performance Monitor is monitoring the storage system.

Disabled: Performance Monitor is not monitoring the storage system.

Time interval of collecting statistics.

Monitor Performance window

Use this window to specify the monitoring period and monitoring objects that will be displayed in graphs. You can set a maximum of eight monitoring objects per graph panel. You can set a maximum of four graph panels with up to 16 monitoring objects.



A-7

Data Range

Graphs are displayed according to the value specified in the Sample Interval field in the Edit Monitoring Switch window. You can specify the sampling interval from 1 to 15 minutes. The interval for measuring or storing the information depends on the number of CUs to be monitored.

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. When this option is selected, you cannot change the date field in the Set Range option.

A-8



Performance Objects

Object:

Item

Monitor Data:

Description

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.

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 A-10

.

Objects that can be displayed in graphs. For details, see

Available Objects table on page A-18 .

Performance Object

Selection:

Add

Adds objects to display the graph.



A-9

Selected Objects table

Item

Object

Monitor Data

Object ID

Remove

Description

Object types selected in the Performance Objects area.

Monitor data types selected in the Performance Objects area.

IDs of the selected objects.

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

A-10



MP


Object field

Item on left side of Monitor

Usage Rate

Data field

%

Unit of monitoring data

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


None

None

Object field


Usage Rate

Write Pending Rate

%

%


• If Fibre Port is selected on the left side of the Object field, the item on the right side of the Monitor Data field is blank.


Object field

Target

Initiator


Data field

Throughput

Data Trans.

Response Time

Throughput

Data Trans.

Response Time

Unit of monitoring

IOPS

MB/s ms

IOPS

MB/s ms

data

• If iSCSI Port is selected on the left side of the Object field, the item on right side of the Monitor Data field is blank.


Object field

Target

Initiator


Data field

Throughput

Data Trans.

Response Time

Throughput

Data Trans.

Response Time


IOPS

MB/s ms

IOPS

MB/s ms

data

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



A-11


WWN

Port

Object field


Data field

Throughput

Data Trans.

Response Time

Throughput

Data Trans.

Response Time


IOPS

MB/s ms

IOPS

MB/s ms

• If Logical Device is selected on the left side of the Object field and if Base is selected on the right of the Object field, the following items can be selected.



Total Throughput

Read Throughput

Write Throughput

Cache Hit

Data Trans.

Response Time

Back Trans.

Item on right side of Monitor

Data field

Total

Sequential

Random

Total

Sequential

Random

Total

Sequential

Random

Read (Total)

Read (Sequential)

Read (Random)

Write (Total)

Write (Sequential)

Write (Random)

Total

Read

Write

Total

Read

Write

Total

monitoring data

IOPS

IOPS

IOPS

%

MB/s ms

Unit of

count/sec

A-12






Data field


Cache To Drive

Drive To Cache (Sequential)

Drive To Cache (Random)

None

Drive Usage Rate

1

Drive Access Rate

1 Read (Sequential)

Read (Random)

%

%

Write (Sequential)

Write (Random)

ShadowImage

1

None %

Notes:

1

.

Only information about internal volumes is displayed. Information about external volumes is not displayed.

• If Logical Device is selected on the left side of the Object field and if TC or

GAD is selected on the right side of the Object field, the following items can be selected.


Object field

RIO

Pair Synchronization Rate

Differential Track

Initial Copy

Update Copy


Data field

Total

Write

Error

None

None

Throughput

Data Trans.

Response Time

Throughput

Data Trans.

Response Time


count

% count count

MB/s ms count

MB/s ms

data

• If Logical Device is selected on the left side of the Object field and if UR is selected on the right side of the Object field, the following items can be selected.


Object field

Write Host I/O


Throughput

Data field


IOPS

data



A-13


Object field

Initial Copy


Data field

Data Trans.

Cache Hit

Data Trans.


MB/s

%

MB/s

• 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. A parity group is displayed only when the CU number of each LDEV within the parity group is to be monitored.



Total Throughput

Read Throughput

Write Throughput

Cache Hit

Data Trans.

Response Time

Back Trans.


Data field

Total

Sequential

Random

Total

Sequential

Random

Total

Sequential

Random

Read (Total)

Read (Sequential)

Read (Random)

Write (Total)

Write (Sequential)

Write (Random)

Total

Read

Write

Total

Read

Write

Total

Cache To Drive


monitoring data

IOPS

IOPS

IOPS

%

MB/s ms

Unit of

count/sec

A-14






Data field



Drive Usage Rate* None %

*Only information about internal volumes is displayed. Information about external volumes is not displayed.

• If LUN is selected on the left side of the Object field and if Base is selected on the right of the Object field, the following items can be selected.



Total Throughput

Read Throughput

Write Throughput

Cache Hit

Data Trans.

Response Time

Back Trans.


Data field

Total

Sequential

Random

Total

Sequential

Random

Total

Sequential

Random

Read (Total)

Read (Sequential)

Read (Random)

Write (Total)

Write (Sequential)

Write (Random)

Total

Read

Write

Total

Read

Write

Total

Cache To Drive


monitoring data

IOPS

IOPS

IOPS

%

MB/s ms

Unit of

count/sec



A-15




Data field



• If LUN is selected on the left side of the Object field and if TC or GAD is selected on the right of the Object field, following items can be selected.


Object field

RIO


Differential Track

Initial Copy

Update Copy


Data field

Total

Write

Error

None

None

Throughput

Data Trans.

Response Time

Throughput

Data Trans.

Response Time


count

% count count

MB/s ms count

MB/s ms

data

• If LUN is selected on the left side of the Object field and if UR is selected on the right of the Object field, following items can be selected.


Object field

Write Host I/O

Initial Copy


Throughput

Data Trans.

Cache Hit

Data Trans.

Data field


IOPS

MB/s

%

MB/s

data

• If Journal is selected on the left side of the Object field, UR is selected on the right side of the Object field.


Object field

Write Host I/O

Initial Copy


Throughput

Data Trans.

Cache Hit

Data Trans.

Data field


IOPS

MB/s

%

MB/s

data

A-16




Object field

Master Journal

Restore Journal


Data field

Throughput

Journal

Data Trans.

Response Time

Data Usage Rate


Throughput

Journal

Data Trans.

Response Time

Data Usage Rate



IOPS count/sec

MB/s ms

%

%

IOPS count/sec

MB/s ms

%

%

• If Entire Storage System is selected on the left side of the Object field and if TC or GAD is selected on the right side of the Object field, following items can be selected.


Object field

RIO


Differential Track

Initial Copy

Update Copy


Data field

Total

Write

Error

None

None

Throughput

Data Trans.

Response Time

Throughput

Data Trans.

Response Time


count

% count count

MB/s ms count

MB/s ms

data

• If Entire Storage System is selected on the left side of the Object field and if UR is selected on the right side of the Object field, following items can be selected.



A-17


Object field

Write Host I/O

Initial Copy

Master Journal

Restore Journal


Data field

Throughput

Data Trans.

Cache Hit

Data Trans.

Throughput

Journal

Data Trans.

Response Time

Throughput

Journal

Data Trans.

Response Time


IOPS

MB/s

%

MB/s

IOPS count/sec

MB/s ms

IOPS count/sec

MB/s ms

• If External Storage is selected on the left side of the Object field, following items can be selected.


Logical Device

Parity Group



Data Trans.

Response Time

Data Trans.

Response Time



Total

Read

Write

Total

Read

Write

Total

Read

Write

Total

Read

Write


MB/s ms

MB/s ms

data

Available Objects table

The items appearing in the Available Objects table depend on the objects selected in the Performance Objects fields.

A-18



Monitoring object

Fibre Port/Target

Fibre Port/Initiator iSCSI Port/Target iSCSI Port/Initiator

WWN/WWN

Port ID

Port ID

HBA WWN

Item

WWN/Port

WWN Name

Port ID

HBA WWN

WWN Name

Logical Device/Base LDEV ID

LDEV Name

Logical Device/TC/GAD LDEV ID

Logical Device/UR

LDEV Name

LDEV ID

Description

Name of the port. Only the ports assigned to the user are displayed.


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. Only the WWNs that correspond to the ports assigned to the user are displayed.

Nickname of the host bus adapter. A WWN name is up to

64 alphanumeric characters and some signs.


WWN of the host bus adapter. A

WWN is a 16-digit hexadecimal number used as the unique identifier for a host bus adapter.



ID of the volume, in the following format:

LDKC:CU:LDEV. Only the LDEVs assigned to the user are displayed.

Name of the LDEV. LDEV Name is the combination of fixed characters and numbers.





LDKC:CU:LDEV. Only the LDEVs



A-19

A-20


Parity Group

LUN/Base

LUN/TC/GAD

LUN/UR

LDEV Name

Item

Parity Group ID

Description

assigned to the user are displayed.


ID of the parity group. Only the parity groups assigned to the user are displayed.

Name of the port.

Port ID

• Item: Type

• Description: Type of port

Host Group Name/iSCSI

Target Alias

• Item: iSCSI target name

• Description: Name of the iSCSI target

LUN

Name of the host group.

ID of the LUN. Only the LUNs that correspond to the host groups and LDEVs assigned to the user are displayed.

Name of the port.

Port ID

• Item: Type



Target Alias



LUN


Port ID

• Item: Type



Target Alias




Name of the port.





LUN

Item

External Storage/Logical

Device

LDEV ID

LDEV Name

External Storage/Parity

Group

Parity Group ID

Controller/MP

Cache

Entire Storage System/

TC/GAD


UR

Journal/UR

MP unit ID/MP ID

MP unit ID

Cache

Object

Object

Journal ID

Description





Parity group ID of the external volume. Only the parity groups assigned to the user are displayed.

ID of an MP unit and processor.

ID of an MP unit.

Name of the cache.

Item for entire storage system.


ID of the journal.

Edit CU Monitor Mode wizard

Related topics

•


•

Edit CU Monitor Mode window on page A-21

•

Confirm window for Edit CU Monitor Mode on page A-25

Edit CU Monitor Mode window

This window contains information about all 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. This window does not display for VSP G200, VSP G400, and VSP G600.



A-21

A-22



Unmonitored CUs table

A table of the CUs that are going to be unmonitored.

Item

CU

Number of LDEVs

Current Monitor Mode

Select by Parity Groups

Description

CUs not to be monitored.

Number of LDEVs in the CU not to be monitored.

Enabled: The CU is a monitoring target object.

Disabled: The CU is not a monitoring target object.

Click to open the Select by Parity Group window.

Add

Click to add CUs to Monitored CUs table.

Remove

Click to remove CUs from Monitored CUs table.



A-23

Monitored CUs table

A table of the CUs that are going to be monitored.

Item

CU

Number of LDEVs


View CU Matrix

Description

CUs to be monitored.

Number of LDEVs in the CU to be monitored.

Enabled: The CU is a monitoring target object.

Disabled: The CU is not a monitoring target object.


A-24



Confirm window for Edit CU Monitor Mode

Use this window to confirm the edited CU monitoring mode information and to assign a task name to the editing task. This window does not display for

VSP G200, VSP G400, and VSP G600.

Selected CUs to Enable Monitor table

Confirm the information about the CUs to be monitored.

Item

CU

Number of LDEVs

View CU Matrix

Description

CUs to be monitored.

Number of LDEVs in the CU to be monitored.




A-25

Selected CUs to Disable Monitor table

Information about the CUs not to be monitored.

Item

CU

Number of LDEVs

View CU Matrix

Description

CUs not to be monitored.

Number of LDEVs in the CU not to be monitored.


• CU which is being monitored

• CU which is scheduled to be monitored

• CU which is scheduled to be released from monitoring.

View CU Matrix window

Use this window to view a matrix of the monitoring status of all CUs in one

LDKC. The cell markers indicate the monitoring status of the individual CUs.

This window does not display for VSP G200, VSP G400, and VSP G600.

A-26



Monitored CUs table

Item

Monitored CUs

Number of Monitored CUs:

Monitored CUs

Description

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

Total count of monitored CUs.

Cell marker indicating that a CU is being monitored.



A-27

Item

Set Monitored CUs

Release Monitored CUs

Description

Cell marker indicating that the CU is scheduled to be monitored.

Cell marker indicating that the CU is scheduled to be released from monitoring.

Related topics

•

Confirming the status of CUs to monitor on page 2-16

Select by Parity Groups window

When you select a parity group, all the CUs included in the parity group display in the Edit CU Monitor Mode window. This window does not display for VSP G200, VSP G400, and VSP G600.

A-28



Available Parity Groups table

Item

Parity Group ID

Number of CUs

Detail

Description

ID of the parity group.

Number of CUs included in the parity group.

Click to display the Parity Group Properties window.



A-29

Parity Group Properties window

Use this window to view information about the CUs in the parity group selected in the previous window. This window does not display for VSP G200,

VSP G400, and VSP G600.

Parity Group Properties table

Item

Parity Group ID

Description

Identification number of the parity group.

A-30



CUs table

Item

CU

Number of LDEVs

Description

Identification number of the CU in this parity group.

Number of LDEVs included in the individual CUs.

Edit WWN wizard

Related topics

•

Editing the WWN nickname on page 2-11

•

Edit WWN window on page A-31

•

Confirm window for Edit WWN on page A-32

Edit WWN window

Use this window to edit the HBA WWN and WWN name of the WWN to be monitored.



A-31

Setting fields

Item

HBA WWN

WWN Name

Description

Edit the worldwide name of the host bus adapter. WWNs are 16-digit hexadecimal numbers used to identify host bus adapters.

Edit a WWN name. Use up to 64 alphanumeric characters and some symbols for a WWN name.

Confirm window for Edit WWN

Use this window to confirm the edited HBA WWN and WWN Name and to assign a task name to the editing task.

Monitored WWNs table

Confirm the information about the WWNs to be monitored.

Item

HBA WWN

WWN Name

Description

HBA WWNs to be applied.

WWN Names to be applied.

A-32



Edit WWN Monitor Mode wizard

Related topics

•

Adding new WWNs to monitor on page 2-8

•

Edit WWN Monitor Mode window on page A-33

•

Confirm window for Edit WWN Monitor Mode on page A-36

Edit WWN Monitor Mode window

Use this window to specify WWNs to be monitored or not to be monitored.



A-33

Unmonitored WWNs table

A-34

A table of WWNs that are going to be unmonitored.

Item

Port ID

HBA WWN

WWN Name


Current Status

Description

Name of the port.

Worldwide name of the host bus adapter


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.

Status of the port connected with WWN.





Add

Click to add WWNs to the Monitored WWNs table.

Remove

Click to remove WWNs from the Monitored WWNs table.

Monitored WWNs table

A table of WWNs that are going to be unmonitored.

Port ID

HBA WWN


Name of the port.

Worldwide name of the host bus adapter.



A-35

Item

WWN Name


Current Status

Description


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.

Status of the port connected with WWN.



Confirm window for Edit WWN Monitor Mode

Use this window to confirm the edited monitoring information and to assign a task name to the editing task.

Selected WWNs to Enable Monitor table

Confirm the information about the WWNs to be monitored.

Item

Port ID

HBA WWN

Description

Port name to be added and monitored.

Worldwide name of the host bus adapter to be added and monitored.

A-36



WWN Name

Item

Status

Description

Nickname of WWN to be added and monitored. The name consists of up to 64 alphanumeric characters and some signs.

Status of a WWN to be added and monitored.

Normal: WWN connected with a port is the monitoring target object.


Selected WWNs to Disable Monitor table

Confirm the information about the WWNs not to be monitored.

Item

Port ID

HBA WWN

WWN Name

Status

Description

Port name not to be monitored.

Worldwide name of the host bus adapter not to be monitored.

Nickname of WWN not to be monitored. The name consists of up to 64 alphanumeric characters and some signs.

Status of a WWN not to be monitored.

Normal: The WWN connected with a port is the monitoring target object.


Delete Unused WWNs window

Use this window to name the task to delete unused WWNs.



A-37

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.

Related topics

•

Removing WWNs to monitor on page 2-9

Add New Monitored WWNs wizard

Related topics

•

Adding WWNs to ports on page 2-10

•

Add New Monitored WWNs window on page A-38

•

Confirm window for Add New Monitored WWNs on page A-42

Add New Monitored WWNs window

Use this window to add new WWNs to be monitored.

A-38



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.



A-39

Available Ports table

Item

Port ID

Number of Monitored

WWNs

Number of Unmonitored

WWNs

Description

Name of the port available in the storage system.

Number of monitored WWNs in the port.

Number of unmonitored WWNs in the port.

Add

Select ports, then click Add to add the combinations of HBA WWN and the selected ports into the Selected WWNs table.

A-40



Selected WWNs table

A list of WWNs to be monitored.

Port ID

HBA WWN

WWN Name

Item

Remove

Description

Name of the port selected for monitoring.

WWN selected for monitoring.

WWN name is up to 64 alphanumeric characters and some signs.

Select the row to be deleted. Click to remove a row from the table.



A-41

Confirm window for Add New Monitored WWNs

Use this window to confirm the new monitoring information and to assign a task name to the editing task.


Confirm the list of combinations of ports and WWNs added as monitoring target objects.

Item

Port ID

HBA WWN

WWN Name

Description

Name of the port selected for monitoring.



Add to Ports wizard

Related topics

•

Connecting WWNs to ports on page 2-12

•

Add to Ports window on page A-43

•

Confirm window for Add to Ports on page A-46

A-42



Add to Ports window

Use 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

Specify a worldwide name using up to 64 characters for a WWN name.



A-43

Available Ports table

A list of available ports in the storage system.

Item

Port ID

Number of Monitored

WWNs

Number of Unmonitored

WWNs

Description

Name of the port available in the storage system.

Number of monitored WWNs in the port.

Number of unmonitored WWNs in the port.

Add

Select ports, then click Add to add the combinations of HBA WWN and the selected ports into the Selected WWNs table.

A-44




A list of WWNs to be monitored.

Item

Port ID

HBA WWN

WWN Name

Remove

Description

Name of the port selected for monitoring

The WWN selected for monitoring.

The WWN name is up to 64 alphanumeric characters and some signs.

Select the row to be deleted. Click to remove a row from the table.



A-45

Confirm window for Add to Ports

Use this window to confirm new WWNs related to ports and to assign a task name to the editing task.


Confirm the information of the WWNs to become the monitoring target objects.

Item

Port ID

HBA WWN

WWN Name

Description

Name of the port selected for monitoring



Monitor window

Use this window to view line graphs of monitored objects.

A-46



Graph panel

Item

Graph display area

Description

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 put the mouse cursor over a point on the graph, a tool tip with more information appears.

• When you click a note on the right of the graph panel, you can show or hide points on the graph panel. However, if the graph displays only one point on the X axis, the graph is always displayed on the screen. In this case, the graph cannot be displayed by clicking the icon that is displayed in the explanatory notes.

• Up to eight graphs can be displayed in one graph panel.

• You can view up to 16 graphs across a total of four panels.

Shows graph panels.

Graph panel

Shows line graphs of monitored objects.

Item

Vertical Scale:

Description

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



A-47

Item

The button in the upper right of the graph panel

Edit Performance Objects

Delete Graph

Description

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.

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

Opens the Edit Performance Objects window where you can change the objects to be monitored.

Deletes the graph panel.

Graph display area

Shows graph panels.

Item

Monitoring Term

Description

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 and the date of last update are also shown.

The following icon and the message are displayed while changing the configuration:

Edit Time Range

Add Graph

Graphs cannot be updated due to the configuration changing.

Wait for a while.

Opens the Edit Time Range window where you can edit the time range for monitoring statistics.

Opens the Add Graph window to add a new graph.

Related topics

•

Deleting a graph on page 2-23

Edit Time Range window

Use this window to select a date and time range for displaying monitoring data in a performance graph.

A-48



Setting fields

Item

Time Range

From:

To:

Description

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

When you specify a time range, Performance Monitor calculates the length of the specified period and displays the total time in hours and minutes.

Specify the date and time to start monitoring performance.

Specify the date and time to stop monitoring performance.

Related topics

•

Changing the time period displayed on the graph panel on page 2-22

Edit Performance Objects window

Use this window to select the monitoring object for displaying in a performance graph.



A-49

Object

A-50



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

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 A-60

.

Add




A-51


A-52

Objects to display the graph.

Item

Object

Monitor Data

Object ID

Remove

Description

Object to display the graph.

Type of monitoring data.

ID of the monitoring object.

Remove the object in this table.



Performance window.




MP


Object field


Usage Rate

Data field

%


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


None

None

Object field


Usage Rate

Write Pending Rate

%

%




Object field

Target

Initiator


Data field

Throughput

Data Trans.

Response Time

Throughput

Data Trans.

Response Time


IOPS

MB/s ms

IOPS

MB/s ms

data

• If iSCSI Port is selected on the left side of the Object field, the item on the right side of the Monitor Data field is blank.


Object field

Target

Initiator


Data field

Throughput

Data Trans.

Response Time

Throughput

Data Trans.

Response Time


IOPS

MB/s ms

IOPS

MB/s ms

data




A-53

A-54


WWN

Port

Object field


Data field

Throughput

Data Trans.

Response Time

Throughput

Data Trans.

Response Time


IOPS

MB/s ms

IOPS

MB/s ms

• Logical Device is selected on the left side of the Object field or Base is selected on the right of the Object field.



Total Throughput

Read Throughput

Write Throughput

Cache Hit

Data Trans.

Response Time

Back Trans.


Data field

Total

Sequential

Random

Total

Sequential

Random

Total

Sequential

Random

Read (Total)

Read (Sequential)

Read (Random)

Write (Total)

Write (Sequential)

Write (Random)

Total

Read

Write

Total

Read

Write

Total

Cache To Drive

monitoring data

IOPS

IOPS

IOPS

%

MB/s ms

Unit of

count/sec






Data field




None

Drive Usage Rate

1

Drive Access Rate

1

Read (Sequential)

Read (Random)

Write (Sequential)

%

%

ShadowImage

1

1

.

Write (Random)

None %



GAD is selected on the right side of the Object field, the following items can be selected.


Object field

RIO


Differential Track

Initial Copy

Update Copy


Data field

Total

Write

Error

None

None

Throughput

Data Trans.

Response Time

Throughput

Data Trans.

Response Time


count

% count count

MB/s ms count

MB/s ms

data

• If Logical Device is selected on the left side of the Object field and if UR is selected on the right side of the Object field, following items can be selected.


Object field

Write Host I/O


Throughput

Data Trans.

Data field


IOPS

MB/s

data



A-55

A-56


Object field

Initial Copy


Data field

Cache Hit

Data Trans.


%

MB/s

• The item on the right side of the Object field is blank.




Data field


Total Throughput

Read Throughput

Write Throughput

Cache Hit

Data Trans.

Total

Sequential

Random

Total

Sequential

Random

Total

Sequential

Random

Read (Total)

Read (Sequential)

Read (Random)

Write (Total)

Write (Sequential)

Write (Random)

Total

Read

Write

Total

IOPS

IOPS

IOPS

%

MB/s

Response Time ms

Back Trans.

Read

Write

Total

Cache To Drive

Drive To Cache (Sequential) count/sec

Drive Usage Rate*


None %







Total Throughput

Read Throughput

Write Throughput

Cache Hit

Data Trans.

Response Time

Back Trans.


Data field

Total

Sequential

Random

Total

Sequential

Random

Total

Sequential

Random

Read (Total)

Read (Sequential)

Read (Random)

Write (Total)

Write (Sequential)

Write (Random)

Total

Read

Write

Total

Read

Write

Total

Cache To Drive



monitoring data

IOPS

IOPS

IOPS

%

MB/s ms

Unit of

count/sec



Object field

RIO


Total

Write

Data field


count

data



A-57


Object field


Differential Track

Initial Copy

Update Copy


Data field

Error

None

None

Throughput

Data Trans.

Response Time

Throughput

Data Trans.

Response Time


% count count

MB/s ms count

MB/s ms

data

• If Logical Device is selected on the left side of the Object field and if UR is selected on the right of the Object field, following items can be selected.


Object field

Write Host I/O

Initial Copy


Throughput

Data Trans.

Cache Hit

Data Trans.

Data field


IOPS

MB/s

%

MB/s

data



Object field

Write Host I/O

Initial Copy

Master Journal

Restore Journal


Data field

Throughput

Data Trans.

Cache Hit

Data Trans.

Throughput

Journal

Data Trans.

Response Time

Data Usage Rate


Throughput


IOPS

MB/s

%

MB/s

IOPS count/sec

MB/s ms

%

%

IOPS

data

A-58




Object field


Data field

Journal

Data Trans.

Response Time

Data Usage Rate



count/sec

MB/s ms

%

%



Object field

RIO


Differential Track

Initial Copy

Update Copy


Data field

Total

Write

Error

None

None

Throughput

Data Trans.

Response Time

Throughput

Data Trans.

Response Time


count

% count count

MB/s ms count

MB/s ms

data



Object field

Write Host I/O

Initial Copy

Master Journal


Throughput

Data Trans.

Cache Hit

Data Trans.

Throughput

Journal

Data Trans.

Data field


IOPS

MB/s

%

MB/s

IOPS count/sec

MB/s

data



A-59


Object field

Restore Journal


Data field

Response Time

Throughput

Journal

Data Trans.

Response Time


ms

IOPS count/sec

MB/s ms



Logical Device

Parity Group



Data Trans.

Response Time

Data Trans.

Response Time



Total

Read

Write

Total

Read

Write

Total

Read

Write

Total

Read

Write


MB/s ms

MB/s ms

data



Item Monitoring object

Fibre Port/Target

Fibre Port/Initiator iSCSI Port/Target iSCSI Port/Initiator

Port ID

Port ID

Description



A-60




WWN/WWN HBA WWN

Item

WWN/Port

WWN Name

Port ID

HBA WWN

WWN Name

Logical Device/Base LDEV ID

LDEV Name

Logical Device/TC/GAD LDEV ID

Logical Device/UR

LDEV Name

LDEV ID

LDEV Name

Description




















A-61


Parity Group

LUN/Base

LUN/TC/GAD

LUN/UR

Item

Parity Group ID


Group

Parity Group ID

Controller/MP

Port ID

Type


Target Alias iSCSI Target Name

LUN

Port ID

Type



LUN

Port ID

Type



LUN


Device

LDEV ID

LDEV Name

MP Unit ID/MP ID

Description


Name of the port.

Type of the port.

Name of the host group or iSCSI target alias.

Name of the iSCSI target.


Name of the port.

Type of the port.




Name of the port.

Type of the port.







Parity group ID of the external volume. Only the parity groups assigned to the user are aisplayed.


A-62




Cache


TC/GAD


UR

Journal/UR

MP Unit ID

Cache

Object

Item

Object

Journal ID

Description

ID of an MP unit.

Name of the cache.



ID of the journal.

Related topics

•

Changing the data displayed on a graph on page 2-21

Add Graph window

Use this window to add the monitoring object to display a graph.



A-63

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

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 A-74

.

A-64



Add



Item

Object

Monitor Data

Object ID

Description

Object to display the graph.

Type of monitoring data.

ID of the monitoring object.



A-65

A-66

Remove


Remove the object in this table.



Performance window.


MP


Object field


Data field

Usage Rate %


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


None

None

Object field


Usage Rate

Write Pending Rate

%

%




Object field

Target

Initiator


Data field

Throughput

Data Trans.

Response Time

Throughput

Data Trans.

Response Time


IOPS

MB/s ms

IOPS

MB/s ms

data

• If iSCSI Port is selected on the left side of the Object field, the item on the right side of the Monitor Data field is blank.


Object field

Target


Throughput

Data Trans.

Data field


IOPS

MB/s

data




Initiator

Object field


Data field

Response Time

Throughput

Data Trans.

Response Time


ms

IOPS

MB/s ms



Object field

WWN

Port


Data field

Throughput

Data Trans.

Response Time

Throughput

Data Trans.

Response Time


IOPS

MB/s ms

IOPS

MB/s ms

data

• If Logical Device is selected on the left side of the Object field and if Base is selected on the right of the Object field, the following items can be selected.



Total Throughput

Read Throughput

Write Throughput

Cache Hit


Data field

Total

Sequential

Random

Total

Sequential

Random

Total

Sequential

Random

Read (Total)

Read (Sequential)

Read (Random)

Write (Total)

Write (Sequential)

IOPS

IOPS

%


IOPS



A-67

A-68




Data field


Data Trans.

Response Time

Write (Random)

Total

Read

Write

Total

Read

Write

MB/s ms

Back Trans.

Total

Cache To Drive



None count/sec

Drive Usage Rate

1

Drive Access Rate

1

Read (Sequential)

Read (Random)

Write (Sequential)

%

%

ShadowImage

1

Write (Random)

None %

Notes:

1

.



GAD is selected on the right side of the Object field, following items can be selected.


Object field

RIO


Differential Track

Initial Copy

Update Copy


Data field

Total

Write

Error

None

None

Throughput

Data Trans.

Response Time

Throughput


count

% count count

MB/s ms count

data




Object field


Data field

Data Trans.

Response Time


MB/s ms

• If Logical Device is selected on the left side of the Object field and if UR is selected on the right side of the Object field, following items can be selected.


Object field

Write Host I/O

Initial Copy


Throughput

Data Trans.

Cache Hit

Data Trans.

Data field


IOPS

MB/s

%

MB/s

data

• 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. A parity group is displayed only when the CU number of each LDEV within the parity group is to be monitored.



Total Throughput

Read Throughput

Write Throughput

Cache Hit

Data Trans.


Data field

Total

Sequential

Random

Total

Sequential

Random

Total

Sequential

Random

Read (Total)

Read (Sequential)

Read (Random)

Write (Total)

Write (Sequential)

Write (Random)

Total

IOPS

IOPS

%

MB/s


IOPS



A-69

A-70




Data field


Response Time

Back Trans.

Read

Write

Total

Read

Write

Total

Cache To Drive ms count/sec



None Drive Usage Rate* %





Total Throughput

Read Throughput

Write Throughput

Cache Hit

Data Trans.


Data field

Total

Sequential

Random

Total

Sequential

Random

Total

Sequential

Random

Read (Total)

Read (Sequential)

Read (Random)

Write (Total)

Write (Sequential)

Write (Random)

Total

Read

IOPS

IOPS

%

MB/s


IOPS





Response Time

Back Trans.


Data field

Write

Total

Read

Write

Total

Cache To Drive




ms count/sec



Object field

RIO


Differential Track

Initial Copy

Update Copy


Data field

Total

Write

Error

None

None

Throughput

Data Trans.

Response Time

Throughput

Data Trans.

Response Time


count

% count count

MB/s ms count

MB/s ms

data

• If LUN is selected on the left side of the Object field and if UR is selected on the right of the Object field, following items can be selected.


Object field

Write Host I/O

Initial Copy


Throughput

Data Trans.

Cache Hit

Data Trans.

Data field


IOPS

MB/s

%

MB/s

data




A-71


Object field

Write Host I/O

Initial Copy

Master Journal

Restore Journal


Data field

Throughput

Data Trans.

Cache Hit

Data Trans.

Throughput

Journal

Data Trans.

Response Time

Data Usage Rate


Throughput

Journal

Data Trans.

Response Time

Data Usage Rate



ms

%

%

IOPS

MB/s

%

MB/s

IOPS count/sec

MB/s

IOPS count/sec

MB/s ms

%

%



Object field

RIO


Differential Track

Initial Copy

Update Copy


Data field

Total

Write

Error

None

None

Throughput

Data Trans.

Response Time

Throughput

Data Trans.

Response Time


count

% count count

MB/s ms count

MB/s ms

data

A-72





Object field

Write Host I/O

Initial Copy

Master Journal

Restore Journal


Data field

Throughput

Data Trans.

Cache Hit

Data Trans.

Throughput

Journal

Data Trans.

Response Time

Throughput

Journal

Data Trans.

Response Time


IOPS

MB/s

%

MB/s

IOPS count/sec

MB/s ms

IOPS count/sec

MB/s ms

data



Logical Device

Parity Group



Data Trans.

Response Time

Data Trans.

Response Time



Total

Read

Write

Total

Read

Write

Total

Read

Write

Total

Read

Write


MB/s ms

MB/s ms

data



A-73



Item Monitoring object

Fibre Port/Target

Fibre Port/Initiator iSCSI Port/Target

WWN/WWN

WWN/Port

Logical Device/Base

Logical Device/TC/GAD

Port ID

Port ID

HBA WWN

WWN Name

Port ID

HBA WWN

WWN Name

LDEV ID

LDEV Name

LDEV ID

LDEV Name

Description















LDKC:CU:LDEV. Only theLDEVs assigned to the user aredisplayed.


A-74




Logical Device/UR

Parity Group

LUN/Base

LUN/TC/GAD

LUN/UR

LDEV ID

LDEV Name

Item

Parity Group ID

Port ID

Type



LUN

Port ID

Type



LUN

Port ID

Type



LUN


Device

LDEV ID

Description





Name of the port.

Type of the port.




Name of the port.

Type of the port.




Name of the port.

Type of the port.








A-75


LDEV Name

Item


Group

Parity Group ID

Controller/MP

Cache


TC/GAD


UR

Journal/UR

MP Unit ID/MP ID

MP Unit ID

Cache

Object

Object

Journal ID

Description


Parity group ID of the external volume. Only the parity groups assigned to the user are displayed.


ID of an MP unit.

Name of the cache.



ID of the journal.

Related topics

•

Adding a new graph on page 2-20

Wizard buttons

These standard buttons are used to set information in and navigate among the monitoring windows.

Item

Go to tasks window for status

Back

Next

Apply

Finish

Cancel

Help

Description

Check to go to the task window after clicking Apply.

Click to move to the previous task.

Click to move to the next task.

Click to apply the settings to the storage system.

Finishes the task.

Cancels the current task and closes this window.

Opens the help topic for this window.

Navigation buttons

These standard buttons are used to control the information appearing the monitoring windows.

A-76



Filter

Item

Select All Pages

Options

|<

<

Page

>

>|

Description

• ON: Click to activate the filter.

• OFF: Click to cancel the filter.

Click to select all pages.

Click to specify options for how the table displays information.

Click to view the first page.

Click to view the previous page.

Page numbers in N/M format, where N indicates the number of the current page and M indicates total number of pages.

Click to view the next page.

Click to view the last page.



A-77

A-78



B

Server Priority Manager GUI reference

This chapter provides detailed information about the Server Priority Manager

GUI. The Server Priority Manager window allows you to prioritize/nonprioritize ports and WWNs and create WWN monitor groups.

□

Server Priority Manager window

□

Port tab of the Server Priority Manager main window

□

WWN tab of the Server Priority Manager main window

□

Add WWN window

□

Change WWN and SPM Name window

□

Add New SPM Group window

□

Change Upper Limit window

□

Rename SPM Group window

Server Priority Manager GUI reference


B-1

Server Priority Manager window

The Server Priority Manager window displays the status of performance monitoring, allows you to set the monitoring term, and provides access to the

Server Priority Manager main window.

B-2

Item

Monitoring Switch

Monitoring Term

Description

Enable: Performance Monitor is monitoring the storage system

Disable: The storage system is not being monitored.

Specify a period in which to collect monitoring data and display in

Server Priority Manager main window. A day is set by default.

To set a date and time in the From and To fields, do either of the following:

• Move the sliders to the left or to the right to adjust the date and time.

• In the text box, select a date or time unit that you want to change and then use the up or down arrows.

Starting and ending times for collecting statistics are displayed on both sides of the slide bars. Performance Monitor stores the monitoring data between these times.

For example, if you want to view usage statistics within the range of 10:30 July 1 2013 to 22:30 July 31 2013, you set 2013/07/01

10:30 in the From field, set 2013/07/31 22:30 in the To field, and then click Apply.



Item

Open SPM Dialog

Description

When you specify dates and time in the From and To fields,

Performance Monitor calculates and displays the length of the specified period. The length of the period is in days.

From and To are unavailable if Server Priority Manager is in View mode or the monitoring data (that is, usage statistics) is not stored in the storage system.

Click Server Priority Manager to open the Server Priority Manager main window.

Port tab of the Server Priority Manager main window

Use this tab to set the limit on the performance of non-prioritized ports and set the threshold on the performance of prioritized ports.


Current Control

Status

Shows the current control status of the system.

• Port Control indicates the system is controlled by the upper limits and threshold specified on the Port tab.



B-3

B-4

Item

Control List

Statistic type list

Ports table

Description

• WWN Control indicates the system is controlled by the upper limits and threshold specified on the WWN tab.

• No Control indicates the system performance is not controlled by

Server Priority Manager.

Tip: If WWN Control is displayed when the Port tab is active, click

Apply to switch control so that Port Control is displayed.

Tip: To return the control status to No Control, specify Prio. for attributes of all ports and then click Apply.

Allows you to narrow ports appearing in the list:

• If All is selected, all ports appear in the list.

• If Prioritize is selected, only the prioritized ports appear in the list.

• If Non-Prioritize is selected, only the non-prioritized ports appear in the list.

If you change settings of a port, that port remains in the list regardless of the selection in the list.

Allows you to change the type of performance statistics to be displayed in the list.

• If IOPS (I/Os per second) is selected, the list displays I/O rates for ports. The I/O rate indicates the number of I/Os per second.

• If MB/s (megabytes per second) is selected, the list displays the transfer rates for ports. The transfer rate indicates the size of data transferred via a port in one second.

A list of ports, including the I/O rate or the transfer rate for each port.

You can specify the port attributes, and the threshold and upper limit of the port traffic.

The measurement unit for the values in the list can be specified by the drop-down list above this table. The port traffic (I/O rate and transfer rate) is monitored by Performance Monitor. To specify the monitoring period, use the Monitoring Term area of Performance Monitor.

The table contains these columns:

• Port indicates ports on the storage system.

• Ave.[IOPS] indicates the average I/O rate or the average transfer rate for the specified period.

• Peak[IOPS] indicates the peak I/O rate or the peak transfer rate of the ports for the specified period. This value means the top of the Max. line in the detailed port-traffic graph drawn in the Monitor

Performance window. For details, see Chapter 3, Hitachi

Performance Monitor data on page 3-1 .

• Attribute indicates the priority of each port. Prio indicates a prioritized port. Non-Prio indicates a non-prioritized port.

• Use the Threshold columns to specify the threshold for the I/O rate and the transfer rate for each prioritized port. Either the IOPS or MB/s column in the list is activated depending on the selection from the list above.

Use the IOPS column to specify the threshold for I/O rates. Use the MB/s column to specify the threshold for transfer rates.

To specify a threshold, double-click a cell to display the cursor in the cell. If you specify a value in either the IOPS or MB/s column,




the other column is unavailable. You can specify thresholds for I/O rates and transfer rates all together for different prioritized ports.

Even if you use the type of rate for the threshold different from that used for the upper limit values, the threshold control can work for all ports.

• Use the Upper columns to specify the upper limit on the I/O rate and the transfer rate for each non-prioritized port. Either the IOPS or MB/s column in the list is activated depending on the selection from the list above.

Use the IOPS column to specify the upper limit for I/O rates. Use the MB/s column to specify the upper limit for transfer rates.

To specify an upper limit, double-click a cell to display the cursor in the cell. If you specify a value in either of the IOPS or MB/s column, the other column is unavailable. You can specify upper limit values for I/O rates and transfer rates all together for different non-prioritized ports.

All Thresholds If you select this check box and enter a threshold value in the text box, the threshold value is applied to the entire storage system.

To specify the threshold for the I/O rate, select IOPS from the list on the right of the text box. To specify the threshold for the transfer rate, select MB/s from the list. For example, if you specify 128 IOPS in All

Thresholds, the upper limits on non-prioritized ports are disabled when the sum of I/O rates for all prioritized ports is below 128 IOPS.

Even if you use the different type of rate (IOPS or MB/s) for the threshold as that used for the upper limit values, the threshold control can work for all ports.

Delete ports if

CHA is removed

If you check this check box, Server Priority Manager deletes, from SVP, the setting information of Server Priority Manager on ports in channel adapters that have been removed.

When a channel adapter is removed, the port and its settings are removed from the Server Priority Manager main window automatically, but they remain in SVP. This may cause the old setting for Server

Priority Manager to be applied to a different channel adapter than the one newly-installed on the same location.

The Delete ports if CHA is removed check box is available only when the following Server Priority Manager settings on ports in a removed channel adapter remains on SVP:

• The setting of prioritized ports or non-prioritized ports.

• The setting of prioritized WWNs or non-prioritized WWNs.

Apply

Reset

Initialize

Applies the settings in this window to the storage system.

Restores the last applied settings in the window. When you click this button, all changes displayed with the blue text in the window are canceled.

Changes the settings in this window as explained below, and then applies the resulting settings to the storage system:

• All ports become prioritized ports.

• The threshold value for all ports becomes 0 (zero).

• The window will display a hyphen (-) instead of 0 (zero).



B-5

Close


• If the All Thresholds check box is checked, the check mark disappears.

Closes the Server Priority Manager main window.

Related topics

•

Analyzing traffic statistics: one-to-one connections on page 5-14

•

Setting priority for ports: one-to-one connections on page 5-13

•


•

Setting a threshold: one-to-one connections on page 5-17

WWN tab of the Server Priority Manager main window

Use this tab to set the limit on the performance of non-prioritized WWNs and set the threshold on the performance of prioritized WWNs.

B-6




Current Control

Status

The current system control.

• Port Control: The system is controlled by the upper limits and threshold specified on the Port tab.

• WWN Control: The system is controlled by the upper limits and threshold specified on the WWN tab.

• No Control: The system performance is not controlled by Server

Priority Manager.

Tip: If Port Control appears when the WWN tab is active, click Apply to switch control so that WWN Control is displayed.

Tip: To return the control status to No Control, specify Prio. for attributes of all host bus adapters and then click Apply.

Control List Allows you to narrow WWNs in the list:

• If All is selected, all WWNs appear in the list.

• If Prioritize is selected, only the prioritized WWNs appear in the list.

• If Non-Prioritize is selected, only the non-prioritized WWNs appear in the list.

Upper-left tree Ports and the host bus adapters connected to these ports in the storage system. Ports on the storage system are shown below the Storage

System folder. The ports are indicated by icons such as and

When you double-click on a port, the tree expands to display two items: Monitor and Non-Monitor. The host bus adapters that are connected to the specified port are displayed below Monitor or Non-

Monitor.

.

•

If you double-click Monitor, the host bus adapters ( ) whose traffic with the specified port is monitored are displayed below

Monitor.

• If you double-click Non-Monitor, the host bus adapters whose traffic with the specified port is not monitored are displayed below

Non-Monitor.

The WWN and SPM names of the host bus adapters are displayed on the right of the host bus adapter icon ( ) below Monitor. WWNs

(Worldwide Name) are 16-digit hexadecimal numbers used to uniquely identify host bus adapters. SPM names are nicknames assigned by the system administrator so that they can easily identify each host bus adapter.

Only the WWN is displayed on the right of the host bus adapter icon

( ) below Non-Monitor.

When many-to-many connections are established between host bus adapters (HBAs) and ports, make sure that all traffic between HBAs and ports is monitored. Therefore, make sure that all connected HBAs are displayed below Monitor. For details on how to move an HBA displayed below Non-Monitor to below Monitor, see


The list on the right of the tree changes depending on the item you select in the tree as follows.



B-7


• When you select a port or Monitor icon, the list shows the information of host bus adapters that are connected to the ports and monitored by Performance Monitor.

• When you select the Monitor icon or the Storage System folder, the list becomes blank.

Lower-left tree SPM groups and host bus adapters (WWNs) in each SPM group:

•

SPM groups ( ), which contain one or more WWNs, appear below the Storage System folder. For details on SPM groups, see

Working with SPM groups on page 5-34

.

• If you double-click an SPM group, host bus adapters in that group expand in the tree. The WWN and SPM name appear to the right of

Add WWN

Statistic type

WWN list the host bus adapter icon ( ).

If the WWN of a host bus adapter (HBA) appears in red in the tree, the host bus adapter is connected to two or more ports, but the traffic between the HBA and some of the ports is not monitored by

Performance Monitor. When many-to-many connections are established between HBAs and ports, make sure that all traffic between HBAs and ports is monitored. For details on the measures when a WWN is displayed in red, see


The list on the right of the tree changes depending on the item you selected in the tree as follows:

• When you select the Storage System folder, the WWN list shows the information of SPM groups.

•

When you select an SPM group icon ( ), the WWN list shows the information of host bus adapters ( group.

) contained in that SPM

Adds a host bus adapter to an SPM group. Before using this button, you must select a host bus adapter ( ) from the upper-left tree and also select an SPM group ( ) from the lower-left tree.

You can add a host bus adapter that appears below Monitor and is not yet registered on any other SPM group. If you select a host bus adapter below Non-Monitor or a host bus adapter already registered on an

SPM group, the Add NNW button is unavailable.

Allows you to change the type of performance statistics to be displayed in the WWN list.

• If IOPS (I/Os per second) is selected, the list displays I/O rates for ports. The I/O rate indicates the number of I/Os per second.

• If MB/s (megabytes per second) is selected, the list displays the transfer rates for ports. The transfer rate indicates the size of data transferred via a port in one second.

A list of WWNs and the I/O rate or the transfer rate for each host bus adapter corresponding to the selection in the upper-left tree or lowerleft tree. Use this list to specify the host bus adapter attributes and the upper limit of the host bus adapter traffic.

B-8



Item

WWN list

(continued)

Description

The measurement unit for the values in the list can be specified by the list at the upper left corner of the list. The displayed items will change depending on the selected tree and item. The host bus adapter traffic

(I/O rate and transfer rate) is monitored by Performance Monitor. To specify the monitoring period, use the Monitoring Term area of

Performance Monitor.

On the right side of the list appear total number of WWNs, the number of prioritized WWNs, and the number of non-prioritized WWNs.

The list contains the following columns (use the slide bar to view all of the columns):

• WWN: column indicates WWNs of host bus adapters. This column does not appear when you select the Storage System folder in the lower-left tree.

• SPM Name: SPM names of host bus adapters. Use Server Priority

Manager to assign an SPM name to each host bus adapter so that you can easily identify each host bus adapters in the Server Priority

Manager main window. This column does not appear when you select the Storage System folder in the lower-left tree.

• Group: The SPM group to which the host bus adapter belongs. This column appears when a port is selected in the upper-left tree and does not appear when an SPM group is selected in the lower-left tree.

• Per Port[IOPS]: The traffic (I/O rate or transfer rate) between the host bus adapter and the port selected in the upper-left tree.

This item is displayed only when you select an icon in the upperleft tree. The Per Port column contains the following:

Ave.: Average I/O rate or the average transfer rate for the specified period.

Max.: Maximum I/O rate or the maximum transfer rate for the specified period.

• WWN Total[IOPS]: The sum of the traffic (I/O rate or transfer rate) between the host bus adapter and all ports connected to the host bus adapter. This value means the total traffic of that host bus adapter. This item is displayed only when you select an icon in the upper-left tree. Whichever port you select in the tree, the WWN

Total column shows the sum of the traffic to all ports.

• The WWN Port column contains the following:

Ave.: Indicates the average I/O rate or the average transfer rate for the specified period. The Ave. column is also displayed when you select an icon in the lower-left tree. In this case, the Ave. column shows the average value same as that of WWN Total.

When you select the Storage System folder in the lower-left tree, the Ave. column shows the sum of the traffic of the host bus adapters registered on each SPM group.

Max.: Indicates the maximum I/O rate or the maximum transfer rate for the specified period. The Max. column is also displayed when you select an icon in the lower-left tree. In this case, the

Max. column shows the maximum value same as that of WWN

Total. When you select the Storage System folder in the lower-left tree, the Max. column shows the sum of the traffic of the host bus adapters registered on each SPM group.

• Attribute: The priority of each WWN. Prio. indicates a prioritized

WWN. Non-Prio. indicates a non-prioritized WWN. For details on



B-9

B-10


how to change the priority, see

Setting priority for WWNs: manyto-many connections on page 5-20

.

If one host bus adapter connects to multiple ports, the attribute setting of the host bus adapter is common to all of the ports.

Therefore, if you specify a host bus adapter as a prioritized WWN or a non-prioritized WWN for one port, the setting is applied to all of the other connected ports automatically.

• The Upper columns let you specify the upper limit on the I/O rate and the transfer rate for each host bus adapter. Either of the IOPS or MB/s column in the list is activated depending on the selection from the list above.

Use the IOPS column to specify the upper limit for I/O rates. Use the MB/s column to specify the upper limit for transfer rates. To specify an upper limit, double-click a cell to display the cursor in the cell.

If you specify a value in either the IOPS or MB/s column, the other column is unavailable. You can specify upper limit values for

I/O rates and transfer rates all together for different non-prioritized

WWNs.

Notes:

• If one host bus adapter connects to multiple ports, the setting of the upper limit value for a non-prioritized WWN is common to all of the ports. Therefore, if you specify an upper limit value of nonprioritized WWN for one port, the setting is applied to all of the other connected ports automatically.

• You cannot change the upper limit value of a host bus adapter that has registered on an SPM group. The upper limit value of such a host bus adapter is defined by the setting of the SPM group to which the host bus adapter is registered. For details on setting the

upper limit value of an SPM group, see Setting an upper-limit value to HBAs in an SPM group on page 5-37 .

•

The Upper columns will not appear if an SPM group ( ) or a host bus adapter ( )is selected in the lower-left tree.

All Thresholds If you select this check box and enter a threshold value in the text box, the threshold value will be applied to the entire storage system. To specify the threshold for the I/O rate, select IOPS from the list on the right of the text box. To specify the threshold for the transfer rate, select MB/s from the list. For example, if you specify 128 IOPS in All

Thresholds, the upper limits on non-prioritized WWNs are disabled when the sum of I/O rates for all prioritized WWNs is below 128 IOPS.

Even if you use the different type of rate (IOPS or MB/s) for the threshold as that used for the upper limit values of the non-prioritized

WWNs, the threshold control can work for all WWNs.

On the WWN tab, you cannot specify individual thresholds for each host bus adapter.

Delete ports if

CHA is removed

If checked, Server Priority Manager will delete, from SVP, the setting information of Server Priority Manager on ports in channel adapters that have been removed.

If checked, when a channel adapter is removed, the port and its settings are removed from the Server Priority Manager main window automatically, but remain in SVP. This may cause the old settings for



Apply

Reset

Initialize

Close


Server Priority Manager to be applied to a different channel adapter that is newly installed on the same location.

This check box is available only when the following Server Priority

Manager settings on ports in a removed channel adapter remain on the

SVP:

• The setting of prioritized ports or non-prioritized ports.

• The setting of prioritized WWNs or non-prioritized WWNs.

Applies the settings in this window to the storage system.

Restores the last applied settings in the window. When you click this button, all changes displayed in blue text in the window are canceled.

Changes the settings in this window, as explained below, and then applies the resulting settings to the storage system:

• All host bus adapters become prioritized WWNs.

• If the All Thresholds checkbox is checked, the check mark disappears.

Closes the Server Priority Manager main window.

Related topics

•

Implementing Server Priority Manager: many-to-many connections on page 5-19

Add WWN window

Use this window to set the WWN and SPM name.

WWN


When you click here, the host bus adapter (WWN) that is out of monitoring target displays. Select WWN from the drop down list.



B-11

SPM Name


Enter SPM name (maximum of 64 characters).

Change WWN and SPM Name window

Use this window to change WWN and SPM Name.

WWN

SPM Name


When you click here, the host bus adapter (WWN) connected to the port displays. Select WWN from the drop down list.

Enter the SPM name (maximum of 64 characters).

Add New SPM Group window

Use this window to add a new SPM group.

Item

SPM Group Name

Description

Enter SPM group name (maximum of 64 characters).

B-12



Change Upper Limit window

Use this window to change the upper limit.

Upper Limit


Enter the upper limit value.

If you want to set the upper limit value of the I/O rate, enter the upper limit value in the text box and select IOPS.

If you want to set the upper limit value of the transfer rate, enter the upper limmit value in the text box and select

MB/s.

Rename SPM Group window

Use this window to rename the SPM group

Item

SPM Group Name

Description

Enter SPM group name (maximum of 64 characters).



B-13

B-14



C

Virtual Partition Manager GUI reference

This chapter provides detailed information about the Virtual Partition Manager

GUI.

□

Cache Partition window

□

Individual CLPR window

□

Create CLPRs wizard

□

Migrate CLPR Resources wizard

□

Edit CLPR wizard

□

Change Settings window

□

CLPR Properties window

□

Delete CLPRs window

Virtual Partition Manager GUI reference


C-1

Cache Partition window

This is the top window that appears when Cache Partitions is selected in

Administration.

•

Summary on page C-2

•

Cache Partitions tab on page C-3

Summary

Item

Number of

CLPRs

Cache Size

Number of

Resources

Description

Displays the number of CLPRs in the storage system.

Displays the cache capacities in the storage system.

Displays the number of resources already assigned to CLPRs:

• Parity Group: Number of parity groups

• Virtual Volume: Number of virtual volumes

• Total: Number of resources already assigned to CLPRs

C-2



Cache Partitions tab


CLPR Name Displays the CLPR names. Click the CLPR name to open the window in which the CLPR is selected.

Displays CLPR IDs.

CLPR ID

1

Cache Size

Number of

Resources

Displays the cache capacities in the storage system:





Opens the Create CLPRs wizard.

Opens the Migrate CLPR Resources wizard.

Create CLPRs

Migrate CLPR

Resources

Edit CLPR Opens the Edit CLPR wizard.

Delete CLPRs

2 Opens the Delete CLPRs window.

Export

2

Opens the window for outputting the table information.

1

.

This item is not shown in the table by default. To display the item, click Column

Settings.

2

.

Click More Actions to display these items.

Related information

•


•


•


•


Individual CLPR window

This window appears when a CLPR is selected in Cache Partitions.

•

Summary on page C-4

•

Parity Groups tab on page C-4

•

Virtual Volumes tab on page C-5



C-3

Summary

Item

CLPR

Cache Size

Number of

Resources

Description

Displays the CLPR ID and CLPR name.

Displays the cache capacities in the storage system:





Parity Groups tab

Item

Parity Group ID

RAID Level

Capacity

Migrate CLPR

Resources

Export

Description

Displays the parity group IDs. Click the parity group ID to open the window in which the parity group is selected.

Displays the RAID level.

Displays the capacity.

Opens the Migrate CLPR Resources window.

Opens the window for outputting the table information.

C-4



Virtual Volumes tab


LDEV ID

LDEV Name

RAID Level

Virtual Storage

Machine*

Migrate CLPR

Resources

Displays the LDEV IDs. Click the LDEV ID to open the properties window of each LDEV.

Displays the LDEV name.

Displays the RAID level.

Capacity Displays the capacity.

Provisioning Type Displays the LDEV type.

Displays information about the virtual storage machine:

• Model type/Serial number*: Displays the model type and serial number of the virtual storage machine of the LDEV.

• LDEV ID*: Displays the virtual LDEV ID of the LDEV. A blank displays when no virtual LDEV ID is assigned.

• Device Name*: Displays the virtual device name of the LDEV.

The virtual device name is displayed as a combination of the number of virtual LUSE volumes and the virtual CVS attribute.

The values of the virtual LUSE volume number, virtual LUSE volume number, and virtual CVS attribute appear only for items that have been set. This column is blank when the virtual LUSE volume number and virtual CVS attribute are not set. If the virtual CVS attribute is set, CVS is attached as the suffix to the device name.

• SSID*: Displays the virtual SSID of the LDEV. A blank displays when no virtual SSID is specified.

Opens the Migrate CLPR Resources window.

Export Opens the window for outputting the table information.

*These items are not shown in the table by default. To display these items, click

Column Settings.


•




C-5

Create CLPRs wizard


•


Create CLPRs window

This window appears when you click Create CLPRs on the Cache Partition window.

Create CLPR settings

Use the left side of this window to create CLPRs.

Item

CLPR ID

CLPR Name

Cache Size

Description

Displays the smallest CLPR ID of available CLPR IDs. Displays a blank if no CLPR ID is available.

Enables you to enter the CLPR name. You can use up to 16 alphanumeric characters but cannot specify CLPR names that are already reserved. A blank is displayed if no CLPR ID is available. For

details see CLPR names on page 6-2 .

Enables you to select the cache capacity of CLPR. A blank is displayed if no CLPR ID is available.

You can select 4 GB or higher value for the cache capacity of the

CLPR, and the desired value can be selected in increments of 2 GB.

The maximum available capacity (subtract the total usage capacity

C-6



Add


of other CLPRs from the total capacity of the storage system) is displayed as the upper limit value.

You can add the CLPR set in the left side of the window to the

Selected CLPRs table.

Default CLPR table

Displays the information about CLPR 0.

Item

CLPR

Cache Size

Description


Displays the cache capacities in the storage system. The values change depending on the created CLPR.

Selected CLPRs table

Displays the information about the CLPRs to be created.

Item

CLPR

Cache Size

Description



Buttons

Item

Change Settings

Remove

Description

Opens the Change Settings window.

Enables you to delete the selected CLPRs from the Selected CLPRs table.

Confirm window for Create CLPRs

Use this window to confirm the CLPRs to be created and to assign a name to the create CLPR task.



C-7

Task Name field

Item

Task Name

Description

Enables you to enter a name (up to 32 alphanumeric characters) for the specified create CLPR task.



Item

CLPR

Cache Size

Description




Use this table to view the information of CLPR to be created.

Item

CLPR

Cache Size

Description


Displays the cache capacities.

C-8



Migrate CLPR Resources wizard


•


Migrate CLPR Resources window

This window appears when you click Migrate CLPR Resources on the Cache

Partition window.

CLPR and CU filters for parity group and virtual volume tables

CLPR

CU


Enables you to filter the Available Parity Groups table or the

Available Virtual Volumes table. Any is selected by default.

Enables you to filter the Available Virtual Volumes table. Any is selected by default.

Available Parity Groups table

Item

Parity Groups ID

CLPR

RAID Level

Description

Displays the parity group ID.


Displays the RAID Level.



C-9

Item

Capacity

Resource Group

Name (ID)

Description

Displays the total capacity of the parity group.

Displays the name and the ID of the resource group of the parity group. The ID is displayed in parentheses.

Available Virtual Volumes table


LDEV ID

LDEV Name

CLPR

RAID Level

Displays the LDEV IDs.

Displays the LDEV names.

Displays the CLPR IDs and CLPR names.

Displays the RAID levels.

Capacity Displays the capacities.

Provisioning Type Displays the LDEV types.

Resource Group

Name (ID)

Displays the name and the ID of the resource group of the

LDEV.The ID is displayed in parentheses.

Button

Item

Set

Description

Adds the resources assigned at the left area of the window to the

CLPR selected in the CLPRs table.

CLPRs table

Displays the information about the resources to assign to CLPRs.

Item

CLPR

Cache Size

Number of

Resources

Detail

Description


Displays the total cache capacities.

Displays the number of resources assigned to CLPRs. The value changes depending on the resources.



• Total: Number of resources assigned to CLPRs

Opens the CLPR Properties window for the selected CLPR.

Confirm window for Migrate CLPR Resources

Use this window to confirm the CLPR resources to be migrated and to assign a name to the migrate CLPR resources task.

C-10



CLPRs table

Displays the information about the CLPRs to be migrated.

Item

CLPR

Cache Size

Number of

Resources

Description


Displays the total cache capacities of the CLPRs.

Displays the number of resources assigned to CLPRs.



• Total: Number of resources assigned to the CLPR

Task Name field

Item

Task Name

Description

Enables you to enter a name (up to 32 alphanumeric characters) for the specified migrate CLPR task.

Button

Item

Detail

Description

Opens the CLPR Properties window.



C-11

Edit CLPR wizard


•


Edit CLPR window

This window appears when you click Edit CLPR on the Cache Partition window.

C-12

Edit CLPR settings

Item

CLPR ID

CLPR Name

Description

Displays the CLPR ID.

Displays the CLPR name set at the time of the CLPR creation, and enables you to edit the name. You can use up to 16 alphanumeric



Item

Cache Size

Description

characters but cannot specify CLPR names that are already

reserved. For details see CLPR names on page 6-2 .

Displays the cache capacity set at the time of the CLPR creation, and enables you to edit the cache capacity.

When you select the CLPR0, this item is inactive.

You can select 4 GB or higher value in the cache capacity of the

CLPR. The value can be selected in increments of 2 GB. The maximum available capacity (subtract the total usage capacity of other CLPRs from the total capacity of the storage system) is displayed as the upper limit value.

Confirm window for Edit CLPR

Use this window to confirm the CLPR to be edited and to assign a name to the edit CLPR task.



C-13



Item

CLPR

Cache Size

Description



Selected CLPR table

Displays information about CLPRs to be edited.

Item

CLPR

Cache Size

Description



Change Settings window

This window appears when you click Change Settings on the Create CLPRs window.

C-14

CLPR Name field

Item

CLPR Name

Description

Displays the CLPR name set at the time of the CLPR creation, and enables you to edit the name.

• Prefix: You can use up to 16 alphanumeric characters but cannot specify CLPR names that are already reserved. For

details see CLPR names on page 6-2

.




• Initial number: You can use numbers 0 to 9, and a blank is set by default. Up to 9 characters can be used.

The maximum number of characters for CLPR name is 16, including both Prefix and Initial number, not 25 (16+9).

Related topics

•


CLPR Properties window

This window appears when you click Detail on the Migrate CLPR Resources window.



C-15

CLPR Properties table

Item

CLPR

Cache Size

Number of

Resources

Description



Displays the number of resources already assigned to CLPRs.



• Total: Number of resources assigned to the CLPR

Parity Groups table

Item

Parity Group ID

Migrated

RAID Level

Capacity

Description

Displays the parity Group IDs.

Indicates whether there is a change by CLPR allocation:

• Yes: There is a change by CLPR allocation.

• No: There is not a change by CLPR allocation.


Displays the capacity.

Virtual Volume table


LDEV ID

LDEV Name

Migrated

Displays the LDEV IDs.

Displays the LDEV names.

Indicates whether there is a change by CLPR allocation:

• Yes: There is a change by CLPR allocation.

• No: There is not a change by CLPR allocation.

RAID Level

Capacity


Displays the capacities.

Provisioning Type Displays the LDEV types.


•


Delete CLPRs window

This window appears when you click Delete CLPR on the Cache Partition window.

C-16





Item

CLPR

Cache Size

Number of

Resources

Description



Displays the number of resources already assigned to the CLPR.



• Total: Number of resources assigned to CLPRs



C-17


Displays information about CLPRs to be deleted.

Item

CLPR

Cache Size

Description




•


C-18



Index

A

Auto LUN restrictions on manual migration across multiple

CLPRs

6-4

CUs add to monitoring

2-14

remove from monitoring

2-14

B

back-end performance and I/O usage rates

3-15

batch file preparing for use with Export Tool

4-8

running for Export Tool

4-9

using termination codes in Export Tool

4-11

Business Copy restrictions on quick restore operations across multiple CLPRs

6-4

D

data drive access rates

3-17

data drive and I/O usage rates

3-16

data transfer size and I/O usage rates

3-10

deleting a CLPR

6-11

C

cache capacity recommendations

6-5

hit rates and I/O usage rates

3-13

memory and I/O usage rates

3-7

partitioning

6-1

partitioning example

6-3

CLPRs creating

6-7

deleting

6-11

migrating resources

6-9

command file preparing for use with Export Tool

4-5

command reference

Export Tool

4-13

creating a CLPR

6-7

E

error handling

Export Tool

4-12

Export Tool commands

4-13

error handling

4-12

file formats

4-10

installing on UNIX systems

4-4

installing on Windows systems

4-4

log files

4-12

overview

4-2

processing time

4-10

requirements

4-2

text files

4-2

using

4-9

G

graphs

3-1

adding new graph panel

2-20

changing displayed objects

2-21

Index-1


changing displayed period

2-22

creating and viewing

2-19

deleting graph panel

2-23

objects and data that can be graphed

3-3

I

I/O usage rates back-end performance

3-15

cache hit rates

3-13

cache memory

3-7

data drive

3-16

data drive access

3-17

data transfer size

3-10

processor blades

3-7

ShadowImage

3-17

throughput

3-8

write pending

3-8

L

log files

Export Tool

4-12

M

migrating resources

6-9

Monitor Performance window

2-5

monitoring starting

2-7

stopping

2-18

N

non-prioritized WWN

5-20

P

partitioning cache

6-1

Performance Monitor

2-2

performance troubleshooting

7-1

prioritized WWN

5-20

processor blades and I/O usage rates

3-7

R

replace firmware

2-4

Index-2

Hitachi Virtual Storage Platform G200, G400, G600, G800 Performance Guide restrictions

Auto LUN manual migration across multiple

CLPRs

6-4

Business Copy quick restore operations across multiple CLPRs

6-4

ShadowImage quick restore operations across multiple CLPRs

6-4

Volume Migration manual migration across multiple CLPRs

6-4

S

ShadowImage

I/O usage rates

3-17

restrictions on quick restore operations across multiple CLPRs

6-4

SPM group

5-34

starting monitoring

2-7

statistics setting storing period

2-6

stopping monitoring

2-18

Support Center

7-7

T

throughput and I/O usage rates

3-8

troubleshooting

Cache Partition

7-7

performance

7-1

Virtual Partition Manager

7-7

V

Volume Migration restrictions on manual migration across multiple

CLPRs

6-4

W

write pending and I/O usage rates

3-8

WWNs adding to monitoring

2-8, 2-9, 2-10

connecting to ports

2-12

editing nickname

2-11

removing from monitoring

2-8, 2-9, 2-13

viewing

2-9


Hitachi Data Systems

Corporate Headquarters

2845 Lafayette Street

Santa Clara, California 95050-2639

U.S.A.

www.hds.com

Regional Contact Information

Americas

+1 408 970 1000 [email protected]

Europe, Middle East, and Africa

+44 (0)1753 618000 [email protected]

Asia Pacific

+852 3189 7900 [email protected]

MK-94HM8012-01