HPE XP7 User Manual

XP7 Performance for Open and Mainframe Systems User Guide

Abstract

This document describes and provides instructions for using Performance Monitor, Performance Control, and Cache Residency
Manager.

This document is intended for system administrators and Hewlett Packard Enterprise representatives and authorized service
providers who install, configure, and operate the XP7 Storage system.

Part Number: 858754-003
Published: May 2016
Edition: 9

© Copyright 2014, 2016 Hewlett Packard Enterprise Development LP

The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services

are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting

an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR

12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed

to the U.S. Government under vendor's standard commercial license.

Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not

responsible for information outside the Hewlett Packard Enterprise website.

Acknowledgments

Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the United States and other countries.

Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

Java® and Oracle® are registered trademarks of Oracle and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

Revision History

May 2014Revision 1

Applies to microcode version 80-01-22-00/02 or later.

September 2014Revision 2

Applies to microcode version 80-01-42-00/00 or later.

October 2014Revision 3

Applies to microcode version 80-02-01-00/01 or later.

April 2015Revision 4

Applies to microcode version 80-02-22-00/00 or later.

June 2015Revision 5

Applies to microcode version 80-02-41-00/00 or later.

September 2015Revision 6

Applies to microcode version 80-03-01-00/00 or later.

December 2015Revision 7

Applies to microcode version 80-03-01-00/00 or later.

April 2016Revision 8

Applies to microcode version 80-04-02-00/00 or later.

May 2016Revision 9

Applies to microcode version 80-04-02-00/00 or later.

Contents

1 Performance management..................................................................................8

Overview of performance management................................................................................................8

System requirements............................................................................................................................8

2 Performance Monitor operations.........................................................................9

Overview of Performance Monitor........................................................................................................9

Data collected by Performance Monitor..........................................................................................9

Short-range monitoring....................................................................................................................9

Long-range monitoring..................................................................................................................10

Performance Monitor data graphs.................................................................................................11

Export Tool for Performance Monitor.............................................................................................11

Cautions and restrictions for Performance Monitor............................................................................11

Cautions and restrictions for monitoring........................................................................................11

Cautions and restrictions for usage statistics................................................................................12

Performance monitoring workflow......................................................................................................13

Setting the storing period for the monitoring data...............................................................................14

Starting monitoring..............................................................................................................................14

Monitoring WWNs...............................................................................................................................15

Adding new WWNs to monitor.......................................................................................................16

Viewing the WWNs that are being monitored................................................................................16

Removing WWNs to monitor.........................................................................................................17

Adding WWNs to ports..................................................................................................................17

Editing the WWN nickname...........................................................................................................18

Connecting WWNs to ports...........................................................................................................19

Deleting unused WWNs from monitoring targets..........................................................................19

Monitoring CUs...................................................................................................................................20

Displaying CUs to monitor.............................................................................................................20

Adding and removing CUs to monitor...........................................................................................20

Selecting CUs to monitor...............................................................................................................22

Confirming the status of CUs to monitor.......................................................................................22

Changing the sampling interval..........................................................................................................23

Stopping monitoring............................................................................................................................24

Using the Performance Monitor data graphs......................................................................................24

About the data graphs...................................................................................................................25

Displaying the monitor data on graphs..........................................................................................25

Adding a new graph.......................................................................................................................26

Changing the data displayed on a graph.......................................................................................27

Changing the time period displayed on the graph panel...............................................................27

Deleting a graph from the graph panel..........................................................................................28

3 Performance Monitor data.................................................................................29

Monitoring data...................................................................................................................................29

Usage rates of MPs............................................................................................................................33

Usage rate of DRRs............................................................................................................................33

Usage rate of cache memory..............................................................................................................33

Write pending rates.............................................................................................................................34

Usage rates of access paths..............................................................................................................34

Storage system throughput.................................................................................................................35

Data transfer rate................................................................................................................................37

Response times..................................................................................................................................39

CMR delay time..................................................................................................................................40

Disconnected time..............................................................................................................................40

Connected time...................................................................................................................................41

Contents 3

HTP port open exchanges..................................................................................................................41

Cache hit rates....................................................................................................................................42

Back-end performance.......................................................................................................................43

Drive usage rates................................................................................................................................44

Data drive access rates......................................................................................................................44

Business Copy usage statistics..........................................................................................................45

Remote I/O (RIO)................................................................................................................................45

Pair Synchronized...............................................................................................................................46

Differential Track.................................................................................................................................46

Number of Journals............................................................................................................................47

Data Usage Rate................................................................................................................................47

Metadata Usage Rate.........................................................................................................................48

Detailed information of resources on top 20 usage rates...................................................................48

4 Exporting Performance Monitor data.................................................................49

About Export Tool...............................................................................................................................49

Preparing to use Export Tool..............................................................................................................49

Export Tool limitation.....................................................................................................................49

Requirements for Export Tool........................................................................................................50

Installing Export Tool.....................................................................................................................50

On Windows.............................................................................................................................51

On UNIX...................................................................................................................................51

Using Export Tool................................................................................................................................51

Preparing a command file..............................................................................................................51

Preparing a batch file.....................................................................................................................55

Running Export Tool......................................................................................................................56

Running a batch file.................................................................................................................56

File formats...............................................................................................................................58

Processing time........................................................................................................................58

Termination code......................................................................................................................58

Log files....................................................................................................................................59

Error handling...........................................................................................................................59

Export Tool command reference.........................................................................................................60

Export Tool command syntax........................................................................................................60

Subcommand list...........................................................................................................................61

svpip..............................................................................................................................................62

retry...............................................................................................................................................62

login...............................................................................................................................................63

show..............................................................................................................................................64

group.............................................................................................................................................65

shortrange.....................................................................................................................................74

longrange.......................................................................................................................................76

outpath...........................................................................................................................................78

option.............................................................................................................................................79

apply..............................................................................................................................................80

set..................................................................................................................................................80

help................................................................................................................................................81

Java...............................................................................................................................................82

Exported files......................................................................................................................................84

Monitoring data exported by Export Tool.......................................................................................84

Resource usage and write-pending rate statistics.........................................................................85

Parity group and external volume group statistics.........................................................................87

Statistics for volumes in parity/external volume groups................................................................88

Volumes in parity groups or external volume groups (at volumes controlled by a particular

CU)................................................................................................................................................89

4 Contents

Port statistics.................................................................................................................................91

Host bus adapters connected to ports statistics............................................................................92

Volumes (LU) statistics..................................................................................................................92

All host bus adapters connected to ports......................................................................................93

MP blades......................................................................................................................................93

Remote copy operations by Cnt Ac-S/Cnt Ac-S MF and monitoring data by HA (whole

volumes)........................................................................................................................................94

Remote copy operations by Cnt Ac-S and monitoring data by HA (for each volume (LU))..........94

Remote copy by Cnt Ac-S/Cnt Ac-S MF and monitoring data by HA (volumes controlled by a

particular CU)................................................................................................................................95

Remote copy by Cnt Ac-J and Cnt Ac-J MF (whole volumes)......................................................96

Remote copy by Cnt Ac-J and Cnt Ac-J MF (at journals)..............................................................97

Remote copy by Cnt Ac-J (for each volume (LU)).........................................................................97

Remote copy by Cnt Ac-J and Cnt Ac-J MF (at volumes controlled by a particular CU)..............98

Causes of Invalid Monitoring Data......................................................................................................99

Troubleshooting Export Tool.............................................................................................................100

Messages issued by Export Tool.................................................................................................101

5 Performance Control operations.....................................................................105

Overview of Performance Control.....................................................................................................105

Performance of high-priority hosts..............................................................................................105

Upper-limit control.......................................................................................................................105

Threshold control.........................................................................................................................106

About I/O rates and transfer rates (traffic)...................................................................................106

Use cases for Performance Control..................................................................................................107

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

Use case for many-to-many connections....................................................................................109

Cautions and restrictions for Performance Control...........................................................................113

Implementing Performance Control: one-to-one connections..........................................................114

Performance Control workflow: one-to-one connections.............................................................114

Setting priority for ports: one-to-one connections........................................................................115

Analyzing traffic statistics: one-to-one connections.....................................................................116

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

Setting a threshold: one-to-one connections...............................................................................118

Implementing Performance Control: many-to-many connections.....................................................119

Performance Control workflow: many-to-many connections.......................................................119

Setting priority for WWNs: many-to-many connections...............................................................120

Monitoring all port-HBA traffic: many-to-many connections........................................................122

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

connections............................................................................................................................124

Analyzing traffic statistics: many-to-many connections...............................................................125

Setting upper-limit values for non-prioritized WWNs: many-to-many connections.....................126

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

Managing host bus adapters............................................................................................................129

Changing the PFC name of a host bus adapter..........................................................................129

Replacing a host bus adapter......................................................................................................130

Working with PFC groups.................................................................................................................132

Creating a PFC group..................................................................................................................132

Deleting an HBA from a PFC group............................................................................................133

Changing the priority of a PFC group..........................................................................................134

Setting an upper-limit value to HBAs in a PFC group.................................................................135

Renaming a PFC group...............................................................................................................136

Deleting a PFC group..................................................................................................................137

6 Cache Residency operations..........................................................................138

Overview of Cache Residency..........................................................................................................138

Contents 5

Priority mode (read data in cache)..............................................................................................138

Bind mode (read and write data in cache)...................................................................................138

Prestaging data in cache.............................................................................................................139

Cache Residency system specifications..........................................................................................140

Estimating cache size for Cache Residency....................................................................................140

Cache Residency cache areas....................................................................................................141

Cache size requirements.............................................................................................................141

Calculating cache size for open systems....................................................................................141

Calculating cache size for mainframe systems...........................................................................143

Cautions and restrictions for Cache Residency................................................................................144

Cautions and restrictions for cache residency.............................................................................144

Interoperability restrictions for cache residency.....................................................................145

Cautions and restrictions for prestaging......................................................................................145

Managing cache-resident data.........................................................................................................146

Placing specific data into cache..................................................................................................146

Placing LDEVs into cache...........................................................................................................149

Releasing specific data from cache.............................................................................................150

Releasing LDEVs from cache.....................................................................................................151

Changing modes for data already in cache.................................................................................153

Viewing Cache Residency information........................................................................................153

7 Troubleshooting...............................................................................................154

General troubleshooting resources...................................................................................................154

Troubleshooting Performance Monitor.............................................................................................154

Troubleshooting Performance Control..............................................................................................154

Troubleshooting Cache Residency...................................................................................................154

Calling HPE technical support..........................................................................................................155

8 Support and other resources...........................................................................156

Accessing Hewlett Packard Enterprise Support...............................................................................156

Accessing updates............................................................................................................................156

Related information...........................................................................................................................156

Websites...........................................................................................................................................157

Remote support................................................................................................................................157

Documentation feedback..................................................................................................................157

A Performance Monitor GUI reference...............................................................159

Performance Monitor main window..................................................................................................159

Edit Monitoring Switch wizard...........................................................................................................161

Edit Monitoring Switch window....................................................................................................161

Edit Monitoring Switch confirmation window...............................................................................162

Monitor Performance window...........................................................................................................163

Edit CU Monitor Mode wizard...........................................................................................................176

Edit CU Monitor Mode window....................................................................................................176

Edit CU Monitor Mode confirmation window...............................................................................179

View CU Matrix window....................................................................................................................180

Select by Parity Groups window.......................................................................................................181

Parity Group Properties window.......................................................................................................182

Edit WWN wizard..............................................................................................................................183

Edit WWN window.......................................................................................................................183

Edit WWN confirmation window..................................................................................................184

Edit WWN Monitor Mode wizard.......................................................................................................184

Edit WWN Monitor Mode window................................................................................................185

Edit WWN Monitor Mode confirmation window...........................................................................187

Delete Unused WWNs window.........................................................................................................188

Add New Monitored WWNs wizard...................................................................................................189

6 Contents

Add New Monitored WWNs window............................................................................................189

Add New Monitored WWNs confirmation window.......................................................................191

Add to Ports wizard...........................................................................................................................192

Add to Ports window....................................................................................................................192

Add to Ports confirmation window...............................................................................................194

Monitor window.................................................................................................................................195

MP Properties window......................................................................................................................197

Edit Time Range window..................................................................................................................199

Edit Performance Objects window....................................................................................................200

Add Graph window...........................................................................................................................212

Wizard buttons..................................................................................................................................225

Navigation buttons............................................................................................................................226

B Performance Control GUI reference...............................................................227

Performance Control window............................................................................................................227

Port tab of the Performance Control main window...........................................................................228

WWN tab of the Performance Control main window........................................................................230

C Cache Residency GUI reference....................................................................236

Cache Residency window.................................................................................................................236

Multi Set dialog box..........................................................................................................................240

Multi Release dialog box...................................................................................................................241

D Warranty and regulatory information...............................................................243

Warranty information.........................................................................................................................243

Regulatory information......................................................................................................................243

Belarus Kazakhstan Russia marking...........................................................................................243

Turkey RoHS material content declaration..................................................................................244

Ukraine RoHS material content declaration................................................................................244

Glossary.............................................................................................................245

Index...................................................................................................................250

Contents 7

1 Performance management

This chapter provides an overview on performance management of the XP7 Storage system,
and describes the system requirements.

Overview of performance management

The XP7 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 performance.

• Performance Monitor: Enables you to collect and analyze detailed performance and usage
statistics for the XP7 Storage 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 a spreadsheet and other applications.

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

• Cache Residency: Enables you to improve host access to frequently accessed data by
retaining the data in the storage system's cache memory to make it available at front-end
access speeds.

You can perform performance management operations using Remote Web Console and RAID
Manager for the XP7 Storage system. For details about the Remote Web Console, see the XP7

Remote Web Console User Guide. For details about RAID Manager, see the XP7 RAID Manager
User Guide.

System requirements

• Performance management products. The performance management software products
for the XP7 Storage system are required for performance management operations.

◦ Performance Monitor

◦ Performance Control

◦ Cache Residency

• License keys. The license keys for the performance management software products must
be installed. For details about installing license keys, see the XP7 Remote Web Console
User Guide.

• Java. Java is required for Performance Control and Cache Residency. For details about
installing Java and configuring Remote Web Console, see the XP7 Remote Web Console
User Guide.

• Remote Web Console secondary window. The Remote Web Console secondary window
must be enabled before you use Performance Control or Cache Residency. Java and some
settings of Remote Web Console are required for the Remote Web Console secondary
window. For details, see the chapter on how to use the Remote Web Console secondary
window in the XP7 Remote Web Console User Guide.

• Cache memory for Cache Residency. Use of Cache Residency might require additional
cache memory in the XP7 Storage system. For details, see “Estimating cache size for Cache

Residency” (page 140).

8 Performance management

2 Performance Monitor operations

This chapter describes performance monitoring and provides instructions for conducting
performance monitoring operations using Performance Monitor.

Overview of Performance Monitor

Performance Monitor enables you to monitor your XP7 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. You can perform both short-range monitoring and long-range monitoring. For
long-range monitoring, data is collected constantly. For short-range monitoring, the 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 system.

• “Data collected by Performance Monitor” (page 9)

• “Short-range monitoring” (page 9)

• “Long-range monitoring” (page 10)

• “Performance Monitor data graphs” (page 11)

• “Export Tool for Performance Monitor” (page 11)

Data collected by Performance Monitor

Performance Monitor allows you to collect the performance and usage statistics for the XP7
Storage system. All statistics are available for short-range monitoring. Most of the storage system
usage statistics are available for long-range monitoring. For details about the performance and
usage statistics, see “Monitoring data” (page 29).

Short-range monitoring

When you perform short-range monitoring of 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). Short-range monitoring occurs in
parallel with and does not affect long-range monitoring activities. All performance and usage
statistics are available for short-range monitoring.

Overview of Performance Monitor 9

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

• Up to 64 CUs. If there are 64 or fewer CUs to be monitored, you can set the sampling interval
from 1 minute 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.

◦ Performance Monitor collects statistics for up to 15 days when data is collected at

15-minute intervals.

• More than 64 CUs. If there are more than 64 CUs to be monitored, you can set the sampling
interval to 5, 10, or 15 minutes.

◦ Performance Monitor collects statistics for one day when data is collected at 5-minute

intervals.

◦ Performance Monitor collects statistics for up to three days when data is collected at

15-minute intervals.

For short-range monitoring the SVP can store a maximum of 1,440 data collection events if there
are 64 or fewer CUs to be monitored. Based on this number and the sampling interval, you can
calculate the maximum storing period for the statistics as the sampling interval multiplied by
1,440. 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 one minute for the sampling interval as in the example above,
Performance Monitor displays the statistics for a maximum of one 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.

If there are more than 64 CUs to be monitored, SVP can store a maximum of 288 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 288. For example, if you set the
sampling interval to 5 minutes, the maximum storing period for the statistics is 1 day (24 hours):

5 minutes x 288 = 1440 minutes = 24 hours = 1 day
This maximum storing period is the maximum range of display in the Monitor Performance

windows. When you specify one minute for the sampling interval, as in the previous example,
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 three days in the lists and graphs.

Long-range monitoring

When you perform long-range monitoring of the storage system, you control when the statistics
are collected in real time or during a specified period of time. The long-range monitoring statistics
are collected at fixed 15-minute intervals (0, 15, 30, and 45 minutes of every hour) and stored
for up to 6 months (186 days). Long-range monitoring occurs in parallel with and does not affect
short-range monitoring activities.

10 Performance Monitor operations

You can collect the following statistics in long-range monitoring:

• Usage rates of MPs

• Usage rates of DRRs

• Write-pending statistics

• Access path usage statistics

• Data drive usage statistics

• Data drive access rates

Performance Monitor data graphs

You can view both the short-range and long-range statistics on data graphs. All statistics can be
viewed in short range (for the storing period corresponding to the sampling interval setting).
Usage statistics about storage system resources, which are monitored in both ranges, can be
viewed in both short range and long range. 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.
A few storage system usage statistics are not available for long-range monitoring.

For details about the Performance Monitor data graphs, see “About the data graphs” (page 25).

Export Tool for Performance Monitor

The Export Tool software that comes with Performance Monitor allows you to export the monitoring
data in a .csv file for analysis, for example, using spreadsheet software 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 “Exporting Performance Monitor data” (page 49).

Cautions and restrictions for Performance Monitor

• “Cautions and restrictions for monitoring” (page 11)

• “Cautions and restrictions for usage statistics” (page 12)

Cautions and restrictions for monitoring

• Performance monitoring switch

When the performance monitoring switch is set to disabled, short-range 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. Next, obtain the monitoring data. For details about the monitoring
switch, see “Starting monitoring” (page 14).

• 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” (page 16),

“Adding WWNs to ports” (page 17), and “Connecting WWNs to ports” (page 19).

Cautions and restrictions for Performance Monitor 11

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

◦ Formatting or quick-formatting logical devices

◦ Adding, replacing, or removing MP blades

• Storage system power-off

If the storage system is powered off during monitoring, monitoring stops until the storage
system is powered on again. Monitoring resumes when the storage system is powered on
again. 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.

• Microprogram replacement

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

Cautions and restrictions for usage statistics

• Retention of short-range and long-range usage statistics

Usage statistics for the last six months (186 days) are displayed in long-range monitoring,
and usage statistics for up to the last 15 days are displayed in short-range monitoring. Usage
statistics outside of these ranges are deleted from the SVP. In short range monitoring, results
are retained for the last 1 to 15 days depending on the specified sampling interval. If the
retention period has passed since a monitoring result was obtained, the previous result has
been deleted from the SVP and cannot be displayed.

• Statistics for periods of high I/O workload

For short-range monitoring, 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” (page 14).

• Volumes and CU ranges

The volumes to be monitored by Performance Monitor are specified by control unit (CU). If
the range of used CUs does not match the range of CUs monitored by Performance Monitor,
usage statistics might not be collected for some volumes.

• Reverse resync operations

When you run the RAID Manager horctakeover command, the pairresync-swaps command
for a Cnt Ac-J pair, or the BCM YKRESYNC REVERSE command for a Cnt Ac-J MF pair,

12 Performance Monitor operations

the primary and secondary volumes are swapped. You can collect the before-swapped
information immediately after you run any of the commands. Invalid monitoring data will be
generated for a short time but will be corrected automatically when the monitoring data gets
updated. The invalid data will temporarily be generated when the volume used for a secondary
volume is used as a primary volume after a Cnt Ac-J pair or Cnt Ac-J MF pair is deleted.

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

