HP XP RAID Manager Software User Manual

HP XP P9000 Performance for Open and Mainframe Systems User Guide

Abstract

This guide describes and provides instructions for using HP XP P9000 Performance Monitor Software and HP XP P9000 Cache Residency Manager Software to configure and perform operations on HP XP P9000 disk arrays. The intended audience is a storage system administrator or authorized service provider with independent knowledge of HP XP P9000 disk arrays and the HP StorageWorks Remote Web Console.

HP Part Number: AV400-96634 Published: March 2014 Edition: Twelfth

Confidential computer software. Valid license from HP 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.

The information contained herein is subject to change without notice. The only warranties for HP 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. HP shall not be liable for technical or editorial errors or omissions contained herein.

Acknowledgements

Microsoft®, Windows®, Windows® XP, and Windows NT® are U.S. registered trademarks of Microsoft Corporation.

UNIX® is a registered trademark of The Open Group.

Export Requirements

You may not export or re-export this document or any copy or adaptation in violation of export laws or regulations.

Without limiting the foregoing, this document may not be exported, re-exported, transferred or downloaded to or within (or to a national resident of) countries under U.S. economic embargo, including Cuba, Iran, North Korea, Sudan, and Syria. This list is subject to change.

This document may not be exported, re-exported, transferred, or downloaded to persons or entities listed on the U.S. Department of Commerce Denied Persons List, Entity List of proliferation concern or on any U.S. Treasury Department Designated Nationals exclusion list, or to parties directly or indirectly involved in the development or production of nuclear, chemical, biological weapons, or in missile technology programs as specified in the U.S. Export Administration Regulations (15 CFR 744).

Revision History

DescriptionDateEdition

Applies to microcode version 70-01-01-00/00 or later.October 2010First

Applies to microcode version 70-01-24-00/00 or later.November 2010Second

Applies to microcode version 70-01-62-00/00 or later.January 2011Third

Applies to microcode version 70-02-01-00/00 or later.May 2011Fourth

Applies to microcode version 70-02-5x-00/00 or later.September 2011Fifth

Applies to microcode version 70-03-00-00/00 or later.November 2011Sixth

Applies to microcode version 70-03-30-00/00 or later.April 2012Seventh

Applies to microcode version 70-04-00-00/00 or later.August 2012Eighth

Applies to microcode version 70-04-00-00/00 or later.November 2012Ninth

Applies to microcode version 70-06-04-00/00 or later.July 2013Tenth

Applies to microcode version 70-06-11-00/00 or later.January 2014Eleventh

Applies to microcode version 70-06-15-00/00 or later.March 2014Twelfth

1 Performance overview.................................................................................8

Performance Monitor overview...................................................................................................8

Performance Control overview....................................................................................................8

Performance of high-priority hosts...........................................................................................8

Upper-limit control................................................................................................................9

Threshold control.................................................................................................................9

Cache Residency overview.........................................................................................................9

Prestaging data in cache......................................................................................................9

Priority mode (read data only).............................................................................................10

Bind mode (read and write data).........................................................................................11

2 About performance monitoring...................................................................13

Monitoring storage system resources.........................................................................................13

Placing data in cache.............................................................................................................13

Prestaging specific data...........................................................................................................13

Priority mode.........................................................................................................................14

Bind mode.............................................................................................................................14

3 Interoperability of Performance Monitor and other products............................17

Cautions and restrictions for monitoring.....................................................................................17

Cautions and restrictions for usage statistics...............................................................................18

Using Performance Control.......................................................................................................18

WWN monitoring data...........................................................................................................20

Microprogram replacement......................................................................................................20

Changing the time setting of SVP..............................................................................................21

Using Performance Control.......................................................................................................21

4 Monitoring WWNs..................................................................................23

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

Adding new WWNs to monitor...............................................................................................23

Removing WWNs to monitor...................................................................................................23

Adding WWNs to ports..........................................................................................................23

Editing the WWN nickname....................................................................................................24

Connecting WWNs to ports....................................................................................................24

Deleting unused WWNs from monitoring targets........................................................................25

5 Monitoring CUs.......................................................................................26

Displaying CUs to monitor.......................................................................................................26

Adding or removing CUs to monitor..........................................................................................26

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

6 Monitoring operation................................................................................28

Performing monitoring operations.............................................................................................28

Starting monitoring.................................................................................................................28

Stopping monitoring...............................................................................................................28

7 Setting statistical storage ranges.................................................................30

About statistical storage ranges................................................................................................30

Viewing statistics................................................................................................................30

Setting the storing period of statistics.........................................................................................30

8 Working with graphs................................................................................32

Basic operation .....................................................................................................................32

Objects that can be displayed in graphs ...................................................................................33

Usage rates of MPs ................................................................................................................34

Contents 3

Usage rate of a data recovery and reconstruction processor.........................................................35

Usage rate of cache memory...................................................................................................35

Write pending statistics...........................................................................................................35

Access paths usage statistics....................................................................................................36

Throughput of storage system...................................................................................................37

Size of data transferred...........................................................................................................38

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

Cache hit rates.......................................................................................................................40

Back-end performance.............................................................................................................42

Hard disk drive usage statistics.................................................................................................42

Hard disk drive access rates.....................................................................................................43

Business Copy usage statistics..................................................................................................43

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

9 Changing display of graphs......................................................................45

Graph operation....................................................................................................................45

Changing displayed items.......................................................................................................45

Changing a display period......................................................................................................45

