HP 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.
© Copyright 2014 Hewlett-Packard Development Company, L.P. 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.
Contents 1 Performance management...........................................................................8 Overview of performance management.......................................................................................8 System requirements..................................................................................................................8 2 Performance Monitor operations...................................................................9 Overview of Performance Monitor...........
CMR delay time.....................................................................................................................35 Disconnected time..................................................................................................................36 Connected time......................................................................................................................36 HTP port open exchanges......................................................................................
Bind mode (read and write data in cache)............................................................................72 Prestaging data in cache....................................................................................................73 Cache Residency system specifications......................................................................................74 Estimating cache size for Cache Residency................................................................................
apply.............................................................................................................................118 set.................................................................................................................................119 help...............................................................................................................................120 Java.......................................................................................................
Confirm window for Add New Monitored WWNs...............................................................175 Add to Ports wizard..............................................................................................................176 Add to Ports window........................................................................................................176 Confirm window for Add to Ports.......................................................................................179 Monitor window........
1 Performance management This chapter provides an overview of performance management of the HP XP7 Storage system and describes the system requirements. Overview of performance management The HP 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 storage system performance. • Performance Monitor.
2 Performance Monitor operations This chapter describes performance monitoring and provides instructions for performing performance monitoring operations using Performance Monitor. Overview of Performance Monitor Performance Monitor enables you to monitor your HP 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.
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.
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.
• ◦ 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 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.
the interval is changed. For instance, if the sampling interval is set or changed to 15 minutes, monitoring data is not accumulated for up to 29 minutes after this setting is made. • Display of monitoring data during high SVP workload If the SVP is overloaded, the system might require more time than the sampling interval allows to update the display of monitoring data. If this occurs, some portion of monitoring data is not displayed.
3. 4. 5. On the Performance Monitor window click Monitor Performance to open the Monitor Performance window. On the Monitor Performance window select Long-Range or Short-Range in the Data Range as the periods (ranges) for collecting and storing statistics. 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. 6.
• “Removing WWNs to monitor” (page 15) • “Adding WWNs to ports” (page 16) • “Editing the WWN nickname” (page 16) • “Connecting WWNs to ports” (page 17) • “Deleting unused WWNs from monitoring targets” (page 17) Adding new WWNs to monitor Prerequisites • Required role: Storage Administrator (Performance Management) To add new WWNs to monitor: 1. Display the Remote Web Console main window. 2.
4. 5. 6. 7. 8. On the Monitored WWNs tab click Edit WWN Monitor Mode to open the Edit WWN Monitor Mode window. Select the WWNs in the Monitored WWNs list that you want to remove, and click Remove. Enter your task name in Task Name, and click Finish. In the Confirm window click Apply. When the warning message appears, click OK to close the message. The settings are applied to the storage system.
2. 3. 4. 5. 6. Select Analytics in Explorer, and select Performance Monitor in the tree to open the Performance Monitor window. Click the Monitored WWNs tab to see the list of WWNs being monitored. Select the WWN to edit. You can edit only one WWN at a time. If you select multiple WWNs, an error will occur. On the Monitored WWNs tab click Edit WWN to open the Edit WWN window. On the Edit WWN window edit the HBA WWN and WWN Name fields as needed. • HBA WWN A 16-digit hexadecimal number.
1. 2. 3. 4. 5. Display the Remote Web Console main window. Select Analytics in Explorer, and select Performance Monitor in the tree to open the Performance Monitor window. Click the Monitored WWNs tab. On the Monitored WWNs tab click Deleted Unused WWNs to open the Deleted Unused WWNs window. In the Confirm window enter your task name in Task Name, and click Apply.
7. In the Confirm window enter your task name in Task Name, and click Apply. NOTE: To monitor a parity group, specify the CU numbers of all LDEVs belonging to the parity group. Otherwise the parity group is not subjected to monitoring. Related topics • “Edit CU Monitor Mode wizard” (page 161) Selecting CUs to monitor Prerequisites • Required role: Storage Administrator (Performance Management) To select the CUs to monitor: 1. Display the Remote Web Console main window. 2.
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: 6. • Monitored CUs • Set monitored CUs • Release monitored CUs Click Close. The Edit CU Monitor Mode window opens. Related topics • “View CU Matrix window” (page 164) Changing the sampling interval You can change the sampling interval for short-range monitoring.
3. 4. In the Performance Monitor window click Edit Monitoring Switch to open the Edit Monitoring Switch window. Click Disable in the Monitoring Switch field. The Sample Interval list is grayed out and becomes ineffective. 5. 6. Click Finish. In the Confirm window enter your task name in Task Name, and click Apply to stop monitoring.
2. 3. 4. 5. Select Analytics in Explorer, and select Performance Monitor in the tree to open the Performance Monitor window. In the Performance Monitor window click Monitor Performance to open the Monitor Performance window. 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.
Related topics • “Monitor Performance window” (page 148) • “Add Graph window” (page 195) • “Displaying the monitor data on graphs” (page 21) Changing the data displayed on a graph Prerequisites • Required role: Storage Administrator (Performance Management) To change the data displayed on a graph: 1. Display the Remote Web Console main window. 2. Select Analytics in Explorer, and select Performance Monitor in the tree to open the Performance Monitor window. 3.
Deleting a graph Prerequisites • Required role: Storage Administrator (Performance Management) To delete a graph from the graph panel: 1. Display the Remote Web Console main window. 2. Select Analytics in Explorer, and select Performance Monitor in the tree to open the Performance Monitor window. 3. Display the graph panel in the Monitor Performance window. For details, see “Displaying the monitor data on graphs” (page 21). 4. 5.
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. The monitoring data for each sampling interval is the average value of the data over the data sampling interval. For instructions on viewing the monitoring data, see “Using the Performance Monitor data graphs” (page 21).
Object of monitoring Monitoring data Read throughput (IOPS) Write throughput (IOPS) Cache hit (%) Data transfer (MB/s) Response time (ms) Back transfer (count/sec) Drive usage rate (%)1 Drive access rate (%)1 Business Copy usage rates (BC/BC Z) (%)1 LDEV (Cnt Ac-J/Cnt Ac-J Z) Write host I/O throughput (IOPS) Write host I/O data transfer (MB/s) Initial copy cache hit (%) Initial copy data transfer (MB/s) LDEV (Cnt Ac-S/Cnt Ac-S Z) RIO (count) Pair Synchronized (%) Differential track (count) Initial copy
Object of monitoring Monitoring data LUN (Cnt Ac-J)2 Write host I/O throughput (IOPS) Write host I/O data transfer (MB/s) Initial copy cache hit (%) Initial copy data transfer (MB/s) 2 LUN (Cnt Ac-S) RIO (count) Pair Synchronized (%) Differential track (count) Initial copy throughput (count) Initial copy data transfer (MB/s) Initial copy response time (ms) Update copy throughput (count) Update copy data transfer (MB/s) Update copy response time (ms) External storage Data transfer between HP XP7 Stor
Object of monitoring Monitoring data Restore journal journal (count/sec) Restore journal data transfer (MB/s) Restore journal response time (ms) Restore journal usage data (%) Restore journal meta data usage rate (%) Entire storage system (Cnt Ac-J/Cnt Ac-J Z) Write host I/O throughput (IOPS) Write host I/O data transfer (MB/s) Initial copy cache hit (%) Initial copy data transfer (MB/s) Master journal throughput (IOPS) Master journal journal (count/sec) Master journal data transfer (MB/s) Master journal
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, this can indicate high write penalty condition. Please consult your HP representative about high write penalty conditions.
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 Cache None Write Pending Rate (%) None Access path usage statistics Function The access paths are the paths through which data and commands are transferred within a storage system.
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 Storing period Short-Range can be specified.
Item on left side of Object field Item on right side of Object field Item on left side of Monitor Item on right side of Monitor Data field Data field Random CFW Read Throughput (IOPS) Total Sequential Random CFW Write Throughput (IOPS) Total Sequential Random CFW LUN3 Base Total Throughput (IOPS) Total Sequential Random CFW Read Throughput (IOPS) Total Sequential Random CFW Write Throughput (IOPS) Total Sequential Random CFW Initial copy Throughput (count)2 Update copy Throughput (count)2
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. 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 Fibre Port* None Data Trans.
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 Write Journal Entire Storage System Cnt Ac-J/Cnt Ac-J Z Cnt Ac-S/Cnt Ac-S Z Cnt Ac-J/Cnt Ac-J Z Write host I/O Data Trans. (MB/s) Initial copy Data Trans. (MB/s) Master journal Data Trans. (MB/s) Restore journal Data Trans. (MB/s) Initial copy Data Trans. (MB/s) Update copy Data Trans. (MB/s) Write host I/O Data Trans.
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 Parity Group* None Response Time (ms) Total Read Write LUN* Base Response Time (ms) Total Read Write Cnt Ac-S External Storage Parity Group Initial Copy Response Time (ms) Update Copy Response Time (ms) Response Time (ms) Total Read Write Logical Device Response Time (ms) Total Read Write Journal Entire Storage System Cnt Ac-J/Cnt Ac-
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. Storing period Short-Range can be specified. Selection of monitoring objects Select the desired monitoring objects in the Performance Objects field.
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 Item on right side of Monitor field Data field Mainframe Fibre Port* None HTP Port Open Exchanges (count/sec) None * Volumes that do not accept I/O from the host, such as pool-VOLs, are not monitored.
Item on left side of Object field Item on right side of Objecc Item on left side of Monitor field Data field Item on right side of Monitor Data field Parity Group* None Read (Total) Cache Hit (%) Read (Sequential) Read (Random) Read (CFW) Write (Total) Write (Sequential) Write (Random) Write (CFW) LUN* Base Cache Hit (%) Read (Total) Read (Sequential) Read (Random) Read (CFW) Write (Total) Write (Sequential) Write (Random) Write (CFW) Cnt Ac-J Initial Copy Cache Hit (%) Entire Storage System
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 Logical Device* Base Back Trans. (count/sec) Total Cache to Drive Drive to Cache (Sequential) Drive to Cache (Random) Parity Group* None Back Trans.
The rate of file reading Read (Random) or file writing Write (Random) processing of the data drive in the random access mode is displayed. Storing period Long-Range or Short-Range can be specified. Selection of monitoring objects Select the desired monitoring objects in the Performance Objects field.
Selection of monitoring objects Select the desired monitoring objects in the Performance Objects field.
Selection of monitoring objects Select the desired monitoring objects in the Performance Objects field.
Meta Data Usage Rate Function The meta data usage rate of the current journal is shown, with journal volume meta data space assumed to be 100%. Storing period Short-Range can be specified. Selection of monitoring objects Select the desired monitoring objects in the Performance Objects field.
4 Performance Control operations This chapter describes and provides instructions for managing host I/O activity using Performance Control. Overview of Performance Control Performance Control allows you to set upper limits of the number of accesses from the server to storage system as well as the amount of data transfer. The upper limits are automatically disabled when the traffic between the server and storage system drops to user-defined levels.
Related topics • “Overview of Performance Control” (page 44) Threshold control While upper-limit control can help production servers to perform at higher levels during periods of heavy use, it may not be desirable when production servers are not busy. For example, if the I/O activity on production servers is high between 09:00 and 15:00 hours and decreases significantly after 15:00, upper-limit control for development servers may not be required after 15:00.
Figure 1 Graph 1: actual I/O rate (measured every second) Figure 2 Graph 2: I/O rate displayed in Performance Monitor Figure 3 Graph 3: detailed I/O rate displayed in Performance Monitor Related topics • “Overview of Performance Control” (page 44) Use cases for Performance Control This section describes the use cases for implementing Performance Control on the HP XP7 Storage system: • “Use case for one-to-one connections” (page 46) • “Use case for many-to-many connections” (page 48) Use case for on
Figure 4 Network A: 1-to-1 connections between HBAs and ports In Network A, ports 1A and 1C are connected to high-priority production servers. Port 2A is connected to a low-priority development server. Therefore, high priority (Prio.) is set to ports 1A and 1C, and low priority (Non-Prio.) is set to port 2A. The following figure shows the priority settings for these ports on the Port tab of the Performance Control main window. The I/O traffic at the ports is now monitored.
If you want to allow improved performance for non-prioritized ports when system activity is low, you can apply a threshold. For one-to-one connections threshold values can be set in either of the following two ways: • Set a threshold to each prioritized port.
Figure 5 Network B: many-to-many connections between HBAs and ports First, the priority for the host adapters is set using the WWN tab of the Performance Control main window. In Network B, the production server is high priority (Prio.), and the development server is low priority (Non-Prio.). The following figure shows the priority settings for these WWNs on the WWN tab of the Performance Control main window.
Figure 7 Host adapters being monitored The I/O traffic between the ports and host adapters is now monitored. When the desired amount of data has been collected, the traffic statistics are reviewed on graphs using the Performance Monitor window. The following graph shows the measured I/O rate for the paths between each port and the host adapters.
Figure 9 Upper limits for non-prioritized WWNs in Network B After upper limits have been applied, the traffic is measured again to check the result of the upper limits and see whether host performance has improved to a desirable level, in this case 400 IO/s for wwn01. If not, you can adjust the upper limit to a smaller value until the I/O rate for wwn01 reaches the desirable level. If you want to allow higher performance for non-prioritized WWNs when system activity is low, you can apply a threshold.
If you set the non-priority attribute to an RCU target port, I/O requests from the initiator port are not controlled by threshold control, and I/Os on the port will not be limited. On the other hand, I/O requests from a host are controlled by upper limit control, and I/Os on the port will be limited. • Statistics for initiator/external ports The initiator ports and external ports of your storage system are not controlled by Performance Control.
Performance Control workflow: one-to-one connections The workflow for Performance Control depends on the connection between the host adapters and the ports. When one-to-one connections are established between host adapters and ports, you can manage the priority of I/O operations on each port. You can specify upper limit values on the non-prioritized ports. You can also specify threshold values on the prioritized ports or apply one threshold value to the entire storage system.
8. 9. Right-click a lower-priority port and in the pop-up menu select Prio ->> Non-Prio. The Attribute column displays Non-Prio. Repeat this action for each lower-priority port. You can set upper limit values only on the Non-prio. ports. Click Apply to apply the settings to the storage system. Now that you have set the port priorities, you can start monitoring the traffic (I/O rates and transfer rates) to collect data for analysis.
When you set an upper limit for the first time, it is recommended that the upper limit value be approximately 90 percent of the peak traffic. Prerequisites • Required role: Storage Administrator (System Resource Management) • You must enable the Remote Web Console secondary window. For details, see the HP XP7 Remote Web Console User Guide. Display the Remote Web Console main window. Click Reports > Performance Monitor > Performance Control to open the Performance Control window. 1. 2. 3. 4. 5. 6. 7.
Setting a threshold: one-to-one connections When one-to-one connections are established between HBAs and ports, you can set a threshold value for each prioritized port or one threshold value for the entire storage system. When traffic between high-priority servers and the ports or storage system falls below the specified threshold level, upper limit control is disabled to allow higher performance on non-prioritized ports during periods of low activity on prioritized ports.
Related topics • “Performance Control workflow: one-to-one connections” (page 53) • “Performance Control window” (page 208) • “Port tab of the Performance Control main window” (page 209) Implementing Performance Control: many-to-many connections This section describes and provides instructions for implementing Performance Control for many-to-many connections.
Setting priority for WWNs: many-to-many connections If many-to-many connection is established between HBAs and ports, you need to define the priority of WWNs, measure the traffic between the HBAs and the ports that the HBAs are connected to, and analyze the traffic data. The HBAs are divided into two types: prioritized WWNs and non-prioritized WWNs. Specify an HBA on which high-priority processing is performed as a prioritized WWN.
14. In the Performance Control main window click Apply to apply the settings to the storage system. For instructions on measuring traffic (that is, I/O rates and transfer rates), see “Starting monitoring” (page 14).
NOTE: It is recommended that you specify the same names for the PFC names and the host adapter nicknames defined in LUN Manager for convenience of host adapter management. In the Performance Monitor window, both the PFC names and the nicknames are displayed as the aliases of host adapters (WWNs), so if you use the same names, management of the host adapters is easier. 11. Click OK. The selected WWN (of the host adapter) is moved from Non-Monitor to Monitor.
8. 9. Double-click Monitor below the specified port. Right-click the WWN of a host adapter you want to exclude from the monitoring target and then select Delete WWN from the pop-up menu. If the selected host adapter is connected to multiple ports, when you select the host adapter and select the Delete WWN pop-up menu, a message will appear that asks you whether to move the host adapter from Monitor to Non-Monitor below all other ports, too.
The following two types of traffic are shown. The traffic has attributes including the average and maximum values. • Traffic between the host adapter and the selected port (shown in Per Port) • Sum of the traffic between the host adapter and all ports connected to the host adapter (shown in WWN Total) The traffic statistics only about the host adapters below Monitor appear in the list. The WWN Total traffic statistics will also be displayed in the list when you click an icon in the lower left tree.
3. 4. 5. 6. 7. Click to change to Modify mode. In the Performance Control window, click Performance Control. The Performance Control main window appears. Ensure that the WWN tab is displayed. Do one of the following: • To limit the I/O rate of the non-prioritized WWN, select IOPS from the list at the upper left corner. • To limit the transfer rate of the non-prioritized WWN, select MB/s from the list at the upper left corner.
If many-to-many connections are established between host adapters and storage system ports, you can set one threshold value for the entire storage system. In this environment, you cannot set individual threshold values for each prioritized WWN. Prerequisites • Required role: Storage Administrator (System Resource Management) • You must enable the Remote Web Console secondary window. For details, see the HP XP7 Remote Web Console User Guide. Display the Remote Web Console main window.
For details about assigning PFC names, see “Monitoring all port-HBA traffic: many-to-many connections” (page 59). Prerequisites • Required role: Storage Administrator (System Resource Management) • You must enable the Remote Web Console secondary window. For details, see the HP XP7 Remote Web Console User Guide. Display the Remote Web Console main window. Click Reports > Performance Monitor > Performance Control to open the Performance Control window. 1. 2. 3. 4. 5. 6. 7. 8. 9.
2. Click Reports > Performance Monitor > Performance Control to open the Performance Control window. 3. 4. Click to change to Modify mode. In the Performance Control window, click Performance Control. The Performance Control main window appears. Select the WWN tab. 5. 6. 7. 8. In the upper-left tree, select the old host adapter ( ) from below Monitor and then right-click the selection. From the pop-up menu, select Change WWN and PFC Name. The Change WWN and PFC Name window opens.
Creating a PFC group Prerequisites • Required role: Storage Administrator (System Resource Management) • You must enable the Remote Web Console secondary window. For details, see the HP XP7 Remote Web Console User Guide. A host adapter can belong to only one PFC group. To create a PFC group and add host adapters to the group: 1. Display the Remote Web Console main window. 2. Click Reports > Performance Monitor > Performance Control to open the Performance Control window. 3. 4. 5. 6. 7. 8.
2. Click Reports > Performance Monitor > Performance Control to open the Performance Control window. 3. 4. Click to change to Modify mode. In the Performance Control window, click Performance Control. The Performance Control main window appears. Select the WWN tab. 5. 6. In the lower-left tree, double-click the PFC group ( deleted. 7. 8. Below the PFC icon, right-click the icon the host adapter ( Select Delete WWN from the pop-up menu. ) that contains the host adapter to be ) you want to delete.
Related topics • “WWN tab of the Performance Control main window” (page 211) Setting an upper-limit value to HBAs in a PFC group If all host adapters in a PFC group are non-prioritized WWNs, you can set an upper limit value to HBA performance (i.e., I/O rate or transfer rate). You can assign one upper limit value for one PFC group. For example, suppose that the upper limit value 100 IOPS is assigned to a PFC group consisting of four host adapters.
8. In the Performance Control main window, click Apply to apply the settings to the storage system. To confirm an upper limit value specified for each PFC group, select the Storage System folder in the lower-left tree on the WWN tab. The PFC groups are displayed in the list and you can confirm each upper limit value.
4. 5. 6. 7. 8. In the Performance Control window, click Performance Control. The Performance Control main window appears. Select the WWN tab. In the lower-left tree, select and right-click a PFC group ( ). Select Delete PFC Group from the pop-up menu. In the Performance Control main window, click Apply to apply the settings to the storage system.
5 Cache Residency Manager operations This chapter provides instructions for managing data in cache using the Cache Residency Manager software. Overview of Cache Residency 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.
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.
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.
Cache Residency cache areas For OPEN-V volumes, the resident cache areas are defined in logical blocks using logical block addresses (LBAs), with a minimum size of 512 LBAs (equivalent to 264 KB). In most cases you will assign an entire open-systems volume for cache residency. For mainframe volumes, the resident cache areas are defined on contiguous tracks with a minimum size of one cache slot (or track) (equivalent to 66 KB) and a maximum size of one LVI.
If priority mode or bind mode is used, the cache size is calculated assuming that one slot has the following values. • • For open-systems volumes: ◦ For OPEN-V, one slot is 264 KB (512 LBAs). ◦ For other than OPEN-V, one slot is 66 KB (128 LBAs). For mainframe (3390) volumes: ◦ One slot is 66 KB (128 LBAs).
1. Calculate the converted values of the starting address and the ending address. For all specified LDEVs: 1. For OPEN-V: Number of LBAs = LDEV size (KB) × 2 Convert the LDEV size to the number of LBAs. Number of slots = ceil(Number of LBAs / 512) ceil(): Round up the value that is calculated from the formula. Converted value of starting address = 0 Converted value of ending address = (Number of slots × 512) - 1 2.
1. For OPEN-V: Number of addresses = Converted value of ending address Converted value of starting address + 1 Calculate the number of LBAs that are used by the user data. 2. For emulation types other than OPEN-V: Number of LBAs = Converted value of ending address - Converted value of starting address + 1 Calculate the number of LBAs that are used by the user data. Number of slots = Number of LBAs / 96 Convert the number of LBAs to the number of slots.
2. Calculate the required cache size according to the Cache Residency operation mode: 1. Bind mode: Required cache size (in KB) = (Number of slots × ((128 × (512 + 16)) × 3) / 1,024 2. Priority mode: Required cache size (in KB) = (Number of slots × (128 × (512 + 16))) / 1,024 If the area is changed from priority mode to bind mode and no cache is added, then only 33% of the user data will fit in the area previously assigned for priority mode, and the remaining 67% is used to save read/write data.
• Host I/O response time Performing Cache Residency operations on many LDEVs during host I/O may slow the host I/O response time. To avoid degradation of response time, set only one LDEV at a time. Deleting data from cache during host I/O may cause the response time of host I/O to become slow.
the power supply again, the prestaging process is aborted. If the prestaging process is aborted, you need to perform the prestaging operation again. • Access before completion of the prestaging operation 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.
6. Select an unallocated area in the LDEV information table as the area to place specific data from one or more LDEVs into Cache Residency cache. The starting and ending addresses of the selected area appear in the Start and End fields. NOTE: For OPEN-V LUs, Cache Residency identifies a logical area in units of 512 blocks. If you enter 0 or 1 as the starting LBA and a value less than 511 as the ending LBA, Cache Residency automatically changes the ending block address to 511. 7.
3. Click Set to return to the Cache Residency window. The requested Cache Residency operations appear in blue in the LDEV information table. CAUTION: Prestaging cannot be set to the following volumes. As a result, even if Yes is set for Prestaging Mode and the Multi Set/Release box is checked, these volumes are not displayed in the Multi Set window. • Thin Provisioning volume • Smart Tiers volume • Thin Provisioning Z volume • Smart Tiers Z volume 9.
3. Check the Select All Area box. Leave the Start and End fields blank. CAUTION: Make sure to select the correct options, because the options cannot be changed after a cache area is added. To change between bind and priority modes, or to enable and disable the prestaging function, you must release the cache area that you want to change and then place the data back into cache with the desired settings. 7.
5. In the CU:LDEV tree, select the LDKC and the CU containing the desired LDEV, and then select the desired LDEV. The LDEV information table shows the information for the selected LDEV. The Mode column indicates PRIO or BIND for each data area that is allocated to Cache Residency cache. 6. 7. Select the data areas that you want to release from Cache Residency cache. This enables the Release. Click Release, and click OK on the confirmation message.
1. Check the Multi Set / Release box, click Release, and then click OK on the confirmation message. 2. In the Multi Release dialog box, select the desired LDKC and CU image, and select the desired LDEVs to release from Cache Residency cache. Click Release to return to the Cache Residency window. The requested Cache Residency operations appear in blue in the LDEV information table. 3. 7. Repeat steps (2) and (3) until all desired operations are listed. NOTE: 8. 9.
For instructions on releasing data from cache, see “Releasing specific data from cache” (page 84) and “Releasing LDEVs from cache” (page 85). For instructions on placing data into cache, see “Placing specific data into cache” (page 81) and “Placing LDEVs into cache” (page 83).
6 Troubleshooting This chapter provides troubleshooting and contact information for HP Technical Support. General troubleshooting resources For troubleshooting information on the HP XP7 Storage system, see the HP XP7 Owner Guide. For troubleshooting information on the Remote Web Console software, see the HP XP7 Remote Web Console User Guide. For information on Remote Web Console error codes, see the HP XP7 Remote Web Console Messages.
Error Recommended action If the host timeout period is set to 11 seconds or longer, limit the total amount of data in one operation to: • 3 GB or less for open systems • 3,000 cylinders or less for mainframe systems Cache Residency is not available. The remaining cache memory after the cache residency operation will be less than 512 MB. Select less data to place in cache, or install additional cache memory.
7 Exporting Performance Monitor data This appendix describes and provides instructions for export the Performance Monitor data for your HP XP7 Storage system using the Export Tool for use in spreadsheet and other applications. About the Export Tool Use the Export Tool to export the monitoring data (statistics) shown in the Monitor Performance window to text files.
NOTE: If a firewall exists between the Remote Web Console computer and the SVP, see Chapter 2 of the HP 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 the Export Tool. • Java Runtime Environment (JRE) software To use the Export Tool, you must have the JRE software on your Windows or UNIX computer.
5. Double-click export.exe to start the installation. The Export Tool is installed, and a new folder named “export” is created. NOTE: We recommend that you delete runUnix.bat from the export folder because this file is no longer needed. On UNIX The Export Tool program is a Java class file and is located in the lib directory. 1. Log on as a superuser. You do not need to remove a previous installation of Export Tool. The new installation overwrites the older program. 2. 3. 4. 5.
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 SVP whose IP address is 158.214.135.57. You must log into SVP when using the Export Tool. The svpip subcommand specifies the IP address of SVP. You must include the svpip subcommand in your command file.
in short range is exported. But you can direct to export monitoring data stored in long range when you specify some of the operands. The example script group PhyPG Long in “Preparing a command file” (page 92) 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 Z in short range.
The outpath subcommand specifies the directory in which files should be saved. For detailed information about the outpath subcommand, see “outpath” (page 117). • option compress This script specifies that the Export Tool should compress monitoring data in ZIP files. The option subcommand specifies whether to save files in ZIP format or in CSV format. For detailed information about the option subcommand, see “option” (page 118). • apply The apply subcommand saves monitoring data in files.
Example of specifying a proxy host on Windows (runWin.bat): java -classpath "./lib/JSanExport.jar;./lib/JSanRmiApiEx.jar;./lib/JSanRmiServerUx.jar" -Dhttp.proxyHost=Jupiter -Dhttp.proxyPort=8080 -Xmx536870912 -Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain pause Example of specifying a proxy host on UNIX (runUnix.bat): #! /bin/sh java -classpath "./lib/JSanExport.jar:./lib/JSanRmiApiEx.jar:./lib/JSanRmiServerUx.jar" -Dhttp.proxyHost=Jupiter -Dhttp.
Target = 16, Total = 16 +----+----+----+----+----+----+----+----+----+----+ ...........................! ................................. End gathering port data By default, the system compresses monitoring data files into a ZIP-format archive file. When you want to view the monitoring data, you can decompress and extract the CSV files from the ZIP archive. If the operating system on your computer does not include a way to extract files from a ZIP archive, you need to obtain software to view the data.
Table 5 Estimate of time required for exporting files (continued) Operand for the group Estimated time subcommand Remarks 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 104).
Error handling When an internal error occurs during export processing, an exclamation mark (!) appears to signal an error. By default, the Export Tool makes up to three more attempts at processing. You can change the maximum number of retries by using the retry subcommand. For detailed information about the retry subcommand, see “retry” (page 102). If export processing does not finish within three retries or if an internal error occurs other than those listed in the following table, the Export Tool stops.
• “Writing a script in the command file” • “Viewing the online Help for subcommands” Conventions The following conventions are used to explain syntax: Convention Description bold Indicates characters that you must type exactly as they are shown. italics Indicates a type of an operand. You do not need to type characters in italics exactly as they are shown. [] Indicates one or more operands that can be omitted.
Viewing the online Help for subcommands You can display the online Help to view the syntax of subcommands when you are working at the command prompt. To be able to view the online Help, you must use the help subcommand of the Export Tool. For more information about how to use the help subcommand, see “help” (page 120). Subcommand list Subcommand Function “svpip” (page 101) Specifies the IP address of SVP to be logged in. “retry” (page 102) Makes settings on retries of export processing.
Example The following example specifies the IP address of SVP as 158.214.127.170. svpip 158.214.127.170 retry Description This subcommand makes settings on retries of export processing. When an internal error occurs during export processing, the Export Tool stops processing and then retries export processing. By default, the Export Tool can retry processing up to three times, but you can change the maximum number of retries by using the retry subcommand.
Operand Description If the user ID includes any non-alphanumeric character, the user ID must be enclosed by double quotation marks ("). Be sure to specify a user ID that should be used exclusively with the Export Tool. For detailed information, see “Requirements for the Export Tool” (page 90). password Specifies the password of the user. If the password includes any non-alphanumeric character, the password ID must be enclosed by double quotation marks (").
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 the Export Tool, you can export the monitoring data within these periods into files. If you use the short-range or long-range subcommand additionally, you can narrow the term of data to be exported (see “Short-range” (page 113) or “long-range” (page 115)).
Table 7 Operands of the group subcommand and saved monitoring data (continued) Operand GUI operation Monitoring data saved in the file Saved ZIP file See field in Monitor Performance window. LDEVEachOfCU Select Logical Device/Base from Object list in Performance Objects field in Monitor Performance window. Statistics about volumes in LDEVEachOfCU_dat/LDEV_XXXXX.
Table 7 Operands of the group subcommand and saved monitoring data (continued) Operand GUI operation Monitoring data saved in the file Saved ZIP file See UniversalReplicator Select Entire Storage System Cnt Ac-J/Cnt Ac-J Z from Object list in Performance Objects field in Monitor Performance window Statistics about remote UniversalReplicator.
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-CUid]][…]|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.
Operand Description 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 Use this operand when you want to export statistics about external volume groups, which are [[exg-id]:[exg-id]][…] displayed in the Monitor Performance window. When statistics are exported to a ZIP file, the file name will be PhyExG_dat.ZIP.
Operand Description 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. PG Use this operand when you want to export statistics about parity groups, external volume groups, p[a[rity-group-id|V-VOL-group-id|exg-id|Migration-Volume-group-id :] or migration volume groups which are displayed in the Monitor Performance window.
Operand Description Ensure that the LDKC-CU-id value on the left of the colon is smaller than the LDKC-CU-id value on the right of the colon. For example, you can specify LDEVEachOfCU 000:105, but you cannot specify LDEVEachOfCU 105:000. If internal is specified, you can export statistics about volumes in the parity group. If virtual is specified, you can export statistics about volumes in the external volume group, V-VOL, or migration volume group.
Operand Description U p L[o [rt-name.host-group-idp ] [o :rt-name.host-group-i … [d ]]] 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 16 (page 130). When you specify variables port-name.host-group-id, you can narrow the range of LU paths whose monitoring data are to be exported.
Operand Description 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][…]| Use this operand when you want to export statistics about remote copy operations of Continuous Access Synchronous and Continuous Access Synchronous Z.
Operand Description URLDEV Use this operand when you want to export statistics about remote copy operations which of Cnt [LDKC-CU-id]:[LDKC-CU-id][…] Ac-J and Cnt Ac-J Z. By using this operand, you can export monitoring data about remote copy operations performed by Continuous Access Journal and Continuous Access Journal Z 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.
Tool without specifying the short-range subcommand, the data stored in the whole monitoring term will be exported. The login subcommand must execute before the short-range subcommand executes. Syntax short-range [[yyyyMMddhhmm][{+|-}hhmm]:[yyyyMMddhhmm][{+|-}hhmm]] Operands The value on the left of the colon (:) specifies the starting time of the period. The value on the right of the colon specifies the ending time of the period.
Operand Description 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. short-range 201301010930:201301011730 The Export Tool saves monitoring data within the range of Jan. 1, 9:30-17:30. short-range 201301010930: The Export Tool saves monitoring data within the range of Jan. 1, 9:30 to Jan. 2, 00:00.
Monitoring Data Operands of the group subcommand Usage statistics about MPs and data recovery and reconstruction processors PhyProc Long Usage statistics about access paths and write pending rate PhyCMPK Long If you run the Export Tool without specifying the long-range subcommand, the data stored in the whole monitoring term will be exported. The login subcommand must execute before the long-range subcommand executes.
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. long-range 201301010930:201301011730 The Export Tool saves monitoring data within the range of Jan. 1, 9:30-17:30. long-range 201301010930: The Export Tool saves monitoring data within the range of Jan. 1, 9:30 to Jan. 2, 00:00. longrange:201301011730 The Export Tool saves monitoring data within the range of Jan.
Examples The following example saves files in the directory C:\Project\out on a Windows computer: outpath "C:\\Project\\out" The following example saves files in the out directory in the current directory: outpath out option Description This subcommand specifies the following: • whether to compress monitoring data in ZIP files • whether to overwrite or delete existing files and directories when saving monitoring data in files Syntax option [compress|nocompress] [ask|clear|noclear] Operands Operand D
set Description The set subcommand starts or ends monitoring the storage system (for example, starts or ends collecting performance statistics). The set subcommand also specifies the sampling interval (interval of collecting statistics) in short range monitoring. If you want to use the set subcommand, you must use the login subcommand (see “login” (page 102) to log on to SVP. Ensure that the set subcommand executes immediately before the Export Tool finishes.
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 help Description The help subcommand displays the online help for subcommands.
Operand Description The path must be enclosed in double quotation marks ("). property-parameters You can specify the following parameters. At minimum you must specify -Dmd.command. • -Dhttp.proxyHost=host-name-of-proxy-host, or -Dhttp.proxyHost=IP-address-of-proxy-host Specifies the host name or the IP address of a proxy host. You must specify this parameter if the computer that runs the Export Tool communicates with SVP via a proxy host. • -Dhttp.
-Dmd.rmitimeout=20 -Dmd.logpath=log sanproject.getmondat.RJMdMain In the following example, a log file named export.log will be created in the log directory below the current directory when the Export Tool executes: java -classpath "./lib/JSanExport.jar;./lib/JSanRmiApiEx.jar; ./lib/JSanRmiServerUx.jar" -Xmx536870912 -Dmd.command=command.txt -Dmd.logfile=export.log -Dmd.logpath=log sanproject.getmondat.RJMdMain In the above script, indicates the end of a command line.
Table 8 Performance management windows and monitoring data saved by the Export Tool (continued) GUI operation Monitoring data Select Fibre Port from Object list in Performance Objects “Port statistics” (page 129) field in Monitor Performance window. Select Mainframe Fibre Port from Object list in Performance Objects field in Monitor Performance window.
Table 9 Files with resource usage and write pending rate statistics (continued) ZIP file CSV file Data saved in the file PHY_ExG_Read_Response.csv If external storage volumes are mapped to the volume groups of HP XP7 Storage, this file includes the average read response time for the volume groups including external storage volumes (milliseconds). PHY_ExG_Write_Response.
Table 9 Files with resource usage and write pending rate statistics (continued) ZIP file CSV file Data saved in the file PHY_Short_DKA_CMPK.csv Usage rates for access paths between disk adapters and CM packages in short range PHY_Long_MPPCB_CMPK.csv Usage rates for access paths between MP blades and CM packages in long range PHY_Short_MPPCB_CMPK.csv Usage rates for access paths between MP blades and CM packages in short range PHY_Long_CMPK_Cache.
Table 10 Files with parity group and external volume group statistics (continued) ZIP file CSV file Data saved in the file PG_CFW_Read_IOPS.csv Number of read operations in "cache-fast-write" mode per second PG_Write_IOPS.csv Number of write operations per second PG_Seq_Write_IOPS.csv Number of sequential write operations per second PG_Rnd_Write_IOPS.csv Number of random write operations per second PG_CFW_Write_IOPS.
Table 11 Files with statistics about volumes in parity/external volume groups ZIP file CSV file Data saved in the file LDEV_dat/LDEV_IOPS.ZIP LDEV_IOPS_x-y.csv Number of read and write operations per second LDEV_dat/LDEV_TransRate.ZIP LDEV_TransRate_x-y.csv Size of data transferred per second (KB/sec) LDEV_dat/LDEV_Read_TransRate.ZIP LDEV_Read_TransRate_x-y.csv Size of read data transferred per second (KB/sec) LDEV_dat/LDEV_Read_TransRate.ZIP LDEV_Write_TransRate_x-y.
Table 11 Files with statistics about volumes in parity/external volume groups (continued) ZIP file CSV file LDEV_dat/LDEV_Write_Response.ZIP LDEV_Write_Response_x-y.csv Data saved in the file Average write response time (microseconds) at volumes Note: The letters "x-y" in CSV filenames indicate a parity group. For example, if the filename is LDEV_IOPS_1-2.csv, the file contains the I/O rate for each volume in the parity group 1-2.
Table 12 Files with statistics about volumes in parity groups or external volume groups (at volumes controlled by a particular CU) (continued) ZIP file CSV file Data saved in the file LDEVEachOfCU_dat/LDEV_Rnd_Read_Hit.ZIP LDEV_Rnd_Read_Hitxx.csv The read hit ratio in random access mode LDEVEachOfCU_dat/LDEV_CFW_Read_Hit.ZIP LDEV_CFW_Read_Hitxx.csv The read hit ratio in "cache-fast-write" mode LDEVEachOfCU_dat/LDEV_Write_Hit.ZIP LDEV_Write_Hitxx.
Table 14 Files with statistics about mainframe ports ZIP file CSV file Data saved in the file MF_Port_dat.ZIP MF_Port_IOPS.csv The number of read and write operations per second measured at every port MF_Port_Response.csv Response time per port (in microseconds) MF_Port_Read_Write_KBPS.csv Read/write data transfer amount per port (in KB/sec) MF_Port_Read_KBPS.csv Read data transfer amount per port (in KB/sec) MF_Port_Write_KBPS.csv Write data transfer amount per port (in KB/sec) MF_Port_Avr_CMR.
Table 16 Files with statistics about volumes (LUs) (continued) ZIP file CSV file Data saved in the file LU_Write_Response.csv The average write response time (microseconds) LU_Seq_Read_IOPS.csv The number of sequential read operations per second LU_Rnd_Read_IOPS.csv The number of random read operations per second LU_Seq_Write_IOPS.csv The number of sequential write operations per second LU_Rnd_Write_IOPS.csv The number of random write operations per second LU_Seq_Read_Hit.
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 the Export Tool. The file contains statistics about usage rates of MPs. Table 18 MP usage rate of each resource allocated to MP blades ZIP file CSV file Data saved in the file PhyMPPK_dat.ZIP PHY_MPPK_x.y.
Remote copy operations by Cnt Ac-S and Cnt Ac-S Z (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 Cnt Ac-S Z window that can be exported to files using the Export Tool. These files contain statistics about remote copy operations (for each volume (LU)) by Continuous Access Synchronous and Continuous Access Synchronous Z.
Table 21 Files with statistics about remote copy operations by Cnt Ac-S and Cnt Ac-S Z (at volumes controlled by a particular CU) (continued) ZIP file CSV file Data saved in the file RCLDEV_dat/RCLDEV_Initial_Copy_Transfer.ZIP RCLDEV_Initial_Copy_Transfer_xx.csv The average transfer rate (KB/sec) for initial copy remote I/Os RCLDEV_dat/RCLDEV_Initial_Copy_Response.ZIP RCLDEV_Initial_Copy_Response_xx.
Table 22 Files with statistics about remote copy operations by Cnt Ac-J and Cnt Ac-J Z (In the whole volumes) (continued) ZIP file CSV file Data saved in the file • The remote I/O average response time (milliseconds) on the primary storage system • The number of asynchronous remote I/Os per second at the secondary storage system • The number of journals at the secondary storage system • The average transfer rate (KB/sec) for journals in the secondary storage system • The remote I/O average response time (
Remote copy by Cnt Ac-J and Cnt Ac-J Z (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 and Cnt Ac-J Z window that can be exported to files using the Export Tool. These files contain statistics about remote copy operations (for each volume (LU)) by Continuous Access Journal and Continuous Access Journal Z.
Causes of Invalid Monitoring Data If the value of monitoring data in CSV files is less than 0 (zero), consider the following causes: Invalid values of monitoring Probable causes data The monitoring data in the The value (-1) indicates that Performance Monitor failed to obtain monitoring data. Probable CSV file includes (-1). reasons are: • Performance Monitor attempted to obtain statistics when an operation for rebooting the disk array is in progress.
Troubleshooting the Export Tool The following table explains possible problems with the Export Tool and probable solutions to the problems. Possible problems Probable causes and recommended action You cannot run the batch file. The path to the Java Virtual Machine (Java.exe) might not be defined in the PATH environment variable. If this is true, you must add that path to the PATH environment variable.
Possible problems Probable causes and recommended action When a CSV file is opened, the To display a CSV file correctly, you need to perform following operations: parity group ID and volume ID 1. Start Microsoft Excel. appear as follows: 2. On the menu bar, select Data, Import External Data, and Import Text File, and • The parity group IDs appear specify a CSV file to import. The Text Import.zip - Step 1 of 3 dialog box is displayed as dates 3. In the Text Import.zip - Step 1 of 3 dialog box, click Next.
Export Tool messages Probable causes and recommended action Missing host name No host name is specified. Specify a host name. Missing output directory No directory is specified for saving files. Specify the directory for saving files. Missing password The Export Tool cannot find the user ID, which is used to log into SVP. Specify the password. Missing svpip The svpip subcommand is not used. Use the svpip command. Missing time range Specify the time range.
Export Tool messages Probable causes and recommended action Start gathering group data Target = xxx, Total = yyy End gathering group data The Export Tool starts collecting data specified by the group subcommand. The number of target objects is xxx and the total number is yyy (see Note below). The Export Tool ends collecting data.
8 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
HP websites For additional information, see the following HP websites: • http://www.hp.com • http://www.hp.com/go/storage • http://www.hp.com/service_locator • http://www.hp.com/support/manuals • http://www.hp.com/support/downloads • http://www.hp.
Table 26 Document conventions (continued) Convention Element Monospace text • File and directory names • System output • Code • Commands, their arguments, and argument values Monospace, italic text • Code variables • Command variables Monospace, bold text WARNING! CAUTION: IMPORTANT: NOTE: TIP: Emphasized monospace text Indicates that failure to follow directions could result in bodily harm or death. Indicates that failure to follow directions could result in damage to equipment or data.
A Performance Monitor GUI reference This chapter provides detailed information about the Performance Monitor GUI. Performance Monitor main window This is the main window for monitoring performance on your storage system. From this window you can set up monitoring parameters, start and stop monitoring, and view performance graphs. To open this window, select Performance Monitor in the Remote Web Console main window.
Buttons Item Description Performance Control Click to open the Performance Control window, which allows you to prioritize/non-prioritize ports and WWNs and to create WWN monitor groups. Monitor Performance Click to open the Monitor Performance window where you can specify the monitoring objects and monitoring period. Up to 8 objects can be specified in one graph panel. Up to 16 objects can be specified in 4 graph panels.
Item Description WWN Name A WWN name is up to 64 alphanumeric characters and some signs. Status Following statuses of the port connected with WWN. Normal: All WWNs connected with the port are monitoring target objects. Non-Integrity: The WWN is not monitored for the corresponding port, but monitored for other ports. Edit WWN Monitor Mode Click to open the Edit WWN Monitor Mode window. Add New Monitored WWNs Click to open the Add New Monitored WWNs window.
Setting fields Item Description Monitoring Switch Specify the monitoring status. Enable: Performance Monitor is monitoring the storage system. Disable: Performance Monitor is not monitoring the storage system. Sample Interval Specify the time interval of collecting statistics. • If the number of CUs to be monitored is 64 or less, you can specify from 1 to 15 minutes at intervals of 1 minute. Default is blank.
Data Range Specify a range of statistics. Short-Range is default when there is monitor data collected with Short-Range. However, Long-Range is default when there is no monitor data collected with Short-Range. • Short-Range: Graphs are displayed according to the value specified in the Sample Interval field in the Edit Monitoring Switch window. • Long-Range: Graphs are displayed 0, 15, 30, or 45 minutes on every hour.
Performance Objects Item Description Object: Types of objects to display on graphs. The list on the left specifies a large classification of monitoring objects. The list on the right specifies a small classification of monitoring objects. Monitor Data: Performance data specified in the Object field. The list on the left specifies a large classification of performance data. The list on the right specifies a small classification of performance data.
Selected Objects table Item Description Object Object types selected in the Performance Objects area. Monitor Data Monitor data types selected in the Performance Objects area. Object ID IDs of the selected objects. Remove Selected rows can be deleted from the table. Object and Monitor Data combinations The following table shows the possible Object and Monitor Data combinations that can be selected in the Performance Objects area of the Monitor Performance window.
• Item on right side of Object field Item on left side of Monitor Data field Unit of monitoring data None Usage Rate % None Write Pending Rate % • If Access Path is selected on the left side of the Object field, the item on the right side of the Monitor Data field is blank.
• If WWN is selected on the left side of the Object field, the item on the right side of the Monitor Data field is blank. Item on right side of Object field Item on left side of Monitor Data field Unit of monitoring data WWN Throughput IOPS Data Trans. MB/s Response Time ms Throughput IOPS Data Trans. MB/s Response Time ms Port • Logical Device is selected on the left side of the Object field or Base is selected on the right of the Object field.
Item on left side of Monitor Data field Item on right side of Monitor Data field Unit of monitoring data Write Back Trans. Total count/sec Cache To Drive Drive To Cache (Sequential) Drive To Cache (Random) Drive Usage Rate1 None % Drive Access Rate1 Read (Sequential) % Read (Random) Write (Sequential) Write (Random) Business Copy1,2 None % Notes: 1. Only information about internal volumes is displayed. Information about external volumes and FICON DM volumes is not displayed. 2.
• If Parity Group is selected on the left side of the Object field, the item on the right side of the Object field is blank. A parity group is displayed only when the CU number of each LDEV within the parity group is to be monitored.
• LUN is selected on the left side of the Object field or Base is selected on the right of the Object field. A parity group is displayed only when the CU number of each LDEV within the parity group is to be monitored.
• Cnt Ac-S/Cnt Ac-S Z is selected on the right side of the Object field. Item on right side of Object field Item on left side of Monitor Data field Unit of monitoring data RIO Total count Write Error Pair Synchronous Rate None % Differential Track None count Initial Copy Throughput count Data Trans. MB/s Response Time ms Throughput count Data Trans. MB/s Response Time ms Update Copy • Cnt Ac-J/Cnt Ac-J Z is selected on the right side of the Object field.
Item on right side of Object field • Item on left side of Monitor Data field Unit of monitoring data Response Time ms Data Usage Rate % Meta Data Usage Rate % Entire Storage System is selected on the left side of the Object field, or Cnt Ac-S/Cnt Ac-S Z is selected on the right side of the Object field.
• If External Storage is selected on the left side of the Object field, following items can be selected. Item on right side of Object field Item on left side of Monitor Data field Item on right side of Monitor Data field Unit of monitoring data Logical Device Data Trans. Total MB/s Read Write Response Time Total ms Read Write Parity Group* Data Trans.
Monitoring object Item Description Logical Device/Base LDEV ID ID of the volume, in the following format: LDKC:CU:LDEV. Only the LDEVs assigned to the user are displayed. LDEV Name Name of the LDEV. LDEV Name is the combination of fixed characters and numbers. Logical Device/Cnt Ac-S/Cnt Ac-S LDEV ID Z ID of the volume, in the following format: LDKC:CU:LDEV. Only the LDEVs assigned to the user are displayed. LDEV Name Name of the LDEV. LDEV Name is the combination of fixed characters and numbers.
Monitoring object Item Description Cache Name of the cache. Access Path/CHA-Cache Access Path Name of the access path. Access Path/DKA-Cache Access Path Name of the access path. Access Path/MP Blade-Cache Access Path Name of the access path. Access Path/Cache Access Path Name of the access path. Entire Storage System/ Cnt Ac-S/Cnt Ac-S Z Object Item for entire storage system. Entire Storage System/ Cnt Ac-J/Cnt Ac-J Z Object Item for entire storage system.
Unmonitored CUs table A table of the CUs that are going to be unmonitored. Item Description CU Unmonitored CU number. Number of LDEVs Number of LDEVs included in the unmonitored CUs. Current Monitor Mode Enabled: The CU is a monitoring target object. Disabled: The CU is not a monitoring target object. Select by Parity Groups Click to open the Select by Parity Group window, where you can select CUs from parity groups. Add Click to add CUs to Monitored CUs table.
Monitored CUs table A table of the CUs that are going to be monitored. Item Description CU Number of a CU which is going to be monitored. Number of LDEVs Number of LDEVs included in the monitored CUs. Current Monitor Mode Enabled: The CU is a monitoring target object. Disabled: The CU is not a monitoring target object. View CU Matrix Click to open the View CU Matrix window, where you can view following monitoring statuses of CUs.
Selected CUs to Enable Monitor table Confirm the information about the CUs to be monitored. Item Description CU CUs to be monitored. Number of LDEVs Number of LDEVs in the CU to be monitored. View CU Matrix Click to open the View CU Matrix window, where you can view following monitoring statuses of CUs. • CU which is being monitored • CU which is scheduled to be monitored • CU which is scheduled to be released from monitoring.
Monitored CUs table Item Description Monitored CUs The table consists of cells representing CUs. One cell corresponds to one CU. Each row consists of 16 cells (CUs). A set of 16 rows represents CUs for one LDKC. The table header row shows the last digit of each CU number in the form of +n (where n is an integer from 0 to 9, or a letter from A to F). Number of Monitored CUs: Total count of monitored CUs.
Available Parity Groups table Item Description Parity Group ID ID of the parity group. Number of CUs Number of CUs included in the parity group. Detail Click to display the Parity Group Properties window to view information about the CUs in the selected parity group. Parity Group Properties window Use this window to view information about the CUs in the parity group selected in the previous window.
Parity Group Properties table Item Description Parity Group ID Identification number of the parity group. CUs table Item Description CU Identification number of the CU in this parity group. Number of LDEVs Number of LDEVs included in the individual CUs. Edit WWN wizard Related topics • “Editing the WWN nickname” (page 16) • “Edit WWN window” (page 167) • “Confirm window for Edit WWN” (page 168) Edit WWN window Use this window to edit the HBA WWN and WWN name of the WWN to be monitored.
Setting fields Item Description HBA WWN Edit the worldwide name of the host bus adapter. WWNs are 16-digit hexadecimal numbers used to identify host bus adapters. WWN Name Edit a WWN name. Use up to 64 alphanumeric characters and some symbols for a WWN name. Confirm window for Edit WWN Use this window to confirm the edited HBA WWN and WWN Name and to assign a task name to the editing task. Monitored WWNs table Confirm the information about the WWNs to be monitored.
Edit WWN Monitor Mode wizard Related topics • “Adding new WWNs to monitor” (page 15) • “Edit WWN Monitor Mode window” (page 169) • “Confirm window for Edit WWN Monitor Mode” (page 171) Edit WWN Monitor Mode window Use this window to specify WWNs to be monitored or not to be monitored.
A table of WWNs that are going to be unmonitored. Item Description Port ID Name of the port. HBA WWN Worldwide name of the host bus adaptor WWN Name A WWN name is up to 64 alphanumeric characters and some signs. Current Monitor Mode Monitoring modes indicate whether WWNs are monitoring target objects or not. Enabled: The WWN is the monitoring target object. Disabled: The WWN is not the monitoring target object. Current Status Status of the port connected with WWN.
A table of WWNs that are going to be unmonitored. Item Description Port ID Name of the port. HBA WWN Worldwide name of the host bus adaptor. WWN Name A WWN name is up to 64 alphanumeric characters and some signs. Current Monitor Mode Monitoring modes indicate whether WWNs are monitoring target objects or not. Enabled: The WWN is the monitoring target object. Disabled: The WWN is not the monitoring target object. Current Status Status of the port connected with WWN.
Selected WWNs to Disable Monitor table Confirm the information about the WWNs not to be monitored. Item Description Port ID Port name not to be monitored. HBA WWN Worldwide name of the host bus adapter not to be monitored. WWN Name Nickname of WWN not to be monitored. The name consists of up to 64 alphanumeric characters and some signs. Status Status of a WWN not to be monitored. Normal: The WWN connected with a port is the monitoring target object.
Add New Monitored WWNs window Use this window to add new WWNs to be monitored. HBA WWN Specify a worldwide name of the host bus adapter. WWNs are 16-digit hexadecimal numbers used to identify host bus adapters. WWN Name Specify a worldwide name using up to 64 characters for a WWN name.
Available Ports table Item Description Port ID Name of the port available in the storage system. Number of Monitored WWNs Number of monitored WWNs in the port. Number of Unmonitored WWNs Number of unmonitored WWNs in the port. Add Select ports, then click Add to add the combinations of HBA WWN and the selected ports into the Selected WWNs table.
Selected WWNs table A list of WWNs to be monitored. Item Description Port ID Name of the port selected for monitoring. HBA WWN WWN selected for monitoring. WWN Name WWN name is up to 64 alphanumeric characters and some signs. Remove Select the row to be deleted. Click to remove a row from the table. Confirm window for Add New Monitored WWNs Use this window to confirm the new monitoring information and to assign a task name to the editing task.
Selected WWNs table Confirm the list of combinations of ports and WWNs added as monitoring target objects. Item Description Port ID Name of the port selected for monitoring. HBA WWN WWN selected for monitoring. WWN Name WWN name is up to 64 alphanumeric characters and some signs. Add to Ports wizard Related topics • “Connecting WWNs to ports” (page 17) • “Add to Ports window” (page 176) • “Confirm window for Add to Ports” (page 179) Add to Ports window Use this window to add a WWN to the port.
HBA WWN Specify a worldwide name of the host bus adapter. WWNs are 16-digit hexadecimal numbers used to identify host bus adapters. WWN Name Specify a worldwide name using up to 64 characters for a WWN name.
A list of available ports in the storage system. Item Description Port ID Name of the port available in the storage system. Number of Monitored WWNs Number of monitored WWNs in the port. Number of Unmonitored WWNs Number of unmonitored WWNs in the port. Add Select ports, then click Add to add the combinations of HBA WWN and the selected ports into the Selected WWNs table. Selected WWNs table A list of WWNs to be monitored.
Confirm window for Add to Ports Use this window to confirm new WWNs related to ports and to assign a task name to the editing task. Selected WWNs table Confirm the information of the WWNs to become the monitoring target objects. Item Description Port ID Name of the port selected for monitoring HBA WWN WWN selected for monitoring. WWN Name WWN name is up to 64 alphanumeric characters and some signs. Monitor window Use this window to view line graphs of monitored objects.
Item Description Graph panel Shows line graphs. The line graph is displayed at the left of the graph panel, and explanatory notes are displayed at the right of the graph panel. Following operations can be performed. • If you put the mouse cursor over a point on the graph, a tool tip with more information appears. • When you click a note on the right of the graph panel, you can show or hide points on the graph panel.
Graph display area Shows graph panels. Item Description Monitoring Term Shows the monitor period in the bottom left corner of this window. The first monitored time and the latest time are shown. If Use Real Time is selected, the interval and the date of last update are also shown. The following icon and the message are displayed while changing the configuration: Graphs cannot be updated due to the configuration changing. Wait for a while.
Item Description External Volume: Indicates an external volume assigned to the storage system. Journal: Indicates a journal. Resource ID Shows the ID of the resource. Resource Name Shows the name of the following resources: LDEV: An LDEV name is displayed. External Volume: A hyphen (-) is displayed because an external volume has no name. Journal: A hyphen (-) is displayed because a journal has no name.
Setting fields Item Description Time Range Specify dates in the From and To fields to define a time range for displaying monitoring data in a performance graph. You can input directly or select from the calendar. When you specify a time range, Performance Monitor calculates the length of the specified period and displays the total time in hours and minutes. From: Specify the date and time to start monitoring performance. To: Specify the date and time to stop monitoring performance.
Object Object types to display graphs. The list on the left specifies a large classification of monitoring objects. The list on the right specifies a small classification of monitoring objects. Monitor Data Performance data specified in the Object field. The list on the left specifies a large classification of performance data. The list on the right specifies a small classification of performance data.
Selected Objects table Objects to display the graph. Item Description Object Object to display the graph. Monitor Data Type of monitoring data. Object ID ID of the monitoring object. Remove Remove the object in this table. Object and Monitor Data combinations The following table shows the possible Object and Monitor Data combinations that can be selected in the Performance Objects area of the Monitor Performance window.
• If Cache is selected on the left side of the Object field, the item on the right side of the Monitor Data is blank field. Item on right side of Object field Item on left side of Monitor Data field Unit of monitoring data None Usage Rate % None Write Pending Rate % • If Access Path is selected on the left side of the Object field, the item on the right side of the Monitor Data field is blank.
• If WWN is selected on the left side of the Object field, the item on the right side of the Monitor Data field is blank. Item on right side of Object field Item on left side of Monitor Data field Unit of monitoring data WWN Throughput IOPS Data Trans. MB/s Response Time ms Throughput IOPS Data Trans. MB/s Response Time ms Port • Logical Device is selected on the left side of the Object field or Base is selected on the right of the Object field.
Item on left side of Monitor Data field Item on right side of Monitor Data field Unit of monitoring data Write Back Trans. Total count/sec Cache To Drive Drive To Cache (Sequential) Drive To Cache (Random) Drive Usage Rate None % Drive Access Rate Read (Sequential) % Read (Random) Write (Sequential) Write (Random) Business Copy* None % *Information for Business Copy and Business Copy Z is displayed. • Cnt Ac-S/Cnt Ac-S Z is selected on the right side of the Object field.
• If Parity Group is selected on the left side of the Object field, the item on the right side of the Object field is blank. A parity group is displayed only when the CU number of each LDEV within the parity group is to be monitored.
• LUN is selected on the left side of the Object field or Base is selected on the right of the Object field. A parity group is displayed only when the CU number of each LDEV within the parity group is to be monitored.
• Cnt Ac-S/Cnt Ac-S Z is selected on the right side of the Object field. Item on right side of Object field Item on left side of Monitor Data field Unit of monitoring data RIO Total count Write Error Pair Synchronous Rate None % Differential Track None count Initial Copy Throughput count Data Trans. MB/s Response Time ms Throughput count Data Trans. MB/s Response Time ms Update Copy • Cnt Ac-J/Cnt Ac-J Z is selected on the right side of the Object field.
Item on right side of Object field • Item on left side of Monitor Data field Unit of monitoring data Response Time ms Data Usage Rate % Meta Data Usage Rate % Entire Storage System is selected on the left side of the Object field or Cnt Ac-S/Cnt Ac-S Z is selected on the right side of the Object field.
• If External Storage is selected on the left side of the Object field, following items can be selected. Item on right side of Object field Item on left side of Monitor Data field Item on right side of Monitor Data field Unit of monitoring data Logical Device Data Trans. Total MB/s Read Write Response Time Total ms Read Write Parity Group* Data Trans.
Monitoring object Item Description Logical Device/Base LDEV ID ID of the volume, in the following format: LDKC:CU:LDEV. Only the LDEVs assigned to the user are displayed. LDEV Name Name of the LDEV. LDEV Name is the combination of fixed characters and numbers. Logical Device/Cnt Ac-S/Cnt Ac-S LDEV ID Z LDEV Name Name of the LDEV. LDEV Name is the combination of fixed characters and numbers. LDEV ID ID of the volume, in the following format: LDKC:CU:LDEV.
Monitoring object Item Description Cache Name of the cache. Access Path/CHA-Cache Access Path Name of the access path. Access Path/DKA-Cache Access Path Name of the access path. Access Path/MP Blade-Cache Access Path Name of the access path. Access Path/Cache Access Path Name of the access path. Entire Storage System/ Cnt Ac-S/Cnt Ac-S Z Object Item for entire storage system. Entire Storage System/ Cnt Ac-J/Cnt Ac-J Z Object Item for entire storage system.
Object Object types to display graphs. The list on the left specifies a large classification of monitoring objects. The list on the right specifies a small classification of monitoring objects. Monitor Data Performance data specified in the Object field. The list on the left specifies a large classification of performance data. The list on the right specifies a small classification of performance data.
Selected Objects table Objects to display the graph. Item Description Object Object to display the graph. Monitor Data Type of monitoring data. Object ID ID of the monitoring object. Remove Remove the object in this table. Object and Monitor Data combinations The following table shows the possible Object and Monitor Data combinations that can be selected in the Performance Objects area of the Monitor Performance window.
• If Cache is selected on the left side of the Object field, the item on the right side of the Monitor Data is blank field. Item on right side of Object field Item on left side of Monitor Data field Unit of monitoring data None Usage Rate % None Write Pending Rate % • If Access Path is selected on the left side of the Object field, the item on the right side of the Monitor Data field is blank.
• If WWN is selected on the left side of the Object field, the item on the right side of the Monitor Data field is blank. Item on right side of Object field Item on left side of Monitor Data field Unit of monitoring data WWN Throughput IOPS Data Trans. MB/s Response Time ms Throughput IOPS Data Trans. MB/s Response Time ms Port • Logical Device is selected on the left side of the Object field or Base is selected on the right of the Object field.
Item on left side of Monitor Data field Item on right side of Monitor Data field Unit of monitoring data Write Back Trans. Total count/sec Cache To Drive Drive To Cache (Sequential) Drive To Cache (Random) Drive Usage Rate None % Drive Access Rate Read (Sequential) % Read (Random) Write (Sequential) Write (Random) Business Copy 1,2 None % Notes: 1. Only information about internal volumes is displayed. Information about external volumes and FICON DM volumes is not displayed. 2.
• If Parity Group is selected on the left side of the Object field, the item on the right side of the Object field is blank. A parity group is displayed only when the CU number of each LDEV within the parity group is to be monitored.
• LUN is selected on the left side of the Object field or Base is selected on the right of the Object field. A parity group is displayed only when the CU number of each LDEV within the parity group is to be monitored.
• Cnt Ac-S/Cnt Ac-S Z is selected on the right side of the Object field. Item on right side of Object field Item on left side of Monitor Data field Unit of monitoring data RIO Total count Write Error Pair Synchronous Rate None % Differential Track None count Initial Copy Throughput count Data Trans. MB/s Response Time ms Throughput count Data Trans. MB/s Response Time ms Update Copy • Cnt Ac-J/Cnt Ac-J Z is selected on the right side of the Object field.
Item on right side of Object field • Item on left side of Monitor Data field Unit of monitoring data Response Time ms Data Usage Rate % Meta Data Usage Rate % Entire Storage System is selected on the left side of the Object field or Cnt Ac-S/Cnt Ac-S Z is selected on the right side of the Object field.
• If External Storage is selected on the left side of the Object field, following items can be selected. Item on right side of Object field Item on left side of Monitor Data field Item on right side of Monitor Data field Unit of monitoring data Logical Device Data Trans. Total MB/s Read Write Response Time Total ms Read Write Parity Group* Data Trans.
Monitoring object Item Description Logical Device/Base LDEV ID ID of the volume, in the following format: LDKC:CU:LDEV. Only the LDEVs assigned to the user are displayed. LDEV Name Name of the LDEV. LDEV Name is the combination of fixed characters and numbers. Logical Device/Cnt Ac-S/Cnt Ac-S LDEV ID Z ID of the volume, in the following format: LDKC:CU:LDEV. Only theLDEVs assigned to the user aredisplayed. LDEV Name Name of the LDEV. LDEV Name is the combination of fixed characters and numbers.
Monitoring object Item Description Cache Name of the cache. Access Path/CHA-Cache Access Path Name of the access path. Access Path/DKA-Cache Access Path Name of the access path. Access Path/MP Blade-Cache Access Path Name of the access path. Access Path/Cache Access Path Name of the access path. Entire Storage System/ Cnt Ac-S/Cnt Ac-S Z Object Item for entire storage system. Entire Storage System/ Cnt Ac-J/Cnt Ac-J Z Object Item for entire storage system.
B Performance Control GUI reference This chapter provides detailed information about the Performance Control GUI. Performance Control window The Performance Control window displays the status of performance monitoring, allows you to set the monitoring term, and provides access to the Performance Control main window. Item Description Monitoring Switch Enable: Performance Monitor is monitoring the storage system Disable: The storage system is not being monitored.
Port tab of the Performance Control main window Use this tab to set the limit on the performance of non-prioritized ports and set the threshold on the performance of prioritized ports. Item Description Current Control Status Shows the current control status of the system. • Port Control indicates the system is controlled by the upper limits and threshold specified on the Port tab. • WWN Control indicates the system is controlled by the upper limits and threshold specified on the WWN tab.
Item Description Ports table A list of ports, including the I/O rate or the transfer rate for each port. You can specify the port attributes, and the threshold and upper limit of the port traffic. The measurement unit for the values in the list can be specified by the drop-down list above this table. The port traffic (I/O rate and transfer rate) is monitored by Performance Monitor. To specify the monitoring period, use the Monitoring Term area of Performance Monitor.
Item Description Reset Restores the last applied settings in the window. When you click this button, all changes displayed with the blue text in the window are canceled. Initialize Changes the settings in this window as explained below, and then applies the resulting settings to the storage system: • All ports become prioritized ports. • The threshold value for all ports becomes 0 (zero). • The window will display a hyphen (-) instead of 0 (zero).
Item Description Current Control Status The current system control. • Port Control: The system is controlled by the upper limits and threshold specified on the Port tab. • WWN Control: The system is controlled by the upper limits and threshold specified on the WWN tab. • No Control: The system performance is not controlled by Performance Control. Tip: If Port Control appears when the WWN tab is active, click Apply to switch control so that WWN Control is displayed.
Item Description The WWN and PFC names of the host bus adapters are displayed on the right of the host bus adapter icon ( ) below Monitor. WWNs (Worldwide Name) are 16-digit hexadecimal numbers used to uniquely identify host bus adapters. PFC names are nicknames assigned by the system administrator so that they can easily identify each host bus adapter. Only the WWN is displayed on the right of the host bus adapter icon ( ) below Non-Monitor.
Item Description The list contains the following columns (use the slide bar to view all of the columns): • WWN: column indicates WWNs of host bus adapters. This column does not appear when you select the Storage System folder in the lower-left tree. • PFC Name: PFC names of host bus adapters. Use Performance Control to assign a PFC name to each host bus adapter so that you can easily identify each host bus adapters in the Performance Control main window.
Item Description WWN list (continued) • The WWN Port column contains the following: Ave.: Indicates the average I/O rate or the average transfer rate for the specified period. The Ave. column is also displayed when you select an icon in the lower-left tree. In this case, the Ave. column shows the average value same as that of WWN Total. When you select the Storage System folder in the lower-left tree, the Ave. column shows the sum of the traffic of the host bus adapters registered on each PFC group. Max.
Item Description This check box is available only when the following Performance Control settings on ports in a removed channel adapter remain on the SVP: • The setting of prioritized ports or non-prioritized ports. • The setting of prioritized WWNs or non-prioritized WWNs. Apply Applies the settings in this window to the storage system. Reset Restores the last applied settings in the window. When you click this button, all changes displayed in blue text in the window are canceled.
C Cache Residency GUI reference This chapter provides detailed information about the Cache Residency GUI. Cache Residency window This window provides the Cache Residency information for the connected HP XP7 Storage system and provides access to all Cache Residency operations. Item Description Prestaging Enables and disables the prestaging function for Cache Residency. If you select the Prestaging check box check box and click Apply, a Yes/No confirmation is displayed.
Item Description : Indicates an open/expanded folder. An open LDKC folder shows the CUs that belong to that LDKC. An expanded CU folder shows the LDEVs that belong to that CU. : Indicates an unopened/unexpanded LDKC or CU folder. :Indicates that the LDEV is an internal volume for which Cache Residency is not set or an external volume whose Cache mode is set to Enable. : Indicates that the LDEV is an internal volume for which Cache Residency is set or an external volume whose Cache mode is set to Enable.
Item Description A capacity in blue italics indicates a requested operation. Mode Cache Residency cache mode: • PRIO: Priority mode. • BIND: Bind mode. • A dash (-) indicates that the area is not allocated for Cache Residency cache. A cache mode in blue italics indicates a requested operation. Prestage Setting for the prestaging function: • Blank: Indicates that the prestaging function is not set. • ON: The prestaging function is set. A prestaging mode in blue italics indicates a requested operation.
Operations box Item Description Cache Residency Mode Selects the mode for the data to be added to Cache Residency cache: • Bind: Sets the bind mode. Bind mode is not available to external volumes whose cache mode is set to Disable (which is the mode that disables the use of the cache when there is an I/O request from the host). • Priority: Sets priority mode. Once you have requested a Cache Residency operation, the mode options are unavailable.
Item Description This button is unavailable when Cache Residency operations to set data into cache have been requested. To enable the Release, either perform the requested set operations, or cancel the requested set operations. Multi Set dialog box Use this dialog box to select multiple LDEVs with data that you want to place into Cache Residency cache. The items shown on the Multi Set dialog box reflect the options selected on the Cache Residency window.
Multi Set LDEV table Item Description LDEV LDEV number. An LDEV number ending with # (for example, 01#) is an external volume. Size Size of the LDEV. Emulation Emulation type of the LDEV. RAID RAID level of the LDEV. A dash (-) indicates the LDEV is an external volume. Multi Release dialog box Use this dialog box to release Cache Residency data from cache for more than one LDEV.
Multi-Release LDEV table Item Description LDEV LDEV num. An LDEV number ending with # (for example, 01#) is an external volume. Emulation Emulation type of the LDEV.
Glossary allocation The ratio of allocated storage capacity versus total capacity as a percentage. Allocated storage refers to those logical devices (LDEVs) that have paths assigned to them. Allocated storage capacity is the sum of the storage of these LDEVs. Total capacity is the sum of the capacity of all LDEVs on the disk array. BC P9000 or XP Business Copy. An HP application that provides volume-level, point-in-time copies in the disk array.
to be associated with 1 to 36 LDEVs. Essentially, LUSE makes it possible for applications to access a single large pool of storage. M-VOL Main volume. MCU Main control unit. OPEN-x A general term describing any of the supported OPEN emulation modes (for example, OPEN-E). There are two types of OPEN-x devices: legacy OPEN-x devices with a fixed size (such as OPEN-3, OPEN-8, OPEN-9, and OPEN-E), and OPEN-V, which has a variable size and is a CVS-based volume.
Index A D access paths and I/O usage rates, 30 Auto LUN restrictions on manual migration across multiple CLPRs , 80 data drive access rates, 39 data drive and I/O usage rates, 39 data prestaging, 73 data recovery and reconstruction processor and I/O usage rates, 29 data transfer size and I/O usage rates, 33 document conventions, 143 related information, 142 documentation HP website, 142 providing feedback, 142 B back-end performance and I/O usage rates, 38 batch file preparing for use with Export Tool,
cache memory, 29 data drive, 39 data drive access, 39 data recovery and reconstruction processor, 29 data transfer size, 33 processor blades, 28 throughput, 31 write pending, 29 L LDEVs placing into cache, 83 releasing from cache, 85 log files Export Tool, 98 M mainframe systems calculating cache requirements, 78 managing resident cache, 72 modes bind, 72 changing after Cache Residency is registered in cache, 86 priority, 72 Monitor Performance window, 12 monitoring starting, 14 stopping, 20 N non-priori