Monitoring data cannot be displayed within the first two sampling intervals after the monitoring
starts or the sampling interval is changed because no monitoring data has accumulated.
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, a 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 Remote Web Console PC:

◦ Adding, replacing, or removing cache memory.

◦ Adding, replacing, or removing data drives.

◦ Changing the storage system configuration.

◦ Replacing the microprogram.

• Pool-VOLs

Pool-VOLs of Fast Snap, Thin Provisioning, and Thin Provisioning MF are not monitored.

• Margin of error

The short-range and long-range monitoring data might have a margin of error.

Performance monitoring workflow

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

2. Set the storing period (short-range or long-range) for the monitoring statistics. For instructions,
see “Setting the storing period for the monitoring data” (page 14).

3. Start performance monitoring. For instructions, see “Starting monitoring” (page 14).

4. Add the WWNs that you want to monitor. For instructions, see “Monitoring WWNs” (page 15).

5. Add the CUs that you want to monitor. For instructions, see “Monitoring CUs” (page 20).

6. Adjust the sampling interval as needed to increase or decrease the maximum storing period

of short-range statistics. For instructions, see “Changing the sampling interval” (page 23).

7. View the monitoring data on graphs. For details, see “Using the Performance Monitor data

graphs” (page 24).

8. Export the monitoring data as needed for analysis and for retention of long-term data. For
details, see “Exporting Performance Monitor data” (page 49).

9. When you want to stop collecting monitor data, stop monitoring by disabling the monitoring
switch. For details, see “Stopping monitoring” (page 24).

Performance monitoring workflow 13

Setting the storing period for the monitoring data

Before you start the monitoring function, you must set the storing period, short-range or long-range,
for the monitoring data. Short-range data can be collected for up to 15 days, and long-range data
can be collected for up to six months (186 days).

Prerequisites

• Required role: Storage Administrator (Performance Management)

Procedure

1. Open the Performance Monitor window.
In Command View Advanced Edition:

1. On the Resources tab, expand the Storage Systems tree.

2. Right-click the target storage system.

3. Select Performance Monitor.

In Remote Web Console:

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

Performance Monitor window.

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

3. On the Monitor Performance window select Long-Range or Short-Range in the Data
Range as the periods (ranges) for collecting and storing statistics.

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

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

5. Click Apply to apply the settings to the storage system.

Related topics

• “Performance Monitor main window” (page 159)

• “Monitor Performance window” (page 163)

Starting monitoring

After you have set the storing period for the monitoring data (short-range or long-range), you can
start the monitoring function.

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 Export Tool and then restart monitoring.

14 Performance Monitor operations

Prerequisites

• Required role: Storage Administrator (Performance Management)

Procedure

1. Open the Performance Monitor window.
In Command View Advanced Edition:

1. On the Resources tab, expand the Storage Systems tree.

2. Right-click the target storage system, and then select Performance Monitor.
In Remote Web Console:

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

Performance Monitor window.

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

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

5. Click Finish.

6. In the Confirm window enter your task name in Task Name, and click Apply to start
monitoring.

In CVAE you can check the progress of the task on the Tasks & Alerts tab. Click the task
name to view details of the task.

In RWC the Tasks window opens if Go to tasks window for status is checked.

NOTE: Monitoring data cannot be displayed within the first two sampling intervals after the
monitoring starts or the sampling interval is changed 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” (page 161)

Monitoring WWNs

This section provides instructions for monitoring WWNs using Performance Monitor:

• “Adding new WWNs to monitor” (page 16)

• “Viewing the WWNs that are being monitored” (page 16)

• “Removing WWNs to monitor” (page 17)

• “Adding WWNs to ports” (page 17)

• “Editing the WWN nickname” (page 18)

• “Connecting WWNs to ports” (page 19)

• “Deleting unused WWNs from monitoring targets” (page 19)

Monitoring WWNs 15

Adding new WWNs to monitor

Prerequisites

• Required role: Storage Administrator (Performance Management)

Procedure

1. Open the Performance Monitor window.
In Command View Advanced Edition:

1. On the Resources tab, expand the Storage Systems tree.

2. Right-click the target storage system, and then select Performance Monitor.
In Remote Web Console:

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

Performance Monitor window.

2. Select the Monitored WWNs tab, and click Edit WWN Monitor Mode to open the Edit
WWN Monitor Mode window.

3. In the Edit WWN Monitor Mode window select the WWNs in the Unmonitored WWNs list,
and click Add.

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

5. In the Confirm window click Apply to apply the settings to the storage system.
In CVAE you can check the progress of the task on the Tasks & Alerts tab. Click the task

name to view details of the task.
In RWC the Tasks window opens if Go to tasks window for status is checked.

Related topics

• “Edit WWN Monitor Mode wizard” (page 184)

Viewing the WWNs that are being monitored

Prerequisites

• Required role: Storage Administrator (Performance Management)

Procedure

1. Open the Performance Monitor window.
In Command View Advanced Edition:

1. On the Resources tab, expand the Storage Systems tree.

2. Right-click the target storage system, and then select Performance Monitor.
In Remote Web Console:

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

Performance Monitor window.

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

16 Performance Monitor operations

Related topics

• “Performance Monitor main window” (page 159)

Removing WWNs to monitor

Prerequisites

• Required role: Storage Administrator (Performance Management)

Procedure

1. Open the Performance Monitor window.
In Command View Advanced Edition:

1. On the Resources tab, expand the Storage Systems tree.

2. Right-click the target storage system, and then select Performance Monitor.
In Remote Web Console:

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

Performance Monitor window.

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.

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

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

In CVAE you can check the progress of the task on the Tasks & Alerts tab. Click the task
name to view details of the task.

In RWC the Tasks window opens if Go to tasks window for status is checked.

Related topics

• “Edit WWN Monitor Mode wizard” (page 184)

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

• Required role: Storage Administrator (Performance Management)

Procedure

1. Open the Performance Monitor window.
In Command View Advanced Edition:

1. On the Resources tab, expand the Storage Systems tree.

2. Right-click the target storage system, and then select Performance Monitor.
In Remote Web Console:

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

Performance Monitor window.

2. In the Performance Monitor window click the Monitored WWNs tab.

Monitoring WWNs 17

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

4. Specify the information for each WWN, as listed in the following table.

DescriptionItem

Enter the 16-digit hexadecimal number.HBA WWN (required)

WWN Name (optional)

Port (in Available Ports)

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

6. If you need to remove a WWN from the Selected WWNs list, select the WWN and click
Remove.

7. When you are done adding WWNs, click Finish.

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

Related topics

• “Add New Monitored WWNs wizard” (page 189)

Editing the WWN nickname

Prerequisites

• Required role: Storage Administrator (Performance Management)

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

In the Available Ports list select the port connected to the WWN. Ports
connected to mainframe hosts are not displayed, because they are not
supported for Performance Monitor.

Procedure

1. Open the Performance Monitor window.
In Command View Advanced Edition:

1. On the Resources tab, expand the Storage Systems tree.

2. Right-click the target storage system, and then select Performance Monitor.
In Remote Web Console:

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

Performance Monitor window.

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

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. On the Monitored WWNs tab click Edit WWN to open the Edit WWN window.

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

• WWN Name

The nickname distinguishes the host bus adapter from other adapters. The WWN Name
must be less than 64 digits and must consist of alphanumeric characters and at least
one symbol.

18 Performance Monitor operations

6. When you are done editing WWNs, click Finish.

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

Related topics

• “Edit WWN wizard” (page 183)

Connecting WWNs to ports

Prerequisites

• Required role: Storage Administrator (Performance Management)

Procedure

1. Open the Performance Monitor window.
In Command View Advanced Edition:

1. On the Resources tab, expand the Storage Systems tree.

2. Right-click the target storage system, and then select Performance Monitor.
In Remote Web Console:

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

Performance Monitor window.

2. In the Performance Monitor window click the Monitored WWNs tab.

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

4. On the Monitored WWNs tab click Add to Ports to open the Add to Ports window.

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.
Mainframe ports are not displayed because they are not supported for Performance Monitor.

6. If you need to delete a WWN from the Selected WWNs list, select the WWN, and then click
Remove.

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

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

Related topics

• “Add to Ports wizard” (page 192)

Deleting unused WWNs from monitoring targets

Prerequisites

• Required role: Storage Administrator (Performance Management)

Procedure

To delete WWNs that are being monitored:

Monitoring WWNs 19

1. Open the Performance Monitor window.
In Command View Advanced Edition:

1. On the Resources tab, expand the Storage Systems tree.

2. Right-click the target storage system, and then select Performance Monitor.
In Remote Web Console:

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

Performance Monitor window.

2. Click the Monitored WWNs tab.

3. On the Monitored WWNs tab, click More Actions > Delete Unused WWNs to open the
Delete Unused WWNs window.

4. Enter your task name in Task Name, and click Apply.
In CVAE you can check the progress of the task on the Tasks & Alerts tab. Click the task

name to view details of the task.
In RWC the Tasks window opens if Go to tasks window for status is checked.

Related topics

• “Delete Unused WWNs window” (page 188)

Monitoring CUs

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

• “Displaying CUs to monitor” (page 20)

• “Adding and removing CUs to monitor” (page 20)

• “Selecting CUs to monitor” (page 22)

• “Confirming the status of CUs to monitor” (page 22)

Displaying CUs to monitor

Prerequisites

• Required role: Storage Administrator (Performance Management)

Procedure

1. Open the Performance Monitor window.
In Command View Advanced Edition:

1. On the Resources tab, expand the Storage Systems tree.

2. Right-click the target storage system, and then select Performance Monitor.
In Remote Web Console:

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

Performance Monitor window.

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

Related topics

• “Performance Monitor main window” (page 159)

Adding and removing CUs to monitor

Use the Performance Monitor window to add and remove CUs to monitor.

20 Performance Monitor operations

NOTE: When you remove a CU from monitoring, the monitoring data for the CU will be deleted.
Therefore, export the desired monitoring data before performing this operation. For details, see

“Exporting Performance Monitor data” (page 49).

Prerequisites

• Required role: Storage Administrator (Performance Management)

Procedure

1. Open the Performance Monitor window.
In Command View Advanced Edition:

1. On the Resources tab, expand the Storage Systems tree.

2. Right-click the target storage system, and then select Performance Monitor.
In Remote Web Console:

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

Performance Monitor window.

2. Open the Monitored CUs tab.

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

4. 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
CUsfield and click Remove.

5. Click Finish.

6. In the Confirm window enter your task name in Task Name, and click Apply.
In CVAE you can check the progress of the task on the Tasks & Alerts tab. Click the task

name to view details of the task.
In RWC the Tasks window opens if Go to tasks window for status is checked.

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.

Monitoring CUs 21

Related topics

• “Edit CU Monitor Mode wizard” (page 176)

Selecting CUs to monitor

Prerequisites

• Required role: Storage Administrator (Performance Management)

Procedure

1. Open the Performance Monitor window.
In Command View Advanced Edition:

1. On the Resources tab, expand the Storage Systems tree.

2. Right-click the target storage system, and then select Performance Monitor.
In Remote Web Console:

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

Performance Monitor window.

2. Open the Monitored CUs tab.

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.
The Select by Parity Groups window opens. The available parity group IDs and number

of CUs are displayed.

5. 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” (page 20).

Related topics

• “Select by Parity Groups window” (page 181)

• “Parity Group Properties window” (page 182)

• “Adding and removing CUs to monitor” (page 20)

Confirming the status of CUs to monitor

Prerequisites

• Required role: Storage Administrator (Performance Management)

Procedure

To view the monitoring status of CUs:

22 Performance Monitor operations

1. Open the Performance Monitor window.
In Command View Advanced Edition:

1. On the Resources tab, expand the Storage Systems tree.

2. Right-click the target storage system, and then select Performance Monitor.
In Remote Web Console:

1. Select Analytics in Explorer, and click Performance Monitor in the tree.

2. On the Monitored CUs tab, click View CU Matrix.
The following CUs are displayed in the Monitored CUs window.

• Monitored CUs

• Set monitored CUs

• Release monitored CUs

Related topics

• “View CU Matrix window” (page 180)

Changing the sampling interval

You can change the sampling interval for short-range 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.

Prerequisites

• Required role: Storage Administrator (Performance Management)

Procedure

1. Open the Performance Monitor window.
In Command View Advanced Edition:

1. On the Resources tab, expand the Storage Systems tree.

2. Right-click the target storage system, and then select Performance Monitor.
In Remote Web Console:

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

Performance Monitor window.

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

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

4. Click Finish.

5. In the Confirm window enter your task name in Task Name, and click Apply to change the
sampling interval.

In CVAE, you can check the progress of the task on the Tasks & Alerts tab. Click the task
name to view details of the task.

In RWC, the Tasks window opens if Go to tasks window for status is checked.

NOTE: Monitoring data cannot be displayed within the first two sampling intervals after the
monitoring starts or the sampling interval is changed because no monitoring data has accumulated.
For instance, if the sampling interval is changed to 15 minutes, monitoring data is not accumulated
for up to 29 minutes after the interval was changed.

Changing the sampling interval 23

Related topics

• “Edit Monitoring Switch window” (page 161)

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 Export
Tool, because the existing statistics are deleted each time monitoring is restarted.

Prerequisites

• Required role: Storage Administrator (Performance Management)

Procedure

1. Open the Performance Monitor window.
In Command View Advanced Edition:

1. On the Resources tab, expand the Storage Systems tree.

2. Right-click the target storage system, and then select Performance Monitor.
In Remote Web Console:

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

Performance Monitor window.

2. Click Edit Monitoring Switch to open the Edit Monitoring Switch window.

3. Click Disable in the Monitoring Switch field.
The Sample Interval list is grayed out and becomes ineffective.

4. Click Finish.

5. In the Confirm window, enter your task name in Task Name, and click Apply to stop
monitoring.

In CVAE, you can check the progress of the task on the Tasks & Alerts tab. Click the task
name to view details of the task.

In RWC, the Tasks window opens if Go to tasks window for status is checked.

Related topics

• “Edit Monitoring Switch wizard” (page 161)

Using the Performance Monitor data graphs

• “About the data graphs” (page 25)

• “Displaying the monitor data on graphs” (page 25)

• “Adding a new graph” (page 26)

• “Changing the data displayed on a graph” (page 27)

• “Changing the time period displayed on the graph panel” (page 27)

• “Deleting a graph from the graph panel” (page 28)

24 Performance Monitor operations

About the data graphs

The Performance Monitor data graphs are displayed on panels with the graph on the left and the
legend for the graph on the right. Performance Monitor can display up to four panels with up to
four graphs in each panel for a maximum of 16 graphs at the same time.

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

• You can plot up to 8 sets of data on each graph.

• You can display the value of each data point by placing the 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 might need to increase the vertical scale to see
data with high values.

In some cases, you might need to adjust the vertical scale to display the data properly. For
example, if the scale is too small, a single data line might 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 blades in real time (Time Range is set to Use Real
Time), the MP blade names are displayed as text links. Click the text link to display the

resources assigned to an MP blade of top 20 in usage rates on the detailed window.

Displaying the monitor data on graphs

Prerequisites

• Required role: Storage Administrator (Performance Management)

Procedure

To display the monitor data on graphs:

1. Open the Performance Monitor window.
In Command View Advanced Edition:

1. On the Resources tab, expand the Storage Systems tree.

2. Right-click the target storage system, and then select Performance Monitor.
In Remote Web Console:

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

Performance Monitor window.

2. Click Monitor Performance to open the Monitor Performance window.

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

1. In the Data Range field, select the desired data range: Long-Range or Short-Range.

If you want to display real-time data, you must select Short-Range.

2. 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. The Use Real
Time option can only be specified when Short-Range is selected.

3. If you selected Set Range, specify the starting date and time and ending date and time

for the range of data in the From and To fields.

4. Specify the monitor data to be displayed on the graphs:

Using the Performance Monitor data graphs 25

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

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

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

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

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

5. Click Apply to display the selected monitor data on graphs in the Monitor Performance
window.

Related topics

• “Performance Monitor main window” (page 159)

• “Monitor Performance window” (page 163)

Adding a new graph

Prerequisites

• Required role: Storage Administrator (Performance Management)

Procedure

1. Open the Performance Monitor window.
In Command View Advanced Edition:

1. On the Resources tab, expand the Storage Systems tree.

2. Right-click the target storage system, and then select Performance Monitor.
In Remote Web Console:

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

Performance Monitor window.

2. Display the graph panel in the Monitor Performance window.
For details, see “Displaying the monitor data on graphs” (page 25).

3. 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 must first delete an
existing graph. For details, see “Deleting a graph from the graph panel” (page 28).

4. 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 “Displaying the monitor data on graphs” (page 25).

5. Click OK to add the specified graph.

Related topics

• “Displaying the monitor data on graphs” (page 25)

• “Monitor Performance window” (page 163)

• “Add Graph window” (page 212)

26 Performance Monitor operations

Changing the data displayed on a graph

Prerequisites

• Required role: Storage Administrator (Performance Management)

Procedure

1. Open the Performance Monitor window.
In Command View Advanced Edition:

1. On the Resources tab, expand the Storage Systems tree.

2. Right-click the target storage system, and then select Performance Monitor.
In Remote Web Console:

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

Performance Monitor window.

2. Display the graph panel in the Monitor Performance window.
For details, see “Displaying the monitor data on graphs” (page 25).

3. Click Edit Performance Objects to open the Edit Performance Objects window.

4. 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 “Displaying the monitor data on graphs” (page 25).

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

Related topics

• “Monitor Performance window” (page 163)

• “Edit Performance Objects window” (page 200)

• “Displaying the monitor data on graphs” (page 25)

Changing the time period displayed on the graph panel

Prerequisites

• Required role: Storage Administrator (Performance Management)

Procedure

1. Open the Performance Monitor window.
In Command View Advanced Edition:

1. On the Resources tab, expand the Storage Systems tree.

2. Right-click the target storage system, and then select Performance Monitor.
In Remote Web Console:

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

Performance Monitor window.

2. Display the graph panel in the Monitor Performance window.
For details, see “Displaying the monitor data on graphs” (page 25).

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

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

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

Using the Performance Monitor data graphs 27

Related topics

• “Displaying the monitor data on graphs” (page 25)

• “Monitor Performance window” (page 163)

• “Edit Time Range window” (page 199)

Deleting a graph from the graph panel

Prerequisites

• Required role: Storage Administrator (Performance Management)

Procedure

1. Open the Performance Monitor window.
In Command View Advanced Edition:

1. On the Resources tab, expand the Storage Systems tree.

2. Right-click the target storage system, and then select Performance Monitor.
In Remote Web Console:

1. Select Analytics in Explorer.

2. Select Performance Monitor in the tree to open the Performance Monitor window.

2. Display the graph panel in the Monitor Performance window.
For details, see “Displaying the monitor data on graphs” (page 25).

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

• “Displaying the monitor data on graphs” (page 25)

• “Monitor Performance window” (page 163)

28 Performance Monitor operations

3 Performance Monitor data

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

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 resources
that are shown in the necessary resources 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 for Short Range and 15 minutes for
Long Range. 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” (page 24).

monitoring

port

Monitoring dataObject of

Usage rates of DRR (%)

Write pending rates (%)

Usage rates of access path between DKA and cache (%)

Usage rates of access path between MP blade and cache (%)

Usage rates of access path between cache (%)

Data transfer (Mbps)

Response time (ms)

Data transfer (Mbps)

Response time (ms)

Necessary
resources

NoneUsage rates of MPs (%)Controller

NoneUsage rates of cache (%)Cache

NoneUsage rates of access path between CHA and cache (%)Access path

PortThroughput (IOPS)Fibre port

PortThroughput (IOPS)Mainframe fibre

CMR delay time (ms)

Disconnected time (ms)

Connected time (ms)

HTP port open exchange (count/sec)

Data transfer (Mbps)

Response time (ms)

Data transfer of WWN (Mbps)

PortThroughput (IOPS)iSCSI Port

PortThroughput of WWN (IOPS)WWN

Monitoring data 29

monitoring

Monitoring dataObject of

Response time of WWN (ms)

Throughput of port (IOPS)

Data transfer of port (Mbps)

Response time of port (ms)

Read throughput (IOPS)

Write throughput (IOPS)

Cache hit (%)

Data transfer (Mbps)