Adding a new graph .............................................................................................................45

Deleting graph panel..............................................................................................................46

10 Performance Control operations................................................................47

Overview of Performance Control operations..............................................................................47

If one-to-one connections link HBAs and ports............................................................................47

If many-to-many connections link HBAs and ports........................................................................49

Port tab operations..................................................................................................................53

Analyzing traffic statistics....................................................................................................54

Setting priority for ports on the storage system.......................................................................54

Setting upper-limit values to traffic at non-prioritized ports........................................................55

Setting a threshold ............................................................................................................56

WWN tab operations.............................................................................................................57

Monitoring all traffic between HBAs and ports.......................................................................57

Excluding traffic between a host bus adapter and a port from the monitoring target...............59

Analyzing traffic statistics....................................................................................................59

Setting priority for host bus adapters....................................................................................60

Setting upper-limit values for non-prioritized WWNs...............................................................61

Setting a threshold.............................................................................................................62

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

Registering a replacement host bus adapter...........................................................................64

Grouping host bus adapters................................................................................................65

Containing multiple HBAs in an PFC group.......................................................................65

Deleting an HBA from an PFC group...............................................................................65

Switching priority of an PFC group..................................................................................66

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

Renaming an PFC group................................................................................................67

Deleting an PFC group...................................................................................................68

11 Estimating cache size...............................................................................69

About cache size....................................................................................................................69

Calculating cache size for open systems....................................................................................70

Calculating cache size for mainframe systems.............................................................................73

Cache Residency cache areas..................................................................................................73

Cache Residency system specifications......................................................................................74

12 Managing resident cache........................................................................75

Cache Residency rules, restrictions, and guidelines......................................................................75

Launching Cache Residency.....................................................................................................77

4 Contents

Viewing Cache Residency information.......................................................................................77

Placing specific data into Cache Residency cache.......................................................................77

Placing LDEVs into Cache Residency cache................................................................................79

Releasing specific data from Cache Residency cache..................................................................80

Releasing LDEVs from Cache Residency cache............................................................................80

Changing mode after Cache Residency is registered in cache......................................................81

13 Troubleshooting......................................................................................82

Troubleshooting resources........................................................................................................82

14 Support and other resources.....................................................................83

Contacting HP........................................................................................................................83

Subscription service............................................................................................................83

Documentation feedback....................................................................................................83

Related information.................................................................................................................83

HP websites......................................................................................................................83

Conventions for storage capacity values....................................................................................84

Typographic conventions.........................................................................................................84

A Export Tool..............................................................................................86

About the Export Tool..............................................................................................................86

Installing the Export Tool..........................................................................................................86

System requirements...........................................................................................................86

Installing the Export Tool on a Windows system.....................................................................87

Installing the Export Tool on a UNIX system...........................................................................87

Using the Export Tool..............................................................................................................88

Preparing a command file...................................................................................................88

Preparing a batch file.........................................................................................................91

Running the Export Tool......................................................................................................92

File formats...................................................................................................................92

Processing time.............................................................................................................93

Termination code..........................................................................................................93

Log files.......................................................................................................................94

Error handling..............................................................................................................94

Export Tool command reference................................................................................................95

Export Tool command syntax...............................................................................................95

Conventions.................................................................................................................95

Syntax descriptions........................................................................................................95

Writing a script in the command file................................................................................96

Viewing the online Help for subcommands.......................................................................96

Subcommand list...............................................................................................................96

svpip................................................................................................................................96

retry.................................................................................................................................97

login................................................................................................................................98

show................................................................................................................................98

group...............................................................................................................................99

Short-range.....................................................................................................................109

long-range......................................................................................................................111

outpath...........................................................................................................................113

option............................................................................................................................113

apply.............................................................................................................................114

set.................................................................................................................................114

help...............................................................................................................................115

Java...............................................................................................................................116

Exported files.......................................................................................................................117

Monitoring data exported by the Export Tool.......................................................................117

Contents 5

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

Parity groups, external volume groups, or V-VOL groups statistics............................................121

Volumes in parity/external volume groups or V-VOL groups statistics.......................................122

Volumes in parity groups, external volume groups, or V-VOL groups (at volumes controlled by a

particular CU).................................................................................................................123

Port statistics....................................................................................................................124

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

Volumes (LU) statistics.......................................................................................................125

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

MP blades......................................................................................................................126

Remote copy operations by Cnt Ac-S/Cnt Ac-S Z (whole volumes)...........................................127

Remote copy operations by Cnt Ac-S and Cnt Ac-S Z (for each volume (LU)).............................127

Remote copy by Cnt Ac-S and Cnt Ac-S Z (volumes controlled by a particular CU)....................128

Remote copy by Cnt Ac-J and Cnt Ac-J Z (whole volumes)......................................................129

Remote copy by Cnt Ac-J and Cnt Ac-J Z (at journals)............................................................130

Remote copy by Cnt Ac-J and Cnt Ac-J Z (for each volume (LU))..............................................131

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

Causes of Invalid Monitoring Data..........................................................................................132

Troubleshooting the Export Tool..............................................................................................133

Messages issued by the Export tool....................................................................................134

B Performance Monitor GUI reference .........................................................137

Performance Monitor main window.........................................................................................137

Edit Monitoring Switch wizard................................................................................................139

Edit Monitoring Switch window..........................................................................................139

Confirm window..............................................................................................................140

Monitor Performance window.................................................................................................140