Response time (ms)

Back transfer (count/sec)

Drive usage rate (%)

Drive access rate (%)

1

1

Business Copy usage rates (BC/BC MF) (%)

Necessary
resources

LDEVTotal throughput (IOPS)LDEV (base)

1,2

Cnt Ac-J MF)

Ac-S/Cnt Ac-S
MF/HA)

LDEVWrite host I/O throughput (IOPS)LDEV (Cnt Ac-J/

Write host I/O data transfer (Mbps)

Initial copy cache hit (%)

Initial copy data transfer (Mbps)

LDEVRIO (count)LDEV (Cnt

Pair Synchronized (%)

Differential track (count)

Initial copy throughput (count)

Initial copy data transfer (Mbps)

Initial copy response time (ms)

Update copy throughput (count)

Update copy data transfer (Mbps)

Update copy response time (ms)

Parity groupTotal throughput (IOPS)Parity group

Read throughput (IOPS)

Write throughput (IOPS)

30 Performance Monitor data

Cache hit (%)

Data transfer (Mbps)

Response time (ms)

Back transfer (count/sec)

Drive usage rate (%)

1

monitoring

Monitoring dataObject of

Necessary
resources

Ac-S/HA)

Total throughput (IOPS)LUN (base)

Read throughput (IOPS)

• Host group

• LDEV

Write throughput (IOPS)

Cache hit (%)

Data transfer (Mbps)

Response time (ms)

Back transfer (count/sec)

3

Write host I/O throughput (IOPS)LUN (Cnt Ac-J)

Write host I/O data transfer (Mbps)

• Host group

• LDEV

Initial copy cache hit (%)

Initial copy data transfer (Mbps)

3

RIO (count)LUN (Cnt

Pair Synchronized (%)

• Host group

• LDEV

Differential track (count)

Initial copy throughput (count)

Initial copy data transfer (Mbps)

External storage

system (Cnt
Ac-S/Cnt Ac-S
MF/HA)

Initial copy response time (ms)

Update copy throughput (count)

Update copy data transfer (Mbps)

Update copy response time (ms)

LDEVData transfer between XP7 Storage system and external storage per

logical device (Mbps)

Response time between XP7 Storage system and external storage per
logical device (ms)

Parity groupData transfer between XP7 Storage system and external storage per

external volume group (Mbps)

Response time between XP7 Storage system and external storage per
external volume group (ms)

NoneRIO (count)Entire storage

Pair Synchronized (%)

Differential track (count)

Initial copy throughput (count)

Initial copy data transfer (Mbps)

Initial copy response time (ms)

Update copy throughput (count)

Update copy data transfer (Mbps)

Update copy response time (ms)

Monitoring data 31

monitoring

Ac-J/Cnt Ac-J MF)

Monitoring dataObject of

Write host I/O data transfer (Mbps)

Initial copy cache hit (%)

Initial copy data transfer (Mbps)

Master journal throughput (IOPS)

Master journal journal (count/sec)

Master journal data transfer (Mbps)

Master journal response time (ms)

Master journal usage data (%)

Master journal metadata usage rate (%)

Restore journal throughput (IOPS)

Restore journal journal (count/sec)

Restore journal data transfer (Mbps)

Restore journal response time (ms)

Necessary
resources

NoneWrite host I/O throughput (IOPS)Journal (Cnt

Restore journal usage data (%)

Restore journal metadata usage rate (%)

NoneWrite host I/O throughput (IOPS)Entire storage
system (Cnt
Ac-J/Cnt Ac-J MF)

Note:

1. Only information on internal volumes is displayed. Information on external volumes and FICON® DM volumes is

not displayed.

2. Includes usage rates for Business Copy MF.

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

Write host I/O data transfer (Mbps)

Initial copy cache hit (%)

Initial copy data transfer (Mbps)

Master journal throughput (IOPS)

Master journal journal (count/sec)

Master journal data transfer (Mbps)

Master journal response time (ms)

Restore journal throughput (IOPS)

Restore journal journal (count/sec)

Restore journal data transfer (Mbps)

Restore journal response time (ms)

32 Performance Monitor data

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

Storing period

Short-Range or Long-Range can be specified.

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on left side of Object
field

Usage rate of DRRs

Function

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

If the monitor data shows high DRR usage overall, perform either of the following operations to
distribute the workload for the system:

• Move a volume whose write usage rate is high (especially, sequential write usage rate) from
a RAID-5 (or RAID-6) parity group to a RAID-1 parity group.

• Move the data to another storage system.

Use Auto LUN to move a volume. For details on Auto LUN, see the XP7 Auto LUN User Guide.
If the monitor data shows relatively high DRR usage overall, the performance of the system might

not be improved even after moving a volume using Auto LUN.

Storing period

Item on right side of
Object field

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

NoneUsage Rate (%)MPController

Short-Range or Long-Range can be specified.

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on left side of Object
field

Item on right side of
Object field

Usage rate of cache memory

Function

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

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

NoneUsage Rate (%)DRRController

Usage rates of MPs 33

Storing period

Short-Range can be specified.

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on left side of Object
field

Write pending rates

Function

The write pending rate indicates the ratio of write pending data to the cache memory capacity.
It is expressed as a percentage of the cache memory capacity used for write pending. The Monitor
Performance window displays the average and the maximum write pending rate for the specified
period of time.

Storing period

Short-Range or Long-Range can be specified.

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on left side of Object
field

Item on right side of
Object field

Item on right side of
Object field

Item on left side of
Monitor Data field

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

NoneUsage Rate (%)NoneCache

Item on right side of
Monitor Data field

Usage rates of access paths

Function

The access paths are the paths through which data and commands are transferred within a
storage system. As shown in the following figure, the channel adapters (CHAs) (also called
channel adapters) in the XP7 Storage system control the transfer of data between the hosts and
the cache memory, and the disk adapters (DKAs) (also called disk adapters) control the transfer
of data between the cache memory and the data drives, as shown below. Data transfer does not
occur between the channel adapters and disk adapters. Data is transferred through the CM
package (cache switch) to the cache memory.

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

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

• Access paths between channel adapters and the CM package (CHA cache)

• Access paths between disk adapters and the CM package (DKA cache)

• Access paths between the MP blade and the CM package (MP blade cache)

• Access paths in the CM package (cache)

NoneWrite Pending Rate (%)NoneCache

34 Performance Monitor data

Storing period

Short-Range or Long-Range can be specified.

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on left side of Object
field

Item on right side of
Object field

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

• Cache fast write (CFW) mode

• Total value in the above-mentioned modes

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

NoneUsage Rate (%)CHA cacheAccess path

NoneUsage Rate (%)DKA cache

NoneUsage Rate (%)MP blade cache

NoneUsage Rate (%)Cache

Storing period

Short-Range can be specified.

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on left side of Object
field

1

1

Item on right side of
Object field

Item on left side of
Monitor Data field

Storage system throughput 35

Item on right side of
Monitor Data field

NoneThroughput (IOPS)NoneFibre port

NoneThroughput (IOPS)NoneMainframe fibre port

Item on left side of Object
field

1

1

1

Item on right side of
Object field

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

NoneThroughput (IOPS)NoneiSCSI Port

NoneThroughput (IOPS)WWNWWN

NoneThroughput (IOPS)Port

TotalTotal Throughput (IOPS)BaseLogical device

Sequential

Random

CFW

TotalRead Throughput (IOPS)

Sequential

Random

CFW

TotalWrite Throughput (IOPS)

Sequential

Random

CFW

Initial copyCnt Ac-S/Cnt Ac-S MF/HA

Update copy

Throughput (count)

Throughput (count)

2

2

Throughput (IOPS)Write Host I/OCnt Ac-J/Cnt Ac-J MF

1

TotalTotal Throughput (IOPS)NoneParity Group

Sequential

Random

CFW

TotalRead Throughput (IOPS)

Sequential

Random

CFW

TotalWrite Throughput (IOPS)

Sequential

Random

CFW

3

TotalTotal Throughput (IOPS)BaseLUN

36 Performance Monitor data

Sequential

Random

CFW

TotalRead Throughput (IOPS)

Item on left side of Object
field

Item on right side of
Object field

Item on left side of
Monitor Data field

Initial copyCnt Ac-S/HA

Update copy

Initial copyCnt Ac-S/Cnt Ac-S MF/HAEntire Storage System

Update copy

Item on right side of
Monitor Data field

Sequential

Random

CFW

TotalWrite Throughput (IOPS)

Sequential

Random

CFW

Throughput (count)

Throughput (count)

Throughput (IOPS)Write host I/OCnt Ac-J

Throughput (IOPS)Write host I/OCnt Ac-J/Cnt Ac-J MFJournal

Throughput (IOPS)Master journal

Throughput (IOPS)Restore journal

Throughput (count)

Throughput (count)

2

2

2

2

Note:

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

Short-Range can be specified.

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Throughput (IOPS)Write host I/OCnt Ac-J/Cnt Ac-J MF

Throughput (IOPS)Master journal

Throughput (IOPS)Restore journal

Item on left side of Object
field

Item on right side of
Object field

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

NoneData Trans. (Mbps)NoneFibre port*

TotalData Trans. (Mbps)NoneMainframe fibre port*

Read

Data transfer rate 37

Item on left side of Object
field

Item on right side of
Object field

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

Write

NoneData Trans. (Mbps)NoneiSCSI Port*

NoneData Trans. (Mbps)WWNWWN*

NoneData Trans. (Mbps)Port

TotalData Trans. (Mbps)BaseLogical device*

Read

Write

Data Trans. (Mbps)Initial CopyCnt Ac-S/Cnt Ac-S MF/HA

Data Trans. (Mbps)Update Copy

Data Trans. (Mbps)Write Host I/OCnt Ac-J/Cnt Ac-J MF

Data Trans. (Mbps)Initial Copy

TotalData Trans. (Mbps)NoneParity Group*

Read

Write

TotalData Trans. (Mbps)BaseLUN*

Read

Write

Data Trans. (Mbps)Initial CopyCnt Ac-S/HA

Data Trans. (Mbps)Update Copy

Data Trans. (Mbps)Write Host I/OCnt Ac-J

Data Trans. (Mbps)Initial Copy

TotalData Trans. (Mbps)Parity GroupExternal Storage

Read

Write

TotalData Trans. (Mbps)Logical Device

Read

Write

Data Trans. (Mbps)Write host I/OCnt Ac-J/Cnt Ac-J MFJournal

Data Trans. (Mbps)Initial copy

Data Trans. (Mbps)Master journal

38 Performance Monitor data

Data Trans. (Mbps)Restore journal

Data Trans. (Mbps)Initial copyCnt Ac-S/Cnt Ac-S MF/HAEntire Storage System

Data Trans. (Mbps)Update copy

Data Trans. (Mbps)Write host I/OCnt Ac-J/Cnt Ac-J MF

Data Trans. (Mbps)Initial copy

Item on left side of Object
field

* 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 XP7 Storage system to the external volume group. The average response time in the
period specified at Monitoring Term is displayed.

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

Storing period

Short-Range can be specified.

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on right side of
Object field

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

Data Trans. (Mbps)Master journal

Data Trans. (Mbps)Restore journal

Item on left side of Object
field

Item on right side of
Object field

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

NoneResponse Time (ms)NoneFibre port*

NoneResponse Time (ms)NoneMainframe fibre port*

NoneResponse Time (ms)NoneiSCSI Port*

NoneResponse Time (ms)WWNWWN*

NoneResponse Time (ms)Port

TotalResponse Time (ms)BaseLogical device*

Read

Write

Response Time (ms)Initial CopyCnt Ac-S/Cnt Ac-S MF/HA

Response Time (ms)Update Copy

TotalResponse Time (ms)NoneParity group*

Read

Write

TotalResponse Time (ms)BaseLUN*

Read

Write

Response Time (ms)Initial CopyCnt Ac-S/HA

Response Time (ms)Update Copy

TotalResponse Time (ms)Parity GroupExternal Storage

Response times 39

Item on left side of Object
field

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

CMR delay time

Item on right side of
Object field

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

Read

Write

TotalResponse Time (ms)Logical Device

Read

Write

Response Time (ms)Master JournalCnt Ac-J/Cnt Ac-J MFJournal

Response Time (ms)Restore Journal

Response Time (ms)Initial CopyCnt Ac-S/Cnt Ac-S MF/HAEntire Storage System

Response Time (ms)Update Copy

Response Time (ms)Master JournalCnt Ac-J/Cnt Ac-J MF

Response Time (ms)Restore Journal

Function

When I/O access from the storage system is made to the monitoring object port, command
response (CMR) delay time shows the time (in milliseconds) from the I/O access to the return of
a command response from the port.

Storing period

Short-Range can be specified.

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on left side of Object
field

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

Disconnected time

Function

When I/O access is made from the storage system to the monitoring object port, Disconnected
time shows the time (in milliseconds) during which processing is interrupted because of I/O
processing to the data drives.

Item on right side of
Object field

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

NoneCMR delay Time (ms)NoneMainframe fibre port*

Storing period

Short-Range can be specified.

40 Performance Monitor data

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on left side of Object
field

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

Connected time

Function

Connected time shows the time (in milliseconds) obtained by subtracting the CMR delay time
and the disconnected time from the response time.

Storing period

Short-Range can be specified.

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on left side of Object
field

Item on right side of
Object field

Item on right side of
Object field

Item on left side of
Monitor Data field

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

NoneDisconnected Time (ms)NoneMainframe fibre port*

Item on right side of
Monitor Data field

NoneConnected Time (ms)NoneMainframe fibre port*

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

HTP port open exchanges

Function

HTP port open exchanges shows the number of open exchanges for the monitoring object port.
The number of open exchanges is the average number of active I/O accesses at the monitoring
object port.

Storing period

Short-Range can be specified.

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on left side of
Object field

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

Item on right side of
Object field

NoneMainframe fibre port*

Item on left side of Monitor
Data field

(count/sec)

Item on right side of
Monitor Data field

NoneHTP Port Open Exchanges

Connected time 41

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 the sequential access mode, the random access mode, the cache fast
write (CFW) mode, and the entire these modes.

• Read hit ratio
For a read I/O, when the requested data is already in cache, the operation is classified as

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

• Write hit ratio
For a write I/O, when the requested data is already in cache, the operation is classified as

a write hit. For example, if ten write requests were made from hosts to devices in a given
time period and the write data was already on the cache memory three cases out of ten, the
write 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

Short-Range can be specified.

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on left side of Object
field

Item on right side of
Object field

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

Read (Total)Cache Hit (%)BaseLogical Device*

Read (Sequential)

Read (Random)

Read (CFW)

Write (Total)

Write (Sequential)

Write (Random)

Write (CFW)

Cache Hit (%)Initial CopyCnt Ac-J/Cnt Ac-J MF

42 Performance Monitor data

Read (Total)Cache Hit (%)NoneParity Group*

Read (Sequential)

Read (Random)

Read (CFW)

Write (Total)

Write (Sequential)

Item on left side of Object
field

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

Item on right side of
Object field

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

Write (Random)

Write (CFW)

Read (Total)Cache Hit (%)BaseLUN*

Read (Sequential)

Read (Random)

Read (CFW)

Write (Total)

Write (Sequential)

Write (Random)

Write (CFW)

Cache Hit (%)Initial CopyCnt Ac-J

Cache Hit (%)Initial CopyCnt Ac-J/Cnt Ac-J MFEntire Storage System

Cache Hit (%)Initial CopyCnt Ac-J/Cnt Ac-J MFJournal

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

Short-Range can be specified.

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on left side of Object
field

Item on right side of
Object field

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

TotalBack Trans. (count/sec)BaseLogical Device*

Cache to Drive

Drive to Cache (Sequential)

Back-end performance 43

Item on left side of Object
field

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

Drive usage rates

Function

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

Item on right side of
Object field

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

Drive to Cache (Random)

TotalBack Trans. (count/sec)NoneParity Group*

Cache to Drive

Drive to Cache (Sequential)

Drive to Cache (Random)

TotalBack Trans. (count/sec)BaseLUN*

Cache to Drive

Drive to Cache (Sequential)

Drive to Cache (Random)

Storing period

Short-Range or Long-Range can be specified.

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on left side of Object
field

*Only information on internal volumes is displayed. Information about external volumes, FICON® DM volumes, and
virtual volumes such as THP V-VOL and Fast Snap V-VOLs 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.

Item on right side of
Object field

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

NoneDrive Usage Rate (%)BaseLogical Device*

NoneDrive Usage Rate (%)NoneParity Group*

Storing period

Long-Range or Short-Range can be specified.

44 Performance Monitor data

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on left side of Object
field

*Only information on internal volumes is displayed. Information about external volumes, FICON® DM volumes, and
virtual volumes such as THP V-VOL and Fast Snap V-VOLs is not displayed.

Item on right side of
Object field

Business Copy usage statistics

Function

The access rate of volume by Business Copy and Business Copy MF 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.

Storing period

Short-Range can be specified.

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

Read (Sequential)Drive Access Rate (%)BaseLogical device*

Read (Random)

Write (Sequential)

Write (Random)

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on left side of Object
field

1

Note:

1. Only information on internal volumes is displayed. Information about external volumes, FICON® DM volumes,

and virtual volumes such as THP V-VOL and Fast Snap V-VOLs is not displayed.

2. Information for Business Copy and Business Copy MF is displayed.

Remote I/O (RIO)

Function

Information about LDEV performance is shown through the total number of remote I/Os from
P-VOL to S-VOL for Continuous Access Synchronous, Continuous Access Synchronous MF,
and High Availability pairs.

Storing period

Short-Range can be specified.

Item on right side of
Object field

BaseLogical device

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

2

NoneBusiness Copy (%)

Business Copy usage statistics 45

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on left side of Object
field

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

Pair Synchronized

Function

The synchronization rate between P-VOL and S-VOL is shown as (%) for Continuous Access
Synchronous, Continuous Access Synchronous MF, and High Availability pairs.

Item on right side of
Object field

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

TotalRIO (count)Cnt Ac-S/Cnt Ac-S MF/HALogical Device*

Write

Error

TotalRIO (count)Cnt Ac-S/HALUN*

Write

Error

TotalRIO (count)Cnt Ac-S/Cnt Ac-S MF/HAEntire Storage System

Write

Error

Storing period

Short-Range can be specified.

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on left side of
Object field

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

Differential Track

Function

The synchronization rate between P-VOL and S-VOL is shown through the number of differential
tracks (the number of tracks not transmitted from P-VOL to S-VOL) for Continuous Access
Synchronous, Continuous Access Synchronous MF, and High Availability pairs.

Item on right side of
Object field

Item on left side of Monitor
Data field

Item on right side of
Monitor Data field

NonePair Synchronized (%)Cnt Ac-S/Cnt Ac-S MF/HALogical Device*

NonePair Synchronized (%)Cnt Ac-S/HALUN*

NonePair Synchronized (%)Cnt Ac-S/Cnt Ac-S MF/HAEntire Storage System

Storing period

Short-Range can be specified.

46 Performance Monitor data

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on left side of
Object field

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

Number of Journals

Function

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

Storing period

Short-Range can be specified.

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on right side of Object
field

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

NoneDifferential track (count)Cnt Ac-S/Cnt Ac-S MF/HALogical Device*

NoneDifferential track (count)Cnt Ac-S/HALUN*

NoneDifferential track (count)Cnt Ac-S/Cnt Ac-S MF/HAEntire Storage System

Item on left side of Object
field

Data Usage Rate

Function

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

Storing period

Short-Range can be specified.

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on right side of
Object field

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

Journal (count/sec)Master JournalCnt Ac-J/Cnt Ac-J MFJournal

Journal (count/sec)Restore Journal

Journal (count/sec)Master JournalCnt Ac-J/Cnt Ac-J MFEntire Storage System

Journal (count/sec)Restore Journal

Item on left side of
Object field

Item on right side of
Object field

Item on left side of
Monitor Data field

Item on right side of Monitor
Data field

Data Usage Rate (%)Master JournalCnt Ac-J/Cnt Ac-J MFJournal

Data Usage Rate (%)Restore Journal

Number of Journals 47

Metadata Usage Rate

Function

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

Storing period

Short-Range can be specified.

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on left side of
Object field

Item on right side of
Object field

Item on left side of
Monitor Data field

Item on right side of Monitor Data
field

Metadata Usage Rate (%)Master JournalCnt Ac-J/Cnt Ac-J MFJournal

Metadata Usage Rate (%)Restore Journal

Detailed information of resources on top 20 usage rates

Function

You can view resources of the 20 most-used MP blades. The system puts in order of use 20 MP
blades based on rates collected during the most recent usage period. You cannot specify a
particular period.

Storing period

Only the Short-Range real time monitoring data can be supported.

Selection of monitoring objects

Select the desired monitoring objects in the Performance Objects field.

Item on left side of Object
field

Item on right side of
Object field

Item on left side of
Monitor Data field

Item on right side of
Monitor Data field

Viewing MP blade resource details

To view the resources assigned to an individual MP blade, click the link to the name of the MP
blade in the right panel of the Monitor window. The MP Properties window lists the 20 most-used
resources by blade name.

48 Performance Monitor data

NoneUsage Rate (%)MPController

4 Exporting Performance Monitor data

This chapter describes and provides instructions for using Export Tool to export Performance
Monitor data for your XP7 Storage system to the spreadsheet application and other applications.

About Export Tool

Use Export Tool to export the monitoring data (statistics) shown in the Monitor Performance
window to text files. After exporting monitoring data to text files, you can import that data into
desktop publishing applications, such as Microsoft Word, or into the spreadsheet application or
database applications for analysis. You can also use Export Tool to export monitoring data on
remote copy operations performed by Continuous Access Synchronous, Continuous Access
Synchronous MF, Continuous Access Journal, and Continuous Access Journal MF.

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 cannot find 1-3[1-4] in column
headings. To locate monitoring data about 1-3[1-4], locate the 1-3 column or the 1-4 column.
Either of these columns contains monitoring data about 1-3[1-4].

Preparing to use Export Tool

Export Tool limitation

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

About Export Tool 49

Requirements for Export Tool

The following components are required to use Export Tool (for more information, see the XP7
Remote Web Console User Guide):

• Windows computer or a UNIX computer

You can only run Export Tool on Windows computers and UNIX computers that can run
Remote Web Console.

NOTE: If a firewall exists between the Remote Web Console computer and the SVP, see
Chapter 2 of the XP7 Remote Web Console User Guide. In the section “Setting up TCP/IP
for a firewall”, the RMI port numbers listed are the only direct communication settings required
for Export Tool.

• Java Runtime Environment (JRE)

To use Export Tool, you must have the JRE software on your Windows computer or UNIX
computer. If your computer runs Remote Web Console, the required JRE version is already
installed, and you can install Export Tool. Both Export Tool and Remote Web Console use
the same JRE version. For the required JRE version, see the chapter on how to use the
Remote Web Console secondary window in the XP7 Remote Web Console User Guide.

• User ID for exclusive use of Export Tool

Before you can use Export Tool, you must create a user ID for exclusive use of Export Tool.
Assign only the Storage Administrator (Performance Management) role to the user ID for
Export Tool. You should not assign any roles other than the Storage Administrator
(Performance Management) role to this user ID. The user who is assigned to the Storage
Administrator (Performance Management) role can perform the following:

◦ Save the monitoring data into files

◦ Change the sampling interval

◦ Start or stop monitoring by using the set subcommand

For details on creating the user ID, see XP7 Remote Web Console User Guide.

• Export Tool program

CD-ROM Disc 2, which is named Host PP, contains Export Tool. For information about how
to install Export Tool, see “Installing Export Tool” (page 50).

If the version of the DKCMAIN program is 80-03-01-00/00 or later and the version of Export
Tool is 80-03-01/00 or later, the reinstallation of Export Tool is not mandatory. For the version
of Export Tool, see the Readme.txt file on the Host PP disk.

CAUTION: Remove Export Tool if the installed Export Tool version is earlier than
80-03-01/00. To remove Export Tool, delete the folder created when Export Tool was installed.
This operation also deletes the monitoring data, the log data obtained by Export Tool, and
the files edited by the user. If you need monitoring data, log data, and the files edited by the
user, save them in a separate folder before removing Export Tool.

Installing Export Tool

• “On Windows” (page 51)

• “On UNIX” (page 51)

50 Exporting Performance Monitor data

On Windows

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

CAUTION: The files edited by the user are overwritten if Export Tool is reinstalled. Save these
files in a separate folder in advance.

1. Log on with administrator privileges.

2. Create a new folder for the Export Tool application (for example, C:\Program Files\

3. Insert the Export Tool CD-ROM into the CD drive.

4. Locate the \program\monitor\win folder on the CD-ROM, and copy the self-extracting

5. Double-click export.exe to start the installation. Export Tool is installed into the installation

On UNIX

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

monitor). If the folder already exists, skip this step.

file export.exe from the CD-ROM into the new folder you just created.

directory, and a new folder named “export” is created.

NOTE: You should delete runUnix.bat and delUnix.bat from the export folder
because these files are no longer needed.

CAUTION: The files edited by the user are overwritten if Export Tool is reinstalled. Save these
files in a separate folder in advance.

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

3. Mount the Export Tool CD-ROM.

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

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

NOTE: You should delete runWin.bat and delWin.bat from the installation directory
because these files are no longer needed.

Using Export Tool

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

Preparing a command file

To run 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 Export Tool, the
subcommands in the command file run sequentially, and then the monitoring data is saved in
files.

Example of a command file

svpip 158.214.135.57 ; Specifies IP address of SVP
login expusr passwd ; Logs user into the SVP
show ; Outputs storing period to standard

Using Export Tool 51

; output

group PhyPG Long ; Specifies type of data to be

; exported and type of
; storing period

group RemoteCopy ; Specifies type of data to be

; exported

shortrange 201305010850:201305010910

; Specifies term of data to be
; exported for data stored
; in short range

longrange 201304301430:201305011430

; Specifies term of data to be
; exported for data stored
; in long range

outpath out ; Specifies directory in which files

; will be saved
option compress ; Specifies whether to compress files
apply ; Executes processing for saving

; monitoring data in files

A semicolon (;) indicates the beginning of a comment. Characters from a semicolon to the end
of the line are comments.

The scripts in this command file are explained as follows:

• svpip 158.214.135.57

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

The svpip subcommand specifies the IP address of the SVP. You must include the svpip
subcommand in your command file. For detailed information about the svpip subcommand,
see “svpip” (page 62).

Export Tool creates a directory with the name specified by the svpip subcommand under
the following directory:

- For Windows: export\lib

- For UNIX: export\lib
If the value specified by the svpip subcommand is an IP address, a hexadecimal value is

specified as the directory name. Periods (.) and colons (:) cannot be used. If the value is a
host name, the IP address of the specified server is specified as the directory name.

The following table provides examples of directory names to be created.

0000:0000:0020:00B4:0000:0000:9ED6:874 (for IPv6)

of host01 is 158.214.135.57)

• login expusr passwd

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

52 Exporting Performance Monitor data

Directory nameValue specified by the svpip subcommand

9ED68739Value for the svpip subcommand is svpip 158.214.135.57 (for IPv4)

00000000002000B4000000009ED68740Value for the svpip subcommand is svpip

9ED68739Value for the svpip subcommand is svpip host01 (when the IP address

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” (page 63).

CAUTION: When you write the login subcommand in your command file, you must
specify a user ID that is used exclusively for running Export Tool. See “Requirements for

Export Tool” (page 50) 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.

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

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

Short Range From: 2013/05/01 01:00 - To: 2013/05/01 15:00

Interval: 1min.

Long Range From: 2013/04/01 00:00 - To: 2013/05/01 15:00

Interval: 15min.

Short Range indicates the storing period and sampling interval of the monitoring data

stored in short range. Long Range indicates those of the monitoring data stored in long
range. In the previous example, the monitoring data in short range is stored every 1 minute
in the term of 1:00-15:00 on May 1, 2013. Also, the monitoring data in long range is stored
every 15 minutes in the term of April 1, 2013, 0:00 through May 1, 2013, 15:00. When you
run Export Tool, you can export monitoring data within these periods into files.

All of the monitoring items are stored in short range, but a part of monitoring items is stored
in both short range and long range. For details on monitoring items that can be stored in
long range, see “longrange” (page 76).

The use of the show subcommand is not mandatory, but you should include the show
subcommand in your command file. If an error occurs when you run 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” (page 64).

• group PhyPG Long 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. Basically, monitoring
data stored in short range is exported. But you can direct the export of monitoring data stored
in long range when you specify some of the operands.

The example script group PhyPG Long in “Preparing a command file” (page 51) specifies
to export usage statistics about parity groups in long range. Also, the script
group RemoteCopy specifies to export statistics about remote copy operations by
Continuous Access Synchronous and Continuous Access Synchronous MF and monitoring
data by High Availability in short range. You can describe multiple lines of the group
subcommand to export multiple monitoring items at the same time.

For detailed information about the group subcommand, see “group” (page 65).

• shortrange 201305010850:201310010910 and longrange
201304301430:201305011430

The shortrange subcommand and the longrange subcommand specify the term of
monitoring data to be exported. Use these subcommands when you want to narrow the

Using Export Tool 53

export-target term within the stored data. You can specify both subcommands at the same
time. The difference between these subcommands is as follows:

◦ The shortrange subcommand is valid for monitoring data in short range. 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 "Short Range From XXX To XXX" which is output by the
show subcommand.

◦ The longrange subcommand is valid for monitoring data in long range. You can use

this subcommand only when you specify the PhyPG, PhyLDEV, PhyProc, or PhyCMPK
operand with the Long option in the group subcommand. (The items that can be saved
by these operands are the monitoring data displayed on the Physical tab of the
Performance Management window with selecting longrange.)

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

In the sample file in “Preparing a command file” (page 51), the script shortrange
201305010850:201305010910 specifies the term 8:50-9:10 on May 1, 2013. This script
is applied to the group RemoteCopy subcommand in this example. When you run Export
Tool, it will export the statistics about remote copy operations by Continuous Access
Synchronous and Continuous Access Synchronous MF and monitoring data by High
Availability in the term specified by the shortrange subcommand.

Also, in “Preparing a command file” (page 51), the script longrange
201304301430:201305011430 specifies the term from April 30, 2013, 14:30 to May 1,
2013, 14:30. This script is applied to the group PhyPG Long subcommand in this example.
When you run Export Tool, it will export the usage statistics about parity groups in the term
specified by the longrange subcommand.

If you run Export Tool without specifying the shortrange or longrange subcommand,
the monitoring data in the entire storing period (data in the period displayed by the show
subcommand) will be exported.

◦ For detailed information about the shortrange subcommand, see “shortrange”

(page 74).

◦ For detailed information about the longrange subcommand, see “longrange” (page 76).

• outpath out

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

The outpath subcommand specifies the directory in which files will be saved. For detailed
information about the outpath subcommand, see “outpath” (page 78).

• option compress

This script specifies that Export Tool will compress monitoring data in ZIP files.
The option subcommand specifies whether to save files in ZIP format or in CSV format.

For more information, see “option” (page 79).

• apply

The apply subcommand saves monitoring data in files. For detailed information about the
apply command, see “apply” (page 80).

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

54 Exporting Performance Monitor data

according to your needs. For detailed information about subcommand syntax, see “Export Tool

command reference” (page 60).

Preparing a batch file

Use a batch file to run Export Tool, which starts and saves monitoring data in files when you run
the batch file.

The installation directory for Export Tool contains four default batch files: runWin.bat,

runUnix.bat, delWin.bat, and delUnix.bat. If your computer runs Windows, use
runWin.bat and delWin.bat. If your computer runs UNIX, use runUnix.bat and
delUnix.bat.

The following examples illustrate scripts in runWin.bat and runUnix.bat batch files. These
batch files include a command line that runs a Java command. When you run the batch file, the
Java command runs 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/JSanExportLoader.jar"

-Del.tool.Xmx=536870912 -Dmd.command=command.txt

-Del.logpath=log -Dmd.rmitimeout=20

sanproject.getexptool.RJElMain<CR+LF>
pause<CR+LF>

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

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

-Del.tool.Xmx=536870912 -Dmd.command=command.txt

-Del.logpath=log -Dmd.rmitimeout=20

sanproject.getexptool.RJElMain<LF>

In the previous scripts, <CR+LF> and <LF> indicate the end of a command line.
If the computer running 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 occasions, for example:

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

• If you moved your command file to a different directory

• If you do not want to save in the log directory

• If you want to name log files as you like

If the computer that runs 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 the IP address) and the port
number of the proxy host. For example, if the host name is Jupiter and the port number is 8080,
the resulting command script would be as shown in the following examples:

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

java -classpath "./lib/JSanExportLoader.jar"

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

-Del.tool.Xmx=536870912 -Dmd.command=command.txt

-Dmd.logpath=log -Dmd.rmitimeout=20 sanproject.getexptool.RJElMain<CR+LF>

pause<CR+LF>

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

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

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

-Del.tool.Xmx=536870912

-Dmd.command=command.txt

-Dmd.logpath=log -Dmd.rmitimeout=20 sanproject.getexptool.RJElMain<LF>

Using Export Tool 55

In the preceding scripts, <CR+LF> and <LF> indicate 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/JSanExportLoader.jar"

-Dhttp.proxyHost=158.211.122.124

-Dhttp.proxyPort=8080 -Del.tool.Xmx=536870912

-Dmd.command=command.txt

-Dmd.logpath=log -Dmd.rmitimeout=20 sanproject.getexptool.RJElMain<CR+LF>
pause<CR+LF>

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

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

-Dhttp.proxyHost=158.211.122.124

-Dhttp.proxyPort=8080 -Del.tool.Xmx=536870912

-Dmd.command=command.txt

-Dmd.logpath=log -Dmd.rmitimeout=20 sanproject.getexptool.RJElMain<LF>

In the above scripts, <CR+LF> and <LF> indicate the end of a command line.
The following examples illustrate scripts in delWin.bat and delUnix.bat files. These batch

files include a command line that runs a Java command. When you run the batch file, the Java
command is run, and the directories created by Export Tool, and the files in the directories are
deleted.

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

java -classpath "./lib/JSanExportLoader.jar"

-Dmd.command=command.txt

-Del.logpath=log

-Del.mode=delete sanproject.getexptool.RJElMain<CR+LF>

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

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

-Dmd.command=command.txt

-Del.logpath=log

-Del.mode=delete sanproject.getexptool.RJElMain<LF>

For detailed information about syntax of the Java command, see “Java” (page 82).

Running Export Tool

Running a batch file

To save monitoring data in files, launch Export Tool by running the batch file.
From a system running Windows, double-click the batch file to run it.

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 Export Tool restarts automatically.

Example of command prompt outputs from Export Tool:

[ 2] svpip 158.214.135.57
[ 3] login User = expusr, Passwd = [****************]

:
:

[ 6] group Port

:

:
[20] apply
Start gathering port data

56 Exporting Performance Monitor data

Target = 16, Total = 16

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

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

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

End gathering port data

It might take time after Loading ExportTool is displayed in the command prompt and before

Export tool start [Version 80-xx-xx/xx] is displayed. The time elapsed between the two

messages varies depending on the communication environment of the computer and SVP. The

following table shows the approximate time period.

Approximate timeLine usage rate (%)Communication speed between a computer and SVP

1 minute0.11 Gbps

12 seconds0.5

5 minutes0.2100 Mbps

1 minute1

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 must obtain software to view the data.

When Export Tool is running, if an internal error listed in the Errors in the Export Tool table

occurs, an exclamation mark (!) appears, and then Export Tool tries to export again. By default,

Export Tool retries three times.

If export processing does not end after three retries, or an internal error that is not listed in the

table occurs, no retries are performed. In this case, close the command prompt, and then run

Export Tool again.

Note that the maximum number of retries can be changed by the retry subcommand. For details

about the retry subcommand, see “retry” (page 62).

When Export Tool processing is completed, the directories and files created by Export Tool are

deleted automatically. If Export processing stops abnormally, the following directories and files

are not deleted:

export/lib/SVP-value

JSanExport.jar

JSanRmiApiEx.jar

JSanRmiApiSx.jar

JSanRmiServerEx.jar

JSanRmiServerSx.jar

JSanRmiServerUx.jar

To delete the above directories and files, run a batch file. If your computer runs Windows, run

delWin.bat. If your computer runs UNIX, use delUnix.bat.

CAUTION: Do not run delWin.bat or delUnix.bat while obtaining monitoring data by

running Export Tool.

NOTE: If you change the svpip value in command.txt before running delWin.bat or

delUnix.bat, the directories and files created by Export Tool are not deleted. In this case,

delete them manually in the lib directory.

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” (page 79).

For a complete list of files to be saved by Export Tool, see “Using Export Tool” (page 51).

Using Export Tool 57

File formats

If you specify the nocompress operand for the option subcommand, Export Tool saves files
in CSV format instead of ZIP format (For detailed information, see “option” (page 79).) 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 Export Tool are often very large. The total file size can be as large as 2 GB.
Therefore, you might need a lot of time to complete the exporting process. If you want to export
statistics spanning a long period of time, you should run Export Tool multiple times for shorter
periods, rather than run 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-hour increments.

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

Table 1 Estimate of time required for exporting files

group subcommand

DescriptionEstimated timeOperand for the

5 minutesPort

5 minutesPortWWN

* 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” (page 65).

This estimate assumes that Export Tool is saving 24 hours of statistics
for 128 ports.*

This estimate assumes that Export Tool is saving 24 hours of statistics
for 128 ports.*

This estimate assumes that:60 minutesLDEV

• Export Tool is saving 24 hours of statistics for 8,192 volumes.*

• Export Tool is used eight times. Each time Export Tool is used, the

tool obtains statistics for a 3-hour period.

This estimate assumes that:60 minutesLU

• Export Tool is saving 24 hours of statistics for 12,288 LUs.*

• Export Tool is used eight times. Each time Export Tool is used, the

tool obtains statistics for a 3-hour period.

Termination code

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

• 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 runs and Export Tool returns the termination code 1 or 3, the command prompt displays
a message that indicates the set subcommand fails.

58 Exporting Performance Monitor data

Log files

java -classpath "./lib/JSanExportLoader.jar"

-Del.tool.Xmx=536870912 -Dmd.command=command.txt

-Dmd.logpath=log sanproject.getexptool.RJElMain<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 script, <CR+LF> indicates the end of a command line.

When Export Tool runs, it creates a log file on your computer. Therefore, if you run Export Tool
repeatedly, the size of free space on your computer will be reduced. To secure free space on
your computer, it is important that you delete log files regularly. For information about the directory
containing log files, see “Java” (page 82).

Export Tool returns a termination code when Export Tool finishes as listed in the following table:

Table 2 Termination codes returned by Export Tool

DescriptionTermination code

Export Tool finished successfully.0

1

3

4

101

Error handling

When an internal error occurs during export processing, an exclamation mark (!) indicates the
error. By default, 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” (page 62).

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

For more information, see “Troubleshooting Export Tool” (page 100).

An error occurred when the set subcommand (see “set” (page 80)) is run, 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:2

• 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. For example, an attempt to switch to
Modify mode failed when the set subcommand (see “set” (page 80)) is run. Some other
user might have been logged on in Modify mode.

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

An error occurred during the preparation process for running Export Tool. For details on
the error, see the displayed message and the table in “Messages issued by Export Tool”

(page 101).

Errors returned by Export Tool

DescriptionError message ID

An error occurred during the SVP processing.0001 4001

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

An administrator is changing a system environment file.0001 5508

Using Export Tool 59

DescriptionError message ID

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

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

Now processing.0002 6502

Another user has locked the file.0002 9000

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

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

An error occurred during the SVP processing.0003 3006

The storage system status is invalid.0405 8003

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

The SVP is updating the statistics data.5205 2033

The SVP is updating the statistics data.5305 2033

The storage system status is invalid.5305 8002

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 you should use in your batch file. “Subcommand list”

(page 61) lists and provides links to the subcommands explained in this section. The Java

command is explained in “Java” (page 82).

• “Export Tool command syntax” (page 60)

• “Subcommand list” (page 61)

Export Tool command syntax

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

• “Conventions” (page 60)

• “Syntax descriptions” (page 61)

• “Writing a script in the command file” (page 61)

• “Viewing the online help for subcommands” (page 61)

Conventions

italics

DescriptionConvention

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

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 you can omit.[ ]

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

{ }

60 Exporting Performance Monitor data

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

DescriptionConvention

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

|

Syntax descriptions

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

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

connect 123.01.22.33connect ip-address

destinationdestination [directory]

destination c:\temp

compresscompress [yes|no]

compress yes

compress no

answer yesanswer {yes|no}

answer no

portsports [name][...]

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 ;;;;
;;;;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
svpip 158.214.135.57 ; IP address of the SVP
login expusr "passwd" ; Log onto 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 Export Tool. For more information about how to use the help subcommand, see “help”

(page 81).

Subcommand list

FunctionSubcommand

Specifies the IP address of SVP to be logged in.“svpip” (page 62)

Makes settings on retries of export processing.“retry” (page 62)

Logs the specified user into SVP.“login” (page 63)

Export Tool command reference 61

FunctionSubcommand

svpip

“show” (page 64)

“shortrange” (page 74)

“longrange” (page 76)

“set” (page 80)

Description

Checks SVP to find the period of monitoring data stored in 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.“group” (page 65)

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

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

Specifies the directory in which files should be saved.“outpath” (page 78)

Specifies whether to save files in ZIP format or in CSV format.“option” (page 79)

Saves monitoring data in files.“apply” (page 80)

Starts or ends monitoring of the storage system, and specifies the sampling
interval in short-range monitoring.

Displays the online help for subcommands.“help” (page 81)

Starts Export Tool and writes monitoring data into files.“Java” (page 82)

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

Syntax

svpip {ip-address|host-name}

Operands

DescriptionOperand

Specifies the IP address of SVP.ip-address

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

Specifies the host name of SVP.host-name

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

Example

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

svpip 158.214.127.170

retry

Description

This subcommand makes settings on retries of export processing.
When an internal error occurs during export processing, Export Tool stops processing and then

retries export processing. By default, Export Tool can retry processing up to three times, but you
can change the maximum number of retries by using the retry subcommand.

62 Exporting Performance Monitor data

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 run before the login subcommand runs.

Syntax

retry [time=m] [count=n]

Operands

DescriptionOperand

login

time=m

Specifies the interval between retries in minutes, where m is a value within the range of 1 to

59.

If this operand is omitted, the interval between retries is two minutes.

Specifies the maximum number of retries.count=n

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.

svpip 158.214.135.57 retry time=5 count=10login expusr passwd

show group Portshort-range 201304010850:201304010910outpath
outoption compressapply

Description

This subcommand uses a user ID and a password to log the specified user in SVP.
The svpip subcommand must run before the login subcommand runs.

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

Syntax

login userid password

Operands

DescriptionOperand

Specifies the user ID for SVP.userid

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 is used exclusively with Export Tool. For detailed information,
see “Requirements for Export Tool” (page 50).

Specifies the password of the user.password

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 SVP whose IP address is 158.214.127.170. The password
is pswd.

Export Tool command reference 63

show

svpip 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 onto SVP (storing period).

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

Performance Monitor collects statistics by the two types of storing periods: in short range and in
long range. In short-range monitoring, the monitoring data between 1 day and 15 days is stored
in SVP, and in long-range monitoring the monitoring data up to 6 months is stored in SVP. For
details about the two storing periods, see “shortrange” (page 74) and “longrange” (page 76).

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

Figure 1 The monitoring term area

The login command must run before the show subcommand runs.

Syntax

show

Outputs

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

Short Range From: 2013/05/01 01:00 - To: 2013/05/01 15:00

Interval: 1min.

Long Range From: 2013/04/01 00:00 - To: 2013/05/01 15:00

Interval: 15min.

Short Range indicates the storing period and sampling interval of the monitoring data stored

in short range. Long Range indicates those of the monitoring data stored in long range. When
you run Export Tool, you can export the monitoring data within these periods into files. If you use
the shortrange or longrange subcommand additionally, you can narrow the term of data to
be exported (see “shortrange” (page 74) or “longrange” (page 76)).

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.

64 Exporting Performance Monitor data

group

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 3 (page 65) shows the monitoring data that can be saved into files by each operand, and

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

Table 3 Operands of the group subcommand and saved monitoring data

PhyPG

PhyLDEV

PhyExG

PhyExLDEV

PhyProc

PhyCMPK

GUI operationOperand

Select Parity Groups
from Object list in

Performance Objects
field in Monitor
Performance window.

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

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

Select Access Path
from Object list in

Performance Objects
field in Monitor
Performance window.

the file

Usage statistics about
parity groups

Usage statistics about
volumes

external volume groups

Usage conditions about
external volumes

Usage statistics about
MPs and data recovery
and reconstruction
processors

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

1

PhyLDEV_dat.ZIP

PhyExG_dat.ZIPUsage conditions about

PhyExLDEV_dat/PHY_ExLDEV_XXXXX.ZIP

2

PhyProc_dat.ZIP

PhyCMPK_dat.ZIP

1

1

1

SeeSaved ZIP fileMonitoring data saved in

Table 5 (page 85)PhyPG_dat.ZIP

PG

LDEV

LDEVEachOfCU

Port

Select Parity Group
from Object list in

Performance Objects
field in Monitor
Performance window.

Select Logical Device
from Object list in

Performance Objects
field in Monitor
Performance window.

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

Object list in
Performance Objects
field in Monitor
Performance window.

groups, external volume
groups

Statistics about volumes
in parity groups, in
external volume groups

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

Table 6 (page 87)PG_dat.ZIPStatistics about parity

3

Table 7 (page 88)LDEV_dat/LDEV_XXXXX.ZIP

3

Export Tool command reference 65

Table 8 (page 89)LDEVEachOfCU_dat/LDEV_XXXXX.ZIP

Table 9 (page 91)Port_dat.ZIPStatistics about portsSelect Fibre Port from

Table 3 Operands of the group subcommand and saved monitoring data (continued)

MFPort

PortWWN

LU

PPCGWWN

RemoteCopy

GUI operationOperand

the file

Object list in
Performance Objects
field in Monitor
Performance window.

Select WWN from
Object list in
Performance Objects

adapters connected to
ports

field in Monitor

Performance window.

Object list in
Performance Objects
field in Monitor
Performance window.

Select WWN from
Object list in

are connected to ports

Performance Objects
field in Monitor
Performance window.

Select Entire Storage
System Cnt Ac-S/Cnt

copy operations by
Continuous AccessAc-S MF/HA from
Synchronous andObject list in
Continuous AccessPerformance Objects
Synchronous MF andfield in Monitor

Performance window monitoring data by High

Availability (in complete
volumes)

SeeSaved ZIP fileMonitoring data saved in

MF_Port_dat.ZIPMainframe fibre portsSelect Fibre Port from

Table 10
(page 91)

PortWWN_dat.ZIPStatistics about host bus

Table 11
(page 92)

LU_dat.ZIPStatistics about LUsSelect LUN/Base from

Table 12
(page 92)

PPCGWWN_dat.ZIPAll host bus adapters that

Table 13
(page 93)

RemoteCopy_dat.ZIPStatistics about remote

Table 15
(page 94)

RCLU

RCLDEV

UniversalReplicator

URJNL

Select LUN Cnt
Ac-S/HA from Object

copy operations by
Continuous Accesslist in Performance
Synchronous andObjects field in
monitoring data by HighMonitor Performance

window Availability (for each

volume (LU))

Select Logical Device

Cnt Ac-S/Cnt Ac-S

Statistics about remote
copy operations by
Continuous AccessMF/HA from Object list
Synchronous andin Performance
Continuous AccessObjects field in
Synchronous MF andMonitor Performance

window monitoring data by High

Availability (for volumes
controlled by a particular
CU)

Select Entire Storage

System Cnt Ac-J/Cnt

copy operations by
Continuous AccessAc-J MF from Object
Journal and Continuouslist in Performance

Objects field in
Monitor Performance

Access Journal MF (for
entire volumes)

window

Select Journal from
Object list in

copy operations by
Continuous AccessPerformance Objects

RCLU_dat.ZIPStatistics about remote

RCLDEV_dat/RCLDEV_XXXXX.ZIP

UniversalReplicator.ZIPStatistics about remote

URJNL_dat.ZIPStatistics about remote

Table 16
(page 94)

4

Table 17
(page 95)

Table 18
(page 96)

Table 19
(page 97)

66 Exporting Performance Monitor data

Table 3 Operands of the group subcommand and saved monitoring data (continued)

GUI operationOperand

the file

field in Monitor
Performance window

URLU

URLDEV

PhyMPPK

Notes:

1. When you specify the PhyPG, PhyLDEV, PhyProc, or PhyCMPK operand, you can select the storing period of the
monitoring data to be exported from short range or long range. When you specify other operands, the monitoring
data in short range is exported.

2. A ZIP file name beginning with PhyExLDEV_.

3. A ZIP file name beginning with LDEV_.

4. A ZIP file name beginning with RCLDEV_.

5. A ZIP file name beginning with URLDEV_.

Select LUN from
Object list in

field in Monitor
Performance window

Select Logical Device

Cnt Ac-J/Cnt Ac-J MF
from Object list in

Performance window volumes controlled by a

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

Journal and Continuous
Access Journal MF (for
journals)

copy operations by
Continuous AccessPerformance Objects
Journal (for each volume
(LU))

Statistics about remote
copy operations by
Continuous Access
Journal and ContinuousPerformance Objects
Access Journal MF (forfield in Monitor

particular CU)

resource allocated to MP
blades

URLU_dat.ZIPStatistics about remote

URLDEV_dat/URLDEV_XXXXX.ZIP

5

PhyMPPK_dat.ZIPMP usage rate of each

SeeSaved ZIP fileMonitoring data saved in

Table 20
(page 98)

Table 21
(page 98)

Table 14
(page 93)

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 an operand is used more than one time in a command file, the last operand takes effect. In the
example below, the first group subcommand does not take effect, but the second group
subcommand takes effect:

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

Syntax

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

PhyLDEV [Short|Long] [parity-group-id]:[parity-group-id]][…]|
PhyExG [[exg-id]:[exg-id]][…]|
PhyExLDEV [exg-id]:[exg-id]][…]|
PhyProc [Short|Long]|

PhyCMPK [Short|Long]|

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

[parity-group-id|exg-id|Migration-Volume-group-id]][…]|
LDEV [[[parity-group-id|exg-id|Migration-Volume-group-id]:
[parity-group-id|exg-id|Migration-Volume-group-id]][.…]|

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

Export Tool command reference 67

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

Port [[port-name]:[port-name]][...]|
MFPort [[port-name]:[port-name]][...]|
PortWWN [port-name]:[port-name]][...]|
LU[[port-name.host-group-id]:[port-name.host-group-id]][…]|
PPCGWWN[[monitor-target-name:monitor-target-name]][…]|
RemoteCopy|
RCLU [[port-name.host-group-id]:[port-name.host-group-id]][…]|
RCLDEV[[LDKC-CU-id]:[LDKC-CU-id]][…]|
UniversalReplicator |
URJNL[[JNL-group-id]:[JNL-group-id]][…]|
URLU [[port-name.host-group-id]:[port-name.host-group-id]][…]|
URLDEVr[[LDKC-CU-id]:[LDKC-CU-id]][…]|

PhyMPPK

}

Operands

DescriptionOperand

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

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

Use this operand to export statistics about parity group usage rates, which are displayed in
the Monitor Performance window. When statistics are exported to a ZIP file, the file name will
be PhyPG_dat.ZIP. For details on the statistics exported by this operand, see Table 5