Edit CU Monitor Mode wizard...............................................................................................148

Edit CU Monitor Mode window.........................................................................................148

Confirm window..............................................................................................................150

View CU Matrix window.......................................................................................................152

Select by Parity Groups window.............................................................................................153

Parity Group Properties window..............................................................................................154

Edit WWN wizard...............................................................................................................155

Edit WWN window.........................................................................................................155

Confirm window..............................................................................................................155

Edit WWN Monitor Mode wizard..........................................................................................156

Edit WWN Monitor Mode window....................................................................................156

Confirm window..............................................................................................................158

Delete Unused WWNs window..............................................................................................160

Add New Monitored WWNs wizard......................................................................................160

Add New Monitored WWNs window................................................................................160

Confirm window..............................................................................................................162

Add to Ports wizard..............................................................................................................163

Add to Ports window........................................................................................................163

Confirm window..............................................................................................................164

Monitor window...................................................................................................................165

MP Properties window...........................................................................................................167

Edit Time Range window.......................................................................................................168

Edit Performance Objects window...........................................................................................169

Add Graph window..............................................................................................................177

Wizard buttons....................................................................................................................185

Navigation buttons...............................................................................................................185

C Performance Control GUI reference...........................................................187

Performance Control window..................................................................................................187

6 Contents

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

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

D Cache Residency GUI reference...............................................................195

Cache Residency window......................................................................................................195

Multi Set dialog box ............................................................................................................199

Multi Release dialog box ......................................................................................................200

Glossary..................................................................................................202

Index.......................................................................................................204

Contents 7

1 Performance overview

Unless specified otherwise, the term HP XP P9000 refers to the HP XP P9500 Disk Array. This chapter provides an overview of the Remote Web Console software products that enable you

to monitor and manage the performance of the HP XP P9500 storage system.

Performance Monitor overview

Performance Monitor enables you to monitor your HP XP P9500 storage system and collect detailed usage and performance statistics. You can view the storage system data on graphs to identify changes in usage rates, workloads, and traffic, analyze trends in disk I/O, and detect peak I/O times. If there is a decrease in storage system performance (for example, delayed host response times), Performance Monitor can help you detect the cause of the problem and resolve it.

Performance Monitor provides data about storage system resources such as drives, volumes, and microprocessors as well as statistics about front-end (host I/O) and back-end (disk I/O) workloads. Using the Performance Monitor data you can configure Performance Control, Cache Residency, and Cache Partition operations to manage and fine-tune the performance of your storage system.

NOTE:

• To correctly display the performance statistics of a parity group, all volumes belonging to the

parity group must be specified as monitoring targets.

• To correctly display the performance statistics of a LUSE volume, all volumes making up the

LUSE volume must be specified as monitoring targets.

• 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, performance statistics may not be collected for some volumes.

Performance Control overview

Performance Control allows you to designate prioritized ports (for example, for production servers) and non-prioritized ports (for example, for development servers) and set upper limits and thresholds for the I/O activity of these ports to prevent low-priority activities from negatively impacting high-prority activities. Performance Control operations can be performed only for ports connected to open-systems hosts.

Performance of high-priority hosts

In a storage area network (SAN) environment, the storage system is usually connected with many host servers. Some types of host servers often require higher performance than others. For example, production servers such as database and application servers that are used to perform daily tasks of business organizations usually require high performance. If production servers experience decreased performance, productivity in business activities can be negatively impacted. To prevent this from happening, the system administrator needs to maintain the performance of production servers at a relatively high level.

Computer systems in business organizations often include development servers, which are used for developing, testing, and debugging business applications, as well as production servers. If development servers experience decreased performance, development activities can be negatively impacted, but a drop in development server performance does not have as much negative impact to the entire organization as a drop in production server performance. In this case, you can use Performance Control to give higher priority to I/O activity from production servers than I/O activity from development servers to manage and control the impact of development activities.

8 Performance overview

Upper-limit control

Using Performance Control you can limit the number of I/O requests from servers to the storage system as well as the amount of data that can be transferred between the servers and the storage system to maintain production server performance at the required levels. This practice of limiting the performance of low-priority host servers is called upper-limit control.

Threshold control

While upper-limit control can help production servers to perform at higher levels during periods of heavy use, it may not be useful when production servers are not busy. For example, if the I/O activity from production servers is high between 09:00 and 15:00 hours and decreases significantly after 15:00, upper-limit control for development servers may not be required after 15:00.

To address this situation Performance Control provides threshold control, which automatically disables upper-limit control when I/O traffic between production servers and the storage system decreases to a user-specified level. This user-specified level at which upper-limit control is disabled is called the threshold. You can specify the threshold as an I/O rate (number of I/Os per second) and a data transfer rate (amount of data transferred per second).

For example, if you set a threshold of 500 I/Os per second to the storage system, the upper-limit controls for development servers are disabled when the I/O rate of the production servers drops below 500 I/Os per second. If the I/O rate of the production servers goes up and exceeds 500 I/Os per second, upper-limit control is restored to the development servers.

If you also set a threshold of 20 MB per second to the storage system, the data transfer rate limit for the development servers is not reached when the amount of data transferred between the storage system and the production servers is less than 20 MB per second.

Cache Residency overview

Cache Residency enables you to store frequently accessed data in the storage system's cache memory so that it is immediately available to hosts. Using Cache Residency you can increase the data access speed for specific data by enabling read and write I/Os to be performed at the higher front-end access speeds. You can use Cache Residency for both open-systems and mainframe data.

When Cache Residency is used, total storage system cache capacity must be increased to avoid data access performance degradation for non-cache-resident data. The maximum allowable Cache Residency cache area is configured when the cache is installed, so you must plan carefully for Cache Residency operations and work with your HP representative to calculate the required amount of cache memory for your configuration and requirements.

Cache Residency provides the following functions:

• Prestaging data in cache

• Priority cache mode

• Bind cache mode

Once data has been placed in cache, the cache mode cannot be changed without cache extension. If you need to change the cache mode without cache extension, you must release the data from cache, and then place the data back in cache with the desired mode.

Prestaging data in cache

Using Cache Residency you can place specific data into user-defined Cache Residency cache areas, also called cache extents, before it is accessed by the host. This is called prestaging data in cache. When prestaging is used, the host locates the prestaged data in the Cache Residency cache during the first access, thereby improving data access performance. Prestaging can be used for both priority mode and bind mode operations.

Cache Residency overview 9

Prestaging occurs under any of the following circumstances:

• When prestaging is performed using Cache Residency.

• When the storage system is powered on.

• When cache maintenance is performed.

Figure 1 Cache Residency cache area

NOTE:

• If the Cache Residency cache area is accessed for I/O before the prestaging operation is

complete, the data may not be available in cache at the first I/O access.

• To prevent slow response times for host I/Os, the storage system may interrupt the prestaging

operation when the cache load is heavy.

• Do not use the prestaging function if you specify the Cache Residency setting on a volume

during the quick formatting operation. To use the prestaging function after the quick formatting operation completes, first release the Cache Residency setting and then specify the setting again with the prestaging setting enabled. For information about quick formatting, see the HP

XP P9000 Provisioning for Open Systems User Guide or HP XP P9000 Provisioning for Mainframe Systems User Guide.

• When external volumes are configured in the storage system, you need to disconnect the

external storage system before powering off the storage system. If you power off the storage system without performing the disconnect external storage system operation and then turn on the power supply again, the prestaging process is aborted. If the prestaging process is aborted, you need to perform the prestaging operation again.

The prestaging process is aborted if a volume is created, deleted, or restored during the prestaging operation. If the prestaging process is aborted, you need to perform the prestaging operation again after the create, delete, or restore volume operation is complete.

Priority mode (read data only)

In priority mode the Cache Residency extents are used to hold read data for specific extents on volumes. Write data is write duplexed in cache other than Cache Residency cache, and the data is destaged to the drives when disk utilization is low.

The required total cache capacity for priority mode (normal mode) is: standard cache + Cache Residency cache + additional cache The next table specifies the standard cache capacity requirements for priority mode operations.

Meeting these requirements is important for preventing performance degradation. For more information about calculating cache size for priority mode, see “Estimating cache size” (page 69).

10 Performance overview

Table 1 Cache capacity requirements for CR priority mode

capacity is 128 GB or less

capacity exceeds 128 GB

1 GB = 1,073,741,824 bytes

Bind mode (read and write data)

In bind mode the Cache Residency extents are used to hold read and write data for specific extents on volumes. Data written to the Cache Residency bind area is not destaged to the drives. To ensure data integrity, write data is duplexed in the Cache Residency cache area, which consumes a significant amount of the Cache Residency cache.

Bind mode provides the following advantages over priority mode:

• The accessibility of read data is the same as Cache Residency priority mode.

• Write operations do not have to wait for available cache segments.

• There is no back-end contention caused by destaging data.

The required total cache capacity for bind mode is: standard cache + Cache Residency cache Cache Residency bind data that has write attributes is normally not destaged. However, the data

is destaged to disk in the following cases:

Standard cache capacitySettings of priority mode

16 GBSpecified number of cache areas is 8,192 or less and the specified

32 GBSpecified number of cache areas exceeds 8,192 or the specified

• During cache blockage that is caused by certain maintenance operations (for example, cache

upgrades) or by cache failure.

• When the storage system is powered off.

• When the volume is deleted from Cache Residency bind mode.

The next table specifies the cache requirements for bind mode operations. Meeting these requirements is important for preventing performance degradation. For more information about calculating cache size for bind mode, see “Estimating cache size” (page 69).

Table 2 Bind mode cache requirements

System Type

Open systems

Type

RAID 5 (3390) or RAID 6

RAID 1, or external volumes

Capacity SpecificationsRAID Level or Volume

Slot capacity: 264 KB Cache segment capacity: 16.5 KB Cache segments needed per slot: 48

(slot capacity / cache segment capacity)

Slot capacity: 264 KB Cache segment capacity: 16.5 KB Cache segments needed per slot: 32

(slot capacity / cache segment capacity)

Cache Residency Cache Requirement

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

2 times the space required for user data: 1 slot = 2 × 264 KB = 528 KB = 32 cache segments

Mainframe (for example, 3390-3, 3390-9)

RAID 5 mainframe or RAID 6

Slot capacity: 66 KB Cache segment capacity: 16.5 KB

3 times the space required for user data: 1 slot = 3 × 66 KB

Cache Residency overview 11

Table 2 Bind mode cache requirements (continued)

System Type

Type

RAID 1 mainframe, or external volumes

Capacity SpecificationsRAID Level or Volume

Cache segments needed per slot: 12 (slot capacity / cache segment capacity)

Note: Even though a mainframe track is 56 KB, because cache is divided into 16.5 KB segments, it requires 4 segments.