(page 85).

You can use the Short or Long option to select the storing period of the monitoring data to
be exported. If you specify Short, the exported file will contain statistics in a short range for
up to 15 days. If you specify Long, the exported file will contain statistics in a long range for
up to six months (for example, up to 186 days). If neither Short nor Long is specified, statistics
in both the short and long range are exported.

When you specify variable parity-group-id, you can narrow the range of parity groups
whose monitoring data are to be exported. parity-group-id is a parity group ID. The colon
(:) indicates a range. For example, 1-1:1-5 indicates parity groups from 1-1 to 1-5.

Ensure that the parity-group-id value on the left of the colon is smaller than the
parity-group-id value on the right of the colon. For example, you can specify

PhyPG 1-1:1-5, but you cannot specify PhyPG 1-5:1-1. Also, you can specify
PhyPG 1-5:2-1, but you cannot specify PhyPG 2-1:1-5.

If parity-group-id is not specified, the monitoring data of all 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 5 (page 85).

You can use the Short or Long option to select the storing period of the monitoring data to
be exported. If you specify Short, the exported file will contain statistics in short range for up
to 15 days. If you specify Long, the exported file will contain statistics in long range for up to
six months (for example, up to 186 days). If neither Short nor Long is specified, statistics in
both the short and long range are exported.

When you specify variable parity-group-id, you can narrow the range of parity groups
whose monitoring data are to be exported. parity-group-id is a parity group ID. The colon
(:) indicates a range. For example, 1-1:1-5 indicates parity groups from 1-1 to 1-5.

Ensure that the parity-group-id value on the left of the colon is smaller than the
parity-group-id value on the right of the colon. For example, you can specify

PhyLDEV 1-1:1-5, but you cannot specify PhyLDEV 1-5:1-1. Also, you can specify
PhyLDEV 1-5:2-1, but you cannot specify PhyLDEV 2-1:1-5.

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

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

68 Exporting Performance Monitor data

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

DescriptionOperand

file name will be PhyExG_dat.ZIP. For details on the statistics exported by this operand,
see Table 5 (page 85).

When you specify variable exg-id, you can narrow the range of external volume groups
whose monitoring data are to be exported. exg-id is an ID of an external volume group. The
colon (:) indicates a range. For example, E1-1:E1-5 indicates external volume groups from
E1-1 to E1-5.

Ensure that the exg-id value on the left of the colon is smaller than the exg-id value on
the right of the colon. For example, you can specify PhyExG E1-1:E1-5, but you cannot
specify PhyExG E1-5:E1-1. Also, you can specify PhyExG E1-5:E2-1, but you cannot
specify PhyExG E2-1:E1-5.

If exg-id is not specified, the monitoring data of all external volume groups will be exported.

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

PhyProc[Short|Long]

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 5 (page 85).

When you specify variable 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.

Use this operand when you want to export the following statistics, which are displayed in the
Monitor Performance window:

• Usage rates of MPs

• Usage rates of DRRs (data recovery and reconstruction processors)

When statistics are exported to a ZIP file, the file name will be PhyProc_dat.ZIP. For details
on the statistics exported by this operand, see Table 5 (page 85).

You can use the Short or Long option to select the storing period of the monitoring data to
be exported. If you specify Short, the exported file will contain statistics in short range for up
to 15 days. If you specify Long, the exported file will contain statistics in long range for up to
six months (for example, up to 186 days). If neither Short nor Long is specified, statistics in
both the short and long range are exported.

PhyCMPK[Short|Long]

Use this operand when you want to export the following statistics, which are displayed in the
Monitor Performance window:

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

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

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

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

• Usage rates of cache memories

• Size of the allocated cache memories

When statistics are exported to a ZIP file, the file name will be PhyCMPK_dat.ZIP. For details
on the statistics exported by this operand, see Table 5 (page 85).

You can use the Short or Long option to select the storing period of the monitoring data to
be exported. If you specify Short, the exported file will contain statistics in short range for up
to 15 days. If you specify Long, the exported file will contain statistics in long range for up to
six months (for example, up to 186 days). If neither Short nor Long is specified, statistics in
both the short and long range are exported.

Export Tool command reference 69

DescriptionOperand

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

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

Use this operand when you want to export statistics about parity groups, external volume
groups, or migration volume groups which are displayed in the Monitor Performance window.
When statistics are exported to a ZIP file, the file name will be PG_dat.ZIP. For details on
the statistics exported by this operand, see Table 5 (page 85).

When you specify variables parity-group-id, exg-id, or Migration-Volume-group-id
you can narrow the range of parity groups, external volume groups, or migration volume groups
whose monitoring data are to be exported. parity-group-id is a parity group ID. exg-id
is an ID of an external volume group. Migration-Volume-group-id is a migration volume
group ID. 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. M1-1:M5-1 indicates
migration volume groups from M1-1 to M5-1.

Ensure that the parity-group-id, exg-id, or Migration-Volume-group-id value on
the left of the colon is smaller than the parity-group-id, exg-id, or
Migration-Volume-group-id value on the right of the colon. For example, you can specify
PG 1-1:1-5, but you cannot specify PG 1-5:1-1. Also, you can specify PG 1-5:2-1, but
you cannot specify PG 2-1:1-5.

If none of parity-group-id, exg-id, or Migration-Volume-group-id are specified,
the statistics of all parity groups, external volume groups, and migration volume groups will
be exported.

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 9 (page 91).

When you specify variables parity-group-id, exg-id, or Migration-Volume-group-id
you can narrow the range of parity groups, external volume groups, or migration volume groups
whose monitoring data are to be exported. parity-group-id is a parity group ID. exg-id
is an ID of an external volume group. Migration-volume-group-id is a migration volume
group ID. 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. M1-1:M5-1 indicates
migration volume groups from M1-1 to M5-1.

Ensure that the parity-group-id, exg-id, or Migration-Volume-group-id value on
the left of the colon is smaller than the parity-group-id, exg-id, or
Migration-Volume-group-id value on the right of the colon. For example, you can specify

LDEV 1-1:1-5, but you cannot specify LDEV 1-5:1-1. Also, you can specify
LDEV 1-5:2-1, but you cannot specify LDEV 2-1:1-5.

If internal is specified, you can export statistics about volumes in the parity group. If virtual is
specified, you can export statistics about volumes in the external volume group or migration
volume group.

If none of parity-group-id, exg-id, or Migration-Volume-group-id are specified,
the statistics of all parity groups, external volume groups, and migration volume groups will
be exported.

One of the following values can be specified:

• parity-group-id, exg-id, or Migration-Volume-group-id

• internal

• virtual

LDEVEachOfCU[[[LDKC-CU-id]:[LDKC-CU-id]][…]|
internal|virtual]

70 Exporting Performance Monitor data

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 about
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 8 (page 89).

When you specify variable 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.

DescriptionOperand

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.

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

MFPort
[[port-name]:[port-name]][…]

Use this operand when you want to export port statistics, which are displayed in the Monitor
Performance window. When statistics are exported in a ZIP file, the file name will be
Port_dat.ZIP. For details on the statistics exported by this operand, see Table 9 (page 91).

When you specify variable port-name, you can specify a range of ports for which data is
saved using the format port-name:port-name. For example, CL3-a:CL3-c indicates
ports from CL3-a to CL3-c.

Ensure that the port-name value on the left of the colon is smaller than the port-name
value on the right of the colon. The smallest port-name value is CL1-A and the largest
port-name value is CL4-r. The following formula illustrates which value is smaller than which
value:

CL1-A < CL1-B < … < CL2-A < CL2-B < … < CL3-a < CL3-b < … < CL4-a < … < CL4-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 save monitoring data for mainframe fibre ports displayed
on the Performance Monitor window. When statistics are exported to a ZIP file, the file name
is MF_Port_dat.ZIP. For details on the statistics exported by this operand, see Table 10

(page 91).

When you specify variable port-name, you can narrow a range of ports for which data is
saved using the format port-name:port-name. For example, CL1-C.01:CL1-C.03
indicates the range from host group #01 of port CL1-C to host group #03 of port CL1-C.

Ensure that the value on the left of the colon is smaller than the value on the right of the colon.
The smallest port-name value is CL1-A and the largest port-name value is CL4-r. The
following formula illustrates which port-name value is smaller than which port-name value:

CL1-A < CL1-B < … < CL2-A < CL2-B < … < CL3-a < CL3-b < … < CL4-a < …<CL4-r

For example, you can specify CL1-C:CL2-A, but you cannot specify CL2-A:CL1-C. Also, you
can specify CL3-a:CL3-c, but you cannot specify CL3-c:CL3-a. If port-name is not specified,
the monitoring data of all volumes is exported.

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

Use this operand when you want to export statistics about host bus adapters (WWNs) connected
to ports, which are displayed in the Monitor Performance window. When statistics are exported
in a ZIP file, the file name will be PortWWN_dat.ZIP. For details on the statistics exported
by this operand, see Table 9 (page 91).

When you specify variable port-name, you can narrow a range of ports for which data is
saved using the format port-name:port-name. For example, CL3-a:CL3-c indicates ports
from CL3-a to CL3-c.

Ensure that the port-name value on the left of the colon is smaller than the port-name
value on the right of the colon. The smallest port-name value is CL1-A and the largest
port-name value is CL4-r. The following formula illustrates which value is smaller than which
value:

CL1-A < CL1-B < … < CL2-A < CL2-B < … < CL3-a < CL3-b < … < CL4-a < … < CL4-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 CL3-a: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.

Export Tool command reference 71

DescriptionOperand

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

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

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 12 (page 92).

When you specify variable port-name.host-group-id, you can narrow the range of LU
paths whose monitoring data are to be exported. port-name is a port name. host-group-id
is the ID of a host group (that is, a host storage domain). The host group (host storage domain)
ID must be a hexadecimal numeral. The colon (:) indicates a range. For example,
CL1-C.01:CL1-C.03 indicates the range from the host group #01 of the CL1-C port to the
host group #03 of the CL1-C port.

Ensure that the value on the left of the colon is smaller than the value on the right of the colon.
The smallest port-name value is CL1-A and the largest port-name value is CL4-r. The
following formula illustrates which port-name value is smaller than which port-name value:

CL1-A < CL1-B < … < CL2-A < CL2-B < … < CL3-a < CL3-b < … < CL4-a < … < CL4-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.

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 13 (page 93).

When you specify variable 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 PFC 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

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

72 Exporting Performance Monitor data

Use this operand when you want to export statistics about remote copy operations of Continuous
Access Synchronous, Continuous Access Synchronous MF, and High Availability. By using
this operand, you can export monitoring data about remote copy operations performed by Cnt
Ac-S, Cnt Ac-S MF, and HA 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 15 (page 94).

Use this operand when you want to export statistics about remote copy operations of Continuous
Access Synchronous and High Availability. By using this operand, you can export monitoring
data about remote copy operations performed by Cnt Ac-S and HA 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 16 (page 94).

When you specify variable port-name.host-group-id, you can narrow the range of LU
paths whose monitoring data are to be exported, where port-name is a port name and
host-group-id is the ID of a host group. The host group ID must be a hexadecimal numeral.
The colon (:) indicates a range. For example, CL1-C.01:CL1-C.03 indicates the range from
the host group #01 of the CL1-C port to the host group #03 of the CL1-C port.

Ensure that the value on the left of the colon is smaller than the value on the right of the colon.
The smallest port-name value is CL1-A and the largest port-name value is CL4-r. The
following formula illustrates which port-name value is smaller than which port-name value:

CL1-A < CL1-B < … < CL2-A < CL2-B < … < CL3-a < CL3-b < … < CL4-a < … < CL4-r

DescriptionOperand

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[[LDKC-CU-id]:[LDKC-CU-id]][…]|

UniversalReplicator

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

Use this operand when you want to export statistics about remote copy operations of Continuous
Access Synchronous, Continuous Access Synchronous MF, and High Availability. By using
this operand, you can export monitoring data about remote copy operations performed by Cnt
Ac-S, Cnt Ac-S MF, and HA 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 17 (page 95).

When you specify variable 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 an LDKC:CU.
The colon (:) indicates a range. For example, 000:105 indicates LDKC:CUs from 00:00 to
01:05.

Ensure that the LDKC-CU-id value on the left of the colon is smaller than the LDKC-CU-id
value on the right of the colon. For example, you can specify RCLDEV 000:105, but you
cannot specify RCLDEV 105:000.

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

Use this operand when you want to export statistics about remote copy operations of Cnt Ac-J
and Cnt Ac-J MF. By using this operand, you can export monitoring data about remote copy
operations performed by Continuous Access Journal and Continuous Access Journal MF 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 18 (page 96).

Use this operand when you want to export statistics about remote copy operations of Cnt Ac-J
and Cnt Ac-J MF. By using this operand, you can export monitoring data about remote copy
operations performed by Continuous Access Journal and Continuous Access Journal MF 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 19 (page 97).

When you specify variable 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]][…]

Use this operand when you want to export statistics about remote copy operations of Cnt Ac-J.
By using this operand, you can export monitoring data about Cnt Ac-J remote copy operations
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 20 (page 98).

When you specify variable port-name.host-group-id, you can narrow the range of LU
paths whose monitoring data are to be exported, where port-name is a port name and
host-group-id is the ID of a host group. The host group ID must be a hexadecimal numeral.
The colon (:) indicates a range. For example, CL1-C.01:CL1-C.03 indicates the range from
the host group #01 of the CL1-C port to the host group #03 of the CL1-C port.

Ensure that the value on the left of the colon is smaller than the value on the right of the colon.
The smallest port-name value is CL1-A and the largest port-name value is CL4-r. The
following formula illustrates which port-name value is smaller than which port-name value:

CL1-A < CL1-B < … < CL2-A < CL2-B < … < CL3-a < CL3-b < … < CL4-a < … < CL4-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.

Export Tool command reference 73

DescriptionOperand

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

PhyMPPK

Use this operand when you want to export statistics about remote copy operations which of
Cnt Ac-J and Cnt Ac-J MF. By using this operand, you can export monitoring data about remote
copy operations performed by Continuous Access Journal and Continuous Access Journal
MF 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 21 (page 98).

When you specify variable 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 an LDKC:CU.
The colon (:) indicates a range. For example, 000:105 indicates LDKC:CUs from 00:00 to
01:05.

Ensure that the LDKC-CU-id value on the left of the colon is smaller than the LDKC-CU-id
value on the right of the colon. For example, you can specify URLDEV 000:105, but you
cannot specify URLDEV 105:000.

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

Use this operand when you want to export statistics about MP usage rate of each resource
allocated to MP blades in short range. 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 14

(page 93).

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

shortrange

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 shortrange subcommand is valid for monitoring data in short range. Short-range monitoring
data appears in the Monitor Performance window when Short-Range is selected as the storing
period.

74 Exporting Performance Monitor data

All the monitoring items are stored in short range. Therefore, you can use the shortrange
subcommand whichever operand you specify to the group subcommand. If you run Export Tool
without specifying the shortrange subcommand, the data stored in the whole monitoring term
will be exported.

The login subcommand must run before the shortrange subcommand runs.

Syntax

shortrange [[yyyyMMddhhmm][{+|-}hhmm]:[yyyyMMddhhmm][{+|-}hhmm]]

Operands

The value on the left of the colon (:) specifies the starting time of the period. The value on the
right of the colon specifies the ending time of the period. Specify the term within "Short Range
From XXX To XXX" which is output by the show subcommand.

If no value is specified on the left of the colon, the starting time for collecting monitoring data is
assumed. If no value is specified on the right of the colon, the ending time for collecting monitoring
data is assumed. The starting and ending times for collecting monitoring data are displayed in
the Monitoring Term area in the Monitor Performance window.

Figure 2 Starting and Ending Time for Collecting Monitoring Data

+hhmm

-hhmm

DescriptionOperand

yyyyMMdd indicates the year, the month, and the day. hhmm indicates the hour and the minute.yyyyMMddhhmm

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 digits of the time on the left or right of the colon (:) are not a multiple of the
sampling interval, the time will automatically be changed so that the last two digits is a multiple
of the sampling interval. If this change occurs to the time on the left of the colon, the time will

Export Tool command reference 75

DescriptionOperand

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 are not
a multiple of 10 minutes. The time on the right will remain unchanged because the last two
digits of the time are 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 are not
a multiple of 7 minutes. The time on the right will be changed to 20:35 because of the same
reason.

Examples

The examples below assume that the:

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

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

shortrange
201301010930:201301011730

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

shortrange 201301010930: Export Tool saves monitoring data within the range of Jan.

1, 9:30 to Jan. 2, 00:00.

shortrange:201301011730 Export Tool saves monitoring data within the range of Jan.

1, 0:00-17:30.

shortrange +0001: Export Tool saves monitoring data within the range of Jan.

1, 0:01 to Jan. 2, 00:00.

shortrange -0001: Export Tool saves monitoring data within the range of Jan.

1, 23:59 to Jan. 2, 00:00.

shortrange:+0001 Export Tool saves monitoring data within the range of Jan.

1, 0:00-00:01.

shortrange:-0001 Export Tool saves monitoring data within the range of Jan.

1, 0:00-23:59.

shortrange +0101:-0101 Export Tool saves monitoring data within the range of Jan.

1, 1:01-22:59.

shortrange
201301010900+0130:201301011700-0130

shortrange
201301010900-0130:201301011700+0130

shortrange
201301010900-0130:

Export Tool saves monitoring data within the range of Jan.
1, 10:30-15:30.

Export Tool saves monitoring data within the range of Jan.
1, 7:30-18:30.

Export Tool saves monitoring data within the range of Jan.
1, 7:30 to Jan. 2, 00:00.

longrange

Description

The longrange subcommand is used to specify a monitoring term (time range) for collecting
monitoring data to be exported into files. Use this subcommand when you want to narrow the
export-target term within the stored data.

76 Exporting Performance Monitor data

The longrange subcommand is valid for monitoring data in long range. The monitoring data in
long range is the contents displayed on the Physical tab of the Performance Management window
with selecting longrange as the storing period.

The monitoring items whose data can be stored in long range are limited. The following table
shows the monitoring items to which the longrange subcommand can be applied, and also
shows the operands to export those monitoring items.

Operands of the group subcommandMonitoring Data

PhyPG LongUsage statistics about parity groups

PhyLDEV LongUsage statistics about volumes

PhyProc LongUsage statistics about MPs and data recovery and reconstruction

processors

PhyCMPK LongUsage statistics about access paths and write pending rate

If you run Export Tool without specifying the longrange subcommand, the data stored in the
whole monitoring term will be exported.

The login subcommand must run before the longrange subcommand runs.

Syntax

longrange [[yyyyMMddhhmm][{+|-}ddhhmm]:[yyyyMMddhhmm][{+|-}ddhhmm]]

Operands

The value on the left of the colon (:) specifies the starting time of the period. The value on the
right of the colon specifies the ending time of the period. Specify the term within "Long Range
From XXX To XXX" which is output by the show subcommand.

If no value is specified on the left of the colon, the starting time for collecting monitoring data is
assumed. If no value is specified on the right of the colon, the ending time for collecting monitoring
data is assumed. The starting and ending times for collecting monitoring data are displayed in
the Monitoring Term area in the Monitor Performance window.

Figure 3 Starting and Ending Time for Collecting Monitoring Data

DescriptionOperand

yyyyMMddhhmm

yyyyMMdd indicates the year, the month, and the day. hhmm indicates the hour and the

minute.

If yyyyMMddhhmm is omitted on the left of the colon, the starting time for collecting monitoring
data is assumed. If yyyyMMddhhmm is omitted on the right of the colon, the ending time for
collecting monitoring data is assumed.

+ddhhmm

Adds time (ddhhmm) to yyyyMMddhhmm if yyyyMMddhhmm is specified. For example,

201301120000+010130 indicates Jan. 13, 2013. 01:30.

Export Tool command reference 77

DescriptionOperand

Adds time to the starting time for collecting monitoring data, if yyyyMMddhhmm is omitted.

-ddhhmm

Subtracts time (ddhhmm) from yyyyMMddhhmm if yyyyMMddhhmm is specified. For example,

201301120000-010130 indicates Jan. 10, 2013. 22:30.

Subtracts time from the ending time for collecting monitoring data, if yyyyMMddhhmm is
omitted.

Ensure that mm is 00, 15, 30, or 45. If you do not specify mm in this way, the value on the left
of the colon (:) will be rounded down to one of the four values. Also, the value on the right
of the colon will be rounded up to one of the four values. For example, if you specify

201301010013:201301010048, the specified value is regarded as
201301010000:201301010100.

Examples

The examples below 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.

longrange
201301010930:201301011730

longrange 201301010930: Export Tool saves monitoring data within the range of Jan.

longrange:201301011730 Export Tool saves monitoring data within the range of Jan.

longrange +000015: Export Tool saves monitoring data within the range of Jan.

longrange -000015: Export Tool saves monitoring data within the range of Jan.

longrange:+000015 Export Tool saves monitoring data within the range of Jan.

longrange:-000015 Export Tool saves monitoring data within the range of Jan.

longrange +000115:-000115 Export Tool saves monitoring data within the range of Jan.

longrange
201301010900+000130:201301011700-000130

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

1, 9:30 to Jan. 2, 00:00.

1, 0:00-17:30.

1, 0:15 to Jan. 2, 00:00.

1, 23:45 to Jan. 2, 00:00.

1, 0:00-00:15.

1, 0:00-23:45.

1, 1:15-22:45.
Export Tool saves monitoring data within the range of Jan.

1, 10:30-15:30.

longrange
201301010900-000130:201301011700+000130

longrange
201301010900-000130:

outpath

Description

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

Syntax

outpath [path]

78 Exporting Performance Monitor data

Export Tool saves monitoring data within the range of Jan.
1, 7:30-18:30.

Export Tool saves monitoring data within the range of Jan.
1, 7:30 to Jan. 2, 00:00.

option

Operands

DescriptionOperand

Specifies the directory in which files will be saved.path

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

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

DescriptionOperand

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

compress

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

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

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

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

Overwrites existing files and directories.noclear

Example

The following example saves monitoring data in CSV files, not in ZIP files:

option nocompress

Export Tool command reference 79

apply

set

Description

The apply subcommand saves monitoring data specified by the group subcommand into files.

The login subcommand must run before the apply subcommand runs.

The apply subcommand does nothing if the group subcommand runs.

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, starting or
ending the collection of performance statistics). The set subcommand also specifies the sampling
interval (interval of collecting statistics) in short range monitoring.

If you want to use the set subcommand, you must use the login subcommand (see “login”

(page 63) to log on to SVP). Ensure that the set subcommand runs immediately before Export

Tool finishes.
Executing the set subcommand generates an error in the following conditions:

• Some other user is being logged onto SVP in Modify mode.

• Maintenance operations are being performed at SVP.

If an error occurs, do the following:

• Ensure that all users who are logged onto SVP are not in Modify mode. If any user is logged
on in Modify mode, ask the user to switch to View mode.

• Wait until maintenance operations finish at SVP, so that the set subcommand can run.

NOTE: Following are notes of the set command.

◦ Batch files can include script that will run when an error occurs. For information about

writing such a script in your batch file, see Notes in “Running Export Tool” (page 56).

◦ 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 do 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 Remote Web Console main
window.

◦ If you change the specified sampling interval during a monitoring, the previously collected

monitoring data will be deleted.

Syntax

set [switch={m|off}]

80 Exporting Performance Monitor data

Operands

DescriptionOperand

help

switch={m|off}

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 in short
range monitoring by Performance Monitor. The sampling interval in long range is fixed to 15
minutes.

To end monitoring, specify off.

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

Examples

The following command file saves port statistics and then ends monitoring ports:

svpip 158.214.135.57 login expusr passwd show group Portshort

-range 201304010850:201304010910
applyset switch=off

The following command file starts monitoring remote copy operations. The sampling time interval
is 10 minutes:

svpip 158.214.135.57 login expusr passwd set switch=10

Description

The help subcommand displays the online help for subcommands.

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

Syntax

help

Example

In this example, a command file (cmdHelp.txt) and a batch file (runHelp.bat) are created in the
C:\export directory on a Windows computer:

• Command file (c:\export\cmdHelp.txt):

help

• Batch file (c:\export\runHelp.bat):

java -classpath "./lib/JSanExportLoader.jar"

-Del.tool.Xmx=536870912 -Dmd.command=cmdHelp.txt

-Dmd.logpath=log sanproject.getexptool.RJElMain<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.

Export Tool command reference 81

Java

Description

This command starts Export Tool and exports monitoring data into files. To start Export Tool,
write this Java command in your batch file and then run the batch file.

Syntax

Java -classpath class-pathrproperty-parameters
sanproject.getexptool.RJElMain

Operands

DescriptionOperand

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

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

You can specify the following parameters. At minimum you must specify -Dmd.command.property-parameters

• -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 Export Tool communicates with SVP through a
proxy host.

• -Dhttp.proxyPort=port-number-of-proxy-host

Specifies the port number of a proxy host. You must specify this parameter if the
computer that runs Export Tool communicates with SVP through a proxy host.

• -Del.tool.Xmx=VM-heap-size-when-ExportTool-starts

Specifies the size of memory to be used by JRE when Export Tool is being run. You
must specify this parameter. The memory size must be 536870912, as shown in the
Example below. If an installed memory size is smaller than the recommended size of
the PC running Remote Web Console, you must install more memory before executing
Export Tool.

If an installed memory size is larger than the recommended memory size of the PC
running Remote Web Console, 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 Export Tool runs.

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 Export Tool runs. For example, the log file
export0101091010.log contains log information about the Export Tool execution at Jan.
1, 09:10:10.

82 Exporting Performance Monitor data

DescriptionOperand

• -Dmd.rmitimeout=timeout(min.)

Specifies the timeout value for communication between Export Tool and the SVP:

◦ Default: 20 minutes

◦ Minimum: 1 minute

◦ Maximum: 1,440 minutes (24 hours)

If a request does not come from Export Tool within the timeout period, the SVP
determines that execution has stopped and disconnects the session with Export Tool.
Therefore, if the machine on which 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.

• -Del.logpath=log-output-directory-name

Specify the directory to store the log file generated when Export Tool was downloaded.
By default, the current directory is set. The initial value for the startup batch file is log.

• -Del.logfile=log-file-name

Specify the name of the log file generated when Export Tool was downloaded. By
default, loaderMMddHHmmss.log is set. MM is the month, dd is the date, and HH is
the hour, mm is minutes, and ss is seconds. When the default name is used, a new log
file is created every time you run Export Tool. As a result, you need to delete log files
regularly. The initial value for the startup batch file is not specified.

• -Del.mode=startup-mode-of-Export-Tool (all/delete)

Specify the startup mode of Export Tool. The following shows startup modes and their
behavior.

◦ Mode: all

Download Export Tool: Yes

Run Export Tool: Yes

Delete temporary directories in the lib directory: Yes

◦ Mode: delete

Download Export Tool: no

Run Export Tool: no

Delete temporary directories in the lib directory: Yes

Examples

The following example assumes that the computer running Export Tool communicates with 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/JSanExportLoader.jar"

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

-Dmd.command=command.txt

-Dmd.rmitimeout=20

-Dmd.logpath=log sanproject.getexptool.RJElMain <CR+LF>

In the following example, a log file named export.log will be created in the log directory below
the current directory when Export Tool runs:

java -classpath "./lib/JSanExportLoader.jar"

-Del.tool.Xmx=536870912 -Dmd.command=command.txt -Dmd.logfile=export.log

-Dmd.logpath=log sanproject.getexptool.RJElMain<CR+LF>

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

Export Tool command reference 83

Exported files

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.

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 Export Tool to save monitoring data in CSV files instead
of ZIP files.

Monitoring data exported by Export Tool

The following table shows the correspondence between the Performance Management windows
and the monitoring data that can be exported by 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 and 15 minutes for Short Range and Long Range, respectively, that can be set
in the Edit Monitoring Switch window.

Table 4 Performance management windows and monitoring data saved by Export Tool

Monitoring dataGUI operation

“Resource usage and write-pending rate statistics” (page 85)Select Parity Groups from Object list in Performance

Objects field in Monitor Performance window.

“Parity group and external volume group statistics” (page 87)

Performance Objects field in Monitor Performance
window.

Select Logical Devices (Cnt Ac-S/Cnt Ac-S MF/HA) from

Object list in Performance Objects field in Monitor
Performance window.

Select Logical Devices (Cnt Ac-J/Cnt Ac-J MF) from
Object list in Performance Objects field in Monitor
Performance window.

Objects field in Monitor Performance window.

in Monitor Performance window.

field in Monitor Performance window.

field in Monitor Performance window.

Performance Objects field in Monitor Performance
window.

“Resource usage and write-pending rate statistics” (page 85)Select Logical Devices (Base) from Object list in

“Statistics for volumes in parity/external volume groups” (page 88)

“Volumes in parity groups or external volume groups (at volumes
controlled by a particular CU)” (page 89)

“Remote copy by Cnt Ac-S/Cnt Ac-S MF and monitoring data by
HA (volumes controlled by a particular CU)” (page 95)

“Remote copy by Cnt Ac-J and Cnt Ac-J MF (at volumes controlled
by a particular CU)” (page 98)

“Resource usage and write-pending rate statistics” (page 85)Select Access Path from Object list in Performance

“Resource usage and write-pending rate statistics” (page 85)Select Cache from Object list in Performance Objects field

“Resource usage and write-pending rate statistics” (page 85)Select Controller from Object list in Performance Objects