Slot capacity: 66 KB Cache segment capacity: 16.5 KB Cache segments needed per slot: 8

(slot capacity / cache segment capacity)

Cache Residency Cache Requirement

= 198 KB = 12 cache segments

2 times the space required for user data: 1 slot = 2 × 66 KB = 132 KB = 8 cache segments

12 Performance overview

2 About performance monitoring

This topic presents an overview of Performance Monitor and Cache Residency.

Monitoring storage system resources

Performance Monitor enables you to monitor your storage system and collect detailed usage and performance statistics. If there is a decrease in storage system performance (for example, delayed host response times), Performance Monitor can help you detect the cause of the problem and resolve it.

Performance Control uses the data collected by Performance Monitor to identify and resolve bottlenecks of activity on the ports.

Placing data in cache

Cache Residency enables you to place specific data into user-defined Cache Residency cache areas, also called cache extents, so that the data is available to hosts at front-end data transfer speeds. This is called prestaging data in cache.

Prestaging specific data

Cache Residency supports prestaging of data in which specific data is placed into the Cache Residency cache before it is accessed by the host. When prestaging is used, the host locates the prestaged data in the Cache Residency cache during the first access, thereby improving performance.

Figure 2 Cache Residency cache area

CAUTION: Total storage system cache capacity must be increased when using Cache Residency

to avoid data access performance degradation for non-cache-resident data. Cache Residency is available only on HP XP P9500 storage systems configured with at least 512 MB of cache. The HP representative configures the maximum allowable Cache Residency area when the cache is installed.

Both priority mode and bind mode permit prestaging. Prestaging occurs under any of the following circumstances:

• When prestaging is performed from the SVP or from Remote Web Console.

• When the power is turned on.

• When cache maintenance is performed.

Monitoring storage system resources 13

NOTE:

• If you access the Cache Residency area for input and output before the prestaging operation

is performed from the SVP or Remote Web Console, the host may not be able to find data in the cache at the first I/O access after Cache Residency is configured.

• To prevent the slow response time of the host I/O, the prestaging operation may be interrupted

when the cache load is heavy.

• If you specify the Cache Residency setting on the volume during the quick formatting, do not

use the prestaging function. If you want to use the prestaging function after the quick formatting processing completes, first release the setting and then specify the Cache Residency setting again, with the prestaging setting enabled. For information about the quick formatting, see

HP XP P9000 Provisioning for Open Systems User Guide or HP XP P9000 Provisioning for Mainframe Systems User Guide.

• When external volumes are set in the storage system, execute the disconnect external storage

system operation to the external storage system before turning off the power supply of the storage system. If you turn off the power supply of the storage system without executing the disconnect external storage system operation to the external storage system and then turn on the power supply again, the prestaging processing is aborted. If the prestaging processing is aborted, perform the prestaging operation from SVP or Remote Web Console.

The prestaging processing is aborted if a volume is created, deleted, or restored during the prestaging operation. If the prestaging processing is aborted, perform the prestaging operation from SVP or Remote Web Console after finishing a volume create, delete, or restore volume operation.

Priority mode

In priority mode the Cache Residency extents are used to hold read data for specific extents on volumes. Write data is write duplexed in cache other than that of Cache Residency, and the data is destaged to the disk drive when disk utilization is low.

In priority mode (normal mode), the total capacity of cache required is: standard cache + Cache Residency cache + additional cache The following table specifies the standard cache capacity requirements for Cache Residency priority

mode operations. Meeting these requirements is important for preventing performance degradation. For more information about calculating cache size for priority mode, see “Estimating cache size”

(page 69).

Table 3 Cache capacity requirements for CR priority mode

and the specified capacity is 128 GB or less

or the specified capacity exceeds 128 GB

1 GB = 1,073,741,824 bytes

Bind mode

Standard cache capacitySettings of priority mode

16 GBSpecified number of cache areas is 8,192 or less

32 GBSpecified number of cache areas exceeds 8,192

Cache Residency uses extents to hold read and write data for specific extents on volumes. Data written to the Cache Residency bind area is not destaged to the disk. To ensure data integrity, write data is duplexed in the Cache Residency area, which consumes a significant amount of the Cache Residency cache.

14 About performance monitoring

Bind mode has the following advantages:

• The accessibility of read data is the same as Cache Residency priority mode.

• Write operations do not have to wait for available cache segments.

• There is no back-end contention caused by destaging data.

In Bind Mode, the total capacity of cache required is: standard cache + Cache Residency cache For more information about calculating case size for bind mode, see “Estimating cache size”

(page 69).

The next table specifies the cache requirements for bind mode operations:

Table 4 Bind mode cache requirements

System Type

OPEN Systems

Mainframe (for example, 3390-3, 3390-9)

Type

RAID 5 (3390) or RAID 6

RAID 1, or external volumes

RAID 5 mainframe or RAID 6

Capacity SpecificationsRAID Level or Volume

Slot capacity: 264 KB Cache segment capacity: 16.5

KB Cache segments needed per

slot: 48 (slot capacity / cache segment capacity)

Slot capacity: 264 KB Cache segment capacity: 16.5

KB Cache segments needed per

slot: 32 (slot capacity / cache segment capacity)

Slot capacity: 66 KB Cache segment capacity: 16.5

KB Cache segments needed per

slot: 12 (slot capacity / cache segment capacity)

Note: Even though a mainframe track is 56 KB, because cache is divided into 16.5 KB segments, it requires 4 segments.