“MP blades” (page 93)

“Port statistics” (page 91)Select Fibre Port from Object list in Performance Objects

“Port statistics” (page 91)Select Mainframe Fibre Port from Object list in

field in Monitor Performance window.

Select LUN (Cnt Ac-S/HA) from Object list in Performance
Objects field in Monitor Performance window.

84 Exporting Performance Monitor data

“Volumes (LU) statistics” (page 92)Select LUN Base from Object list in Performance Objects

“Remote copy operations by Cnt Ac-S and monitoring data by
HA (for each volume (LU))” (page 94)

Table 4 Performance management windows and monitoring data saved by Export Tool (continued)

Monitoring dataGUI operation

“Remote copy by Cnt Ac-J (for each volume (LU))” (page 97)Select LUN (Cnt Ac-J/Cnt Ac-J MF) from Object list in

Performance Objects field in Monitor Performance

window.

“Host bus adapters connected to ports statistics” (page 92)Select WWN from Object list in Performance Objects field

in Monitor Performance window.

“All host bus adapters connected to ports” (page 93)

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

Select Entire Storage System (Cnt Ac-S/Cnt Ac-S MF/HA)
from Object list in Performance Objects field in Monitor
Performance window.

Select Entire Storage System (Cnt Ac-J/Cnt Ac-J MF)
from Object list in Performance Objects field in Monitor
Performance window.

“Remote copy by Cnt Ac-J and Cnt Ac-J MF (at journals)”
(page 97)

“Remote copy operations by Cnt Ac-S/Cnt Ac-S MF and
monitoring data by HA (whole volumes)” (page 94)

“Remote copy by Cnt Ac-J and Cnt Ac-J MF (whole volumes)”
(page 96)

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 Export Tool. These files contain statistics about resource
usage and write pending rates.

Table 5 Files with resource usage and write pending rate statistics

Data saved in the fileCSV fileZIP file

Usage rates for parity groups in long rangePHY_Long_PG.csvPhyPG_dat.ZIP

Usage rates for parity groups in short rangePHY_Short_PG.csv

Usage rates for volumes in a parity group in long rangePHY_Long_LDEV_x-y.csvPhyLDEV_dat.ZIP

Usage rates for volumes in a parity group in short rangePHY_Short_LDEV_x-y.csv

PHY_Short_LDEV_SI_x-y.csv

PHY_ExG_Response.csvPhyExG_dat.ZIP

PHY_ExG_Trans.csv

PHY_ExG_Read_Response.csv

PHY_ExG_Write_Response.csv

PHY_ExG_Read_Trans.csv

Usage rates for Business Copy and Business Copy MF
volumes in a parity group in short range

If external storage volumes are mapped to the volume
groups of the XP7 Storage system, this file includes the
average response time for the volume groups including
external storage volumes (milliseconds).

If external storage volumes are mapped to the volume
groups of the XP7 Storage system, this file includes the
amount of transferred data for volume groups including
external storage volumes (Kbps).

If external storage volumes are mapped to the volume
groups of the XP7 Storage system, this file includes the
average read response time for the volume groups
including external storage volumes (milliseconds).

If external storage volumes are mapped to the volume
groups of the XP7 Storage system, this file includes the
average write response time for the volume groups
including external storage volumes (milliseconds).

If external storage volumes are mapped to the volume
groups of the XP7 Storage system, this file includes the
amount of read transferred data for volume groups
including external storage volumes (Kbps).

Exported files 85

Table 5 Files with resource usage and write pending rate statistics (continued)

Data saved in the fileCSV fileZIP file

PHY_ExG_Write_Trans.csv

PHY_ExLDEV_Response_x-y.csvPhyExLDEV_dat/PHY_ExLDEV_Response.ZIP

PHY_ExLDEV_Trans_x-y.csvPhyExLDEV_dat/PHY_ExLDEV_Trans.ZIP

PHY_ExLDEV_Read_Response_x-y.csvPhyExLDEV_dat/PHY_ExLDEV_Read_Response.ZIP

PHY_ExLDEV_Write_Response_x-y.csvPhyExLDEV_dat/PHY_ExLDEV_Write_Response.ZIP

PHY_ExLDEV_Read_Trans_x-y.csvPhyExLDEV_dat/PHY_ExLDEV_Read_Trans.ZIP

If external storage volumes are mapped to the volume
groups of the XP7 Storage system, this file includes the
amount of write transferred data for volume groups
including external storage volumes (Kbps).

If external storage volumes are mapped to the volume
groups of the XP7 Storage system, this file includes the
average response time for external storage volumes in
the volume group x-y (milliseconds).

If external storage volumes are mapped to the volume
groups of the XP7 Storage system, this file includes the
amount of data transferred for external storage volumes
in the volume group x-y (Kbps).

If external storage volumes are mapped to the volume
groups of the XP7 Storage system, this file includes the
average reading response time for external storage
volumes in the volume group x-y (milliseconds).

If external storage volumes are mapped to the volume
groups of the XP7 Storage system, this file includes the
average writing response time for external storage
volumes in the volume group x-y (milliseconds).

If external storage volumes are mapped to the volume
groups of the XP7 Storage system, this file includes the
amount of reading data transferred for external storage
volumes in the volume group x-y (Kbps).

PHY_ExLDEV_Write_Trans_x-y.csvPhyExLDEV_dat/PHY_ExLDEV_Write_Trans.ZIP

PHY_Long_DRR.csv

PHY_Short_DRR.csv

PHY_Long_CHA_CMPK.csvPhyCMPK_dat.ZIP

PHY_Short_CHA_CMPK.csv

PHY_Short_DKA_CMPK.csv

PHY_Long_MPPCB_CMPK.csv

PHY_Short_MPPCB_CMPK.csv

If external storage volumes are mapped to the volume
groups of the XP7 Storage system, this file includes the
amount of writing data transferred for external storage
volumes in the volume group x-y (Kbps).

Usage rates for MPs in long rangePHY_Long_MP.csvPhyProc_dat.ZIP

Usage rates for MPs in short rangePHY_Short_MP.csv

Usage rates for DRRs (data recovery and reconstruction
processors) in long range

Usage rates for DRRs (data recovery and reconstruction
processors) in short range

Usage rates for access paths between channel adapters
and CM packages in long range

Usage rates for CM packages in long rangePHY_Long_DKA_CMPK.csv

Usage rates for access paths between channel adapters
and CM packages in short range

Usage rates for access paths between disk adapters
and CM packages in short range

Usage rates for access paths between MP blades and
CM packages in long range

Usage rates for access paths between MP blades and
CM packages in short range

86 Exporting Performance Monitor data

Cache usage rates within CM packages in long rangePHY_Long_CMPK_Cache.csv

Cache usage rates within CM packages in short rangePHY_Short_CMPK_Cache.csv

Write pending rates in long range in the entire systemPHY_Long_Write_Pending_Rate.csv

Table 5 Files with resource usage and write pending rate statistics (continued)

Data saved in the fileCSV fileZIP file

Write pending rates in short range in the entire systemPHY_Short_Write_Pending_Rate.csv

Usage rates for cache memory in each the entire systemPHY_Short_Cache_Usage_Rate.csv

Write pending rates in long range in each MP bladePHY_Long_Write_Pending_Rate_z.csv

Write pending rates in short range in each MP bladePHY_Short_Write_Pending_Rate_z.csv

Usage rates for cache memory in each MP bladePHY_Short_Cache_Usage_Rate_z.csv

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

• Both long range and short range statistics are stored for resource usage and write pending rates.

• You can select Long-Range or Short-Range from Data Range field in the Monitor Performance window

The allocated size of the cache memory in each MP
blade (MB)

This value does not correspond with the total capacity
of cache because the value is same as the allocated
size of the cache memory that is managed by an MP
blade.

Parity group and external volume group statistics

The following table shows the file names and types of information in the Monitor Performance
window that can be exported to files using Export Tool. These files contain statistics about parity
groups and external volume groups.

Table 6 Files with parity group and external volume group statistics

Data saved in the fileCSV fileZIP file

Number of read and write operations per secondPG_IOPS.csvPG_dat.ZIP

Size of data transferred per second (Kbps)PG_TransRate.csv

Size of read data transferred per second (Kbps)PG_Read_TransRate.csv

Size of write data transferred per second (Kbps)PG_Write_TransRate.csv

Number of read operations per secondPG_Read_IOPS.csv

Number of random read operations per secondPG_Rnd_Read_IOPS.csv

Number of read operations in "cache-fast-write" mode per secondPG_CFW_Read_IOPS.csv

Number of write operations per secondPG_Write_IOPS.csv

Number of sequential write operations per secondPG_Seq_Write_IOPS.csv

Number of random write operations per secondPG_Rnd_Write_IOPS.csv

Number of write operations in "cache-fast-write" mode per secondPG_CFW_Write_IOPS.csv

Read hit ratioPG_Read_Hit.csv

Read hit ratio in sequential access modePG_Seq_Read_Hit.csv

Read hit ratio in random access modePG_Rnd_Read_Hit.csv

Read hit ratio in "cache-fast-write" modePG_CFW_Read_Hit.csv

Exported files 87

Table 6 Files with parity group and external volume group statistics (continued)

Data saved in the fileCSV fileZIP file

Write hit ratioPG_Write_Hit.csv

Write hit ratio in sequential access modePG_Seq_Write_Hit.csv

Write hit ratio in random access modePG_Rnd_Write_Hit.csv

Write hit ratio in "cache-fast-write" modePG_CFW_Write_Hit.csv

PG_BackTrans.csv

PG_C2D_Trans.csv

PG_D2CS_Trans.csv

PG_D2CR_Trans.csv

PG_Response.csv

PG_Read_Response.csv

PG_Write_Response.csv

Number of data transfer operations between cache memory and data drives
(for example, parity groups or external volume groups) per second

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

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

The following table shows the file names and types of information in the Monitor Performance
window that can be exported to files using Export Tool. These files contain statistics about volumes
in parity groups or in external volume groups.

Table 7 Files with statistics about volumes in parity/external volume groups

Data saved in the fileCSV fileZIP file

Number of read and write operations per secondLDEV_IOPS_x-y.csvLDEV_dat/LDEV_IOPS.ZIP

Size of data transferred per second (Kbps)LDEV_TransRate_x-y.csvLDEV_dat/LDEV_TransRate.ZIP

Size of read data transferred per second (Kbps)LDEV_Read_TransRate_x-y.csvLDEV_dat/LDEV_Read_TransRate.ZIP

Size of write data transferred per second (Kbps)LDEV_Write_TransRate_x-y.csvLDEV_dat/LDEV_Read_TransRate.ZIP

Number of read operations per secondLDEV_Read_IOPS_x-y.csvLDEV_dat/LDEV_Read_IOPS.ZIP

Number of sequential read operations per secondLDEV_Seq_Read_IOPS_x-y.csvLDEV_dat/LDEV_Seq_Read_IOPS.ZIP

Number of random read operations per secondLDEV_Rnd_Read_IOPS_x-y.csvLDEV_dat/LDEV_Rnd_Read_IOPS.ZIP

LDEV_CFW_Read_IOPS_x-y.csvLDEV_dat/LDEV_CFW_Read_IOPS.ZIP

Number of read operations in "cache-fast-write"
mode per second

Number of write operations per secondLDEV_Write_IOPS_x-y.csvLDEV_dat/LDEV_Write_IOPS.ZIP

Number of sequential write operations per secondLDEV_Seq_Write_IOPS_x-y.csvLDEV_dat/LDEV_Seq_Write_IOPS.ZIP

88 Exporting Performance Monitor data

Table 7 Files with statistics about volumes in parity/external volume groups (continued)

Data saved in the fileCSV fileZIP file

Number of random write operations per secondLDEV_Rnd_Write_IOPS_x-y.csvLDEV_dat/LDEV_Rnd_Write_IOPS.ZIP

LDEV_CFW_Write_IOPS_x-y.csvLDEV_dat/LDEV_CFW_Write_IOPS.ZIP

LDEV_BackTrans_x-y.csvLDEV_dat/LDEV_BackTrans.ZIP

LDEV_C2D_Trans_x-y.csvLDEV_dat/LDEV_C2D_Trans.ZIP

LDEV_D2CS_Trans_x-y.csvLDEV_dat/LDEV_D2CS_Trans.ZIP

Number of write operations in "cache-fast-write"
mode per second

Read hit ratioLDEV_Read_Hit_x-y.csvLDEV_dat/LDEV_Read_Hit.ZIP

Read hit ratio in sequential access modeLDEV_Seq_Read_Hit_x-y.csvLDEV_dat/LDEV_Seq_Read_Hit.ZIP

Read hit ratio in random access modeLDEV_Rnd_Read_Hit_x-y.csvLDEV_dat/LDEV_Rnd_Read_Hit.ZIP

Read hit ratio in "cache-fast-write" modeLDEV_CFW_Read_Hit_x-y.csvLDEV_dat/LDEV_CFW_Read_Hit.ZIP

Write hit ratioLDEV_Write_Hit_x-y.csvLDEV_dat/LDEV_Write_Hit.ZIP

Write hit ratio in sequential access modeLDEV_Seq_Write_Hit_x-y.csvLDEV_dat/LDEV_Seq_Write_Hit.ZIP

Write hit ratio in random access modeLDEV_Rnd_Write_Hit_x-y.csvLDEV_dat/LDEV_Rnd_Write_Hit.ZIP

Write hit ratio in "cache-fast-write" modeLDEV_CFW_Write_Hit_x-y.csvLDEV_dat/LDEV_CFW_Write_Hit.ZIP

Number of data transfer operations between cache
memory and data drives (for example, volumes)
per second

Number of data transfer operations from cache
memory and data drives (for example, volumes)
per second

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.csvLDEV_dat/LDEV_D2CR_Trans.ZIP

LDEV_Read_Response_x-y.csvLDEV_dat/LDEV_Read_Response.ZIP

LDEV_Write_Response_x-y.csvLDEV_dat/LDEV_Write_Response.ZIP

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.

Number of data transfer operations from data
drives (for example, volumes) per second to cache
memory in random access mode

Average response time (microseconds) at volumesLDEV_Response_x-y.csvLDEV_dat/LDEV_Response.ZIP

Average read response time (microseconds) at
volumes

Average write response time (microseconds) at
volumes

Volumes in parity groups or external volume groups (at volumes controlled by a particular CU)

The following table shows the file names and types of information in the Monitor Performance
window that can be exported to files using Export Tool. These files contain statistics about volumes
in parity groups or external volume groups (at volumes controlled by a particular CU).

Table 8 Files with statistics about volumes in parity groups or external volume groups (at
volumes controlled by a particular CU)

Data saved in the fileCSV fileZIP file

LDEV_Read_TransRatexx.csvLDEVEachOfCU_dat/LDEV_Read_TransRate.ZIP

LDEV_Write_TransRatexx.csvLDEVEachOfCU_dat/LDEV_Write_TransRate.ZIP

The size of read data transferred per
second (Kbps)

The size of write data transferred per
second (Kbps)

Exported files 89

Table 8 Files with statistics about volumes in parity groups or external volume groups (at
volumes controlled by a particular CU) (continued)

Data saved in the fileCSV fileZIP file

LDEV_Read_Responsexx.csvLDEVEachOfCU_dat/LDEV_Read_Response.ZIP

LDEV_Write_Responsexx.csvLDEVEachOfCU_dat/LDEV_Write_Response.ZIP

LDEV_IOPSxx.csvLDEVEachOfCU_dat/LDEV_IOPS.ZIP

LDEV_TransRatexx.csvLDEVEachOfCU_dat/LDEV_TransRate.ZIP

LDEV_Read_IOPSxx.csvLDEVEachOfCU_dat/LDEV_Read_IOPS.ZIP

LDEV_Seq_Read_IOPSxx.csvLDEVEachOfCU_dat/LDEV_Seq_Read_IOPS.ZIP

LDEV_Rnd_Read_IOPSxx.csvLDEVEachOfCU_dat/LDEV_Rnd_Read_IOPS.ZIP

LDEV_CFW_Read_IOPSxx.csvLDEVEachOfCU_dat/LDEV_CFW_Read_IOPS.ZIP

LDEV_Write_IOPSxx.csvLDEVEachOfCU_dat/LDEV_Write_IOPS.ZIP

LDEV_Seq_Write_IOPSxx.csvLDEVEachOfCU_dat/LDEV_Seq_Write_IOPS.ZIP

The average read response time
(microseconds) at volumes

The average write response time
(microseconds) at volumes

The number of read and write
operations per second

The size of data transferred per second
(Kbps)

The number of read operations per
second

The number of sequential read
operations per second

The number of random read operations
per second

The number of read operations in
"cache-fast-write" mode per second

The number of write operations per
second

The number of sequential write
operations per second

LDEV_Rnd_Write_IOPSxx.csvLDEVEachOfCU_dat/LDEV_Rnd_Write_IOPS.ZIP

LDEV_CFW_Write_IOPSxx.csvLDEVEachOfCU_dat/LDEV_CFW_Write_IOPS.ZIP

LDEV_Seq_Read_Hitxx.csvLDEVEachOfCU_dat/LDEV_Seq_Read_Hit.ZIP

LDEV_Rnd_Read_Hitxx.csvLDEVEachOfCU_dat/LDEV_Rnd_Read_Hit.ZIP

LDEV_CFW_Read_Hitxx.csvLDEVEachOfCU_dat/LDEV_CFW_Read_Hit.ZIP

LDEV_Seq_Write_Hitxx.csvLDEVEachOfCU_dat/LDEV_Seq_Write_Hit.ZIP

LDEV_Rnd_Write_Hitxx.csvLDEVEachOfCU_dat/LDEV_Rnd_Write_Hit.ZIP

LDEV_CFW_Write_Hitxx.csvLDEVEachOfCU_dat/LDEV_CFW_Write_Hit.ZIP

LDEV_BackTransxx.csvLDEVEachOfCU_dat/LDEV_BackTrans.ZIP

The number of random write
operations per second

The number of write operations in
"cache-fast-write" mode per second

The read hit ratioLDEV_Read_Hitxx.csvLDEVEachOfCU_dat/LDEV_Read_Hit.ZIP

The read hit ratio in sequential access
mode

The read hit ratio in random access
mode

The read hit ratio in "cache-fast-write"
mode

The write hit ratioLDEV_Write_Hitxx.csvLDEVEachOfCU_dat/LDEV_Write_Hit.ZIP

The write hit ratio in sequential access
mode

The write hit ratio in random access
mode

The write hit ratio in "cache-fast-write"
mode

The number of data transfer operations
per second between cache memories
and data drives (for example, volumes)

90 Exporting Performance Monitor data

LDEV_C2D_Transxx.csvLDEVEachOfCU_dat/LDEV_C2D_Trans.ZIP

The number of data transfer operations
per second from cache memories and
data drives (for example, volumes)

Table 8 Files with statistics about volumes in parity groups or external volume groups (at
volumes controlled by a particular CU) (continued)

Data saved in the fileCSV fileZIP file

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

The following table shows the file names and types of information in the Monitor Performance
window that can be exported to files using Export Tool. These files contain statistics about ports.

Table 9 Files with statistics about ports

LDEV_D2CS_Transxx.csvLDEVEachOfCU_dat/LDEV_D2CS_Trans.ZIP

LDEV_D2CR_Transxx.csvLDEVEachOfCU_dat/LDEV_D2CR_Trans.ZIP

LDEV_Responsexx.csvLDEVEachOfCU_dat/LDEV_Response.ZIP

Data saved in the fileCSV fileZIP file

The number of read and write operations per second at portsPort_IOPS.csvPort_dat.ZIP

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

The average response time
(microseconds) at volumes

The size of data transferred per second at ports (Kbps)Port_KBPS.csv

The average response time (microseconds) at portsPort_Response.csv

Port_Initiator_IOPS.csv

The number of read and write operations per second at Initiator/External
ports

The size of data transferred per second at Initiator/External ports (Kbps)Port_Initiator_KBPS.csv

The average response time (microseconds) at Initiator/External portsPort_Initiator_Response.csv

Table 10 Files with statistics about mainframe ports

Data saved in the fileCSV fileZIP file

MF_Port_IOPS.csvMF_Port_dat.ZIP

The number of read and write operations per second measured at
every port

Response time per port (in microseconds)MF_Port_Response.csv

Read/write data transfer amount per port (in Kbps)MF_Port_Read_Write_KBPS.csv