Cache Residency Cache Requirement

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

2 times the space required for user data: 1 slot = 2 × 264 KB = 528 KB = 32 cache segments

3 times the space required for user data: 1 slot = 3 × 66 KB = 198 KB = 12 cache segments

RAID 1 mainframe, or external volumes

Slot capacity: 66 KB Cache segment capacity: 16.5

KB Cache segments needed per

slot: 8 (slot capacity / cache segment capacity)

2 times the space required for user data: 1 slot = 2 × 66 KB = 132 KB = 8 cache segments

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

• During cache blockage that is caused by certain maintenance operations (for example, cache

upgrades) or by cache failure.

• If the storage system is powered off.

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

Bind mode 15

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

16 About performance monitoring

3 Interoperability of Performance Monitor and other products

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

Cautions and restrictions for monitoring

• Storage system maintenance

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

◦ 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 on, replacing, or removing MP blades

• Storage system power-off

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

• Microprogram replacement

After the microprogram is replaced, monitoring data is not stored until the service engineer releases the SVP from Modify mode. While the SVP is in Modify mode, inaccurate data is displayed.

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

To change the SVP time setting, first disable the monitoring switch, change the SVP time setting, and then re-enable the monitoring switch. After that, obtain the monitoring data. For details about the monitoring switch, see “Starting monitoring” (page 28).

• 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 23),

“Adding WWNs to ports” (page 23), and “Connecting WWNs to ports” (page 24).

Cautions and restrictions for monitoring 17

Cautions and restrictions for usage statistics