Read data transfer amount per port (in Kbps)MF_Port_Read_KBPS.csv

Write data transfer amount per port (in Kbps)MF_Port_Write_KBPS.csv

Average CMR processing time (in microseconds)MF_Port_Avr_CMR.csv

Average disconnection time (in microseconds)MF_Port_Avr_DisconnectTime.csv

Average connection time (in microseconds)MF_Port_Avr_ConnectTime.csv

Number of open exchanges per secondMF_Port_Avr_OpenExchange.csv

Exported files 91

Host bus adapters connected to ports statistics

The following table shows the file names and types of information in the Monitor Performance
window that can be exported to files using Export Tool. These files contain statistics about host
bus adapters connected to ports.

Table 11 Files with statistics about host bus adapters connected to ports

Data saved in the fileCSV fileZIP file

PortWWN_xx_IOPS.csvPortWWN_dat.ZIP

PortWWN_xx_KBPS.csv

PortWWN_xx_Response.csv

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

The following table shows the file names and types of information in the Monitor Performance
window that can be exported to files using Export Tool. These files contain statistics about volumes
(LUs).

Table 12 Files with statistics about volumes (LUs)

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 (Kbps) between a port
and the HBAs connected to that port

The average response time (microseconds) between a port and
the HBAs connected to that port

Data saved in the fileCSV fileZIP file

The number of read and write operations per secondLU_IOPS.csvLU_dat.ZIP

LU_C2D_Trans.csv

LU_D2CS_Trans.csv

The size of data transferred per second (Kbps)LU_TransRate.csv

The size of read data transferred per second (Kbps)LU_Read_TransRate.csv

The size of write data transferred per second (Kbps)LU_Write_TransRate.csv

The average read response time (microseconds)LU_Read_Response.csv

The average write response time (microseconds)LU_Write_Response.csv

The number of sequential read operations per secondLU_Seq_Read_IOPS.csv

The number of random read operations per secondLU_Rnd_Read_IOPS.csv

The number of sequential write operations per secondLU_Seq_Write_IOPS.csv

The number of random write operations per secondLU_Rnd_Write_IOPS.csv

The read hit ratio in sequential access modeLU_Seq_Read_Hit.csv

The read hit ratio in random access modeLU_Rnd_Read_Hit.csv

The write hit ratio in sequential access modeLU_Seq_Write_Hit.csv

The write hit ratio in random access modeLU_Rnd_Write_Hit.csv

The number of data transfer operations per second from cache memories
to data drives (for example, LUs)

The number of data transfer operations per second from data drives (for
example, LUs) to cache memories in sequential access mode

92 Exporting Performance Monitor data

Table 12 Files with statistics about volumes (LUs) (continued)

Data saved in the fileCSV fileZIP file

LU_D2CR_Trans.csv

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)LU_Response.csv

All host bus adapters connected to ports

The following table shows the file names and types of information in the Monitor Performance
window that can be exported to files using Export Tool. These files contain statistics about all
host bus adapters connected to ports.

Table 13 Files with statistics about host bus adapters belonging to PFC groups

PPCGWWN_xx_IOPS.csvPPCGWWN_dat.ZIP

PPCGWWN_xx_Response.csv

PPCGWWN_NotGrouped_IOPS.csv

PPCGWWN_NotGrouped_KBPS.csv

Data saved in the fileCSV fileZIP file

I/O rate (that is, the number of read and write operations
per second) for HBAs belonging to a PFC group

Transfer rate (Kbps) for HBAs belonging to a PFC groupPPCGWWN_xx_KBPS.csv

Average response time (microseconds) for HBAs
belonging to a PFC group

I/O rate (that is, the number of read and write operations
per second) for HBAs that do not belong to any PFC
group

Transfer rate (Kbps) for HBAs that do not belong to any
PFC group

Notes:

• The letters "xx" in CSV filenames indicate the name of a PFC group.

• If files are exported to a Windows computer, CSV filenames may end with numbers (for example,

MP blades

The following table shows the file names and types of information in the Monitor Performance
window that can be exported to files using Export Tool. The file contains statistics about usage
rates of MPs.

Table 14 MP usage rate of each resource allocated to MP blades

PPCGWWN_NotGrouped_Response.csv

PPCGWWN_mygroup_IOPS-1.csv and PPCGWWN_MyGroup_IOPS-2.csv).

Data saved in the fileCSV fileZIP file

PHY_MPPK_x.y.csvPhyMPPK_dat.ZIP

The MP usage rate of each resource allocated to MP blades in short
range is output in the following formats:

• Performance information of LDEVs

Kernel-type *;LDEV;LDEV-number;Usage-rate

• Performance information of journals

Kernel-type *;JNLG; Journal-number;Usage-rates

Average response time (microseconds), for HBAs that
do not belong to any PFC group

• Performance information of external volumes

Kernel-type *;ExG;External-volume-group-number;Usage-rate

You can view up to 100 of the most used items in order of use.

Exported files 93

Table 14 MP usage rate of each resource allocated to MP blades (continued)

Data saved in the fileCSV fileZIP file

Caution: Use performance information as a guide to identify resources

that greatly increase the MP usage rate. Adding the performance items
together does not equal the total estimated capacity of the MPs. Likewise,
this performance information is not appropriate to estimate the usage of
a particular resource.

* The kernel type is any one of the following types:

Open-Target, Open-Initiator, Open-External, MF-Target, MF-External, BackEnd, or System.

Remote copy operations by Cnt Ac-S/Cnt Ac-S MF and monitoring data by HA (whole volumes)

The following table shows the file names and types of information on the Usage Monitor tab in
the Cnt Ac-S, Cnt Ac-S MF, and HA window that can be exported to files using Export Tool.
These files contain statistics about remote copy operations (whole volumes) by Continuous
Access Synchronous, Continuous Access Synchronous MF, and High Availability.

Table 15 Files with statistics about remote copy operations by Cnt Ac-S/Cnt Ac-S MF and
monitoring data by HA (In the whole volumes)

Data saved in the fileCSV fileZIP file

The following data in the whole volumes are saved:RemoteCopy.csvRemoteCopy_dat.ZIP

• The total number of remote I/Os (read and write operations)

• The total number of remote write I/Os

• The number of errors that occur during remote I/O

• The number of initial copy remote I/Os

• The average response time (milliseconds) for initial copy

• The average transfer rate (Kbps) for initial copy remote I/Os

• The number of update copy remote I/Os

• The average transfer rate (Kbps) 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 Cnt Ac-S and monitoring data by HA (for each volume (LU))

The following table shows the file names and types of information on the Usage Monitor tab in
the Cnt Ac-S and HA window that can be exported to files using Export Tool. These files contain
statistics about remote copy operations (for each volume (LU)) by Continuous Access Synchronous
and High Availability.

Table 16 Files with statistics about remote copy operations by Cnt Ac-S and monitoring
data by HA (for each volume (LU))

RCLU_All_RIO.csvRCLU_dat.ZIP

94 Exporting Performance Monitor data

Data saved in the fileCSV fileZIP file

The total number of remote I/Os (read and write
operations)

The total number of remote write I/OsRCLU_All_Write.csv

Table 16 Files with statistics about remote copy operations by Cnt Ac-S and monitoring
data by HA (for each volume (LU)) (continued)

Data saved in the fileCSV fileZIP file

The number of errors that occur during remote I/ORCLU_RIO_Error.csv

The number of initial copy remote I/OsRCLU_Initial_Copy_RIO.csv

RCLU_Initial_Copy_Transfer.csv

RCLU_Initial_Copy_Response.csv

RCLU_Update_Copy_Transfer.csv

RCLU_Update_Copy_Response.csv

RCLU_Pair_Synchronized.csv

RCLU_Out_of_Tracks.csv

The average transfer rate (Kbps) for initial copy remote
I/Os

The average response time (milliseconds) for the initial
copy of each volume (LU)

The number of update copy remote I/OsRCLU_Update_Copy_RIO.csv

The average transfer rate (Kbps) for update copy
remote I/Os

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)

The number of tracks that have not yet been copied by
the initial copy or resync copy operation

Remote copy by Cnt Ac-S/Cnt Ac-S MF and monitoring data by HA (volumes controlled by a particular CU)

The following table shows the file names and types of information on the Usage Monitor tab in
the Cnt Ac-S, Cnt Ac-S MF, and HA window that can be exported to files using Export Tool.
These files contain statistics about remote copy operations (volumes controlled by a particular
CU) by Continuous Access Synchronous, Continuous Access Synchronous MF, and High
Availability.

Table 17 Files with statistics about remote copy operations by Cnt Ac-S/Cnt Ac-S MF and
monitoring data by HA (at volumes controlled by a particular CU)

Data saved in the fileCSV fileZIP file

RCLDEV_All_RIO_xx.csvRCLDEV_dat/RCLDEV_All_RIO.ZIP

RCLDEV_All_Write_xx.csvRCLDEV_dat/RCLDEV_All_Write.ZIP

RCLDEV_RIO_Error_xx.csvRCLDEV_dat/RCLDEV_RIO_Error.ZIP

RCLDEV_Initial_Copy_RIO_xx.csvRCLDEV_dat/RCLDEV_Initial_Copy_RIO.ZIP

RCLDEV_Initial_Copy_Transfer_xx.csvRCLDEV_dat/RCLDEV_Initial_Copy_Transfer.ZIP

RCLDEV_Initial_Copy_Response_xx.csvRCLDEV_dat/RCLDEV_Initial_Copy_Response.ZIP

RCLDEV_Update_Copy_RIO_xx.csvRCLDEV_dat/RCLDEV_Update_Copy_RIO.ZIP

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 transfer rate
(Kbps) for initial copy
remote I/Os

The average response
time (milliseconds) for
initial copy at volumes

The number of update
copy remote I/Os

Exported files 95

Table 17 Files with statistics about remote copy operations by Cnt Ac-S/Cnt Ac-S MF and
monitoring data by HA (at volumes controlled by a particular CU) (continued)

Data saved in the fileCSV fileZIP file

RCLDEV_Update_Copy_Transfer_xx.csvRCLDEV_dat/RCLDEV_Update_Copy_Transfer.ZIP

RCLDEV_Update_Copy_Response_xx.csvRCLDEV_dat/RCLDEV_Update_Copy_Response.ZIP

RCLDEV_Pair_Synchronized_xx.csvRCLDEV_dat/RCLDEV_Pair_Synchronized.ZIP

RCLDEV_Out_of_Tracks_xx.csvRCLDEV_dat/RCLDEV_Out_of_Tracks.ZIP

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 Cnt Ac-J and Cnt Ac-J MF (whole volumes)

The following table shows the file names and types of information on the Usage Monitor tab in
the Cnt Ac-J and Cnt Ac-J MF window that can be exported to files using Export Tool. These
files contain statistics about remote copy operations (whole volumes) by Continuous Access
Journal and Continuous Access Journal MF.

The average transfer rate
(Kbps) for update copy
remote I/Os

The average response
time (milliseconds) for the
update copy at volumes

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

Table 18 Files with statistics about remote copy operations by Cnt Ac-J and Cnt Ac-J MF
(In the whole volumes)

Data saved in the fileCSV fileZIP file

The following data in the whole volumes are saved:UniversalReplicator.csvUniversalReplicator_dat.zip

• The number of write I/Os per second

• The amount of data that are written per second (Kbps)

• The initial copy hit rate (percent)

• The average transfer rate (Kbps) for initial copy operations

• The number of asynchronous remote I/Os per second at the

primary storage system

• The number of journals at the primary storage system

• The average transfer rate (Kbps) 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 (Kbps) for journals in the secondary

storage system

• The remote I/O average response time (milliseconds) on the
secondary storage system

96 Exporting Performance Monitor data

Remote copy by Cnt Ac-J and Cnt Ac-J MF (at journals)

The following table shows the file names and types of information on the Usage Monitor tab in
the Cnt Ac-J and Cnt Ac-J MF window that can be exported to files using Export Tool. These
files contain statistics about remote copy operations (at journals) by Continuous Access Journal
and Continuous Access Journal MF.

Table 19 Files with statistics about remote copy operations by Cnt Ac-J and Cnt Ac-J MF
(at journals)

Data saved in the fileCSV fileZIP file

The number of write I/Os per secondURJNL_Write_Record.csvURJNL_dat.ZIP

(continued)

URJNL_Write_Transfer.csv

URJNL_Initial_Copy_Transfer.csv

URJNL_M-JNL_Asynchronous_RIO.csv

URJNL_M-JNL_Asynchronous_Journal.csv

URJNL_M-JNL_Asynchronous_Copy_Transfer.csv

URJNL_M-JNL_Asynchronous_Copy_Response.csv

URJNL_R-JNL_Asynchronous_RIO.csv

URJNL_R-JNL_Asynchronous_Journal.csv

URJNL_R-JNL_Asynchronous_Copy_Transfer.csv

URJNL_R-JNL_Asynchronous_Copy_Response.csvURJNL_dat.ZIP

The amount of data that are written per second
(Kbps)

The initial copy hit rate (percent)URJNL_Initial_Copy_Hit.csv

The average transfer rate (Kbps) for initial copy
operations

The number of asynchronous remote I/Os per
second at the primary storage system

The number of journals at the primary storage
system

The average transfer rate (Kbps) 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 (Kbps) for journals in
the secondary storage system

The remote I/O average response time
(milliseconds) on the secondary storage system

URJNL_M-JNL_Meta_Data_Used_Rate.csv

URJNL_R-JNL_Meta_Data_Used_Rate.csv

Remote copy by Cnt Ac-J (for each volume (LU))

The following table shows the file names and types of information on the Usage Monitor tab in
the Cnt Ac-J window that can be exported to files using Export Tool. These files contain statistics
about remote copy operations (for each volume (LU)) by Continuous Access Journal.

Data usage rate (percent) for master journalsURJNL_M-JNL_Data_Used_Rate.csv

Metadata usage rate (percent) for master
journals

Data usage rate (percent) for restore journalsURJNL_R-JNL_Data_Used_Rate.csv

Metadata usage rate (percent) for restore
journals

Exported files 97

Table 20 Files with statistics about remote copy operations by Cnt Ac-J (for each volume
(LU))

Data saved in the fileCSV fileZIP file

The number of read I/Os per secondURLU_Read_Record.csvURLU_dat.ZIP

The number of read hit records per secondURLU_Read_Hit.csv

The number of write I/Os per secondURLU_Write_Record.csv

The number of write hit records per secondURLU_Write_Hit.csv

The amount of data that are read per second (Kbps)URLU_Read_Transfer.csv

The amount of data that are written per second (Kbps)URLU_Write_Transfer.csv

The initial copy hit rate (percent)URLU_Initial_Copy_Hit.csv

The average transfer rate (Kbps) for initial copy operationsURLU_Initial_Copy_Transfer.csv

Remote copy by Cnt Ac-J and Cnt Ac-J MF (at volumes controlled by a particular CU)

The following table shows the file names and types of information on the Usage Monitor tab in
the Cnt Ac-J and Cnt Ac-J MF window that can be exported to files using Export Tool. These
files contain statistics about remote copy operations (at volumes controlled by a particular CU)
by Continuous Access Journal and Continuous Access Journal MF.

Table 21 Files with statistics about remote copy operations by Cnt Ac-J and Cnt Ac-J MF
(at Volumes controlled by a particular CU)

Data saved in the fileCSV fileZIP file

The number of read I/Os per secondURLDEV_Read_Record_xx.csvURLDEV_dat/URLDEV_Read_Record.ZIP

URLDEV_Read_Hit_xx.csvURLDEV_dat/URLDEV_Read_Hit.ZIP

URLDEV_Write_Hit_xx.csvURLDEV_dat/URLDEV_Write_Hit.ZIP

URLDEV_Read_Transfer_xx.csvURLDEV_dat/URLDEV_Read_Transfer.ZIP

URLDEV_Write_Transfer_xx.csvURLDEV_dat/URLDEV_Write_Transfer.ZIP

URLDEV_Initial_Copy_Transfer_xx.csvURLDEV_dat/URLDEV_Initial_Copy_Transfer.ZIP

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.

The number of read hit records per
second

The number of write I/Os per secondURLDEV_Write_Record_xx.csvURLDEV_dat/URLDEV_Write_Record.ZIP

The number of write hit records per
second

The amount of data that are read per
second (Kbps)

The amount of data that are written per
second (Kbps)

The initial copy hit rate (percent)URLDEV_Initial_Copy_Hit_xx.csvURLDEV_dat/URLDEV_Initial_Copy_Hit.ZIP

The average transfer rate (Kbps) for
initial copy operations

98 Exporting Performance Monitor data

Causes of Invalid Monitoring Data

If the value of monitoring data in CSV files is less than 0 (zero), consider the following causes:

Probable causesInvalid values of

monitoring data

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 restarting
the disk array is in progress.

• Performance Monitor attempted to obtain statistics when a heavy workload is imposed
on the disk array.

• There is no volume in a parity group.

• Just after the CUs to be monitored were added, Export Tool failed to save files that

contain monitoring data for all volumes or journal volumes used by remote copy
software (Cnt Ac-S, Cnt Ac-S MF, Cnt Ac-J, Cnt Ac-J MF) and HA. For details about
the files, see Table 15 (page 94), Table 18 (page 96), and Table 19 (page 97).

• If Disable is selected to stop monitoring in the Monitoring Switch field on the Monitoring
Options window and longrange is specified as the sampling interval, the monitoring
data for the period when Performance Monitor stops monitoring is (-1).

• If you added the CU during monitoring, specified longrange as the sampling interval,
and collected monitoring data, the value (-1) is displayed as the monitoring data
before the CU was added.

• If the CU number is not the monitoring target object, Performance Monitor cannot
obtain monitoring data from the CU. However, when the RemoteCopy,
UniversalReplicator, or URJNL operand is specified for the group subcommand, the
value (-1) is not displayed as the monitoring data even if the CU number is not the
monitoring target object. In that case, data on the monitored CU is added up and
output to the CSV file.

• If no CU is specified as a monitoring target, the value (-1) is displayed as the
monitoring data.

• If the mainframe host runs a command to clear usage information, the monitoring
data counter is cleared. As a result, the monitoring data at that point becomes disabled,
and the value (-1) displays as the monitoring data.

The monitoring data in the
CSV file includes (-3).

The monitoring data in the
CSV file includes (-4).

The monitoring data in the
CSV file includes "-5".

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 Export Tool does not match
the collecting period for monitoring data, Export Tool cannot collect the monitoring data.
If data of SVP is updated while the monitoring data is being collected, the collected
monitoring data near the collection start time is (-4).

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

Causes of Invalid Monitoring Data 99

Troubleshooting Export Tool

The following table explains possible problems with Export Tool and probable solutions to the
problems.

Probable causes and recommended actionPossible problems

You cannot run the batch file.

Export Tool stops and the
processing does not continue.

The command prompt window
was displaying progress of the
export processing, but the
window stopped displaying
progress before the
processing stopped. The
progress information does not
seem to be updated anymore.

An error occurs and the
processing stops.

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

If 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
Export Tool is running. To cancel pause mode, activate the command prompt
window and then press the <ESC> key. If a timeout of RMI occurs during pause
mode, the login will be canceled and an error will occur when you cancel pause
mode after the timeout. The error message ID will be (0001 4011).

• If a memory size is not specified in a batch file, the Out Of Memory Error occurs
in JRE, 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 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 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 Export Tool, first increase the value of the -Dmd.rmitimeout
parameter (maximum: 1,440 minutes (24 hours), and then run Export Tool. For details
about -Dmd.rmitimeout, see the Operands table for the Java command in

“Operands” (page 82). If the error persists, contact the HPE technical 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 Export Tool again.

• Maintenance operations are being performed on the disk array. Wait until the
maintenance operations finish and then run Export Tool again.

If the error message ID is none of the above, see “Messages issued by Export Tool”

(page 101).

The monitoring data in the
CSV file includes (-1).

• When Export Tool
terminated abnormally due
to error, the row of Check
License is shown as
Unmarshal Exception in
the log file.

• Export Tool terminated
abnormally because the
processing did not
continue. version
unmatched is shown in the
log file.

100 Exporting Performance Monitor data

For details on invalid monitoring data, see “Causes of Invalid Monitoring Data”

(page 99).

It might be an unsuitable combination of the DKCMAIN/SVP program version and
the Export Tool version. Confirm whether versions of these programs are correct.