• Usage statistics for the last three months (93 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 storage system.

• In the short range, monitoring results are retained for the last 8 hours to 15 days depending

on the specified gathering interval. If the retention period has passed since a monitoring result was obtained, the previous result has been deleted from the storage system and cannot be displayed.

• When the monitoring switch is set to disabled, no monitoring data is collected. This applies

to both long-range and short-range data.

• 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 Time Range option to lengthen the collection interval. For details, see “Starting monitoring” (page 28).

• The monitoring data (short-range and long-range) may have a margin of error.

• If the SVP is overloaded, the system might require more time than the gathering interval allows

to update the display of monitoring data. If this occurs, some portion of monitoring data is not displayed. For example, suppose that the gathering interval is 1 minute. In this case, if the display in the Performance Management window is updated at 9:00 and the next update occurs at 9:02, the window (including the graph) does not display the monitoring result for the period of 9:00 to 9:01. This situation can occur when the following maintenance operations are performed:

◦ Adding, replacing, or removing cache memory.

◦ Adding, replacing, or removing data drives.

◦ Changing the storage system configuration.

◦ Replacing the microprogram.

• Pool-VOLs of Fast Snap, Snapshot, Thin Provisioning, and Thin Provisioning Z are not monitored.

NOTE: When you run the RAID Manager horctakeover or pairresync-swaps command for a Cnt

Ac-J pair or the BCM YKRESYNC REVERSE command for a Cnt Ac-J Z pair, the primary and secondary volumes are swapped. You can collect the before-swapped information immediately after you run any of the commands. Incorrect monitoring data will be generated for a short time but will be corrected automatically when the monitoring data gets updated. The incorrect data will also be generated when the volume used for a secondary volume is used as a primary volume after a Cnt Ac-J or Cnt Ac-J Z pair is deleted.

Using Performance Control

• Starting Performance Control. Ensure that the Time Range in the Monitor Performance window

is not set to Use Real Time. You cannot start Performance Control in real-time mode.

• I/O rates and transfer rates. Performance Control runs based on I/O rates and transfer rates

measured by Performance Monitor. Performance Monitor measures I/O rates and transfer rates every second, and calculates the average I/O rate and the average transfer rate for every gathering interval (specified between 1 and 15 minutes) regularly.

Suppose that 1 minute is specified as the gathering interval and the I/O rate at the port 1-A changes as illustrated in Graph 1. When you use Performance Monitor to display the I/O rate graph for 1A, the line in the graph indicates changes in the average I/O rate calculated every minute (refer to Graph 2). If you select the Detail check box in the Performance Monitor

18 Interoperability of Performance Monitor and other products

windows, the graph displays changes in the maximum, average, and minimum I/O rates in one minute.

Performance Control applies upper limits and thresholds to the average I/O rate or the average transfer rate calculated every gathering interval. For example, in the following figures in which the gathering interval is 1 minute, if you set an upper limit of 150 I/Os to the port 1A, the highest data point in the line CL1-A in Graph 2 and the line Ave.(1 min) in Graph 3 is somewhere around 150 I/Os. It is possible that the lines Max (1 min.) and Min (1 min.) in Graph 3 might exceed the upper limit.

Figure 3 Graph 1: actual I/O rate (measured every second)

Figure 4 Graph 2: I/O rate displayed in Performance Monitor (the Detail check box is not selected)

Figure 5 Graph 3: I/O rate displayed in Performance Monitor (the Detail check box is selected)

Using Performance Control 19

NOTE:

• Continuous Access Synchronous: Performance Control monitors write I/O requests issued from

initiator ports of your storage system.

• When the remote copy functions: (Continuous Access Synchronous, Continuous Access

Synchronous Z, Continuous Access Journal, and Continuous Access Journal Z) are used in your environment, Performance Control monitors write I/O requests issued from initiator ports of your storage system.

If you give a priority attribute to the RCU target port, all I/Os received on the port will be controlled as the threshold control and its performance data will be added to the total number of I/Os (or the transfer rate) of all prioritized ports. I/Os on the port will not be limited.

If you give a non priority attribute to the RCU target port, I/O requests from the initiator port will not be controlled as threshold control and I/Os on the port will not be limited. On the other hand, I/O requests from a host will be controlled as the upper limit control and I/Os on the port will be limited.

• Statistics of Initiator/External ports: The initiator ports and external ports of your storage system

are not controlled by Performance Control. Although you can set Prioritize or Non-Prioritize to initiator ports and external ports by using Performance Control, the initiator ports and the external ports become the prioritized ports that are not under threshold control, regardless of whether the setting of the ports are Prioritize or Non-Prioritize. If the port attributes are changed from Initiator/External into Target/RCU Target, the settings by Performance Control take effect instantly and the ports are subject to threshold or upper limit control.

The statistics of the Monitor Performance window are the sum of the statistics on Target/RCU Target ports that are controlled by Performance Control. The statistics do not include the statistics of Initiator/External ports. Because the statistics of Initiator/External ports and Target/RCU Target ports are based on different calculation methods, it is impossible to sum up the statistics of Initiator/External ports and Target/RCU Target ports.

• Settings of Performance Control main window: The Performance Control main window has

two tabs: the Port tab and the WWN tab. The settings on only one tab at a time can be applied to the storage system. If you make settings on both tabs, the settings cannot be applied at the same time. When you select Apply, the settings on the last tab on which you made settings are applied, and the settings on the other tab are discarded.

NOTE:

• Settings for Performance Control from RAID Manager: You cannot operate Performance Control

from RAID Manager and Remote Web Console simultaneously.If you change some settings for Performance Control from RAID Manager, you cannot change those settings from Remote Web Console. If you do, some settings might not appear. Before you change features that use Performance Control, delete all Performance Control settings from the currently used features.

WWN monitoring data

You must configure some settings before you start monitoring traffic between host bus adapters and storage system ports. For details, see topics between “Viewing the WWNs that are being

monitored” (page 23) and “Deleting unused WWNs from monitoring targets” (page 25).

Microprogram replacement

After the microprogram is replaced, the monitoring data is not stored until a service engineer releases the SVP from Modify mode. While the SVP is in Modify mode, inaccurate data is displayed.

20 Interoperability of Performance Monitor and other products

Changing the time setting of SVP

If the monitoring switch function is performed, do not change the time setting of the SVP. If the time setting is changed, the following problems can happen:

• Invalid monitoring data appears.

• No monitoring data is collected.

If the time setting of the SVP is changed, turn off the monitoring switch, and then turn on the switch. After that, obtain the monitoring data. For details about the monitoring switch, see “Starting

monitoring” (page 28).

Using Performance Control

• When starting Performance Control. Ensure that the Time Range in the Monitor Performance

window is not set to Use Real Time. You cannot start Performance Control in real-time mode.

• Performance Control runs based on I/O rates and transfer rates measured by Performance

Monitor. Performance Monitor measures I/O rates and transfer rates every second, and calculates the average I/O rate and the average transfer rate for each gathering interval (specified between 1 and 15 minutes).

Figure 6 Graph 1: actual I/O rate (measured every second)

Figure 7 Graph 2: I/O rate displayed in Performance Monitor (the Detail check box is not selected)

Changing the time setting of SVP 21

Figure 8 Graph 3: I/O rate displayed in Performance Monitor (the Detail check box is selected)

NOTE:

• Continuous Access Synchronous: Performance Control monitors write I/O requests issued from

initiator ports of your storage system.

• When the remote copy functions: (Continuous Access Synchronous, Continuous Access

• Statistics of Initiator/External ports: The initiator ports and external ports of your storage system

The statistics of the Monitor Performance window are sum total of statistics on Target/RCU Target ports that are controlled by Performance Control. The statistics does not include the statistics of Initiator/External ports. Because the statistics of Initiator/External ports and Target/RCU Target ports are based on different calculation methods, it is impossible to sum up the statistics of Initiator/External ports and Target/RCU Target ports.

• Settings of Performance Control main window: The settings in the Port tab or the WWN tab

are valid as the current settings in the Performance Control main window. All port settings in the invalid tab are invalid regardless of the resources that are assigned to you. You can confirm the current status in Current Control Status which appears in the upper right of the Performance Control main window.

NOTE:

• Settings for Performance Control from RAID Manager: You cannot operate Performance Control

22 Interoperability of Performance Monitor and other products

4 Monitoring WWNs

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

Viewing the WWNs that are being monitored

To view the WWNs that are being monitored:

1. Display the Remote Web Console main window.

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

3. Select the Monitored WWNs tab to see the list of WWNs that are currently being monitored.

Adding new WWNs to monitor

To add new WWNs to monitor:

1. Display the Remote Web Console main window.

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

3. Select the Monitored WWNs tab.

4. Click Edit WWN Monitor Mode. The Edit WWN Monitor Mode window opens.

5. Select the WWNs in the Unmonitored WWNs list, and click Add.

6. Click Finish to display the Confirm window.

7. Click Apply in the Confirm window to apply the settings to the storage system.

Removing WWNs to monitor

To remove WWNs to monitor:

1. Display the Remote Web Console main window.

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

3. Click the Monitored WWNs tab.

4. Click Edit WWN Monitor Mode. The Edit WWN Monitor Mode window opens.

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

6. Click Finish to display the Confirm window.

7. Click Apply in the Confirm window.

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

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.

1. Display the Remote Web Console main window.

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

3. Click the Monitored WWNs tab.

Viewing the WWNs that are being monitored 23

4. Click Add New Monitored WWNs. The Add New Monitored WWNs window opens.

5. Specify the following information for each new WWN:

• HBA WWN (required)

Enter the 16-digit hexadecimal number.

• WWN Name (optional)

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

• Port (In Available Ports)

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

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

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

8. When you are done adding new WWNs, click Finish.

9. Click Apply in the Confirm window to apply the settings to the storage system.

Editing the WWN nickname

To edit the nickname of a WWN being monitored:

1. Display the Remote Web Console main window.

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

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

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

The Edit WWN window opens.

5. 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 others. The WWN Name must be less than 64 digits and must consist of alphanumeric characters and at least one symbol.

6. Click Finish to display the Confirm window.

7. Click Apply in the Confirm window to apply the settings to the storage system.

Connecting WWNs to ports

To connect the WWNs to monitor to ports:

1. Display the Remote Web Console main window.

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

3. Click the Monitored WWNs tab.

24 Monitoring WWNs

4. Select the WWN to connect to the port, and click Add to Ports. The Add to Ports window opens. If you select a WWN to connect, select one WWN in the

list. If you select multiple WWNs and click Add to Ports, an error occurs.

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

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

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

WWNs are deleted.

7. Click Finish to display the Confirm window.

8. Click Apply in the Confirm window to apply the settings to the storage system.

Deleting unused WWNs from monitoring targets

To delete WWNs that are being monitored:

1. Display the Remote Web Console main window.

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

3. Click the Monitored WWNs tab.

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

5. Click Apply in the Confirm window.

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

Deleting unused WWNs from monitoring targets 25

5 Monitoring CUs

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

Displaying CUs to monitor

To display the list of CUs to monitor:

1. Open the Remote Web Console main window.

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

3. Open the Monitored CUs tab. View the list of CUs.

Adding or removing CUs to monitor

NOTE: When a CU is removed from monitoring, the monitor data for that CU is deleted. If you

want to save the data, export it first using the Export Tool (see “Export Tool” (page 86)), and then remove the CU.

1. Display the Remote Web Console main window.

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

3. Open the Monitored CUs tab.

4. Click Edit CU Monitor Mode. The Edit CU Monitor Mode window opens.

5. To add CUs as monitoring target objects, select the CUs in the Unmonitored CUs list, and click Add to move the selected CUs into the Monitored CUs list.

To add all CUs in a parity group as monitoring target objects:

1. Click Select by Parity Groups in the Unmonitored CUs area.

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

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

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

3. Confirm the properties of the parity group and click Close.

The Select by Parity Groups window opens.

4. Select the parity group to be the monitoring target in the Select by Parity Groups window,

and click OK. The CUs in the parity group are selected in the Unmonitored CUs list.

5. Click Add to move the selected CUs into the Monitored CUs list.

6. To remove CUs as monitoring target objects, select the CUs in the Monitored CUs list, and click Remove to move the selected CUs into the Unmonitored CUs list.

7. When you are done adding and/or deleting CUs, click Finish.

8. When the confirmation dialog box opens, click Apply. If you are removing CUs, a warning message appears asking whether you want to continue

this operation even though monitor data will be deleted.

9. To add and remove the CUs, click OK. The new settings are registered in the system.

Confirming the status of CUs to monitor

To view the monitoring status of CUs:

26 Monitoring CUs

1. Display the Remote Web Console main window.

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

3. Open the Monitored CUs tab.

4. Click Edit CU Monitor Mode. The Edit CU Monitor Mode window opens.

5. Click View CU Matrix in the Edit CU Monitor Mode window. The View CU Matrix window opens. The following CUs are displayed in the Monitored CUs

window:

• Monitored CUs

• Set monitored CUs

• Release monitored CUs

6. Click Close. The Edit CU Monitor Mode window opens.

Confirming the status of CUs to monitor 27

6 Monitoring operation

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

Performing monitoring operations

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

• To start the monitoring operation, see “Starting monitoring” (page 28).

• To stop the monitoring operation, see “Stopping monitoring” (page 28).

Starting monitoring

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

1. Display the Remote Web Console main window.

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

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

4. Click Enable in the Monitoring Switch field.

5. Select the collecting interval in the Sample Interval. Specify the interval to obtain usage statistics about the storage system for short range

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

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

6. Click Finish to display the Confirm window.

7. Click Apply in the Confirm window. A warning message appears, asking whether you continue this operation although graph

data is deleted.

8. Click OK to start monitoring. When statistics are collected, a heavy workload is likely to be placed on servers. Therefore,

the client processing might slow down.

Stopping monitoring

To stop monitoring the storage system:

1. Display the Remote Web Console main window.

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

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

28 Monitoring operation

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

5. Click Finish to display the Confirm window.

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

Stopping monitoring 29

7 Setting statistical storage ranges

This topic describes setting statistical storage ranges.

About statistical storage ranges

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

• Short range

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

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

• Long range

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

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

Viewing statistics

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

Setting the storing period of statistics

To set the storing period of statistics:

1. Display the Remote Web Console main window.

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

3. Click Monitor Performance in the Performance Monitor window. The Monitor Performance window opens.

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

30 Setting statistical storage ranges

+ 175 hidden pages